Timestamp Second Millisecond Split
Split an exact signed epoch millisecond integer into floor seconds and a nonnegative millisecond component.
Description
Split an exact signed epoch millisecond integer into floor seconds and a nonnegative millisecond component.
Splitting a negative millisecond value by floor keeps its millisecond component between zero and 999.
When to use this tool
Split an exact signed epoch millisecond integer into floor seconds and a nonnegative millisecond component.
- Prepare the supplied milliseconds fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter milliseconds. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.seconds, result.millisecond. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Parse exact milliseconds, compute floor(milliseconds/1000) and return that decimal-text seconds value plus the nonnegative remainder.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| milliseconds | Exact decimal integer text; keep it quoted in JSON rather than converting through a floating-point number. | Optional leading + or - and 1 to 256 decimal digits; no whitespace |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.seconds | The seconds value under the stated formula or text convention. |
| result.millisecond | The millisecond value under the stated formula or text convention. |
{
"input": {
"milliseconds": "-1"
},
"output": {
"result": {
"seconds": "-1",
"millisecond": 999
}
}
}Limitations and assumptions
- For example, minus one millisecond becomes seconds minus one and remainder 999. No calendar timestamp is formatted.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Lists are limited to 128 entries. JSON text must meet bounded size and depth checks, and numeric outputs beyond the safe finite magnitude are rejected. Exact large integers use decimal strings.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Keep elapsed durations, circular clocks, calendar months and epoch offsets distinct. Use a date/time method with explicit timezone and timescale rules for dated instants; arithmetic on one representation does not supply the others.
References
Similar or alternative tools
- Timestamp Millisecond Component Join
Join exact signed epoch second text and a 0–999 millisecond component without unsafe numeric conversion.
- Clock Window Day Splitter
Split each ordinary or overnight half-open civil clock window into same-day segments; no time-zone inference.