Closed whedon closed 2 years ago
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks.
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
For a list of things I can do to help you, just type:
@whedon commands
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
@whedon generate pdf
Software report (experimental):
github.com/AlDanial/cloc v 1.88 T=0.08 s (403.3 files/s, 58113.8 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
C/C++ Header 2 3 38 1971
R 23 147 851 550
Markdown 2 118 0 518
Rmd 3 84 171 157
C++ 3 24 31 92
-------------------------------------------------------------------------------
SUM: 33 376 1091 3288
-------------------------------------------------------------------------------
Statistical information for the repository 'c0a408a899254ff930b80c7a' was
gathered on 2021/10/01.
The following historical commit information, by author, was found:
Author Commits Insertions Deletions % of changes
Alexander (Sasha) Pa 7 3599 2 100.00
Below are the number of rows from each author that have survived and are still
intact in the current revision:
Author Rows Stability Age % in comments
Alexander (Sasha) Pa 2159 60.0 0.1 3.29
@whedon generate pdf from branch joss
Attempting PDF compilation from custom branch joss. Reticulating splines etc...
PDF failed to compile for issue #3789 with the following error:
Can't find any papers to compile :-(
@whedon check references from branch joss
Attempting to check references... from custom branch joss
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1167/11.10.12 is OK
- 10.5281/zenodo.5543212 is OK
- 10.1016/j.visres.2007.08.023 is OK
- 10.1364/JOSAA.26.002612 is OK
- 10.18637/jss.v076.i01 is OK
MISSING DOIs
- None
INVALID DOIs
- None
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
@alexander-pastukhov - Your paper should have a section titled "Statement of Need" that explains why this software is needed, and what kinds of problems can be solved using it, in what fields.
Please add this, and then use the command @whedon generate pdf from branch joss
to regenerate the pdf, noting the whedon commands need to be the first thing in a comment.
@whedon generate pdf from branch joss
On Fri, Oct 1, 2021 at 3:55 PM whedon @.***> wrote:
Software report (experimental): github.com/AlDanial/cloc v 1.88 T=0.08 s (403.3 files/s, 58113.8 lines/s)
Language files blank comment code
C/C++ Header 2 3 38 1971 R 23 147 851 550 Markdown 2 118 0 518 Rmd 3 84 171 157 C++ 3 24 31 92
SUM: 33 376 1091 3288
Statistical information for the repository 'c0a408a899254ff930b80c7a' was gathered on 2021/10/01. The following historical commit information, by author, was found:
Author Commits Insertions Deletions % of changes Alexander (Sasha) Pa 7 3599 2 100.00
Below are the number of rows from each author that have survived and are still intact in the current revision:
Author Rows Stability Age % in comments Alexander (Sasha) Pa 2159 60.0 0.1 3.29
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/3789#issuecomment-932250844, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCQDEKBQAMLPR2JDRQG7QDUEW4URANCNFSM5FEYBMLA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
@alexander-pastukhov - you may have to give whedon commands directly on GitHub - I'm not sure that the email interface will work
@whedon generate pdf from branch joss
Attempting PDF compilation from custom branch joss. Reticulating splines etc...
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
👋 @chartgerink - Would you be willing to edit this submission for JOSS?
@whedon invite @chartgerink as editor
@chartgerink has been invited to edit this submission.
Hi @danielskatz - sorry I'm editing three other papers right now and want to complete my first one before adding to that, as a new editor in town :-)
@chartgerink - ok, thanks - @kyleniemeyer will look for another editor. Also, you might want to change your max papers on the JOSS dashboard from 4 to 3 to help AEiCs.
👋 @mikldk could you edit this submission?
@whedon invite @mikldk as editor
@mikldk has been invited to edit this submission.
@mikldk has been invited to edit this submission.
:wave: @mikldk – just checking to see if you think you might be able to edit this paper for us?
Sorry to all. This somehow slipped through my fingers. Yes, I'll edit this.
@whedon assign me as editor
OK, the editor is @mikldk
@alexander-pastukhov - thank you for the submission.
Do you have any suggestions for reviewers (here is a list of potential reviewers)?
@mikldk - based on Programming language + Topic I would suggest: marcjwilliams1, szorowi1, nhtran93, mdogucu, lindemann09.
Should I mention (how many of) them via @?
What you've done is great - now it's the job of the editor to actually invite some of them (or others)
Should I mention (how many of) them via @?
Please do not mention any with '@'. I'll invite some. Thanks for the suggestions.
Thank you! Was just checking whether I am accidentally stalling the process :)
@szorowi1, @mdogucu: Would you be interested in reviewing this submission to The Journal of Open Source Software? Reviews are open and based on a checklist. The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. If you have any questions or concerns please let me know.
I am sorry but I am not available for review.
@marcjwilliams1: Would you be interested in reviewing this submission to The Journal of Open Source Software? Reviews are open and based on a checklist. The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. If you have any questions or concerns please let me know.
Hi all, apologies for the delay. Unfortunately I have several other reviews due at this time so I'll need to decline (package looks very interesting though!)
@nhtran93: Would you be interested in reviewing this submission to The Journal of Open Source Software? Reviews are open and based on a checklist. The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. If you have any questions or concerns please let me know.
Sorry for the slow reply. Not available at this time I'm afraid.
@lindemann09: Would you be interested in reviewing this submission to The Journal of Open Source Software? Reviews are open and based on a checklist. The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. If you have any questions or concerns please let me know.
@alexander-pastukhov Do you have two additional suggestions for reviewers? Please do not tag them with @
.
I woudl suggest: fernandomayer, fartist
@fernandomayer, @fartist: Would you be interested in reviewing this submission to The Journal of Open Source Software? Reviews are open and based on a checklist. The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. If you have any questions or concerns please let me know.
Hi, I can make this review.
I can do it as well, thanks.
On Mon, Nov 8, 2021 at 4:08 PM Fernando Mayer @.***> wrote:
Hi, I can make this review.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/openjournals/joss-reviews/issues/3789#issuecomment-963688417, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADMVHB3QWZR5VDOFUASZE6TULBQ6RANCNFSM5FEYBMLA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
@whedon assign @fernandomayer as reviewer
OK, @fernandomayer is now a reviewer
@whedon add @ fartist as reviewer
OK, @ fartist is now a reviewer
@whedon remove @ fartist as reviewer
Submitting author: @alexander-pastukhov (Alexander Pastukhov) Repository: https://github.com/alexander-pastukhov/bistablehistory Version: v1.0.0 Editor: @mikldk Reviewers: @fernandomayer, @fartist Managing EiC: Daniel S. Katz
:warning: JOSS reduced service mode :warning:
Due to the challenges of the COVID-19 pandemic, JOSS is currently operating in a "reduced service mode". You can read more about what that means in our blog post.
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @alexander-pastukhov. Currently, there isn't an JOSS editor assigned to your paper.
@alexander-pastukhov 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 @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type: