script to identify images and calibration files needed to process a brick #96
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Related: There is a program create_testcase.py that cuts out postage stamps of the images and invvars and DQs, and grabs the calibs and builds a tiny LEGACY_SURVEY_DIR directory to re-run the data touched by a previous run. Use it by running "runbrick.py -s image_coadds" and feeding the resulting per-brick CCDs table to create_testcase.py |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a convenience function to just write out the set of images and calibration files one needs to run Tractor on a single brick. Useful for transferring data to a laptop or non-NERSC server.