Cause of train–test reward mismatch in RLER training
Investigate whether the observed discrepancy between high training rewards and lower downstream evaluation performance in DR Tulu results from mismatches between training-time tasks, rubric designs, and evaluation protocols, and characterize conditions under which such mismatches occur.
References
We conjecture that this stems from a mismatch between the tasks, rubrics, and evaluation setups of the external benchmarks vs.~what we used for training. We defer a deeper investigation of this mismatch phenomenon to future work, as addressing it would help improve the effectiveness of rubrics for RL training.
A robot verifier is optimized against in the same way, and the mechanism therefore applies on the robot side, where the corresponding measurement has yet to be run.
We don't understand why this gap is larger, but are investigating this in future work.
The converse question, when an internal mismatch must incur nonvanishing task loss, remains open.
Two failure modes remain open. The first is a dense-gain fade. In some runs, the dense-inference gain peaks and then decays, while the reward of the routed training rollouts keeps rising. The generator then improves its routed transitions faster than its dense ones. Centered routed steps keep the rollouts near the dense path and reduce this split on Stable Diffusion 3.5, but the mechanism is not fully isolated. The second is reward hacking against the frozen preference model. This risk is general to online RL for generative models and is not specific to RPO. Both failure modes suggest that a scalar terminal reward is a coarse supervisor for a routed exploration action.