datetick — Accept legacy date-axis calls without formatting axes.
RunMat compatibility no-op, not a date-axis formatter. All arguments are accepted without option validation. Resident argument payloads are gathered through their existing owners, then discarded. Success returns double zero, suppressed from automatic display; no axes, tick labels, files, or workspace are changed. This deliberately does not claim MATLAB datetick plotting semantics.
Syntax
status = datetick(args...)Inputs
args- Type
Any- Required
- Variadic
- Default
- —
- Description
- Accepted compatibility arguments; no axis formatting is performed.
Returns
status- Type
NumericScalar- Description
- Double zero; no axis change is made.
Errors
RunMat:datetime:InvalidArgument- When
- Input count is not one for isdatetime or two for a calendarDuration method.
- Message
datetime: invalid argument count
RunMat:datetime:TooManyOutputs- When
- More than one output is requested.
- Message
datetime: too many output arguments
RunMat:datetime:InvalidInput- When
- Calendar receiver/component storage, operand class, scalar expansion, or calendar range is invalid.
- Message
datetime: invalid calendar operator input
RunMat:parallel:InfrastructureFailure- When
- Calendar scratch has no complete managed owner under the selected finite allocation authority; the typed MissingManagedOwner control failure is preserved as infrastructure failure.
- Message
datetime: calendar workspace requires unrestricted allocation
Runtime behavior
Outputs are host-resident. Method calls accept exactly two inputs and zero or one requested output; isdatetime accepts one input; datetick accepts any number. Excess outputs are rejected before scratch, provider calls, or output publication.
Calendar methods use existing binary64 month/day components. Arrays require identical shapes unless an operand has one element. No singleton-dimension broadcasting is added. Resident operands are not downloaded by calendar methods; isdatetime checks class without reading payloads. Datetick retains compatibility downloads but does not change any axes.
Example
Accept legacy date-axis calls without formatting axes.
status = datetick('x','yyyy','keeplimits');Using datetick with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how datetick changes the result.
Run a small datetick example, explain the result, then change one input and compare the output.
Related Datetime functions
Calendar Duration
caldays · calendarDuration · calendarDuration.eq · calendarDuration.minus · calendarDuration.ne · calendarDuration.plus · calmonths · calquarters · calweeks · calyears · iscalendarduration · isdatetime
Datetime
Construction
Operators
datetime.eq · datetime.ge · datetime.gt · datetime.le · datetime.lt · datetime.minus · datetime.ne · datetime.plus
Indexing
Duration
days · duration · duration.eq · duration.ge · duration.gt · duration.le · duration.lt · duration.minus · duration.ne · duration.plus · duration.subsasgn · duration.subsref · hours · isduration · milliseconds · minutes · seconds · years
Source you can read
Every RunMat function's source is public. Read exactly how datetick is executed, line by line, in Rust.
- View the source for datetick 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.