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]: Can you predict the future? A tutorial for the National Ecological Observatory Network Ecological Forecasting Challenge #232
Comments
Hello human, I'm @editorialbot, a robot that can help you with some common editorial tasks. 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:
|
|
|
Wordcount for |
@OlssonF 👋 |
@labarba Since the submission we have continued to develop and improve the tutorial and so some edits have been made to the code. We have made some minor edits to the For reviewers, we would suggest S. K. Morgan Ernest, who recently published with you. In addition, from your reviewers database we suggest Jeffrey Hollister and/or Jem Stachelek, both R coders with backgrounds in ecology. Thanks |
Submitting author: @OlssonF (Freya Olsson)
Repository: https://github.com/OlssonF/NEON-forecast-challenge-workshop
Branch with paper.md (empty if default branch): main
Version: v1.1.0
Editor: Pending
Reviewers: Pending
Managing EiC: Lorena Barba
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSE @OlssonF. Currently, there isn't a JOSE editor assigned to your paper.
@OlssonF if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSE submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: