From: Roy S. <roy...@ic...> - 2012-05-17 15:28:17
|
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 |