Skip to content

Main content

Cardiac Cycle Phase Fraction

Normalize an explicit cardiac event offset to a supplied cycle duration without wrapping or assigning physiological phases.

Loading tool…

Description

Normalize a supplied event offset by a positive cardiac-cycle duration.

Cardiology records distinguish event times, signal intervals, recording duration, paper calibration and Doppler angle conventions. A waveform distance requires a stated recording speed, and a signed projected velocity is not a diagnosis. Timing fractions and source labels do not establish cardiac function or appropriate care.

Normalize a supplied event offset by a positive cardiac-cycle duration.

When to use this tool

Use Cardiac Cycle Phase Fraction when you already have eventOffsetMilliseconds, cycleMilliseconds and need to normalize a supplied event offset by a positive cardiac-cycle duration.

How to use the tool and how it works

  1. Enter eventOffsetMilliseconds, cycleMilliseconds. 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 phaseFraction, withinCycle. Inspect withinCycle before interpreting the associated values.

Require cycleMilliseconds>0; phase=eventOffset/cycle and withinCycle=0<=offset<cycle.1

Input fieldMeaning and unitsAccepted input
eventOffsetMillisecondsEvent Offset MillisecondsRequired. Finite number.
cycleMillisecondsCycle MillisecondsRequired. Finite number; strictly above 0.
Output fieldInterpretationReturned shape
phaseFractioneventOffsetMilliseconds/cycleMilliseconds without wrapping.Required. Finite number.
withinCycleTrue for offset in [0,cycleMilliseconds), excluding the final endpoint.Required. Boolean.
json
{
  "input": {
    "eventOffsetMilliseconds": 200,
    "cycleMilliseconds": 800
  },
  "output": {
    "phaseFraction": 0.25,
    "withinCycle": true
  }
}

Limitations and assumptions

  • No wrapping is applied and fractions outside [0,1) are retained. No cycle, event, cardiac phase, rhythm or clinical interpretation is detected.
  • 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

Review the original trace, acquisition settings, measurements and complete clinical context. Use the appropriate professional assessment for interpretation; local conversions and flags do not identify rhythms, assess disease or guide treatment.

References

  1. Calculation and input contract: cardiology/cardiac-cycle-phase-fraction — tool.io

Similar or alternative tools