-
Notifications
You must be signed in to change notification settings - Fork 27
Issues: thorstenwagner/ij-ridgedetection
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
response vector of the first Line in 'contours' list potential issues
#40
opened Sep 25, 2019 by
lucalusn
potential bad assignment in the "split the lines at the junction points"
#39
opened Sep 23, 2019 by
lucalusn
The position of the point is not accurate enough, and the angle will appear unselected when it tends to PI.
#36
opened Jul 25, 2019 by
DLFCW
Correlation between contrast range and the number (and or the length) of detected ridges
#32
opened Jun 26, 2018 by
Asef67
arguments 'low' and 'high' never used in function Link.compute_contours
#26
opened Mar 12, 2017 by
renxida
Overlap resolution by search radius + shortest path + straightness
enhancement
#16
opened Dec 11, 2015 by
thorstenwagner
Some junction points are getting lost when correct position & estimate width is activated
bug
#8
opened Nov 6, 2015 by
thorstenwagner
ProTip!
Find all open issues with in progress development work with linked:pr.