fivebar_reach_interval — DRIVE `puck` op

• Data kinds: table × scalar → table

• Call: import fullseye as fs; fs.ledger.fivebar_reach_interval(link: 'dict', x_line: 'float', *, n: 'int' = 801) -> 'dict' (to call the implementation directly, import puck; puck.fivebar_reach_interval(link: 'dict', x_line: 'float', *, n: 'int' = 801) -> 'dict'; from the registry, opsdrive.get("fivebar_reach_interval"))

Usage

The reachable y interval on the defense line x = x_line (on a grid, with an FK∘IK round trip). {"y_lo","y_hi","ok"}.

References (sample data, literature)

• 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.

Runnable examples (verified samples that actually call this op)

• poc_air_hockey_intercept — py -3.11 examples/poc_air_hockey_intercept.py

Ops the type connects to (they accept `table` as input)

course_layout · course_occupancy · course_contains · world_build · world_camera · world_move · lidar_scan · rss_longitudinal_same

Same category (`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).*

fivebar_reach_interval — DRIVE puck op