Page History
...
| Pipeline step | NIRISS status | NIRISS comments | NIRCam status | NIRCam comments | MIRI status | MIRI comments | NIRSpec status | NIRSpec comments | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| group_scale |
| The step is supossed to do nothing for NIRISS/SOSS (here, a group = 1 frame). Indeed, nothing changes when running this step, except for the length of the ASDF element in the HDU list object, which is normal. |
| N/A |
| |||||||||||||||||||||||||
| dq_init |
| This step correctly initializes the data-quality flags, as it is supposed to do, according to the reference mask in CRDS. |
|
| (high-level test) |
| ||||||||||||||||||||||||
| saturation |
| This step does what is expected to do: it captures saturated pixels and flags them in the GROUPDQ masks. The simulations used for this validation had saturated pixels and they were correctly identified (flagged) by the pipeline. |
|
| (high-level) |
| ||||||||||||||||||||||||
| superbias |
| Tested my own bias substraction using reference files and got exact same results. |
| N/A |
| |||||||||||||||||||||||||
| reset | N/A | N/A |
| This was tested on a TSO imaging file separately since this step does not currently run by default. The test passed with no issues. | N/A | |||||||||||||||||||||||||
| linearity |
| Tested linearity correction using reference files and got exact same results. |
|
|
| |||||||||||||||||||||||||
| rscd | N/A | N/A |
| N/A | ||||||||||||||||||||||||||
| dark_current |
| Dark frames perform expected corrections on the data. |
|
|
| |||||||||||||||||||||||||
| refpix |
| Currently, does not do anything to NIRISS/SOSS simulations, as reference pixels there are set to zero. When injecting a fake strain of reference pixels got results I still don't understand (see below). |
|
| This step is sufficiently tested in unit tests. It is skipped for MIRI subarray data so only needs testing for applies to FULL array imaging TSOs. this step is sufficiently tested in unit tests., and note that MIRISim's implementation of Refpix is different from the pipeline step, so may give unexpected results. |
| ||||||||||||||||||||||||
| jump |
| Step produced no errors. Manually introduced jumps were detected. |
|
|
| |||||||||||||||||||||||||
| ramp_fitting |
| *rateints files show small spikes that do not show on my own ramps, even when being careful with GROUPSDQ. |
| produced rateints with 7.5 and independent linear fits; substantial difference in a subset of data. |
|
| ||||||||||||||||||||||||
| gain_scale |
|
|
|
| ||||||||||||||||||||||||||
...
