philippguevorguian commited on
Commit
408c0f9
·
verified ·
1 Parent(s): d15b2dd

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +149 -1
README.md CHANGED
@@ -1,3 +1,151 @@
1
  ---
2
- license: cc-by-nc-4.0
 
 
 
 
 
 
3
  ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
  ---
2
+ language:
3
+ - en
4
+ tags:
5
+ - robotics
6
+ - vision-language-model
7
+ - robot-learning
8
+ - embodied-ai
9
  ---
10
+
11
+ <!-- Add the final license and pipeline_tag before publication. -->
12
+
13
+ # Isaac 0.5 by Perceptron
14
+
15
+ Introducing Isaac 0.5, our open foundation model for robot learning.
16
+
17
+ Isaac 0.5 brings multimodal video understanding, embodied reasoning, spatial grounding, task-progress estimation, and robot control into one 36-billion-parameter sparse model. It reads images, video, language instructions, robot state, and previous actions, then produces text, normalized coordinates, task-state outputs, or robot actions.
18
+
19
+ To our knowledge, Isaac 0.5 is the first open model operating at the frontier of multimodal video understanding, embodied reasoning, and robot control.
20
+
21
+ **[Read the paper](REPORT LINK) · [Download the weights](HUGGING FACE LINK) · [View the code](GITHUB LINK)**
22
+
23
+ ## Extending the frontier of open robot learning
24
+
25
+ Isaac 0.5 is trained on more than 35 robot systems, 100,000 hours of robot experience, one million hours of general video, and three trillion multimodal tokens. Video understanding, spatial grounding, task progress, future-percept prediction, and robot action are co-trained from the beginning on one shared backbone.
26
+
27
+ Teams can fine-tune Isaac as a robot policy or use its visual outputs inside a planner, controller, or data engine. The release includes base and action checkpoints, action-training and inference code, LeRobot integration, a reference policy server, evaluation tools, and the manifests needed to reproduce the model's data and checkpoint interfaces.
28
+
29
+ ## What's new in Isaac 0.5
30
+
31
+ - **A scaling law for video and robot data:** Isaac measures how general video, egocentric video, UMI data, and teleoperation data trade off as training scales.
32
+ - **Semantic world modeling:** The model predicts compact future percepts that capture task-relevant changes such as object motion, contact, grasp state, spatial relationships, and task progress.
33
+ - **Unified perception, reasoning, and control:** One shared sparse backbone supports video understanding, pointing, tracking, task-state estimation, and robot action generation.
34
+ - **Continuous and discrete action interfaces:** Isaac supports continuous control through a dedicated Flow expert and diffusion transformer, plus discrete control through a 2,048-token FAST action vocabulary.
35
+ - **Real-time closed-loop control:** Isaac predicts the next action chunk while the current chunk is still executing, using the latest observation and previously issued commands.
36
+ - **Open training and deployment stack:** The release includes model weights, training code, inference code, LeRobot integration, a reference policy server, evaluation code, and reproduction manifests.
37
+
38
+ ## A scaling law for video and robot experience
39
+
40
+ Isaac 0.5 establishes a scaling law for choosing the mix of broad video and expensive robot demonstrations.
41
+
42
+ We trained Isaac across a grid of general-video, egocentric-video, UMI, and teleoperation mixtures, then measured action-prediction loss on robot trajectories held out from training. The resulting contours map data mixtures that reach the same held-out action loss.
43
+
44
+ At a target action loss of 2.50:
45
+
46
+ - a model trained on 1,000 hours of general video requires about 5,900 hours of teleoperation;
47
+ - a model trained on one million hours of general video requires about 28 hours of teleoperation.
48
+
49
+ This is a 210× reduction in required teleoperation. The result gives teams a practical way to decide when another order of magnitude of video is valuable and when collecting more robot experience matters more.
50
+
51
+ General video contributes broad coverage of objects, activities, environments, and tasks. Egocentric video adds close-up, task-relevant views of hands, motion, and contact. UMI data connects visual knowledge to manipulation. Teleoperation grounds that knowledge in a specific embodiment and action space. Isaac trains on these sources together so each shapes the representation used for control.
52
+
53
+ > **[FIGURE: Scaling-law contours with teleoperation on the horizontal axis and general video on the vertical axis]**
54
+
55
+ ## Semantic world modeling
56
+
57
+ Isaac learns from video by predicting future percepts: compact representations of changes that matter for a task. These include which object moved, how objects are related, whether contact occurred, whether a grasp held, and which stage of a task has been reached.
58
+
59
+ Targets are derived from later frames, including general video without robot action labels. Given observations through time *t*, Isaac predicts the percept at a later time *t + Δ*:
60
+
61
+ $$
62
+ L_{\text{percept}} = \mathbb{E}\left[\ell\left(g_\theta(o_{\leq t}), z_{t+\Delta}\right)\right]
63
+ $$
64
+
65
+ Here, $o_{\leq t}$ is the observation history and $z_{t+\Delta}$ is the future percept. This objective trains the same backbone Isaac uses to produce actions.
66
+
67
+ ## Model architecture
68
+
69
+ Isaac uses a 36B Qwen-family vision-language backbone with sparse experts. Text, vision, time, robot state, and action history enter one shared sequence.
70
+
71
+ The autoregressive interface produces text, normalized coordinates, task-state outputs, and discrete actions. Discrete control uses a separate vocabulary of 2,048 FAST action tokens. For continuous control, backbone states condition a dedicated Flow expert and 36-block diffusion transformer that generates an action chunk.
72
+
73
+ Each mixture-of-experts layer gives every token access to 256 learned experts and a null route. A token may use zero to eight routed experts, while a shared expert and residual path remain active. This lets Isaac vary routed compute across visual, language, state, and action tokens. The checkpoint contains 36B parameters in total.
74
+
75
+ > **[FIGURE: Isaac 0.5 architecture and action interfaces]**
76
+
77
+ ## Training system
78
+
79
+ mHarmony, our typed input compiler, converts every data source into one stream of text, vision, time, state, and action events while preserving provenance. Isaac uses the same format in training and serving.
80
+
81
+ Training examples are packed into 16,384-token sequences with 2% padding across the full mixture. Video is decoded outside the training process so corrupted files can restart without interrupting a run. Visual blocks are distributed across workers before encoding to prevent one long video from slowing an entire step. The released hyper-sparse configuration reaches 24% model FLOP utilization.
82
+
83
+ ## Performance benchmarks
84
+
85
+ We evaluate the same Isaac checkpoints across multimodal video understanding, spatial grounding, held-out action prediction, and closed-loop robot control.
86
+
87
+ - **Video understanding:** [TK-VIDEO RESULT] on [TK-VIDEO EVALUATION]
88
+ - **Pointing:** [TK-POINTING RESULT] on [TK-POINTING EVALUATION]
89
+ - **Tracking:** [TK-TRACKING RESULT] on [TK-TRACKING EVALUATION]
90
+ - **Closed-loop control:** [TK-HEADLINE-RESULT] across [TK-TASKS] standard manipulation tasks under the released protocol
91
+
92
+ > **[FIGURE: Video understanding, pointing, tracking, task-progress, and future-percept results]**
93
+
94
+ > **[FIGURE: Closed-loop task success and progress by robot and task family, with trial counts and confidence intervals]**
95
+
96
+ ## Robot-control evaluation
97
+
98
+ Our YAM-native simulation and data engine is built around MolmoSpaces. It spans five hardware revisions and four grippers, producing 20 arm-and-gripper configurations with one common observation and action interface. Reach, joint limits, contact geometry, force limits, calibration, and collision envelopes remain specific to each configuration.
99
+
100
+ The current zero-shot suite contains 42 tasks across nine manipulation families, including object interaction, spatial rearrangement, articulation, insertion, tool use, and multistage tasks. Compound tasks run continuously across subgoals, and grasp outcomes require valid contact with a stable object.
101
+
102
+ We vary placement, lighting, instruction wording, and distractors while keeping each task and scorer fixed. Alongside task success, we report completion time, path length, jerk, collisions, slips, controller saturation, and safety interventions. Timeouts, invalid actions, dropped observations, and controller faults count as failures.
103
+
104
+ Simulation provides repeatable coverage. Physical trials measure deployment directly. Where possible, we pair both and hold out complete robot families to measure transfer before hardware-specific adaptation. LIBERO and SIMPLER provide additional standardized comparisons under matched observations, instructions, action horizons, controllers, and serving paths.
105
+
106
+ > **[MEDIA: Evaluation gallery filtered by task, robot, condition, and outcome, including failures, perturbations, and recoveries]**
107
+
108
+ ## Where Isaac sits among open models
109
+
110
+ | Model | Robot training scope | Obs. steps | RTC-trained | Prev. actions | Mistake modeling | Non-robot video | Flow expert | Open source |
111
+ | :---- | :---- | :---- | :---- | :---- | :---- | :---- | :---- | :---- |
112
+ | **Isaac 0.5** | 35 embodiments | 1–3 | Yes | Yes | Yes | Yes | Yes | Yes |
113
+ | π0.7 | Not reported | ≤6 / camera | Yes | No | Yes | Yes | Yes | No |
114
+ | π0.5 | ~7 robots | 1 | No | No | No | Yes | Yes | Yes |
115
+ | Qwen-VLA | ~10 robots | 1+ | No | No | No | Yes | Yes | No |
116
+ | LingBot-VLA | 9 robots | 1 | No | No | No | No | Yes | Yes |
117
+ | MolmoAct2 | ~5 embodiments | 1 | No | No | No | Yes | Yes | Yes |
118
+ | SmolVLA | 1 embodiment | 1 | No | No | No | No | Yes | Yes |
119
+ | Octo | 25 datasets | 2 | No | No | No | No | No | Yes |
120
+ | OpenVLA | Not reported | 1 | No | No | No | No | No | Yes |
121
+
122
+ ## Building with Isaac in the open
123
+
124
+ Isaac 0.5 can be fine-tuned on new demonstrations, used as a visual backbone inside a larger embodied system, or deployed as an action policy through LeRobot or our reference server.
125
+
126
+ The release includes:
127
+
128
+ - base and action-capable weights;
129
+ - continuous Flow and discrete FAST action configurations;
130
+ - action training and fine-tuning code;
131
+ - text, pointing, tracking, and task-state output schemas;
132
+ - LeRobot integration and a reference policy server;
133
+ - evaluation code, task definitions, and rollout manifests;
134
+ - checkpoint, data, and model-I/O manifests;
135
+ - the technical report, model card, and reproduction guide.
136
+
137
+ ### Usage
138
+
139
+ > **[TODO: Add final installation command and checkpoint-specific inference example.]**
140
+
141
+ ## Resources
142
+
143
+ - **Weights:** [Hugging Face](HUGGING FACE LINK)
144
+ - **Code:** [GitHub](GITHUB LINK)
145
+ - **Technical report:** [Read the paper](REPORT LINK)
146
+ - **Results and rollouts:** [View results](RESULTS LINK)
147
+ - **Reproduction guide:** [View guide](REPRODUCTION GUIDE LINK)
148
+
149
+ Open models are essential to robotics progress. We are releasing Isaac 0.5 with its weights, code, interfaces, benchmarks, and manifests so others can inspect, reproduce, and extend the work.
150
+
151
+ For help deploying Isaac on your infrastructure, contact [sales@perceptron.inc](mailto:sales@perceptron.inc).