Description
Constant Frame Time coordinate for one zero-based frame index; not a variable Frame Time Vector or acquisition datetime parser.
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.
Constant Frame Time coordinate for one zero-based frame index; not a variable Frame Time Vector or acquisition datetime parser.
When to use this tool
Use it for dicom frame increment time index term when the required inputs and conventions are already available.
How to use the tool and how it works
- Enter frameIndex, frameCount, frameTimeMs, firstFrameTimeMs. Use the stated units and boundary conventions.
- Run the calculation. Correct any input error before interpreting a result.
- Read timeMs, durationThroughFrameMs. Inspect any known, defined, inclusion, or boundary flags before interpreting numeric values.
Require positive integer frameCount, a zero-based frameIndex below that count, and nonnegative frameTimeMs. Return timeMs=firstFrameTimeMs+frameIndex*frameTimeMs and durationThroughFrameMs=(frameIndex+1)*frameTimeMs.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| frameIndex | Frame Index | Required. Safe integer; minimum 0. |
| frameCount | Frame Count | Required. Safe integer; minimum 1. |
| frameTimeMs | Uniform frame interval in milliseconds; zero is allowed. | Required. Finite number; minimum 0. |
| firstFrameTimeMs | First-frame time on the supplied millisecond axis. | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| timeMs | Time Ms | Required. Finite number. |
| durationThroughFrameMs | Number of frames through the selected frame multiplied by frameTimeMs, in milliseconds. | Required. Finite number. |
{
"input": {
"frameIndex": 4,
"frameCount": 10,
"frameTimeMs": 40,
"firstFrameTimeMs": 100
},
"output": {
"timeMs": 260,
"durationThroughFrameMs": 200
}
}Limitations and assumptions
- This assumes uniform frame timing; a zero step is allowed. It does not interpret Frame Time Vector, acquisition date-time values, or irregular timing metadata.
- 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 dicom frame increment time index term, 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
Similar or alternative tools
- Acquisition Time Offset Precision Flag
Preserve a truncated timestamp quantum and offset-known flag; unknown UTC values use flagged zero placeholders.
- DICOM Image Orientation Dot Orthogonality Gap
Check supplied DICOM row/column direction cosines for unit lengths and orthogonality using an explicit tolerance.