Closed editorialbot closed 2 months ago
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:
@editorialbot commands
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
@editorialbot generate pdf
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1016/s0149-7634(01)00062-8 is OK
- 10.1209/0295-5075/81/48002 is OK
- 10.1103/physreve.94.032311 is OK
MISSING DOIs
- None
INVALID DOIs
- None
Software report:
github.com/AlDanial/cloc v 1.90 T=0.06 s (1290.4 files/s, 216114.6 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
HTML 24 537 72 3854
SVG 1 0 0 2671
JavaScript 13 150 261 967
CSS 6 192 45 788
Python 7 202 370 395
reStructuredText 23 329 514 177
Markdown 2 58 0 124
YAML 2 19 6 96
Jupyter Notebook 1 0 1751 59
TeX 1 5 0 36
DOS Batch 1 8 1 26
make 1 4 7 9
-------------------------------------------------------------------------------
SUM: 82 1504 3027 9202
-------------------------------------------------------------------------------
Commit count by author:
61 Alisha Angdembe
1 AlishaAng
Paper file info:
📄 Wordcount for paper.md
is 1659
✅ The paper includes a Statement of need
section
License info:
✅ License found: MIT License
(Valid open source OSI approved license)
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Five most similar historical JOSS papers:
timeseriesflattener: A Python package for summarizing features from (medical) time series
Submitting author: @MartinBernstorff
Handling editor: @mstimberg (Active)
Reviewers: @yarikoptic, @Ebedthan
Similarity score: 0.6826
interflow: A Python package to organize, calculate, and visualize sectoral interdependency flow data
Submitting author: @kmongird
Handling editor: @fraukewiese (Active)
Reviewers: @wiljnich, @j3r3m1
Similarity score: 0.6716
plotastic: Bridging Plotting and Statistics in Python
Submitting author: @markur4
Handling editor: @rkurchin (Active)
Reviewers: @gmrandazzo, @SunnyXu
Similarity score: 0.6716
ewstools: A Python package for early warning signals of bifurcations in time series data
Submitting author: @ThomasMBury
Handling editor: @osorensen (Active)
Reviewers: @mhu48, @mikesha2, @ranzhengcode
Similarity score: 0.6688
dtrackr: An R package for tracking the provenance of data
Submitting author: @robchallen
Handling editor: @ajstewartlang (Active)
Reviewers: @debruine, @craig-willis
Similarity score: 0.6665
⚠️ Note to editors: If these papers look like they might be a good match, click through to the review issue for that paper and invite one or more of the authors before considering asking the reviewers of these papers to review again for JOSS.
@editorialbot reject
:wave: @AlishaAng - Thank you for your submission to JOSS. At this time we have to reject this submission due to not meeting the substantial scholarly effort requirements due to:
We wish you the best in continuing your work and look forward to seeing more from you in the future.
Thank you.
Paper rejected.
Hello @crvernon,
Thank you for the feedback. I have some questions regarding the requirements that I did not meet according to the report. The software report indicates that my Python code exceeds 300 lines, and my commit history goes back 4 months. I thought this was acceptable, but it seems I may have misunderstood the requirements.
Could you please clarify this for me?
Thank you, Alisha
:wave: @AlishaAng - the statement in our documentation for substantial scholarly effort is:
Total lines of code (LOC). Submissions under 1000 LOC will usually be flagged, those under 300 LOC will be desk rejected.
In almost all cases, we require a codebase of at least 1000 lines of code and often those around 1000 will get reviewed for scope as well. Sorry for the confusion with this and thank you for the follow-up question.
Submitting author: !--author-handle-->@AlishaAng<!--end-author-handle-- (Alisha Angdembe) Repository: https://github.com/ai-multiply/bursty_dynamics.git Branch with paper.md (empty if default branch): paper Version: 0.1.0 Editor: Pending Reviewers: Pending Managing EiC: Chris Vernon
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @AlishaAng. Currently, there isn't a JOSS editor assigned to your paper.
@AlishaAng 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: