Skip to content

Main content

Acquisition Time Offset Precision Flag Tool

Preserve a truncated timestamp quantum and offset-known flag; unknown UTC values use flagged zero placeholders.

Loading tool…

Description

Preserve a truncated timestamp quantum and offset-known flag; unknown UTC values use flagged zero placeholders.

An image grid has array indices as well as physical spacing, timing, and signal conventions. A calculation on supplied metadata describes one part of that grid or signal; it does not inspect an image, validate a complete file, or interpret anatomy.

Preserve a truncated timestamp quantum and offset-known flag; unknown UTC values use flagged zero placeholders.

When to use this tool

Use it for acquisition time offset precision flag when the required inputs and conventions are already available.

How to use the tool and how it works

  1. Enter timeSeconds, utcOffsetSeconds, quantumSeconds, offsetKnown. Use the stated units and boundary conventions.
  2. Run the calculation. Correct any input error before interpreting a result.
  3. Read utcDefined, utcLower, utcUpper. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.

Require positive quantumSeconds. If offsetKnown is true, set utcLower=timeSeconds-utcOffsetSeconds and utcUpper=utcLower+quantumSeconds. Otherwise return both numeric bounds as zero with utcDefined false.1

Input fieldMeaning and unitsAccepted input
timeSecondsTime SecondsRequired. Finite number.
utcOffsetSecondsUtc Offset SecondsRequired. Finite number.
quantumSecondsPositive truncation precision in seconds.Required. Finite number; strictly above 0.
offsetKnownOffset KnownRequired. Boolean.
Output fieldInterpretationReturned shape
utcDefinedWhether a supplied UTC offset makes the returned bounds meaningful.Required. Boolean.
utcLowerLower UTC bound in seconds, or a zero placeholder when utcDefined is false.Required. Finite number.
utcUpperUpper UTC bound in seconds, or a zero placeholder when utcDefined is false.Required. Finite number.
json
{
  "input": {
    "timeSeconds": 3600,
    "utcOffsetSeconds": 1800,
    "quantumSeconds": 60,
    "offsetKnown": true
  },
  "output": {
    "utcDefined": true,
    "utcLower": 1800,
    "utcUpper": 1860
  }
}

Limitations and assumptions

  • The interval represents a supplied truncated time precision, not rounding by half a quantum. Unknown UTC bounds are placeholders; no time zone, date rollover, or offset is inferred.
  • The field tables describe structural bounds; the mechanics also state cross-field requirements. Malformed input shapes, disallowed keys, and invalid domains cause input errors. Results must remain finite and within the declared output contract. A successful false flag or zero placeholder is distinct from an error.
  • Numeric arithmetic uses binary floating point. Exact comparisons have no hidden tolerance or decimal rounding; negative zero is exported as zero. Decimal-text integer operations retain the exactness specifically stated above.

Alternative or Complementary methods

For acquisition time offset precision flag, check the source records and the supplied rule before comparing the result with another method. Use a full image reader and geometry or signal analysis when the task requires interpreting image data.

References

  1. Calculation and input contract: radiology/acquisition-time-offset-precision-flag — tool.io

Similar or alternative tools