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-5532 #24
DM-5532 #24
Conversation
Copying the config fields is unnecessary and complicates the constructor. Clean this up before rewriting to use StarSelector
Use the standard name for bad flag fields badFlags instead of badStarPixelFlags for the catalog star selector
Make CatalogStarSelector a subclass of StarSelectorTask, append Task to the name, and change CatalogStarSelectorTask.selectStars to return a catalog of stars instead of a list of PSF candidates.
Avoid lambdas by using RangeField in CatalogStarSelectorConfig
Standardize on "badFlags" as the variable name for bad flags in the catalog star selector, to match the standard config field name.
CatalogStarSelectorTask had two redundant debug variables: display and displayTas. I removed the latter and cleaned up the debug code slightly.
|
||
@section meas_astrom_catalogStarSelector_IO Invoking the Task | ||
|
||
Like all star selectors, the main method is `run`. |
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.
Should call out the fact that this is an unusual StarSelector
for which usesMatches=True
, and hence that argument is required.
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.
Good idea
Add full task documentation to CatalogStarSelectorTask
Can one of the admins verify this patch? |
No description provided.