Skip to content
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

Closed
whedon opened this issue Nov 7, 2021 · 144 comments
Assignees
Labels
accepted published Papers published in JOSS Python recommend-accept Papers recommended for acceptance in JOSS. review Track: 3 (PE) Physics and Engineering

Comments

@whedon
Copy link

whedon commented Nov 7, 2021

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

⚠️ JOSS reduced service mode ⚠️

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

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/10e7361e43785dbb1b3d659c5b01757a"><img src="https://joss.theoj.org/papers/10e7361e43785dbb1b3d659c5b01757a/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/10e7361e43785dbb1b3d659c5b01757a/status.svg)](https://joss.theoj.org/papers/10e7361e43785dbb1b3d659c5b01757a)

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:

  1. Make sure you're logged in to your GitHub account
  2. Be sure to accept the invite at this URL: https://github.com/openjournals/joss-reviews/invitations

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

@whedon
Copy link
Author

whedon commented Nov 7, 2021

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 🎉.

⚠️ JOSS reduced service mode ⚠️

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:

  1. Set yourself as 'Not watching' https://github.com/openjournals/joss-reviews:

watching

  1. You may also like to change your default settings for this watching repositories in your GitHub profile here: https://github.com/settings/notifications

notifications

For a list of things I can do to help you, just type:

@whedon commands

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@whedon generate pdf

@whedon
Copy link
Author

whedon commented Nov 7, 2021

PDF failed to compile for issue #3896 with the following error:

 Can't find any papers to compile :-(

@whedon
Copy link
Author

whedon commented Nov 7, 2021

Software report (experimental):

github.com/AlDanial/cloc v 1.88  T=0.11 s (659.4 files/s, 49581.6 lines/s)
-------------------------------------------------------------------------------
Language                     files          blank        comment           code
-------------------------------------------------------------------------------
Python                          60            586            375           3462
Markdown                         1             93              0            527
YAML                            10             33              6            257
-------------------------------------------------------------------------------
SUM:                            71            712            381           4246
-------------------------------------------------------------------------------


Statistical information for the repository '8066b4e37f38bca61302e6b0' was
gathered on 2021/11/07.
The following historical commit information, by author, was found:

Author                     Commits    Insertions      Deletions    % of changes
Maciej Manna                     9           196            263            1.06
Michael                         93          1687           1332            6.97
Michaeldz36                     38          3704           1752           12.60
Sylwester Arabas               334         14308           9780           55.61
kruci-no                         2            22              4            0.06
piotrbartman                     1            37           1207            2.87
prbartman                       42          3780           5245           20.83

Below are the number of rows from each author that have survived and are still
intact in the current revision:

Author                     Rows      Stability          Age       % in comments
Michael                     109            6.5         17.4               10.09
Sylwester Arabas           4095           28.6          5.4                8.03
kruci-no                      4           18.2         14.6                0.00
piotrbartman                215          581.1         17.5                2.33

@mjsottile
Copy link

@whedon generate pdf from branch JOSS

@whedon
Copy link
Author

whedon commented Nov 7, 2021

Attempting PDF compilation from custom branch JOSS. Reticulating splines etc...

@whedon
Copy link
Author

whedon commented Nov 7, 2021

👉📄 Download article proof 📄 View article proof on GitHub 📄 👈

@mjsottile
Copy link

@whedon check references

@mjsottile
Copy link

@whedon check references from branch JOSS

@whedon
Copy link
Author

whedon commented Nov 7, 2021

Attempting to check references... from custom branch JOSS

@whedon
Copy link
Author

