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

Usage

> This operator's description has not been translated yet. The original text follows as it is.

イベントカメラのイベント列を読む(.txt / .csv / .npy / .npz)。

Returns:

`x・y(int64)、t(float64、ファイルの単位のまま)、p(int8、+1 / −1)、columns`

(どの列をどれと読んだか —— 推定したなら `guessed=True)、shape`(x・y の最大 + 1)。

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

read_bvh · 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_events — DRIVE motion_io op