You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should update the code such that it can use 0_ramp_fit or 1_ramp_fit files. This will make it easier for people who have exposures containing a single integration, where the pipeline (may not?) output a 1_ramp_fit file. I think the file format of the 0_ramp_fit and 1_ramp_fit files are the same. I think the only difference is the dimensionality of the data.
Perhaps it would be worth adding a check that the NINT header keyword is equal to 1 if the user attempts to use 0_ramp_fit files.
@KevinVolkSTScI and @bsunnquist made updates to the code to get it to work with their files. Are your updates generic enough that they can be applied to all instruments?
The text was updated successfully, but these errors were encountered:
My code changes are not specific to an instrument. They should work for NIRSpec as well as for NIRISS. I will try to post the changes today or tomorrow morning, but I have other pressing issues right now so there is some chance it will take longer.
My intention was if someone did not have 1_ramp.fits files it would by default look at 0_ramp.fits files.
I must of done something wrong. Bryan take a look at the module 'read_slope_integrations'
that is where I tried to do this. Maybe you can easily see what I did wrong.
We should update the code such that it can use 0_ramp_fit or 1_ramp_fit files. This will make it easier for people who have exposures containing a single integration, where the pipeline (may not?) output a 1_ramp_fit file. I think the file format of the 0_ramp_fit and 1_ramp_fit files are the same. I think the only difference is the dimensionality of the data.
Perhaps it would be worth adding a check that the NINT header keyword is equal to 1 if the user attempts to use 0_ramp_fit files.
@KevinVolkSTScI and @bsunnquist made updates to the code to get it to work with their files. Are your updates generic enough that they can be applied to all instruments?
The text was updated successfully, but these errors were encountered: