Page History
...
Stage 1: Detector Processing TSO testing
| 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. |
|
|
| |||||||||||||||||||||||
| 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. |
|
|
| |||||||||||||||||||||
| 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). |
|
|
| ||||||||||||||||||||||||||||
| jump |
| Step produced no errors. Manually introduced jumps were detected. |
|
|
| |||||||||||||||||||||||||
| ramp_fitting |
| *rateints files show spikes not seen with my own ramp fits, and do not report timestamps. This has been identified as an awesimsoss header bug. |
| produced rateints with 7.5 and independent linear fits; substantial difference in a subset of data. |
|
| ||||||||||||||||||||||||
| gain_scale |
|
|
|
| ||||||||||||||||||||||||||
Extended comments by instrument branch:
...
