-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
min_distance
doesn't work with 3D tracking where dz
not constant
#430
Comments
There's a secondary bug in |
I realised this when you pointed out the issue with |
Shouldn't we be able to just do interpolation first without too much of an issue? There's probably a performance penalty there, but I assume it isn't too bad of one. |
It probably should be fine, I just haven't had any time recently to look into implementing it. I'll look into making the kdTree/BallTree neighbour search a more generic method to avoid these issues in future, as it it will be useful for other methods |
Aha the feature detection code is making what should be a simple fix headache inducing 🙃 I'll see if I can get this fix finished in time for the 1.5.4 release, but it may have to wait until afterwards. It may also conflict with some of the changes in v1.6, so we'll have to watch out for that |
Resolved by #452 |
Reported to me by Yishi Hu from OU. When you use
min_distance
in feature detection with a non-constantdz
, it fails as the coordinate interpolation takes place aftermin_distance
is called. That meansmin_distance
doesn't have any vertical information. This should be able to be solved by reversing the order of the two calls.The text was updated successfully, but these errors were encountered: