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-18643: Move AstrometryTask source selection from "matcher" into AstrometryTask #122

Merged
merged 3 commits into from Apr 12, 2019

Conversation

erykoff
Copy link
Contributor

@erykoff erykoff commented Apr 10, 2019

Implementing RFC-589, this moves the source selector into the astrometry task, and additionally fixes the reference selector so it is run in both matching and solving modes.

self.sourceSelector.name = "matcher"
self.sourceSelector["matcher"].sourceFluxType = self.sourceFluxType

# Note that if the matcher is MatchOptimisticBTask, then the
Copy link
Contributor

Choose a reason for hiding this comment

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

Quick clarification: The excludePixelFlags value doesn't need to be set True for the matcher to work, this was just the previous behavior. In fact, you can get more stable behavior for the matcher in fields with many bright stars by setting this too True as most of the stars in those fields that are attempted to match with all have saturated centers.

@morriscb
Copy link
Contributor

Looks good. I would suggest squashing the "Fix typo" commits.

Note that the default source and reference selectors (defined in
RefMatchConfig) do not down-select, so fixing this bug will not change the
default runs.
Move the sourceSelector from the match tasks into the astrometry and ref_match
tasks, as per RFC-589.  This will ensure that source selection is only
performed once, and with a single, consistent selector.  Furthermore, the
reference selector is properly called in the astrometry task, rather than being
skipped.
@erykoff erykoff merged commit a01e3e3 into master Apr 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants