Conversation
sbailey
reviewed
Feb 23, 2025
Member
Author
|
@sbailey I think this is ready to review. I reverted to the old default location for DR1 to be consistent with the tutorials. I also added the --no-tiles option. I also added support to download EDR data (default location is rosette 1 for dark targets). |
Member
Author
|
Using the default settings, tiny_edr, tiny_dr1 and tiny_dr2 weigh 102GB, 40GB and 91GB, respectively (using the --no-tiles option they only weigh 9.2GB, 23GB and 51GB) |
Contributor
|
Thanks for the update and for including the sizes. This highlights that the selected defaults are optimized for DR1, but are probably too big for both EDR and DR2 due to the increased tile density. I think that is good enough for now, but we'll need to revisit how we provide a minimal subset for DR2. A breakdown for tiny_dr1: |
This file contains hidden or 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
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.
I am adding a script that
By default, the script looks around the COSMOS location RA=150.12, Dec=2.21 within a radius of 0.5dec, but users can change these coordinates using command-line arguments.