Closed whedon closed 4 years ago
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @xin-huang, @tkchafin it looks like you're currently assigned to review this paper :tada:.
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
: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:
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
PDF failed to compile for issue #2643 with the following error:
Can't find any papers to compile :-(
@whedon generate pdf from branch paper
Attempting PDF compilation from custom branch paper. Reticulating splines etc...
The authors implemented a python package to perform simulation with different evolutionary strategies under Moran process. This is an interesting simulator in population biology, because there are very few user-friendly simulators for evolutionary game currently. After testing this package and reading the paper, I have several concerns on the documentation and software paper. I have opened some issues (https://github.com/AngryMaciek/angry-moran-simulator/issues/5 and https://github.com/AngryMaciek/angry-moran-simulator/issues/6) in the repository. Because I do not have computers with MacOS and TravisCI cannot make python builds on MacOS. I cannot verify the installation and performance on MacOS.
[Review complete] The authors have provided a flexible and user-friendly software to generate simulations under several different scenarios from evolutionary game theory. I was able to verify functionality of the simulated processes and built-in plotting functions under MacOS, after minor changes to the documented installation instructions provided by the authors. After completing my review, I would recommend publication of this contribution in JOSS after completing several necessary revisions, which are aimed primarily at increasing clarity of the communications associated with this package (both software paper and documentation), and making installation/ plotting easier for the user. These are summarized below, and in greater detail as Issues on the software github page.
Software paper: Major issues (per checklist) are currently: 1) The lack of a non-specialist summary statement; and 2) There are many inconsistencies in the writing that make me suggest the authors go back through more carefully to edit for clarity and language). For example, “EES” vs “ESS” is not consistent, and several other instances (i.e. “A population consists of individuals…” rather than “Population is created by individuals…”) where the quality of writing could be improved. These problems are listed in more detail over at issue #9(https://github.com/AngryMaciek/angry-moran-simulator/issues/9).
Documentation/ Functionality: There are 2 major issues here that I think should be corrected prior to publication: 1) The installation was not initially successful (on MacOS) without first manually relaxing the version constraints specified in the .yml file. I suspect that these constraints are overly specific, which for me created conflicts when creating the environment in conda; and 2) Documentation for the plotting functions is insufficient. A third issue (which I consider minor) is that - per the checklist - the documentation should also contain a statement of need. These are also added as issues #7 (https://github.com/AngryMaciek/angry-moran-simulator/issues/7) and #8 (https://github.com/AngryMaciek/angry-moran-simulator/issues/8)
Wow @xin-huang and @tkchafin, you may have set some kind of record. Thanks very much.
@whedon generate pdf from branch paper
Attempting PDF compilation from custom branch paper. Reticulating splines etc...
@whedon generate pdf from branch paper
Attempting PDF compilation from custom branch paper. Reticulating splines etc...
Hi @majensen I have checked off all the items on the checklist. The authors already addressed my concerns. I have no further comments.
Thanks @xin-huang - so @AngryMaciek I will look for https://github.com/AngryMaciek/angry-moran-simulator/issues/7 to be addressed and @tkchafin to then tick the final box on that review. I'll then proceed with editorial checks. Thanks all!
Dear @majensen , I believe we have addressed all of the suggestions raised by the reviewers :)
(CC @rozmanowna @tkchafin @xin-huang )
@whedon generate pdf from branch paper
Attempting PDF compilation from custom branch paper. Reticulating splines etc...
@whedon check references from branch paper
Attempting to check references... from custom branch paper
PDF failed to compile for issue #2643 with the following error:
sh: 0: getcwd() failed: No such file or directory pandoc: 10.21105.joss.02643.pdf: openBinaryFile: does not exist (No such file or directory) Looks like we failed to compile the PDF
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1017/S0305004100033193 is OK
- 10.1017/CBO9780511806292 is OK
- 10.1016/j.jocs.2019.101067 is OK
- 10.5281/zenodo.3980654 is OK
- 10.1155/2007/18636 is OK
- 10.1038/nature07921 is OK
- 10.1137/15M1044825 is OK
- 10.1038/380240a0 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@openjournals/dev - please see error in compilation at https://github.com/openjournals/joss-reviews/issues/2643#issuecomment-699695148 - I was able to use https://whedon.theoj.org successfully.
@whedon check references from branch paper
Attempting to check references... from custom branch paper
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1017/S0305004100033193 is OK
- 10.1017/CBO9780511806292 is OK
- 10.1016/j.jocs.2019.101067 is OK
- 10.5281/zenodo.3980654 is OK
- 10.1155/2007/18636 is OK
- 10.1038/nature07921 is OK
- 10.1137/15M1044825 is OK
- 10.1038/380240a0 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@whedon generate pdf from branch paper
Attempting PDF compilation from custom branch paper. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Dear Editors,
Should we now make a zenodo
submission ourselves, or... (?)
You can do that if you wish @AngryMaciek. I will have a pull request for you with a number of suggested changes. Apologies for the delay, thanks for your patience.
@majensen Then there is no need now, I will wait until I merge your suggestions.
will get to this by Thursday - thanks @AngryMaciek
@AngryMaciek please have a look at the suggestions in the PR (and assoc. comments).
I would also like to see an example run in the paper that exemplifies stochastic effects. One example might be to show that if an invading population is small enough, it can disappear frequently (i.e., among many replicate simulations) even if it uses an ESS. Probably (just guessing) the fitness benefit has to exceed 1/N more or less to get a high probability of establishment. (This is also a test of the software - if a rare invader never disappears over multiple replicates, there is probably a code issue.) thanks
@whedon generate pdf from branch paper
Attempting PDF compilation from custom branch paper. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
We have just included the most recent changes in the branch paper
of the repository.
@whedon generate pdf from branch paper
Attempting PDF compilation from custom branch paper. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@AngryMaciek I think things look quite good. Can you now create your archive, making sure that the archive title and authors are the same as those on the paper? Once that's done, please provide the archive DOI in this thread. Then I will attempt the spell summoning the editors-in-chief. thanks!
@majensen
We have merged branch paper
to master
and removed the former.
We have submitted the code to zenodo: https://doi.org/10.5281/zenodo.4114143
Good luck with the spellcasting! (∩`-´)⊃━☆゚.*・。゚
@whedon set 10.5281/zenodo.4114143 as archive
OK. 10.5281/zenodo.4114143 is the archive.
@whedon set 1.0.0 as version
OK. 1.0.0 is the version.
@whedon accept
Submitting author: @AngryMaciek (Maciej Bak) Repository: https://github.com/AngryMaciek/angry-moran-simulator Version: 1.0.0 Editor: @majensen Reviewer: @xin-huang, @tkchafin Archive: 10.5281/zenodo.4114143
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
Status
Status badge code:
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
@xin-huang & @tkchafin, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @majensen 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 ✨
Review checklist for @xin-huang
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @tkchafin
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper