-
-
Notifications
You must be signed in to change notification settings - Fork 36
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]: SAnTex: A Python-based Library for Seismic Anisotropy Calculation #6706
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 @utpal-singh 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. |
@utpal-singh some comments/questions:
|
Hi @kthyng , Thank you for your feedback. Although the documentation is in the readme.pdf, but I will also upload the readthedocs link. I will also add tests to insure proper functionality. I appreciate your feedback. Thanks. Utpal |
@editorialbot commands |
Hello @utpal-singh, 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 |
@editorialbot generate pdf |
@utpal-singh I see you added a tests file. That is ok though it is pretty short. You can probably make an argument (though I haven't looked in detail) that your examples and notebook can be used to verify behavior. You might also consider integrating these into your readthedocs now that you have everything so nicely set up, to make them more user-friendly. This is a suggestion not a requirement (at this point). Hi author and thanks for your submission! We have a backlog of submissions so I will add this to our waitlist. Thanks for your patience. 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. |
Hi @kthyng, Thanks for checking the repo. Here are some of the reviewers I can suggest (non-conflicted)
|
@rkurchin Might you be able to edit this submission? |
@editorialbot invite @rkurchin as editor |
Invitation to edit this submission sent! |
@editorialbot assign me as editor Sure, I should be able to handle this. |
Assigned! @rkurchin is now the editor |
👋 @elena-pascal and/or @SunilAnandatheertha, 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 |
Sure, looks interesting. |
@editorialbot add @elena-pascal as reviewer |
@elena-pascal added to the reviewers list! |
Should be ok. Happy to review.
…On Sat, 1 Jun 2024 at 01:34, The Open Journals editorial robot < ***@***.***> wrote:
@elena-pascal <https://github.com/elena-pascal> added to the reviewers
list!
—
Reply to this email directly, view it on GitHub
<#6706 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APY25RVWLYO4JEKLAGXC3Y3ZFEJKBAVCNFSM6AAAAABHAYKNTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGE3TIMBXGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Kind regards
Sunil
|
@editorialbot generate my checklist |
Checklists can only be created once the review has started in the review issue |
Submitting author: @utpal-singh (Utpal Singh)
Repository: https://github.com/utpal-singh/SAnTex
Branch with paper.md (empty if default branch): main
Version: v1.2
Editor: @rkurchin
Reviewers: @elena-pascal
Managing EiC: Kristen Thyng
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @utpal-singh. Currently, there isn't a JOSS editor assigned to your paper.
@utpal-singh 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: