puck op• Data kinds: signal × matrix × table → table
• Call: import fullseye as fs; fs.ledger.puck_restitution_from_wall(t, xy, table: 'dict', *, model: 'str' = 'coulomb') -> 'dict' (to call the implementation directly, import puck; puck.puck_restitution_from_wall(t, xy, table: 'dict', *, model: 'str' = 'coulomb') -> 'dict'; from the registry, opsdrive.get("puck_restitution_from_wall"))
e (normal) and kₜ (tangential) from a trajectory bouncing off a wall: splits it into before and after at the frame where the direction changes most, and extrapolates both sides to the collision time with puck_velocity_estimate. The wall is the one closest to the collision point. {"e", "kt", "t_hit", "wall", "n_before", "n_after", "v_in", "v_out"}. Fewer than 3 points on either side raises ValueError.
• 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_air_hockey_intercept — py -3.11 examples/poc_air_hockey_intercept.py
table as input)course_layout · course_occupancy · course_contains · world_build · world_camera · world_move · lidar_scan · rss_longitudinal_same
puck)puck_table · puck_wall_bounce · puck_slide_predict · puck_state_at · puck_crossing_point · puck_mirror_path · puck_stop_distance · puck_camera
*Provenance: puck.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.