the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
Evaluating Skill and Stability of ArchesWeather and ArchesWeatherGen under Multi-Decadal Climate Simulations
Abstract. We evaluate the climate simulation capabilities of ArchesWeather and ArchesWeatherGen, two machine learning models originally trained for weather forecasting and evaluated up to a 10-day lead time. ArchesWeather is a deterministic model, while ArchesWeatherGen is a probabilistic flow-matching model leveraging ArchesWeather's forecasts, enabling ensemble based uncertainty quantification. In this work, we adapt these models to act as forced atmospheric models by using additional conditioning on the monthly mean sea surface temperature (SST) and sea ice cover (SIC) as boundary conditions. In particular, we follow the AI Model Intercomparison Project (AIMIP) Phase 1 protocol, which, analogous to the Atmospheric Model Intercomparison Project (AMIP), proposes a standardized experimental setup to evaluate the climate skill of machine learning based forced atmospheric models. We present a comprehensive evaluation of both models under these conditions, including comparison against numerical climate models, ablation studies that examine key design choices in the extension, and an analysis of forced versus unforced configurations. Despite being originally developed for weather forecasting, we demonstrate that forced configurations of ArchesWeather and ArchesWeatherGen produce stable long-term climate simulations, have a stable annual cycle, and capture the drift of many climate variables. The models faithfully reproduce ERA5's climatology, large-scale circulations and interannual variability, and they capture the tails of the distributions.
Status: open (until 17 Sep 2026)
-
CEC1: 'Comment on egusphere-2026-3782 - No compliance with the policy of the journal', Juan Antonio Añel, 07 Aug 2026
reply
-
CC1: 'Reply on CEC1', Robert Brunstein, 10 Aug 2026
reply
Dear Editor,
thank your for pointing this out. We will address your concerns regarding data availability and repository structure and respond again immediately when we resolved this issue.
Best regards,
Robert BrunsteinCitation: https://doi.org/10.5194/egusphere-2026-3782-CC1
-
CC1: 'Reply on CEC1', Robert Brunstein, 10 Aug 2026
reply
-
CC2: 'Comment on egusphere-2026-3782', Robert Brunstein, 18 Aug 2026
reply
Dear Editor,
Thank you for your comments. We address the concerns about suitable repositories below.
The code to download data, train and run ArchesWeatherGen for AIMIP is available in the following Zenodo repository: https://zenodo.org/records/20784771. The same Zenodo repository also includes a docs/ folder, which holds all the documentation from the readthedocs.io link on how to run and train models with the geoarches codebase, including an interactive notebook.
The ERA5 data was regridded while downloading from the Copernicus site, we have updated the Code and Data Availability statement with this information. We have also added information on how to access and regrid CMIP6 model outputs, as used in our for evaluation.
The required CMORisation and evaluation pipeline is available this Zenodo repository: https://zenodo.org/records/21913147. With that code, users are able to evaluate the output of our models against other climate models and ERA5.
We have updated the Code and Data Availability section in the arxiv preprint with references to both Zenodo repositories and information on how to access and re-grid data. The new arxiv version will be available from tomorrow on, we append our new Code and Data Availability section here:
“Code to train and run models is available at https://zenodo.org/records/20784771 (Couairon et al., 2026a). Model weights and configs will be made available on Hugging Face. ERA5 data for training is available for download on Copernicus (regridded to 1◦ resolution with the internal Copernicus tool) and scripts to preprocess are made available in the repo above. The data needed to rollout models (initial conditions and forcings) are available at https://zenodo.org/records/21952904. The reference climate model data from AMIP used in this study is available from https://wcrp-cmip.org/cmip-data-access/. The specific amip-p4k runs used for the warming scenarios can be found via https://doi.org/10.22033/ESGF/CMIP6.7536 (Danabasoglu, 2019) and https://doi.org/doi:10.22033/ESGF/CMIP6.8508(Silvers et al., 2018). We accessed all the data via the DKRZ compute cluster Levante. The models were regridded using the Climate Data Operators (CDO) (Schulzweida, 2023), https://doi.org/10.5281/zenodo.10020800. Forcing data is available at https://zenodo.org/records/17065758 (Arcomano et al., 2025). The model outputs are available in the AIMIP Phase 1 data, publicly available via the DKRZ S3 endpoint (Download instructions available in (Henn et al., 2026). Code to convert model outputs into CMOR format as required by AIMIP and to evaluate it successively is available at https://zenodo.org/records/21913147 (Brunstein and Jost, 2026)
Thank you for your time,
Robert and Renu, on behalf of all authors
Citation: https://doi.org/10.5194/egusphere-2026-3782-CC2 -
CEC2: 'Reply on CC2', Juan Antonio Añel, 18 Aug 2026
reply
Dear authors,
Many thanks for your reply. I have checked it, and two issues remain outstanding regarding the compliance with the Code and Data Policy of the journal . First, we can not accept Hugging Face to store assets related to your manuscript. Also, we can not accept future expressions of compliance. The policy of the journal is clear regarding the fact that all the assets relevant for a submission must be published openly and without limitations at the submission time.
Therefore, please, publish the mentioned information in a repository acceptable according to the policy of the journal, and reply to this comment with a new Code and Data Availability section that is in compliance.
I must insist that if you do not fix this problem, we cannot continue with the peer-review process or accept your manuscript for publication in GMD.
Juan A. Añel
Geosci. Model Dev. Executive EditorCitation: https://doi.org/10.5194/egusphere-2026-3782-CEC2
-
CEC2: 'Reply on CC2', Juan Antonio Añel, 18 Aug 2026
reply
Data sets
ERA5 Bill Bell, Hans Hersbach, Adrian Simmons, Paul Berrisford, Per Dahlgren, András Horányi, Joaquín Muñoz-Sabater, Julien Nicolas, Raluca Radu, Dinand Schepers, Cornel Soci, Sebastien Villaume, Jean-Raymond Bidlot, Leo Haimberger, Jack Woollen, Carlo Buontempo, and Jean-Noël Thépaut https://doi.org/10.24381/cds.adbb2d47
AIMIP forcing dataset Troy Arcomano, Brian Henn, and Christopher Bretherton https://doi.org/10.5281/zenodo.16782372
Model code and software
Geoarches Guillaume Couairon, Renu Singh, and Robert Brunstein https://doi.org/10.5281/zenodo.20784770
Interactive computing environment
Geoarches Documentation Renu Singh, Aymeric Delefosse, and Adrien Le Coz https://geoarches.readthedocs.io/en/latest/archesweather/run/
Viewed
Since the preprint corresponding to this journal article was posted outside of Copernicus Publications, the preprint-related metrics are limited to HTML views.
| HTML | XML | Total | BibTeX | EndNote | |
|---|---|---|---|---|---|
| 200 | 0 | 1 | 201 | 0 | 0 |
- HTML: 200
- PDF: 0
- XML: 1
- Total: 201
- BibTeX: 0
- EndNote: 0
Viewed (geographical distribution)
Since the preprint corresponding to this journal article was posted outside of Copernicus Publications, the preprint-related metrics are limited to HTML views.
| Country | # | Views | % |
|---|
| Total: | 0 |
| HTML: | 0 |
| PDF: | 0 |
| XML: | 0 |
- 1
Dear authors,
Unfortunately, after checking your manuscript, it has come to our attention that it does not comply with our "Code and Data Policy".
First, the "Code and Data Availability" section in your manuscript points to some GitHub sites. However, GitHub is not a suitable repository for scientific publication. GitHub itself instructs authors to use other long-term archival and publishing alternatives, such as Zenodo. Internally in the system, you have shared several repositories and sites containing additional information. The problem here is that the mentioned information is not available for Discussions, as it should be, and openly available.
The GMD review and publication process depends on reviewers and community commentators being able to access, during the discussion phase, the code and data on which a manuscript depends, and on ensuring the provenance of replicability of the published papers for years after their publication. Therefore, I am publishing here the information shared internally to the editors so that all the readers have access to it, and the Discussions stage is developed with guarantees:
I must note that if you do not fix this problem, we cannot accept your manuscript for publication in GMD.
Juan A. Añel
Geosci. Model Dev. Executive Editor