whedon commented Nov 7, 2021

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1175/1520-0493(1983)111<0479:ASPDAS>2.0.CO;2 is OK
- 10.1016/0021-9991(84)90121-9 is OK
- 10.1016/0021-9991(86)90270-6  is OK
- 10.1016/0021-9991(90)90105-A is OK
- 10.1175/1520-0493(1993)121<1847:OFITDF>2.0.CO;2 is OK
- 10.1201/9780203711194 is OK
- 10.1006/jcph.1998.5901 is OK
- 10.1137/S106482759324700X is OK
- 10.1016/j.jcp.2004.12.021 is OK
- 10.1002/fld.1070 is OK
- doi:10.1002/fld.1071 is OK
- 10.1002/qj.1913 is OK
- 10.3233/SPR-140379 is OK
- 10.1016/j.jcp.2015.02.003 is OK
- 10.5194/gmd-8-1005-2015 is OK
- 10.1007/978-3-319-93864-6_5 is OK
- 10.5194/gmd-12-651-2019 is OK
- 10.1016/j.cam.2019.05.023 is OK
- 10.5194/gmd-2020-404 is OK

MISSING DOIs

- None

INVALID DOIs

- 10.1175/1520-0450(1968)007%3C0160:AOFDMA%3E2.0.CO;2 is INVALID
- 10.1175/1520-0493(1989)117%3C0102:TDSLTW%3E2.0.CO;2 is INVALID

@slayoo
Copy link

slayoo commented Nov 7, 2021

it's puzzling as the above "INVALID DOIs" seem correct, at leat both of the below URLs redirect correctly to the journal site:

@danielskatz
Copy link

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

@danielskatz
Copy link

And perhaps change the characters that are being encoded for example:

10.1175/1520-0493(1989)117<0102:TDSLTW>2.0.CO;2

@slayoo
Copy link

slayoo commented Nov 8, 2021

@whedon check references from branch JOSS

@whedon
Copy link
Author

whedon commented Nov 8, 2021

Attempting to check references... from custom branch JOSS

@whedon
Copy link
Author

whedon commented Nov 8, 2021

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1175/1520-0450(1968)007<0160:AOFDMA>2.0.CO;2 is OK
- 10.1175/1520-0493(1983)111<0479:ASPDAS>2.0.CO;2 is OK
- 10.1016/0021-9991(84)90121-9 is OK
- 10.1016/0021-9991(86)90270-6  is OK
- 10.1175/1520-0493(1989)117<0102:TDSLTW>2.0.CO;2 is OK
- 10.1016/0021-9991(90)90105-A is OK
- 10.1175/1520-0493(1993)121<1847:OFITDF>2.0.CO;2 is OK
- 10.1201/9780203711194 is OK
- 10.1006/jcph.1998.5901 is OK
- 10.1137/S106482759324700X is OK
- 10.1016/j.jcp.2004.12.021 is OK
- 10.1002/fld.1070 is OK
- doi:10.1002/fld.1071 is OK
- 10.1002/qj.1913 is OK
- 10.3233/SPR-140379 is OK
- 10.1016/j.jcp.2015.02.003 is OK
- 10.5194/gmd-8-1005-2015 is OK
- 10.1007/978-3-319-93864-6_5 is OK
- 10.5194/gmd-12-651-2019 is OK
- 10.1016/j.cam.2019.05.023 is OK
- 10.5194/gmd-2020-404 is OK

MISSING DOIs

- None

INVALID DOIs

- None

@slayoo
Copy link

slayoo commented Nov 8, 2021

thank you @danielskatz, indeed the URL escapes in the bib file were the cause - good job on the checker side!

@whedon
Copy link
Author

whedon commented Nov 21, 2021

👋 @dmikushin, please update us on how your review is going (this is an automated reminder).

@whedon
Copy link
Author

whedon commented Nov 21, 2021

👋 @olekravchenko, please update us on how your review is going (this is an automated reminder).

@mjsottile
Copy link

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.

@mjsottile
Copy link

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.

@slayoo
Copy link

slayoo commented Dec 9, 2021

