On May 17, 2012, at 8:42 AM, Roy Stogner wrote: > SerialMesh::renumber_nodes_and_elements() "renumbers" all elements, > true, but as long as they start out in proper order > (_elements[i]->id() == i) they should stay the same up until the first > hole is reached, which shouldn't happen until after all the level 0 > elements have been passed. Perhaps the trouble is that for file-based > numberings our MeshInput classes *aren't* starting us with > (_elements[i]->id() == i)?
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… Derek ------------------------------------------------------------------------------ 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
