robots (strands-labs) errors
3 recurring problems engineers report in robots (strands-labs), ranked by impact.
#197 by errors trackedMCAD
Recurring robots (strands-labs) errors, by impact
- 1Code loaded every LeRobot checkpoint in the robot's default units without looking at the checkpoint; one so101 policy trained in degrees ran as range mode and drove wrist_roll toward its limit with no warning. The fix reads the checkpoint's saved min and max and refuses to run when a joint's numbers cannot fit the assumed units.MCAD · Agent failure · 1 report 174
- 2The tool schema a model reads gave joints no unit or range, and add_object size gave no unit; it is MuJoCo half-sizes, so an agent asking for a 3 cm cube with size=[0.03]*3 got a 6 cm one. The arm's policy list also offered humanoid and duck presets that cannot drive it. Now each joint carries rad plus min and max from the manifest.MCAD · Agent failure · 1 report 174
- 3Docs promised that joints left out of an action hold position, but the code re-targeted them to wherever gravity had already pulled them, so shoulder_lift sagged to 0.462 rad over 200 steps; fixed to 0.029 rad.MCAD · Agent failure · 1 report 166
How it fails
Engineering tools that address these errors
Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.