meshing.load — Load a saved solver mesh and its evidence as a jointly validated meshing.Mesh.
mesh = meshing.load(meshPath, evidencePath) reads a canonical solver-mesh artifact and its matching meshing-evidence artifact and returns them as one meshing.Mesh.
Syntax
mesh = meshing.load(meshPath, evidencePath)Inputs
meshPath- Type
StringScalar- Required
- Yes
- Default
- —
- Description
- Canonical solver-mesh artifact path.
evidencePath- Type
StringScalar- Required
- Yes
- Default
- —
- Description
- Matching canonical meshing-evidence artifact path.
Returns
mesh- Type
Any- Description
- Jointly validated meshing.Mesh object.
Errors
RunMat:meshing:InvalidInput- When
- A meshing object, path, option, artifact, or evidence contract is invalid, or meshing cannot produce a result that satisfies the request.
- Message
meshing operation failed
Behavior
Both paths are scalar text. Each file is decoded with its canonical codec, which checks its artifact kind and schema version, and the evidence is then validated against the mesh: the evidence must describe exactly this artifact, its request, and its stage results. Passing the paths in the wrong order, a mismatched pair, or a corrupted file fails without returning a mesh.
The files are the ones meshing.save and runmat mesh write, so a mesh generated on the command line or on another machine can be inspected and used in scripts. The loaded mesh has the same canonical_digest as the mesh that was saved.
Region identity is part of the mesh: every element and boundary face carries the canonical persistent identity (persistent-entity:sha256:...) of the CAD entity it came from, so a reloaded mesh selects model regions exactly like the mesh that was saved.
Reading is synchronous and requires filesystem access.
Use in a study
Load an archived mesh to rerun a study on exactly the same discretization: pass the result to fea.study(id, part, model, "Mesh", mesh). Check meshing.evidence(mesh) to confirm the request and geometry revision it was generated from.
Errors
Every failure reports RunMat:meshing:InvalidInput, with a message that names the operation and the specific cause.
Typical causes are the wrong number of arguments, an unreadable file, a file of the wrong artifact kind, or evidence that does not match the mesh.
Example
Reload a saved mesh and confirm its identity
part = geometry.load('box.brep', 'Units', 'm');
solverMesh = meshing.generate(part, 'TargetSize', 0.5, 'MaximumDeviation', 0.05, 'ElementOrder', 'tet4', 'Seed', 42);
meshing.save(solverMesh, 'artifacts/box.solver-mesh.cbor', 'artifacts/box.meshing-evidence.cbor');
reloaded = meshing.load('artifacts/box.solver-mesh.cbor', 'artifacts/box.meshing-evidence.cbor');
reloaded.canonical_digestUsing meshing.load with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how meshing.load changes the result.
Run a small meshing.load example, explain the result, then change one input and compare the output.
FAQ
Can I load only the mesh file?⌄
No. A solver mesh is admitted only together with the evidence that proves how it was generated, so both files are required.
Related Meshing functions
meshing.boundaryFaces · meshing.elements · meshing.evidence · meshing.generate · meshing.nodes · meshing.quality · meshing.regions · meshing.save
Related guides
Source you can read
Every RunMat function's source is public. Read exactly how meshing.load is executed, line by line, in Rust.
- View the source for meshing.load in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.