Skip to content
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

Closed
4 tasks done
freemansw1 opened this issue May 21, 2024 · 6 comments · Fixed by #452
Closed
4 tasks done

min_distance doesn't work with 3D tracking where dz not constant #430

freemansw1 opened this issue May 21, 2024 · 6 comments · Fixed by #452
Assignees
Labels
bug Code that is failing or producing the wrong result
Milestone

Comments

@freemansw1
Copy link
Member

Reported to me by Yishi Hu from OU. When you use min_distance in feature detection with a non-constant dz, it fails as the coordinate interpolation takes place after min_distance is called. That means min_distance doesn't have any vertical information. This should be able to be solved by reversing the order of the two calls.

  • Have you searched the issue tracker for the same problem?
  • Have you checked if you're using the latest version? If not, which version are you using?
  • Have you mentioned the steps to reproduce the issue?
  • Have you, if applicable, included error messages?
@freemansw1 freemansw1 added the bug Code that is failing or producing the wrong result label May 21, 2024
@freemansw1
Copy link
Member Author

There's a secondary bug in filter_min_distance, line 1534 of main, where it always uses dz even if none is passed.

@w-k-jones
Copy link
Member

I realised this when you pointed out the issue with dz in #372 . It's a bit trickier with feature detection, as we will need to perform coordinate interpolation before distance filtering. It may have to wait until I have time to fix it in a later release

@w-k-jones w-k-jones self-assigned this May 21, 2024
@freemansw1
Copy link
Member Author

I realised this when you pointed out the issue with dz in #372 . It's a bit trickier with feature detection, as we will need to perform coordinate interpolation before distance filtering. It may have to wait until I have time to fix it in a later release

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.

@w-k-jones
Copy link
Member

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

@w-k-jones
Copy link
Member

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

@w-k-jones
Copy link
Member

Resolved by #452

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Code that is failing or producing the wrong result
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants