Closed editorialbot closed 5 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
Software report:
github.com/AlDanial/cloc v 1.88 T=0.17 s (704.4 files/s, 138703.3 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Python 71 2479 3313 10703
SQL 1 189 0 2016
Qt 3 0 0 1558
XML 15 0 0 1159
Markdown 13 289 0 987
YAML 13 80 180 675
TeX 1 10 0 96
TOML 1 6 1 70
C 1 40 54 61
DOS Batch 1 8 1 26
make 1 4 7 9
SVG 1 0 0 1
-------------------------------------------------------------------------------
SUM: 122 3105 3556 17361
-------------------------------------------------------------------------------
gitinspector failed to run statistical information for the repository
Wordcount for paper.md
is 1331
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.5880/GFZ.2.4.2020.003 is OK
- 10.5281/zenodo.10054611 is OK
- 10.1785/gssrl.81.3.530 is OK
- 10.3390/s23063315 is OK
- 10.5194/se-13-301-2022 is OK
MISSING DOIs
- 10.5194/se-11-627-2020 may be a valid DOI for title: Influence of reservoir geology on seismic response during decameter-scale hydraulic stimulations in crystalline rock
INVALID DOIs
- https://doi.org/10.1016/j.ascom.2015.06.004 is INVALID because of 'https://doi.org/' prefix
- 10.5281/zenodo.10598393 is INVALID
- 10.3929/ethz-b-000651477 is INVALID
: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:
SeismicMesh: Triangular meshing for seismology
Submitting author: @krober10nd
Handling editor: @meg-simula (Retired)
Reviewers: @nschloe, @jorgensd
Similarity score: 0.8239
UWGeodynamics: A teaching and research tool for numerical geodynamic modelling
Submitting author: @rbeucher
Handling editor: @lheagy (Retired)
Reviewers: @flohorovicic
Similarity score: 0.8203
Telewavesim: Python software for teleseismic body wave modeling
Submitting author: @paudetseis
Handling editor: @kbarnhart (Retired)
Reviewers: @andreww, @seisman, @brmather
Similarity score: 0.8202
pySYD: Automated measurements of global asteroseismic parameters
Submitting author: @ashleychontos
Handling editor: @mbobra (Active)
Reviewers: @danhey, @benjaminpope
Similarity score: 0.8189
DearEIS - A GUI program for analyzing impedance spectra
Submitting author: @vyrjana
Handling editor: @jgostick (Active)
Reviewers: @Aslan-Kosakian, @mdmurbach
Similarity score: 0.8187
⚠️ 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.
Hi @mrosskopf and thanks for your submission! We have a backlog of submissions so I will add this to our waitlist. In the meantime, please suggest 5 reviewers from the database listed above or your own (non-conflicted) extended network. Their github handles are most useful to receive but please don't use "@" to reference them since it will prematurely ping them. Also please address the DOI notes above. Thanks for your patience.
@editorialbot generate pdf
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
Hi @kthyng thank you for adding me to the waitlist. I addressed the DOI notes and hope all works now. My suggestions for reviewers are: ThomasLecocq, leonard-seydoux, fwalter, calum-chamberlain, seisman
Thank you again!
Hi @mrosskopf! Another note — it would be great to add a readme to your repo to have something of a landing page for any potential users. I see you have info in your docs but it feels a bit empty without some info in the readme itself too.
Also still looking for an editor for you.
Hi @kthyng, thank you for the note. I updated the readme in the repo.
@crvernon Are you up for editing another submission?
@editorialbot invite @crvernon as editor
Invitation to edit this submission sent!
@editorialbot assign me as editor
Assigned! @crvernon is now the editor
:wave: @mrosskopf - I'll be your editor on this one. Once I get at least two reviews signed up I'll move this to full review status. Thanks!
👋 @ThomasLecocq - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
👋 @leonard-seydoux - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
👋 @calum-chamberlain - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
👋 @ThomasLecocq - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
Yes
Thanks @ThomasLecocq !
@editorialbot add @ThomasLecocq as reviewer
@ThomasLecocq added to the reviewers list!
👋 @calum-chamberlain - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
Sorry, but I am flat out with teaching at the moment and won't be able to provide a timely review.
👋 @fwalter - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
:wave: @rowanc1 - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
👋 @kwinkunks - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
👋 @nialov - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
Hello Chris,
I cannot see the paper I am supposed to review.
Fabian.
Von: Chris Vernon @.> Gesendet: Freitag, 26. April 2024 14:16 An: openjournals/joss-reviews @.> Cc: Fabian Walter @.>; Mention @.> Betreff: Re: [openjournals/joss-reviews] [PRE REVIEW]: DUGseis: A Python Package for Real-Time and Post-Processing of Picoseismicity (Issue #6349)
👋 @nialovhttps://github.com/nialov - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
— Reply to this email directly, view it on GitHubhttps://github.com/openjournals/joss-reviews/issues/6349#issuecomment-2079272977, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADC2IN37HJJ2KCBBHHLKRJTY7JASXAVCNFSM6AAAAABDGXKMHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZZGI3TEOJXG4. You are receiving this because you were mentioned.Message ID: @.***>
@editorialbot generate pdf
Hello @fwalter the command above will compile the paper in a following comment. We are in pre-review status now, which is where we ensure we have at least two reviewers to kick off the full review which is where the checklist is present and the full review takes place.
Are you able to review this submission? If so, I'll assign you and we can kick this off to full review.
Thanks!
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
👋 @SaumikDana - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
I will have to decline, sorry for the late response. Several of the authors are part of an ongoing research collaboration and one may appear on a paper with me soon. I am not comfortable with this review.
Fabian.
Von: Chris Vernon @.> Datum: Freitag, 3. Mai 2024 um 13:53 An: openjournals/joss-reviews @.> Cc: Fabian Walter @.>, Mention @.> Betreff: Re: [openjournals/joss-reviews] [PRE REVIEW]: DUGseis: A Python Package for Real-Time and Post-Processing of Picoseismicity (Issue #6349)
👋 @SaumikDanahttps://github.com/SaumikDana - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
— Reply to this email directly, view it on GitHubhttps://github.com/openjournals/joss-reviews/issues/6349#issuecomment-2092849700, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADC2IN4ECFKCIZPCA4ZC5P3ZAN3C3AVCNFSM6AAAAABDGXKMHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJSHA2DSNZQGA. You are receiving this because you were mentioned.Message ID: @.***>
Sorry, I am too busy with prior reviews for a month or two. I can not take this one on my plate :(. So it is a no from me for the review.
No problem @nialov thanks for the notice!
👋 @AnantHariharan1996 - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
😅 @mrosskopf - I am working on getting you another reviewer, once I do we can get this kicked over to full review!
Hang in there @ThomasLecocq, we will get you something to review ASAP!
👋 @megies - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
👋 @trichter - Would you be willing to review this submission to JOSS? We carry out our checklist-driven reviews here in GitHub issues and follow these guidelines: https://joss.readthedocs.io/en/latest/review_criteria.html
@crvernon Apologies for the delay in response. Thanks for the review offer, but I have a few other items to review currently and so I will have to decline this for now. Best wishes.
@crvernon I'm sorry, I won't be able to review
:wave: @mrosskopf - having a crazy tough time finding you reviewers on this one. Any help would be appreciated.
In this case, I am going to go ahead and start the review with @ThomasLecocq confirmed so things can get moving. I'll find you another reviewer in parallel.
Thank you!
@editorialbot start review
OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/6768.
Submitting author: !--author-handle-->@mrosskopf<!--end-author-handle-- (Martina Rosskopf) Repository: https://github.com/swiss-seismological-service/DUGseis Branch with paper.md (empty if default branch): Version: v0.3 Editor: !--editor-->@crvernon<!--end-editor-- Reviewers: !--reviewers-list-->@ThomasLecocq<!--end-reviewers-list-- Managing EiC: Kristen Thyng
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @mrosskopf. Currently, there isn't a JOSS editor assigned to your paper.
@mrosskopf 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: