The pipeline at a glance
| Stage | Phone app | Web app |
|---|---|---|
| Record demonstrations | Record tab | Collect page |
| Configure & launch training | Train tab | Training page |
| Monitor runs | Runs tab | Running now card |
| Download & activate | Completed tab | automatic |
What goes in, what comes out
Input: A dataset of teleoperated demonstrations — each episode captures synchronized camera images (main + wrist), joint positions, joint velocities, and optionally wheel odometry at 30 Hz. We recommend at least 30 episodes of good quality — consistent start poses, smooth motions — and more diverse data almost always improves robustness (see the recording tips). (Curious what’s inside an episode file? See Dataset format.) Output: A PyTorch checkpoint that runs inference at 25 Hz, outputting 6 arm joint commands and 2 base velocity commands every 40 ms.When to use trained skills
Trained policies shine when the task needs visuomotor coordination — reaching, grasping, placing — especially when object positions vary between runs. For fixed, repeatable motions (a wave, a gesture), a replay skill is simpler: record once, play back. The full comparison lives in the skill selection guide.Next steps
Record a dataset
Collect high-quality demonstrations.
Train a policy
Configure and launch training on Innate’s cloud.
Deploy your skill
Download, activate, and run your trained model.
Dataset format
Understand what’s inside each episode file.

