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
|
% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/rename.R, R/rename_at.R
\name{step_rename}
\alias{step_rename}
\alias{tidy.step_rename}
\alias{tidy.step_rename_at}
\title{Rename variables by name}
\usage{
step_rename(
recipe,
...,
role = "predictor",
trained = FALSE,
inputs = NULL,
skip = FALSE,
id = rand_id("rename")
)
\method{tidy}{step_rename}(x, ...)
\method{tidy}{step_rename_at}(x, ...)
}
\arguments{
\item{recipe}{A recipe object. The step will be added to the
sequence of operations for this recipe.}
\item{...}{One or more unquoted expressions separated by commas. See
\code{\link[dplyr:rename]{dplyr::rename()}} where the convention is \strong{\code{new_name = old_name}}.}
\item{role}{For model terms created by this step, what analysis role should
they be assigned? By default, the function assumes that the new dimension
columns created by 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{inputs}{Quosure(s) of \code{...}.}
\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_rename} 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{values} which contains the \code{rename} expressions as character
strings (and are not reparsable).
}
\description{
\code{step_rename} creates a \emph{specification} of a recipe step that will add
variables using \code{\link[dplyr:rename]{dplyr::rename()}}.
}
\details{
When an object in the user's global environment is referenced in
the expression defining the new variable(s), it is a good idea to use
quasiquotation (e.g. \verb{!!}) to embed the value of the object in the
expression (to be portable between sessions).
}
\examples{
recipe( ~ ., data = iris) \%>\%
step_rename(Sepal_Width = Sepal.Width) \%>\%
prep() \%>\%
bake(new_data = NULL) \%>\%
slice(1:5)
vars <- c(var1 = "cyl", var2 = "am")
car_rec <-
recipe(~ ., data = mtcars) \%>\%
step_rename(!!vars)
car_rec \%>\%
prep() \%>\%
bake(new_data = NULL)
car_rec \%>\%
tidy(number = 1)
}
\concept{preprocessing}
\concept{transformation_methods}
\keyword{datagen}
|
