Articles | Volume 18, issue 21
https://doi.org/10.5194/gmd-18-8313-2025
© Author(s) 2025. This work is distributed under the Creative Commons Attribution 4.0 License.
Bias correcting regional scale Earth system model projections: novel approach using empirical mode decomposition
Download
- Final revised paper (published on 06 Nov 2025)
- Preprint (discussion started on 27 Mar 2025)
Interactive discussion
Status: closed
Comment types: AC – author | RC – referee | CC – community | EC – editor | CEC – chief editor
| : Report abuse
-
CEC1: 'Comment on egusphere-2025-1112 - No compliance with the policy of the journal', Juan Antonio Añel, 08 Apr 2025
-
AC1: 'Reply on CEC1', Arkaprabha Ganguli, 19 Apr 2025
-
CEC2: 'Reply on AC1', Juan Antonio Añel, 19 Apr 2025
-
AC2: 'Reply on CEC2', Arkaprabha Ganguli, 24 Apr 2025
-
CEC3: 'Reply on AC2', Juan Antonio Añel, 24 Apr 2025
-
AC3: 'Reply on CEC3', Arkaprabha Ganguli, 25 Apr 2025
- CEC4: 'Reply on AC3 - No compliance with the policy of the journal', Juan Antonio Añel, 09 May 2025
-
AC3: 'Reply on CEC3', Arkaprabha Ganguli, 25 Apr 2025
-
CEC3: 'Reply on AC2', Juan Antonio Añel, 24 Apr 2025
-
AC2: 'Reply on CEC2', Arkaprabha Ganguli, 24 Apr 2025
-
CEC2: 'Reply on AC1', Juan Antonio Añel, 19 Apr 2025
-
AC1: 'Reply on CEC1', Arkaprabha Ganguli, 19 Apr 2025
-
RC1: 'Comment on egusphere-2025-1112', Anonymous Referee #1, 12 Jun 2025
- AC4: 'Reply on RC1', Arkaprabha Ganguli, 28 Jun 2025
-
RC2: 'Comment on egusphere-2025-1112', Anonymous Referee #2, 23 Jun 2025
- AC5: 'Reply on RC2', Arkaprabha Ganguli, 09 Jul 2025
- AC6: 'Comment on egusphere-2025-1112', Arkaprabha Ganguli, 11 Jul 2025
Peer review completion
AR: Author's response | RR: Referee report | ED: Editor decision | EF: Editorial file upload
AR by Arkaprabha Ganguli on behalf of the Authors (04 Aug 2025)
Author's response
Author's tracked changes
Manuscript
ED: Referee Nomination & Report Request started (05 Aug 2025) by Stefan Rahimi-Esfarjani
RR by Anonymous Referee #2 (19 Sep 2025)
RR by Anonymous Referee #3 (22 Sep 2025)
ED: Publish as is (22 Sep 2025) by Stefan Rahimi-Esfarjani
AR by Arkaprabha Ganguli on behalf of the Authors (30 Sep 2025)
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
You have archived your code on a Git site in a server hosted by the Argonne National Laboratory. However, it is not a suitable repository for scientific publication and as a result your manuscript does not comply with the policy of our journal. Therefore, the current situation with your manuscript is irregular, as we can not accept manuscripts in Discussions that do not comply with our policy.
We ask you to publish your code in one of the appropriate repositories listed in our policy and reply to this comment with the relevant information (link and a permanent identifier for it (e.g. DOI)) as soon as possible.
Something similar applies to the data. You have not published the necessary specific data to replicate the work presented in your manuscript, but simply point out to a data portal hosted by the ANL. We can not accept it, first, because again it is not a suitable repository for scientific publication; Secondly, because it does not identify clearly the exact data that you have used, making hard to get access to it for readers. Therefore, you must deposit the necessary input and output data from your work in one of the suitable repositories, and reply to this comment with the relevant information (again, link and permanent identifier).
Also, you must include a modified 'Code and Data Availability' section in a potentially reviewed manuscript, containing the information for the new repositories. Also, I have to note that the Git site for the Python scripts does not have a license listed. If you do not include a license the code remains your property, and nobody can use it. Therefore, when uploading your code to the repository, please, choose a free software/open-source (FLOSS) license. For example, if you use the GPLv3 you simply need to include the file 'https://www.gnu.org/licenses/gpl-3.0.txt' as LICENSE.txt with your code. Also, you can choose other options such as: GPLv2, Apache License, MIT License, etc.
Finally, I have to note that if you do not fix this problem, we will have to reject your manuscript for publication in our journal.
Juan A. Añel
Geosci. Model Dev. Executive Editor