-
-
Notifications
You must be signed in to change notification settings - Fork 41
[PRE REVIEW]: Atomic Simulation Interface (ASI): application programming interface for electronic structure codes #5011
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:
|
Checking the BibTeX entries failed with the following error:
|
|
Failed to discover a |
|
|
Hello @PavelStishenko, here are the things you can ask me to do:
|
@editorialbot generate pdf |
Notes for this submission
|
@PavelStishenko thanks for this submission. I am the AEiC for this track and here to help with the first steps and to check if this work is in scope for JOSS. Can you clarify if the following two links are equivalent/the same or if they contain different functionality: If they are the same, does the main development take place on the first or second link? I am assuming the first since that one is provided as the repository for the paper too. |
@editorialbot set joss-paper as branch |
Done! branch is now joss-paper |
@editorialbot check repository |
|
Wordcount for |
@PavelStishenko looks like I missed that you added the paper to the |
I ran
|
@editorialbot invite @lucydot as editor @lucydot this looks like your cup of tea, is that right? 🍵 |
Invitation to edit this submission sent! |
@Kevin-Mattheus-Moerman absolutely my cup of tea, I'm happy to edit. RE: potential Conflict of Interest - I am co-I on a bid submission (unrelated to this project) with two of the authors. The bid submission includes many different researchers from across the UK (I'd say around 30) and relates to community infrastructure - I don't work closely on a day-to-day basis with any of the authors. Personally I don't judge it to be a COI but will disclose here and happy to pass on if it could be perceived as so. |
@lucydot thanks for getting back to me so quickly, and for sharing that information. I'm afraid that does sound like it could be perceived as a COI so I'll work to find an alternative editor. Thanks again. |
@editorialbot set master as branch |
Done! branch is now master |
@Kevin-Mattheus-Moerman , no, the main development take place on GitLab repo (second link). I have created the GitHub mirror specifically for JOSS submission. |
@editorialbot invite @jgostick as editor |
Invitation to edit this submission sent! |
Hi @Kevin-Mattheus-Moerman, I'm sorry but I am not qualified to edit molecular dynamics packages, as I learned this past summer when I was unable to effectively adjudicate a review that went awry. |
👋 @Kevin-Mattheus-Moerman I could edit this if needed. |
@editorialbot assign @rkurchin as editor |
Assigned! @rkurchin is now the editor |
👋 @xwang862, @jeffhammond, and @keipertk, 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 |
@rkurchin thanks for inviting. Sure, I'd love to review it. |
@editorialbot add @xwang862 as reviewer |
@xwang862 added to the reviewers list! |
👋 @rangsimanketkaew, 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 |
👋 @yES, 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 |
👋 @vijaymocherla, 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 |
Hi @rkurchin, |
👋 @junghans, 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 |
👋 @srmnitc, 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 can do it. |
I can help review this submission |
@editorialbot add @junghans as reviewer |
@junghans added to the reviewers list! |
@editorialbot add @srmnitc as reviewer |
@srmnitc added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #5186. |
Submitting author: @PavelStishenko (Pavel Stishenko)
Repository: https://gitlab.com/pvst/asi
Branch with paper.md (empty if default branch): master
Version: v1.0
Editor: @rkurchin
Reviewers: @xwang862, @junghans, @srmnitc
Managing EiC: Kevin M. Moerman
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @PavelStishenko. Currently, there isn't a JOSS editor assigned to your paper.
@PavelStishenko if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission (please start at the bottom of the list).
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: