Page 2 of 2

Re: Multi-task policies vs a library of specialist policies - which do production teams prefer?

Posted: Fri Aug 21, 2026 9:56 pm
by dchen
@betty.king Agreed, and I'd add: OpenVLA is a notable open-source VLA model - roughly 7 billion parameters, trained on hundreds of thousands of real-world robot demonstrations - and has been shown to outperform much larger closed models on some manipulation benchmarks, which says a lot about how much of VLA performance comes from data curation rather than raw scale. Zero Moment Point (ZMP) control keeps the robot's center of pressure within its support polygon and has been the classical backbone of bipedal walking for two decades - it's robust and well-understood, but tends to produce a somewhat conservative, flat-footed gait compared to more dynamic approaches.

Re: Multi-task policies vs a library of specialist policies - which do production teams prefer?

Posted: Sun Aug 23, 2026 6:22 pm
by dubois35
@dchen I'll believe the stronger version of that claim when it's independently verified. Domain randomization - varying friction, mass, sensor noise, and even visual textures during training - is one of the more reliable tricks for improving sim-to-real transfer, but overdoing it can make training slower to converge and produce overly conservative policies. Balance-recovery controllers are usually evaluated with push-recovery tests (a known, repeatable lateral push) in demos, but real-world robustness also depends on recovering from unstructured events like uneven flooring, unexpected contact, or a dropped payload shifting the center of mass mid-stride - which is a much harder, less demo-friendly test. Makes me wonder how this looks in another five years.

Re: Multi-task policies vs a library of specialist policies - which do production teams prefer?

Posted: Mon Aug 24, 2026 12:50 pm
by emma_whit
Speaking from personal experience here, Cross-embodiment training (training one policy across data from multiple different robot bodies) has shown some real transfer benefits for high-level behaviors, but low-level control (exact joint torques, timing) still tends to need embodiment-specific fine-tuning.

Re: Multi-task policies vs a library of specialist policies - which do production teams prefer?

Posted: Sat Aug 29, 2026 9:20 pm
by greta.carter
@emma_whit I can speak to this a bit. Isaac Lab (the successor to Isaac Gym) is widely used for large-scale parallel RL training thanks to GPU-accelerated physics, while MuJoCo is often used as a secondary 'sim-to-sim' validation step because its contact dynamics are generally considered more realistic than Isaac's, even though it trains slower at scale.