Skip to content

Main content

Running Contact Flight Duty Factor

Describe one explicitly paired running contact/flight cycle under a stated two-phase segmentation.

Loading tool…

Description

Calculate supplied contact and flight fractions of a positive cycle.

Movement geometry depends on coordinate registration, time origins, force signs and reference axes. A moment arm must already represent perpendicular leverage, a stride percentage has an endpoint convention, and a toe-to-heel projection differs from full Euclidean separation. Scalar results do not establish a movement diagnosis or a safe activity.

Calculate supplied contact and flight fractions of a positive cycle.

When to use this tool

Use Running Contact Flight Duty Factor when you already have contactSeconds, flightSeconds and need to calculate supplied contact and flight fractions of a positive cycle.

How to use the tool and how it works

  1. Enter contactSeconds, flightSeconds. 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 cycleSeconds, contactDutyFactor, flightFraction. Use the output convention below.

Require both times>=0 with positive sum; return cycle sum, contact/sum and flight/sum.1

Input fieldMeaning and unitsAccepted input
contactSecondsContact SecondsRequired. Finite number; minimum 0.
flightSecondsFlight SecondsRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
cycleSecondsCycle SecondsRequired. Finite number.
contactDutyFactorcontactSeconds/(contactSeconds+flightSeconds); assumes these supplied phases exhaust the modeled cycle.Required. Finite number.
flightFractionFlight FractionRequired. Finite number.
json
{
  "input": {
    "contactSeconds": 0.2,
    "flightSeconds": 0.3
  },
  "output": {
    "cycleSeconds": 0.5,
    "contactDutyFactor": 0.4,
    "flightFraction": 0.6
  }
}

Limitations and assumptions

  • The two categories are assumed exhaustive and nonoverlapping. No running events, multiple-leg contact convention, efficiency, injury risk or actual gait is assessed.
  • 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

Use calibrated motion, force and timing records with a complete biomechanical model. Check coordinate frames, axis normalization and sampling limitations before interpreting local distances, moments or phase values as performance or clinical findings.

References

  1. Calculation and input contract: biomechanics/running-contact-flight-duty-factor — tool.io

Similar or alternative tools