Date: Fri, 29 Mar 2024 10:58:07 -0400 (EDT) Message-ID: <359675021.2638.1711724287958@ploutercf.stsci.edu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2637_1464236455.1711724287955" ------=_Part_2637_1464236455.1711724287955 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
After observations are executed on the telescope, JWST science data are = processed to produce fully calibrated data products. See the JWST Science Calibration Pipeline Overvi= ew for details. The data calibration is being continuously improved ove= r time as better, in-flight characterizations of instrument performance are= derived. JWST science data are periodically reprocessed to leverage new im= provements and provide the best quality products to the community. Reproces= sing may happen after:
The schedule for reprocessing data, and rel= ated details, are discussed in the article Reprocessing JWST Data.
It is useful to identify the pedigree of your data to help you figure ou= t if you have the best available products. There are a few keyword records = in the headers of science FITS files that record this information:
Keyword | Description<= /th> |
---|---|
CAL_VER |
The JWST Science Calibration Pipeline version used to process data=
(with a value like "1.4.6 "). |
CRDS_CTX |
The context=
of calibration reference data that was used to process data (with a value =
like "jwst_1061.pmap "). The context is basically a self-consis=
tent mapping of best reference files to be used for processing to a specifi=
c version of the calibration pipeline. |
DATE |
The date/time that a product was created. |
The operational=
version of the pipeline is typically updated every few months, but the pip=
eline is also released independently to the user community for custom proce=
ssing. See JWST Operational Pipeline Build Information for details. Reference file updates may happen as often as a few times pe=
r month.
You can view pe=
digree of the data products in MAST by performing a search of the JWST Instrument Keywords co=
llection for the appropriate instrument, and selecting the Program ID for y=
our data. After the search, look for the above-named pedigree keywords in t=
he results table. If the values of the pedigree keywords are higher than th=
ose of the data on your machine, or the creation date is later than that of=
your data, the products in the Archive are newer
There are dozens of fields displayed in the results table. To find your =
fields of interest more quickly, click the "Edit Columns" button, click the=
"Select None" button, and then check the boxes next to the pedigree keywor=
d names, as well as that for the filename
column.
You may elect to receive notifications from MAST when data from particul= ar JWST Programs or Observations are reprocessed. See Program Subscriptions and = Notifications in the Portal = Guide to learn how to subscribe.
Some JWST programs, or even observations within programs, can take many =
hours (or even days) to process. If you subscribe to JWST data it is
You will see a warning dialog in the MAST P= ortal if you attempt to download Observations that are queued to be reproce= ssed. You have the option to proceed with the download, cancel, or subscrib= e to receive a notification when the data have been updated in MAST.
The wait time specified in the dialog for calibration to complete is not= currently meaningful. It may take many hours or even a few days for update= d data to be available in MAST.
You may elect to be notified when new refer= ence files are delivered to CRDS by subscribing to a list server. There are= separate distribution lists for each instrument. See the sub-section "Refe= rence Files and my data" in the article JWST Data Calibration R= eference Files. The notification email will include a list of updated r= eference file names and a summary of why the reference files were updated. = It may be take some time between the delivery of a new reference file and i= ts application the operational pipeline.