animatedline — Create an animated line graphics object for incremental plotting.

animatedline creates a graphics handle backed by RunMat's normal 2-D or 3-D line rendering paths. The handle can be updated with addpoints and queried or styled with get and set.

Syntax

an = animatedline()
an = animatedline(x, y)
an = animatedline(x, y, z)
an = animatedline(..., Name, Value)
an = animatedline(ax, ...)

Inputs

Returns

Errors

How animatedline works

• animatedline() creates an empty animated line on the current axes.
• animatedline(x,y) creates a 2-D animated line with initial points.
• animatedline(x,y,z) creates a 3-D animated line when the initial coordinate vectors are nonempty.
• X, Y, and Z independently accept single, double, and all eight integer classes. Exact integer storage is read authoritatively before coordinates enter RunMat's client-side f64 graphics domain.
• A leading axes handle or Parent name/value pair routes the animated line to explicit axes.
• MaximumNumPoints accepts every integer class as a positive scalar, or a positive integral single/double value. The default is 1000000; positive Inf disables trimming.
• Integer MaximumNumPoints values are validated exactly before conversion to the host point-count type; zero, negative, fractional, nonfinite values other than positive Inf, and values beyond host limits reject.
• Returned handles report Type as animatedline and support line styling properties such as Color, LineWidth, LineStyle, marker properties for 2-D animated lines, DisplayName, and Visible.

Options

• Parent accepts an axes handle.
• MaximumNumPoints accepts a positive integral value in single, double, or any integer class, or positive Inf.
• Common line properties include Color, LineWidth, LineStyle, DisplayName, and Visible. Marker properties are supported for 2-D animated lines; 3-D animated lines reject marker metadata until RunMat's 3-D line renderer has marker support.

Does RunMat run animatedline on the GPU?

Construction gathers GPU coordinate vectors and resident numeric MaximumNumPoints scalars into client-side animated-line state. Integer coordinates cross one explicit floating graphics boundary, while integer point limits are validated exactly before host-size conversion.

Rendering still uses RunMat's existing line and line3 rendering paths after points are stored.

GPU memory and residency

animatedline accepts GPU-resident coordinate inputs but stores animated state as host-side graphics data so subsequent addpoints, get, and set operations have MATLAB-compatible handle semantics.

Examples

Create and update a 2-D animated line

an = animatedline('Color', 'r', 'MaximumNumPoints', 100);
addpoints(an, 1:3, [2 4 8]);
get(an, 'XData')

Expected output:

ans =
     1     2     3

Create a 3-D animated line

an = animatedline();
addpoints(an, [1 2], [3 4], [5 6]);
get(an, 'ZData')

Expected output:

ans =
     5     6

Using animatedline with coding agents

Open a RunMat example with live inputs, then ask the agent to explain how animatedline changes the result.

FAQ

Related Plotting functions

Open-source implementation

Unlike proprietary runtimes, every RunMat function is open-source. Read exactly how animatedline is executed, line by line, in Rust.

• View the source for animatedline in Rust on GitHub
• Learn how the RunMat runtime works
• Found a bug? Open an issue with a minimal reproduction.

About RunMat

RunMat is an open-source runtime that executes MATLAB-syntax code blazing on any GPU. It is licensed under the Apache 2.0 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.

Getting started · Benchmarks · Pricing