Update ASN rules to handle NIRSpec MOS exposures with sub-pixel dithers #8183
Comments
7 tasks
|
Comment by Howard Bushouse on JIRA: Fixed by #8184 |
|
Comment by Howard Bushouse on JIRA: Original issue was submitted via help desk, regarding observations in program 2640. So once B10.2 is installed in Ops, this should be testable by reprocessing data for PID 2640. |
|
Comment by Christian Hayes on JIRA: I ran across this fix in some NIRSpec build test data (PID 1810) and confirmed with PID 2640 that the spectral dithers are now being excluded from MOS associations. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue JP-3505 was created on JIRA by Howard Bushouse:
As described in JWSTDMS-866, NIRSpec MOS observations taken as prime, with NIRCam imaging in parallel, that use one of the "compromise" dither patterns (a single dither pattern that produces useful data in both instruments) such as "3-POINT-WITH-NIRCAM-SIZEn", currently result in spec2 associations for the NIRSpec exposures that designate one image as "science" and all other images from the entire dither/nod pattern as "background". These dither patterns use the traditional 3-point nodding between MSA shutters as the primary pattern and then either 2 or 3-point sub-pixel dithers at each primary nod position. Hence the sub-pixel images taken at the same primary nod position should not be treated as background. Only the images from the other 2 primary nod positions should be treated as background.
One of the reasons the current ASN generator rules are not handling this correctly is the fact that there's no information in the pool file to indicate that sub-pixel dithers are involved, hence the generator thinks that all images are simply different nod positions. SDP work done via JWSTDMS-866 will correct that situation by populating both the PRIDTPTS and SUBPXPTS (number of primary dither points and number of sub-pixel dither points, respectively) keywords for these observations. Once that has been implemented, the SUBPXPTS value in the pool files will no longer be "NULL" and will have the appropriate value of 2 or 3.
The ASN generator code then also needs a minor update to take advantage of the SUBPXPTS value for NRS MOS observations, in order to create the appropriate spec2 ASN files, where only the images from other primary nod positions are designated as "background" members. This is handled within the "make_nod_asns" function in rules_level2_base.py.
The text was updated successfully, but these errors were encountered: