No spec2 associations created for NIRSPEC IFU data about jwst HOT 6 CLOSED

Comment by Howard Bushouse on JIRA:

Robert Jedrzejewski Does this actually affect jwst 1.14.0, which was the version released for DMS B10.2 and will be installed in Ops in June? Or does it only affect the on-going B11.0 development version?

from jwst.

It only affects the ongoing development, not 1.14.0. The commits were make a few days after the 1.14.0 tag.

from jwst.

Comment by Robert Jedrzejewski on JIRA:

I changed the affects version label to "master"

from jwst.

Comment by Melanie Clarke on JIRA:

This issue appears to be specific to the test conditions for JP-3151.  

Spec2 association files are still generated for NIRSpec IFU data from pool files generated by DMS.  When a pool file is made locally from FITS files on disk, they are missing.

This appears to be because the asn_make_pool script needs special handling for any non-header keywords used in generating associations.  JP-3518 introduced requirements for MOSTILNO and DITHPTIN, so the asn_make_pool script needs to be updated to use default values for those keywords in the output pool file.  I'll make this change, but I think this issue shouldn't impact operations.

However, I have a related question, maybe for Howard Bushouse -

It looks like JP-3518 changed the MOSTILNO constraint for the Asn_Lv2Spec rules, but there is a similar constraint in Asn_Lv2NRSIFUNod that was not modified.  Does this need updating?

from jwst.

Comment by Melanie Clarke on JIRA:

Since JP-3518 is still marked ready for testing, I'll follow up on the question about the MOSTILNO constraint on that ticket.  The fix for this ticket is unrelated.

from jwst.

Comment by Howard Bushouse on JIRA:

Fixed by #8508

from jwst.