meshc — Create mesh-and-contour composite plots in MATLAB and RunMat.
meshc combines a wireframe mesh surface with contour overlays on the base plane. Composite handle and plotting behavior follow MATLAB semantics.
Syntax
h = meshc(Z)
h = meshc(X, Y, Z)
h = meshc(Z, Name, Value, ...)
h = meshc(X, Y, Z, Name, Value, ...)Inputs
Z- Type
NumericArray- Required
- Yes
- Description
- Surface height grid.
X- Type
NumericArray- Required
- Yes
- Description
- X axis vector/meshgrid matrix matching Z columns.
Y- Type
NumericArray- Required
- Yes
- Description
- Y axis vector/meshgrid matrix matching Z rows.
props- Type
Any- Required
- Variadic
- Description
- Name/value surface style options.
Returns
h- Type
NumericScalar- Description
- Handle to the rendered mesh surface (with contour overlay).
Errors
RunMat:meshc:InvalidArgument- When
- Surface/grid/axis inputs or style name/value arguments are invalid.
- Message
meshc: invalid argument
RunMat:meshc:Internal- When
- Internal surface/contour construction or render preparation fails unexpectedly.
- Message
meshc: internal operation failed
RunMat:plotting:TooManyOutputs- When
- More than one output is requested from a coordinate chart constructor.
- Message
plotting: too many output arguments
Behavior
meshc shares the same wireframe surface semantics as mesh for the primary surface object.
The primary surface's XData, YData, and ZData retain native single, double, or integer class and exact host values, including an owner-aware snapshot of resident inputs.
The documented independent color-array and leading-axes forms are not implemented yet; this remains a general graphics-surface gap.
The returned handle is the surface handle for the wireframe component of the composite.
Contour overlays are produced through the shared contour path.
View state, colormaps, and subplot-local metadata all flow through the shared axes model.
GPU-aware execution applies where supported to both the surface and contour sides of the composite.
Rendering and residency
meshc combines the shared wireframe and contour paths, retaining native coordinate storage for the returned surface properties while treating contour generation and rendering as explicit floating boundaries.
Declared source precision and class coverage
single
double
Coordinate broadcasting
none
Runtime contract and boundaries
Graphics results are host double handles; fill/fill3 may return a row of handles for independently created polygon columns/groups. Sphere instead supports zero through three requested outputs: statement form plots, while output forms return host double coordinate grids. Handle aliases, value-selected options and exact graphics receiver roles are resolved by Runtime, not guessed from scalar facts.
The existing numerical and geometry owners validate coordinates, integer controls, shapes and properties. Single/double and all eight integer source classes retain their native storage wherever the object has authoritative source properties; client geometry and renderer buffers are deliberate floating boundaries, not a promise of exact wide-integer pixel positions. There is no sparse/complex plotting implementation or numeric broadcasting promise here. Logical, scalar, vector, matrix, rank and empty admission follows each documented owner below rather than a universal coercion.
RuntimeOwned preparation retains the original BuiltinArguments through suspension and completion. Eligible direct GPU routes require the live owning provider, admitted precision/storage/shape, compatible exports and installed plotting device. NoAttempt means pre-effect inapplicability, not permission to swallow export, allocation, cancellation or emission errors. Existing provider errors are propagated and ingress errors are terminal Never replay. Source-property queries and figure persistence may require explicit owner-aware readback; surface property snapshots and quiver3/patch construction are not zero-copy routes.
Canonical UserInterface capability and host-callback effects reflect scene creation/presentation; function-sampling entries additionally declare Unknown effects for arbitrary user callbacks and require the Process execution stack. NativeAndWasm means the Runtime entry is portable, not that an absent graphics host is emulated. Portable Runtime linkage introduces no separate native numerical library artifact. Rendering is a fusion boundary and distributed execution is unsupported; no numeric provider kernel or fusion primitive is invented.
Chart scratch, metadata, retained render state and the sphere coordinate builder do not yet have complete finite host allocation ownership. The shared canonical HostAllocationReceipt policy guard refuses Managed work before extraction/gather/callbacks or scene mutation, preserves ordinary Unbounded routes, and checks captured cancellation generation and policy before publication. This is an explicit L25 gap, not allocation completion. Long synchronous geometry/copy loops, renderer/provider-private allocation accounting, full MATLAB property parity, physical performance and actual example execution remain independently required.
Supported representations and remaining forms
Supported input forms are Z and X,Y,Z, followed by the existing shared surface style name/value grammar. Z-only styles retain the rooted tail instead of being misclassified as three coordinates. X indexes columns and Y indexes rows. Explicit vectors or opposite-varying meshgrid coordinate matrices must match the height grid; mesh/meshc/surfc do not implement arbitrary parametric X/Y matrices, independent C color arrays or leading-axes forms merely because surf supports a broader surface representation.
Native Single/double/integer XData/YData/ZData and their shape remain authoritative for properties and scene persistence. Resident source snapshots are real owning-provider gathers even when eligible floating rendering also uses device buffers. A retained native property snapshot and a later host geometry fallback can perform repeated owning-provider readback/copy of the same resident source. This is an explicit performance frontier, not a precision-preserving provider numerical result or a one-readback guarantee. Complex/sparse inputs and malformed/empty grids follow existing shape/type errors, not silently accepted MATLAB parity.
Surface style parsing includes ColorMap/Colormap, Alpha/FaceAlpha, Wireframe, Shading, FaceColor, EdgeColor, Lighting, Visible and DisplayName according to the shared style owner. Mesh defaults to Turbo/faceted/wireframe; surfc defaults to Parula/smooth and composites add default-level contours at the surface base. The result is the primary surface handle, not a vector of composite handles. Broader property compatibility remains incomplete.
Meshc retains the wireframe surface as its primary object and adds a contour projection. Both required pieces are built before the render closure publishes them; automatic host fallback is not recovery from an attempted physical preparation.
Examples
Create a wireframe surface with contour overlays
[X, Y] = meshgrid(linspace(-2, 2, 50), linspace(-2, 2, 50));
Z = sin(X.^2 + Y.^2);
meshc(X, Y, Z);Compare wireframe/composite behavior with camera controls
[X, Y] = meshgrid(linspace(-3, 3, 60), linspace(-3, 3, 60));
Z = cos(X) .* sin(Y);
h = meshc(X, Y, Z);
view(3);
colormap('parula');Inspect the returned primary surface handle
[X, Y] = meshgrid(1:20, 1:20);
Z = X - Y;
h = meshc(X, Y, Z);
get(h, 'Type')Expected output:
ans =
'surface'Rendered meshc example
[X, Y] = meshgrid(linspace(-3, 3, 80), linspace(-3, 3, 80));
Z = (X.^2 - Y.^2).*exp(-0.18*(X.^2 + Y.^2));
meshc(X, Y, Z);
colormap('turbo');
colorbar;
title('Coupled Response Surface');
xlabel('x');
ylabel('y');
zlabel('Response');
view(40, 28);
Compare this result with other chart types in the plot examples.
Using meshc with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how meshc changes the result.
Run a small meshc example, explain the result, then change one input and compare the output.
FAQ
Where does the contour overlay appear in a meshc plot?⌄
The contour lines are projected onto the base plane beneath the wireframe, at the z-minimum of the axes. This gives you a top-down height map below the 3-D wireframe so you can read both the grid structure and the level sets at the same time.
What's the difference between meshc and mesh?⌄
mesh draws only the wireframe surface. meshc draws the same wireframe plus contour lines projected onto the base plane underneath. If you don't need the contour overlay, use mesh — it's the same surface rendering with less visual clutter.
Should I use meshc or surfc?⌄
Both add contour projections to the base plane. The difference is the surface itself: meshc uses a wireframe (transparent faces, grid lines only), while surfc uses a shaded, filled surface. Pick meshc when you want to see through the geometry, and surfc when you want a solid surface on top.
Related Plotting functions
2D Charts
area · bar · errorbar · heatmap · hist · histogram · loglog · pie · plot · scatter · semilogx · semilogy · stairs · stem
Other
addpoints · ancestor · animatedline · autumn · axes · barh · bone · caxis · cla · clf · clim · colorcube · colororder · cool · copper · copyobj · cylinder · daspect · datacursormode · dataTipTextRow · drawnow · fcontour · figure · fill · fill3 · findobj · fsurf · gobjects · gray · groot · hgload · hgsave · hidden · histogram2 · hold · hot · inferno · isgraphics · ishandle · jet · line · lines · linkaxes · magma · openfig · opengl · pan · parula · patch · pink · plasma · plotmatrix · plotyy · polarhistogram · polarplot · polarscatter · print · quiver3 · ribbon · saveas · savefig · sphere · spring · stackedplot · subtitle · summer · suptitle · text · textscatter · textscatter3 · triplot · turbo · viridis · waitbar · winter · wordcloud · xlabel · xlim · xline · xscale · xtickangle · xtickformat · xticklabels · xticks · ylabel · ylim · yline · yscale · ytickangle · ytickformat · yticklabels · yticks · zlim · zoom
More plotting resources
Source you can read
Every RunMat function's source is public. Read exactly how meshc is executed, line by line, in Rust.
- View the source for meshc 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.