Articles | Volume 17, issue 9
https://doi.org/10.5194/gmd-17-3733-2024
© Author(s) 2024. This work is distributed under the Creative Commons Attribution 4.0 License.
Terrestrial Ecosystem Model in R (TEMIR) version 1.0: simulating ecophysiological responses of vegetation to atmospheric chemical and meteorological changes
Download
- Final revised paper (published on 08 May 2024)
- Supplement to the final revised paper
- Preprint (discussion started on 14 Jul 2023)
- Supplement to the preprint
Interactive discussion
Status: closed
Comment types: AC – author | RC – referee | CC – community | EC – editor | CEC – chief editor
| : Report abuse
-
CEC1: 'Comment on egusphere-2023-1287', Juan Antonio Añel, 03 Aug 2023
- AC1: 'Reply on CEC1', Amos Tai, 04 Aug 2023
- RC1: 'Comment on egusphere-2023-1287', Anonymous Referee #1, 21 Sep 2023
- RC2: 'Comment on egusphere-2023-1287', Anonymous Referee #2, 30 Sep 2023
- AC2: 'Comment on egusphere-2023-1287', Amos Tai, 09 Jan 2024
Peer review completion
AR: Author's response | RR: Referee report | ED: Editor decision | EF: Editorial file upload
AR by Amos Tai on behalf of the Authors (09 Jan 2024)
Author's response
Author's tracked changes
Manuscript
ED: Referee Nomination & Report Request started (10 Jan 2024) by Christoph Müller
RR by Anonymous Referee #2 (19 Jan 2024)
RR by Anonymous Referee #1 (02 Feb 2024)
ED: Publish as is (12 Feb 2024) by Christoph Müller
AR by Amos Tai on behalf of the Authors (16 Feb 2024)
Post-review adjustments
AA: Author's adjustment | EA: Editor approval
AA by Amos Tai on behalf of the Authors (06 May 2024)
Author's adjustment
Manuscript
EA: Adjustments approved (07 May 2024) by Christoph Müller
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
Actually, it contains several flaws regarding our policy, and your manuscript should not have been accepted in Discussions, given this lack of compliance. Therefore, the current situation with your manuscript is irregular. In this way, if you do not fix the issues listed next, we will have to reject your manuscript for publication in our journal.
First, as the handling topical editor pointed out earlier, your code repository does not include a license. If you do not include a license, the code continues to be your property, and nobody can use it. Therefore, it is not possible to test or replicate your work. In this way, you must add a license to your repository. You could want to choose a free software/open-source (FLOSS) license. We recommend the GPLv3. You only 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 that Zenodo provides: GPLv2, Apache License, MIT License, etc.
Second, the instructions to execute your code include links to repositories that we do not accept. Again, please, check our policy. Some of them even request a password that it is said needs to be obtained by contacting by email. Our policy is crystal clear that all the assets used to produce the submitted work must be published openly and publicly at submission time and that the need to request access is not acceptable. Therefore, all the input data necessary for your work and the output data generated during your experiments must be published in a repository that we accept according to our policy.
I note here, too, that your manuscript does not even contain a "Data availability" section.
Therefore, please, add a license to your code, publish your data in one of the appropriate repositories, and reply to this comment with the relevant information (link and DOI) as soon as possible, as it should be available before the Discussions stage.
Also, you must include in a potentially reviewed version of your manuscript the new 'Data Availability' section and the DOI of the repository.