Timestamp Precision Loss Audit
Audit exact integer timestamp precision loss when flooring to a positive unit quantum, retaining signed-era behavior.
Description
Audit exact integer timestamp precision loss when flooring to a positive unit quantum, retaining signed-era behavior.
Reducing timestamp precision to a quantum loses a remainder. For negative values, this implementation rounds down rather than toward zero.
When to use this tool
Audit exact integer timestamp precision loss when flooring to a positive unit quantum, retaining signed-era behavior.
- Prepare the supplied timestamp, quantum 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 timestamp, quantum. 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.truncatedTimestamp, result.lostUnits, result.loss. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require positive exact integer quantum. Compute floor(timestamp/quantum)*quantum as truncatedTimestamp, return timestamp minus that value as lostUnits and flag nonzero loss.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| timestamp | 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 |
| quantum | 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.truncatedTimestamp | The truncated timestamp value under the stated formula or text convention. |
| result.lostUnits | The lost units value under the stated formula or text convention. |
| result.loss | Flag for loss under the exact condition described above. |
{
"input": {
"timestamp": "-1",
"quantum": "1000"
},
"output": {
"result": {
"truncatedTimestamp": "-1000",
"lostUnits": "999",
"loss": true
}
}
}Limitations and assumptions
- The field name truncatedTimestamp does not imply truncation toward zero. Units follow the inputs and no nearest-rounding or epoch policy is inferred.
- 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 Epoch Offset Transform
Translate integer timestamps between explicitly supplied epoch origins expressed in the same units; no calendar or leap-second conversion.
- Timestamp Millisecond Component Join
Join exact signed epoch second text and a 0–999 millisecond component without unsafe numeric conversion.