Closed whedon closed 4 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
Failed to discover a Statement of need
section in paper
Software report (experimental):
github.com/AlDanial/cloc v 1.84 T=0.29 s (91.6 files/s, 14760.9 lines/s)
--------------------------------------------------------------------------------
Language files blank comment code
--------------------------------------------------------------------------------
Python 13 568 957 1314
reStructuredText 5 159 79 346
Markdown 2 27 0 176
TeX 1 9 0 167
YAML 4 15 8 83
Bourne Again Shell 1 5 3 14
Jupyter Notebook 1 0 406 14
--------------------------------------------------------------------------------
SUM: 27 783 1453 2114
--------------------------------------------------------------------------------
Statistical information for the repository '2532' was gathered on 2020/07/28.
The following historical commit information, by author, was found:
Author Commits Insertions Deletions % of changes
Brendan Boyd 4 25 17 0.05
Brendan Isaac Seaton 9 32 37 0.08
biboyd 68 11753 14264 32.02
boydbre1 301 29635 25484 67.84
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
biboyd 2722 23.2 0.7 13.96
boydbre1 117 0.4 1.8 21.37
Reference check summary:
OK DOIs
- 10.1146/annurev-astro-091916-055240 is OK
- 10.3847/1538-4357/aa7d04 is OK
- 10.3847/1538-4357/aa7e2d is OK
- 10.3847/1538-4357/aadd03 is OK
- 10.3847/1538-4357/aa87b4 is OK
- 10.1088/0004-637X/731/1/6 is OK
- 10.1088/0004-637X/791/1/64 is OK
- 10.3847/1538-4357/ab0654 is OK
MISSING DOIs
- None
INVALID DOIs
- None
@whedon query scope
Submission flagged for editorial review.
@xuanxu - would you be able to edit this submission?
@whedon invite @xuanxu as editor
@xuanxu has been invited to edit this submission.
@danielskatz I can't take it, I don't have bandwidth right now.
@whedon assign me as editor
OK, the editor is @danielskatz
👋 @biboyd - please add an explicit section title Statement of Need to the paper - see https://joss.readthedocs.io/en/latest/submitting.html#what-should-my-paper-contain
Once you have done this, please enter @whedon generate pdf
as a new command here to regenerate the pdf.
Also, please suggest potential reviewers by mentioning them here in this thread (without tagging them with an @). 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), or you may know of others in this field. I will also check for reviewers through some other channels.
👋 @chummels & @brittonsmith - would one of you be willing to review this submission to JOSS? I am aware you are acknowledged in the paper, but I also think this is likely not a COI. Let me know what you think.
If you're not familiar with JOSS's review style/guidelines, we are basically checklist driven and use GitHub, where reviewers, editors, and authors work openly and iteratively to ideally improve submissions to the point where they can be accepted. See https://joss.readthedocs.io/en/latest/reviewer_guidelines.html
@whedon generate pdf
A couple of names on the list that could be good reviewers might be eteq or olebole
@biboyd - I also notice that a number of your references seem to be missing journals - which in our style, makes them incomplete. Please add the journals or conferences for all references.
👋 @chummels & @brittonsmith - just checking with you again, and hoping that one of you will be willing to do this.
👋 @chummels & @brittonsmith - would one of you be willing to review this submission to JOSS? I am aware you are acknowledged in the paper, but I also think this is likely not a COI. Let me know what you think.
If you're not familiar with JOSS's review style/guidelines, we are basically checklist driven and use GitHub, where reviewers, editors, and authors work openly and iteratively to ideally improve submissions to the point where they can be accepted. See https://joss.readthedocs.io/en/latest/reviewer_guidelines.html
👋 @eteq & @olebole - would one of you be willing to review this JOSS submission?
@danielskatz, sorry for the delay in getting back to you. I work quite closely with the authors and attend regular meetings with them. I'm not sure if that is too close, but I am really drowning this summer. I just can't spare the time. My apologies. I can think of a couple people who would do an excellent job at this: neutrinoceros and cphyc. I hope they can help.
👋 @neutrinoceros and @cphyc - would one of you be willing to review this submission to JOSS? If you're not familiar with JOSS's review style/guidelines, we are basically checklist driven and use GitHub, where reviewers, editors, and authors work openly and iteratively to ideally improve submissions to the point where they can be accepted. See https://joss.readthedocs.io/en/latest/reviewer_guidelines.html
@danielskatz, I would be willing to review this submission but won't be able to do so until the beginning of September.
Thanks @cphyc - let's see if we can find 2 reviewers before then, but if not, I will take you up on your offer.
@danielskatz I don't think I'll have time for this in the foreseeable future unfortunately, but feel free to ping me again in a month if you're still looking, things might change !
I could do it next week. Would that be ok? (Would be my first review...)
thanks @olebole - I'll add you as a reviewer, but we won't start the review until I also find a second reviewer.
@whedon assign @olebole as reviewer
OK, @olebole is now a reviewer
👋 @namurphy - would you be willing to review this submission to JOSS? You were suggested by a colleague at CfA.
If you're not familiar with JOSS's review style/guidelines, we are basically checklist driven and use GitHub, where reviewers, editors, and authors work openly and iteratively to ideally improve submissions to the point where they can be accepted. See https://joss.readthedocs.io/en/latest/reviewer_guidelines.html
👍 @marcocamma - would you be willing to review this JOSS submission?
@biboyd - sorry this is taking longer than expected to find a second reviewer - I'm still working on it
👋 @namurphy & @marcocamma - I'm just checking with you again to see if one of you would be able to review this submission
👋 @cwchurchill-DrQSO, @gkacprzak, MTMurphy77 - would one of you be willing to review this submission to JOSS? You were suggested by a colleague at CfA.
If you're not familiar with JOSS's review style/guidelines, we are basically checklist driven and use GitHub, where reviewers, editors, and authors work openly and iteratively to ideally improve submissions to the point where they can be accepted. See https://joss.readthedocs.io/en/latest/reviewer_guidelines.html
👋 @zpace - would you be willing to review this JOSS submission?
HI Daniel,
I am sorry, I just don't have the time. With full lockdown in Australia, no daycare, and two full time jobs are making it impossible to do this at this time. Sorry about that.
Thank you, Glenn
A/Prof. Glenn G. Kacprzak
From: Daniel S. Katz notifications@github.com Sent: Monday, 17 August 2020 10:51 PM To: openjournals/joss-reviews joss-reviews@noreply.github.com Cc: Glenn Kacprzak gkacprzak@hotmail.com; Mention mention@noreply.github.com Subject: Re: [openjournals/joss-reviews] [PRE REVIEW]: SALSA: A Python Package for Constructing Synthetic Quasar Absorption Line Catalogs from Astrophysical Hydrodynamic Simulations (#2532)
👋 @zpacehttps://github.com/zpace - would you be willing to review this JOSS submission?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/openjournals/joss-reviews/issues/2532#issuecomment-674862412, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADMACV6TYDTBFWOVNZKFFJDSBERV7ANCNFSM4PKUECEQ.
Yes, I think I can commit to this.
Thanks @zpace - I'll add you, and we'll start in a new review issue
@whedon add @zpace as reviewer
OK, @zpace is now a reviewer
@whedon start review
OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/2581.
Submitting author: @biboyd (Brendan Boyd) Repository: https://github.com/biboyd/SALSA Version: v0.1.0 Editor: @danielskatz Reviewers: @olebole, @zpace Managing EiC: Kristen Thyng
: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.
Author instructions
Thanks for submitting your paper to JOSS @biboyd. Currently, there isn't an JOSS editor assigned to your paper.
The author's suggestion for the handling editor is @harpolea.
@biboyd 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: