puck_crossing_point — DRIVE `puck` op

• Data kinds: table × scalar → any

• Call: import fullseye as fs; fs.ledger.puck_crossing_point(pred: 'dict', x_line: 'float') (to call the implementation directly, import puck; puck.puck_crossing_point(pred: 'dict', x_line: 'float'); from the registry, opsdrive.get("puck_crossing_point"))

Usage

Time and place where the predicted path first crosses the defense line x = x_line (closed form: solves d(τ)·uₓ = required distance per segment).

> The detailed description below is the original text — the summary and the headings are translated.

返り値 {"t", "p", "v", "segment"}、横切らなければ None(fail-closed —— 止まる・ゴールに入る・時間切れ)。

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 `any` as input)

course_crank · course_s_curve · course_turnaround · course_slope · course_intersection · course_parallel_parking · course_crossing · course_road

Same category (`puck`)

puck_table · puck_wall_bounce · puck_slide_predict · puck_state_at · puck_mirror_path · puck_stop_distance · puck_camera · puck_pinhole_camera

*Provenance: puck.py — DRIVE operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*

puck_crossing_point — DRIVE puck op