Papers › ChaosBench: A Multi-Channel, Physics-Based Benchmark for Subseasonal-to-Seasonal...

ChaosBench: A Multi-Channel, Physics-Based Benchmark for Subseasonal-to-Seasonal Climate Prediction

1 Feb 2024arXiv:2402.00712archive 2025-07-28

Juan Nathaniel, Yongquan Qu, Tung Nguyen, Sungduk Yu, Julius Busecke, Aditya Grover, Pierre Gentine

Accurate prediction of climate in the subseasonal-to-seasonal scale is crucial for disaster preparedness and robust decision making amidst climate change. Yet, forecasting beyond the weather timescale is challenging because it deals with problems other than initial condition, including boundary interaction, butterfly effect, and our inherent lack of physical understanding. At present, existing benchmarks tend to have shorter forecasting range of up-to 15 days, do not include a wide range of operational baselines, and lack physics-based constraints for explainability. Thus, we propose ChaosBench, a challenging benchmark to extend the predictability range of data-driven weather emulators to S2S timescale. First, ChaosBench is comprised of variables beyond the typical surface-atmospheric ERA5 to also include ocean, ice, and land reanalysis products that span over 45 years to allow for full Earth system emulation that respects boundary conditions. We also propose physics-based, in addition to deterministic and probabilistic metrics, to ensure a physically-consistent ensemble that accounts for butterfly effect. Furthermore, we evaluate on a diverse set of physics-based forecasts from four national weather agencies as baselines to our data-driven counterpart such as ViT/ClimaX, PanguWeather, GraphCast, and FourCastNetV2. Overall, we find methods originally developed for weather-scale applications fail on S2S task: their performance simply collapse to an unskilled climatology. Nonetheless, we outline and demonstrate several strategies that can extend the predictability range of existing weather emulators, including the use of ensembles, robust control of error propagation, and the use of physics-informed models. Our benchmark, datasets, and instructions are available at https://leap-stc.github.io/ChaosBench.

PaperPDFCodeCode Syntology ran

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

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2402.00712")

Code

Syntology Ran 11 of 11 code samples harvested from 2 repositories linked to this paper; 0 have no recorded run. Of those that ran: 2 ran · violated contract; 9 ran with no contract checked.

By repository: official repository: 9 samples from 1 repository, 9 ran; found in paper text by Syntology: 2 samples from 1 repository, 2 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

leap-stc/ChaosBench officialmentioned in papermentioned on GitHubpytorchGPL-3.0 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.

Code Syntology ran Syntology

11 samples harvested; 11 ran; 0 honoured the contract we drafted; 0 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

2ran · violated contract
9ran

Licence: 9 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 2 repositories linked to this paper, official or community; each sample names its own and says which. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

cast_tuple leap-stc/ChaosBench/chaosbench/models/vit.py official repository ran · violated contract fingerprinted GPL-3.0 (copyleft) · pointer only · 1f7c550e65142ef8 · report
conv2d_bn_relu leap-stc/ChaosBench/chaosbench/models/ae.py official repository ran GPL-3.0 (copyleft) · pointer only · 92f1a3fa77bf2251 · report
conv_block leap-stc/ChaosBench/chaosbench/models/cnn.py official repository ran GPL-3.0 (copyleft) · pointer only · 143f63c99701b6a9 · report
convert_time leap-stc/ChaosBench/chaosbench/utils.py official repository ran fingerprinted GPL-3.0 (copyleft) · pointer only · 3cd9a84568633114 · report
deconv_relu leap-stc/ChaosBench/chaosbench/models/ae.py official repository ran GPL-3.0 (copyleft) · pointer only · 451d321a21300bea · report
deconv_sigmoid leap-stc/ChaosBench/chaosbench/models/ae.py official repository ran GPL-3.0 (copyleft) · pointer only · 1d3a3f04669fabe7 · report
exists leap-stc/ChaosBench/chaosbench/models/vit.py official repository ran · violated contract GPL-3.0 (copyleft) · pointer only · aa5486a3650902d8 · report
interpolate leap-stc/ChaosBench/eval_direct.py official repository ran GPL-3.0 (copyleft) · pointer only · b12e0af56d8cccb1 · report
upconv_block leap-stc/ChaosBench/chaosbench/models/cnn.py official repository ran GPL-3.0 (copyleft) · pointer only · 362233a242a189a5 · report
peek ecmwf-lab/ai-models/src/ai_models/checkpoint.py found in paper text by Syntology ran Apache-2.0 (permissive) · 9dd689a970ea2365 · report
tidy ecmwf-lab/ai-models/src/ai_models/checkpoint.py found in paper text by Syntology ran Apache-2.0 (permissive) · 93ab76178df79a49 · report

Datasets

Introduced by this paper, per the archive.

ChaosBench

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

SET

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