[REVIEW]: MOTrainer: Distributed Measurement Operator Trainer for Data Assimilation Applications

[editorialbot]

Submitting author: @rogerkuou (Ou Ku)
Repository: https://github.com/VegeWaterDynamics/motrainer
Branch with paper.md (empty if default branch):
Version: v0.1.3
Editor: @srmnitc
Reviewers: @abhishektiwari, @KwickSilver
Archive: Pending

Status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/0ec1cefe66e3d09476dad0fe3b918c35"><img src="https://joss.theoj.org/papers/0ec1cefe66e3d09476dad0fe3b918c35/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/0ec1cefe66e3d09476dad0fe3b918c35/status.svg)](https://joss.theoj.org/papers/0ec1cefe66e3d09476dad0fe3b918c35)

Reviewers and authors:

Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)

Reviewer instructions & questions

@abhishektiwari & @KwickSilver, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review.
First of all you need to run this command in a separate comment to create the checklist:

@editorialbot generate my checklist

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @srmnitc know.

✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨

Checklists

📝 Checklist for @abhishektiwari

📝 Checklist for @KwickSilver

[editorialbot]

Hello humans, I'm @editorialbot, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@editorialbot commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@editorialbot generate pdf

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1109/JSTARS.2014.2325780 is OK
- 10.1080/02723646.2016.1236606 is OK
- 10.5334/jors.148 is OK

MISSING DOIs

- No DOI given, and none found for title: Hydrologic Analysis and Design
- 10.25080/majora-7b98e3ed-013 may be a valid DOI for title: Dask: Parallel Computation with Blocked algorithms...

INVALID DOIs

- https://doi.org/10.1016/j.rse.2022.113116 is INVALID because of 'https://doi.org/' prefix
- https://doi.org/10.1016/j.rse.2015.09.009 is INVALID because of 'https://doi.org/' prefix

[editorialbot]

Software report:

github.com/AlDanial/cloc v 1.90  T=0.03 s (1411.9 files/s, 227817.3 lines/s)
--------------------------------------------------------------------------------
Language                      files          blank        comment           code
--------------------------------------------------------------------------------
Python                           12            241            331            904
Markdown                         12            179              0            445
Jupyter Notebook                  6              0           4309            298
YAML                              6             17              7            156
TOML                              1             16              6            128
TeX                               1              7              0             76
Bourne Shell                      1             10              5             48
JSON                              4              0              0             47
Bourne Again Shell                1              5              4             11
HTML                              1              2              0              9
--------------------------------------------------------------------------------
SUM:                             45            477           4662           2122
--------------------------------------------------------------------------------

Commit count by author:

   117	rogerkuou
    88	Ou Ku
    37	SarahAlidoost
    22	xushanthu-2014
     1	Meiert Grootes
     1	cpranav93

[editorialbot]

Paper file info:

📄 Wordcount for paper.md is 555

✅ The paper includes a Statement of need section

[editorialbot]

License info:

✅ License found: Apache License 2.0 (Valid open source OSI approved license)

[editorialbot]

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

[srmnitc]

👋🏼 @rogerkuou @abhishektiwari @KwickSilver this is the review thread for the paper. All of our communications will happen here from now on.

As you might know, as a reviewer, the first step is to create a checklist for your review by entering

@editorialbot generate my checklist

as the top of a new comment in this thread.

These checklists contain the JOSS requirements. As you go over the submission, please check any items that you feel have been satisfied. The first comment in this thread also contains links to the JOSS reviewer guidelines.

The JOSS review is different from most other journals. Our goal is to work with the authors to help them meet our criteria instead of merely passing judgment on the submission. As such, the reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention openjournals/joss-reviews#REVIEW_NUMBER so that a link is created to this thread (and I can keep an eye on what is happening). Please also feel free to comment and ask questions on this thread. In my experience, it is better to post comments/questions/suggestions as you come across them instead of waiting until you've reviewed the entire package.

We aim for reviews to be completed within about 2-4 weeks. Please let me know if any of you require some more time. We can also use EditorialBot (our bot) to set automatic reminders if you know you'll be away for a known period of time.

Please feel free to ping me (@srmnitc ) if you have any questions/concerns, thanks again for the submission, and for thr reviews

[KwickSilver]

Hi Sarath, Apologies for my delayed response; I haven't been able to start reviewing the journal yet. I plan to begin tomorrow and aim to complete it by the end of this month. Does this timeline work for you? Thanks, Shantanu

…

On Mon, 8 Apr 2024 at 04:47, Sarath Menon ***@***.***> wrote: 👋🏼 @rogerkuou <https://github.com/rogerkuou> @abhishektiwari <https://github.com/abhishektiwari> @KwickSilver <https://github.com/KwickSilver> this is the review thread for the paper. All of our communications will happen here from now on. As you might know, as a reviewer, the first step is to create a checklist for your review by entering @editorialbot <https://github.com/editorialbot> generate my checklist as the top of a new comment in this thread. These checklists contain the JOSS requirements. As you go over the submission, please check any items that you feel have been satisfied. The first comment in this thread also contains links to the JOSS reviewer guidelines. The JOSS review is different from most other journals. Our goal is to work with the authors to help them meet our criteria instead of merely passing judgment on the submission. As such, the reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention openjournals/joss-reviews#REVIEW_NUMBER so that a link is created to this thread (and I can keep an eye on what is happening). Please also feel free to comment and ask questions on this thread. In my experience, it is better to post comments/questions/suggestions as you come across them instead of waiting until you've reviewed the entire package. We aim for reviews to be completed within about 2-4 weeks. Please let me know if any of you require some more time. We can also use EditorialBot (our bot) to set automatic reminders if you know you'll be away for a known period of time. Please feel free to ping me ***@***.*** <https://github.com/srmnitc> ) if you have any questions/concerns, thanks again for the submission, and for thr reviews — Reply to this email directly, view it on GitHub <#6591 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABCUHHJ5AU25RZTRQPVGMKDY4J7VBAVCNFSM6AAAAABF4RFJNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBSGUZTQOBYGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[srmnitc]

