Human Feedback Types
missingNone explicit
No explicit feedback protocol extracted.
"Test-time scaling improves the performance of a fixed model by spending more computation at inference."
HFEPX · Eval paper review
Junlin Wang, Haozhe Chen, Ang Li, Rahul Chalamala +1 more
Published
Nov 6, 2026
Citations
0
Trust level
Low
Usefulness score
0/100 (Low)
Extraction confidence
15% (Low)
Derived from extracted protocol signals and abstract evidence.
Rater population
Not reported
Signals refreshed
Nov 6, 2026
This paper is adjacent to HFEPX scope and is best used for background context, not as a primary protocol reference.
Use this as background context only. Do not make protocol decisions from this page alone.
All signals on this page are inferred from the abstract only and may be inaccurate. Do not use this page as a primary protocol reference.
Best use
Background context only
Use if you need
A secondary eval reference to pair with stronger protocol papers.
What to verify
Read the full paper before copying any benchmark, metric, or protocol choices.
Main weakness
This paper looks adjacent to evaluation work, but not like a strong protocol reference.
Treat as adjacent context, not a core eval-method reference.
If you are doing eval pipeline work, start here
Test-time scaling improves the performance of a fixed model by spending more computation at inference. There are two common ways to spend it on agents when a verifier can score every attempt. Best-of-N sampling runs many independent agents and keeps the best result but saturates quickly. One large team of collaborating agents can score higher but stops improving as it grows. Can we get the best of both? Our method, parallel agent teams, does so by sampling many small teams in parallel and keeping the best team's result. We test it on 12 long-horizon tasks from GPU kernels and formal proofs to exploit development. With a 27B model and a budget of 100 agents, parallel teams of ten beat parallel agents on 10 of 12 tasks and beat one team of 100 on all four tasks where we ran such large teams. At equal dollar cost the same parallel teams beat a frontier model on half the tasks. A simple statistical model shows that individual agents lose because their many samples have a low mean and that one large team loses because a single sample gets no gain from variance. Sampling many small teams in parallel balances a high mean with the gain from variance. Parallel agent teams thus offer a more effective way to scale test-time compute.
These are the protocol signals we could actually recover from the available paper metadata. Use them to decide whether this paper is worth deeper reading.
None explicit
No explicit feedback protocol extracted.
"Test-time scaling improves the performance of a fixed model by spending more computation at inference."
None explicit
Validate eval design from full paper text.
"Test-time scaling improves the performance of a fixed model by spending more computation at inference."
Not reported
No explicit QC controls found.
"Test-time scaling improves the performance of a fixed model by spending more computation at inference."
Not extracted
No benchmark anchors detected.
"Test-time scaling improves the performance of a fixed model by spending more computation at inference."
Not extracted
No metric anchors detected.
"Test-time scaling improves the performance of a fixed model by spending more computation at inference."
No benchmark or dataset names were extracted from the available abstract.
No metric terms were extracted from the available abstract.
Test-time scaling improves the performance of a fixed model by spending more computation at inference.
Based on abstract + metadata only. Check the source paper before making high-confidence protocol decisions.
Human feedback protocol is explicit
No explicit human feedback protocol detected.
Evaluation mode is explicit
No clear evaluation mode extracted.
Quality control reporting appears
No calibration/adjudication/IAA control explicitly detected.
Benchmark or dataset anchors are present
No benchmark/dataset anchor extracted from abstract.
Metric reporting is present
No metric terms extracted.