Skip to content

Main content

Stride Normalized Time Percent

Normalize one sample time to an explicitly bounded stride interval, including both 0% and 100% endpoints.

Loading tool…

Description

Normalize a supplied sample time to a stride percentage.

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.

Normalize a supplied sample time to a stride percentage.

When to use this tool

Use Stride Normalized Time Percent when you already have sampleTimeSeconds, strideStartSeconds, strideEndSeconds and need to normalize a supplied sample time to a stride percentage.

How to use the tool and how it works

  1. Enter sampleTimeSeconds, strideStartSeconds, strideEndSeconds. 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 stridePercent. Use the output convention below.

Require end>start and sample within both inclusive endpoints; return 100*(sample-start)/(end-start).1

Input fieldMeaning and unitsAccepted input
sampleTimeSecondsSample Time SecondsRequired. Finite number.
strideStartSecondsStride Start SecondsRequired. Finite number.
strideEndSecondsStride End SecondsRequired. Finite number.
Output fieldInterpretationReturned shape
stridePercent100*(sampleTimeSeconds-strideStartSeconds)/(strideEndSeconds-strideStartSeconds), accepting 0 and 100. Rescale extreme clocks to preserve differences.Required. Finite number.
json
{
  "input": {
    "sampleTimeSeconds": 1.25,
    "strideStartSeconds": 1,
    "strideEndSeconds": 2
  },
  "output": {
    "stridePercent": 25
  }
}

Limitations and assumptions

  • Endpoints give nominal 0 and 100, not a periodic wrap. No gait event, stride validity or clinical conclusion is inferred. Rescale extreme timestamps to avoid intermediate overflow corrupting the percentage or causing rejection.
  • 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/stride-normalized-time-percent — tool.io

Similar or alternative tools