JWST associations products are the result of combining science exposures using a set of predefined rules that depend on the type of data and observation.

Association overview

See also: Understanding JWST Data Files
Software documentation outside JDox: JWST Associations

Relationships between multiple exposures are captured in an association, which is a means of identifying a set of exposures that belong together and may be dependent upon one another. The association concept permits exposures to be calibrated, archived, retrieved, and reprocessed as a set rather than as individual objects.

In order to capture a list of exposures that could potentially form an association product and provide relevant information about those exposures, the JWST Science Calibration Pipeline first generates an association pool. These are Astropy tables that contain the metadata for all the data in a given proposal. These pools are then used by the association generator, that runs within software, to generate stage 2 associations or stage 3 associations in JSON format. Based on the association pool content, the JWST Science Calibration Pipeline software creates the associated data products.

The basic association products that the pipeline generates are combinations of mosaics or dithers for a single observation. Higher level products are built by associating data outside the routine science calibration pipeline; these might include multiple observations from a single target in a program or large mosaics similar to HLA for HST data. An association file can contain several science data products, related files that support the science data (e.g., jitter data or target acquisition images), and contemporaneous calibration files used to calibrate the science data.

Association pool

See also: Understanding JWST Data Files, Association Generator, Types of Associations

There is a separate association file for each program and each target within a program. The list of data that goes into constructing an association file, within a specific program, is contained in what is called an association pool. This will include:

• All observations from the same target in a given program
• Observations of a given target from multiple science instruments within the same program
• Different filters for the same target within the same program
• Exposures from linked observations within the same program
• Calibration exposures, which can be members of more than one association pool

Association generator

See also: Understanding JWST Data Files, Association Pool, Types of Associations

In the JWST science calibration pipeline, the association generator classifies the data into one or more association files based on a set of rules. When all of the exposures for an observation or set of observations have been collected, the association generator will determine which exposures are needed for the stage 2 and stage 3 data products, and will output an association file with the list of all these files. Multiple association files can be generated from a single association pool. Observers should not need to run the generator; instead, it is expected they will edit the existing association files that accompanies the JWST data.

Association file

An association file is a JSON formatted file that includes the list of all related data that might be combined into a single image, as shown in this example stage 3 association.

Types of associations

See also: Understanding JWST Data Files, Association Pool, Association Generator

Table 1 shows a list of data types that might be included in an association file. Some of these files, if they exist for that type of observation, might be or not be used to create the association products. Any background or PSF observation can be part to more than one association product.

Table 1. List of data types that can be included in an association file

Currently we have three types of associations being produced, these are "candidates", "observation", and "discovered" associations. These rules used to select the data along with the naming convention for each of these cases are provided in Table 2. Note than different type of associations might include the same datasets but associated following different rules.

Table 2.  Association Types and type of data included