Information about what's new in the latest JWST pipeline build, and what was done in previous builds, is provided in this article. It also gives a preview of some updates likely to be coming soon in upcoming builds. The information contained here is generally a high-level summary of changes, with links provided to more extensive external documentation. 

Build lifecycle

JWST pipeline development proceeds according to a quarterly build schedule. Each quarter, the active development version of the JWST Science Calibration Pipeline is frozen, combined with other dependent software (e.g., the JWST Science Data Processing system; SDP) and a particular CRDS reference file context, and tagged to produce a candidate build. This candidate build is then tested extensively prior to becoming an operations build installed by the Data Management System (DMS) at STScI and used to reprocess all previous JWST data as well as newly obtained observations. Once a build is no longer operational, it becomes archived.

There are thus four kinds of builds:

• Development (Dev) build:  Changing daily, uses the Latest CRDS context, not recommended for non-developers.
• Candidate build: Development has finished, currently working on testing and documentation. Uses a fixed CRDS context. Available for experienced users.
• Operations build: Installed at STScI and being used to produce data products available in MAST. Uses a fixed CRDS context. Default recommendation for users.
• Archived build: Outdated operations build that is no longer recommended for general use (may still correspond to some MAST data products until reprocessing is completed).
  

Record of JWST Operations Pipeline builds

Table 1 provides a historical record of JWST operations builds, along with links to the build release notes and tagged software versions. The "CRDS Context" column indicates the fixed context used by default by each pipeline version. Note that many intermediate development tags of the JWST Science Calibration Pipeline (indicated by minor version releases of the jwst package) are never installed in STScI DMS operations, but can be installed by end users. For full information on all jwst releases, see the github software version table.

Table 1. Release notes and associated versions for JWST Operations Pipeline releases

What's new in the latest build?

The latest released JWST Calibration Pipeline is build 13.0. Some highlights are provided here about major relevant changes; please refer to the build 13.0 release notes for additional details.

Please also refer to the calibration notes broken down by instrument mode in the JWST calibration status articles, and the known issues with JWST data articles for instrument-specific information.

Major pipeline updates in build 13.0

• Added support for superstripe mode for NIRCam imaging.
• Added support for new MIRI subarrays (SLITLESSPRISM_IP, SLITLESSPRISM_IPS, SUB64_IP, SUB128_IP) and FASTGRPAVG readout mode.
• Implemented a new step for optional flagging of pixels affected by persistence.
• Updated the NIRSpec IFU distortion solution to fix issues related to spectral "wander" of PSF centroids.
• Extended the optional Adaptive Trace Model technique to MSA and slit spectra, incorporated multiprocessing to improve runtime.
• Improved reference pixel correction for some NIRCam subarray modes.
• Changed the default behavior of the imaging source_catalog step to apply deblending instead of merging all contiguous pixels.

Major reference file updates in build 13.0

Build 13.0 is tied to the CRDS reference file context jwst_1584.pmap. A full list of CRDS context updates can be found at https://jwst-crds.stsci.edu/display_all_contexts/. Significant reference file deliveries (not including routine updates, e.g., to bad pixel masks) included in this context include:

• New "chromcorr" reference file for NIRSpec IFU to characterize chromaticity in the instrument fore-optics (jwst_1565.pmap).
• New MIRI reference files for FASTGRPAVG readout mode, WFSS observing mode, and new subarrays (various).
• Updated NIRCam "wavelengthrange" reference file to more accurately describe the dispersed wavelength range for each filter (jwst_1555.pmap).
• Enabled the clean_flicker_noise step by default for NIRSpec BOTS and fixed slit (jwst_1554.pmap, jwst_1575.pmap).
• Reference files to support NIRISS SOSS multistripe observations (jwst_1583.pmap).
• Use autocentroid for extracting point sources from NIRSpec IFU data (jwst_1570.pmap).

Coming soon

The next JWST pipeline build is build 13.2 (release candidate expected December 2026).  The following list indicates some of the areas in which users can expect to see changes and updates in the coming months.

Pipeline development

Ongoing JWST Science Calibration Pipeline development work in build 13.2 includes:

• Additional superstripe/multistripe development
• Initial development of NIRSpec MSA slitlet-stepping
• MRS fixed pattern correction
• Improvements to WFSS contamination modeling and spectral extraction
• Brighter-fatter effect (BFE)

Reference files

Major reference file updates currently planned for build 13.2 include:

• Further updates to the MIRI WFSS calibration.

Reference files

In the early phases of the JWST mission, reference file contexts updated frequently and data within MAST processed with a given build could thus have used different reference files.

As of build 11.1 (December 2024), JWST now uses a fixed CRDS reference file context for each pipeline build (see the CRDS overview and CRDS Migration to Quarterly Calibration Updates).

Ephemeris information

Note that ephemeris information (the 3-dimentional position and velocity as a function of time) for JWST can evolve between the initial processing of a dataset available through MAST and subsequent reprocessing of that data. The Flight Dynamics Facility (FDF) group at Goddard evaluates the ephemeris for JWST's orbit and releases a weekly update that includes the actual ephemeris up to a specific date, and a predicted ephemeris that is used for planning and executing upcoming observations. Both are stored in a database within minutes of the files being delivered by FDF, and the database is accessed by level 1 data processing in the operations pipeline. Subsequent weekly deliveries by FDF will update the predicted ephemeris database values.

To populate the ephemeris headers in the JWST data products, the JWST Data Management System (DMS) uses the definitive ephemeris values, or if they are not yet available, they use the predicted ephemeris values. Most data are initially processed with the predicted ephemeris values, while later reprocessing will use the definitive values. The header keyword EPH_TYPE lists if Definitive or Predicted was used. The ephemeris files (both definitive and predicted) are also ingested into MAST. The ephemeris is used for aberration correction in the WCS parameters in the science headers, so all science types are affected.

References

Bushouse, H., et al. 2023, Zenodo 
JWST Calibration Pipeline