Skip to content

Main content

DICOM Frame Time Offset

Convert an explicit zero-based frame index to an offset under a supplied constant DICOM frame-time assumption.

Loading tool…

Description

Calculate a frame's time offset under a constant frame-time model.

Medical-image metadata separates patient position, laterality, pixel spacing, slice spacing, padding and frame timing. Row and column spacing order matters, and slice spacing is distinct from slice thickness. A rectangular voxel or constant-frame model uses declared geometry; it does not inspect images, confirm a patient or establish a clinical finding.

Calculate a frame's time offset under a constant frame-time model.

When to use this tool

Use DICOM Frame Time Offset when you already have zeroBasedFrameIndex, frameTimeMilliseconds and need to calculate a frame's time offset under a constant frame-time model.

How to use the tool and how it works

  1. Enter zeroBasedFrameIndex, frameTimeMilliseconds. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read offsetMilliseconds. Use the output convention below.

Require nonnegative safe whole zeroBasedFrameIndex and frameTimeMilliseconds>0; return index*frameTimeMilliseconds.1

Input fieldMeaning and unitsAccepted input
zeroBasedFrameIndexZero-based frame offset from the chosen constant-time origin.Required. Safe integer; minimum 0.
frameTimeMillisecondsFrame Time MillisecondsRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
offsetMillisecondsOffset MillisecondsRequired. Finite number.
json
{
  "input": {
    "zeroBasedFrameIndex": 12,
    "frameTimeMilliseconds": 40
  },
  "output": {
    "offsetMilliseconds": 480
  }
}

Limitations and assumptions

  • The index is zero based; variable frame timing, acquisition clocks and actual DICOM frame metadata are not read.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Inspect the original DICOM attributes and complete image geometry when validating an image record. Use the relevant attribute and value-representation checks for format compliance, and actual per-frame timing when constant spacing or frame time is inadequate.

References

  1. Calculation and input contract: radiology/dicom-frame-time-offset — tool.io

Similar or alternative tools