cup_catch_check — DRIVE `ball` op

• Data kinds: none → table (an op determined by its arguments alone — it takes no image or data input)

• Call: import fullseye as fs; fs.ledger.cup_catch_check(p_ball, v_ball, cup_center, cup_axis, cup_radius: 'float', ball_radius: 'float', v_rel_max: 'float' = 1.0) -> 'dict' (to call the implementation directly, import ballistics; ballistics.cup_catch_check(p_ball, v_ball, cup_center, cup_axis, cup_radius: 'float', ball_radius: 'float', v_rel_max: 'float' = 1.0) -> 'dict'; from the registry, opsdrive.get("cup_catch_check"))

Usage

Geometric test of whether the ball enters a cup (center, axis, radius): the ball's center lies within (cup_radius − ball_radius) of the cup axis, at a height within 1.5 times the ball radius from the cup surface (0 ≤ height ≤ 1.5 r), and the speed is ≤ v_rel_max. {"caught", "lateral", "height", "speed"}. ValueError if the cup is smaller than the ball.

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)

• (none yet)

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 (`ball`)

ball_params · impact_params · flight_vacuum · flight_ode · flight_simulate · flight_state_at · magnus_lift_coefficient · drag_coefficient_sphere

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

cup_catch_check — DRIVE ball op