[REVIEW]: simode: R Package for Statistical Inference of Ordinary Differential Equations using Separable Integral-Matching

whedon commented 5 years ago

Submitting author: @ramiyaari (Rami Yaari) Repository: https://github.com/ramiyaari/simode/ Version: v1.1.8 Editor: @mjsottile Reviewer: @cscherrer, @jgoldfar, @osorensen Archive: 10.5281/zenodo.3576265

Status

Status badge code:

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

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

@cscherrer & @jgoldfar & @osorensen, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:

Make sure you're logged in to your GitHub account
Be sure to accept the invite at this URL: https://github.com/openjournals/joss-reviews/invitations

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

✨ Please try and complete your review in the next two weeks ✨

Review checklist for @cscherrer

Conflict of interest

[x] 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

[x] I confirm that I read and will adhere to the JOSS code of conduct.

General checks

[x] Repository: Is the source code for this software available at the repository url?
[x] License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
[x] Contribution and authorship: Has the submitting author (@ramiyaari) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?

Functionality

[x] Installation: Does installation proceed as outlined in the documentation?
[x] Functionality: Have the functional claims of the software been confirmed?
[x] 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

[x] A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
[x] Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
[x] Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
[x] Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
[x] Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
[x] 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

[x] Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
[x] A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
[x] State of the field: Do the authors describe how this software compares to other commonly-used packages?
[x] Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
[x] 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?

Review checklist for @jgoldfar

Conflict of interest

[x] 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

[x] I confirm that I read and will adhere to the JOSS code of conduct.

General checks

[x] Repository: Is the source code for this software available at the repository url?
[x] License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
[x] Contribution and authorship: Has the submitting author (@ramiyaari) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?

Functionality

[x] Installation: Does installation proceed as outlined in the documentation?
[x] Functionality: Have the functional claims of the software been confirmed?
[x] 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

[x] A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
[x] Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
[x] Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
[x] Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
[x] Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
[x] 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

[x] Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
[x] A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
[x] State of the field: Do the authors describe how this software compares to other commonly-used packages?
[x] Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
[x] 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?

Review checklist for @osorensen

Conflict of interest

[x] 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

[x] I confirm that I read and will adhere to the JOSS code of conduct.

General checks

[x] Repository: Is the source code for this software available at the repository url?
[x] License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
[x] Contribution and authorship: Has the submitting author (@ramiyaari) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?

Functionality

[x] Installation: Does installation proceed as outlined in the documentation?
[x] Functionality: Have the functional claims of the software been confirmed?
[x] 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

[x] A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
[x] Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
[x] Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
[x] Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
[x] Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
[x] 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

[x] Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
[x] A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
[x] State of the field: Do the authors describe how this software compares to other commonly-used packages?
[x] Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
[x] 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?

whedon commented 5 years ago

Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @cscherrer, @jgoldfar, @osorensen it looks like you're currently assigned to review this paper :tada:.

:star: Important :star:

If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/openjournals/joss-reviews) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews 😿

To fix this do the following two things:

Set yourself as 'Not watching' https://github.com/openjournals/joss-reviews:

watching

You may also like to change your default settings for this watching repositories in your GitHub profile here: https://github.com/settings/notifications

notifications

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

@whedon commands

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

@whedon generate pdf

whedon commented 5 years ago

Attempting PDF compilation. Reticulating splines etc...

whedon commented 5 years ago

:point_right: Check article proof :page_facing_up: :point_left:

cscherrer commented 4 years ago

https://github.com/ramiyaari/simode/issues/5

osorensen commented 4 years ago

@whedon generate pdf

whedon commented 4 years ago

Attempting PDF compilation. Reticulating splines etc...

whedon commented 4 years ago

:point_right: Check article proof :page_facing_up: :point_left:

ramiyaari commented 4 years ago

@whedon generate pdf

whedon commented 4 years ago

Attempting PDF compilation. Reticulating splines etc...

whedon commented 4 years ago

:point_right: Check article proof :page_facing_up: :point_left:

mjsottile commented 4 years ago

It looks like we only have a couple boxes to check in the review checklists above. @cscherrer and @jgoldfar - can you take a look at the remaining items on your checklists to see if they have been addressed to your satisfaction?

