-
Notifications
You must be signed in to change notification settings - Fork 28
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
Adding a basic source catalog from Source Detection Step #1029
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1029 +/- ##
==========================================
- Coverage 70.94% 70.90% -0.04%
==========================================
Files 105 105
Lines 6979 6974 -5
==========================================
- Hits 4951 4945 -6
- Misses 2028 2029 +1
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Sentry. |
2f7278e
to
7adddb3
Compare
18559d8
to
2cbba5d
Compare
2cbba5d
to
f3ca274
Compare
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. Will it break the regression tests?
Regression tests started here |
Basic source catalogs got merged in a separate PR by Larry; closing. |
Resolves RCAL-719
Closes #1014
This PR does two things:
The data structure originally used for the tweakreg catalog was a 2D ndarray without labels or metadata. Recent PRs have switched to a structured array (Structured array source detection catalogs #987, Fix issue with source catalog in TweakReg. #1001) partly because I was under the impression that an astropy table wasn't supported. I found out that this was incorrect, so this PR saves the tweakreg catalog as an astropy table.
One of the related catalog requirements is to predict if a source is extended or not. There are lots of useful metrics produced but not preserved during Source Detection that help with this task. Sources are found with DAOStarFinder, which estimates source centroids and fluxes, as well as sharpness and roundness metrics. Users can optionally fit PSF models to the image via PSFPhotometry for more accurate astrometry and photometry, which also computes two quality of fit metrics (
qfit, cfit
). Those last quality metrics are best described in this ISR or in literature citations that discuss their use like Häberle 2021 or Griggio 2023.Checklist
CHANGES.rst
under the corresponding subsection