A distilled value head breaks search, but search remains an effective teacher, not a move selector: a case study in 19x19 Go
This study demonstrates that while distilling a value head from a strong Go AI can result in a calibrated but non-discriminative evaluator that breaks MCTS search performance, the search process itself remains a highly effective teacher, as training the policy to mimic MCTS visit counts yields significant strength gains despite the search failing to select better moves during inference.
Original paper licensed under CC BY 4.0 (https://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 teaching a brilliant but stubborn student how to play a complex strategy game like Chess or Go. You have a super-smart teacher (let's call it "The Oracle") who can look at the board and tell you exactly who is winning. Usually, when you teach a student, you let them practice by playing against the teacher, or you let them think through a few moves ahead to see what happens. In the world of artificial intelligence, this "thinking ahead" is called Monte Carlo Tree Search (MCTS). It's like a simulator that runs thousands of tiny, imaginary games in a split second to figure out the best move.
The big idea in modern AI is that if you combine a smart "brain" (a neural network) with this "simulator" (MCTS), the result should be unbeatable. The brain guesses the move, and the simulator double-checks it. But what if the simulator starts making the brain worse? What if the tool meant to help you think actually confuses you? This is the strange puzzle a researcher named Taiki Kojima tackled. He wasn't trying to build a robot that wins the World Championship; he was trying to understand a glitch where the "thinking" part of the AI broke the "playing" part, even though the "thinking" part was still incredibly useful for teaching. It's a story about how a bad compass can still be a great map for a teacher.
The Glitchy Compass
In the world of computer Go (a game played on a 19x19 grid), researchers usually train AI by having it learn from a super-strong teacher. In this study, the teacher was a famous AI called KataGo. The researcher took a smaller, simpler AI and tried to copy the teacher's brain using a technique called knowledge distillation. Think of this like a student trying to memorize the teacher's homework answers.
Usually, once the student learns the answers, you let them use their own "thinking engine" (MCTS) to double-check their work before they make a move. The expectation was that this would make the student even stronger. But here is where the plot twists: When the researcher let the student use MCTS to pick its moves, the student actually got worse.
The student, playing without any thinking engine, won about 32% of the games against itself. But the moment it turned on the "thinking engine" to help choose moves, its win rate plummeted. It was as if a student who could solve math problems perfectly suddenly started failing every test the moment they were allowed to use a calculator.
The Broken Value Head
The researcher had to figure out why the calculator was broken. Was the calculator itself (the search algorithm) faulty? Or was the student's brain (the neural network) giving the calculator bad information?
To test this, the researcher swapped the student's brain with the teacher's brain for just the final step of the calculation. Suddenly, the win rate skyrocketed to 98.3%. This proved the "calculator" (MCTS) was working perfectly. The problem was entirely in the student's brain.
Specifically, the problem was in the value head. In AI terms, the "value head" is the part of the brain that says, "Is this position good or bad?" The student's value head was actually pretty good at judging the absolute score (it knew if a position was winning or losing overall). But it was terrible at comparing two similar moves side-by-side. It couldn't tell which of two sibling moves was slightly better.
Imagine a judge who can tell you if a painting is "good" or "bad," but when you show them two paintings that are both "good," they can't tell you which one is better. When the AI tried to use this confused judge to pick the best move, it kept making mistakes. The search engine dug deeper, found more confusing comparisons, and made the AI's decisions worse and worse.
The Fix: Stop Using the Compass, Start Using the Map
The researcher tried to fix the broken judge by retraining just that part of the brain. The judge got slightly better at comparing moves, but the AI still couldn't use the search engine to play better. The search engine was still broken as a move selector.
So, the researcher tried a completely different approach. Instead of trying to fix the AI's ability to use the search engine to pick moves, they decided to use the search engine only as a teacher.
Here is the magic trick:
- The AI played a game using the search engine to generate a "visit distribution." This is a record of how much time the search engine spent looking at different moves. Even if the search engine picked the wrong final move, it might have spent a lot of time thinking about the right move.
- The researcher then trained the AI's brain to copy this "thinking pattern" (the visit distribution) rather than just copying the final move.
- They removed the "safety anchor" that usually keeps the AI from changing too much.
The result was shocking. By ignoring the search engine's final decision and only using its "thought process" as a lesson, the AI improved massively.
- Generation 2 (using the old method): The AI played no better than its previous version.
- Generation 3 (using the search engine as a teacher): The AI won 94.1% of games against the original baseline and 82.4% against the previous version.
This happened using less than half the amount of practice data (self-play games) that the previous generation used. The search engine was a terrible player (it picked the wrong moves 73% of the time), but it was an amazing teacher.
Why This Matters
The paper concludes that there is a huge difference between an AI's ability to make a decision and its ability to teach a lesson.
Think of it like a coach who is terrible at playing the sport themselves. If you ask this coach to play a match, they will lose. But if you ask them to watch a game and tell you where the players should focus their attention, they might be brilliant. The search engine in this study was like that coach: it couldn't pick the winner, but its "attention map" showed the student exactly where to look to learn.
The study also highlights a warning for anyone building AI: Don't trust your "scorecards" too much. The researchers found that standard metrics (like how well the AI ranked moves in a test) often failed to predict if the AI would actually get better at playing the game. Sometimes, the AI got better even when the test scores looked worse.
In the end, this isn't just about Go. The same problem happens in other AI fields, like training language models. Sometimes, the tool you use to generate answers is too flawed to be used directly, but the process of generating those answers holds the secret to making the AI smarter. The lesson? Don't throw away the teacher just because they can't play the game.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.