rerunlisted

# rerun The data-centric visualization tool for robium's ML/non-ROS side: a timeline-and-entity-path logging model (Python-first via `rerun-sdk`, `pip install rerun-sdk` / `uv add rerun-sdk`, currently at **0.34.1** as of 2026-07-10 — verified via direct fetch of `github.com/rerun-io/rerun`'s release page) for policy rollouts, LeRobot episode data, and arbitrary sensor streams that don't fit ROS message types. This skill deliberately stays thin: Rerun's own logging API surface (which archetype for which data shape, exact keyword arguments) changes across releases, and its own getting-started docs and example gallery are the actual source of truth — this skill's job is orientation (what the pieces are called, how the operating modes map to robium's local/remote needs) and the hand-off into `lerobot` for episode visualization, not a re-implementation of Rerun's own tutorials. ## When to use this skill - Logging and viewing ML rollouts, sensor streams, or embeddings/tensors outside ROS's message-type world; visualizing a LeRobot dataset episode. - The trigger phrases in the description: 'rerun', visualizing ML training/eval rollouts, LeRobot episode data, custom sensor pipelines outside ROS tooling. - Before writing any `rr.log(...)` call for a new data shape — check Rerun's own examples first (see Key directives); this skill's job is pointing there, not supplying every archetype from memory. - Cross-references — go to the sibling skill instead when the question is: