-
Notifications
You must be signed in to change notification settings - Fork 421
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
change contact, distance primitive id to intptr_t
The contact and distance result brief primitive information stored the brief information in an `int`. However, some primitive ids can only be stored by relative pointer (namely octree nodes), and `int` is not wide enough on 64-bit platforms to safely store a pointer. So upgrade the brief information to be `intptr_t` which is guaranteed to be wide enough. Also, provide a method, getNode, to make use of the query cell id returned for `fcl::OcTree` cells. For getNode to efficiently find the cell from the query cell id, it must be passed the contact point or nearest point returned by the query to work correctly. The getNode method returns a pointer to the corresponding OcTree node, and also optionally returns the AABB representing the cell, the octomap::OcTreeKey (which can be used with various octomap APIs) and the depth of the cell in the tree (which may also be needed when using octomap APIs). Refer the contact info and distance result documentation to the new getNode method for callers to know how to make use of these OcTree query cell ids. Add OcTree query cell id tests to test the new getNode method at the same time as testing the BVH mesh ids in test_fcl_octomap_collision.cpp.
- Loading branch information
C. Andy Martin
committed
May 30, 2020
1 parent
9269ccc
commit db8f8bd
Showing
6 changed files
with
185 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters