-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
API: disk vs circle vs circle_perimeter #4406
Comments
@sciunto I'm 👍 on this proposal! Great catch(es)! |
How will you handle the deprecation cycle for the new circle? Will you do it in a single shot or two? |
Great catches indeed @sciunto, one more step for our consistency! |
@hmaarrfk Good question. The number/type of arguments for the new disk and the new circle functions are the same. Therefore, it's hard to detect users who have an outdated code, embarrassing for a single shot. I would suggest:
I think this will give the best user experience. |
See PR #4462 por favor! Which addresses a few warnings introduced by the first few PRs. |
What is the plan for implementing perimeter drawing now? |
I think it is:
|
I guess this comment was written specifically for me :) |
And, there will be a keyword parameter on |
Description
In morphology disk means a full circle
In Hough transform circle means the edge of a circle
In draw.circle means a full circle
In draw.circle_perimeter and draw.circle_perimeter_aa circle perimeter means the edge of a circle.
In measure circleModel, circle means edge of a circle
In measure circle_level_set circle is a full circle.
I admit this can be disturbing.
I recommend to rename
In my mind, disk = circle filled up with pixels, circle = mathematical line.
What do you think @scikit-image/core
The text was updated successfully, but these errors were encountered: