lt — Compute element-wise less-than comparisons in MATLAB and RunMat.
lt(A, B) (or A < B) compares inputs element-wise for less-than relations. Scalar expansion and output-shape behavior follow MATLAB semantics.
Syntax
tf = lt(A, B)Inputs
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
A | Any | Yes | — | Left operand. |
B | Any | Yes | — | Right operand. |
Returns
| Name | Type | Description |
|---|---|---|
tf | LogicalArray | Logical less-than result. |
Errors
| Identifier | When | Message |
|---|---|---|
RunMat:lt:InvalidInput | Operands contain unsupported types or mixed numeric/string domains. | lt: mixing numeric and string inputs is not supported |
RunMat:lt:SizeMismatch | Operands are not broadcast-compatible. | lt: array sizes are not compatible for broadcasting |
RunMat:lt:ComplexNotSupported | At least one operand is complex. | lt: complex numbers are not supported |
How lt works
- Numeric, logical, and character inputs compare element-wise using MATLAB's implicit expansion rules.
- Character arrays compare by Unicode code point; mixing them with numeric arrays behaves like comparing numeric codes (
'A' < 66). - String scalars and string arrays compare lexically; implicit expansion works across string dimensions.
- Complex inputs are not supported, matching MATLAB's behaviour.
- Mixed numeric/string inputs raise MATLAB-compatible type errors.
Does RunMat run lt on the GPU?
When both operands are gpuArray values and the active acceleration provider implements the elem_lt hook, RunMat executes the comparison entirely on the device and returns a gpuArray logical result. If the provider does not expose this hook, the runtime gathers the inputs to host memory automatically and performs the CPU comparison instead of failing.
GPU memory and residency
You usually do not need to call gpuArray explicitly. RunMat's native auto-offload planner keeps intermediate results on the GPU when fused expressions benefit from device execution. Explicit gpuArray and gather calls remain available for compatibility with MATLAB code that manages residency manually.
Examples
Determine Whether One Scalar Is Less Than Another
flag = lt(17, 42)Expected output:
flag =
1Filter Matrix Elements Below A Threshold
M = [1 2 3; 4 5 6];
mask = lt(M, 3)Expected output:
mask =
2×3 logical array
1 1 0
0 0 0Apply Less-Than With Implicit Expansion
v = [1 3 5 7];
mask = lt(v, [2 6])Expected output:
mask =
1×4 logical array
1 0 0 0Compare Character Data To Numeric Codes
letters = ['A' 'B' 'C'];
isBeforeC = lt(letters, 67)Expected output:
isBeforeC =
1×3 logical array
1 1 0Compare String Arrays Lexicographically
names = ["alice" "charlie" "bob"];
earlier = lt(names, "bob")Expected output:
earlier =
1×3 logical array
1 0 0Run lt Directly On gpuArray Inputs
G1 = gpuArray([1 4 7]);
G2 = gpuArray([2 4 8]);
deviceResult = lt(G1, G2);
hostResult = gather(deviceResult)Expected output:
deviceResult =
1×3 gpuArray logical array
1 0 1
hostResult =
1×3 logical array
1 0 1Using lt with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how lt changes the result.
Run a small lt example, explain the result, then change one input and compare the output.
FAQ
Does lt return logical values?⌄
Yes. Scalars return true or false. Arrays return logical arrays, and gpuArray inputs return gpuArray logical outputs.
How are NaN values treated?⌄
Any comparison involving NaN returns false, matching MATLAB behaviour.
Can I compare complex numbers with lt?⌄
No. MATLAB does not define relational ordering for complex numbers, so RunMat raises a MATLAB-compatible error when complex inputs are supplied.
How are strings compared?⌄
String scalars and arrays compare lexicographically using Unicode code points, with full support for implicit expansion against scalar strings.
Are character vectors treated as numbers or text?⌄
Character arrays participate as numeric code points when compared to numeric inputs, and they are converted to strings when compared against string scalars or arrays.
Do I need to gather results manually after a GPU comparison?⌄
No. When both inputs are gpuArray values and the provider supports elem_lt, the result stays on the GPU. Otherwise, RunMat gathers inputs transparently and returns a host logical array.
Does implicit expansion apply to string arrays?⌄
Yes. String arrays support MATLAB-style implicit expansion, so you can compare against scalar strings without manual replication.
Can I fuse lt inside GPU expressions?⌄
Yes. The builtin registers element-wise fusion metadata so the planner can fuse comparisons with surrounding GPU-friendly operations.
Related Logical functions
Open-source implementation
Unlike proprietary runtimes, every RunMat function is open-source. Read exactly how lt is executed, line by line, in Rust.
- View the source for lt 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.