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/ratio.R
\name{step_ratio}
\alias{step_ratio}
\alias{denom_vars}
\alias{tidy.step_ratio}
\title{Ratio Variable Creation}
\usage{
step_ratio(
recipe,
...,
role = "predictor",
trained = FALSE,
denom = denom_vars(),
naming = function(numer, denom) make.names(paste(numer, denom, sep = "_o_")),
columns = NULL,
skip = FALSE,
id = rand_id("ratio")
)
denom_vars(...)
\method{tidy}{step_ratio}(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 will be used in the \emph{numerator} of the ratio.
When used with \code{denom_vars}, the dots indicate which
variables are used in the \emph{denominator}. See
\code{\link[=selections]{selections()}} for more details. For the \code{tidy}
method, these are not currently used.}
\item{role}{For terms created by this step, what analysis role
should they be assigned?. By default, the function assumes that
the newly created ratios 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{denom}{A call to \code{denom_vars} to specify which
variables are used in the denominator that can include specific
variable names separated by commas or different selectors (see
\code{\link[=selections]{selections()}}). If a column is included in both lists
to be numerator and denominator, it will be removed from the
listing.}
\item{naming}{A function that defines the naming convention for
new ratio columns.}
\item{columns}{The column names used in the ratios. This
argument is not populated until \code{\link[=prep.recipe]{prep.recipe()}} is
executed.}
\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_ratio} 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
selectors or variables selected) and \code{denom}.
}
\description{
\code{step_ratio} creates a \emph{specification} of a recipe
step that will create one or more ratios out of numeric
variables.
}
\examples{
library(recipes)
library(modeldata)
data(biomass)
biomass$total <- apply(biomass[, 3:7], 1, sum)
biomass_tr <- biomass[biomass$dataset == "Training",]
biomass_te <- biomass[biomass$dataset == "Testing",]
rec <- recipe(HHV ~ carbon + hydrogen + oxygen + nitrogen +
sulfur + total,
data = biomass_tr)
ratio_recipe <- rec \%>\%
# all predictors over total
step_ratio(all_predictors(), denom = denom_vars(total)) \%>\%
# get rid of the original predictors
step_rm(all_predictors(), -ends_with("total"))
ratio_recipe <- prep(ratio_recipe, training = biomass_tr)
ratio_data <- bake(ratio_recipe, biomass_te)
ratio_data
}
\concept{preprocessing}
\keyword{datagen}
|
