-
-
Notifications
You must be signed in to change notification settings - Fork 39
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]: PyroRL: A Reinforcement Learning Environment for Wildfire Evacuation #6639
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:
|
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: ✅ License found: |
|
@cpondoc - thanks for your submission to JOSS. We're currently managing a large backlog of submissions and the editor most appropriate for your area is already rather busy. For now, we will need to waitlist this paper and process it as the queue reduces. Thanks for your patience! |
Hey @arfon -- sounds good! We'll take care of fixing up the DOIs in the meantime. Let me know if there's anything else that needs to get taken care of? |
@editorialbot generate preprint |
📄 Preprint file created: Find it here in the Artifacts list 📄 |
@editorialbot generate preprint |
📄 Preprint file created: Find it here in the Artifacts list 📄 |
@editorialbot invite @mikemahoney218 as editor 👋 @mikemahoney218 this one looks to be right down your alley from a SME point of view. Would you want to take this on as editor? |
Invitation to edit this submission sent! |
@editorialbot assign me as editor |
Assigned! @mikemahoney218 is now the editor |
Happy to take this one on! @cpondoc , would you be able to suggest 5 reviewers for this package? Reviewers can come from either our reviewer database or your own network, so long as they don't have a conflict of interest. When you suggest them, please do not ping them using After that, I should be able to start pinging people for reviews! |
Hey @mikemahoney218 -- sounds great! We will get back to you in the next day or two with a list of 5 reviewers for this package. Just thought I'd acknowledge the message in the interim -- thanks again! |
@editorialbot commands |
Hello @cpondoc, here are the things you can ask me to do:
|
@editorialbot check references |
|
@editorialbot generate preprint |
📄 Preprint file created: Find it here in the Artifacts list 📄 |
Just in case it's helpful, people often want |
@editorialbot check references |
|
Hey @mikemahoney218 — thanks again for the top about
Thanks again! |
Thanks! The Stable-baselines3 case is weird; JMLR doesn't assign DOIs (which is a weird decision in the first place) and it seems like ACM generates a "fake" DOI in its url, though if you click the "citation" button on that page or the JMLR original, there's no DOI field in the generated bibtex. I think the best option would be to remove the DOI from that entry, as it's not a valid DOI. Entries with no DOI are fine -- we want to make sure we're using DOIs wherever applicable, but we understand some resources don't. I haven't checked, but if you can make sure you've got the ISBN included for |
Sounds great! We just took out the DOI for Stable-baselines3 and also added the ISBN for |
Also -- here are 5 reviewers our team thinks would be great for this package! I linked their JOSS profiles rather than tagging them. |
Thanks @cpondoc ! I'll start reaching out to reviewers Monday. (Editing for my own tracking purposes -- third round of invites sent 2024-05-07) |
@editorialbot generate pdf |
@editorialbot assign @SamTov as reviewer |
I'm sorry human, I don't understand that. You can see what commands I support by typing:
|
@editorialbot add @SamTov as reviewer (picky bot...) |
@SamTov added to the reviewers list! |
@cpondoc I'm having a harder time than usual getting reviewers for this one (not a comment about your work, probably more a comment about it being the end of the semester!). If you've got any suggestions for reviewers from your network (keeping in mind our conflict of interest policy) it'd be a huge help -- and I'll keep reaching out to additional reviewers. |
@mikemahoney218 thanks for the note! Will get back to you by next week with any updates! |
@editorialbot add @shahchiragh as reviewer |
@shahchiragh added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #6739. |
Submitting author: @cpondoc (Christopher Pondoc)
Repository: https://github.com/sisl/PyroRL
Branch with paper.md (empty if default branch): master
Version: v1.0.1
Editor: @mikemahoney218
Reviewers: @SamTov, @shahchiragh
Managing EiC: Arfon Smith
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @cpondoc. Currently, there isn't a JOSS editor assigned to your paper.
@cpondoc 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 JOSS 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: