desihub / desihub/desispec

Loss of calibration provenance in processed science data

Open
#2,012 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
42
Forks
26
Avg merge
1d 20h
Merged PRs (30d)
11

Description

When we process a science exposure, we use four types of calibration files that are typically derived from calibration data taken on the night of observations: `badcolumns`, `biasnight`, `psfnight`, and `fiberflatnight`. The nightly calibrations are stored in `$DESI_SPECTRO_REDUX/$SPECPROD/calibnight/`. If the files for a given camera on a given night are not present, then we use default versions of these data in an SVN directory.

Since the choice of calibration file is dynamically selected at runtime based on whether the data exists from a given night or not, we should be saving which file was used in the header of the processed files.

We do trace the origins of the psf that we use:
In the `'FLUX'` HDU of `frame`, `cframe`, etc. it is saved as the header keyword `ORIG_PSF`.
In the `'PSF'` HDU of the `psf` files it is saved under the header keyword `IN_PSF`.

The other file types are not propagated to any of the science exposure headers. We should add these.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.