forked from flexible-collision-library/fcl
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Performance optimization for supportConvex (flexible-collision-librar…
…y#488) * Performance optimization for supportConvex The original implementation of supportConvex did a linear search across all vertices. This makes the Convex mesh smarter to make the search for the support vertex cheaper. - It builds an adjacency graph on all vertices upon construction. - It introduces the method findExtremeVertex Method which does a walk along the edges of the mesh to find the extreme vertex. - This is faster for large meshes but slower for small meshes. - Empirical data suggests around 32 vertices to be a good cut off. - This uses vertex count to determine which algorithm to use. - It also introduces initial validation of the mesh -- that validation absolutely necessary for the edge walking to provide a correct answer. - Several aspects of the implementation have been tested and tweaked for performance. See: - use of vector<int8_t> in Convex::findExtremeVertex - cache-friendly implementation of adjacency graph Convex::neighbors_.
- Loading branch information
1 parent
33cc3cf
commit 0d98b83
Showing
7 changed files
with
835 additions
and
54 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
Oops, something went wrong.