jgoldfar commented 4 years ago

Done

mjsottile commented 4 years ago

@ramiyaari it looks like the review checklists are complete. I will look everything over in a few days when I return from travel and see what the next steps are.

mjsottile commented 4 years ago

Can the reviewers @cscherrer, @jgoldfar, @osorensen confirm their recommendation to accept the submission by responding in this thread?

Also, @ramiyaari - I see that there is a pull request still waiting for a documentation correction. Can you address that and close the open pull request?

osorensen commented 4 years ago

@mjsottile , I confirm my recommendation.

ramiyaari commented 4 years ago

Thanks @mjsottile . I've merged the pull request.

jgoldfar commented 4 years ago

@mjsottile I confirm my recommendation

On Dec 6, 2019, at 5:14 PM, Matthew Sottile notifications@github.com wrote:

Can the reviewers @cscherrer https://github.com/cscherrer, @jgoldfar https://github.com/jgoldfar, @osorensen https://github.com/osorensen confirm their recommendation to accept the submission by responding in this thread?

Also, @ramiyaari https://github.com/ramiyaari - I see that there is a pull request still waiting for a documentation correction. Can you address that and close the open pull request?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/1850?email_source=notifications&email_token=ABKORGOJL6KUGXCS5KJP42DQXLFFJA5CNFSM4JHAS3YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGFPYXI#issuecomment-562756701, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABKORGIYWZHNNWKEXKZ7PETQXLFFJANCNFSM4JHAS3YA.

cscherrer commented 4 years ago

Sorry I had missed this. Yes, I confirm my recommendation

mjsottile commented 4 years ago

@whedon generate pdf

whedon commented 4 years ago

Attempting PDF compilation. Reticulating splines etc...

whedon commented 4 years ago

:point_right: Check article proof :page_facing_up: :point_left:

mjsottile commented 4 years ago

@whedon check references

whedon commented 4 years ago

Attempting to check references...

whedon commented 4 years ago


OK DOIs

- 10.18637/jss.v033.i09 is OK
- 10.1177/0962280217746443 is OK
- 10.1214/15-EJS1053 is OK

MISSING DOIs

- https://doi.org/10.1371/journal.pcbi.1004012 may be missing for title: 150 years of the mass action law
- https://doi.org/10.1098/rsif.2016.0525 may be missing for title: Modelling and parameter inference of predator–prey dynamics in heterogeneous environments using the direct integral approach
- https://doi.org/10.1016/j.spl.2017.08.013 may be missing for title: Consistency of direct integral estimator for partially observed systems of ordinary differential equations
- https://doi.org/10.1111/stan.12124 may be missing for title: Application of one-step method to parameter estimation in ODE models
- https://doi.org/10.18637/jss.v075.i02 may be missing for title: CollocInfer: Collocation Inference in Differential Equation Models
- https://doi.org/10.1007/s11222-014-9486-9 may be missing for title: Time-course window estimator for ordinary differential equations linear in the parameters
- https://doi.org/10.1111/biom.12348 may be missing for title: A model-based initial guess for estimating parameters in systems of ordinary differential equations
- https://doi.org/10.1098/rsif.2010.0412 may be missing for title: Parameterizing state–space models for infectious disease dynamics by generalized profiling: measles in Ontario
- https://doi.org/10.1016/j.jmva.2008.03.005 may be missing for title: Statistical properties of the Hough transform estimator in the presence of measurement errors
- https://doi.org/10.1111/j.1541-0420.2008.01172.x may be missing for title: Forcing function diagnostics for nonlinear dynamics
- https://doi.org/10.1093/bioinformatics/bth140 may be missing for title: Decoupling dynamical systems for pathway identification from metabolic profiles

INVALID DOIs

- None

mjsottile commented 4 years ago

Only a few steps left to finalize acceptance @ramiyaari

Please review the pull request I just submitted. I did a final pass over the paper and found a small number of minor changes to the text.
Please add the missing DOIs to the references that lack them. See the message from whedon above.
Once you have completed this, the last step is to make a tagged release and archive. Please comment in this thread with the version number and archive DOI.

