Papers › Measuring Mathematical Problem Solving With the MATH Dataset

Measuring Mathematical Problem Solving With the MATH Dataset

5 Mar 2021arXiv:2103.03874archive 2025-07-28

Dan Hendrycks, Collin Burns, Saurav Kadavath, Akul Arora, Steven Basart, Eric Tang, Dawn Song, Jacob Steinhardt

Many intellectual endeavors require mathematical problem solving, but this skill remains beyond the capabilities of computers. To measure this ability in machine learning models, we introduce MATH, a new dataset of 12,500 challenging competition mathematics problems. Each problem in MATH has a full step-by-step solution which can be used to teach models to generate answer derivations and explanations. To facilitate future research and increase accuracy on MATH, we also contribute a large auxiliary pretraining dataset which helps teach models the fundamentals of mathematics. Even though we are able to increase accuracy on MATH, our results show that accuracy remains relatively low, even with enormous Transformer models. Moreover, we find that simply increasing budgets and model parameter counts will be impractical for achieving strong mathematical reasoning if scaling trends continue. While scaling Transformers is automatically solving most other text-based tasks, scaling is not currently solving MATH. To have more traction on mathematical problem solving we will likely need new algorithmic advancements from the broader research community.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 3 code samples: 2 from 1 repository linked to this paper, 1 identical to code harvested from another paper's repository. Across all 3: 3 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: official repository: 2 samples from 1 repository, 2 ran (0 with no instrument failure; 2 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 3 samples that ran has no recorded date.

hendrycks/math officialmentioned in papermentioned on GitHubpytorchSyntology: 2 samples, 2 ran (2 instrument-failed) · 0 unverified report
facebookresearch/minif2f mentioned on GitHubSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to MiniF2F: a cross-system benchmark for formal Olympiad-level mathematics (arXiv:2109.00110; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
openai/minif2f mentioned on GitHubSyntology: not harvested report
radzim/obfuscated mentioned on GitHubSyntology: not harvested report
rah4927/lean-dojo-mew mentioned on GitHubMITSyntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

3 samples harvested: 3 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · our draft was wrong
1ran; the contract check could not run

Licence: 1 of the 3 samples is pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from hendrycks/math. 1 sample is listed last, in a group without a repository. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

hendrycks/math official repository 2 samples, 2 ran (2 instrument-failed) · 0 unverified
dict_to_gpu modeling/eval_math_gpt.py ran; the contract check could not run (RAISES) MIT (permissive) · 48d671a5de2eef0a · report fixture: returned dict · level recorded 2026-09-22
get_level_type modeling/eval_math_gpt.py ran · our draft was wrong MIT (permissive) · 203cd02db658aac9 · report fixture: signature fname:str/0/str · returned tuple · level recorded 2026-09-22
Repository not located 1 sample, 1 ran (1 instrument-failed) · 0 unverified
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
remove_boxed in 48 papers repository not located ran · our draft was wrong fingerprinted licence of this copy not recorded · f3bbe264b05aadd3 · report fixture: signature s:str/0/str · returned str · level recorded, date not recorded

Tasks

MathMath Word Problem SolvingMathematical Problem-SolvingMathematical ReasoningText Generation

Datasets

Introduced by this paper, per the archive.

AMPSMATH

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Math Word Problem Solving MATH GPT-2 (1.5B) Accuracy 6.9 #122 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-2 (1.5B) Parameters (Billions) 1.5 #122 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-2 (0.7B) Accuracy 6.4 #123 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-2 (0.7B) Parameters (Billions) 0.7 #123 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-2 (0.3B) Accuracy 6.2 #124 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-2 (0.3B) Parameters (Billions) 0.3 #124 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-3 13B Accuracy 5.6 #125 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-3 13B Parameters (Billions) 13 #125 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-2 (0.1B) Accuracy 5.4 #127 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-2 (0.1B) Parameters (Billions) 0.1 #127 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-3-175B (few-shot) Accuracy 5.2 #128 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-3-175B (few-shot) Parameters (Billions) 175 #128 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-3-13B (few-shot) Accuracy 3.0 #132 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-3-13B (few-shot) Parameters (Billions) 13 #132 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-3 2.7B Accuracy 2.9 #134 of 135 Archive leaderboard report
Math Word Problem Solving MATH GPT-3 2.7B Parameters (Billions) 2.7 #134 of 135 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformer

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections