jhlee-visionkalman / accord

Automatically exported from code.google.com/p/accord
0 stars 0 forks source link

KD-Tree does not always capture all of the possible neighbors for a given point #71

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The mistake seems to be in the TryAdd method of KDTreeNodeCollection.

On line 137: farthest = node;

At some point the node collection was meant to be made an ordered collection. 
This could have been inadvertently reversed on a previous version and this 
change was not captured by the unit tests.

Original issue reported on code.google.com by cesarso...@gmail.com on 18 Sep 2013 at 5:38

GoogleCodeExporter commented 9 years ago
Should have been fixed in the 2.11 release.

Original comment by cesarso...@gmail.com on 27 Oct 2013 at 4:51