-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
ContinuousSpace: Fix get_distance calculation on toroidal boundary condition #430
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
Conversation
|
@rht Thanks for the fix! It works well. |
|
Thanks @rht. But what do you mean by
Are there any test cases where the calculation fails? |
There are not. In retrospect, I should have added this point in my description though. |
|
For clarification (maybe I don't understand), how does this PR differ from #425 ? |
|
#425 fails the test at [1] [1] #410 (comment) |
5f07737 to
f047ae4
Compare
|
I added that test case |
|
I think this can finally be merged, thanks everyone for the contributions! |
cc: @simonchx, @clmerlos, @JamesArruda, @njvrzm
This fixes the distance calculation back to before this commit change: 600c62b#diff-84ac902399d236cac5d91bacaad69b2bL547, additionally, uses numpy for the arithmetic as suggested by @JamesArruda's implementation. This version of distance calculation passes the most number of test cases.
This fixes #410.