-
-
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]: GB_code: A grain boundary generation code #853
Comments
|
PDF failed to compile for issue #853 with the following error: /app/vendor/ruby-2.3.4/lib/ruby/2.3.0/psych.rb:379:in |
👋 @labarba - the submitting author suggested you as the handling editor. |
@oekosheri - this PR should fix the paper compilation issues oekosheri/GB_code#1 |
Thanks, I edited paper.md and merged. does it look alright now? |
@whedon generate pdf |
|
PDF failed to compile for issue #853 with the following error: % Total % Received % Xferd Average Speed Time Time Time Current 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 Looks like we failed to compile the PDF |
I edited paper.bib and and paper.md again and committed the new changes. |
@whedon generate pdf |
|
PDF failed to compile for issue #853 with the following error: % Total % Received % Xferd Average Speed Time Time Time Current 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 Looks like we failed to compile the PDF |
@arfon Could you tell me what the problem is? |
Here are some things you can ask me to do:
|
@arfon I used pandoc to generate the PDF myself and had no issues. Waiting for your help to see what the problem is. |
@oekosheri - I think the underscore in the title needs escaping. I fixed it in oekosheri/GB_code#2 |
Thank you, I merged it. Let me see if I can generate the PDF now. |
@whedon generate pdf |
|
I made a minor change, |
@whedon generate pdf |
|
@arfon Dear Editor, I was wondering about the time frame of the review process. Could you let me know approximately when my code will be reviewed? Thanks and I appreciate it. |
It can take between two weeks and two months, typically, to complete the review and acceptance process. Thank you for your patience with our wholly volunteer-staffed journal. |
Note that the Pre-review header requests that you provide reviewer suggestions, if possible. |
@labarba Thank you for your answer. I didn't know I should suggest reviewers. Is there a list I can choose from? |
☝️@oekosheri - I've copied the link from above. |
OK, the reviewer is @vyasr |
FYI — I'm waiting for replies from potential second reviewers. Once I get a positive reply, I'll add the reviewer and start the review issue. Stay tuned. |
Thank you for informing me. |
hi @labarba I can jump in as a second reviewer if you are still looking for someone to do it |
thank you, @trallard, that's great! I'll add you now and start the review |
OK, @trallard is now a reviewer |
@whedon start review |
OK, I've started the review over in #900. Feel free to close this issue now! |
Submitting author: @oekosheri (raheleh Hadian)
Repository: https://github.com/oekosheri/GB_code
Version: v1.0.0
Editor: @labarba
Reviewers: @vyasr, @trallard
Author instructions
Thanks for submitting your paper to JOSS @oekosheri. The JOSS editor (shown at the top of this issue) will work with you on this issue to find a reviewer for your submission before creating the main review issue.
@oekosheri 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:
The text was updated successfully, but these errors were encountered: