search

spacetelescope / jwst

Python library for science observations from the James Webb Space Telescope
https://jwst-pipeline.readthedocs.io/en/latest/
Other
566 stars 167 forks source link

Bad ramp flagging step needed in calwebb_detector1 #1456

Open karllark opened 6 years ago

karllark commented 6 years ago

The JCalWG has asked for a bad ramp flagging step to be run at the end of calwebb_detector1.

Text from JCalWG confluence page: Even with all the corrections to the ramps, it is still likely that there will be ramps that are significantly non-linear. It will be useful to flag such ramps as bad to advise later ensemble processing of data (e.g., when mosiaicking such bad ramp data may be automatically rejected).
The chisqr should be computed correctly accounting for the covariance in the ramp (i.e., using the noise model created covariance matrix). The threshold above which to designate a pixel as bad will be provided by a calibration reference file.

hbushouse commented 3 years ago

@stscijgbot-jp

stscijgbot-jp commented 2 years ago

This issue is tracked on JIRA as JP-2158.

stscijgbot-jp commented 2 years ago

Comment by Howard Bushouse on JIRA:

Karl Gordon Anton Koekemoer This request was originally submitted as a github issue. I've now created the corresponding Jira ticket. So in the meantime it hasn't been tracked or included in the INS priority list for pipeline tickets. Is this something that should go into the backlog for "optimal" enhancements?

stscijgbot-jp commented 2 years ago

Comment by Karl Gordon on JIRA:

Yes, this is in the list for the enhanced version of the pipeline. So, it should go in the backlog.