-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
'IndexError: tuple index out of range' error when using Confidence via fit.est_errors method #342
Comments
I think the issue might be that the fit object only thinks there's two thawed parameters, even though there are three. Just before calling
If I call
|
DougBurke
changed the title
Strange error when using Confidence via fit.est_errors method
'IndexError: tuple index out of range' error when using Confidence via fit.est_errors method
Mar 6, 2017
So, if you get this, one work around appears to be
|
dtnguyen2
added a commit
to dtnguyen2/sherpa
that referenced
this issue
Jul 17, 2019
DougBurke
added a commit
to dtnguyen2/sherpa
that referenced
this issue
Sep 30, 2019
Update the fit documentation to remove the workaround since sherpa#342 has been fixed. The example code was re-run to check it still gave the same answers, and it did modulo the following - numeric precision (values have been updated to match numpy 1.17.2) - the change to add the covariance-estimated errors with the LevMar fit output The documentation has been updated for these changes as well.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following sequence, fitting a simple 1D dataset with errors using chi-square statistics, fails when it comes to using Confidence to estimate the errors. It appears to be due to the two-phase approach (fit with c1 frozen then with c1 thawed). I've put details and test scripts in
https://gist.github.com/DougBurke/2e5000ed458d261537907b569f2afc02
This results in the error:
This is not a recent change, as I see the same behaviour in CIAO 4.8 (with Python 2.7) and master (with Python 3.5). It also appears not to happen using the
sherpa.ui
layer.Note that the error case (
python fail.py 1
in the gist) reports this when evaluating the errors before it errors outwhereas the successful run reports
What is interesting here is that the c2 bounds are very different in the two runs: ~0.03 in the second case but 0.001 and lower in the failing case. My guess is that this is part of the problem that leads to the
IndexError
(i.e. something internal is really messed up).The text was updated successfully, but these errors were encountered: