-
Notifications
You must be signed in to change notification settings - Fork 1
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
DM-46939: make reprocessVisitImage usable without calibrateImage #79
Conversation
0b23bd7
to
0156f94
Compare
Defaults are still set to use newer CalibrateImageTask outputs.
0156f94
to
a9eb27a
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.
Looks good—just a few typos.
# TODO (DM-46971): | ||
# Now that we're running them before we apply the PhotoCalib to the | ||
# image pixels, there's no need for post_calibrations to exist as | ||
# as separate measurement instance from the main one (which is invoked |
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.
to exist as as separate measurement instance
→ to exist as a separate measurement instance
# Now that we're running them before we apply the PhotoCalib to the | ||
# image pixels, there's no need for post_calibrations to exist as | ||
# as separate measurement instance from the main one (which is invoked | ||
# (in _find_sources), but it's better to save removal (which may need |
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.
(which is invoked (in _find_sources)
→ (which is invoked in _find_sources)
This puts the output background and summary stats measurements in ADU, making them more consistent with other backgrounds and summary stats produced earlier in the pipeline, but inconsistent with the units of the "pvi" output image. It also makes the LocalWcs and LocalPhotoCalib plugin outputs reflect the transformation from ADU to nJy; I'm pretty sure they were previously just identities, which seems like it was probably a bug, unless downstream transform tasks had been configured to read "flux" fields rather than "instFlux" fields.
a9eb27a
to
f69187c
Compare
No description provided.