-
-
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]: MontePy: a Python library for reading, editing, and writing MCNP input files. #6977
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: Monte Carlo / Dynamic Code (MC/DC): An accelerated Python package for fully transient neutron transport and rapid methods development WATTS: Workflow and template toolkit for simulation polypy - Analysis Tools for Solid State Molecular Dynamics and Monte Carlo Trajectories PYroMat: A Python package for thermodynamic properties PyMedPhys: A community effort to develop an open, Python-based standard library for medical physics applications |
Hello @MicahGale, sorry for the delay in processing this. Unfortunately, we do not have any editors available to handle your submission right now, so I have to put this on our waitlist. In the meantime, any reviewer recommendations would be welcome (though please don't actually tag/request folks yourself). |
The MCNP 6.3 manual does have a DOI number on OSTI. I will have to check but changing to citing the 6.3 manual will probably make sense.
Nothing can be done here.
This report is on OSTI as an INL external report, and it's odd that it doesn't have a DOI. I will ask around to see if this can be given a DOI. |
Thank you @kyleniemeyer for the update, and moving this along for the time being. I will get you a list of potential reviewers in the next few days. Just as a heads up I will be on vacation starting next week through August 12, and won't be checking GitHub during that time. If needed @tjlaboss should be able to address most concerns about this paper during that time. |
For reviews might I suggest:
|
This makes sense to me. Not only is MCNP6.3 the most recent version at time of submission, but also its documentation has been cleaned up and expanded since 6.2. |
Hello @kyleniemeyer , Chiara speaking here, I am currently serving as editor in chief for pyOpenSci: @MicahGale submitted MontePy to pyOpenSci, without knowing we have a collaboration with JOSS. I cannot guarantee to find an editor faster than JOSS, but moving forward via pyOpenSci we can probably optimize the number of volounteers mobilized for this review: would that sound reasonable? |
@kyleniemeyer 👋 I could take this on as editor. |
@editorialbot assign @kellyrowland as editor Thank you! |
Assigned! @kellyrowland is now the editor |
@cmarmo sorry, I just saw your note about pyOpenSci. Normally, for rOpenSci and pyOpenSci, our fast-track process kicks in after the package was reviewed and approved there, to avoid reviewing the same things twice. Then, the JOSS editor essentially just checks for scope and then reviews the paper. If @MicahGale is fine with it, we can pause the JOSS review until the pyOpenSci review has concluded, and then handle the paper fast-track acceptance afterwards. (This will probably take the same amount of time anyways!) |
That sounds good to me. |
@kyleniemeyer , I'm having trouble finding editors this summer, but I think the "pyOpenSci then JOSS" workflow can save reviewers some time. On the other hand, you've already found an editor. So, I dare to imagine a scenario... let me know if it could be feasible... What if @kellyrowland would be interested in being an editor for the pyOpenSci submission? |
@editorialbot generate pdf |
Five most similar historical JOSS papers: WATTS: Workflow and template toolkit for simulation Monte Carlo / Dynamic Code (MC/DC): An accelerated Python package for fully transient neutron transport and rapid methods development PYroMat: A Python package for thermodynamic properties polypy - Analysis Tools for Solid State Molecular Dynamics and Monte Carlo Trajectories model-traits: Model attribute definitions for scientific simulations in C++ |
@editorialbot commands |
Hello @MicahGale, here are the things you can ask me to do:
|
@editorialbot check references |
|
link to pyOpenSci issue: pyOpenSci/software-submission#205 |
Submitting author: @MicahGale (Micah D. Gale)
Repository: https://github.com/idaholab/MontePy
Branch with paper.md (empty if default branch): joss_submit
Version: v0.2.7
Editor: @kellyrowland
Reviewers: Pending
Managing EiC: Kyle Niemeyer
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @MicahGale. Currently, there isn't a JOSS editor assigned to your paper.
@MicahGale 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: