-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
KdTree::remove() fails in some circumstances #12
Comments
Thanks for this report too. This is a strange one! Looks like I'll have to break out the debugger for this one... |
Confirmed, I see the same behaviour. Looking into it now |
Fixed! Released as https://crates.io/crates/kiddo/2.0.0-beta.7. Thanks a lot for the example, it was invaluable in tracking down the problem! Please do let me know how you get on if you continue to use the v2 beta, especially if you experience any more issues - happy to help. |
Great, thanks! |
This is a WIP commit before replacement of Kiddo by kdtree 0.7, as kiddo has breaking bugs (eg sdd/kiddo#12).
It seems there is more problems with point removals. See #28. |
I have been able to narrow down a case where
remove()
incorrectly fails to remove an item, returning 0:This test fails as
tree.remove(&pts[0], 0)
return 0. Commenting out any of the points in the input array makes the test pass. Removing any/all of the points except 0 works. Removing index 0 fails in all circumstances.Also, this failing case appears to be sensitive to the specific order of the input points. I can't reproduce the fail by moving points around.
kiddo 2.0.0-beta.5
Toolchain: nightly-2023-03-03
macOS Ventura 13.2.1 on MBP M1 Max
The text was updated successfully, but these errors were encountered: