Does MOOSE simulation output (Exodus) preserve node numbering and element connectivity in the original mesh file?

[abqlalala]

Hi everyone, I realized the Exodus output file from MOOSE has different node numbering and element connectivity from the original mesh file. I did not use MPI but did use multithreading (--n-threads) for the simulation. I am wondering if there is way to preserve the original node ordering? If not, is it possible to output the original node number as an additional output so I can retrieve the original mesh information? I need it because some postprocessing code I have is based on the original mesh information, and it breaks with the modified mesh information in the Exodus output.

Thanks!

[GiudGiud]

Hello

It won't be possible to preserve the node ordering. That one is set by the format.

You can output the initial node ordering using a new auxkernel. I don't think we have one for this already. It will be very simple:

ComputeValue() will simply be:
{
return _current_node->id();
}

Guillaume

[abqlalala]

Thanks!

[lindsayad]

There is a libmesh issue for this: libMesh/libmesh#3966