Page History
...
- NIRISS testing is being done using awesimsoss NIRISS/SOSS simulations of HAT-P-1K2-141 (which has a short transit duration, hence the selection). Care must be taken as this is the first end-to-end simulation of awesimsoss (which is under active development). In-progress notebooks of each stage testing can be found here.
- MIRI testing is being done using MIRISim simulations of MIRI/LRS.
- NIRCam testing is being done using Mirage simulations.
- NIRSpec testing is being done on CV3 data.
...
| 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)some deviations that most likely have to do with DMS-detector frame rotations. |
|
| This step is sufficiently tested in unit tests. It is skipped for MIRI subarray data so only applies to FULL array imaging TSOs, 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 detectedDetected jumps are consistent with pipeline specifications. |
|
|
| |||||||||||||||||||||||||
| ramp_fitting |
| *rateints files show small spikes that do not show on my own ramps, even when being careful with GROUPSDQ (see notebook). |
| produced rateints with 7.5 and independent linear fits; substantial difference in a subset of data. |
|
| ||||||||||||||||||||||||
| gain_scale |
|
|
|
| ||||||||||||||||||||||||||
Extended comments by instrument branch:
- NIRISS:
- Regarding error on ramp_fitting step, Nestor Espinoza is looking into what headers have to be added to awesimsoss in order for the step to properly work. The problem has to do with the fact that the pipeline is not reading the time-stamps — and hence not calculating the rates correctly. After that's done, will run the step again and compare against his ramp fit (which was done using a simple OLS). - NIRCam
- MIRI:
- NIRSpec:
Stage 2: Spectroscopic processing TSO testing
...
