ball op• Data kinds: none → signal (an op determined by its arguments alone — it takes no image or data input)
• Call: import fullseye as fs; fs.ledger.apex_sequence(h0: 'float', e: 'float', n: 'int') -> 'np.ndarray' (to call the implementation directly, import ballistics; ballistics.apex_sequence(h0: 'float', e: 'float', n: 'int') -> 'np.ndarray'; from the registry, opsdrive.get("apex_sequence"))
Apex heights h_k = e^{2k} h₀ (k = 0..n) of a drop-and-bounce sequence.
• Sample-data catalog (download URLs / licences) — 2-D uses skimage.data (BSD/public domain) plus synthetic images; 3-D lists download URLs for real data sources (Stanford, PDS, …).
• Operator provenance and references — the sources of the research/methods this op family came from.
• The canonical algorithm (author, year) and its uses are named in the family usage guide above.
• poc_ball_bounce — py -3.11 examples/poc_ball_bounce.py
signal as input)flight_vacuum · magnus_lift_coefficient · drag_coefficient_sphere · restitution_from_apexes · restitution_from_intervals · fit_parabola · flight_fit · fit_aero
ball)ball_params · impact_params · flight_vacuum · flight_ode · flight_simulate · flight_state_at · magnus_lift_coefficient · drag_coefficient_sphere
*Provenance: ballistics.py — DRIVE operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*
© 2026 Kazufumi Furuse — Fullseye operator documentation. Licensed under Apache-2.0.