Closed whedon closed 4 years ago
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @dangeles, @YichaoOU 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:
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
Reference check summary:
OK DOIs
- 10.1534/genetics.109.103010 is OK
- 10.1038/s41559-018-0611-6 is OK
- 10.1186/1479-7364-7-1 is OK
- 10.1126/sciadv.1501714 is OK
- 10.1145/1854776.1854788 is OK
- 10.1093/bioinformatics/btr330 is OK
- 10.3390/genes9030123 is OK
MISSING DOIs
- None
INVALID DOIs
- None
The documentation and manuscript are well written. Installation and test cases are easy to follow.
In my case, ./FGTpartitioner.py -h
does not work, but python FGTpartitioner.py -h
works.
The GitHub repo provides examples but the documentation didn't specifically provide test commands such as, python FGTpartitioner.py -v examples/example_1.vcf.gz
Minor comments:
What is the time complexity for your algorithm? Remember in the Wang 2010 paper, they claimed to have O(mn) and O(nm^2) in their proposed DP algorithms. It is OK that you don't write a formal algorithmic complexity analysis, but I think it is better to show the complexity of your algorithm.
Did you use any publicly available data to verify your method?
Thanks, Yichao
This is a neat algorithm that addresses an important problem for non-canonical model organism genomics. The README and paper are well-written, and in general the code is well-documented and nicely written.
Doc-strings are missing from all defined function in FGTpartitioner.py
. It would improve the code significantly to add short doc-strings explaining the input, output and purpose of each function.
Two example datasets are provided, but to the best of my ability, it appears they give identical results, and no guidance is given to the user as to why two examples are provided. The example_noHet
is included without a .tbi
file (probably a good teaching moment). On the other hand, additional files are provided within the examples folder that could probably be ignored or documented somewhere.
Best, David
Hey @tkchafin, do you think you could address the few comments of the editors?
@lpantano
@whedon generate pdf
@whedon check references
Reference check summary:
OK DOIs
- 10.1534/genetics.109.103010 is OK
- 10.1038/s41559-018-0611-6 is OK
- 10.1186/1479-7364-7-1 is OK
- 10.1126/sciadv.1501714 is OK
- 10.1145/1854776.1854788 is OK
- 10.1093/bioinformatics/btr330 is OK
- 10.3390/genes9030123 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@tkchafin, thank you! Then, last two steps: 1) is the version still v1.0.0, 2) can you create a zenodo DOI link where the title and the author match exactly the paper information and give it to us? Thanks!
@lpantano
@whedon set v1.0.1 as version
OK. v1.0.1 is the version.
@whedon set 10.5281/zenodo.3635843 as archive
OK. 10.5281/zenodo.3635843 is the archive.
@openjournals/joss-eics, we are ready here
@whedon accept
Attempting dry run of processing paper acceptance...
PDF failed to compile for issue #2030 with the following error:
/app/vendor/ruby-2.4.4/lib/ruby/2.4.0/find.rb:43:in block in find': No such file or directory - tmp/2030 (Errno::ENOENT) from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/find.rb:43:in
collect!'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/find.rb:43:in find' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-9847f98e9ec6/lib/whedon/processor.rb:61:in
find_paper_paths'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-9847f98e9ec6/bin/whedon:73:in compile' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/command.rb:27:in
run'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in invoke_command' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor.rb:387:in
dispatch'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/base.rb:466:in start' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-9847f98e9ec6/bin/whedon:116:in
<top (required)>'
from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in load' from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in
Reference check summary:
OK DOIs
- 10.1534/genetics.109.103010 is OK
- 10.1038/s41559-018-0611-6 is OK
- 10.1186/1479-7364-7-1 is OK
- 10.1126/sciadv.1501714 is OK
- 10.1145/1854776.1854788 is OK
- 10.1093/bioinformatics/btr330 is OK
- 10.3390/genes9030123 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@whedon generate pdf
@whedon accept
Attempting dry run of processing paper acceptance...
PDF failed to compile for issue #2030 with the following error:
sh: 0: getcwd() failed: No such file or directory sh: 0: getcwd() failed: No such file or directory pandoc: 10.21105.joss.02030.pdf: openBinaryFile: does not exist (No such file or directory) Looks like we failed to compile the PDF
Reference check summary:
OK DOIs
- 10.1534/genetics.109.103010 is OK
- 10.1038/s41559-018-0611-6 is OK
- 10.1186/1479-7364-7-1 is OK
- 10.1126/sciadv.1501714 is OK
- 10.1145/1854776.1854788 is OK
- 10.1093/bioinformatics/btr330 is OK
- 10.3390/genes9030123 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@openjournals/dev I'm not able to figure out what is going wrong with the paper here. Could you help?
@whedon accept
Attempting dry run of processing paper acceptance...
PDF failed to compile for issue #2030 with the following error:
/app/vendor/ruby-2.4.4/lib/ruby/2.4.0/find.rb:43:in block in find': No such file or directory - tmp/2030 (Errno::ENOENT) from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/find.rb:43:in
collect!'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/find.rb:43:in find' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-9847f98e9ec6/lib/whedon/processor.rb:61:in
find_paper_paths'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-9847f98e9ec6/bin/whedon:73:in compile' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/command.rb:27:in
run'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in invoke_command' from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor.rb:387:in
dispatch'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.3/lib/thor/base.rb:466:in start' from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-9847f98e9ec6/bin/whedon:116:in
<top (required)>'
from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in load' from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in
Reference check summary:
OK DOIs
- 10.1534/genetics.109.103010 is OK
- 10.1038/s41559-018-0611-6 is OK
- 10.1186/1479-7364-7-1 is OK
- 10.1126/sciadv.1501714 is OK
- 10.1145/1854776.1854788 is OK
- 10.1093/bioinformatics/btr330 is OK
- 10.3390/genes9030123 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@whedon accept
Attempting dry run of processing paper acceptance...
Reference check summary:
OK DOIs
- 10.1534/genetics.109.103010 is OK
- 10.1038/s41559-018-0611-6 is OK
- 10.1186/1479-7364-7-1 is OK
- 10.1126/sciadv.1501714 is OK
- 10.1145/1854776.1854788 is OK
- 10.1093/bioinformatics/btr330 is OK
- 10.3390/genes9030123 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Check final proof :point_right: https://github.com/openjournals/joss-papers/pull/1273
If the paper PDF and Crossref deposit XML look good in https://github.com/openjournals/joss-papers/pull/1273, then you can now move forward with accepting the submission by compiling again with the flag deposit=true
e.g.
@whedon accept deposit=true
@openjournals/dev I'm not able to figure out what is going wrong with the paper here. Could you help?
Apologies, I accidentally introduced a regression last night. This should be fixed now.
@whedon accept deposit=true
Doing it live! Attempting automated processing of paper acceptance...
π¦π¦π¦ π Tweet for this paper π π¦π¦π¦
π¨π¨π¨ THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! π¨π¨π¨
Here's what you must now do:
Party like you just published a paper! πππ¦ππ»π€
Any issues? notify your editorial technical team...
Ok it looks like everything is in order!
Congratulations to @tkchafin on your new publication! Thanks very much for your time and expertise to editor @lpantano and reviewers @dangeles and @YichaoOU!
:tada::tada::tada: Congratulations on your paper acceptance! :tada::tada::tada:
If you would like to include a link to your paper from your README use the following code snippets:
Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.02030/status.svg)](https://doi.org/10.21105/joss.02030)
HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.02030">
<img src="https://joss.theoj.org/papers/10.21105/joss.02030/status.svg" alt="DOI badge" >
</a>
reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.02030/status.svg
:target: https://doi.org/10.21105/joss.02030
This is how it will look in your documentation:
We need your help!
Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:
Submitting author: @tkchafin (Tyler Chafin) Repository: https://github.com/tkchafin/FGTpartitioner Version: v1.0.1 Editor: @lpantano Reviewer: @dangeles, @YichaoOU Archive: 10.5281/zenodo.3635843
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
@dangeles & @YichaoOU, 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 @lpantano know.
β¨ Please try and complete your review in the next two weeks β¨
Review checklist for @dangeles
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper
Review checklist for @YichaoOU
Conflict of interest
Code of Conduct
General checks
Functionality
Documentation
Software paper