On Thu, 6 Dec 2012, Kirk, Benjamin (JSC-EG311) wrote:
results *currently* in a global solution vector ordered like so:
(u0 u1 … uN v0 v1 … vN p0 p1 … pM)
whereas automatically identifying u & v and collapsing them into a
VariableGroup will yield instead
( u0 v0 u1 v1 … uN vN p0 p1… pM)
At the element level all should be good - the dof_indices will
simply be permuted to handle the global scatter/gather differences,
but if anyone is accessing the global solution directly things will
be different.
Ugh; you're right of course. In that case we might as well try to
enable "under-the-hood" optimization even for non-contiguous cases,
but provide some bool (controlled by API, command line option,
whatever) to allow it to be disabled for anyone depending on global
solution ordering.
---
Roy
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
