[REVIEW]: ecopath_matlab: A Matlab-based implementation of the Ecopath food web algorithm

whedon commented 8 years ago

Submitting author: kakearney (Kelly Kearney) Repository: https://github.com/kakearney/ecopath_matlab-pkg Version: v2.0 Editor: @Kevin-Mattheus-Moerman Reviewer: @roliveros-ramos Archive: 10.5281/zenodo.240977

Status

Status badge code:

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

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) 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 questions

Conflict of interest

[x] As the reviewer I confirm that there are no conflicts of interest for me to review this work (such as being a major contributor to the software).
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] Version: Does the release version given match the GitHub release (v2.0)?
Functionality
[x] Installation: Does installation proceed as outlined in the documentation?
[x] Functionality: Have the functional claims of the software been confirmed?
[x] Performance: Have any performance claims of the software been confirmed?
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 function 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

Paper PDF: 10.21105.joss.00064.pdf

[x] Authors: Does the paper.md file include a list of authors with their affiliations?
[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] References: Do all archival references that should have a DOI list one (e.g. papers, datasets, software)?

kakearney commented 7 years ago

I just issued a new release, v2.1b. (Edit: accidentally copied and pasted the wrong one a moment ago, sorry about that). The new DOI is 10.5281/zenodo.240977

arfon commented 7 years ago

@whedon set 10.5281/zenodo.240977 as archive

whedon commented 7 years ago

OK. 10.5281/zenodo.240977 is the archive.

arfon commented 7 years ago

@roliveros-ramos many thanks for your review here and to you for editing @Kevin-Mattheus-Moerman ✨

@kakearney - your paper is now accepted into JOSS and your DOI is http://joss.theoj.org/papers/10.21105/joss.00064 ⚡️ 🚀 💥

openjournals / joss-reviews