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-9953: Pixels rejected from coaddition and CCD are not masked on coadds #164

Merged
merged 6 commits into from Nov 21, 2017

Conversation

PaulPrice
Copy link
Contributor

No description provided.

The presence of background matching confuses the code, and it doesn't
belong here because it doesn't work on pointed observations. Its removal
was approved in RFC-137.
The EDGE pixels from the individual CCDs have printed through into the
coadd, but EDGE means "we couldn't search for sources in this area
because we couldn't convolve by the PSF near the edge of the image",
so this mask plane needs to be converted to something else if we want
to keep them. We do want to be able to identify pixels near the edge
of the detector because they will have an inexact CoaddPsf. We
rename EDGE pixels as SENSOR_EDGE.
Masking of clipped pixels is now done in afw.math.statisticsStack, so the
workaround can be removed.
If any of the input images isn't represented in the coadd
(due to clipped pixels or chip gaps), the `CoaddPsf` will be
inexact. Flag these pixels.

Using a mask plane for this allows us to keep SENSOR_EDGE
and CLIPPED separate (in case the distinction is important)
while providing a convenient shorthand with a clear name that
covers both.
We want to know when sources are on pixels that satisfy any
of these.
We measure the variance for forcedPhotCoadd, so might help to have it here
too.
@PaulPrice PaulPrice merged commit 67b1ea0 into master Nov 21, 2017
@ktlim ktlim deleted the tickets/DM-9953 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

2 participants