-
-
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]: SlicerSPECTRecon: A 3D Slicer Extension for SPECT Image Reconstruction #7231
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: |
|
Correction made to ORCID. |
@editorialbot generate pdf |
Five most similar historical JOSS papers: Virtual Scanner: MRI on a Browser elsa: an elegant framework for tomographic reconstruction PyMedPhys: A community effort to develop an open, Python-based standard library for medical physics applications Radial Interstices Enable Speedy Low-volume Imaging PyQMRI: An accelerated Python based Quantitative MRI toolbox |
Potential reviewers:
|
@ObedDzik Dear author, thanks for this submission. I am the AEiC on this track and here to help process the initial steps. Since all editors in this domain are currently busy handling other submission, I've just waitlisted this submission. I aim to assign an editor as soon as possible. |
@samhforbes you are currently handling a large amount of other submissions. I was wondering, is this submission something you could help edit once you are available? |
@editorialbot invite @mstimberg as editor |
Invitation to edit this submission sent! |
@Kevin-Mattheus-Moerman thanks for the update. |
@editorialbot assign me as editor @Kevin-Mattheus-Moerman apologies for the late reply, happy to edit this submission 😊 |
Assigned! @mstimberg is now the editor |
@mstimberg that is great thanks! |
👋 @ObedDzik I will be the editor for your submission, looking forward to working with you. |
@mstimberg Great! We suggest Marek Oerlemans, Thomas Else, Jonathan Bach Martin, and Ibrahim Hadzic. |
@mstimberg thanks for coordinating this! Is there any updates on the review process? |
@lukepolson Unfortunately, finding reviewers has been more difficult than I hoped (I have a couple of replies pending, and two potential reviewers have declined). On the good side, I've just found a first reviewer who agreed, and I will add them to this issue right away. |
@editorialbot add @zapaishchykova as reviewer Many thanks again for helping us out! |
@zapaishchykova added to the reviewers list! |
@editorialbot add @cnmy-ro as reviewer Welcome aboard! |
@cnmy-ro added to the reviewers list! |
I am still waiting for a reply from a potential reviewer, but we can still add them later to the process. I will now start the review, which will close this issue and open a new one. See you on the other side! |
@editorialbot start review |
OK, I've started the review over in #7399. |
Submitting author: @ObedDzik (Obed Dzikunu)
Repository: https://github.com/PyTomography/slicer_spect_recon.git
Branch with paper.md (empty if default branch): j_paper
Version: v1.0.0
Editor: @mstimberg
Reviewers: @zapaishchykova, @cnmy-ro
Managing EiC: Kevin M. Moerman
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @ObedDzik. Currently, there isn't a JOSS editor assigned to your paper.
@ObedDzik 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: