-
-
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
[REVIEW]: PyMPDATA v1: Numba-accelerated Pythonic implementation of MPDATA with examples in Python, Julia and Matlab #3896
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. @dmikushin, @olekravchenko it looks like you're currently assigned to review this paper 🎉. 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. ⭐ Important ⭐ If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/openjournals/joss-reviews) repository. As a reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all reviews 😿 To fix this do the following two things:
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:
|
PDF failed to compile for issue #3896 with the following error:
|
|
@whedon generate pdf from branch JOSS |
|
@whedon check references |
@whedon check references from branch JOSS |
|
|
it's puzzling as the above "INVALID DOIs" seem correct, at leat both of the below URLs redirect correctly to the journal site: |
Please make sure the DOIs are in doi entries in the bib file rather than url entries, and that they don't include the https://doi.org part |
And perhaps change the characters that are being encoded for example: 10.1175/1520-0493(1989)117<0102:TDSLTW>2.0.CO;2 |
@whedon check references from branch JOSS |
|
|
thank you @danielskatz, indeed the URL escapes in the bib file were the cause - good job on the checker side! |
👋 @dmikushin, please update us on how your review is going (this is an automated reminder). |
👋 @olekravchenko, please update us on how your review is going (this is an automated reminder). |
Hello @dmikushin and @olekravchenko - I was wondering if you needed anything in starting the reviews? I noticed that there hasn't been activity since the review was initiated. I'm happy to help or answer questions in getting started. |
Hi @slayoo : it appears that the reviewers who agreed to review have vanished and are unresponsive (unless you’ve heard from them outside this review thread). This unfortunately happens sometimes. I will identify alternative reviewers to replace them so the review doesn’t go idle. Give me a day or so to find people to take their place. |
Thank you, @mjsottile. (I haven't heard from the reviewers) |
👋 @d-chambers Would you be willing to perform a review for this submission to the Journal of Open Source Software? I identified you based on your areas of expertise as listed on the spreadsheet of potential JOSS reviewers. Please let me know if you would be interested. Thank you! |
👋 @highlando Would you be willing to perform a review for this submission to the Journal of Open Source Software? I identified you based on your areas of expertise as listed on the spreadsheet of potential JOSS reviewers. Please let me know if you would be interested. Thank you! |
|
🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦 |
🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨 Here's what you must now do:
Any issues? Notify your editorial technical team... |
@arfon Thank you! |
Can you remove the |
@slayoo fixed in open-atmos/PyMPDATA#338 |
Merged, thank you, @arfon! |
BTW, we have an analogous problem in #4326 |
@editorialbot reaccept |
|
🌈 Paper updated! New PDF and metadata files 👉 openjournals/joss-papers#3506 |
OK, this should be fixed now. |
🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉 If you would like to include a link to your paper from your README use the following code snippets:
This is how it will look in your documentation: We need your help! The Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:
|
Thank you, @arfon ! |
@arfon I've noticed that there were three more nbsps in the author list that also go through into the paper metadata and JOSS website: Just removed it in the repo: open-atmos/PyMPDATA@a35a159 Let me ask for one more regeneration of the metadata. |
@arfon, please let us know if it would be possible to fix the remaining nbsp problems in the author list (already fixed in the project repo) - see above, thanks, Sylwester |
@openjournals/dev Could you take a look at this? |
@kthyng, is there any better place to report such issues? (this issue is closed, so it's perhaps not the best place) |
@kthyng if the paper is already updated in the original repo, the |
@editorialbot reaccept |
|
🌈 Paper updated! New PDF and metadata files 👉 openjournals/joss-papers#3530 |
@slayoo How does your paper look now? |
@kthyng it's now fixed: Thank you for your help! |
Submitting author: @slayoo (Sylwester Arabas)
Repository: https://github.com/atmos-cloud-sim-uj/PyMPDATA
Branch with paper.md (empty if default branch):
Version: v1
Editor: @arfon
Reviewers: @Chiil, @wdeconinck
Archive: 10.5281/zenodo.6934418
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.
Status
Status badge code:
Reviewers and authors:
Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)
Reviewer instructions & questions
@dmikushin & @olekravchenko, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:
The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @mjsottile know.
✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨
The text was updated successfully, but these errors were encountered: