track_triangulate — DRIVE `balltrack` op

• Data kinds: table × any × any → table

• Call: import fullseye as fs; fs.ledger.track_triangulate(tracks, poses, Ks, n_frames: 'int') -> 'dict' (to call the implementation directly, import balltrack; balltrack.track_triangulate(tracks, poses, Ks, n_frames: 'int') -> 'dict'; from the registry, opsdrive.get("track_triangulate"))

Usage

Triangulates the per-camera trajectories (return values of ball_track) into a 3-D trajectory: {"frame", "p" (N, 3), "reproj_rms" (N,)} (only frames seen in 2 or more views).

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_ball_bounce — py -3.11 examples/poc_ball_bounce.py

• poc_table_tennis_spin — py -3.11 examples/poc_table_tennis_spin.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 (`balltrack`)

ball_detect · ball_track · kalman_ca · triangulate_dlt · bounce_detect · marker_direction · spin_from_markers · spin_from_marker_sequence

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

track_triangulate — DRIVE balltrack op