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
106
107
108
109
110
111
112
113
|
% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/log.R
\name{step_log}
\alias{step_log}
\alias{tidy.step_log}
\title{Logarithmic Transformation}
\usage{
step_log(
recipe,
...,
role = NA,
trained = FALSE,
base = exp(1),
offset = 0,
columns = NULL,
skip = FALSE,
signed = FALSE,
id = rand_id("log")
)
\method{tidy}{step_log}(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}{Not used by this step since no new variables are
created.}
\item{trained}{A logical to indicate if the quantities for
preprocessing have been estimated.}
\item{base}{A numeric value for the base.}
\item{offset}{An optional value to add to the data prior to
logging (to avoid \code{log(0)}).}
\item{columns}{A character string of variable names that will
be populated (eventually) by the \code{terms} argument.}
\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{signed}{A logical indicating whether to take the signed log.
This is sign(x) * abs(x) when abs(x) => 1 or 0 if abs(x) < 1.
If \code{TRUE} the \code{offset} argument will be ignored.}
\item{id}{A character string that is unique to this step to identify it.}
\item{x}{A \code{step_log} 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{base}.
}
\description{
\code{step_log} creates a \emph{specification} of a recipe step
that will log transform data.
}
\examples{
set.seed(313)
examples <- matrix(exp(rnorm(40)), ncol = 2)
examples <- as.data.frame(examples)
rec <- recipe(~ V1 + V2, data = examples)
log_trans <- rec \%>\%
step_log(all_predictors())
log_obj <- prep(log_trans, training = examples)
transformed_te <- bake(log_obj, examples)
plot(examples$V1, transformed_te$V1)
tidy(log_trans, number = 1)
tidy(log_obj, number = 1)
# using the signed argument with negative values
examples2 <- matrix(rnorm(40, sd = 5), ncol = 2)
examples2 <- as.data.frame(examples2)
recipe(~ V1 + V2, data = examples2) \%>\%
step_log(all_predictors()) \%>\%
prep(training = examples2) \%>\%
bake(examples2)
recipe(~ V1 + V2, data = examples2) \%>\%
step_log(all_predictors(), signed = TRUE) \%>\%
prep(training = examples2) \%>\%
bake(examples2)
}
\seealso{
\code{\link[=step_logit]{step_logit()}} \code{\link[=step_invlogit]{step_invlogit()}}
\code{\link[=step_hyperbolic]{step_hyperbolic()}} \code{\link[=step_sqrt]{step_sqrt()}}
\code{\link[=recipe]{recipe()}} \code{\link[=prep.recipe]{prep.recipe()}}
\code{\link[=bake.recipe]{bake.recipe()}}
}
\concept{preprocessing}
\concept{transformation_methods}
\keyword{datagen}
|
