ModelRefs / LiveCodeBench Methodology — Methodology
LiveCodeBench Methodology — Methodology
LiveCodeBench evaluates code generation on contamination-free programming problems with rolling cutoffs.
Overview
What it measures: Code generation, self-repair, test-output prediction, and code execution on fresh problems.
How it works
- Problems sourced continuously from LeetCode, AtCoder, and CodeForces.
- Rolling time windows allow contamination-free evaluation.
- Multiple tasks: generation, self-repair, test-output prediction, execution.
Strengths
- Contamination-resistant
- Rich multi-task evaluation
Limitations
- Competitive-programming bias
- Frequent re-evaluation required
Best use cases
Coding-model contamination control
Continue your research
Use these connected ModelRefs sections to compare alternatives, inspect implementation paths, and review the evidence and governance boundaries relevant to LiveCodeBench Methodology — Methodology.
Frequently asked questions
What does LiveCodeBench measure?
Code generation, self-repair, test-output prediction, and code execution on fresh problems.
What are its main limitations?
Competitive-programming bias Frequent re-evaluation required
When should I use this benchmark?
Coding-model contamination control