The mesh model
This chapter defines the core concepts of mefikit: the elements that make up
a mesh, the distinction between topological and spatial dimension, and the
rules a mesh must follow to be considered valid.
Element
An element is an abstract mesh entity specified by:
- its type (e.g., triangle, hexahedron, polygon, polyhedron)
- its connectivity (indices referencing the global coordinate array)
In mefikit, elements are ephemeral, zero-copy views constructed on the fly
when iterating through a mesh block. They do not own memory; instead they refer
to underlying index and coordinate buffers. This mirrors VTK’s “cell iterator”
pattern while improving cache locality and reducing overhead.
Element iteration is a Rust-API detail. The Python bindings do not expose elements directly, because Python is meant for high-level scripting where you operate on whole meshes; the Rust API is where per-element work belongs.
Topological Dimension
The topological dimension of an element is the dimension of the mathematical object it represents:
- 0D → vertices
- 1D → edges / segments
- 2D → faces
- 3D → volumes
This categorization is independent of the embedding space and is central for field association and mesh validity checks.
Spatial Dimension
The spatial dimension is the dimension of the coordinate system in which the mesh is embedded, typically 2D or 3D. All element coordinates must be consistent with this spatial dimension. For example, one may have:
- 2D elements in 2D (pure surface mesh)
- 2D elements in 3D (surface embedded in 3D)
- 3D volumetric elements in 3D
mefikit does not assume a fixed coordinate system beyond this requirement.
Mesh
A mesh in mefikit is a container that holds:
- the global node coordinate array,
- a set of blocks, each containing elements of a given type,
- fields (scalar/vector/tensor) attached to elements of a given topological dimension,
- groups, i.e., labeled subsets of elements for boundary conditions, materials, or post-processing.
Properties:
- You may attach any number of fields or groups.
- Groups may overlap arbitrarily.
- A field must cover all elements of its associated topological dimension (similar to Gmsh’s “node data” or “element data” consistency).
If these constraints seem restrictive, mefikit encourages using multiple
meshes (e.g., one per partition, or one per physical domain) to better match
specialized workflows.
Topologically Valid Mesh
A topologically valid mesh in mefikit satisfies the following conditions:
-
No overlapping higher-dimensional elements Two 3D elements may share faces or edges, but they must not occupy the same region of space. (Duplicate faces in a hex-dominant mesh are allowed and interpreted in context.)
-
Lower-dimensional entities derive consistently from higher-dimensional ones
- All edges must be edges of some face or volume.
- All faces must be boundaries of some volume.
- No “floating” or orphaned lower-dimension elements are allowed. This is consistent with the expectations of many finite-element and finite-volume codes.
-
Non-degenerate geometry Elements must not be geometrically degenerate:
- triangles must have non-zero area,
- tetrahedra must have non-zero volume,
- polygons must be well-defined and non-self-intersecting, etc. These checks are similar to the geometric validation steps performed by MeshGems and various meshing libraries.