-
Notifications
You must be signed in to change notification settings - Fork 421
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
Nan value in the nearest points when using distance() #293
Comments
Thanks for the detailed reproduction info. I'll look into this and get back to you. |
@SeanCurtis-TRI What I have found is that the normal |
SeanCurtis-TRI
added a commit
to SeanCurtis-TRI/fcl
that referenced
this issue
Jun 1, 2018
If the simplex is degenerate, it can lead to divide-by-zero errors. This test is drawn from the real world and exposes such a problem - nearest points are returned as NaN. See flexible-collision-library#293 for the discussion
SeanCurtis-TRI
added a commit
to SeanCurtis-TRI/fcl
that referenced
this issue
Jun 8, 2018
If the simplex is degenerate, it can lead to divide-by-zero errors. This test is drawn from the real world and exposes such a problem - nearest points are returned as NaN. See flexible-collision-library#293 for the discussion
sherm1
pushed a commit
that referenced
this issue
Jun 19, 2018
…mplex (#296) * Expose numerical errors in gjk_libccd-inl.h extractClosestPoints() If the simplex is degenerate, it can lead to divide-by-zero errors. This test is drawn from the real world and exposes such a problem - nearest points are returned as NaN. See #293 for the discussion * Make extractClosestPoints more robust For simplex of size n, if the simplex is degenerate, extracts from a simplex of size n - 1 (to prevent returning NaN). 1. Refactor point extraction into independently callable methods. 2. At each level, add method for downgrading the simplex. 3. Add unit tests on the local methods. 4. Add integration test with motivating example. 5. Update documentation of this implementation.
nicovanduijn
pushed a commit
to nicovanduijn/fcl
that referenced
this issue
Jul 5, 2018
…mplex (flexible-collision-library#296) * Expose numerical errors in gjk_libccd-inl.h extractClosestPoints() If the simplex is degenerate, it can lead to divide-by-zero errors. This test is drawn from the real world and exposes such a problem - nearest points are returned as NaN. See flexible-collision-library#293 for the discussion * Make extractClosestPoints more robust For simplex of size n, if the simplex is degenerate, extracts from a simplex of size n - 1 (to prevent returning NaN). 1. Refactor point extraction into independently callable methods. 2. At each level, add method for downgrading the simplex. 3. Add unit tests on the local methods. 4. Add integration test with motivating example. 5. Update documentation of this implementation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While doing distance check for two boxes, I found
nan
values in the nearest points after using distance().One of the sample is as follows, and two boxes do not collide.
Can someone help me to figure out the reason, or give me some hint about the algorithm of distance calculation between two boxes?
The text was updated successfully, but these errors were encountered: