meshing.save — Save a solver mesh and its evidence as a canonical artifact pair.
saved = meshing.save(mesh, meshPath, evidencePath) writes the canonical solver-mesh artifact and its meshing evidence to two files and returns logical true; meshing.save(..., 'Force', true) replaces existing files.
Syntax
saved = meshing.save(mesh, meshPath, evidencePath, Name, Value, ...)Inputs
mesh- Type
Any- Required
- Yes
- Default
- —
- Description
- meshing.Mesh to persist.
meshPath- Type
StringScalar- Required
- Yes
- Default
- —
- Description
- Destination solver-mesh artifact path.
evidencePath- Type
StringScalar- Required
- Yes
- Default
- —
- Description
- Destination meshing-evidence path; must differ from meshPath.
Name, Value- Type
Any- Required
- Variadic
- Default
- —
- Description
- Optional Force (logical, default false) to replace existing destinations.
Returns
saved- Type
Any- Description
- Logical true once both artifacts are published.
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
meshPath and evidencePath are scalar text and must differ. Missing parent directories are created. The two artifacts are the canonical CBOR encodings, identical to the files runmat mesh writes for the same mesh, and they can be read back with meshing.load. Region identity is part of the mesh artifact, so no other file is written.
Existing destinations are protected: if either file exists, the call fails and none is changed, unless the only option, Force, is true. Force must be logical; numeric 1 is rejected.
All files are staged before any destination is replaced. If publishing one fails, the files already replaced are rolled back, so the set on disk always matches. The call returns true only after every file is in place.
Use in a study
Keep both files with analysis results. The mesh alone does not record how it was generated; the evidence binds it to the geometry revision, request, seed, and measured stage checks, and meshing.load admits the mesh only together with that evidence.
Errors
Every failure reports RunMat:meshing:InvalidInput, with a message that names the operation and the specific cause.
Typical causes are identical paths, an existing destination without Force, a non-logical Force value, an unknown option, or a filesystem failure.
Examples
Save a mesh and its evidence for an archive
part = geometry.load('box.brep', 'Units', 'm');
solverMesh = meshing.generate(part, 'TargetSize', 0.5, 'MaximumDeviation', 0.05, 'ElementOrder', 'tet4', 'Seed', 42);
saved = meshing.save(solverMesh, 'artifacts/box.solver-mesh.cbor', 'artifacts/box.meshing-evidence.cbor');Existing files are replaced only with Force
part = geometry.load('box.brep', 'Units', 'm');
solverMesh = meshing.generate(part, 'TargetSize', 0.5, 'MaximumDeviation', 0.05, 'ElementOrder', 'tet4', 'Seed', 42);
meshing.save(solverMesh, 'box.solver-mesh.cbor', 'box.meshing-evidence.cbor');
try
meshing.save(solverMesh, 'box.solver-mesh.cbor', 'box.meshing-evidence.cbor');
protected = false;
catch err
protected = strcmp(err.identifier, 'RunMat:meshing:InvalidInput');
end
replaced = meshing.save(solverMesh, 'box.solver-mesh.cbor', 'box.meshing-evidence.cbor', 'Force', true);Using meshing.save with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how meshing.save changes the result.
Run a small meshing.save example, explain the result, then change one input and compare the output.
FAQ
Why are there two files?⌄
The mesh artifact holds the discretization; the evidence artifact holds the request, geometry binding, and stage checks that prove the mesh is valid. They are saved and loaded as a pair.
Related Meshing functions
meshing.boundaryFaces · meshing.elements · meshing.evidence · meshing.generate · meshing.load · meshing.nodes · meshing.quality · meshing.regions
Related guides
Source you can read
Every RunMat function's source is public. Read exactly how meshing.save is executed, line by line, in Rust.
- View the source for meshing.save 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.