Skip to content
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-39227: drop overrides for deprected config options #456

Merged
merged 4 commits into from Jul 13, 2023

Conversation

TallJimbo
Copy link
Member

No description provided.

@@ -6,6 +6,3 @@
config.measurement.plugins["base_CircularApertureFlux"].radii = [12.0]

config.measurement.slots.gaussianFlux = None
config.doApplyExternalPhotoCalib = True
config.doApplyExternalSkyWcs = True
config.doApplySkyCorr = True
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are skyCorr datasets also being bundled into finalVisitSummary tables? From looking through the forcedPhotCcd script in the meas_base PR, I don't think so?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, good catch. Backgrounds are not in visit summaries, and I think removing this last line was a mistake.

Comment on lines -3 to -4
config.doApplyExternalPhotoCalib = True
config.doApplyExternalSkyWcs = True
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

By removing these doApply... configs (here and elsewhere), are we also removing the flexibility to turn these components off? I see a new useVisitSummaryPsf config option - do we also need similar useVisitSummaryPhotoCalib and useVisitSummaryWcs configs to replicate this functionality?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, we are intentionally dropping this functionality here, because the expectation is that controlling what goes into a visit summary dataset (which still has these knobs) is sufficient for everything downstream of that visit summary and upstream of any other visit summary.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, thanks for the explanation, good to know!

@leeskelvin
Copy link
Contributor

Other than a doApplySkyCorr config being removed that shouldn't be, this LGTM 👍

The correct external-calibs behavior no longer requires different
per-instrument configs.
The correct external-calibs behavior no longer requires different
per-instrument configs.
These overrides are for subtask usage of AssembleCoaddTask, which
gets these config options from CoaddBaseTask but doesn't use them
(they should have only been options for MakeWarpTask, but they're
being deprecated anyway).
@TallJimbo TallJimbo merged commit 1eb1041 into main Jul 13, 2023
2 checks passed
@TallJimbo TallJimbo deleted the tickets/DM-39227 branch July 13, 2023 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants