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
save_all for 2D dataset does not save set_psf() #1873
Labels
Comments
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 6, 2023
The problem is that we do not include the "set_psf" call in the ASCII serialization. Since it's not obvious what the text will be we can't check the output serialization, but we can at least check that the PSF has not been applied when we restore the saved file.
So, it's supposed to add the sherpa/sherpa/astro/ui/serialize.py Lines 819 to 828 in b230164
but it isn't. One of the problems with a big "try/except` block - it's easy to not notice it's skipping for some other issue.... |
Do, it's because Doh. |
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 6, 2023
This was a logical error in the existing code, coupled with incomplete testing. The fix is simple: we just need to loop through the session's _psf dictionary and use the key,value as the arguments to set_psf call(s).
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 7, 2023
The problem is that we do not include the "set_psf" call in the ASCII serialization. Since it's not obvious what the text will be we can't check the output serialization, but we can at least check that the PSF has not been applied when we restore the saved file.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 7, 2023
This was a logical error in the existing code, coupled with incomplete testing. The fix is simple: we just need to loop through the session's _psf dictionary and use the key,value as the arguments to set_psf call(s). There is still something weird going on with the warning messages for this test. I don't understand but have got it to a point where it works for me.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 7, 2023
This was a logical error in the existing code, coupled with incomplete testing. The fix is simple: we just need to loop through the session's _psf dictionary and use the key,value as the arguments to set_psf call(s). There is still something weird going on with the warning messages for this test. I don't understand but have got it to a point where it works for me.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 8, 2023
The problem is that we do not include the "set_psf" call in the ASCII serialization. Since it's not obvious what the text will be we can't check the output serialization, but we can at least check that the PSF has not been applied when we restore the saved file.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 8, 2023
This was a logical error in the existing code, coupled with incomplete testing. The fix is simple: we just need to loop through the session's _psf dictionary and use the key,value as the arguments to set_psf call(s). There is still something weird going on with the warning messages for this test. I don't understand but have got it to a point where it works for me.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 9, 2023
The problem is that we do not include the "set_psf" call in the ASCII serialization. Since it's not obvious what the text will be we can't check the output serialization, but we can at least check that the PSF has not been applied when we restore the saved file.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 9, 2023
This was a logical error in the existing code, coupled with incomplete testing. The fix is simple: we just need to loop through the session's _psf dictionary and use the key,value as the arguments to set_psf call(s). There is still something weird going on with the warning messages for this test. I don't understand but have got it to a point where it works for me.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 10, 2023
The problem is that we do not include the "set_psf" call in the ASCII serialization. Since it's not obvious what the text will be we can't check the output serialization, but we can at least check that the PSF has not been applied when we restore the saved file.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 10, 2023
This was a logical error in the existing code, coupled with incomplete testing. The fix is simple: we just need to loop through the session's _psf dictionary and use the key,value as the arguments to set_psf call(s). There is still something weird going on with the warning messages for this test. I don't understand but have got it to a point where it works for me.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 11, 2023
The problem is that we do not include the "set_psf" call in the ASCII serialization. Since it's not obvious what the text will be we can't check the output serialization, but we can at least check that the PSF has not been applied when we restore the saved file.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 11, 2023
This was a logical error in the existing code, coupled with incomplete testing. The fix is simple: we just need to loop through the session's _psf dictionary and use the key,value as the arguments to set_psf call(s). There is still something weird going on with the warning messages for this test. I don't understand but have got it to a point where it works for me.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 25, 2023
The problem is that we do not include the "set_psf" call in the ASCII serialization. Since it's not obvious what the text will be we can't check the output serialization, but we can at least check that the PSF has not been applied when we restore the saved file.
DougBurke
added a commit
to DougBurke/sherpa
that referenced
this issue
Sep 25, 2023
This was a logical error in the existing code, coupled with incomplete testing. The fix is simple: we just need to loop through the session's _psf dictionary and use the key,value as the arguments to set_psf call(s). There is still something weird going on with the warning messages for this test. I don't understand but have got it to a point where it works for me.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed from a CIAO helpdesk ticket that the sherpa
save_all
output does not save the equivalent ofset_psf
.For example:
and look at the
my.script
output, it loads the PSF,but it never runs
set_psf
. When I run the script (well, I just cut-n-pasted it) then the PSF is not actually used.Tested Linux RH8 CIAO 4.14, 4.15 and ciaox (Sherpa 4.15.1+196.g15479eb1)
dummy data
The text was updated successfully, but these errors were encountered: