-
-
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]: cookiecutter-cmdstanpy-analysis: an interactive template for statisical analysis projects #4760
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:
|
|
Wordcount for |
|
👋 @teddygroves - thanks for your submission. Due to the relatively small amount of code, the editors will now discuss if it meets the substantial scholarly effort criterion for review by JOSS. I'm also unsure if it is research software as defined by JOSS. You should hear back in a week or so. |
@editorialbot query scope |
Submission flagged for editorial review. |
Sounds good, please let me know if I can make your assessment easier by clarifying anything! |
I made a few minor changes today, including adding the flagged doi for pytest. @editorialbot generate pdf |
@editorialbot check references |
@editorialbot check repository |
|
Wordcount for |
@editorialbot generate pdf |
@editorialbot check references |
@editorialbot check repository |
|
Wordcount for |
fwiw this repository contains over 1000 lines of source code (648+93+75+75+71+26+22 as above + 64 non-blank lines in |
Hello @teddygroves, unfortunately, after further review, the JOSS editorial team has decided that your submission does not fit our scope in terms of substantial scholarly effort to proceed to review. This is not a judgment about the quality or usefulness of your software. We encourage you to pursue alternate venues for sharing and receiving credit for your work, including archiving the software on Zenodo to create a DOI. |
@editorialbot reject |
Paper rejected. |
@kyleniemeyer thanks for the pre-review! I’d really like to resubmit this project in the future if possible so I’d very much appreciate some advice if it’s not too much trouble. First, is it possible to confirm whether the project is in scope as research software? This was part of the original query I think. Second, is there a particular area that I should focus on in order to demonstrate additional scholarly effort? |
@teddygroves the feedback focused on the small size, and the fact that it looked more like a minor utility rather than research software. There was also a question about whether a cookie cutter/template would be research software; the software packages that your utility relies on to do the actual calculations/processing/etc. certainly are. |
Thanks a lot for the extra feedback! It sounds like the research software scope question came up but wasn’t settled definitively, and that the main issue regarding scholarly effort is the amount of code. Good to know! |
Submitting author: @teddygroves (Teddy Groves)
Repository: https://github.com/teddygroves/cookiecutter-cmdstanpy-analysis/
Branch with paper.md (empty if default branch):
Version: 1.0.1
Editor: Pending
Reviewers: Pending
Managing EiC: Daniel S. Katz
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @teddygroves. Currently, there isn't a JOSS editor assigned to your paper.
@teddygroves 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: