Articles | Volume 18, issue 22
https://doi.org/10.5194/gmd-18-8751-2025
© Author(s) 2025. This work is distributed under the Creative Commons Attribution 4.0 License.
Autoencoder-based feature extraction for the automatic detection of snow avalanches in seismic data
Download
- Final revised paper (published on 20 Nov 2025)
- Preprint (discussion started on 27 May 2024)
Interactive discussion
Status: closed
Comment types: AC – author | RC – referee | CC – community | EC – editor | CEC – chief editor
| : Report abuse
-
CEC1: 'Comment on gmd-2024-76', Juan Antonio Añel, 15 Jun 2024
- AC1: 'Reply on CEC1', Andri Simeon, 21 Jun 2024
-
RC1: 'Comment on gmd-2024-76', Anonymous Referee #1, 15 Jul 2024
- AC2: 'Reply on RC1', Andri Simeon, 28 Aug 2024
-
RC2: 'Comment on gmd-2024-76', Anonymous Referee #2, 27 Jul 2024
- AC3: 'Reply on RC2', Andri Simeon, 28 Aug 2024
Peer review completion
AR – Author's response | RR – Referee report | ED – Editor decision | EF – Editorial file upload
AR by Andri Simeon on behalf of the Authors (11 Sep 2024)
Author's response
Author's tracked changes
Manuscript
ED: Referee Nomination & Report Request started (05 Oct 2024) by Le Yu
RR by Anonymous Referee #3 (24 Oct 2024)
RR by Tate Meehan (08 Jan 2025)
RR by Kevin Hank (13 Jan 2025)
RR by Anonymous Referee #6 (01 Feb 2025)
ED: Reconsider after major revisions (06 Feb 2025) by Le Yu
AR by Andri Simeon on behalf of the Authors (19 Mar 2025)
Author's response
Author's tracked changes
Manuscript
ED: Referee Nomination & Report Request started (27 May 2025) by Le Yu
RR by Anonymous Referee #3 (04 Jun 2025)
RR by Anonymous Referee #6 (11 Jun 2025)
RR by Tate Meehan (02 Jul 2025)
ED: Publish subject to minor revisions (review by editor) (19 Aug 2025) by Le Yu
AR by Andri Simeon on behalf of the Authors (25 Aug 2025)
Author's response
Author's tracked changes
Manuscript
ED: Publish as is (09 Oct 2025) by Le Yu
AR by Andri Simeon on behalf of the Authors (14 Oct 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
The problem is that you have not published the code and data necessary to replicate your manuscript. Our policy clearly states that all the code and data used in a manuscript must be published at the submission time in one of the acceptable repositories listed in our policy, and that the Code and Data Availability section must contain the details (links and DOIs) for such repositories. Instead this section in your manuscript reads "The code and data to develop the final models used in this study will be made available on GitLab and EnviDat"
You have provided internally a internet address containing part of these assets (not all of them, according to my understanding). This is not enough. First, the WSL server is not a repository that complies with the standards required for scientific publication; second, all the information must be available to every potential reader in Discussions to facilitate the peer-review and comments by the community, and sharing it privately with the editors fails to comply with the Discussions peer-review process.
Therefore, please, publish your code in one of the appropriate repositories, and reply to this comment with the relevant information (link and DOI) as soon as possible, as we can not accept manuscripts in Discussions that do not comply with our policy. Therefore, the current situation with your manuscript is irregular.
In this way, if you do not fix this problem, we will have to reject your manuscript for publication in our journal.
Also, you must include in a potentially reviewed version of your manuscript the modified 'Code and Data Availability' section, containing the links and DOI of the repository containing code and data.
Finally, in the current git that you have provided for the assets, there is no license listed. If you do not include a license, the code is not "free software/open-source"; it continues to be your property and nobody can use it, despite you make it public. Therefore, when uploading the code and data to the new repository, you should add a license. 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 acceptable repositories provide: GPLv2, Apache License, MIT License, etc.
Juan A. Añel
Geosci. Model Dev. Executive Editor