JWST Conventions¶
Naming Conventions¶
When produced through the ground processing, all association files are named according to the following scheme:
jwPPPPP-TNNNN_YYYYMMDDtHHMMSS_ATYPE_MMM_asn.json
where:
jw: All JWST-related products begin withjwPPPPP: 5 digit proposal numberTNNNN: Canididate Identifier. Can be one of the following:
oNNN: Observation candidate specified by the letterofollowed by a 3 digit number.c1NNN: Association candidate, specified by the letter ‘c’, followed by a number starting at 1001.a3NNN: Discovered whole program associations, specified by the letter ‘a’, followed by a number starting at 3001rNNNN: Reserverd for future use. If you see this in practice, file an issue to have this document updated.YYYYMMDDtHHMMSS: This is generically referred to as theversion_id. DMS specifies this as a timestamp. Note: When used outside the workflow, this field is user-specifiable.ATYPE: The type of association. See Association TypesMMM: A counter for each type of association created.
Association Types¶
Each association is intended to make a specific science
product. The type of science product is indicated by the ATYPE field
in the association file name (see asn-DMS-naming), and in the asn_type meta
keyword of the association itself (see Association Meta Keywords).
The pipeline uses this type as the key to indicate which Level 2 or Level 3 pipeline module to use to process this association.
The current association types are:
image3: Intended forcalwebb_image3processingspec3: Intended forcalwebb_spec3processingwfs: Wave front sensing data, used bywfs_combineami3: Intended forcalwebb_ami3processingcoron3: Intended forcalwebb_coron3processingtso3: Intended forcalwebb_tso3processingimage2: Intended forcalwebb_image2processingspec2: Intended forcalwebb_spec2processingnrslamp-spec2: Intended forcalwebb_nrslamp_spec2processingtso-image2: Intended forcalwebb_tso_image2processingtso-spec2: Intended forcalwebb_tso_spec2processing