-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PRE REVIEW]: title: 'terrainr: An R package for creating immersive virtual environments #4055
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. 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. For a list of things I can do to help you, just type:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
PDF failed to compile for issue #4055 with the following error:
|
Apologies for the paper not rendering -- the paper lives in https://github.com/ropensci/terrainr/tree/paper which I could specify in the pre-submission rendering service, but I couldn't figure out how to provide the branch to the actual submission workflow. |
@whedon check references from branch paper |
|
|
@whedon generate pdf from branch paper |
|
👋 @mikemahoney218 - if you can remove the entries in the .bib file that aren't used, that will simply our checks. Whedon checks everything in that file, whether it is used in the paper or not, unfortunately. |
You can use the commands I gave to check this. note that whedon commands must be the first thing in a comment |
👋 @kbarnhart - would you be willing to edit this submission? |
@whedon invite @kbarnhart as editor |
@kbarnhart has been invited to edit this submission. |
@whedon check references from branch paper |
|
|
@whedon check references from branch paper |
|
|
I believe that should address the reference check! Let me know if I missed anything. |
@whedon generate pdf from branch paper |
|
I can handle this. I see that this package has already gone through and passed the rOpenSci peer review @danielskatz this is the first time I've handled an rOpenSci paper. Looking at the docs, it looks straightforward. Am I correct to thing that this submission should follow the procedure described in this part of the docs? |
@whedon assign @kbarnhart as editor |
OK, the editor is @kbarnhart |
Sorry, I missed the rOpenSci part - given that, you don't need to do anything, I will take care of it. |
@whedon assign me as editor |
OK, the editor is @danielskatz |
Link to rOpenSci review: ropensci/software-review#416 |
Sounds good @danielskatz, thanks! |
@whedon assign @danielskatz as reviewer |
OK, @danielskatz is now a reviewer |
@whedon start review |
OK, I've started the review over in #4060. |
Submitting author: @mikemahoney218 (Michael Mahoney)
Repository: https://github.com/ropensci/terrainr
Version: v0.5.1
Editor: @danielskatz
Reviewers: @danielskatz
Managing EiC: Daniel S. Katz
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:
Author instructions
Thanks for submitting your paper to JOSS @mikemahoney218. Currently, there isn't an JOSS editor assigned to your paper.
@mikemahoney218 if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission (please start at the bottom of the list).
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:
The text was updated successfully, but these errors were encountered: