Closed stscijgbot-jp closed 4 years ago
Comment by Mark Kyprianou on JIRA:
There is a S&OC Level ticket against DMS for this issue : JWSTSOCINTDR-5237
Comment by Howard Bushouse on JIRA:
Please add info to the ticket regarding DMS pipeline version in use, where the processing runs (including ASN pools, ASN tables, and science products) can be found. APT info for the observations in question is also useful (I can't find anything for PID 99508 within the APT "Retrieve from STScI" function).
Comment by Howard Bushouse on JIRA:
Still waiting for info on where the ASN pools and tables can be found for this program in the particular processing run.
Comment by Howard Bushouse on JIRA:
B7.5 results only show datasets for obs 001-010, nothing for 055 or 062. However, the APT file indicates that observations such as 003 and 008 appear to be identical to 055 and 062, all of which use the "FGS External Calibration" observation template, the "SENSING_ONLY" special requirement for Wavefront Sensing, and no dithers (primary dithers=1, subpixel positions=1).
Exposures for obs 003 and 008 show EXP_TYPE='FGS_IMAGE' and VISITYPE='PRIME_WFSC_SENSING_ONLY', with no PATTTYPE keyword, but NUMDTHPT=1 and PATT_NUM=1.
Meanwhile, all exposures for instruments other than FGS (i.e. NIRCam, NIRISS, MIRI) resulted in "wfs-image2" ASN's being created for level-2b processing, which correctly calls the calwebb_wfs-image2 pipeline configuration that skips the resample step and hence only rate (level-2a) and cal (level-2b) products are created. But the FGS observations 003 and 008 for some reason resulted in the creation of normal "image2" ASN's for level-2b processing, which calls the regular calwebb_image2 pipeline that includes the resample step and hence i2d products.
All of the "wfs-image2" ASN's contain a record of using the constraint "DMSAttrConstraint({'name': 'wfsc', 'sources': ['visitype'], 'value': 'prime_wfsc_sensing_only'})". The FGS "image2" ASN's do not contain this constraint. It could be the case that the level-2b ASN rules are too general for FGS imaging, in that any exposures with EXP_TYPE='FGS_IMAGE' or 'FGS_FOCUS' are categorized as "image2", with no provision for adding the wfsc constraint that checks the VISITYPE value.
Will need the pool file "jw99508_20200601t190711_pool" for testing, but it appears that pool files were not copied to the ███████████████████████████████████ directories. Richard Spencer do you know if pool files from the last B7.5 test runs on D-string side-2 were saved anywhere?
Comment by Howard Bushouse on JIRA:
Fixed in #5263
Issue JP-1485 was created on JIRA by Mark Kyprianou:
During the MIMF activity on 2020/5/19, 2 i2d files were produced and delivered to WSS, when none were expected. The FGS Imaging visits (99508:62:1 and 99508:55:1) both produced an i2d file each.