-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Paper #399
base: main
Are you sure you want to change the base?
Paper #399
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sebffischer I finished a first re-writing and text improvement
paper/paper.md
Outdated
At its core, the `mlr3extralearners` package provides a standardized interface for machine learning and connects many R packages implementing machine learning algorithms into a unified framework. | ||
The package currently wraps **85 different learning algorithms** from many different R packages, for tasks such as classification, regression, and survival analysis. | ||
This enables users to seamlessly access and utilize these learners directly within their workflows. | ||
It also facilitates large-scale empirical benchmark experiments, leveraging the `mlr3` framework's parallelization and optimization capabilities [@benchlargescale]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we mention large-scale benchmarks in the abstract, we should add a sentence about tuning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We mention it in two other spots but I added it also here with a citation, thanks!
|
||
The core functionality of `mlr3extralearners` is to integrate new learners into the `mlr3` ecosystem, allowing users to access a wide array of learning algorithms through a unified syntax and standardized interface. | ||
However, the advantages of `mlr3extralearners` go well beyond simple integration. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't we add a few codes examples like list_mlr3learners() to show all availble learners? Or show the unified interface with lrn("classif.gbm")
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have the link to the website with all learners, this covers the first. The second we could, let's see what Bernd also thinks when he reads it.
.github/workflows/draft-pdf.yml
file which renders the paper inpdf
(see example github action output), we should remove upon merging