Closed jdtsmith closed 1 year ago
@jancami what say you? I don't recall where you got the resolution coefficients
for sws, but clearly something isn't right. Is this a speed
issue? Not an SWS expert...
@drvdputt @jdtsmith The resolution for speed 1 and speed 2 should be the same and roughly equal to R/7. A speed 3 should be R/4 and speed 4 should be R/3 where R is the full resolution for an AOT 6 scan. I think I may have labeled that speed 0. I'll have a look at this.
Problem identified and resolved. Pull Request #238 should fix this. I have also slightly modified the naming of the segments. JD's test above becomes:
resolution("iso.sws.aot1.speed2.*", [3,5,10,16,25]) masked_array( data=[[471, --, --], [452, --, --], [446, --, --], [410, --, --], [305, --, --]], mask=[[False, True, True], [False, True, True], [False, True, True], [False, True, True], [False, True, True]], fill_value=999999)
which matches the figures a lot better!
But the resolution function is giving me this
I found this while looking at the included SWS data
pahfit/data/ISO_SWS/Orion_D5_ISO-SWS_merged.ipac
, and doing a fit. This data is supposedly AOT1 speed 2 (is this the same as SWS01 speed 2?), but the lines seem to narrow.Manually hacking the resolution to 500 (as stated in the readme for the ISO files) makes the fit much better.
Originally posted by @drvdputt in https://github.com/PAHFIT/pahfit/issues/235#issuecomment-1268903866