Thank you, @mjsottile. (I haven't heard from the reviewers)

@mjsottile
Copy link

👋 @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!

@mjsottile
Copy link

👋 @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!

@editorialbot
Copy link
Collaborator

Doing it live! Attempting automated processing of paper acceptance...

@editorialbot
Copy link
Collaborator

🐦🐦🐦 👉 Tweet for this paper 👈 🐦🐦🐦

@editorialbot
Copy link
Collaborator

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

  1. Check final PDF and Crossref metadata that was deposited 👉 Creating pull request for 10.21105.joss.03896 joss-papers#3503
  2. Wait a couple of minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.03896
  3. If everything looks good, then close this review issue.
  4. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

@editorialbot editorialbot added accepted published Papers published in JOSS labels Sep 5, 2022
@slayoo
Copy link

slayoo commented Sep 5, 2022

@arfon Thank you!
Unfortunately, we have an issue with a non-breaking space in the title that is wrongly displayed on the JOSS website here:
image

@arfon
Copy link
Member

arfon commented Sep 5, 2022

Can you remove the &nbsp; from the title text please and I'll reprocess.

@arfon
Copy link
Member

arfon commented Sep 5, 2022

@slayoo fixed in open-atmos/PyMPDATA#338

@slayoo
Copy link

slayoo commented Sep 5, 2022

Merged, thank you, @arfon!

@slayoo
Copy link

slayoo commented Sep 5, 2022

BTW, we have an analogous problem in #4326

@arfon
Copy link
Member

arfon commented Sep 5, 2022

@editorialbot reaccept

@editorialbot
Copy link
Collaborator

Rebuilding paper!

@editorialbot
Copy link
Collaborator

🌈 Paper updated!

New PDF and metadata files 👉 openjournals/joss-papers#3506

@arfon
Copy link
Member

arfon commented Sep 5, 2022

OK, this should be fixed now.

@arfon arfon closed this as completed Sep 5, 2022
@editorialbot
Copy link
Collaborator

🎉🎉🎉 Congratulations on your paper acceptance! 🎉🎉🎉

If you would like to include a link to your paper from your README use the following code snippets:

Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.03896/status.svg)](https://doi.org/10.21105/joss.03896)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.03896">
  <img src="https://joss.theoj.org/papers/10.21105/joss.03896/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.03896/status.svg
   :target: https://doi.org/10.21105/joss.03896

This is how it will look in your documentation:

DOI

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:

@slayoo
Copy link

slayoo commented Sep 5, 2022

Thank you, @arfon !

@slayoo
Copy link

slayoo commented Sep 6, 2022

@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:

image

Just removed it in the repo: open-atmos/PyMPDATA@a35a159

Let me ask for one more regeneration of the metadata.
Thank you!
Sylwester

@slayoo
Copy link

slayoo commented Sep 9, 2022

@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

@kthyng
Copy link

kthyng commented Sep 9, 2022

@openjournals/dev Could you take a look at this?

@slayoo
Copy link

slayoo commented Sep 15, 2022

@kthyng, is there any better place to report such issues? (this issue is closed, so it's perhaps not the best place)
Thanks,
Sylwester

@xuanxu
Copy link
Member

xuanxu commented Sep 15, 2022

@kthyng if the paper is already updated in the original repo, the reaccept command should regenerate the metadata

@kthyng
Copy link

kthyng commented Sep 15, 2022

@editorialbot reaccept

@editorialbot
Copy link
Collaborator

Rebuilding paper!

@editorialbot
Copy link
Collaborator

🌈 Paper updated!

New PDF and metadata files 👉 openjournals/joss-papers#3530

@kthyng
Copy link

kthyng commented Sep 15, 2022

@slayoo How does your paper look now?

@slayoo
Copy link

slayoo commented Sep 15, 2022

@kthyng it's now fixed:
image

Thank you for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted published Papers published in JOSS Python recommend-accept Papers recommended for acceptance in JOSS. review Track: 3 (PE) Physics and Engineering
Projects
None yet
Development

No branches or pull requests