ballworld 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.ball_mesh(radius: 'float' = 0.02, subdiv: 'int' = 3, color=(1.0, 0.55, 0.05), marker_dir=(0.0, 0.0, 1.0), marker_angle: 'float' = 25.0, marker_color=(0.05, 0.05, 0.05), markers=None) -> 'dict' (to call the implementation directly, import ballworld; ballworld.ball_mesh(radius: 'float' = 0.02, subdiv: 'int' = 3, color=(1.0, 0.55, 0.05), marker_dir=(0.0, 0.0, 1.0), marker_angle: 'float' = 25.0, marker_color=(0.05, 0.05, 0.05), markers=None) -> 'dict'; from the registry, opsdrive.get("ball_mesh"))
> This operator's description has not been translated yet. The original text follows as it is.
球のメッシュ(原点 = 中心)と模様。`markers` = [(dir, angle_deg), …] で複数の模様(None なら marker_dir 1 つ)。
返り値 `{"V", "F", "color" (M,3), "label" (M,) (23 or 24), "radius", "markers": [単位ベクトル …]}`。
• 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.
• poc_ball_bounce — py -3.11 examples/poc_ball_bounce.py
• poc_table_tennis_bounce — py -3.11 examples/poc_table_tennis_bounce.py
• poc_table_tennis_spin — py -3.11 examples/poc_table_tennis_spin.py
table as input)course_layout · course_occupancy · course_contains · world_build · world_camera · world_move · lidar_scan · rss_longitudinal_same
ballworld)table_params · table_world · add_ball · ball_set_pose · rotation_from_omega · camera_rig · ball_truth · icosphere
*Provenance: ballworld.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.