Closed whedon closed 3 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.46 s (115.7 files/s, 14504.2 lines/s)
-------------------------------------------------------------------------------
Language files blank comment code
-------------------------------------------------------------------------------
Python 18 842 1620 2230
Markdown 7 129 0 523
reStructuredText 10 104 86 209
make 2 38 12 175
YAML 7 22 15 157
SVG 2 0 0 132
TeX 1 8 0 88
Bourne Shell 2 16 19 62
JavaScript 1 3 10 50
JSON 1 0 0 46
TOML 1 3 2 27
CSS 1 3 0 13
-------------------------------------------------------------------------------
SUM: 53 1168 1764 3712
-------------------------------------------------------------------------------
Statistical information for the repository 'c09b3f1657be4e558429b66b' was
gathered on 2021/02/06.
The following historical commit information, by author, was found:
Author Commits Insertions Deletions % of changes
Adam Richie-Halford 54 5860 1110 99.93
Ariel Rokem 2 5 0 0.07
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
Adam Richie-Halford 4751 81.1 0.6 8.84
Ariel Rokem 4 80.0 1.6 25.00
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.5281/zenodo.1283339 is OK
- 10.1101/2019.12.19.882928 is OK
- 10.5281/zenodo.4014775 is OK
MISSING DOIs
- 10.1007/978-3-642-15883-4_27 may be a valid DOI for title: Solving structured sparsity regularization with proximal methods
INVALID DOIs
- None
:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:
At-mentioning co-authors here: @arokem, @mnarayan, @nrs02004, @jyeatman
Here is a non-exhaustive list of potential reviewers from the JOSS reviewers google sheet (coauthors, please feel free to add more in this thread):
@whedon check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.5281/zenodo.1283339 is OK
- 10.1101/2019.12.19.882928 is OK
- 10.5281/zenodo.4014775 is OK
MISSING DOIs
- 10.1007/978-3-642-15883-4_27 may be a valid DOI for title: Solving structured sparsity regularization with proximal methods
INVALID DOIs
- https://doi.org/10.1007/978-3-642-15883-4_27 is INVALID because of 'https://doi.org/' prefix
Thanks @richford. Looks like there may still be some DOI issues to work out.
We will use this pre-review issue to find an editor and reviewers.
@whedon check references
Reference check summary (note 'MISSING' DOIs are suggestions that need verification):
OK DOIs
- 10.1007/978-3-642-15883-4_27 is OK
- 10.5281/zenodo.1283339 is OK
- 10.1101/2019.12.19.882928 is OK
- 10.5281/zenodo.4014775 is OK
MISSING DOIs
- 10.1007/978-3-642-15883-4_27 may be a valid DOI for title: Solving structured sparsity regularization with proximal methods
INVALID DOIs
- None
Hi @galessiorob, could you edit this submission? There are some reviewer suggestions above 👆
@whedon invite @galessiorob as editor
@galessiorob has been invited to edit this submission.
@whedon assign me as editor
OK, the editor is @galessiorob
Hi @richford
Thanks for posting your suggested reviewers, I'll email them and add them as reviewers when they accept. In the meantime feel free to resolve the missing DOI.
Hi @galessiorob, thanks! I'm a bit confused about the missing DOI. The single missing DOI is also listed in the "OK DOIs" list.
@whedon check references
@richford you're right 🤔
@danielskatz do you think this can be a whedon bug?
I wouldn't call this a bug.
In the .bib file, I see
@inproceedings{mosci2010solving, title = {Solving structured sparsity regularization with proximal methods}, author = {Mosci, Sofia and Rosasco, Lorenzo and Santoro, Matteo and Verri, Alessandro and Villa, Silvia}, booktitle = {Joint European conference on machine learning and knowledge discovery in databases}, pages = {418--433}, year = {2010}, organization = {Springer} }
@inproceedings{mosci2010solving, author = {Mosci, Sofia and Rosasco, Lorenzo and Santoro, Matteo and Verri, Alessandro and Villa, Silvia}, editor = {Balc{\'a}zar, Jos{\'e} Luis and Bonchi, Francesco and Gionis, Aristides and Sebag, Mich{`e}le}, title = {{Solving Structured Sparsity Regularization with Proximal Methods}}, booktitle = {{Machine Learning and Knowledge Discovery in Databases}}, year = {2010}, publisher = {Springer Berlin Heidelberg}, address = {Berlin, Heidelberg}, pages = {418--433}, isbn = {978-3-642-15883-4}, doi = {10.1007/978-3-642-15883-4_27} }
Both of these entries have the same title. whedon saw the title of the first one, which doesn't have a DOI listed, looked it up, and found the DOI for the second one, which has the same title and appears to be the same work, or perhaps a different version of the same work (same title, same authors, same year). And they have the same bibtex key. Which one is correct and is intended to be cited in the paper? The other should probably be deleted from the .bib file.
Thanks @danielskatz! 🤦🏻 @arokem fixed this in richford/groupyr#38
@whedon assign @rougier as reviewer
OK, @rougier is now a reviewer
@whedon assign @janfreyberg as reviewer
OK, @janfreyberg is now a reviewer
@whedon add @JonathanReardon as reviewer
OK, @JonathanReardon is now a reviewer
@whedon add @rougier as reviewer
OK, @rougier is now a reviewer
🎉 Thanks for volunteering to be reviewers @rougier @JonathanReardon and @janfreyberg!
I'll generate a "review issue" that will contain individual checklists to go through, feel free to get started at your earliest convenience, don't hesitate to ask if you need clarification or help - you can @mention me directly on the issue.
@whedon start review
OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/3024.
Submitting author: @richford (Adam Richie-Halford) Repository: https://github.com/richford/groupyr Version: v0.2.0 Editor: @galessiorob Reviewers: @janfreyberg, @JonathanReardon, @rougier Managing EiC: Kyle Niemeyer
: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 @richford. Currently, there isn't an JOSS editor assigned to your paper.
@richford 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: