-
-
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]: OpenSCM Two Layer Model: A Python implementation of the two-layer climate model #2728
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:
|
Looking through the list, these people list climate or atmospheric science as areas so could be willing
|
To the editors, I've just read the review criteria properly. Apologies that I missed the description of effort! I am very happy to close this request if it appears to be out of scope because of its limited size. Having said that, this implementation (albeit in a different repository at the time) has already been used in the academic literature and is likely to be used again in future given the prominence of this model. In the event that this submission is deemed out of scope, is it possible to reopen if/when we've been working on the implementation for more time and added more features or would we have to start fresh (not an overly difficult task I agree, just thought I should ask)? |
@whedon check repository |
|
|
|
@leouieda has been invited to edit this submission. |
👋 @leouieda - is there a chance you might be able to edit this submission? |
@danielskatz I'd be happy to 👌🏽 |
OK, the editor is @leouieda |
thanks @danielskatz and @leouieda — I meant to get back to this over the weekend but didn't manage to. |
👋🏽 Hi @znicholls thank you for the review suggestions!
I had a look at the software repository and the paper. This does seem more than "3 months of work" to me given that you have invested in a decent amount of testing and the model has been used in research already. Bare in mind that I'm not a climate scientist, though. We can investigate further if any reviewers have concerns but otherwise I'm happy to proceed with the review. Please have a look at the "missing DOIs" report above and add the relevant DOIs to your |
👋 @sadielbartholomew @kdorheim @bradyrx would you be willing to review this submission for JOSS? Reviews are done entirely through GitHub (issues and pull requests). These are the reviewer guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html This is a pre-review issue in which I will assign reviewers. Once there are sufficient reviewers (usually 2-3), I will open a new issue where the review will take place. If you agree to review, you will be notified when the review process if formally started. If you are not able to review at this time, please let me know if you have recommendations for other reviewers. Please recommend without mentioning a handle to avoid notifying the person (e.g., you would refer to me as leouieda instead of @leouieda). This way we attempt to reduce the number of people who are subscribed to this thread. |
leouieda unfortunately I am unable to review this at the moment given other time commitments. I am not sure if he is registered to review for JOSS but Alexey Shimnokol (https://github.com/ashiklom) comes to mind as someone who has worked on SCMs, is a good reviewer, a python user, and champion of open source science. |
Thanks leouieda. I am very busy this October but in November I will have a lot more free time. I am happy to review assuming the editor and authors wouldn't mind waiting on my review until early November, but that is still a number of weeks away so I appreciate that may be longer than reasonable or desired to wait. So feel free to assign me to review or not depending on timescales required. Certainly if someone else is free to review more quickly, it would be better to choose them. |
@kdorheim thank you for the suggestion! I'll ping Alexey and see if he's available/interested. @sadielbartholomew early November is still within the 4-6 weeks we usually recommend for review turn around. I'm happy to assign you as reviewer 🙂 |
👋 @ashiklom would you be willing to review this submission for The Journal of Open Source Software (JOSS)? JOSS is a developer-friendly open-access journal and reviews are done entirely through GitHub (issues and pull requests). These are our reviewer guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html Please see the previous comments in this thread for more context. The software submission is https://github.com/openscm/openscm-twolayermodel Thank you for your time 🙂 |
Sure, I'd be happy to review this! To confirm, the review deadline is in the first week or two of November? And, there will be a separate GitHub issue where I do the review? |
@ashiklom thank you for agreeing to review! 🎉 We don't have strict deadlines but we aim to have the reviews done or well under way within 4-6 weeks. Of course, these are not normal times for most of us so it's completely understandable if you require longer. There will be a separate issue for the review and I'll post some instructions there as soon as I start the review. |
@whedon generate pdf |
@whedon assign @sadielbartholomew as reviewer |
OK, @sadielbartholomew is now a reviewer |
OK, @ashiklom is now a reviewer |
@whedon start review |
OK, I've started the review over in #2766. |
@ashiklom @sadielbartholomew thank you both for offering your time to review this submission! @znicholls I have now started the review in #2766. I'll post some instructions there. From now on, please use that issue instead. |
@ashiklom @sadielbartholomew if this is your first time reviewing for JOSS, you should get an invitation to join the |
Submitting author: @znicholls (Zebedee Nicholls)
Repository: https://github.com/openscm/openscm-twolayermodel
Version: v0.1.2
Editor: @leouieda
Reviewers: @sadielbartholomew, @ashiklom
Managing EiC: Kristen Thyng
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.
Author instructions
Thanks for submitting your paper to JOSS @znicholls. Currently, there isn't an JOSS editor assigned to your paper.
The author's suggestion for the handling editor is @kthyng.
@znicholls 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: