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

Treatment of threshold values in segmentation and feature detection #367

Open
JuliaKukulies opened this issue Nov 21, 2023 · 0 comments
Open
Milestone

Comments

@JuliaKukulies
Copy link
Member

Following our discussions in #346 and #365 we should allow users to specify if the threshold values in feature detection and segmentation are treated in an inclusive or exclusive way. We should also pick which of the currently implemented versions becomes the new default and make this default consistent between feature detection and segmentation and offer either off-ramps or an option like edge_treatment = {'inclusive', 'exclusive', 'default'}

@JuliaKukulies JuliaKukulies added this to the Version 1.5.x milestone Nov 21, 2023
@fsenf fsenf modified the milestones: Version 1.6, Beyond v1.6 May 17, 2024
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

No branches or pull requests

2 participants