-
Notifications
You must be signed in to change notification settings - Fork 14
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
Add a normalization option #113
Comments
Further info from Eli on Slack:
|
We could also consider a different normalization type that does the pure psf model version, which Eli thinks should work, but Lupton thinks won't. Then it could be relatively easy to compare and see which is better. The other possible algorithm looks something like:
|
More useful information about this here: |
LLOL |
Is the norm supposed to be constant per exposure, or should it be allowed to vary in some way? |
It should at least be per-ccd, not per-exposure. In the Rubin stack it can vary at sub-ccd scales, in sextractor/psfex it can't. |
sorry yes. I meant CCD |
I am not convinced that allowing to vary at sub-ccd scales is particularly useful overall, as it creates more degrees of freedom for things to go wrong. And it's also something that might be more important for HSC than DECam. |
Right now our PSF models are all normalized to have unit integral.
@erykoff has explained that this isn't the right thing if you expect to get accurate photometry at the end. Here is the procedure he laid out for doing the aperture correction:
My proposal is to do this at the very end of the fitting process of an exposure on all the stars used for fitting. This will set an overall normalization number for that exposure, which can be saved at the PSF level and applied when drawing the PSF using the final model.
This seems independent of any particular PSF type, so I think this can be a top-level field, which could look like this in the config:
@beckermr @esheldon @brianyanny
The text was updated successfully, but these errors were encountered: