@@ -79,19 +79,19 @@ between implementations.
79
79
80
80
In this example:
81
81
82
- - the ** type** of model is “random forest”,
83
- - the ** mode** of the model is “regression” (as opposed to
82
+ - the ** type** of model is “random forest”,
83
+ - the ** mode** of the model is “regression” (as opposed to
84
84
classification, etc), and
85
- - the computational ** engine** is the name of the R package.
85
+ - the computational ** engine** is the name of the R package.
86
86
87
87
The goals of parsnip are to:
88
88
89
- - Separate the definition of a model from its evaluation.
90
- - Decouple the model specification from the implementation (whether
89
+ - Separate the definition of a model from its evaluation.
90
+ - Decouple the model specification from the implementation (whether
91
91
the implementation is in R, spark, or something else). For example,
92
92
the user would call ` rand_forest ` instead of ` ranger::ranger ` or
93
93
other specific packages.
94
- - Harmonize argument names (e.g. ` n.trees ` , ` ntrees ` , ` trees ` ) so that
94
+ - Harmonize argument names (e.g. ` n.trees ` , ` ntrees ` , ` trees ` ) so that
95
95
users only need to remember a single name. This will help * across*
96
96
model types too so that ` trees ` will be the same argument across
97
97
random forest as well as boosting or bagging.
@@ -142,7 +142,7 @@ rand_forest(mtry = 10, trees = 2000) %>%
142
142
fit(mpg ~ . , data = mtcars )
143
143
# > parsnip model object
144
144
# >
145
- # > Fit time: 71ms
145
+ # > Fit time: 73ms
146
146
# > Ranger result
147
147
# >
148
148
# > Call:
@@ -172,18 +172,18 @@ This project is released with a [Contributor Code of
172
172
Conduct] ( https://contributor-covenant.org/version/2/0/CODE_OF_CONDUCT.html ) .
173
173
By contributing to this project, you agree to abide by its terms.
174
174
175
- - For questions and discussions about tidymodels packages, modeling,
175
+ - For questions and discussions about tidymodels packages, modeling,
176
176
and machine learning, please [ post on RStudio
177
177
Community] ( https://community.rstudio.com/new-topic?category_id=15&tags=tidymodels,question ) .
178
178
179
- - If you think you have encountered a bug, please [ submit an
179
+ - If you think you have encountered a bug, please [ submit an
180
180
issue] ( https://github.com/tidymodels/parsnip/issues ) .
181
181
182
- - Either way, learn how to create and share a
182
+ - Either way, learn how to create and share a
183
183
[ reprex] ( https://reprex.tidyverse.org/articles/articles/learn-reprex.html )
184
184
(a minimal, reproducible example), to clearly communicate about your
185
185
code.
186
186
187
- - Check out further details on [ contributing guidelines for tidymodels
187
+ - Check out further details on [ contributing guidelines for tidymodels
188
188
packages] ( https://www.tidymodels.org/contribute/ ) and [ how to get
189
189
help] ( https://www.tidymodels.org/help/ ) .
0 commit comments