-
Notifications
You must be signed in to change notification settings - Fork 179
JP-3889: Explain how source position is computed in source catalog step docs #9656
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #9656 +/- ##
=======================================
Coverage ? 80.37%
=======================================
Files ? 367
Lines ? 37265
Branches ? 0
=======================================
Hits ? 29951
Misses ? 7314
Partials ? 0 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, other than a very small typo.
I think the clarification here is helpful, and we can go ahead and get it in. Up to INS if it also closes the ticket, or if more work is needed.
Co-authored-by: Melanie Clarke <[email protected]>
Resolves JP-3889
Closes #9200
This PR clarifies the intent of the source position centroids reported in the source catalog output by the
SourceCatalogStep, including a disclaimer that uncertainty estimation is not attempted.Tasks
Build 12.0(use the latest build if not sure)no-changelog-entry-needed)changes/:echo "changed something" > changes/<PR#>.<changetype>.rst(see changelog readme for instructions)docs/pageokify_regteststo update the truth files