Notes from the build
Engineering write-ups from the people who wrote the code. What a policy sees, how the two control paths differ, why every limit is declared.
Declared, not assumed
The five contracts, the recording rule, the primitive layer and the admission check we build RobotGym against, and the anti-patterns we refuse.
Declared, not assumed
The five contracts, the recording rule, the primitive layer and the admission check we build RobotGym against, and the anti-patterns we refuse.
One photograph, one mug, one trial
Atom rebuilt a kitchen from one public photograph and an agent lifted the mug 8.2 cm in a single recorded trial, with every caveat written down.
Both clocks, every run
Physics pauses while the model thinks, so every RobotGym run records simulated and wall time separately and never reports one as the other.
Two doors into one controller
A language model can drive an arm one primitive per call or by writing a short program, and we ship both doors over one controller.
What a policy sees
Three RGB cameras, the measured gripper pose and camera calibration are what reaches a model in RobotGym, and we record exactly what it saw.
Why we build environments
RobotGym in plain facts, why we think the physical world is the slow part of robot development, and what we will write about here.
No posts match that yet.