adding release filter for queries using the mjd cutoffs #72
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
albireox
reviewed
Dec 9, 2024
|
Hmm, do you have an example sdss_id that has been observed in both? I can see how it looks in the astra db. |
|
On second thought and after discussing it, this all looks good. |
albireox
approved these changes
Dec 9, 2024
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.
This PR closes #49. It adds a filter to the
append_pipesmethod that filters down results based on the data release and the MJD cutoff for the given observatory.For releases less than DR17, we don't have a cutoff implemented yet, as these are different for different surveys. See #71. For all releases < DR17, it uses a MJD cutoff of 0 to effectively null the results, until we can properly support legacy data.