1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/poly.R
\name{step_poly}
\alias{step_poly}
\alias{tidy.step_poly}
\title{Orthogonal Polynomial Basis Functions}
\usage{
step_poly(
recipe,
...,
role = "predictor",
trained = FALSE,
objects = NULL,
degree = 2,
options = list(),
skip = FALSE,
id = rand_id("poly")
)
\method{tidy}{step_poly}(x, ...)
}
\arguments{
\item{recipe}{A recipe object. The step will be added to the
sequence of operations for this recipe.}
\item{...}{One or more selector functions to choose which
variables are affected by the step. See \code{\link[=selections]{selections()}}
for more details. For the \code{tidy} method, these are not
currently used.}
\item{role}{For model terms created by this step, what analysis
role should they be assigned?. By default, the function assumes
that the new columns created from the original variables will be
used as predictors in a model.}
\item{trained}{A logical to indicate if the quantities for
preprocessing have been estimated.}
\item{objects}{A list of \code{\link[stats:poly]{stats::poly()}} objects
created once the step has been trained.}
\item{degree}{The polynomial degree (an integer).}
\item{options}{A list of options for \code{\link[stats:poly]{stats::poly()}}
which should not include \code{x}, \code{degree}, or \code{simple}. Note that
the option \code{raw = TRUE} will produce the regular polynomial
values (not orthogonalized).}
\item{skip}{A logical. Should the step be skipped when the
recipe is baked by \code{\link[=bake.recipe]{bake.recipe()}}? While all operations are baked
when \code{\link[=prep.recipe]{prep.recipe()}} is run, some operations may not be able to be
conducted on new data (e.g. processing the outcome variable(s)).
Care should be taken when using \code{skip = TRUE} as it may affect
the computations for subsequent operations}
\item{id}{A character string that is unique to this step to identify it.}
\item{x}{A \code{step_poly} object.}
}
\value{
An updated version of \code{recipe} with the new step
added to the sequence of existing steps (if any). For the
\code{tidy} method, a tibble with columns \code{terms} (the
columns that will be affected) and \code{degree}.
}
\description{
\code{step_poly} creates a \emph{specification} of a recipe
step that will create new columns that are basis expansions of
variables using orthogonal polynomials.
}
\details{
\code{step_poly} can new features from a single
variable that enable fitting routines to model this variable in
a nonlinear manner. The extent of the possible nonlinearity is
determined by the \code{degree} argument of
\code{\link[stats:poly]{stats::poly()}}. The original variables are removed
from the data and new columns are added. The naming convention
for the new variables is \code{varname_poly_1} and so on.
}
\examples{
library(modeldata)
data(biomass)
biomass_tr <- biomass[biomass$dataset == "Training",]
biomass_te <- biomass[biomass$dataset == "Testing",]
rec <- recipe(HHV ~ carbon + hydrogen + oxygen + nitrogen + sulfur,
data = biomass_tr)
quadratic <- rec \%>\%
step_poly(carbon, hydrogen)
quadratic <- prep(quadratic, training = biomass_tr)
expanded <- bake(quadratic, biomass_te)
expanded
tidy(quadratic, number = 1)
}
\seealso{
\code{\link[=step_ns]{step_ns()}} \code{\link[=recipe]{recipe()}}
\code{\link[=prep.recipe]{prep.recipe()}} \code{\link[=bake.recipe]{bake.recipe()}}
}
\concept{basis_expansion}
\concept{preprocessing}
\keyword{datagen}
|
