-
Notifications
You must be signed in to change notification settings - Fork 131
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
nearestvelocity #699
Comments
|
Also, link_df does not work for me. link_df_iter works. in |
I can confirm that there is something wrong with the
to
I provide my minimal dataset and code below. This is also visible in different versions of the NearestVelocityPredict section of the Dynamic predictors tutorial: The version with link_df()` is working here: Here it is not, there are no tracks to the particles of the third frame:
|
Yeah, I can confirm that |
Thanks for these reports! It looks like there's a serious omission in I probably can't get to it this week, but the needed steps are
|
Going to back to the original report of transposed coordinates by @wyu54 : It would be very helpful to have a minimal example to reproduce that issue. I suspect that the problem is that For now, the workaround would be to specify |
Since I ran into the same issue as @wyu54, I designed a small example. Explicitly calling with
|
Just a note that while I wasn't able to reproduce @snilsn's plots, I was able to produce something similar by:
|
Yeah, it looks like ultimately there are two issues here:
Addressing 1, my rudimentary print statement debugging indicates that the velocities are being calculated correctly by Regardless, it looks like the workaround for now is to use |
Continuing my work on I'm going to try to continue to find a solution here for at least the first issue, as I doubt that the second issue can be fully solved without it. |
Thanks for the examples! Testing for these issues and then cleanly fixing them turned out to be quite involved. Please take a look at #710 , and try it out if that's easy for you. |
Solves the problems for all of my cases @nkeim, thanks for your efforts! |
There might be a bug in NearestVelocityPredict:
line 172
self.interpolator = NearestNDInterpolator(positions.values, vels.values)
I think it should be
self.interpolator = NearestNDInterpolator(positions.values[:,::-1], vels.values[:,::-1])
Changing this fixed particle confusion problem in my tracking.
The text was updated successfully, but these errors were encountered: