-
-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Writing GMSH with multiple cell types #524
Labels
Comments
The mesh you attached is a super-simple triangle mesh and meshio has no problems reading it. You probably meant to upload something else. |
That was intentional. It's a super simple mesh with two cell types, and meshio can't write it back to a file:
|
Ah yes, okay. Well that still needs to be implemented. Feel free to PR. 😸 |
This was referenced Jan 5, 2020
This was referenced Oct 29, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm working on converting a tool that transforms the nodes of a mesh to use meshio for compatibility with multiple gmsh versions. For even a simple case with boundary lines and an interior surface, meshio isn't able to read and then write the mesh file (e.g. square.msh.gz), which is expected per the comment in
msh4_1.py
"not sure what to do if there are multiple element types present".It seems as though there's sufficient information in the mesh data structure to do this, however. Each element type can correspond to a separate entity, which is implicitly encoded by the
entityDim
andentityDim
defining a node block of the$Nodes
section. Writing the elements can then refer back to these entities.Unfortunately, this would lose some of the physical mesh data, although that could be another factor for determining when to begin a new entity: group by physical tag, (dimension), and element type.
I could take a look at implementing something along these lines myself, however I'm not super across the internal data structure maintained by meshio (and particularly whether inter-mesh conversion is a goal, and any considerations thereof).
The text was updated successfully, but these errors were encountered: