Also, on a related note, it looks like in equation_systems.C around line
194 sets "mesh_changed = true"... no matter what.
So calling eq->reinit() will cause a mesh.contract() _no matter what_...
even if you haven't modified the mesh. Meaning that just calling
eq->reinit() you will get your nodes and elements renumbered!
It looks like this is in there because of backwards compatibility...
Derek
On Mon, May 14, 2012 at 12:37 PM, Derek Gaston <fried...@gmail.com> wrote:
> Around line 1100 in unstructured_mesh.C in UnstructuredMesh::contract() it
> calls renumber_nodes_and_elements()
>
> This is a bad idea.
>
> We've initialized our meshes by skipping renumbering... but then calling
> eq->reinit() causes all of the nodes / elems to then be renumbered.
>
> Any ideas for what to do here? Should we make a separate function to
> remove the NULLs out of the element / node vectors but keep the numbering
> the same?
>
> Should we just not renumber if we skipped renumbering when we initialized
> the mesh?
>
> 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
