Gmsh#

.msh read + write (v2) eager

Summary of the specification#

A Gmsh .msh file is a sequence of $Section / $EndSection blocks. $MeshFormat states the version, whether the file is ASCII or binary, and the size of a float. $Nodes lists node tags with coordinates, and $Elements lists elements with an integer type code and their node tags. $PhysicalNames maps physical group ids to names. Version 4.1 restructures nodes and elements into per-entity blocks with a leading count line, which is why the two revisions must be parsed differently.

Specification at a glance#

sections	$MeshFormat, $PhysicalNames, $Nodes, $Elements, $Periodic
v2 nodes	tag x y z, one per line
v4.1 nodes	entity blocks: numBlocks, then per-block tags and coordinates
element codes	integer type ids (1 = 2-node line, 2 = triangle, 4 = tetrahedron, …)
groups	$PhysicalNames: dimension, tag, “name”

Read the full Gmsh specification ↗

Reading#

import polyxios as px

mesh = px.read("model.msh")
mesh.vertices          # (n, 3)
mesh.element_types     # element groups found in the file

Writing#

px.write(mesh, "out.msh")

This codec takes no format-specific options.

Quirks worth knowing#

ASCII v2 and v4.1 are both read; writing emits v2, the revision every consumer still understands.
Physical group names become element tags, so named boundaries and volumes survive the read.
Node tags need not be contiguous; they are remapped to dense indices and kept as vertex tags.