Comments (7)
thanks for playing with this @thorstenwagner!
So, for the bottom image (lines 133, 132) I think it is fairly arbitrary - from a slope/straightness perspective - which "top" end to pair with that "bottom" end pointing to the left.
My current implementation does a greedy search for maximizing straightness. We could improve the results by trying to find a globally optimal configuration for all pairings about an overlap point, which would improve the algorithm in some cases.
However, the primary assumption of a slope/straightness heuristic (that intersection is more likely than overlapping, simultaneous curves) falls apart the larger the length of overlap - especially when the length of overlap is large relative to the overall line length.
So I would say the 132, 133 line set is not an ideal candidate for the slope heuristic and would be better served by SVM, manual inspection, etc..
(and I will try to make this clear in my wiki contribution)
from ij-ridgedetection.
Same explanation for the above two images. The initial segmentation is a poor starting point for a slope/straightness-based heuristic.
I played with the parameters a bit:
which looks opposite of what you might expect at first, but I think it's working exact as advertised. The algorithm likely paired the top two sections together because they were processed first (greedy) and they best preserve overall straightness. Then the bottom two sections are simply left over and paired together.
My goal for the wiki is to contrast these examples with images like this one:
to show when slope overlap detection is, and is not, useful.
from ij-ridgedetection.
There are, of course, probably still bugs! So let me know if you find more odd behavior 😄
Thanks again!
from ij-ridgedetection.
Here is something that should never happen. The wrong ends were merged together.
from ij-ridgedetection.
@hinerm Yes, but it seems only happen sometimes... If check / uncheck preview multiple times it only occurs sometimes...
from ij-ridgedetection.
I will investigate!
from ij-ridgedetection.
So the problem is - unsurprisingly - that I took some short cuts in simplifying the assumptions I was making about intersection structure.
I started a branch to work on making the search more robust - by considering all combinations of "enclosed" segments as possible pairings, which then will necessitate global error minimization as well - but I don't really have the time to finish it right now.
It's fun to work on so I hope to get back to it eventually. Anyone else is welcome to continue its refinement as well. And @thorstenwagner if there's anything you consider a showstopper bug I will try to fix it.
from ij-ridgedetection.
Related Issues (20)
- Extend lines does not work correctly
- Make macro recordable HOT 7
- Overlap resolution by search radius + shortest path + straightness
- Contour classes are wrong when using SLOPE overlap resolution HOT 12
- There are junction points with line ids which do not exist
- There are junction points with line ids which do not exist when SLOPE overlap resolution is activated HOT 2
- Generate binary scene from detected lines HOT 1
- SLOPE overlap resolution produces phantom lines HOT 1
- arguments 'low' and 'high' never used in function Link.compute_contours
- ArrayIndexOutOfBounds exception
- Releasing a new version HOT 7
- Correlation between contrast range and the number (and or the length) of detected ridges
- Scripting in Python available HOT 2
- The position of the point is not accurate enough, and the angle will appear unselected when it tends to PI. HOT 1
- Error in contour linking HOT 2
- Potential issue in Link->compute_contours HOT 1
- potential bad assignment in the "split the lines at the junction points"
- response vector of the first Line in 'contours' list potential issues
- ArrayIndexOutOfBoundsException: 200 at line 1161 of Link.java
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ij-ridgedetection.