Yep - I think that would do it! Derek
On May 17, 2012, at 9:28 AM, Roy Stogner wrote: > > On Thu, 17 May 2012, Derek Gaston wrote: > >> You're right about Elements, Roy… I hadn't notice that. But for >> nodes that's not the case (and that's where we're seeing problems). >> >> The issue happens when the node numbering for an element in a read >> in mesh doesn't match the libMesh ordering for nodes on that >> element. Look just below where it's setting the elem ids… > > Ha! I saw the behavior for elements and just assumed it would be > using the same behavior for nodes. > > Would it fix things for you (at least as a first pass) if it *was* > using the same behavior for nodes? Take the node renumbering out of > the elements loop, add a nodes loop which does the same > renumbering-without-reordering? > --- > 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
