Add formalism to make ledgers for BACKUP targets #681
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds initial priorities and
NUMOBS
to target files forBACKUP
conditions to make them work as ledgers. Prior to this PR,BACKUP
(orsupp
) targets were treated separately (as "filler"). After this PR,BACKUP
targets are treated more like their own separate observing program intended for"BACKUP"
conditions.To reflect the fact that
BACKUP
targets are now more likeBRIGHT
andDARK
targets, the directory structure has been reorganized to replace occurrences ofsupp
withbackup
for such targets.In addition, this PR allows ledgers to be written over a subset of pixels rather than for the entire survey. This facilitates easier testing, and will also allow programs to be quickly written in smaller regions of the sky.
These are additional steps towards being ready for the ".1% Survey". Still to-do:
BACKUP
targets actually work seamlessly with the automated MTL procedures.zcat
on disk, and conduct the whole MTL loop, updating the ledgers.