fivebar_trajectory — DRIVE puck op

• Data kinds: signal × table × signal → matrix

• Call: import fullseye as fs; fs.ledger.fivebar_trajectory(q_now, plan: 'dict', t) -> 'np.ndarray' (to call the implementation directly, import puck; puck.fivebar_trajectory(q_now, plan: 'dict', t) -> 'np.ndarray'; from the registry, opsdrive.get("fivebar_trajectory"))

Usage

Joint trajectory q(t) of the plan: constant angular velocity from t_now over t_move, then stops on arrival. (N,2).

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 matrix as input)

world_camera · lidar_scan · relative_motion · foe_from_motion · flow_from_depth_motion · ttc_truth · world_materials · mesh_signed_volume

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).*

© 2026 Kazufumi Furuse — Fullseye operator documentation. Licensed under Apache-2.0.