Hi Sarath, Apologies for my delayed response; I haven't been able to start reviewing the journal yet. I plan to begin tomorrow and aim to complete it by the end of this month. Does this timeline work for you? Thanks, Shantanu
…
On Mon, 8 Apr 2024 at 04:47, Sarath Menon @.> wrote: 👋🏼 @rogerkuou https://github.com/rogerkuou @abhishektiwari https://github.com/abhishektiwari @KwickSilver https://github.com/KwickSilver this is the review thread for the paper. All of our communications will happen here from now on. As you might know, as a reviewer, the first step is to create a checklist for your review by entering @editorialbot https://github.com/editorialbot generate my checklist as the top of a new comment in this thread. These checklists contain the JOSS requirements. As you go over the submission, please check any items that you feel have been satisfied. The first comment in this thread also contains links to the JOSS reviewer guidelines. The JOSS review is different from most other journals. Our goal is to work with the authors to help them meet our criteria instead of merely passing judgment on the submission. As such, the reviewers are encouraged to submit issues and pull requests on the software repository. When doing so, please mention openjournals/joss-reviews#REVIEW_NUMBER so that a link is created to this thread (and I can keep an eye on what is happening). Please also feel free to comment and ask questions on this thread. In my experience, it is better to post comments/questions/suggestions as you come across them instead of waiting until you've reviewed the entire package. We aim for reviews to be completed within about 2-4 weeks. Please let me know if any of you require some more time. We can also use EditorialBot (our bot) to set automatic reminders if you know you'll be away for a known period of time. Please feel free to ping me @. https://github.com/srmnitc ) if you have any questions/concerns, thanks again for the submission, and for thr reviews — Reply to this email directly, view it on GitHub <#6591 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABCUHHJ5AU25RZTRQPVGMKDY4J7VBAVCNFSM6AAAAABF4RFJNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBSGUZTQOBYGM . You are receiving this because you were mentioned.Message ID: @.***>

@KwickSilver that is fine, thanks for the update!

[srmnitc]

@abhishektiwari hi! just a short reminder about the review, do you need anything from our side to get started?

[abhishektiwari]

Review checklist for @abhishektiwari

Conflict of interest

• I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

• I confirm that I read and will adhere to the JOSS code of conduct.

General checks

• Repository: Is the source code for this software available at the https://github.com/VegeWaterDynamics/motrainer?
• License: Does the repository contain a plain-text LICENSE or COPYING file with the contents of an OSI approved software license?
• Contribution and authorship: Has the submitting author (@rogerkuou) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
• Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
• Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
• Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
• Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

Functionality

• Installation: Does installation proceed as outlined in the documentation?
• Functionality: Have the functional claims of the software been confirmed?
• Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
• Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
• Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
• Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
• Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

• Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
• A statement of need: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
• State of the field: Do the authors describe how this software compares to other commonly-used packages?
• Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
• References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

[abhishektiwari]

@rogerkuou Initial feedback,

1. Update installation instruction as raised here
2. Provide details on example data generation script here
3. Add community/contributing guidelines as mentioned here

Once you have fixed these, let us know in comments here so I can verify functional claims.

[rogerkuou]

Thx @abhishektiwari for the feedback! Sorry for the late reply, just came back from a holiday. I will work on them in the coming days, and will let you know when it's done.

[srmnitc]

@KwickSilver hi! just a short reminder from my side for the review here.

[KwickSilver]

@srmnitc Apologies for the delay. Due to competing priorities, I was unable to allocate sufficient time for the review as promptly as I had intended. However, I will commence the review process without further delay.

[KwickSilver]

Review checklist for @KwickSilver

Conflict of interest

• I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

• I confirm that I read and will adhere to the JOSS code of conduct.

General checks

• Repository: Is the source code for this software available at the https://github.com/VegeWaterDynamics/motrainer?
• License: Does the repository contain a plain-text LICENSE or COPYING file with the contents of an OSI approved software license?
• Contribution and authorship: Has the submitting author (@rogerkuou) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
• Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
• Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
• Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
• Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

Functionality

• Installation: Does installation proceed as outlined in the documentation?
• Functionality: Have the functional claims of the software been confirmed?
• Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
• Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
• Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
• Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
• Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

• Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
• A statement of need: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
• State of the field: Do the authors describe how this software compares to other commonly-used packages?
• Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
• References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

[srmnitc]

@srmnitc Apologies for the delay. Due to competing priorities, I was unable to allocate sufficient time for the review as promptly as I had intended. However, I will commence the review process without further delay.

Thanks for your quick reply!