the Creative Commons Attribution 4.0 License.
the Creative Commons Attribution 4.0 License.
Applying Corrective Machine Learning in the E3SM Atmosphere Model in C++ (EAMxx)
Abstract. The Simplified Cloud-Resolving E3SM Atmosphere Model (SCREAM) is the newest addition to the family of earth system models capable of explicitly resolving convective systems. SCREAM is a kilometer-scale configuration of the advanced E3SM Atmosphere Model (EAMxx), designed for heterogeneous systems. While the enhanced accuracy of kilometer-scale modeling offers significant benefits, it comes with a substantial computational cost, limiting feasible simulation durations to only a few years, even on the fastest supercomputers. Machine learning presents an opportunity for scientists to achieve the high accuracy of storm-resolving models at a significantly reduced cost. Building on the previous success of applying corrective machine learning (ML) to the FV3 model, this study explores the effects of implementing corrective ML in EAMxx-SCREAM. We also address the computational challenges of integrating our implementation of corrective ML, which is written in Python, with the C++/Kokkos EAMxx driver, as well as potential reasons why this approach has not proved as effective for EAMxx-SCREAM as for the FV3 model.
Competing interests: Some authors are members of the editorial board of journal GMD.
Publisher's note: Copernicus Publications remains neutral with regard to jurisdictional claims made in the text, published maps, institutional affiliations, or any other geographical representation in this paper. While Copernicus Publications makes every effort to include appropriate place names, the final responsibility lies with the authors. Views expressed in the text are those of the authors and do not necessarily reflect the views of the publisher.- Preprint
(2648 KB) - Metadata XML
- BibTeX
- EndNote
Status: open (until 04 Dec 2025)
-
CEC1: 'No compliance with the policy of the journal', Juan Antonio Añel, 11 Oct 2025
reply
-
CC1: 'Reply on CEC1', Aaron Donahue, 28 Oct 2025
reply
My apologies for submitting a manuscript that did not adhere to the code and data availability requirements of the manuscript. I have taken measures to publish the data and the software used in this manuscript to the acceptable manuscripts. In response to the editor comments:
1) The software is available for download via Zenodo with the DOI of https://doi.org/10.5281/zenodo.17469329
2) The data is available for download via Zenodo with the DOI of https://doi.org/10.5281/zenodo.17469234
3) I no longer reference the Terai et al. paper for instructions on accessing the data from that study. Instead readers are directed to the following zenodo doi's: https://doi.org/10.5281/zenodo.14579433 and https://doi.org/10.5281/zenodo.14578966
This is all reflected in an updated Code and Data Availability section that I can submit as a revision to the paper if requested.
Citation: https://doi.org/10.5194/egusphere-2025-3883-CC1
-
CC1: 'Reply on CEC1', Aaron Donahue, 28 Oct 2025
reply
Viewed
| HTML | XML | Total | BibTeX | EndNote | |
|---|---|---|---|---|---|
| 960 | 31 | 10 | 1,001 | 6 | 5 |
- HTML: 960
- PDF: 31
- XML: 10
- Total: 1,001
- BibTeX: 6
- EndNote: 5
Viewed (geographical distribution)
| 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".
https://www.geoscientific-model-development.net/policies/code_and_data_policy.html
First, you have archived part of your code on GitHub. However, GitHub is not a suitable repository for scientific publication. GitHub itself instructs authors to use other long-term archival and publishing alternatives. Additionally, you have not made the data used in your manuscript (all input and output data) publicly available, instead linking to sites such as nersc.gov or previous publications to access some of it. Given all these shortcomings, your manuscript should not have been accepted for Discussions and peer review.
Therefore, the current situation with your manuscript is irregular. Please, publish all your code and data in one of the appropriate repositories and reply to this comment with the relevant information (link and a permanent identifier for it (e.g., DOI)) as soon as possible, as we can not accept manuscripts in Discussions that do not comply with our policy.Â
Also, you must include a modified 'Code and Data Availability' section in a potentially reviewed manuscript, containing the information of the new repositories.
Given that no reviewer has been secured for your manuscript yet, I advise the Topical Editor to refrain from inviting reviewers or taking any action on your submission until the issues with the code and data have been adequately addressed and resolved.
Juan A. Añel
Geosci. Model Dev. Executive Editor