Once those three steps are completed, I will send the submission off to the JOSS EICS for final processing.

ramiyaari commented 4 years ago

@whedon generate pdf

whedon commented 4 years ago

Attempting PDF compilation. Reticulating splines etc...

whedon commented 4 years ago

:point_right: Check article proof :page_facing_up: :point_left:

ramiyaari commented 4 years ago

@whedon generate pdf

whedon commented 4 years ago

Attempting PDF compilation. Reticulating splines etc...

whedon commented 4 years ago

:point_right: Check article proof :page_facing_up: :point_left:

ramiyaari commented 4 years ago

@whedon check references

whedon commented 4 years ago

Attempting to check references...

whedon commented 4 years ago


OK DOIs

- 10.18637/jss.v033.i09 is OK
- 10.1155/2013/897658 is OK
- 10.1371/journal.pcbi.1004012 is OK
- 10.1098/rsif.2016.0525 is OK
- 10.1016/j.spl.2017.08.013 is OK
- 10.1177/0962280217746443 is OK
- 10.1111/stan.12124 is OK
- 10.18637/jss.v075.i02 is OK
- 10.1007/s11222-014-9486-9 is OK
- 10.1214/15-EJS1053 is OK
- 10.1111/biom.12348 is OK
- 10.1098/rsif.2010.0412 is OK
- 10.1016/j.jmva.2008.03.005 is OK
- 10.1111/j.1541-0420.2008.01172.x is OK
- 10.1093/bioinformatics/bth140 is OK

MISSING DOIs

- None

INVALID DOIs

- None

ramiyaari commented 4 years ago

Hi @mjsottile , I've completed the first two tasks in your list. Regarding the third, if I understand what you've asked for then the current version of the software in CRAN is 1.1.8, and the doi of the joss paper is 10.21105/joss.01850. Thanks

danielskatz commented 4 years ago

For the second part, JOSS needs the software to be archived in an archival repository, such as Zenodo, figshare, or an institutional repository. Once this is done, that repository should provide a DOI to the archive, which is what @mjsottile needs. For software in GitHub, the easiest path is usually to use to the Zenodo-GitHub linkage, being sure to manually change the metadata in Zenodo so that the title and authors of the archive match the those of the JOSS paper.

ramiyaari commented 4 years ago

Thanks, @danielskatz and @mjsottile. I followed your instructions and created the archive using Zenodo. The doi to the archive is 10.5281/zenodo.3576265 Target URL is https://zenodo.org/badge/latestdoi/142470608

mjsottile commented 4 years ago

@whedon set 10.5281/zenodo.3576265 as archive

whedon commented 4 years ago

OK. 10.5281/zenodo.3576265 is the archive.

mjsottile commented 4 years ago

@whedon set v1.1.8 as version

whedon commented 4 years ago

OK. v1.1.8 is the version.

mjsottile commented 4 years ago

Thanks @ramiyaari - I believe we're ready for final processing.

mjsottile commented 4 years ago

:wave: @openjournals/joss-eics This paper has completed the review process and I believe it's ready for final processing. Let me know if there is anything additional that I should do.

ramiyaari commented 4 years ago

Thank you @mjsottile

labarba commented 4 years ago

@ramiyaari — I'm the associate EiC on rotation, and will process your paper to publication. We ask authors to edit the metadata (in this case, the title) of the Zenodo deposit so it matches the JOSS paper. Could you make that change?

labarba commented 4 years ago

Looking at the paper, it does look rather long for the typical JOSS paper. In fact, the JOSS documentation stipulates that papers should be short: "The paper should be between 250-1000 words." And also,

a “full length” paper is not permitted, and software documentation such as API (Application Programming Interface) functionality should not be in the paper and instead should be outlined in the software documentation.

Do you think the detailed example should rather be in the documentation, and simply be mentioned here with a link?

ramiyaari commented 4 years ago

@whedon generate pdf

whedon commented 4 years ago

Attempting PDF compilation. Reticulating splines etc...

whedon commented 4 years ago

PDF failed to compile for issue #1850 with the following error:

Can't find any papers to compile :-(

ramiyaari commented 4 years ago

@whedon generate pdf

openjournals / joss-reviews