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

Review for DM-4831: Add bright object masks to pipeline outputs #39

Merged
merged 5 commits into from Mar 15, 2016

Conversation

jdswinbank
Copy link
Contributor

No description provided.


def setDefaults(self):
CoaddBaseTask.ConfigClass.setDefaults(self)
self.badMaskPlanes = ["NO_DATA", "BAD", "CR",]


Copy link
Contributor Author

Choose a reason for hiding this comment

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

The whitespace churn is gratuitous (& I'm not even sure it's an improvement).

@natelust natelust force-pushed the tickets/DM-4831 branch 2 times, most recently from a107a86 to eb186c5 Compare March 15, 2016 22:04
natelust and others added 5 commits March 15, 2016 18:17
pipe_tasks (HSC-1342) uses the butler to read these files, of type "brightObjectMask" to set a bit mask and
flags for bright objects.
assembleCoadd.py reads an externally provided specification of
bright object masks (via the butler type "brightObjectMask" which is added in obs_subaru on this ticket) and sets a mask
plane in the exposure, by default BRIGHT_OBJECT.  This is intended to allow us to mask bright stars and other troublesome objects for LSS and other studies.

obs/subaru/config/assembleCoadd.py sets flag bits in sources that fall within this mask.
The 'run' method should be simple so that it may be simply
replicated by subclasses.  Moved the relatively lengthy read
of the bright object masks into its own method. Might have
moved it into the 'setBrightObjectMasks' method, but we want
algorithmic code to be independent of I/O.
@natelust natelust merged commit df27754 into master Mar 15, 2016
@ktlim ktlim deleted the tickets/DM-4831 branch August 25, 2018 06:46
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

4 participants