Papers › The Open Catalyst 2020 (OC20) Dataset and Community Challenges

The Open Catalyst 2020 (OC20) Dataset and Community Challenges

20 Oct 2020arXiv:2010.09990archive 2025-07-28

Lowik Chanussot, Abhishek Das, Siddharth Goyal, Thibaut Lavril, Muhammed Shuaibi, Morgane Riviere, Kevin Tran, Javier Heras-Domingo, Caleb Ho, Weihua Hu, Aini Palizhati, Anuroop Sriram, Brandon Wood, Junwoong Yoon, Devi Parikh, C. Lawrence Zitnick, Zachary Ulissi

Catalyst discovery and optimization is key to solving many societal and energy challenges including solar fuels synthesis, long-term energy storage, and renewable fertilizer production. Despite considerable effort by the catalysis community to apply machine learning models to the computational catalyst discovery process, it remains an open challenge to build models that can generalize across both elemental compositions of surfaces and adsorbate identity/configurations, perhaps because datasets have been smaller in catalysis than related fields. To address this we developed the OC20 dataset, consisting of 1,281,040 Density Functional Theory (DFT) relaxations (~264,890,000 single point evaluations) across a wide swath of materials, surfaces, and adsorbates (nitrogen, carbon, and oxygen chemistries). We supplemented this dataset with randomly perturbed structures, short timescale molecular dynamics, and electronic structure analyses. The dataset comprises three central tasks indicative of day-to-day catalyst modeling and comes with pre-defined train/validation/test splits to facilitate direct comparisons with future model development efforts. We applied three state-of-the-art graph neural network models (CGCNN, SchNet, Dimenet++) to each of these tasks as baseline demonstrations for the community to build on. In almost every task, no upper limit on model size was identified, suggesting that even larger models are likely to improve on initial results. The dataset and baseline models are both provided as open resources, as well as a public leader board to encourage community contributions to solve these important tasks.

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 repositories (Open-Catalyst-Project/Open-Catalyst-Dataset, Open-Catalyst-Project/ocp) is linked to this paper; the 11 samples below come from 1 community repository. Syntology harvested code from Open-Catalyst-Project/Open-Catalyst-Dataset for another paper; Open-Catalyst-Project/ocp was not harvested.

Open-Catalyst-Project/Open-Catalyst-Dataset: Syntology's graph links these samples to The Open Catalyst 2022 (OC22) Dataset and Challenges for Oxide Electrocatalysts (arXiv:2206.08917; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method.

Syntology 11 code samples harvested from 1 repository linked to this paper: 11 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 0 honoured, 0 violated, 11 with no contract checked; 0 where Syntology's instrument failed) · 0 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): 11 samples from 1 repository, 11 ran (11 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 between 2026-09-24 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

Open-Catalyst-Project/Open-Catalyst-Dataset officialmentioned in papermentioned on GitHubMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to The Open Catalyst 2022 (OC22) Dataset and Challenges for Oxide Electrocatalysts (arXiv:2206.08917; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
Open-Catalyst-Project/ocp officialmentioned in papermentioned on GitHubpytorchNOASSERTIONSyntology: not harvested report
atomicarchitects/equiformer_v2 mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to EquiformerV2: Improved Equivariant Transformer for Scaling to Higher-Degree Representations (arXiv:2306.12059; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 1 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
gasteigerjo/ocp mentioned on GitHubpytorchMITSyntology: 11 samples, 11 ran (0 instrument-failed) · 0 unverified report
open-catalyst-project/adsorbml mentioned on GitHubSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to AdsorbML: A Leap in Efficiency for Adsorption Energy Calculations using Generalizable... (arXiv:2211.16486; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. 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

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

11ran

Licence: 11 of the 11 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 gasteigerjo/ocp. “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.

gasteigerjo/ocp community (archive-listed) 11 samples, 11 ran (0 instrument-failed) · 0 unverified
all_gather in 119 papers ocpmodels/common/distutils.py ran fingerprinted MIT recorded; this copy not marked cleared · pointer only · 635a18ab920c357f · report fixture: signature data:Tensor/2/float, group:NoneType/0/?, device:NoneType/0/? · returned Tensor · level recorded 2026-09-24
all_reduce in 42 papers ocpmodels/common/distutils.py ran MIT recorded; this copy not marked cleared · pointer only · 756b5e51d5c1964c · report fixture: signature data:Tensor/2/float, group:NoneType/0/?, average:bool/0/bool, device:NoneType/0/? · returned Tensor · level recorded 2026-09-24
balanced_partition ocpmodels/common/data_parallel.py ran MIT recorded; this copy not marked cleared · pointer only · 533f30a195dbfa61 · report fixture: signature sizes:ndarray/1/float, num_parts:int/0/int · returned list · level recorded 2026-09-24
data_list_collater ocpmodels/datasets/lmdb_dataset.py ran MIT recorded; this copy not marked cleared · pointer only · 2773459a7c1ef8da · report fixture: signature data_list:list/1/callable, otf_graph:bool/0/bool · returned DataBatch · level recorded 2026-09-24
divide_and_check_no_remainder ocpmodels/common/gp_utils.py ran fingerprinted MIT recorded; this copy not marked cleared · pointer only · 4cc559b0523f8850 · report fixture: signature a:int/0/int, b:int/0/int · returned int · level recorded 2026-09-24
label_metric_dict ocpmodels/common/hpo_utils.py ran MIT recorded; this copy not marked cleared · pointer only · 5d9e332995e7cc56 · report fixture: signature metric_dict:dict/0/?, split:str/0/str · returned dict · level recorded 2026-09-26
pad_tensor in 27 papers ocpmodels/common/gp_utils.py ran fingerprinted MIT recorded; this copy not marked cleared · pointer only · db111ae38a618c0c · report fixture: signature tensor:Tensor/2/float, dim:int/0/int, target_size:NoneType/0/? · returned Tensor · level recorded 2026-09-24
pyg2_data_transform ocpmodels/common/utils.py ran MIT recorded; this copy not marked cleared · pointer only · f95aab1cbc14547b · report fixture: signature data:Data/0/? · returned Data · level recorded 2026-09-24
save_checkpoint in 36 papers ocpmodels/common/utils.py ran MIT recorded; this copy not marked cleared · pointer only · c6a184c02a3bee1a · report fixture: signature state:dict/0/?, checkpoint_dir:str/0/str, checkpoint_file:str/0/str · returned str · level recorded 2026-09-24
trim_tensor ocpmodels/common/gp_utils.py ran fingerprinted MIT recorded; this copy not marked cleared · pointer only · 841cbd34a54c14e5 · report fixture: signature tensor:Tensor/2/float, sizes:Tensor/1/int, dim:int/0/int · returned tuple · level recorded 2026-09-24
warmup_lr_lambda ocpmodels/common/utils.py ran MIT recorded; this copy not marked cleared · pointer only · f082e62754852c3a · report fixture: signature current_step:int/0/int, optim_config:dict/0/? · returned float · level recorded 2026-09-24

Tasks

3D Pose EstimationGraph Neural Network

Datasets

Introduced by this paper, per the archive.

OC20

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Graph Neural NetworkSchNetShifted Softplus

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