-
Notifications
You must be signed in to change notification settings - Fork 90
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
Document mapping of arguments between parsnip and underlying engine #238
Comments
I noticed that the
|
I just realized that @DavisVaughan in #235 describes almost exactly the same issue, even down to the same column names I used above. I still think it would be beneficial if this was better documented than using |
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
First of all, thank you all so much for the effort put into parsnip. It's a really great package!
As a first-time user, I found it difficult to track down what the original engine arguments were mapped to in parsnip. I knew very well what the parameter
colsample_bytree
of native xgboost meant for tuning, but I had to dig into the source code to found that it was translated intomtry
in parsnip. This involved some trial-and-error on my side to translate some of my current models.I think it would be beneficial if the mapping between original and standardized arguments was documented either (i) in the function itself or (ii) in a complete reference table, e.g.:
I am not sure how one would go about implementing this. I have thrown together a very hacky solution to list the translation of all current arguments below.
Expand code
Full mapping table
Mapping table by model
$boost_tree
$decision_tree
$linear_reg
$logistic_reg
$mars
$mlp
$multinom_reg
$nearest_neighbor
$rand_forest
$surv_reg
$svm_poly
$svm_rbf
The text was updated successfully, but these errors were encountered: