On Dec 6, 2012, at 1:32 PM, Roy Stogner <royst...@ices.utexas.edu> wrote: > 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.
Will do. I'm starting with the guts to support the add_variables() interface now, and will work the auto detection magic once this is done. While I have your attention, - the SCALAR Variables logic has me a bit confused. Looks like in the System we always assume any SCALAR values were added last, and that we can have only one. As such, a VariableGroup with multiple SCALAR types makes no sense (under current assumptions) right? If you need more SCALARs you up the oder, not append more - seems to be my reading of what is there presently. Mostly trying to grok the Variable::first_scalar_number() business. -Ben ------------------------------------------------------------------------------ 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
