| 2024-09-26 |
jwst_1293.pmap |
operational |
Affected data. MIRI, LRS SLITLESSPRISM modes, specwcs reference file. A new MIRI specwcs rmap is being delivered with updates to specwcs file 0009, because this file was previously delivered with an incorrect keyword. The subarray keyword was set to FULL, rather than SLITLESSPRISM, which means that the data was not using the correct wavelength file, resulting in incorrect results. File 0006 was meant to be replaced by 0009 at the previous delivery, so 0006 has also been deleted from the rmap. With the correct subarray selection criteria in place for file 0009, all SLITLESSPRISM data can be reprocessed with Build 11.0 software. |
| 2024-09-23 |
jwst_1290.pmap |
bad |
Affected data - NIRISS, SOSS modes, pastasoss reference file. NIRSpec, MOS, FS, and BOTS observing modes, fflat reference files.
The initial NIRISS SOSS mode pastasoss reference file was delivered, which will improve the optimal spectral extraction algorithm for SOSS data by accounting for the trace tilt as a function of the NIRISS pupil wheel position. The old algorithm unreliably performs a fit for the trace position but this new reference file uses calibrated on-sky data to accurately predict the trace location. The NIRSpec MOS, FS, and BOTS FFlat reference files have been updated to accompany improvements to the JWST pipeline spectral resampling for NIRSpec data in JWST pipeline versions 1.16.x and above. The pipeline changes require updated flux calibrations that are provided by these FFlat reference files. Any NIRSpec MOS, FS, and BOTS data processed with JWST pipeline versions 1.16.0 and above should use these new reference files. Using previous FFlat reference files with pipeline versions 1.16.0 and newer will produce flux calibrations that are systematically low by up to 5 percent. New system_calver file for jwst software version 1.16.0, which corresponds to DMS Build 11.1. |
| 2024-09-11 |
jwst_1281.pmap |
archived |
Affected data: MIRI MRS data taken after May 14, 2024, bad pixel reference files. All MIRI Imager and coronographs data, photom and apcorr reference files. NIRSpec Fixed Slits and BOTS observing modes, pathloss reference file.
New MIRI MRS bad pixel reference files were delivered for Spring 2024 in adherence with the typical six-month cadence of bad pixel reference file deliveries. A new set of MIRI Imager photom and apcorr files have been delivered which include entries for all imaging and coronographic bands. These files were updated based on analysis of the cycle 1 and cycle 2 absflux observations and associated commissioning observations, whereas the previous files were based only on cycle 1 and commissioning observations. NIRSpec Fixed Slits and BOTEs observing mode pathlosses were delivered based on data obtained in cycles 1 and 2. The previous NIRSpec pathloss reference file was based on a model. The NIRCam flat rmap was updated to use the existing imaging flat field reference files for grism data. Finally, jwst_niriss_trapdensity_0001.fits and jwst_niriss_persat_0001.fits were deleted because these are pedigree=DUMMY files that are not applied to any data, and lack DQ and DQ_DEF columns in their data extension as their successors have. On the CRDS webpage, select Context History, all contexts for more details on each delivery. |
| 2024-08-30 |
jwst_1276.pmap |
archived |
Delivering new MIRI pars-detector1pipeline, pars-outlierdetectionstep, pars-image2pipeline and pars-spec2pipeline rmaps to resolve matching ambiguity errors we are seeing in the pipeline. Currently these rmaps have entries with TSOVISIT=TRUE, that have equal weight cases with other entries with TSOVISIT=N/A. These cases are being resolved by setting any case of TSOVISIT=N/A to TSOVISIT=FALSE, so that all TSO data have only the option of using the TSO specific files.
Deleting two NIRSpec dark and superbias reference files for G395M because they were delivered with a substrt1 matching to other gratings and are now being used with those incorrect gratings. Once removed from the active rmaps, these files will ultimately be marked as bad and should not be used with any data. |