Replies: 1 comment 8 replies
-
I can replicate this; looking at it now.
And I can replicate this. Looks like there's 3 nodes getting a -2 id. |
Beta Was this translation helpful? Give feedback.
8 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear Community,
In Moose I have problems reading the MSH file attached. Because Moose uses libmesh and it looks that the effect is somehow related to libmesh I'd like to ask here for help. The corresponding discussion with Moose can be found here: idaholab/moose#30220
I'm using a

FileMeshGenerator
in Moose to read the MSH file containing the 8 volumes shown below and want to write it to a .e file:The MSH file is a reduced sample from a larger file. This is the smallest file I was able to create showing my problems. Unfortunately, its still very large.
If I import that file, I get 2 (actually 3) problems:
The names of some of the sidesets are not imported (e.g. srfCD4D). Others are (e.g. srfDE4A) imported.
One of the node sets gets a negative ID assigned. This leads to the following error message:
There is one more problem not shown in the file provided below: If the physical name IDs of volumes do not start with 1 but there are lower-dimensional sidesets starting with id=1, the volumes will be ignored (up to my understanding, MSH does not require for each dimension-category to start at 1).
Gmsh is reading the MSH file without problems and shows it correctly.
How can I resolve the problems described above? It is not clear to me, if my MSH file is faulty or there are some issues in libmesh.
The GEO file used
MSH file smpl2.msh
Beta Was this translation helpful? Give feedback.
All reactions