Hi! I bumped into this problem in UnstructuredMesh: at the end of copy_nodes_and elements(), we call this->prepare_for_use(false) and we may end up with different node numbering. Since this is called from constructors and copy-constructors, the newly created object may have different node numbering, resulting in non-identical copy of the original one. Attached patch fixes that issue.
If there are no objections, I can check this patch in. -- David
0001-Do-not-renumber-when-doing-mesh-copy.patch
Description: Binary data
------------------------------------------------------------------------------ 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
