You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the dark current monitor (and possibly other monitors) query MAST for dark current exposures and perform analyses on these exposures. One subset of data that are included in these queries are ASIC tuning data. These files are labeled with an EXP_TYPE of e.g. NRC_DARK, so they are indistinguishable from normal dark current exposures. However, the readout details can change during ASIC tuning, which can result in a change to the measured dark current signal. Therefore, ASIC tuning data should be ignored in terms of instrument monitor analyses.
After some investigation, it turns out that there is a TEMPLATE keyword in the primary header of the science files. For ASIC tuning data, this keyword is set to be 'ISIM ASIC Tuning'. Knowing this, we can now adapt the instrument monitors to filter out the ASIC data by examining this keyword in the list of files returned by MAST queries. In the jwst datamodels, the TEMPLATE keyword corresponds to the model.meta.observation.template entry in the schema. I'm not sure how/if it is stored in the metadata returned by a MAST query.
The text was updated successfully, but these errors were encountered:
Currently the dark current monitor (and possibly other monitors) query MAST for dark current exposures and perform analyses on these exposures. One subset of data that are included in these queries are ASIC tuning data. These files are labeled with an EXP_TYPE of e.g. NRC_DARK, so they are indistinguishable from normal dark current exposures. However, the readout details can change during ASIC tuning, which can result in a change to the measured dark current signal. Therefore, ASIC tuning data should be ignored in terms of instrument monitor analyses.
After some investigation, it turns out that there is a TEMPLATE keyword in the primary header of the science files. For ASIC tuning data, this keyword is set to be 'ISIM ASIC Tuning'. Knowing this, we can now adapt the instrument monitors to filter out the ASIC data by examining this keyword in the list of files returned by MAST queries. In the jwst datamodels, the TEMPLATE keyword corresponds to the model.meta.observation.template entry in the schema. I'm not sure how/if it is stored in the metadata returned by a MAST query.
The text was updated successfully, but these errors were encountered: