Summary
The primary contribution of this paper is to propose a stronger random baseline when accounting for validation set reuse. The authors argue that the standard random baseline (expected accuracy of guessing labels randomly) is not sufficient when we allow for multiple evaluations on validation set, and when accounting for that (multiple evaluations on validation set and picking the max), the authors derive the closed form expression of the stronger random baseline, and show that many published results outperform the weaker standard random baseline but not the newly proposed baseline. The authors also argue that this baseline predicts held-out performance better.
Reasons to accept
- The new maximum random baseline is theoretically motivated and is intuitive to understand: if we allow multiple draws from the binomial distribution which the random classifier is doing, the expected value of the maximum accuracy will be higher than the accuracy if we only allow one draw. The baseline is built on this principle and I agree with the authors that this is also straightforward to implement and can be used as a drop-in replacement for the simple random baseline.
- The revelation that many published results do not, in fact, outperform this simple baseline is a potentially impactful finding.
Reasons to reject
One of my biggest concerns is as follows: the standard machine learning practice is *not* to rely on validation accuracy as the result to report. To give an example, if we train an image classifier, the standard practice is to evaluate the validation set at the end of each epoch, and then choosing the argmax for testing *once*. The test accuracy is typically what we care about, and we are only allowed to evaluate on it exactly once -- putting into the context of this paper, this means we are only allow to draw one realization of the binomial distribution (Eq (1)) once rather than $t$ times at *test-time*, which will reduce the proposed baseline back to the standard random baseline. Thus, even though on validation set, which is designed to be evaluated multiple times, the proposed baseline will be much stronger, it will make no difference at test time if standard protocol is followed. The authors seem to suggest that many reported papers do not properly use this elementary train-validation-test split and either report the validation accuracy only or evaluate on test sets multiple times -- while it is certainly not the authors' fault that basic data splitting protocol is not adhered to, I think that providing a stronger validation baseline seems to be the wrong question to answer when the real solution, which is not very difficult to implement and is virtually in any machine learning 101 course, is to use standard data splitting and to report test performance and allow for a single evaluation on test set.
As such, I felt that the contribution of this paper is somewhat conditional on a flawed practice of not properly using test set being widespread, and to my opinion using the test set properly as told in the textbook is a much better solution (even the authors have acknowledged so in Sec 6 *"While it is best practice to report test performance on a truly held-out set of examples"*). While I think it's unfair to harshly penalize the authors for violations of such basic rules by the others, I think it's necessary for this paper to strongly emphasize this caveat.