-
Notifications
You must be signed in to change notification settings - Fork 0
Prelim work #3
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
Prelim work #3
Conversation
Could we please have a example, including the use of TunedModel, in the readme - or in Documeter.jl docs if you prefer? |
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.
Great progress, thank you 🙏🏾
@OkonSamuel I didn't review the |
Co-authored-by: Anthony Blaom, PhD <anthony.blaom@gmail.com>
Co-authored-by: Anthony Blaom, PhD <anthony.blaom@gmail.com>
recursive feature elimination should return the first columns as important features. | ||
```julia | ||
using MLJ # or, minimally, `using FeatureSelection, MLJModels, MLJBase` | ||
using MLJ, FeatureSelection |
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.
I am proposing that FeatureSelection be a dep of MLJ with all names re-exported. So you won't need FeatureSelection
here, right?
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.
Yeah
println(io, "$(name)=$(value)") | ||
end | ||
end | ||
event_name = "${{ github.event_name }}" |
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.
maybe we can just dump all the documenter.jl stuff since we are not using it. in any case, i don't think we need all that complicated logic for this package.
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.
Happy with the latest changes, thank you 🙏
Co-authored-by: Anthony Blaom, PhD <anthony.blaom@gmail.com>
This PR starts the process of implementation of Feature Selection models for use with the MLJ package. For now the following models are implemented.
RecursiveFeatureElimination
FeatureSelector
In the future, more models will be added based on user requests.