Papers › PDEBENCH: An Extensive Benchmark for Scientific Machine Learning

PDEBENCH: An Extensive Benchmark for Scientific Machine Learning

13 Oct 2022arXiv:2210.07182archive 2025-07-28

Makoto Takamoto, Timothy Praditia, Raphael Leiteritz, Dan MacKinlay, Francesco Alesiani, Dirk Pflüger, Mathias Niepert

Machine learning-based modeling of physical systems has experienced increased interest in recent years. Despite some impressive progress, there is still a lack of benchmarks for Scientific ML that are easy to use but still challenging and representative of a wide range of problems. We introduce PDEBench, a benchmark suite of time-dependent simulation tasks based on Partial Differential Equations (PDEs). PDEBench comprises both code and data to benchmark the performance of novel machine learning models against both classical numerical simulations and machine learning baselines. Our proposed set of benchmark problems contribute the following unique features: (1) A much wider range of PDEs compared to existing benchmarks, ranging from relatively common examples to more realistic and difficult problems; (2) much larger ready-to-use datasets compared to prior work, comprising multiple simulation runs across a larger number of initial and boundary conditions and PDE parameters; (3) more extensible source codes with user-friendly APIs for data generation and baseline results with popular machine learning models (FNO, U-Net, PINN, Gradient-Based Inverse Method). PDEBench allows researchers to extend the benchmark freely for their own purposes using a standardized API and to compare the performance of new models to existing baseline methods. We also propose new evaluation metrics with the aim to provide a more holistic understanding of learning methods in the context of Scientific ML. With those metrics we identify tasks which are challenging for recent ML methods and propose these tasks as future challenges for the community. The code is available at https://github.com/pdebench/PDEBench.

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

No sample from the archive's official repository (pdebench/pdebench) is linked to this paper; the 5 samples below come from 1 community repository. Syntology harvested code from pdebench/pdebench for another paper.

pdebench/pdebench: Syntology's graph links these samples to Fourier Neural Operator for Parametric Partial Differential Equations (arXiv:2010.08895; that paper's own run record: 23 ran (of which 5 constructed an object rather than computing a result; 20 with no instrument failure: 4 honoured, 1 violated, 15 with no contract checked; 3 where Syntology's instrument failed) · 10 unverified); nothing checks that they implement this paper's method.

Syntology 5 code samples harvested from 1 repository linked to this paper: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: community (archive-listed): 5 samples from 1 repository, 4 ran (4 with no instrument failure; 0 where Syntology's instrument failed). 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 3 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

pdebench/pdebench officialmentioned in papermentioned on GitHubjaxNOASSERTIONSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Fourier Neural Operator for Parametric Partial Differential Equations (arXiv:2010.08895; that paper's own run record: 23 ran (of which 5 constructed an object rather than computing a result; 20 with no instrument failure: 4 honoured, 1 violated, 15 with no contract checked; 3 where Syntology's instrument failed) · 10 unverified); nothing checks that they implement this paper's method. report
abrar2652/nlp-roberta-bilstm-attention mentioned on GitHubtfMITSyntology: not harvested report
dmusekamp/al4pde mentioned on GitHubjaxNOASSERTIONSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Active Learning for Neural PDE Solvers (arXiv:2408.01536; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified); nothing checks that they implement this paper's method. report
merantix-momentum/multiscale-pde-operators mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Multiscale Neural Operators for Solving Time-Independent PDEs (arXiv:2311.05964; that paper's own run record: 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
tonyzyl/DiffusionReconstruct mentioned on GitHubpytorchApache-2.0Syntology: 5 samples, 4 ran (0 instrument-failed) · 1 unverified 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

5 samples harvested: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures 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.

4ran
1unverified

Licence: 0 of the 5 samples are 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 tonyzyl/DiffusionReconstruct. “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.

tonyzyl/DiffusionReconstruct community (archive-listed) 5 samples, 4 ran (0 instrument-failed) · 1 unverified
inverse_normalize_transform dataloader/dataset_class.py ran Apache-2.0 (permissive) · 346a5d40f393475e · report fixture: signature normalized_sample:Tensor/3/float, mean:list/1/float, std:list/1/float, target_std:int/0/int · returned Tensor · level recorded 2026-09-25
normalize_transform dataloader/dataset_class.py ran Apache-2.0 (permissive) · 2391f3a886186e96 · report fixture: signature sample:Tensor/3/float, mean:list/1/float, std:list/1/float, target_std:int/0/int · returned Tensor · level recorded 2026-09-25
parse_list_float evaluate.py ran Apache-2.0 (permissive) · 5c684a67efd1e405 · report fixture: signature value:str/0/str · returned list · level recorded 2026-09-25
parse_list_int evaluate.py ran Apache-2.0 (permissive) · 0286d0934a5f1e91 · report fixture: signature value:str/0/str · returned list · level recorded 2026-09-25
metric_func_2D losses/metric.py unverified Apache-2.0 (permissive) · 57be74f22a35caeb · report

Datasets

Introduced by this paper, per the archive.

PDEBench - Benchmark for Scientific Machine Learning

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Concatenated Skip ConnectionConvolutionMax PoolingReLUU-Net

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