ORBIT (orbit-robotics) — RETIRED
This package is no longer maintained. Version 0.7.2 is its final release. All earlier versions have been yanked. Please do not build on it.
Why it was retired
ORBIT was sold on a claim that turned out to be false.
Versions through 0.8.0 stated that ORBIT's A–F dataset grades were "calibrated against 82 real training runs with known success rates," that ORBIT could predict whether training on your dataset would succeed, and that per-episode scoring could identify which demonstrations to keep or remove to improve a policy. Those claims are retracted.
They were retracted because we tested them ourselves and they did not hold:
- We trained 701 policies on controlled demonstration subsets — Diffusion Policy and ACT from scratch, SmolVLA and π₀.₅ fine-tuned — evaluated on PushT, two bimanual ALOHA tasks, and two ten-task LIBERO suites, every batch pre-registered.
- No score we built for a demonstration predicted whether keeping it improved the policy.
- Retraining on byte-identical data with only a different seed moved one LIBERO task's success rate by a standard deviation of 20.4 percentage points, and the ten-task average by 4.23. A calibration against 82 observational outcomes could not have measured what it claimed to, because the noise is the same size as the effect.
The mechanical parts of ORBIT were never the problem. Dead-joint detection, joint clipping, NaN and schema checks, temporal-alignment measurement and format conversion all report real, measurable properties of a dataset. What was wrong was the layer built on top of them that claimed to predict training outcomes.
What replaced it
The measurement programme that produced the retraction continues, and the honest part of the work — statistics for robot-policy evaluation, not predictions about datasets — moved to a separate package:
orbit-eval— noise floors, power analysis, correctly-paired comparisons, per-task release selection, and refusal logic that returns no number when a design cannot support one.
The full study is "Noise Floors and Non-Portable Value: What Robot Imitation Data Curation Can and Cannot Measure" (Lasne, 2026).
If you are still using this package
Pin orbit-robotics==0.7.2 if you depend on the loaders or the mechanical
checks; they work and they are honest. Do not rely on any grade, prediction,
"fit" score, sim2real transfer estimate, or episode-value output from any
version — those are the retracted surfaces.
Why this release exists at all
A package that shipped a false claim for over a year should not simply vanish.
Deleting the project would free the name for someone else and would read as
hiding. This release exists so that anyone who installs orbit-robotics — or
who finds it in an old requirements file — is told plainly what was wrong.
The research in this repository
This repo is also the measurement programme behind the retraction — the only replicate-retraining variance corpus in robot imitation learning, with the pre-registrations, the scored results, and the negative findings kept in.
RETRAIN_LOTTERY.md— the flagship result and the 8-retrain measurement protocolresearch/— pre-registered designs, scored results, freeze chainsexperiments/forecast/atlas.csv— the 16-regime variance atlaspaper/DRAFT.md— Noise Floors and Non-Portable Value
Author
Rahil Lasne (@Rahillasne) — ORBIT Research.
License
MIT (unchanged).
Metadata
Release files for orbit-robotics 0.7.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| orbit_robotics-0.7.2.tar.gz | 696.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| orbit_robotics-0.7.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 MB
Release files / orbit_robotics-0.7.2.tar.gz
| Download URL | orbit_robotics-0.7.2.tar.gz |
|---|---|
| Size | 696.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e09700477b9161406113b9e26ba882809a51b525d254a75c378ab54a27545ae
|
|
BLAKE2b-256 checksum How to use checksums |
43c36b03c4e11623e3e348e796dbcc44f4a8a36d271b468fa0db01e6e371b4c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Release files / orbit_robotics-0.7.2-py3-none-any.whl
| Download URL | orbit_robotics-0.7.2-py3-none-any.whl |
|---|---|
| Size | 634.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc0691dabd0ec2dbb92df059f1d70ff7ce1d408cc42efa11bf1fbc9075f04830
|
|
BLAKE2b-256 checksum How to use checksums |
6d0203d549e178f2cbb81be915f11c552618094b1a62972ac9da0ab62c312085
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.6
|
Security for orbit-robotics 0.7.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.