Clock Offset with Day Carry
Offset civil seconds of day and retain signed day carry; no time-zone transitions or date interpretation.
Description
Offset civil seconds of day and retain signed day carry; no time-zone transitions or date interpretation.
Adding a signed offset to a clock reading can move across one or more day boundaries.
When to use this tool
Offset civil seconds of day and retain signed day carry; no time-zone transitions or date interpretation.
- Prepare the supplied seconds, offset 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 seconds, offset. 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.dayCarry. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Validate seconds of day and integer offset within plus or minus one billion. Return nonnegative modulo(total,86400) plus dayCarry=floor(total/86400).1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| seconds | seconds. | Safe integer |
| offset | offset. | Integer from -1e9 to 1e9 inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.seconds | The seconds value under the stated formula or text convention. |
| result.dayCarry | The day carry value under the stated formula or text convention. |
{
"input": {
"seconds": 10,
"offset": -20
},
"output": {
"result": {
"seconds": 86390,
"dayCarry": -1
}
}
}Limitations and assumptions
- Day carry is an integer offset, not a calendar date. No timezone, daylight-saving or leap-second rules are applied.
- 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
- Clock Components to Seconds Of Day
Join validated ordinary civil clock components into seconds of day; leap-second 60 is not accepted.
- Clock Window Day Splitter
Split each ordinary or overnight half-open civil clock window into same-day segments; no time-zone inference.