-
-
Notifications
You must be signed in to change notification settings - Fork 38
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]: Gauss-Radau Small-body Simulator (GRSS): An Open-Source Library for Planetary Defense #7488
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: |
@rahil-makadia — Thanks for your submission! All the suitable JOSS editors are currently working at capacity so I'm going to "waitlist" this review until an editor with the relevant expertise is available to take it on. Thanks for your patience! |
Five most similar historical JOSS papers: KerrGeoPy: A Python Package for Computing Timelike Geodesics in Kerr Spacetime SpiceyPy: a Pythonic Wrapper for the SPICE Toolkit SkyPy: A package for modelling the Universe NAIF PDS4 Bundler: A Python package to generate SPICE PDS4 archives GECo: A collection of solvers for the self-gravitating Vlasov equations |
For whichever editor might pick this up, note that this is a joint publication with AAS Journals (specifically, the Planetary Science Journal). 🌍 |
@warrickball Looks like it might take some time before the review starts on this paper. Let me know if there's anything to do in the meantime or if it's just a waiting game right now... |
I'm afraid it is mostly a waiting game. Hopefully an editor will become available within a week or two, and they'll then start seeking reviewers. The basic metadata properties all look good. My only comment on the paper at this point is that we prefer inline hyperlinks to footnotes. |
@editorialbot set dev as branch Changing branch to dev since that's where I first make edits |
Done! branch is now dev |
@editorialbot check repository |
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: 🟡 License found: |
@editorialbot generate pdf |
Five most similar historical JOSS papers: KerrGeoPy: A Python Package for Computing Timelike Geodesics in Kerr Spacetime GECo: A collection of solvers for the self-gravitating Vlasov equations SpiceyPy: a Pythonic Wrapper for the SPICE Toolkit SkyPy: A package for modelling the Universe MG-MAMPOSSt, a Fortran code to test gravity at galaxy-cluster scales |
@editorialbot generate pdf I have updated the footnotes to inline hyperlinks as per suggestion |
Five most similar historical JOSS papers: SpiceyPy: a Pythonic Wrapper for the SPICE Toolkit KerrGeoPy: A Python Package for Computing Timelike Geodesics in Kerr Spacetime SkyPy: A package for modelling the Universe NAIF PDS4 Bundler: A Python package to generate SPICE PDS4 archives Swiftest: An \textit{N}-body Integrator for Gravitational Systems |
Submitting author: @rahil-makadia (Rahil Makadia)
Repository: https://github.com/rahil-makadia/grss
Branch with paper.md (empty if default branch): dev
Version: v4.3.6
Editor: Pending
Reviewers: Pending
Managing EiC: Warrick Ball
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @rahil-makadia. Currently, there isn't a JOSS editor assigned to your paper.
@rahil-makadia 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: