spacetelescope / jwst

Python library for science observations from the James Webb Space Telescope

Home Page:https://jwst-pipeline.readthedocs.io/en/latest/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

NIRSpec MSA Metadata Duplicate Slitlet IDs

stscijgbot-jp opened this issue · comments

Issue JP-3582 was created on JIRA by Alaina Henry:

A recent helpdesk ticket (INC0198846) reported a bug in the creation of MSA metadata files.    

As shown in the ticket, the users opened shutters in the same MSA column, at the bottom of Q3 and top of Q4.  In the metafile, these are combined into a single slitlet, but this is not appropriate.  They should have separate slitlet IDs.

Comment by Tyler Pauly on JIRA:

I don't believe msa metadata files are created in CAL - Hien Tran are they built in SDP, or does SDP pull them from a database?

Comment by Howard Bushouse on JIRA:

Tyler Pauly You're correct that the *_msa.fits files are built by SDP during some part of level-1 processing. They pull info from several PPS DB tables in order to construct the contents of the msa.fits files. If there are shutters that are assigned to incorrect slitlet_id's, that could be a problem up at the front-end already, in whatever is being used to populated the PPS DB tables that SDP pulls from.

Comment by Hien Tran on JIRA:

yes, that's correct. my guess is the information comes from pps db tables populated by apt, but Linda Thompson would know all the details

Comment by Howard Bushouse on JIRA:

I do not believe that slitlet_id's are assigned, or shutters grouped into slitlet_id's, by the SDP code that builds the FITS version of the MSA metadata files from the data in the PPS DB tables. As far as I know the SDP process is a "read only" operation that just organizes the DB table info into the FITS tables and hence should not be creating or assigning any slitlet_id's. So this sounds like it could be a problem already in the data that appear in the PPS DB tables. Hence this is likely not a Cal pipeline issue or an SDP issue and should be reassigned to someone in APT to investigate (and perhaps file an APT ticket).