What problem does it solve?
Recording human teleoperation demonstrations for robotics agentic environments requires coordinating environment configs, device-specific controls, and HDF5 recording paths, and mistakes like relative output paths or unsupported devices silently produce empty or orphaned datasets.
Core Features & Use Cases
- Teleop Recording Workflow: Launches
arena/run.sh --teleop for Isaac for Healthcare agentic environments with keyboard, SO-ARM leader, or VR devices, writing episodes to HDF5.
- Device Keybinding Surfacing: Extracts the device-specific keybinding table printed at startup from the teleop log so the human operator can actually drive the simulation.
- Recording Verification: Validates that the HDF5 file exists and that the log reports the requested number of successful episodes before claiming success.
- Use Case: A robotics engineer asks the agent to record 5 keyboard teleop demos for the scissor pick-and-place task; the skill resolves the i4h-workflows repo, creates a timestamped run directory, launches teleop, surfaces controls, and verifies the saved HDF5.
Quick Start
Ask your agent to record 5 keyboard teleop demos for the scissor pick-and-place task into an HDF5 dataset.