Completion vs Optimality: Policy Gradient in Long-Horizon Cumulative-Damage Problems
This paper identifies and decomposes two orthogonal failure modes—completion and optimality—in policy-gradient methods for long-horizon cumulative-damage problems, demonstrating through empirical validation in bricklayer and NBA career simulations that while action-space restrictions enable task completion, they often leave a significant optimality gap caused by early greedy commitments.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine you are training a robot to play a very long game of "Career." The goal is to stay in the game as long as possible while collecting as many points as possible. However, there's a catch: the moves that give you the most points right now also slowly break your robot's legs. If the legs break too much, the game ends immediately.
This paper, titled "Completion vs. Optimality," investigates why smart AI learning methods (specifically something called "Policy Gradient") often fail at this type of game. The authors, Wolfgang Maass and Sabine Janzen, discovered that these AIs fail in two completely different ways, and they need to be fixed with different tools.
Here is the breakdown using simple analogies:
1. The Two Ways to Fail
The authors realized that when an AI does poorly, it's usually failing at one of two distinct tasks, but standard scoring systems mix them up:
Failure A: "Quitting Early" (Completion Failure)
- The Analogy: Imagine a marathon runner who starts sprinting at full speed because they want to get to the finish line fast. They burn out their muscles in the first mile and have to quit the race entirely.
- The AI Problem: The AI sees the "greedy" move (the one with the most immediate points) and takes it. This move secretly damages the robot's "health." Because the damage signal is hidden until it's too late, the AI keeps taking the damaging move until the robot breaks and the episode ends early. It never even gets to the later, high-reward stages of the career.
Failure B: "Playing Too Hard" (Optimality Failure)
- The Analogy: Imagine a runner who does finish the marathon, but they sprinted so hard at the start that they are limping and exhausted by the end. They finished, but they could have run a much better race if they had paced themselves.
- The AI Problem: Even if the AI manages to survive the whole career, it often gets stuck in a "trap." It learns to go 100% effort at the very beginning because that looks like the best move for the first step. Once it commits to this "all-out" start, it can't recover. It ends up with a lower total score than it could have achieved if it had started gently.
2. The Two Experiments
To prove this, the authors built two different "career simulators" that act like video games:
- The Bricklayer: A 49-year career of a construction worker doing heavy lifting.
- The NBA Player: A 20-season career of a basketball power forward.
Both games have the same hidden rule: Do too much work too soon, and you get injured (the game ends).
3. What They Found
The authors tested three different approaches on these games:
- The "Real" AI (PPO): This is the standard AI trying to learn by trial and error.
- Result: It failed Completion. In the bricklayer game, it quit at age 27.8 (instead of 65). In the NBA game, it quit at age 22.6 (instead of 38). It sprinted too hard and broke down.
- The "Unrestricted" AI with a Soft Penalty: The researchers tried to help the AI by giving it a "soft warning" (a small penalty) if it worked too hard, and letting it see the whole career length.
- Result: This actually made things worse. The AI quit even earlier (age 24.7). The penalty confused the AI, causing it to stop working entirely or quit prematurely.
- The "Restricted" AI (Fixed-Share): The researchers forced the AI to follow a specific rule: "You must only do 15% of the dangerous heavy lifting." The AI was only allowed to decide how hard to work, not what to work on.
- Result: This AI achieved Completion. It finished the full 49 years or 20 seasons without quitting.
- The Catch: Even though it finished, it still failed Optimality. It finished with a score of 0.52 (on a scale where the perfect score is 0.79). It survived, but it didn't play the best possible game because it got stuck in that "sprint at the start" trap.
4. The "First Step" Trap
The most interesting discovery is why the AI plays too hard at the start.
The authors found that the AI makes a "greedy commitment" in the very first second of training.
- The Metaphor: Imagine a student taking a test. The first question is easy and gives 100 points. The student thinks, "I'll just answer this one super fast!" They do, but in doing so, they use up all their mental energy for the rest of the test.
- The Science: The AI calculates that the "all-out" move gives a huge reward right now. Because the damage doesn't show up until later, the AI's first instinct is to go for the big reward. Once it locks into that "all-out" strategy, it's too late to change. Even if you train it for a million years, it keeps making that same first mistake.
5. The Conclusion
The paper concludes that you cannot fix these problems with just one tool.
- To stop the AI from quitting early, you have to restrict its choices (force it to not do the dangerous move 100% of the time).
- To stop the AI from playing poorly (even when it survives), you need to fix how it learns from the very first step, because it gets "stuck" in a bad habit immediately.
In short: The AI is like a worker who either quits the job too soon because they work too hard, or stays in the job but burns out their career because they started too hard. The paper shows that simply telling the AI "don't work too hard" isn't enough; you have to change the rules of the game and how the AI thinks about the very first move.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.