- Rating
- 1
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
The paper works with the following problem: if a vendor of some model claims that some configuration of the model meets some performance guarantee, how much data does an auditor need to prove the vendor false? They propose using an intersection-union test (IUT) and show that while you don't need to do multiple-testing corrections on it to control the false discovery rate, its sample complexity does increase as the possible number of configurations increases, so it's not "free" to have many configurations. They also establish a distinction between estimation and testing, showing that in certain settings their IUT can be less sample-efficient than optimal tests, and investigate when this gap can be avoided. They then also conduct some experiments using both synthetic and real data to illustrate their findings.
Critical strengths
The statistical problem presented in this paper seems well-defined. The theoretical results also seem interesting, like the sample-complexity guarantees, the distinction they present between testing and estimation, trying to characterize when auditing can be made more efficient, and having many cases of empirical evaluation.
Critical weaknesses
This paper is extremely difficult to read.
In the abstract, there is no motivation provided for the problem. The opening sentence is dense enough that someone not very familiar with this area might have no idea what this paper is about. The rest of the abstract reads as if it contains all the results of the paper compressed into a short paragraph, but this has the effect of making it unreadable. Towards the end of the abstract, for example, the references to "audit-A" and "audit-B" and "the cleaner multi-annotator Polaris target" are all provided without any context, so the reader cannot infer what they mean.
The introduction provides some motivation for the problem, but it is not clear where this would occur in real life. Say that a hospital is buying an AI classifier, and it needs it to make predictions on at least 90% of patients and make errors on at most 10% of them. A "configuration" might be defined as the confidence threshold that the model needs to make a prediction (e.g., the model will predict if its confidence is at least 80%). Now say that there are many such possible configurations. Why would the hospital want to buy a system just on the claim that some configuration will work for their requirement, without knowing which one? Maybe there are other cases where it does make sense, but they are not obvious to me. It would be good to provide better motivation for this problem.
The introduction also says "This is the dual of risk control and Learn-then-Test, which certify one rule selected by calibration." However, I don't think the paper formalizes a duality. The meaning of this sentence should be made more precise. Additionally, the average reader of ICLR might not be familiar with Learn-then-Test, so some context might be helpful. Shortly after that, the phrase "one fixed witness rule" isn't obvious in its meaning. Line 55 mentions a "gap" but that term hasn't been defined; is defined as the "risk gap" in line 58 but again it's not clear what that means. The explanation of the "main result in one line" is also not very clear (e.g., the phrase "the auditor must rule out that the errors happen to be concentrated there, and the error mass of such a region fluctuates on the scale of that region, not of the whole sample"). The notion of EFC is introduced without much motivation (and an expansion of the acronym is not given until much after the term is first used).
In Section 2, line 156, is used to explain "the exact IUT" before it is introduced in Proposition 1. It might also help to motivate why EFCs are an important class of audits to study. Additionally, it's not clear why it should be called a "certified frontier".
In Theorem 1 of Section 3, it seems like the statement holds for large values of and bounded in specific way, so it might be helpful to give some intuition as to which settings would one expect this to hold (eg if there was a concrete running example, it could be used here to illustrate the theorem).
Section 4 starts with "the reference ...", but this implies that it has already been discussed. There's no motivation or context given here. When the text then says "it is infeasible," it's unclear what that means.
The opening sentence of Section 5 could use some context.
In Section 6.3 line 359, the are undefined, and the description "exact fixed-marginal hiding window" is not clear. is also undefined.
In the experimental protocol in general, there are a lot of undefined terms like 'three-way resplits', ''confidence channels', 'midpoint contracts', and 'transfer'.
Section 7 does not read like a typical related works summary and rather as a list of works. It would be helpful to position this paper amidst the related work and explain its novelty. This is in particular important given the theoretical nature of this work. The limitations are likewise presented as a semicolon-separated list, and some more explanation would be helpful.
In sum, this paper does not feel like it is ready for publication yet; the theoretical results seem interesting but a much clearer writing style and presentation is necessary.
Questions for authors
- In Section 2, Eq 3 is very dense and seems to be optimizing over many things; a plain-language explanation would be very helpful.
- In Section 2, Eq 4 "the exact IUT," the RHS of the equation minimizes over but then the LHS depends on . This seems to be inconsistent.
- In Section 3, a mathematical definition of "robustly infeasible" is given, but a plain-language explanation/intuition would be very helpful. E.g., why should the alternative be strengthened in this way?
- In Section 3, Thm 1, the explanation given below the theorem is very dense. For example, in saying "the magnitudes match their first log even moments but differ in their mean by the best polynomial approximation error of ," it would be helpful to explain why moment matching or polynomial approximation arise, or how they relate to your auditing problem.
- Later in Line 227, "The logarithmic gaps and constants remain open," what exactly does this mean?
- In Section 4, in the "sign families" setup, there is again very dense notation. Could you provide a toy example to help in illustrating what is going on?
- In Section 4, why is the "effective dimension" introduced? What is its purpose?
- In Section 5 what motivates the move to unknown heterogeneous risk? I think this theorem and the previous one differ in their assumptions but clear motivation could be helpful.
- In the right panel of Fig 1, there is a very specific logarithmic factor used to divide the values of the curves; could you provide some motivation for this?