humanoid_clip_mesh — DRIVE `humanoid` op

• Data kinds: table → table

• Call: import fullseye as fs; fs.ledger.humanoid_clip_mesh(clip: 'dict', distance: 'float') -> 'dict' (to call the implementation directly, import drivehumanoid; drivehumanoid.humanoid_clip_mesh(clip: 'dict', distance: 'float') -> 'dict'; from the registry, opsdrive.get("humanoid_clip_mesh"))

Usage

Mesh at walked distance distance [m] ({"V","F","color","label","dims"}, origin = directly below the hips, +x = forward).

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

1 周期で cycle_length 進む。コマの間は頂点を線形に補間する(面の組み方は全コマ同じ)。形は腰の真下が原点のままなので、置く位置を distance だけ進めれば支持脚は地面で止まって見える(コマの位相は advance で歩いた距離に合わせてある)。★2026-10-03: 最初の版は周期内の前進をここでも差し引き、置く側と 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_driving_humanoids — py -3.11 examples/poc_driving_humanoids.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 (`humanoid`)

world_pose_humanoid · humanoid_impostors · world_camera_impostors

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

humanoid_clip_mesh — DRIVE humanoid op