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-44150: Remove unnecessary DetectAndMeasure plugins #318

Merged
merged 5 commits into from
May 29, 2024

Conversation

parejkoj
Copy link
Contributor

No description provided.

Copy link
Contributor

@isullivan isullivan left a comment

Choose a reason for hiding this comment

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

Looks fine, though I am slightly confused by the move of HSM defaults to dipoleFitTask.

Comment on lines 207 to 211
"ext_shapeHSM_HsmSourceMoments",
"ext_shapeHSM_HsmPsfMoments",
]
self.measurement.slots.psfShape = "ext_shapeHSM_HsmPsfMoments"
self.measurement.slots.shape = "ext_shapeHSM_HsmSourceMoments"
Copy link
Contributor

Choose a reason for hiding this comment

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

I am slightly confused by these being moved to dipoleFitTask. Both seem fine, though setting here seems more general.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's a good question. dipoleFitTask is our MeasurementTask for diffim; it's what runs all of our measurement plugins. So I think it's the lowest level place to put the list of what measurements we consider to be canonical. I guess nothing in dipoleFitTask depends on the output of a shape algorithm, so we could just not define anything for the shape slot in that task and do it here (maybe with a note in dipoleFit to that effect?)? I could go either way.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've thought about this more and I think you're right and I'll take it a step further: I'm going to move the plugins currently set in dipoleFitTask that are unnecessary for just that task out of it and into detectAndMeasure. That makes dipoleFit more self-contained, and puts the rest of the diffim measurements together in one place.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Having poked at this some, it's not worth the added complexity of moving plugins out of dipoleFitTask, because of the various slots that have to be unset and then reset in detectAndMeasure.

We don't have a use for this flux measurement on diffim sources, which
are either dipoles, psfs, or trails, none of which are elliptical
Gaussians.
shapeHsm handles negative sources better than SdssShape, otherwise
they're similar enough that there's no benefit here to running both.
This was carried over from much older code; we're now measuring on the
difference exposure instead of the score exposure, so we don't need it.
This reverts commit 2fd0aeb2e2bd2ca630956e4bbcb27829650e56d0.
DipoleFitTask doesn't use shape measurements, and SdssShape doesn't
handle negative sources well; detectAndMeasure uses shapeHsm, which is
better.
@parejkoj parejkoj merged commit 3a940c3 into main May 29, 2024
2 checks passed
@parejkoj parejkoj deleted the tickets/DM-44150 branch May 29, 2024 23:20
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.

2 participants