On Tue, 27 Nov 2012, Derek Gaston wrote:
Also - one more question along these lines... when an Elem is coarsened I
know that the children hang out for a little while - but then are possibly
"pruned". Do we have the ability to impact this situation? i.e. I would
like the children to hang out (as JUST_COARSENED or INACTIVE or something)
until I specifically call a function to clean them up. The reason: I'm need
to recover some data from the children before they go away completely.
Hmmm... this currently isn't under user control - Mesh::contract()
gets called from EquationSystems::reinit() whenever there are newly
coarsened elements.
It probably *should* be under user control, though, if you want to add
an API.
You know, for that matter we ought to finally make the optimization
we've been holding off on in those FIXME commets in ES::reinit, or at
least we should find some way to test for and deprecate the
"refine_and_coarsen was called outside reinit" case that's preventing
that optimization.
---
Roy
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
DESIGN Expert tips on starting your parallel project right.
http://goparallel.sourceforge.net
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
