Mesh assigned node ID 0 which is different from the (zero-based) Exodus ID -1!

[Krystalfang]

I'm having trouble computing a complex model with moose, and the error message is as follows:

*** ERROR ***
Error! Mesh assigned node ID 0 which is different from the (zero-based) Exodus ID -1!

I think this problem comes from my pre-processing process. I completed the pre-processing on cubit, but I don't know exactly what this error message is pointing to, how do I need to modify it, or redefine the node ID.

[GiudGiud]

Hello

This is coming from the exodus file reader in libmesh. I think it s being confused because the numbering in your exodus file is not as expected by the reader.
Did you renumber node ids? What indexing did you choose?

Guillaume

[Krystalfang]

I'm not renumbering the nodes, there are 30,000+ output nodes, I think it is hard.

[Krystalfang]

I see that there is a redefinition of node ID in cubit, what should be the starting ID recognized by libmesh.

[GiudGiud]

Try 0

[GiudGiud]

any updates on this?
What is the numbering of the nodes when you open the file with another software than MOOSE

[Krystalfang]

Hi, thank you very much for your attention and sorry for being late. After following your suggestion, I redefine the node number in Trelis, starting from 0. From the performance of MOOSE, this problem solved successfully.