Skip to content

robustness to DARKs that span noon NIGHT rollover #1512

@sbailey

Description

@sbailey

DARK exposure 20211205/00112406/desi-00112406.fits.fz is under NIGHT 20211205 but has header NIGHT=20211204. Unluckily, it was also a 300s dark, which appears to have taken the spot as the first 300 sec DARK of the night even though the header keyword mismatch prevented it from getting used (initially no dark*.slurm job was created; I submitted the "correct" dark 112463 by hand).

Various remediations to be more robust:

  • only use DARK if PROGRAM starts with "CALIB Dark" (from the zeros+dark sequence) instead of "DARK" from the 90min dark sequences.
  • if an exposure is rejected, don't let it take the spot for the nightly badcolumn dark

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions