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

binary_opening/binary_closing missing arguments #7453

jakirkham opened this issue Jun 2, 2017 · 1 comment


Copy link

commented Jun 2, 2017

As a comparison, binary_dilation provides mask, border_value, and brute_force. While the purpose of brute_force is unclear ( #4586 ), the other two have clear meanings and value for these operations.


This comment has been minimized.

Copy link

commented Mar 11, 2018

I'd like to take this up and work on it. Looking at the code and the docs, it seems simple enough. The basic erosion and dilation operations are being called with default values for mask, border_value, and brute_force. Arguments can be added to the function definition with these default values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.