New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PRE REVIEW]: PMLB v1.0: an open source dataset collection for benchmarking machine learning methods #2756
Comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks. 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:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
|
👋 @trang1618 - I'm the Associate Editor-in-Chief on duty for JOSS this week, and I'm trying to understand if this submission is in scope for JOSS, and I suspect it is not. Can you explain why why you think it is? It seems to mostly be data, not software, though there is a small amount of software to access and view the data. |
@whedon query scope |
Submission flagged for editorial review. |
Hi @danielskatz, thank you for taking a look. Here’s a bit of background. The initial PMLB publication from 2017 introduced the data:
In this manuscript submission to JOSS, we focus on the recent additions to the open source software around PMLB. This includes the python package, R library, continuous integration infrastructure to facilitate the contribution workflow, and website to summarize each dataset. We envision future PMLB users will largely interact with the data through the software clients and website, and this manuscript describes these pieces of software. Reading through the Scope & submission requirements, I see our manuscript fitting under “support[ing] the execution of research experiments” and “extract[ing] knowledge from large data sets”. Given this additional context, does that change your calculation on whether our manuscript is appropriate for JOSS? Thanks again for the consideration. |
Thanks @trang1618 - The editors will now look at this, including your statements above and make a decision. We should be able to let you know around the middle of next week. |
@trang1618 Unfortunately, the JOSS editors have decided that this submission does not meet the substantial scholarly effort criterion for review by JOSS, due to the close connection with the prior publication. Please see https://joss.readthedocs.io/en/latest/submitting.html#other-venues-for-reviewing-and-publishing-software-packages for other suggestions for how you might receive credit for your work. |
@whedon reject |
Paper rejected. |
@kyleniemeyer Thanks for taking a look! |
Submitting author: @trang1618 (Trang Le)
Repository: https://github.com/EpistasisLab/pmlb
Version: v1.0.2
Editor: Pending
Reviewer: Pending
Managing EiC: Daniel S. Katz
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 @trang1618. Currently, there isn't an JOSS editor assigned to your paper.
@trang1618 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:
The text was updated successfully, but these errors were encountered: