Closed archimedes4000 closed 5 years ago
I'm pretty sure this is the same problem I ran into. When a site is on the boundary, the edges are not created properly. The open pull request I have fixes this issue; try applying it to your branch.
Sorry for the delay in responding, @david94133
This did not fix the issue I have run across.
Fixed in #27 (v0.5.0)
When using jc_voronoi for a natural neighbor interpolation problem, I was testing jc_voronoi to make sure it was getting linked correctly by giving it a square of points at {0,0}, {val, 0}, {0, val}, {-val, 0}, and {0, -val}.
There appears to be a bug when val = 2 in this case. I went through and was checking the number of edges that each site said it had, and the {0,0} site is always supposed to say 4. When val = 2, it says it has two. This doesn't seem to happen when I rotate or shift the square. This code runs through these cases and some other vals other than 2
The result from this is
I am not sure why this is happening, especially since it works when val = 2 + 2 *numeric_limits::epsilon.
I am hoping someone more familiar with the code can find it the reason