Articles | Volume 15, issue 4
© Author(s) 2022. This work is distributed underthe Creative Commons Attribution 4.0 License.
CSDMS: a community platform for numerical modeling of Earth surface processes
- Final revised paper (published on 17 Feb 2022)
- Preprint (discussion started on 13 Jul 2021)
Comment types: AC – author | RC – referee | CC – community | EC – editor | CEC – chief editor |
: Report abuse
- RC1: 'Comment on gmd-2021-223', Anonymous Referee #1, 16 Aug 2021
- RC2: 'Comment on gmd-2021-223', Anonymous Referee #2, 07 Nov 2021
- AC1: 'Author response to review comments', Gregory Tucker, 28 Dec 2021
- EC1: 'Proceed to revised manuscript', Andrew Wickert, 02 Jan 2022
Peer review completion
AR: Author's response | RR: Referee report | ED: Editor decision
AR by Gregory Tucker on behalf of the Authors (03 Jan 2022)  Author's response Author's tracked changes Manuscript
ED: Publish subject to technical corrections (06 Jan 2022) by Andrew Wickert
AR by Gregory Tucker on behalf of the Authors (14 Jan 2022)  Author's response Manuscript
This paper has two purposes – to inform the reader about activities of the CSDMS and to describe the tools and standards developed for model interoperability.
Line 94: I am unclear what the analogy the quote is trying to draw.
Line 143: The reviews for JOSS journals are objective reviews set against a checklist of items. Reviewers check for what the authors says it does. Do they inspect the software code itself, that is “evaluate the software directly”?
Figure 2: Include a descriptive figure caption.
Line 241: Strictly speaking, reproducing needs an executable, not necessarily the source code.
Line 244: FAIR data need a persistent identifier such as a DOI.
Figure 3. Include a descriptive figure caption.
Line 347: What happens in the interpolation when there is a first order discontinuity?
Line 360: What happens when the timesteps are not multiples of one another?
Figure 13: Clarify that c. and d. are with the “with landsliding” model
Line 580: Sentences is awkward. Librarization of tools to access data sets not librarization of the data sets themselves.
Review usage of title case in section and subsection headings for consistency
For inline text, use Fig. or Figure consistently. Similarly for figure referenced in parens, ()
Figure 1: Many of the labels on the figures are hard to read at 100% magnification
For citing PETSc, see:
deal.II (not capitalized)
For citing deal.II, see:
Line 279, 359: Are contractions allowed?
Line 295: References Fig. 6 before referencing Fig. 5 (and not referenced elsewhere)
Table 3. Change Table caption to: “… Python Modeling Toolkit pymt.”
All models are capitalized here but may be used as lowercase in text. Theses should be consistent.
Line 384: (Fig. 2). Should this be deleted?
Figure 1 and Figure 13: Descriptions use a syntax of referring to the different panels e.g,. a. vs (a)
Figure 13: Sediment thickness is plotted as soil depth as a yellow and not an orange line according to the legend.
Figure 14: Technically there is no “(b)” so should there be an “(a)”?
Figure 15: Define EKT
Line 614: Define ESPIN
Line 618: CoMSES Net
Line 619: pyOpenSci