scatter — Create 2-D scatter plots with marker size/color encodings using MATLAB-compatible scatter forms.
scatter creates 2-D marker plots from paired x/y coordinates and returns a graphics handle. It supports MATLAB-compatible argument forms for marker sizes, colors, fill mode, axes targeting, and name-value styling.
Syntax
h = scatter(X, Y)
h = scatter(X, Y, S)
h = scatter(X, Y, S, C)
h = scatter(X, Y, LineSpec)
h = scatter(X, Y, Name, Value, ...)
h = scatter(ax, X, Y)All supported scatter forms
h = scatter(X, Y)
h = scatter(X, Y, S)
h = scatter(X, Y, S, C)
h = scatter(X, Y, LineSpec)
h = scatter(X, Y, Name, Value, ...)
h = scatter(ax, X, Y)
h = scatter(ax, X, Y, S)
h = scatter(ax, X, Y, S, C)
h = scatter(ax, X, Y, LineSpec)
h = scatter(ax, X, Y, Name, Value, ...)Inputs
X- Type
NumericArray- Required
- Yes
- Description
- X coordinates.
Y- Type
NumericArray- Required
- Yes
- Description
- Y coordinates.
S- Type
NumericArray- Required
- Yes
- Description
- Marker area specification.
C- Type
Any- Required
- Yes
- Description
- Color specification (uniform, per-point scalar, or RGB matrix).
lineSpec- Type
StyleSpec- Required
- Yes
- Description
- Marker/line style shorthand.
props- Type
Any- Required
- Variadic
- Description
- Name/value marker style properties.
ax- Type
AxesHandle- Required
- Yes
- Description
- Target axes handle.
Returns
h- Type
NumericScalar- Description
- Handle to the rendered scatter plot.
Errors
RunMat:scatter:InvalidArgument- When
- Input data, axes targeting, or marker style arguments are invalid.
- Message
scatter: invalid argument
RunMat:scatter:Internal- When
- Internal scatter construction or rendering fails unexpectedly.
- Message
scatter: 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
scatter(x, y) requires the same element count in both inputs.
The returned value is a scatter-handle object that can be inspected and updated through get and set.
Marker size, marker face color, marker edge color, and display name all flow through the shared plotting handle model.
Scatter plots integrate naturally with subplot and legend, so series labels and axes-local state stay scoped to the active axes.
GPU-resident point buffers can be rendered directly on the happy path; unsupported combinations fall back to host materialization while preserving the same visible result.
Rendering and residency
scatter is a rendering sink. GPU-resident inputs can stay on device when the shared plotting path can consume exported point buffers directly.
scatter preserves GPU residency when the plotting path can consume exported point buffers directly. If the active marker/style combination cannot use the direct path, RunMat gathers once and renders the same plot semantics on the fallback path.
The direct path keeps point buffers on the device and avoids an unnecessary host round-trip for supported scatter workflows.
Marker styling and legend/display-name behavior stay consistent across GPU and host fallback rendering.
Direct floating rendering precisions
single
double
Coordinate broadcasting
none
Runtime contract and boundaries
The result is a host graphics handle, not a numeric coordinate array. Coordinate parsing, native source storage, series expansion, style validation and graphics state use the existing plotting owners. Numeric handle aliases are resolved at Runtime, so static inference does not guess that a scalar coordinate denotes axes. The line, bar, barh and area constructors may return a row of handles; the other identities return the first created handle. More than one language output is rejected before chart work.
Single and double source data use their native storage where the chart has typed source properties; all eight integer classes use the declared identity-specific coordinate/control rules. Rendering is an explicit floating geometry boundary. In particular errorbar, bar, barh and area convert client graphics data to floating geometry; this does not certify exact integer-valued rendered pixels. Complex, logical, sparse, empty and matrix admission is decided by each existing numerical/shape parser, not by this shared ingress. Unsupported representations raise the existing parser diagnostic rather than being assumed fully MATLAB compatible.
Direct GPU rendering is conditional on the actual owning provider, live physical input leases, floating class/storage, supported shape/style, compatible shared device exports and native plotting feature availability. A pre-effect unavailable direct route may take the existing client path; a failed or partially completed export/reduction/emission is terminal and never permission to replay on the host. Source-property reads and figure persistence can perform later explicit readback. There is no elementwise/reduction fusion, distributed execution or portable numeric provider kernel for these graphics sinks.
User-interface capability and host-callback effects describe graphics creation/presentation, not numeric purity. Portable Runtime linking and an ordinary execution stack allow Native and Wasm ingress; actual presentation requires the installed graphics host. Retained chart data, style metadata, renderer buffers and serialization are separate lifetimes. Current chart scratch/state has no complete finite allocation owner: Managed policy is rejected before argument extraction, gather or chart mutation through the existing HostAllocationReceipt authority. Ordinary Unbounded resident and host routes remain available. Issuer/policy/cancellation are fenced before publication and errors carry Never replay. This refusal, unbounded host loops, provider/renderer-private allocations, full property parity and measured performance remain open obligations; Incomplete/Partial is not a completion certificate.
Supported representations and remaining forms
Coordinates use real single/double Tensor storage or native integer storage. Scalar logical coordinates pass through the existing NumericInput double conversion; logical arrays, complex arrays, sparse arrays, categorical and datetime coordinate objects do not have a NumericInput representation and are not implemented by this chart owner.
Coordinate counts must agree and the point constructor rejects empty data. Shapes are retained as source properties while all elements form one point series; full MATLAB matrix-per-column scatter expansion is not implemented. S defaults when empty, accepts scalar or per-point areas, and is converted to floating points-squared rendering metadata. C accepts a named/uniform color, scalar-value vector or per-point RGB/RGBA matrix according to the shared PointArgs owner. Filled, Marker, MarkerSize, MarkerFaceColor, MarkerEdgeColor, LineWidth, DisplayName and visibility use that existing style parser; malformed lengths/shapes and unsupported properties retain its diagnostics.
The returned numeric handle identifies one scatter object. Host XData/YData retain native coordinate class and shape; marker sizing and colormap normalization are separate floating boundaries. A supported direct path consumes live same-owner floating coordinate and marker exports; unsupported styles may require client metadata preparation before rendering.
Examples
Create a basic 2-D scatter plot
t = linspace(0, 2*pi, 100);
scatter(cos(t), sin(t));Use marker sizing and color-style workflows
x = linspace(0, 1, 25);
y = x.^2;
h = scatter(x, y);
set(h, 'SizeData', 12, 'MarkerFaceColor', 'r', 'Marker', 'o');Drive the legend from scatter object display names
x = 1:10;
h1 = scatter(x, x);
set(h1, 'DisplayName', 'linear');
hold on;
h2 = scatter(x, x.^2);
set(h2, 'DisplayName', 'quadratic');
legend;Rendered scatter example
reference = 10:10:100;
run_a = [11.8 21.6 31.5 41.9 51.2 61.7 71.5 81.8 91.3 101.0];
run_b = [8.7 18.4 28.8 38.5 48.6 58.9 68.4 78.9 88.7 98.5];
scatter(reference, run_a, 90, [0.15 0.65 1.0], 'filled');
hold on;
scatter(reference, run_b, 90, [1.0 0.45 0.2], 'filled');
plot([10 100], [10 100], '--', 'LineWidth', 1.5);
hold off;
legend('Calibration run A', 'Calibration run B', 'Ideal response');
title('Calibration Repeatability');
xlabel('Reference value');
ylabel('Measured value');
grid on;
Compare this result with other chart types in the plot examples.
Using scatter with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how scatter changes the result.
Run a small scatter example, explain the result, then change one input and compare the output.
FAQ
How do I color scatter points by a third variable?⌄
Set the CData property on the scatter handle to a vector the same length as x and y. The values map into the current colormap.
x = randn(1, 100);
y = randn(1, 100);
z = x.^2 + y.^2;
h = scatter(x, y);
set(h, 'CData', z);
colorbar;Each point gets a color proportional to its z value. Call colorbar to show the mapping.
What's the difference between scatter and plot?⌄
scatter draws unconnected markers and supports per-point size (SizeData) and per-point color (CData). plot connects points with lines and applies uniform styling to the whole series. Use scatter when the individual point properties carry meaning; use plot when the connection between points is what matters.
How do I control marker size in scatter?⌄
Pass a scalar or vector to SizeData via the handle. A scalar sets uniform size; a vector sets per-point sizes.
h = scatter(x, y);
set(h, 'SizeData', 40); % uniform size
set(h, 'SizeData', abs(y) * 50); % size proportional to |y|The size unit is points squared, matching MATLAB conventions.
Related Plotting functions
2D Charts
area · bar · errorbar · heatmap · hist · histogram · loglog · pie · plot · 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 scatter is executed, line by line, in Rust.
- View the source for scatter 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.