On Thu, 2 Aug 2012, Paul T. Bauman wrote: > On Wed, Aug 1, 2012 at 10:20 PM, Roy Stogner <royst...@ices.utexas.edu> > wrote: > > > We ought to also clearly document what happens with dimension > > mismatch: if a 2D Nedelec element is used while LIBMESH_DIM==3, should > > the corresponding FunctionBase entries be > > previous_variable,u,v,next_variable or should they be > > previous_variable,u,v,w=0,next_variable? > > Just to triple check: we currently tie the number of components to the > mesh_dimension() - this will return 2 for two-dimensional elements in 3 > spatial dimensions, correct?
Correct. At least for now. Eventually we'd like to support meshes with mixed element dimensionality, in which case a mixed 2D/3D mesh would have mesh_dimension()==3... no clue what we'd do here in that scenario, though. --- Roy ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
