Summary
In this paper, the authors propose *easy-to-hard* generalization, which is to train a reward model on simpler tasks and then use it to evaluate the solutions for more difficult tasks. They have conducted in-depth studies on MATH, and also demonstrated effectiveness on the coding benchmark APPS. This work serves as a nice proof-of-concept study of "evaluation is easier than generation", and suggests a new way toward scalable alignment without human supervision.
Strengths
- The idea of *easy-to-hard* generalization is inspiring, and it's nice to see that the idea works out on the challenging MATH dataset.
- The authors have conducted sufficient experiments and detailed analysis, which makes the paper quite worthy to be read and referred to.
Weaknesses
- The definition of "easy" v.s. "hard" is not very clear, and it seems that the proof-of-concept experiments rely on the structure of the benchmarks, as the MATH dataset has 5 divisions of difficulty and APPS has 3. However, when there are not explicit tags of difficulty in a benchmark, what is the authors' definition for "easy" and "hard" in terms of each data sample?
- Following the above weakness, a natural question for the authors is to demonstrate the practical value of this work when compared with recent work that scales synthetic data for MATH (e.g., [1]). Can the massive synthetic data be viewed as a mixture of easy and hard problems + the corresponding solutions? If we treat such mixed data as the easy part and train RMs on it, can we expect similar easy-to-hard generalization? Which kinds of ability would be "unlocked"?
[1] Improve Mathematical Reasoning in Language Models by Automated Process Supervision. https://arxiv.org/abs/2406.06592
- According to the figures shown in the paper, the "Weighted Voting w/ RM" method always yields better performance as N increases. By comparison, "Best-of-N w/ RM" and "Majority Voting" can plateau or even become worse when N increases from 512 to 1024. Does the weighted voting with RM guarantee the increasing performance, or is it just by accident? Would be great if there are formal explanations to this.
- While scaling the sampling times N has seen improvements, are there certain problems whose correct solutions are never sampled by the LLM when letting N be very large?
- More case studies would be beneficial to provide a more intuitive understanding of how the RM on easy problems generalize to hard ones.
- The authors have conducted in-depth analysis about the comparisons between PRM, ORM, and OPRM on MATH. While I appreciate the experiments, I wonder what the effect of PRM/ORM w.r.t. easy-to-hard generalization is. For example, is it true that we should always adopt PRM when it is possible to get process-based supervision (Lines 219~221)? If this is true, would the results on APPS be better when we could access process-based supervision for code (for example, treat the interleaved comments in a code snippet as that)?
Questions
The idea of "evaluation is easier than generation" is appealing, and it seems that the idea draws inspiration from the assumption that P < NP. However, for some tasks it seems that evaluation shares a similar level of difficulty with generation.
For example, let there be N integers: A_1, A_2, ..., A_N, and the task is to multiply them altogether: A_1 * A_2 * ... * A_N = ? . While doing multiplication is no easy task for LLMs, it seems that evaluating whether some potential answer is the result of A_1 * A_2 * ... * A_N is as difficult as generating the answer of the multiplication, since in either way, one should do it a serial manner (for i in 1,2..N).
Any thoughts/evidence on this?
And broadly speaking, are there cases when evaluation is as difficult as generation, or evaluation is even harder than generation? It would be great if the authors could shed light on this.
Limitations
The authors have adequately addressed the limitations.