Change contiguity of GTT's OBB cross-reference to be constructor option
Current code allows for a transition between contiguous (faster vector lookup) and non-contiguous (low memory map lookup) during operation. To do this requires frequent checking of whether or not the geometry managed by a GTT is contiguous, which is expensive.
It is rare that the non-contiguity will be substantial enough to cause a real memory problem, and even more rare that an initially contiguous set of geometry will change enough to be a problem.
This should be refactored to use the vector form as a default in the constructor, but allow the map form as an option, and to NOT allow switching during operation.
Comments (4)
-
reporter -
started work on this here: https://bitbucket.org/pshriwise/moab/branch/GTT_contiguous
-
Merge remote-tracking branch 'pshriwise/GTT_contiguous' into develop
PR #370: GTT contiguous
This PR addresses issue
#73raised by Paul Wilson regarding the contiguity of geometric EntityHandles and the cross-referencing data structures in GeomTopoTool.→ <<cset e14708997823>>
-
reporter - changed status to resolved
Resolved in PR#370
- Log in to comment
Care must be taken to expand the rootSet vector when new geometry sets are added during operation (add_geo_set)