Instructions to use siyuhsu/openpi_lab with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- LeRobot
How to use siyuhsu/openpi_lab with LeRobot:
- Notebooks
- Google Colab
- Kaggle
Model card: piper is a reference example, drop its eval numbers
Browse files
README.md
CHANGED
|
@@ -15,7 +15,12 @@ pipeline_tag: robotics
|
|
| 15 |
# openpi_lab β real-robot Οβ checkpoints + the datasets they were trained on
|
| 16 |
|
| 17 |
Two robots, each with its trained Οβ weights and the exact LeRobot dataset behind them.
|
| 18 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 19 |
|
| 20 |
```
|
| 21 |
g2/model/ Οβ, 30k steps g2/dataset/ 58 ep / 48,332 frames / 10 Hz
|
|
@@ -59,7 +64,7 @@ Each server publishes its deployment contract in the connect-time metadata
|
|
| 59 |
> Piper is 30 Hz. Actions are absolute (G2) or delta-from-start (Piper) joint targets;
|
| 60 |
> stepping G2's chunk at 30 Hz would execute it 3Γ too fast.
|
| 61 |
|
| 62 |
-
## Results
|
| 63 |
|
| 64 |
**G2** β offline replay against a live server, 120 frames / 12 episodes:
|
| 65 |
|
|
@@ -72,15 +77,9 @@ Each server publishes its deployment contract in the connect-time metadata
|
|
| 72 |
Validated on hardware in four stages β dry-run β ground-truth replay β policy-replay on
|
| 73 |
dataset observations β live closed loop β and completes the task in the last stage.
|
| 74 |
|
| 75 |
-
**Piper**
|
| 76 |
-
|
| 77 |
-
|
| 78 |
-
| model | in-dist | OOD-L1 | overall |
|
| 79 |
-
|---|---|---|---|
|
| 80 |
-
| baseline QwenOFT | 55% | 30% | 42.5% |
|
| 81 |
-
| ctxdemo QwenLAP | 80% | 75% | 77.5% |
|
| 82 |
-
| **Οβ** | **85%** | **80%** | **82.5%** |
|
| 83 |
-
| Οβ.β
| 80% | 60% | 70% |
|
| 84 |
|
| 85 |
## Things that will bite you
|
| 86 |
|
|
|
|
| 15 |
# openpi_lab β real-robot Οβ checkpoints + the datasets they were trained on
|
| 16 |
|
| 17 |
Two robots, each with its trained Οβ weights and the exact LeRobot dataset behind them.
|
| 18 |
+
|
| 19 |
+
**G2** is the main release β trained, validated on hardware in four stages, and it completes
|
| 20 |
+
its task closed-loop from live camera observations.
|
| 21 |
+
**Piper** is a **reference example**: a second robot with a different arm count, action space
|
| 22 |
+
and control rate, provided so the pipeline can be followed on a contrasting setup. It ships
|
| 23 |
+
the checkpoints and data only; no evaluation results are claimed for it.
|
| 24 |
|
| 25 |
```
|
| 26 |
g2/model/ Οβ, 30k steps g2/dataset/ 58 ep / 48,332 frames / 10 Hz
|
|
|
|
| 64 |
> Piper is 30 Hz. Actions are absolute (G2) or delta-from-start (Piper) joint targets;
|
| 65 |
> stepping G2's chunk at 30 Hz would execute it 3Γ too fast.
|
| 66 |
|
| 67 |
+
## Results (G2)
|
| 68 |
|
| 69 |
**G2** β offline replay against a live server, 120 frames / 12 episodes:
|
| 70 |
|
|
|
|
| 77 |
Validated on hardware in four stages β dry-run β ground-truth replay β policy-replay on
|
| 78 |
dataset observations β live closed loop β and completes the task in the last stage.
|
| 79 |
|
| 80 |
+
**Piper** is included as a **worked example**, not as a results claim: a second robot with a
|
| 81 |
+
different arm count, action space and control rate, so the pipeline can be compared against
|
| 82 |
+
something other than G2. No success-rate numbers are reported for it here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 83 |
|
| 84 |
## Things that will bite you
|
| 85 |
|