Reward Design and the MPC Debate
LLM-written rewards and curricula; where classical trajectory optimization still wins.
- Last reviewed
- Reading time
- 17 min
- Citations
- 17
Every module so far in this domain assumed someone had already written the objective. The parallel-training module showed thousands of robots collecting reward in lockstep; the sim-to-real module showed how to make the resulting policy survive contact with hardware. This module is about where the reward comes from, and it closes with the argument the whole domain has been circling: whether you need a learned policy at all, when classical trajectory optimization keeps taking back ground.
Twelve weighted terms sit on the illustrative behavior preview below. Its weights, per-term magnitudes and freeze/prance/chatter categories are teaching choices, not the paper's nine-term objective or a runnable legged_gym configuration. Drag the controls to explore this toy weighted sum.
This local teaching model uses twelve authored terms, weights and fixed per-term magnitudes. Its signed weighted total is dimensionless per step, not a measured reward. Freeze, prance and chatter are chosen classification rules and drawn poses, not trained policies, measured control frequencies or actuator-damage predictions.
Local teaching model: twelve illustrative terms and weights, not the paper reward or a source configuration. No policy is trained here.
balanced gait. This toy selects a balanced trot when none of its three failure-category rules fires. The motion is drawn from a fixed gait pattern, not an optimized policy.
The 12 weighted reward terms give an illustrative total of -5.52 per step, and the preview is a balanced trot: neither torque 0.8 nor air time 0.6 clears the 2.5 attractor bar and 2x the 1.0 velocity-tracking weight together, so the chosen rule draws a trot instead of freezing, prancing, or chattering.
Current reward-weight attractor
- attractor
- balanced trot
- total
- -5.52 / step
- torque
- 0.8
- air time
- 0.6
- action-rate
- 0.8
The reward is the product
Rudin and colleagues define a weighted sum of nine reward terms in the paper, including feet air time; gait-independent means that the reward does not prescribe a gait schedule, not that air time is absent Rudin 2021. The separate legged_gym initial commit (October 2021, pinned by commit hash in the cited record's audit trail) declares fifteen entries in LeggedRobotCfg.rewards.scales, of which nine are nonzero: linear- and angular-velocity tracking, vertical linear velocity, roll/pitch angular velocity, joint torque, joint acceleration, feet air time, collisions, and action rate. _prepare_reward_function removes zero scales and multiplies the remaining scales by the environment time step. The base class implements nineteen reward functions, including joint-limit and contact-force functions, but those definitions do not make them active terms in this config. Its zero-valued feet_stumble entry does not even match the _reward_stumble function name. That function penalizes feet hitting vertical surfaces, not foot slip; the air-time function rewards long steps on first contact and requires a planar-command norm above 0.1. These are properties of this pinned base code, not a universal or production reward recipe Rudin 2021.
The preview maps weight settings to three illustrative categories: freeze, prance, and chatter. Those classifications and the displayed motion are outputs of this local teaching model, not policies trained in the cited simulator. Rudin and colleagues report different observed artifacts, including a dragging leg and unusually high or low base height, and describe tuning reward weights before transferring their policy to hardware Rudin 2021.
Rudin and colleagues use an adaptive learning rate in their PPO implementation, based on the KL divergence between the updated and previous policies. Table 3 gives a desired KL of 0.01; Algorithm 1 lowers the learning rate when KL exceeds twice the target and raises it when KL is below half the target, within stated learning-rate limits Rudin 2021. This mechanism does not establish that reward retuning is stable.
Three answers to weight tuning
The field has responded to the tuning burden along three distinct lines, and they should not be conflated.
The first approach reduces reward tuning by adding explicit constraints. Yunho Kim and colleagues use three reward terms for command tracking, joint torque, and action smoothness, alongside 11 constraints: six probabilistic and five average constraints. They trained separate controllers in simulation for Raibo, Mini-cheetah, Hound, ANYmal B, ANYmal C, Unitree Go1, and Atlas; hardware deployment was on Raibo and Mini-cheetah. For transfer between robots, they adjusted only the torque-reward coefficient among the three reward coefficients, after choosing a reference-robot coefficient by trial and error. Constraint limits and other robot-specific settings still changed. Their IPO-based optimizer uses TRPO and adaptive constraint thresholds; these probabilistic and average limits are not hard bounds enforced at every training step Kim 2024.
Dohyeong Kim and colleagues take a different constrained multi-objective approach to acrobatics. They manually divide tasks into stages and define separate reward and cost functions for each stage. Their back-flip example has five stages, Stand-Sit-Jump-Air-Land, with five reward functions and five cost functions. CoMOPPO combines normalized reward and cost advantages in a PPO update; stage-transition rules, cost thresholds, objective preferences, and optimization hyperparameters still need to be specified. The reported simulation tasks use Unitree Go1 and H1; the real-world demonstrations use Go1 for back-flips, side-rolls, and two-hand walking Kim 2024.
The second approach adapts reward weights during training. Srisuchinnawong and Manoonpong’s ROGER uses estimates of nonnegative penalty magnitudes relative to selected constraint thresholds to reduce the primary-reward gain and increase penalty gains near the thresholds, reversing that balance farther away. The penalties are subtracted from the primary reward, not added as bonuses. This is not a universal constraint-satisfaction guarantee: the revised paper reports an exploration-induced violation in its simulated quadruped experiment and explicitly limits its safety claims to assumptions about zero-penalty optimality and gentle system and learning dynamics Srisuchinnawong 2025.
The third outsources the writing to a language model. That one deserves its own section.
Eureka: the reward as code under evolution
Eureka searches over reward code; PPO learns the policies. In the default experiment, GPT-4 receives a task description and environment observation code with the existing reward excluded, then proposes Python reward functions. Candidate rewards train PPO policies in Isaac Gym. Selection uses a separate task-fitness function, while scalar snapshots of that fitness and each reward component provide feedback for the next reward-code mutation. The implementation trims the context to the relevant observation code and the last reward/reflection pair.
Source: Ma 2024.
The evaluation covers 29 simulated tasks: nine original Isaac Gym environments and 20 Dexterity tasks, spanning 10 robot morphologies. The paper's headline reports 83% of tasks and 52% average normalized improvement over human-expert rewards; its detailed results describe matching or exceeding the human reward on all nine Isaac tasks and 15 of the 20 Dexterity tasks, not strict wins everywhere. The human baseline is each benchmark's original shaped reward Ma 2024.
Search uses five independent runs, five iterations per run and 16 candidate rewards per iteration. The reported comparison uses the best reward across search restarts; the separate reward-reflection ablation instead averages restarts. Intermediate rewards receive one PPO run; final rewards receive five, scored by the average of the maximum task fitness over ten fixed-interval checkpoints Ma 2024.
The human-normalized score is (Method - Sparse) / abs(Human - Sparse); for the headline average across all 29 tasks, Appendix D adjusts each score to lie in [0, 3]. The 52% headline is not a 52-percentage-point increase in success rate Ma 2024.
The panel below is a scripted teaching example of the Eureka loop, not a recorded Eureka or PPO experiment. All three generations, reward code, statistics, fitness scores and reflections are authored fixtures. The sequence illustrates sprinting and falling, standing still, then tracking a command; clicking advances the script without training a policy or calling a language model.
Task: quadruped forward walking at 1.0 m/s
Proposed reward code
def reward(obs, act):
# task: walk forward at 1.0 m/s
return obs.base_lin_vel_xScripted reward statistics
- episode length
- 0.4 s
- base_vel_x (mean)
- 2.8 m/s
- episodes ending in a fall
- 100%
- time at target speed
- 3%
- Task fitness
- 0.31
Scripted reflection on the statistics
Fitness is low. base_lin_vel_x spikes to 2.8 m/s, nearly three times the command, then every episode terminates in under half a second. The reward pays for speed and never for survival, so sprinting into a fall is the optimal policy. Next generation: add a survival bonus and make falls expensive.
Scripted replay of the Eureka loop (propose reward code, train, select on fitness, reflect on reward statistics, mutate). The code, statistics, fitness scores, and reflections are authored teaching data, not a recording of a real run.
The limitations are structural, and the 2026 literature treats them as open. Eureka needs a fitness function, which is itself a reward-specification problem one level up. It needs cheap parallel training per candidate, so it inherits the locomotion-manipulation asymmetry from the first module in this domain. And LLM-written rewards are prone to specification gaming that only shows up on hardware; nobody has published a systematic study of whether they induce more or less contact-solver exploitation than human-written ones.
Lee and colleagues' Reward Design Agent (RDA) compares against a matched Eureka implementation with the same GPT-5 backbone, task instructions, and training budget. That baseline reflects on numerical reward-component statistics; RDA additionally analyzes rendered trajectories together with reward logs, scores subtasks, summarizes failures, and revises both the subtask descriptions and reward code. Its experiments cover 12 ManiSkill tabletop tasks and four HumanoidBench whole-body tasks, using SAC with SimbaV2. On HumanoidBench, the paper reports higher VLM-rated alignment for RDA (0.70 versus Eureka's 0.47), with RDA success at 0.42 and slightly below Eureka's: reaching the goal and following the intended behavior are different measurements. The package example illustrates the distinction, contrasting throwing or torso-pushing with the requested hand-contact pushing. Reported alignment comes from GPT-4.1 ratings of five rollout videos, each queried four times, not a guarantee of instruction correctness; the authors identify costly RL training, imperfect fine-grained visual reasoning, and conflicting catch-versus-throw rewards in basketball as limitations Lee 2026. Eureka itself already noted that task fitness need not match human intent and demonstrated an extension using human-written reward reflection, so the comparison concerns RDA's automated visual diagnostics, not the discovery of a previously unacknowledged limitation Ma 2024.
Curriculum: staying on the difficulty frontier
Reward shaping decides what to optimize; curriculum decides in what order the policy is allowed to see difficulty. Three mechanisms dominate, and they are different enough to keep separate.
Terrain curriculum is the game-inspired scheme from the massively parallel walking work: robots that succeed on a terrain tile get promoted to a harder one, robots that fail get demoted, and thousands of parallel robots make the difficulty frontier measurable rather than guessed Rudin 2021. Automatic Domain Randomization widens the randomization distribution itself as success crosses a threshold, an idea from OpenAI's dexterous hand work that now ships in Isaac Lab as a configurable curriculum OpenAI 2019 NVIDIA 2025.
For population-based training, Isaac Lab v1 describes DexPBT workers running independent RL processes with their own hyperparameters; strong workers replace weak workers’ weights and hyperparameters. Its RL-Games implementation reproduces a 6D reposing task using eight workers with one to two GPUs each, converging in approximately 16 hours on NVIDIA OVX L40 hardware
Source: NVIDIA 2025.
Notice what all three assume: cheap, dense, parallel evaluation. Curriculum is a dividend of the throughput covered in the parallel-sim module, and it is one more reason the same machinery does not transfer to manipulation, where the MDP is not cheaply simulatable.
The classical baseline got stronger
Everything above is about making learning work. The learning-vs-model-based debate asks whether it had to. The classical stack for legged control is a hierarchy: a footstep and contact planner, an MPC layer optimizing a reduced-order model, and a whole-body QP tracking the MPC output against full rigid-body dynamics, friction cones, and actuator limits. The reduced-order model in the middle layer existed because full-order MPC was assumed too slow to run online. Whole-body MPC work describes the tradition it replaces as the "model hierarchies commonly seen in traditional model-based MPC", built on "reduced-order models and hierarchical control approaches" Zhang 2026.
Zhang and colleagues' March 2026 revision, listed on arXiv as "to appear at ICRA 2026", demonstrates a MuJoCo-based iLQR controller on Unitree Go1 and Go2 quadrupeds, a Go1 walking on its hind legs and transitioning to a handstand, and an H1 humanoid tracking a trotting gait. It uses forward finite differences for dynamics and residual Jacobians, analytical norm derivatives, approximate cost Hessians, and one warm-started iLQR update per solve without waiting for convergence. Joint-angle targets feed low-level PD control, which is also included in the planning model. On a desktop with a 20-core, 13th-generation Intel i9, the reported iLQR and intervening TV-LQR feedback rates are approximately 50 Hz and 300 Hz; the default horizon is 0.35 s with 100-Hz model discretization. H1 uses a 0.5-s horizon, ten active joint actuators, and four foot contact points after disabling upper-body DoFs with unreliable relative encoders and collision checking elsewhere on the body. These are laboratory experiments using 100-Hz OptiTrack measurements fused with 500-Hz joint measurements, not an onboard-only deployment. The authors' phrase "few sim-to-real considerations" includes consequential setup choices: increasing MuJoCo's impratio from 1 to 100 to reduce slipping roughly doubled a quadruped iteration from 10 to 20 ms on a separate 12th-generation i7 test. An eight-second H1 feedback comparison also records a gantry-assisted recovery in the trial without TV-LQR feedback. The paper presents an accessible model-based baseline, while identifying motion-capture dependence, actuation/contact system identification, contact-mode exploration, and long-horizon numerical behavior as limitations. It does not establish calibration-free operation, zero total engineering cost, or blanket superiority over learned control Zhang 2026.
The structural point is deeper than one paper. MPC has no sim-to-real gap in the RL sense: it re-solves against the measured state at every control step, so model error is rejected by feedback instead of being baked into weights. From this angle, domain randomization is an expensive workaround for not closing the loop on the model. Boston Dynamics describes a source-specific hybrid arrangement, rather than a choice between learning and models: its 2024 Spot account retains the model-based locomotion controller while a learned policy removes the need to evaluate multiple MPC instances in parallel Dynamics 2024. Its August 2025 Atlas/TRI report concerns language-conditioned policies for whole-body manipulation, including locomotion; the teleoperation system is built on MPC, and the learned policies use that same robot control interface Cousineau 2025. These two reports describe different robots and policy generations, not replacement of either robot's entire controls stack.
The debate, steelmanned
The honest comparison runs on the axes where the two stacks actually differ. The table states each; the interactive below it shows what the difference looks like when the ground stops being what either controller expected.
| Axis | Model-based (MPC / whole-body QP) | Learned (sim-RL policy) |
|---|---|---|
| model error | Corrected online: every control step re-solves against the measured state, so model bias is rejected by feedback. | Must be anticipated at training time with domain randomization or system ID; the residual error is baked into the weights. |
| constraints | Explicit and enforced: friction cones and torque limits are hard constraints in the optimization. | Implicit: violations are discouraged by reward penalties, with no guarantee they hold. |
| deploy-time compute | High: a trajectory optimization problem is solved at every control step. | Low: a single network forward pass. |
| contact-mode discovery | Hard: contact schedules are combinatorial, usually given or found by contact-implicit methods. | Emergent from exploration across thousands of parallel environments. |
| rich perception | Awkward: there is no clean way to put an RGB image into a QP. | Natural: end-to-end from images or heightscans. |
| task data | Zero task data needed; the cost is a dynamics model instead. | No model needed; the cost is simulation samples and tuning. |
| development cost | Model derivation and gain tuning. | Reward tuning and randomization tuning. |
The case for learning, at its strongest: locomotion is settled, and sim-trained controllers handle terrain, unknown payloads, and hardware variation, taking two generations of ANYmal through ground beyond the reach of prior published work in legged locomotion (in the papers' own words), at the cost of one forward pass at deploy time Lee 2020 Miki 2022. Perception integrates naturally; there is no clean way to put an RGB image into a QP. Contact schedules emerge from exploration instead of being enumerated. And semantics exists only on the learned side: Gemini Robotics 2 controls three embodiments from one checkpoint, and no model-based stack does anything comparable Parada 2026.
The case for model-based control, at its strongest: the strongest single 2026 result in legged control is not a learning result Zhang 2026. Constraints are enforced, not penalized; a friction cone in a QP holds, a reward penalty merely advises. Data efficiency is infinite in the relevant sense, since MPC needs zero task data. The behavior is verifiable in ways a network is not. And contact fidelity is a modeling problem, which is why the learning stack is importing model-based contact research into its simulators: Newton's hydroelastic contact modeling is inspired by Drake's contact model, Drake-developer TRI now partners with Newton on solver and contact modeling, and Newton acts as the physics layer under Isaac Lab Cano 2026 Reist 2026. The learning stack's current progress on manipulation is gated by better models, not better algorithms.
Model-based MPC (iLQR + MuJoCo)
recoversThe push is inside the model's assumptions, so the next re-solve finds a recovery inside the horizon. The deviation decays cleanly and no constraint is ever violated.
Compute per step: re-solves iLQR against the current state at every control step
Learned policy (sim RL)
recoversPushes were in the randomization distribution, so a recovery behavior is cached in the weights. It is sloppier: a damped oscillation instead of a clean decay.
Compute per step: one network forward pass, weights fixed at training
Same robot, same perturbation, two controllers. The traces are an illustrative model of the failure modes the literature reports, not measured hardware data.
After a lateral push at step 4 the MPC base-height deviation peaks at 6.00 cm and ends at 0.02 cm while the RL policy peaks at 8.00 cm and ends at -0.24 cm; MPC compute per step re-solves iLQR against the current state at every control step, the RL policy is one network forward pass, weights fixed at training, and the dashed RL trace is an illustrative teaching model rather than measured hardware data.
Sampled base-height deviation for both controllers
| step | MPC (cm) | RL (cm) |
|---|---|---|
| 0 | 0.00 | 0.00 |
| 4 | 6.00 | 8.00 |
| 10 | 2.21 | -4.02 |
| 20 | 0.42 | 0.89 |
| 30 | 0.08 | 0.44 |
| 39 | 0.02 | -0.24 |
Where the debate landed
The field has mostly stopped arguing and hybridized along a clean division. Model-based control owns anything with a good analytic model, hard constraints, and a need for guarantees: whole-body torque control, force control, safety layers, and increasingly the low-level interface below a learned policy. Learning owns anything requiring perception, semantics, contact discovery, or generalization across embodiments. The newest position dissolves the boundary entirely: model-based methods as the training signal for learned ones, through differentiable simulation, MPC-as-teacher distillation, and learned models used as forward dynamics for planning.
The genuinely contested question in 2026 is not learning or models. It is where the learned model lives: in the weights of a policy, in a latent dynamics model, in a video generator, or nowhere at all because you re-solve online.
See also
- Legged Locomotion Lineage
From ANYmal to Unitree and the MIT humanoid line: how learned gaits became the default.
- Humanoid Whole-Body Control
Motion tracking from PHC to ASAP and GMT, and the three decompositions of 2026.
- Massively Parallel Sim RL
Isaac Lab, Newton, MJX, and Brax: GPU-parallel environments and the wall-clock economics of training.
Linked from
- RL for Robotics
Sample efficiency decides which reinforcement learning algorithms a robot can actually be trained with, from PPO in simulation to offline learning on a fixed dataset.
- Massively Parallel Sim RL
Isaac Lab, Newton, MJX, and Brax: GPU-parallel environments and the wall-clock economics of training.
- Humanoid Whole-Body Control
Motion tracking from PHC to ASAP and GMT, and the three decompositions of 2026.
- Generative Simulation
Generated content inside real physics engines beats generated dynamics: RoboGen, Holodeck, RoboCasa.
- Motion Planning
RRT and its optimal variants, trajectory optimization, and CHOMP/TrajOpt.
- Control
PID, LQR, MPC, and whole-body QP: the classical stack under every learned policy.
References
Nikita Rudin, David Hoeller, Philipp Reist, Marco Hutter, CoRL 2021.
https://arxiv.org/abs/2109.11978
Nikita Rudin, 2021.
https://github.com/leggedrobotics/legged_gym
NVIDIA, Mayank Mittal, Yunrong Guo, Pascal Roth, David Hoeller, James Tigue, Antoine Richard, Octi Zhang, and 98 more, 2025.
https://arxiv.org/abs/2511.04831
OpenAI, Ilge Akkaya, Marcin Andrychowicz, Maciek Chociej, Mateusz Litwin, Bob McGrew, Arthur Petron, Alex Paino, and 11 more, 2019.
https://arxiv.org/abs/1910.07113
Yecheng Jason Ma, William Liang, Guanzhi Wang, De-An Huang, Osbert Bastani, Dinesh Jayaraman, Yuke Zhu, Linxi Fan, and 1 more, ICLR 2024.
https://arxiv.org/abs/2310.12931
Hojoon Lee, Ajay Subramanian, Ben Abbatematteo, Vijay Veerabadran, Pedro Matias, Karl Ridgeway, Nitin Kamra, RLC 2026.
https://arxiv.org/abs/2606.01672
Yunho Kim, Hyunsik Oh, Jeonghyun Lee, Jinhyeok Choi, Gwanghyeon Ji, Moonkyu Jung, Donghoon Youm, Jemin Hwangbo, IEEE Transactions on Robotics 2024.
https://arxiv.org/abs/2308.12517
Arthicha Srisuchinnawong, Poramate Manoonpong, RSS 2025.
https://arxiv.org/abs/2510.10759
Dohyeong Kim, Hyeokjin Kwon, Junseok Kim, Gunmin Lee, Songhwai Oh, 2024.
https://arxiv.org/abs/2409.15755
John Z. Zhang, Taylor A. Howell, Zeji Yi, Chaoyi Pan, Guanya Shi, Guannan Qu, Tom Erez, Yuval Tassa, and 1 more, ICRA 2026.
https://arxiv.org/abs/2503.04613
Joonho Lee, Jemin Hwangbo, Lorenz Wellhausen, Vladlen Koltun, Marco Hutter, Science Robotics 5(47), 2020.
https://arxiv.org/abs/2010.11251
Takahiro Miki, Joonho Lee, Jemin Hwangbo, Lorenz Wellhausen, Vladlen Koltun, Marco Hutter, Science Robotics 7(62), 2022.
https://arxiv.org/abs/2201.08117
Boston Dynamics, 2024.
https://bostondynamics.com/blog/starting-on-the-right-foot-with-reinforcement-learning/
Eric Cousineau, Scott Kuindersma, Lucas Manuelli, Pat Marion, 2025.
https://bostondynamics.com/blog/large-behavior-models-atlas-find-new-footing/
Carolina Parada, 2026.
https://deepmind.google/blog/gemini-robotics-2-brings-whole-body-intelligence-to-robots/
Johnny Nuñez Cano, Mitesh Patel, Asier Arranz, lior ben horin, Raymond Lo, Rishabh Chadha, 2026.
https://huggingface.co/blog/nvidia/state-of-simulation-for-physical-ai
Philipp Reist, Miguel Zamora Mora, JC Chang, Rishabh Chadha, Mohammad Mohajerani, 2026.
https://developer.nvidia.com/blog/newton-adds-contact-rich-manipulation-and-locomotion-capabilities-for-industrial-robotics
Spot a factual error or missing qualification? Report a content correction.