search

spacetelescope / jwst

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

No data on NRS2 for NRS_MSASPEC with Prism #8573

Closed stscijgbot-jp closed 3 months ago

stscijgbot-jp commented 5 months ago

Issue JP-3663 was created on JIRA by Howard Bushouse:

Operations is reporting a number of cases of NRS_MSASPEC (NIRSpec MOS) exposures using the Prism disperser that abort during the assign_wcs step of the Spec2Pipeline, due to no slit data being projected onto the NRS2 detector. For example, jw04465-o001_20240611t131534_spec2_00045_asn.json, which contains exposure jw04465001001_04108_00001_nrs2_rate.fits, aborts with the messages:


2024-06-13 11:06:35,279 - stpipe.Spec2Pipeline.assign_wcs - INFO - Retrieving open MSA slitlets for msa_metadata_id = 5 and dither_index = 12024-06-13 11:06:35,377 - stpipe.Spec2Pipeline.assign_wcs - INFO - gwa_ytilt is 0.03204867 deg2024-06-13 11:06:35,377 - stpipe.Spec2Pipeline.assign_wcs - INFO - gwa_xtilt is 0.3429093659999988 deg2024-06-13 11:06:35,377 - stpipe.Spec2Pipeline.assign_wcs - INFO - theta_y correction: -0.0042759214196487014 deg2024-06-13 11:06:35,378 - stpipe.Spec2Pipeline.assign_wcs - INFO - theta_x correction: 0.0001925133505087769 deg2024-06-13 11:06:35,711 - stpipe.Spec2Pipeline.assign_wcs - INFO - Removing slit 2 from the list of open slits because the WCS bounding_box is completely outside the detector.2024-06-13 11:06:35,711 - stpipe.Spec2Pipeline.assign_wcs - INFO - Slits projected on detector NRS2: []2024-06-13 11:06:35,711 - stpipe.Spec2Pipeline.assign_wcs - CRITICAL - No open slits fall on detector NRS2.2024-06-13 11:06:35,711 - stpipe.Spec2Pipeline - ERROR - Assign_wcs processing was skipped.2024-06-13 11:06:35,711 - stpipe.Spec2Pipeline - ERROR - Aborting remaining processing for this exposure.2024-06-13 11:06:35,711 - stpipe.Spec2Pipeline - ERROR - No output product will be created.```
I don't think there's a way to trap these ahead of time via association rules, like we do for FS and IFU modes, because there's no way to know what MSA configuration is in use and hence whether any slits project onto NRS2. That can't be known until assign_wcs does its processing of the MSA configuration data.

So Ops may just need to live with this situation, unless someone can clarify whether any MSA slits can ever project onto NRS2 when the prism is in use?
stscijgbot-jp commented 5 months ago

Comment by Melanie Clarke on JIRA:

MSA slits can definitely project onto NRS2 when prism is in use.  For a recent example, observed in May 2024, see jw01181198001_13101_00003_nrs2.

stscijgbot-jp commented 4 months ago

Comment by Jesse Doggett on JIRA:

Couldn't Cal exit with a status 64? This indicates to SDP that a Level 2b product couldn't be produced and that it should be removed from the Level 3 association. See for example, 1128:18:1 mentioned in Hien's 17/Jun/22 comment in JSDP-2303. The ticket is for a completely different issue, but Hien's example is a case where a Level 2b product couldn't be produced and is removed from the Level 3 association by SDP.

stscijgbot-jp commented 3 months ago

Comment by Hien Tran on JIRA:

the error seen in ops had to do with the failure to remove the absent nrs2 members from the l3 asn table file. the work in JSDP-2918 will hopefully improve that process so we won't see this issue again. so i don't think there's anything to do here on the cal side, and this ticket can be closed.  

stscijgbot-jp commented 3 months ago

Comment by Tyler Pauly on JIRA:

Closing ticket, as no work is required for this issue. Tracking SDP work related to the error in JSDP-2918.