Description
Return ideal ballistic ascent/descent times for unequal takeoff and landing heights.
Motion records combine sampled coordinates, periodic angles, event timing and signed work or impulse conventions. Local numerical differences and panels can be computed independently while actual event detection, full trajectories and physiological significance require complete measurements and analysis.
Return ideal ballistic ascent/descent times for unequal takeoff and landing heights.
When to use this tool
Use Jump Apex Flight Asymmetry Time Gap when checking the stated movement timing, angle, geometry, energy or panel convention.
How to use the tool and how it works
- Enter takeoffSpeed, gravity, landingBelowTakeoff. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read ascentTime, descentTime, totalFlight, timeGap. Use the output convention below.
Return ideal ballistic ascent/descent times for unequal takeoff and landing heights. Require takeoffSpeed >= 0, gravity > 0 and speed²+2*g*landingBelowTakeoff >= 0; ascent = speed/g, descent = sqrt(discriminant)/g, total and timeGap sum/subtract these.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| takeoffSpeed | Takeoff Speed | Required. Finite number; minimum 0. |
| gravity | Gravity | Required. Finite number; strictly above 0. |
| landingBelowTakeoff | Signed takeoff-height minus landing-height; positive for a lower landing. | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| ascentTime | Ascent Time | Required. Finite number. |
| descentTime | Descent Time | Required. Finite number. |
| totalFlight | Total Flight | Required. Finite number. |
| timeGap | Time Gap | Required. Finite number. |
{
"input": {
"takeoffSpeed": 4,
"gravity": 2,
"landingBelowTakeoff": 0
},
"output": {
"ascentTime": 2,
"descentTime": 2,
"totalFlight": 4,
"timeGap": 0
}
}Limitations and assumptions
- Positive landingBelowTakeoff means a lower landing surface; drag, body configuration, actual flight detection and safe landing are not modeled.
- 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 calibrated motion/force data and use an appropriate complete trajectory or dynamics analysis; interpret health and safe-loading implications with qualified professionals.
References
Similar or alternative tools
- Gait Phase Event Percentage Offset
Return an event's percentage through a supplied gait cycle.
- Stride Contact Double Count Term
Return union contact, flight duration and contact fraction.