DM-38974: Move photometric repeatability metrics from faro to analysis_tools #136
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
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 implements metrics modelPhotRepStar1-4 and psfPhotRepStar1-4 in analysis_tools. All that was required was (1) modifying stellarPhotometricRepeatability.py to use a "RangeSelector" (i.e., select values between an upper and lower threshold) instead of "ThresholdSelector", and (2) implementing the metrics in the matchedVisitQualityCore.yaml pipeline.
Note that only the stellar repeatability metrics were added. Galaxy metrics will require a different implementation since
isolated_star_sourcesuses only stars.A successful Jenkins run is at: https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/39256/pipeline