Sorry to send two messages in a row - but I'm wondering if it would be ok
to expose BoundaryInfo::_boundary_side_id ?
The issue I'm having is that calling boundary_ids() is "slow" (and causes
memory allocations which is actually the thing I'm trying to remove)
because it passes in a std::vector that it fills...
Barring that - would be it ok if I make boundary_ids() reserve() enough
size in the vec_to_fill to potentially hold all of the IDs from the
equal_range()? That should help out with the reallocs.
I am reusing the vec_to_fill... but it's still not enough to keep down the
memory allocation/deallocation associated with that routine.
Another option is to template boundary_ids() so that I can pass in my own
container that is statically sized (over-sized to hold the max number of
IDs) and won't do any allocation.
Derek
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
