Page 2 of 2
Re: How do you debug a policy that works in sim but falls immediately on hardware?
Posted: Thu Sep 11, 2025 8:14 am
by ivan22
@zoeanderson This matches something I went through recently.
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: How do you debug a policy that works in sim but falls immediately on hardware?
Posted: Sun Sep 14, 2025 3:41 am
by barbara.jones
@ivan22 Genuinely curious -
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: How do you debug a policy that works in sim but falls immediately on hardware?
Posted: Mon Sep 15, 2025 5:42 pm
by karen_kim
@barbara.jones This is a great summary, thanks.
Physical Intelligence's pi0 pairs a smaller pretrained vision-language backbone with a separate flow-matching 'action expert' module, which is one way to get fast, high-frequency action output without needing the whole giant language model to run at control-loop speed. 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.
Re: How do you debug a policy that works in sim but falls immediately on hardware?
Posted: Fri Sep 26, 2025 6:09 pm
by rao91
I'd take that specific number with a grain of salt, honestly.
Whole-body control (WBC) formulates locomotion and manipulation as a single optimization problem across all joints simultaneously, respecting contact constraints and task priorities - it's more general than ZMP-only approaches but is computationally heavier and harder to tune. Model predictive control (MPC) is still very much alive in production humanoids, often working alongside or underneath learned policies - MPC handles short-horizon dynamically-consistent trajectory optimization while learned components handle perception, task-level decisions, or recovery behaviors that are hard to hand-model.
Re: How do you debug a policy that works in sim but falls immediately on hardware?
Posted: Mon Oct 06, 2025 3:12 pm
by kim37
Slight correction, though the overall point stands:
A lot of what reads as 'full autonomy' in public demos is closer to a mix of scripted state machines, teleoperation for the hardest sub-tasks, and autonomous execution for the easier, well-rehearsed parts - transparency about this mix varies a lot between companies.
Re: How do you debug a policy that works in sim but falls immediately on hardware?
Posted: Thu Oct 09, 2025 1:46 pm
by erik_novi
@kim37 Related question -
Diffusion policies model the distribution of possible actions and sample from it, which handles multimodal manipulation tasks (multiple valid ways to grasp something) more naturally than a single deterministic action output, at the cost of slower inference.
Re: How do you debug a policy that works in sim but falls immediately on hardware?
Posted: Mon Oct 13, 2025 2:21 am
by kim37
Same conclusion I've come to. Also worth noting:
Model predictive control (MPC) is still very much alive in production humanoids, often working alongside or underneath learned policies - MPC handles short-horizon dynamically-consistent trajectory optimization while learned components handle perception, task-level decisions, or recovery behaviors that are hard to hand-model.
Re: How do you debug a policy that works in sim but falls immediately on hardware?
Posted: Sat Oct 25, 2025 12:56 am
by gimbalmar65
@kim37 +1 to this. Worth adding:
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.