Repository navigation
Overview
molivag edited this page Oct 19, 2026
·
1 revision
The input file for MeshTran is a plain text file. In future versions, support for a TOML-based input file is planned as an extension of the current format.
The file is composed of key = value pairs. The order in which keys appear does
not matter, since the parser reads each line and dispatches it internally using
a select case structure — each key is matched independently of its position in
the file.
General usage and formatting rules are described below. For the detailed description of each key see Input File Format, and for a full working example see Sample.
-
Comments are marked with
#or!. Anything after these characters on a line is ignored by the parser. - When a comment follows a
key = valuepair on the same line, make sure to leave enough whitespace between the value and the comment marker, so the parser does not misread the comment as part of the value. -
Keys are case-sensitive.
MESH_TYPEandmesh_typeare treated as different keys, so keys must match the expected case exactly. -
Blank lines are ignored and have no effect on section blocks or on the
parsing of
key = valuepairs — they can be used freely to improve readability.
Example:
```text
MESH_TYPE = tetra ! inline comment after the value
N_SURF = 120 ```
The input file is organized into the following sections:
- Mesh Nature and Threads
- Digital Elevation Model (DEM) Information
- Observation Data
- Surface Mesh Configuration
- Meshing over site zone
- Volumetric Refinement
- Model Region Attributes
- Mesh Parameters
MeshTran · Licencia MIT · © 2026