[vtkusers] vtkKDTree FindClosestPoint bug?

[David Doria]

It seems that FindClosestPoint (both versions) ocasionally produce incorrect
points - where FindClosestNPoints works correctly every time. Here is sample
code and the data file it is intended to work with. The correct index of the
closest point is 1, but FindClosestPoint returns 121.

http://rpi.edu/~doriad/VTK_List/ClosestPointBug/

Has anyone else had this problem? This seems to be a VERY big problem
(potentially breaking many peoples code?) if I haven't done anything wrong.
Can anyone confirm or deny? I will put it on Mantis if I don't hear people
shouting that I just did something incorrectly! haha

Thanks,

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20090915/f60d35bd/attachment.htm>