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
It looks like the SSB commands as they are at the moment create the requested output files, but also output 'ramp' files in the working directory. My assumption is that these files are equivalent to the specified output files (e.g. myfile_dq_init_superbias.fits), but the filename gives no clue as to the steps being run.
Try to find a way to prevent this output from being saved, as it is not useful.
The text was updated successfully, but these errors were encountered:
According to the documentation, this file shouldn't be appearing. It looks like all we should need to do is set save_calibrated_ramp to False. I'm confused though because the documentation says that the default is for it to be False.
I've run the pipeline several times lately using the defaults (in python), and it always only saves out the _rate.fits and _rateints.fits file. I've never gotten a _ramp.fits file. Maybe it's an artifact leftover in strun that doesn't appear when using the python methods? SCSB is having a really hard time synching the strun code with the python "run" and "call" methods. There are a lot of inconsistencies that they're trying to work out, especially when it comes to how files get saved.
It looks like the SSB commands as they are at the moment create the requested output files, but also output 'ramp' files in the working directory. My assumption is that these files are equivalent to the specified output files (e.g. myfile_dq_init_superbias.fits), but the filename gives no clue as to the steps being run.
Try to find a way to prevent this output from being saved, as it is not useful.
The text was updated successfully, but these errors were encountered: