Articles | Volume 19, issue 11
https://doi.org/10.5194/gmd-19-4763-2026
© Author(s) 2026. This work is distributed under the Creative Commons Attribution 4.0 License.
Applying corrective machine learning in the E3SM atmosphere model in C+ + (EAMxx)
Download
- Final revised paper (published on 03 Jun 2026)
- Preprint (discussion started on 17 Sep 2025)
Interactive discussion
Status: closed
Comment types: AC – author | RC – referee | CC – community | EC – editor | CEC – chief editor
| : Report abuse
-
CEC1: 'No compliance with the policy of the journal', Juan Antonio Añel, 11 Oct 2025
-
CC1: 'Reply on CEC1', Aaron Donahue, 28 Oct 2025
-
CEC2: 'Reply on CC1', Juan Antonio Añel, 30 Oct 2025
- AC1: 'Reply on CEC2', Aaron Donahue, 19 Nov 2025
-
CEC2: 'Reply on CC1', Juan Antonio Añel, 30 Oct 2025
-
CC1: 'Reply on CEC1', Aaron Donahue, 28 Oct 2025
-
RC1: 'Comment on egusphere-2025-3883', Anonymous Referee #1, 04 Dec 2025
- AC2: 'Reply on RC1', Aaron Donahue, 21 Apr 2026
-
RC2: 'Comment on egusphere-2025-3883', Anonymous Referee #2, 03 Feb 2026
- AC3: 'Reply on RC2', Aaron Donahue, 21 Apr 2026
Peer review completion
AR – Author's response | RR – Referee report | ED – Editor decision | EF – Editorial file upload
AR by Aaron Donahue on behalf of the Authors (21 Apr 2026)
Author's response
Author's tracked changes
Manuscript
ED: Publish as is (11 May 2026) by Olivier Marti
AR by Aaron Donahue on behalf of the Authors (11 May 2026)
Author's response
Manuscript
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