-
-
Notifications
You must be signed in to change notification settings - Fork 403
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
Feature selection - parameter naming conflict #1066
Comments
The problem is that in an internal function |
@jakobbossek |
Added test in b8c46bc. Closing. |
Sorry for the dumb question, but what can I do if I want to apply this patch to my own analysis? I am currently using version 2.9. |
You can install the development version of mlr with
|
Will this be incorporated into version 2.10? If so, how soon do you expect that to be released? Thanks again! |
Yes and we expect a release very soon. |
monday my holiday starts. i want to push to CRAN before this. they should hopefully allow a 2nd release in 10 days. |
What would be included in the 2nd release? |
We are still working on this. |
simply read the NEWS in the GH repo. you can see what we are changing there. |
Sorry to keep this thread going, but do you know how soon version 2.10 will be live on CRAN? It is still showing as 2.9. Thanks! |
I really enjoy working with mlr, but I've run into a little problem, and I'm not sure how to get around it. I'm hoping you can help. I'm trying to do feature selection with the rf.min.depth function. I want to specify a value for the "method" parameter within the underlying library ( randomForestSRC::var.select). But there is also a "method" parameter in the generateFilterValuesData function for the learner name. Below is some example code along with the error I'm getting. I'm running R-3.3.1 and mlr version 2.9.
Error in randomForestSRC::var.select(getTaskFormula(task), getTaskData(task), :
formal argument "method" matched by multiple actual arguments
Any suggestions?
The text was updated successfully, but these errors were encountered: