-
-
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]: PyGMI - a python package for geoscience modelling and interpretation #6472
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: |
Hi @Patrick-Cole and thanks for your submission! We have a backlog of submissions so I will add this to our waitlist. In the meantime, please suggest 5 reviewers from the database listed above or your own (non-conflicted) extended network. Their github handles are most useful to receive but please don't use "@" to reference them since it will prematurely ping them. Thanks for your patience. |
Hi, I chose reviewers on the list based on geophysics, python and earth sciences, but honestly, I am not fussy. Matt Hall |
@fraukewiese Could you edit this submission? |
@editorialbot invite @fraukewiese as editor |
Invitation to edit this submission sent! |
@fraukewiese might you be able to edit this submission? |
Hi, sorry for the late response. The submission does not fit to my area of expertise, so I need to reject. |
@martinfleis Could you edit this submission? |
@editorialbot invite @martinfleis as editor |
Invitation to edit this submission sent! |
Hi @kthyng, If @martinfleis was not available, you could consider inviting me as editor. Geoscience is not my area of expertise, but I belong to a "School of Mines" so many of my colleagues would be great potential reviewers. |
A volunteer! I will most definitely take you up on this! |
@editorialbot assign @boisgera as editor |
Assigned! @boisgera is now the editor |
I am following several leads internally for reviewers ; I've been recently given a list of people that would be great for this by the head of the Geostats team. I am contacting some of them right now. |
Still following the lead for reviewers in my institution. Great discussion with two of them very recently ; one element of feedback that I have is that they are wary of the magnitude of the work (given that the code base has > 30k loc) ; they need a moment to consider if they go for it or not. |
And ... I failed to convince them. Contacting new potential reviewers right now. |
A new potential reviewer declined after evaluation of the paper. He didn't feel that he had enough expertise on many of the project features (and also, lack of time). I am going back to the list of potential rewievers. |
@editorialbot generate pdf |
Five most similar historical JOSS papers: GemGIS - Spatial Data Processing for Geomodeling planetMagFields: A Python package for analyzing and plotting planetary magnetic field data emg3d: A multigrid solver for 3D electromagnetic diffusion GeoBO: Python package for Multi-Objective Bayesian Optimisation and Joint Inversion in Geosciences Geodata-Harvester: A Python package to jumpstart geospatial data extraction and analysis |
@boisgera Maybe some of the authors of these similar papers could be relevant? |
Yes, thank you @kthyng! I was pushing for reviewers coming from my institution so far because I thought that it was worth introducing some new people to JOSS reviews. I also think that it would be beneficial to these researchers (so far the people which have accepted to review for JOSS on my demand like the process a lot better than the classic review process). But it's now likely that I'll have to contact external reviewers already familiar with JOSS. I have sent today e-mails to the last 2 "obvious" potential reviewers internally and if its doesn't pan out, the authors on your liste are next! |
I like your plan @boisgera! |
Started to reach out for JOSS paper authors. |
@editorialbot add @AnkitBarik as reviewer |
@AnkitBarik added to the reviewers list! |
@editorialbot generate checklist |
I'm sorry human, I don't understand that. You can see what commands I support by typing:
|
@editorialbot commands |
Hello @AnkitBarik, here are the things you can ask me to do:
|
@editorialbot generate my checklist |
Checklists can only be created once the review has started in the review issue |
Hi @kthyng, @AnkitBarik, I am discussing with a potential 2nd reviewer who wanted to reach for a colleague first. Hopefully we will be able to start the review soon! |
@editorialbot add @AlexanderJuestel as reviewer |
@AlexanderJuestel added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #7019. |
Submitting author: @Patrick-Cole (Patrick Cole)
Repository: https://github.com/Patrick-Cole/pygmi
Branch with paper.md (empty if default branch):
Version: v3.2.8.0
Editor: @boisgera
Reviewers: @AnkitBarik, @AlexanderJuestel
Managing EiC: Kristen Thyng
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @Patrick-Cole. Currently, there isn't a JOSS editor assigned to your paper.
@Patrick-Cole 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: