You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I'm writing the party package methods for #30, I thought that it might be helpful to list some other connections to make to other tidymodels packages
Parameter objects
If you have any tuning parameters that need dials objects, we could take a dials dependency and add them here or add a PR to dials. I would only add them to dials if you think that there are other models/packages that would be able to use them. For my PR, I'll keep them in treesnip since they are specific to conditional inference trees.
Tuning related things
There are also two other components that probably need some specification to work better with tune.
First, if there are tuning parameters that can use multi_predict(), you will want to set up an S3 min_grid() method. This basically tells tune how to use the submodes efficiently. tune exports a function called fit_max_value() that makes this pretty easy.
Second, if there are parameters that people will want to tune but are not main arguments, you can better enable that to happen by listing them as tunable parameters with the S3 method tunable. Basically it just lists their argument names and the corresponding dials object that should be used. This is described in details on tidymodels.org.
For example, for the randomForest engine, people might want to tune over maxnodes. tune contains this tibble to set that up:
> tune:::randomForest_engine_args
# A tibble: 1 x 5
name call_info source component component_id
<chr> <list> <chr> <chr> <chr>
1 maxnodes <named list [2]> model_spec rand_forest engine
> tune:::randomForest_engine_args$call_info
[[1]]
[[1]]$pkg
[1] "dials"
[[1]]$fun
[1] "max_nodes"
For both of these tune-related items, they need underlying functions in tune so it would be better to PR into tune for them. I'll set that up in a PR for the party models and link to this issue to help make it easier.
The text was updated successfully, but these errors were encountered:
As I'm writing the
party
package methods for #30, I thought that it might be helpful to list some other connections to make to other tidymodels packagesParameter objects
If you have any tuning parameters that need
dials
objects, we could take adials
dependency and add them here or add a PR todials
. I would only add them todials
if you think that there are other models/packages that would be able to use them. For my PR, I'll keep them intreesnip
since they are specific to conditional inference trees.Tuning related things
There are also two other components that probably need some specification to work better with
tune
.First, if there are tuning parameters that can use
multi_predict()
, you will want to set up an S3min_grid()
method. This basically tellstune
how to use the submodes efficiently.tune
exports a function calledfit_max_value()
that makes this pretty easy.Second, if there are parameters that people will want to tune but are not main arguments, you can better enable that to happen by listing them as tunable parameters with the S3 method
tunable
. Basically it just lists their argument names and the correspondingdials
object that should be used. This is described in details ontidymodels.org
.For example, for the
randomForest
engine, people might want to tune overmaxnodes
.tune
contains this tibble to set that up:For both of these
tune
-related items, they need underlying functions intune
so it would be better to PR intotune
for them. I'll set that up in a PR for theparty
models and link to this issue to help make it easier.The text was updated successfully, but these errors were encountered: