-
-
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]: statemodify: a Python framework to facilitate accessible exploratory modeling for discovering drought vulnerabilities #6223
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 |
|
Five most similar historical JOSS papers: Water Systems Integrated Modelling framework, WSIMOD: A Python package for integrated modelling of water quality and quantity across the water cycle mosartwmpy: A Python implementation of the MOSART-WM coupled hydrologic routing and water management model pyDeltaRCM: a flexible numerical delta model Integrated hydrologic model development and postprocessing for GSFLOW using pyGSFLOW pySBeLT: A Python software package for stochastic sediment transport under rarefied conditions |
Hi @rg727 and thanks for your submission. We have a backlog of submissions right now which I will add yours to now. Thanks for your patience. In the meantime, please check the DOIs listed above, and provide the github handles of 5 reviewers (without "@" so we don't prematurely ping them) from the reviewer database listed above or your own (non-conflicted) extended network. |
@editorialbot check references |
|
@kthyng thanks so much! We fixed the DOIs and we are now just compiling a list of candidate reviewers. |
@kthyng here is a list of reviewers: Barney Dobson - barneydobson |
@editorialbot add @cheginit as editor |
Assigned! @cheginit is now the editor |
Hi @barneydobson, @ekblad, and @pfeiffea! Would you like to review this submission to the Journal for Open Source Software? Our reviews are checklist-driven and openly conducted on GitHub over a timeline of 4–6 weeks. Because the process is much more iterative and interactive than a traditional paper review, we would ask you to start within the next 2 weeks. Here are reviewer guidelines for reference: joss.readthedocs.io/en/latest/reviewer_guidelines.html |
@cheginit happy to! |
Thanks @barneydobson! Once the other reviewers agree, I will move the submission to the review queue so we can officially start the review process. |
@editorialbot add @barneydobson as reviewer |
@barneydobson added to the reviewers list! |
Hi, this looks good, I will take a look at the checklist and repo in the
next couple weeks.
…On Mon, Jan 29, 2024 at 9:29 AM Taher Chegini ***@***.***> wrote:
Hi @barneydobson <https://github.com/barneydobson>, @ekblad
<https://github.com/ekblad>, and @pfeiffea <https://github.com/pfeiffea>!
Would you like to review this submission to the Journal for Open Source
Software? Our reviews are checklist-driven and openly conducted on GitHub
over a timeline of 4–6 weeks. Because the process is much more iterative
and interactive than a traditional paper review, we would ask you to start
within the next 2 weeks. Here are reviewer guidelines for reference:
joss.readthedocs.io/en/latest/reviewer_guidelines.html
Thanks for your consideration.
—
Reply to this email directly, view it on GitHub
<#6223 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKJYILG3NLBMLKQQPMT57RLYQ7MAZAVCNFSM6AAAAABBYOKTFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJVGIZDOMZWGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@editorialbot add @ekblad as reviewer |
@ekblad added to the reviewers list! |
Thanks @ekblad! Once the last reviewer agrees, I will move the submission to the review queue so we can officially start the review process. |
Hi @cheginit - I am on maternity leave right now, and wouldn't be able to start the review until March when I get back to work (and have childcare!). I'm guessing you want the review completed before then, yes? |
Thanks for letting me know @pfeiffea and wishing you all the best on your maternity leave! Right, I prefer the review to be done by then. |
Hi @gutabeshu! Would you like to review this submission to the Journal for Open Source Software? Our reviews are checklist-driven and openly conducted on GitHub over a timeline of 4–6 weeks. Because the process is much more iterative and interactive than a traditional paper review, we would ask you to start within the next 2 weeks. Here are reviewer guidelines for reference: joss.readthedocs.io/en/latest/reviewer_guidelines.html |
Hi @cheginit. Thank you for the invitation. Unfortunately, due to current commitments and time constraints, I am concerned that I would not be able to complete the review within the expected timeframe. Therefore, I must respectfully decline the review request this time. Please do consider me for future review opportunities. |
@gutabeshu, I understand. Thanks for letting me know. |
@editorialbot start review. |
OK, I've started the review over in #6325. |
Submitting author: @rg727 (Rohini Gupta)
Repository: https://github.com/IMMM-SFA/statemodify
Branch with paper.md (empty if default branch):
Version: v0.1.4
Editor: @cheginit
Reviewers: @barneydobson, @ekblad
Managing EiC: Kristen Thyng
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @rg727. Currently, there isn't a JOSS editor assigned to your paper.
@rg727 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: