-
-
Notifications
You must be signed in to change notification settings - Fork 41
[PRE REVIEW]: GroLink: A general application programming interface for the plant-modeling platform GroIMP #7846
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
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:
✅ The paper includes a |
License info: 🟡 License found: |
Five most similar historical JOSS papers: PlantSimEngine: A Simulation Engine For The Soil-Plant-Atmosphere System GIMS: Graphical Interface for Materials Simulations CGIMP: Real-time exploration and covariate projection for self-organizing map datasets glottospace: R package for language mapping and geospatial analysis of linguistic and cultural data Cacatoo: building, exploring, and sharing spatially structured models of biological systems |
Hi @tim12312! You said in your note that there are Python and R client libraries. Are those meant to be reviewed with this submission and if so where are they located? |
Hi @kthyng The libraries are used in the presented examples and therefore are part of the submission. They can be found here: |
Hi @tim12312 and thanks for your submission! I am looking for some specific items to make sure your submission fits our requirements at a high level (not at the more detailed review level) before moving on to finding an editor or putting this on our waitlist if no relevant editors are available. I'll comment over time as I have a chance to go through them:
In the meantime, please take a look at the comments above ⬆️ from the editorialbot to address any DOI, license, or paper issues if you're able (there may not be any), or suggest reviewers. For reviewers, 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. |
@tim12312 Your paper is on the long end. Please shorten it by 200-300 words please. @rwegener2 Could you edit this submission? |
@editorialbot invite @rwegener2 as editor |
Invitation to edit this submission sent! |
@editorialbot add me as editor |
Assigned! @rwegener2 is now the editor |
👋🏻 @antoineruzette and @AnjaConev, would you be willing to review this submission for JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html |
@kthyng I just updated the paper, the length should now be in the range. |
Hi @rwegener2 I'm afraid this work is outside of the scope of my expertise and I thus have to decline. Cheers |
No problem, thanks for the reply! |
@tim12312 I will continue to search for reviewers, but would you also please suggest 3-5 potential reviewers for this submission? You can list their Github handles without the @ sign, so they do not get tagged yet. Thank you! |
👋🏻 @oparisot and @sebastian-raubach, would you be willing to review this submission for JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html |
@rwegener2 It's not directly my field of expertise, I would suggest to find an other reviewer for this specific submission! |
@rwegener2 Similar to oparisot, this falls outwith my expertise, so I'd be reluctant to agree to be a reviewer. |
👋🏻 @arbennett, would you be willing to review this submission for JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html I see you are already reviewing a submission at the moment, but I'm happy to extend the usual timeframe for reviews to accommodate that. |
👋🏻 @iimog, would you be willing to review this submission for JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html I see you are already reviewing a submission at the moment, but I'm happy to extend the usual timeframe for reviews to accommodate that. |
No worries, thanks for the response @oparisot and @sebastian-raubach! |
Thanks @rwegener2 for the invitation. While the project looks interesting, I'm afraid, I don't have the proper expertise to provide a timely review. |
@rwegener2 - sorry to also bail, but I am already in the process of doing 3 other reviews at the moment so don't have capacity. Thanks for the invitation to review though! |
No problem @iimog and @arbennett. Thanks for the timely reply! |
👋🏻 @VEZY, would you be willing to review this submission for JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html The repository linked above is in Java, but there are also client libraries in Python and R that are part of the review: |
👋🏻 @jtagusari, would you be willing to review this submission for JOSS? We are looking for a reviewer with knowledge of Java. We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html |
@rwegener2 Thank you for the offer. However, I am not very familiar with java and have been very busy lately, so I don't think I will have the time to get involved. I would like to decline this offer. |
No problem @jtagusari, thanks for the speedy reply! |
👋🏻 @egonw, would you be willing to review this submission for JOSS? We are looking for a reviewer with knowledge of Java. We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html |
@rwegener2, yes, accepted. |
Submitting author: @tim12312 (Tim Oberländer)
Repository: https://gitlab.com/grogra/groimp-plugins/api
Branch with paper.md (empty if default branch):
Version: 1.6
Editor: @rwegener2
Reviewers: Pending
Managing EiC: Kristen Thyng
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @tim12312. Currently, there isn't a JOSS editor assigned to your paper.
@tim12312 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: