-
-
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]: ASIMTools: A lightweight workflow and simulation manager for reproducible atomistic simulations #6929
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: |
Five most similar historical JOSS papers: strucscan: A lightweight Python-based framework for high-throughput material simulation Simmate: a framework for materials science excitingtools: An exciting Workflow Tool FHI-vibes: Ab Initio Vibrational Simulations matscipy: materials science at the atomic scale with Python |
👋 @mkphuthi - thanks for your submission. Can you please add the countries to the author affiliations? Also, JOSS papers are requested to be around 1000 words at most, and this is 2000, so you will have to reduce the content somewhat. Sometimes, there are parts of the paper that either duplicate documentation in the repo, or that could move into documentation in the repo (in this case, perhaps one or both of the examples). Finally, you need to add a references header at the end of the .md file, so that when the references are added to the PDF, they have a header in front of them. After you make changes in your .md file, you can then use the command |
@editorialbot generate pdf |
Five most similar historical JOSS papers: excitingtools: An exciting Workflow Tool Atomic Simulation Interface (ASI): application programming interface for electronic structure codes ShakeNBreak: Navigating the defect configurational landscape Surfaxe: Systematic surface calculations GIMS: Graphical Interface for Materials Simulations |
@editorialbot check repository |
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: ✅ License found: |
thanks @mkphuthi - we're just having a short discussion about which JOSS track this best fits in, then we'll start the process |
👋 @mkphuthi - we've moved this, as you can see, and you should hear from the new track editor next |
@editorialbot invite @HaoZeke as editor |
Invitation to edit this submission sent! |
@editorialbot assign @HaoZeke as editor Thanks for the invite @Kevin-Mattheus-Moerman, I'm happy to accept @mkphuthi thanks for the suggestions, I will start sending out invitations by the end of this week. |
Assigned! @HaoZeke is now the editor |
hi @utf @Andrew-S-Rosen @janosh 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: joss.readthedocs.io/en/latest/review_criteria.html If not, could you recommend any potential reviewers? I was hoping to have your insights because of your work on atomate and jobflow. |
hi @askhl 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: joss.readthedocs.io/en/latest/review_criteria.html If not, could you recommend any potential reviewers? I was hoping to have your insights because of your work on ASE and ASE workflows... |
hi @PavelStishenko @thohamm 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: joss.readthedocs.io/en/latest/review_criteria.html If not, could you recommend any potential reviewers? I was hoping to have your insights because of your work on ASI woskflows and strucscan.. |
@HaoZeke: Thank you for reaching out. Unfortunately, I will have to decline, as I have too much of a conflict of interest due to https://github.com/Quantum-Accelerators/quacc. |
I also have to decline due to CoI. |
I'm sorry but I have to decline due to time constraints. |
Hi @imtambovtcev 👋 would you be interested in and available to review this JOSS submission? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: joss.readthedocs.io/en/latest/review_criteria.html |
Hi Rohit,
I'm very sorry, but there is no way I will have time to review.
Best regards
Ask
Am Di., 9. Juli 2024 um 19:54 Uhr schrieb Rohit Goswami <
***@***.***>:
… hi @askhl <https://github.com/askhl> 👋 would you be interested in and
available to review this JOSS submission? We carry out our checklist-driven
reviews here in GitHub issues and follow these guidelines:
joss.readthedocs.io/en/latest/review_criteria.html
If not, could you recommend any potential reviewers? I was hoping to have
your insights because of your work on ASE and ASE workflows...
—
Reply to this email directly, view it on GitHub
<#6929 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMVG2J5GREUBCANW6WXCKLZLQPUJAVCNFSM6AAAAABJ4RLA2KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJYGMZDCNRRHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@HaoZeke I will be open to review this submission. Feel free to tag me as additional reviewer. |
@editorialbot add @abhishektiwari as reviewer @abhishektiwari thanks for volunteering :) |
@abhishektiwari added to the reviewers list! |
@HaoZeke, I just came from vacation and am ready to review |
@editorialbot add @imtambovtcev as reviewer @imtambovtcev thanks stepping up :) |
@imtambovtcev added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #7085. |
Submitting author: @mkphuthi (Mgcini Keith Phuthi)
Repository: https://github.com/BattModels/asimtools.git
Branch with paper.md (empty if default branch):
Version: v0.0.0
Editor: @HaoZeke
Reviewers: @abhishektiwari, @imtambovtcev
Managing EiC: Daniel S. Katz
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @mkphuthi. Currently, there isn't a JOSS editor assigned to your paper.
@mkphuthi 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: