second — Extract second components from datetime values with MATLAB-compatible output shapes.
second extracts the seconds component from datetime scalars or arrays and returns doubles with the same shape as the input. Fractional seconds are retained to the precision of the stored binary64 serial-date value, not arbitrary nanosecond precision.
Syntax
s = second(t)Inputs
t- Type
Any- Required
- Yes
- Description
- Host datetime scalar or array; no text or numeric conversion.
Returns
s- Type
NumericArray- Description
- Real double seconds with the stored datetime array shape, subject to serial-date precision.
Errors
RunMat:datetime:InvalidInput- When
- Input values cannot be parsed, converted, or broadcast to a valid datetime result.
- Message
datetime: invalid input
RunMat:second:TooManyOutputs- When
- More than one output is requested.
- Message
second: too many output arguments
Behavior
second(t) accepts datetime scalars and datetime arrays.
The output shape matches the input shape.
Returned values are doubles so fractional seconds can be represented.
Passing a non-datetime value raises a datetime-specific error.
Placement and effects
datetime values are host-side objects; second extracts the second component on the CPU.
No. second reads datetime objects on the CPU and returns ordinary host-side numeric arrays.
second does not dispatch GPU kernels; it extracts the second component from CPU-side datetime objects.
This host operation reads only the supplied datetime object; it does not read Clock, gather inputs, or call an acceleration provider. It may throw or suspend at bounded invocation-owned CPU checkpoints. There is no GPU kernel, fusion route, or distributed support. VM/native/Wasm use the canonical portable Runtime binding; this is a source declaration, not backend execution evidence.
Syntax and argument roles
s = second(t)
t must be a datetime object; relative text, numeric serial values, duration values, and resident numeric values are not converted. Exactly one output is available.
Current implementation frontier
Output precision follows binary64 serial-day storage. Nonfinite serials are rejected by the existing calendar conversion. Native stored serial elements are converted individually without a materialized double copy. Independent MATLAB parity and complete backend qualification remain incomplete.
Finite execution frontier
Stored datetime second extraction supports finite Managed execution through the canonical exact output owner: the final double payload and full shape are admitted together, input storage remains borrowed and rooted across suspension, and scalar results remain inline. The original owner is checked after suspension and at publication. This closes the second mapper allocation path, not the broader calendar/legacy-text Managed frontier or unexecuted backend qualification.
Examples
Extract whole seconds from a scalar datetime
t = datetime(2024, 4, 9, 13, 30, 5);
s = second(t)Preserve fractional seconds
t = datetime(2024, 4, 9, 13, 30, 5.25);
s = second(t)Using second with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how second changes the result.
Run a small second example, explain the result, then change one input and compare the output.
FAQ
Can second return fractional values?⌄
Yes. RunMat returns fractional seconds as doubles, subject to the precision of the stored binary64 serial-date value.
Does second preserve the input shape?⌄
Yes. The numeric output has the same size as the input datetime array.
Does second run on the GPU?⌄
No. datetime values are host-side objects, so second executes on the CPU.
Related Datetime functions
Calendar Duration
caldays · calendarDuration · calendarDuration.eq · calendarDuration.minus · calendarDuration.ne · calendarDuration.plus · calmonths · calquarters · calweeks · calyears · datetick · 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 second is executed, line by line, in Rust.
- View the source for second 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.