-
Notifications
You must be signed in to change notification settings - Fork 63
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
Masked pixels appear in segmentation map #149
Comments
This is actually quite an interesting issue - thanks for pointing this out! This is the intended behaviour (there is no equivalent in SExtractor to my knowledge), and stems from the order in which operations are applied. The mask is applied before the default filtering, which becomes clearer when turning this off ( Default filter
`filter_kernel=None`
Or to show the difference graphically, this is how the input data changes when a mask is given: The quantities are measured from these masked (and convolved) images, so it's not correct that the extracted pixels can be retrieved from |
The docs says
A test case to demonstrate this:
The
obj
is correctly calculated after masking the pixels. (∵obj["x"] != 3.0
)However,
seg
includes masked pixels, too.I think this might be intentional, because the pixels used for extract can be retrived by
seg & ~mask
, while the additional segmentation information is given to the user. (I am not sure what is SExtractor's default, as I have never used it)However, if that's the case, I think the documentation needs a bit more information.
The text was updated successfully, but these errors were encountered: