Closed editorialbot closed 1 year 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
Checking the BibTeX entries failed with the following error:
No paper file path
Software report:
github.com/AlDanial/cloc v 1.88 T=0.16 s (1634.3 files/s, 324393.9 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Rust 143 4228 4235 25118
JSON 2 0 0 3808
Python 18 541 251 1708
YAML 22 35 19 1063
Jupyter Notebook 11 0 5302 954
Markdown 7 191 0 513
reStructuredText 22 356 297 337
TOML 11 57 16 317
CSS 2 65 11 276
TeX 1 27 0 245
SVG 5 0 0 230
JavaScript 3 11 4 55
make 2 12 7 29
DOS Batch 1 8 1 26
Dockerfile 1 14 0 26
HTML 3 0 0 23
-------------------------------------------------------------------------------
SUM: 254 5545 10143 34728
-------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Failed to discover a Statement of need
section in paper
:warning: An error happened when generating the pdf. Paper file not found.
@narnolddd Please correct the above errors so I can proceed with your submission. I will invite an editor, but we need a clean build on the paper to proceed.
@editorialbot invite @luizirber as editor
Invitation to edit this submission sent!
@luizirber Just checking whether you saw my invitation to edit.
Hi! Apologies I didn't respond to this, been at a conference last week. I'll have a dig into the build bug now, seemed to be working earlier so I will see what has happened.
@editorialbot commands
Hello @luizirber, here are the things you can ask me to do:
# List all available commands
@editorialbot commands
# Add to this issue's reviewers list
@editorialbot add @username as reviewer
# Remove from this issue's reviewers list
@editorialbot remove @username from reviewers
# Get a list of all editors's GitHub handles
@editorialbot list editors
# Assign a user as the editor of this submission
@editorialbot assign @username as editor
# Remove the editor assigned to this submission
@editorialbot remove editor
# Remind an author, a reviewer or the editor to return to a review after a
# certain period of time (supported units days and weeks)
@editorialbot remind @reviewer in 2 weeks
# Check the references of the paper for missing DOIs
@editorialbot check references
# Perform checks on the repository
@editorialbot check repository
# Adds a checklist for the reviewer using this command
@editorialbot generate my checklist
# Set a value for version
@editorialbot set v1.0.0 as version
# Set a value for branch
@editorialbot set joss-paper as branch
# Set a value for repository
@editorialbot set https://github.com/organization/repo as repository
# Set a value for the archive DOI
@editorialbot set set 10.5281/zenodo.6861996 as archive
# Mention the EiCs for the correct track
@editorialbot ping track-eic
# Generates the pdf paper
@editorialbot generate pdf
# Recommends the submission for acceptance
@editorialbot recommend-accept
# Generates a LaTeX preprint file
@editorialbot generate preprint
# Flag submission with questionable scope
@editorialbot query scope
# Get a link to the complete list of reviewers
@editorialbot list reviewers
# Creates a post-review checklist with editor and authors tasks
@editorialbot create post-review checklist
# Open the review issue
@editorialbot start review
@editorialbot assign @luizirber as editor
Assigned! @luizirber is now the editor
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
I think the error should have resolved now, sorry for the delay! Some people I'd like to recommend as reviewers are:
Thanks!
Just checking the pdf issue is now resolved @luizirber? Thanks.
Hi @luizirber @gkthiruvathukal would it be possible to get an update on this? No worries if it's taking a while to get reviewers etc, just want to know that there's nothing holding up on our end.
@luizirber @gkthiruvathukal any update?
@narnolddd just a bit backlogged. I am working through some submissions today and tomorrow.
@luizirber @gkthiruvathukal I will be open to review this paper.
@luizirber Can you please work on assigning reviewers? Thank you!
@editorialbot commands
Hello @luizirber, here are the things you can ask me to do:
# List all available commands
@editorialbot commands
# Add to this issue's reviewers list
@editorialbot add @username as reviewer
# Remove from this issue's reviewers list
@editorialbot remove @username from reviewers
# Get a list of all editors's GitHub handles
@editorialbot list editors
# Assign a user as the editor of this submission
@editorialbot assign @username as editor
# Remove the editor assigned to this submission
@editorialbot remove editor
# Remind an author, a reviewer or the editor to return to a review after a
# certain period of time (supported units days and weeks)
@editorialbot remind @reviewer in 2 weeks
# Check the references of the paper for missing DOIs
@editorialbot check references
# Perform checks on the repository
@editorialbot check repository
# Adds a checklist for the reviewer using this command
@editorialbot generate my checklist
# Set a value for version
@editorialbot set v1.0.0 as version
# Set a value for branch
@editorialbot set joss-paper as branch
# Set a value for repository
@editorialbot set https://github.com/organization/repo as repository
# Set a value for the archive DOI
@editorialbot set set 10.5281/zenodo.6861996 as archive
# Mention the EiCs for the correct track
@editorialbot ping track-eic
# Generates the pdf paper
@editorialbot generate pdf
# Recommends the submission for acceptance
@editorialbot recommend-accept
# Generates a LaTeX preprint file
@editorialbot generate preprint
# Flag submission with questionable scope
@editorialbot query scope
# Get a link to the complete list of reviewers
@editorialbot list reviewers
# Creates a post-review checklist with editor and authors tasks
@editorialbot create post-review checklist
# Open the review issue
@editorialbot start review
@editorialbot add @abhishektiwari as reviewer
@abhishektiwari added to the reviewers list!
hi @dinacmistry, would you be interested in review this submission?
hi @arashbm, would you be interested in reviewing this submission?
Sounds good. Count me in!
@editorialbot add @arashbm as reviewer
@arashbm added to the reviewers list!
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.5281/zenodo.8009585 is OK
MISSING DOIs
- 10.1145/1852658.1852661 may be a valid DOI for title: Analysing information flows and key mediators through temporal centrality metrics
- 10.1209/0295-5075/81/48002 may be a valid DOI for title: Burstiness and memory in complex systems
- 10.1103/physrevlett.110.198701 may be a valid DOI for title: Betweenness preference: Quantifying correlations in the topological dynamics of temporal networks
- 10.1016/j.future.2019.08.022 may be a valid DOI for title: Raphtory: Streaming analysis of distributed temporal graphs
- 10.1016/j.softx.2022.101301 may be a valid DOI for title: Reticula: A temporal network and hypergraph analysis software package
- 10.1145/3442442.3452052 may be a valid DOI for title: Analysis and visualisation of time series data on networks with pathpy
- 10.1073/pnas.0903215107 may be a valid DOI for title: Stability of graph communities across time scales
- 10.1038/srep00397 may be a valid DOI for title: Universal features of correlated bursty behaviour
- 10.1214/18-aoas1176 may be a valid DOI for title: Tracking network dynamics: A survey using graph distances
- 10.1073/pnas.0800332105 may be a valid DOI for title: A Poissonian explanation for heavy tails in e-mail communication
- 10.1038/s41567-019-0459-y may be a valid DOI for title: From networks to optimal higher-order models of complex systems
- 10.1145/3479591 may be a valid DOI for title: Moving with the Times: Investigating the Alt-Right Network Gab with Temporal Interaction Graphs
- 10.1101/2021.03.26.437187 may be a valid DOI for title: Inferring cell cycle phases from a partially temporal network of protein interactions
INVALID DOIs
- None
@editorialbot check repository
Software report:
github.com/AlDanial/cloc v 1.88 T=0.16 s (1618.9 files/s, 321329.7 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Rust 143 4228 4235 25118
JSON 2 0 0 3808
Python 18 541 251 1708
YAML 22 35 19 1063
Jupyter Notebook 11 0 5302 954
Markdown 7 191 0 513
reStructuredText 22 356 297 337
TOML 11 57 16 317
CSS 2 65 11 276
TeX 1 27 0 245
SVG 5 0 0 230
JavaScript 3 11 4 55
make 2 12 7 29
DOS Batch 1 8 1 26
Dockerfile 1 14 0 26
HTML 3 0 0 23
-------------------------------------------------------------------------------
SUM: 254 5545 10143 34728
-------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Wordcount for paper.md
is 1308
@narnolddd can you please check https://github.com/openjournals/joss-reviews/issues/5633#issuecomment-1727836515 for suggestions for DOIs for the references, and add the corrected ones to https://github.com/Pometry/Raphtory/blob/paper/paper/joss-raphtory.bib ? Thanks!
Sorry for my late reply @luizirber -- of course, I will get on that now! Thanks.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@editorialbot check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1137/19M1242252 is OK
- 10.1145/1852658.1852661 is OK
- 10.1209/0295-5075/81/48002 is OK
- 10.1103/physrevlett.110.198701 is OK
- 10.1016/j.future.2019.08.022 is OK
- 10.1016/j.softx.2022.101301 is OK
- 10.1145/3442442.3452052 is OK
- 10.5281/zenodo.7682609 is OK
- 10.6084/m9.figshare.1164194.v14 is OK
- 10.1103/PhysRevE.85.056115 is OK
- 10.1073/pnas.0903215107 is OK
- 10.1063/1.2711640 is OK
- 10.1145/3159652.3159706 is OK
- 10.1038/srep00397 is OK
- 10.1214/18-aoas1176 is OK
- 10.1073/pnas.0800332105 is OK
- 10.1038/s41567-019-0459-y is OK
- 10.1093/oso/9780198805090.001.0001 is OK
- 10.1007/978-3-642-36461-7 is OK
- 10.1142/q0033 is OK
- 10.1145/3479591 is OK
- 10.1145/3018661.3018731 is OK
- 10.1145/3093742.3093913 is OK
- 10.5281/zenodo.8009585 is OK
- 10.1101/2021.03.26.437187 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@luizirber just to confirm, the DOIs seem to be okay now.
Thanks @narnolddd, we are ready to go!
@editorialbot start review
OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/5940.
Submitting author: !--author-handle-->@narnolddd<!--end-author-handle-- (Naomi Arnold) Repository: https://github.com/Pometry/Raphtory Branch with paper.md (empty if default branch): paper Version: v0.4.2 Editor: !--editor-->@luizirber<!--end-editor-- Reviewers: @abhishektiwari, @arashbm Managing EiC: George K. Thiruvathukal
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @narnolddd. Currently, there isn't a JOSS editor assigned to your paper.
@narnolddd 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: