Submitting author: @grabear (Robert Gilmore)
Repository: https://github.com/vallenderlab/MicrobiomeR
Version: 0.5.1
Editor: @lpantano
Reviewers: @CosteaPaul
Author instructions
Thanks for submitting your paper to JOSS @grabear. Currently, there isn't an JOSS editor assigned to your paper.
@grabear if you have any suggestions for potential reviewers then please mention them here in this thread. In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission.
Editor instructions
The JOSS submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type:
@whedon commands
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks.
For a list of things I can do to help you, just type:
@whedon commands
What happens now?
This submission is currently in a pre-review
state which means we are waiting for an editor to be assigned and for them to find some reviewers for your submission. This may take anything between a few hours to a couple of weeks. Thanks for your patience :smile_cat:
You can help the editor by looking at this list of potential reviewers to identify individuals who might be able to review your submission (please start at the bottom of the list). Also, feel free to suggest individuals who are not on this list by mentioning their GitHub handles here.
Attempting PDF compilation. Reticulating splines etc...
PDF failed to compile for issue #1288 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/1288 (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-01ece1d1d135/lib/whedon/processor.rb:57:in
find_paper_paths'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-01ece1d1d135/bin/whedon:50:in prepare'
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-01ece1d1d135/bin/whedon:116:in
load'
from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in
👋 @pjotrp - the author requested you (or someone from your group) as editor - ok?
Of course, some work is needed on the paper first...
👋 @grabear - I don't see the paper part of your submission. Take a look at the author submission guidelines, specifically What should my paper contain? and Example paper and bibliography
Hi, I put the paper in a separate folder under inst/paper/ @danielskatz
@whedon generate pdf from inst/paper
Attempting PDF compilation. Reticulating splines etc...
thanks - I see some issues with the figure, the table, and the references. You can make changes to the paper.md and paper.bib, then use the same command I used (as a new comment here) to regenerate until you are satisfied with the generated proof.
In the meantime, @pjotrp and his group can figure out who will edit this, I think.
@danielskatz Thank you! I'll work on it.
@whedon commands
Here are some things you can ask me to do:
# List Whedon's capabilities
@whedon commands
# List of editor GitHub usernames
@whedon list editors
# List of reviewers together with programming language preferences and domain expertise
@whedon list reviewers
EDITORIAL TASKS
# Compile the paper
@whedon generate pdf
# Compile the paper from alternative branch
@whedon generate pdf from branch custom-branch-name
# Ask Whedon to check the references for missing DOIs
@whedon check references
@whedon generate pdf from branch joss-review from inst/paper
Attempting PDF compilation from custom branch joss-review from inst/paper . Reticulating splines etc...
@sdhutchins working on tweaking the paper!
Yes, I'll ask for an editor.
@whedon assign @lpantano as editor
OK, the editor is @lpantano
@whedon generate pdf from inst/paper branch joss-review
Attempting PDF compilation. Reticulating splines etc...
Hi @grabear,
let me know when you can figure out the format issue, I will look into possible reviewers in the meantime.
Looking forward to working together in the process.
Cheers
Hello @lpantano! I'll be working on it this afternoon! I just need to play around with whedon a little.
Looking forward to it as well :+1:
@whedon generate pdf from branch joss-review inst/paper
Attempting PDF compilation from custom branch joss-review inst/paper. Reticulating splines etc...
@pjotrp @lpantano @danielskatz Any idea what I should do with @whedon when I'm generating the pdf on a separate branch and in a folder that's not on the top level?
👋 @arfon ?
Part of the problem is that I always protect my master and dev-master branches, so it makes it a bit more complicated for me to edit. I can always change the permissions temporarily, but that's not ideal.
@whedon generate pdf from branch joss-review
Attempting PDF compilation from custom branch joss-review. Reticulating splines etc...
sorry @grabear that is not working with two of the conditions (other branch and other location), hopefully, somebody who knows the backend infrastructure can help. I will reach somebody if @arfon doesn't chime in.
At least the figure now. seems right. :)
Thanks!
@lpantano It seems to be working now! It's finding the paper, so no complaints. :)
@whedon generate pdf from branch joss-review
Attempting PDF compilation from custom branch joss-review. Reticulating splines etc...
@whedon check references
Attempting to check references...
```Reference check summary:
OK DOIs
MISSING DOIs
INVALID DOIs
@whedon check references from branch joss-review
Attempting to check references...
```Reference check summary:
OK DOIs
MISSING DOIs
INVALID DOIs
@whedon generate pdf from branch joss-review
Attempting PDF compilation from custom branch joss-review. Reticulating splines etc...
@whedon generate pdf from branch joss-review
Attempting PDF compilation from custom branch joss-review. Reticulating splines etc...
PDF failed to compile for issue #1288 with the following error:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 16 0 16 0 0 207 0 --:--:-- --:--:-- --:--:-- 207
Error producing PDF.
! Misplaced \noalign.
\hline ->\noalign
{\ifnum 0=`}\fi \hrule @height \arrayrulewidth \futurelet...
l.386 \hline
Looks like we failed to compile the PDF
@whedon generate pdf from branch joss-review
Attempting PDF compilation from custom branch joss-review. Reticulating splines etc...
@whedon generate pdf from branch joss-review
Attempting PDF compilation from custom branch joss-review. Reticulating splines etc...
@whedon generate pdf from branch joss-review
Attempting PDF compilation from custom branch joss-review. Reticulating splines etc...
@lpantano @sdhutchins I think I have the table, diagram, and DOIs in a good place.
Thoughts?
Thanks!
I think looks good, the only think is that some DOIs have the https
and other not. Can you normalize that?
Hi @CosteaPaul,
@brainstorm mentioned to me that you could be a good reviewer for this paper, Do you think you would have time for this? It would be great!
I think it looks good, @grabear! I would only say perhaps the diagram's height could be decreased while keeping the same scale. It looks good as it is though.
@whedon generate pdf from branch joss-review
Attempting PDF compilation from custom branch joss-review. Reticulating splines etc...
@whedon generate pdf from branch joss-review
Attempting PDF compilation from custom branch joss-review. Reticulating splines etc...
@whedon generate pdf from branch joss-review
Attempting PDF compilation from custom branch joss-review. Reticulating splines etc...
@lpantano @sdhutchins Made some changes!
@whedon check references
Attempting to check references...
```Reference check summary:
OK DOIs
MISSING DOIs
INVALID DOIs
@lpantano this looks like fun :).
Would be happy to help with reviewing, though I have no idea how this is supposed to work.
Thank you, @CosteaPaul !
We have some guidelines here:
https://joss.readthedocs.io/en/latest/reviewer_guidelines.html
For now, I will move this to review, that will close this issue and open a new one where the review process will happen. Our friend whedon, will help you with the requirements to review the paper. When the new issue is open, there will be some guidelines. I will follow up there.
Thanks so much!
@whedon assign @CosteaPaul as reviewer
OK, the reviewer is @CosteaPaul
Hi @grabear,
I see there are some issues with the DOI links , let me know when you solve this and we can move this to under review.
Thanks!
@lpantano All of those DOI's are not missing. I copied an pasted those during my first check, so Idk why they are considered "Missing" or "may be missing".
I just updated an F1000 DOI, but only because they release a second version of that paper. I also checked all of the other ones and they are working links..
Hi,
Weird, When I click on the PDF link it lands on a broken web page. Did you try to use the link of the PDF, maybe there is something wrong on the latex code that breaks the link?
https://doi.org/https://doi.org/10.1038/nmeth.f.303
This url is malformed.
Cheers
@whedon generate pdf from branch joss-review
Attempting PDF compilation from custom branch joss-review. Reticulating splines etc...
@whedon check references
Attempting to check references...
```Reference check summary:
OK DOIs
MISSING DOIs
INVALID DOIs
@whedon check references from branch joss-review
Attempting to check references...
```Reference check summary:
OK DOIs
MISSING DOIs
INVALID DOIs
Not really sure what's going on with whedon's reference check, but the DOIs should be correct now. Sorry about that!
@whedon check references from branch joss-review
I'm afraid @whedon only knows how to check references for the master
or default branch of your repository.
Thank you, @arfon. I think is fine since the links work now. I will start the review process.
@whedon start review
Whedon needs separate lines
@whedon start review
OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/1299. Feel free to close this issue now!
Most helpful comment
In the meantime, @pjotrp and his group can figure out who will edit this, I think.