read_bvh — DRIVE `motion_io` 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.read_bvh(path) -> 'dict' (to call the implementation directly, import motionio; motionio.read_bvh(path) -> 'dict'; from the registry, opsdrive.get("read_bvh"))

Usage

Reads a BVH file and returns the skeleton and the world coordinates of the joints for all frames.

Returns:

names joint names (End Site is <親>_end), parents (root is −1), offsets (J, 3), positions (T, J, 3) world coordinates, frame_time [s], channels (names of the CHANNELS per joint), motion (T, C) raw values.

Raises:

ValueError: HIERARCHY / MOTION missing, unbalanced braces, the number of values in a frame differs from the total of CHANNELS.

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)

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

read_events · events_to_frames

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

read_bvh — DRIVE motion_io op