This document demonstrates some basic uses of recipes. First, some definitions are required:

  • variables are the original (raw) data columns in a data frame or tibble. For example, in a traditional formula Y ~ A + B + A:B, the variables are A, B, and Y.
  • roles define how variables will be used in the model. Examples are: predictor (independent variables), response, and case weight. This is meant to be open-ended and extensible.
  • terms are columns in a design matrix such as A, B, and A:B. These can be other derived entities that are grouped such a a set of principal components or a set of columns that define a basis function for a variable. These are synonymous with features in machine learning. Variables that have predictor roles would automatically be main effect terms

An Example

The packages contains a data set that used to predict whether a person will pay back a bank loan. It has 13 predictor columns and a factor variable Status (the outcome). We will first separate the data into a training and test set:



train_test_split <- initial_split(credit_data)

credit_train <- training(train_test_split)
credit_test <- testing(train_test_split)

Note that there are some missing values in these data:

Rather than remove these, their values will be imputed.

The idea is that the preprocessing operations will all be created using the training set and then these steps will be applied to both the training and test set.

An Initial Recipe

First, we will create a recipe object from the original data and then specify the processing steps.

Recipes can be created manually by sequentially adding roles to variables in a data set.

If the analysis only required outcomes and predictors, the easiest way to create the initial recipe is to use the standard formula method:

The data contained in the data argument need not be the training set; this data is only used to catalog the names of the variables and their types (e.g. numeric, etc.).

(Note that the formula method here is used to declare the variables and their roles and nothing else. If you use inline functions (e.g. log) it will complain. These types of operations can be added later.)

Preprocessing Steps

From here, preprocessing steps for some step X can be added sequentially in one of two ways:

step_dummy and the other functions will always return updated recipes.

One other important facet of the code is the method for specifying which variables should be used in different steps. The manual page ?selections has more details but dplyr-like selector functions can be used:

  • use basic variable names (e.g. x1, x2),
  • dplyr functions for selecting variables: contains, ends_with, everything, matches, num_range, and starts_with,
  • functions that subset on the role of the variables that have been specified so far: all_outcomes, all_predictors, has_role, or
  • similar functions for the type of data: all_nominal, all_numeric, and has_type.

Note that the methods listed above are the only ones that can be used to select variables inside the steps. Also, minus signs can be used to deselect variables.

For our data, we can add an operation to impute the predictors. There are many ways to do this and recipes includes a few steps for this purpose:

Here, K-nearest neighbor imputation will be used. This works for both numeric and non-numeric predictors and defaults K to five To do this, it selects all predictors then removes those that are numeric:

It is important to realize that the specific variables have not been declared yet (as shown when the recipe is printed above). In some preprocessing steps, variables will be added or removed from the current list of possible variables.

Since some predictors are categorical in nature (i.e. nominal), it would make sense to convert these factor predictors into numeric dummy variables (aka indicator variables) using step_dummy. To do this, the step selects all predictors then removes those that are numeric:

At this point in the recipe, all of the predictor should be encoded as numeric, we can further add more steps to center and scale them:

If there are the only preprocessing steps for the predictors, we can now estimate the means and standard deviations from the training set. The prep function is used with a recipe and a data set:

Note that the real variables are listed (e.g. Home etc.) instead of the selectors (all_predictors()).

Now that the statistics have been estimated, the preprocessing can be applied to the training and test set:

train_data <- bake(trained_rec, new_data = credit_train)
test_data  <- bake(trained_rec, new_data = credit_test)

bake returns a tibble that, by default, includes all of the variables:

Selectors can also be used. For example, if only the predictors are needed, you can use bake(object, new_data, all_predictors()).

There are a number of other steps included in the package:

#>  [1] "step_arrange"       "step_bagimpute"     "step_bin2factor"   
#>  [4] "step_BoxCox"        "step_bs"            "step_center"       
#>  [7] "step_classdist"     "step_corr"          "step_count"        
#> [10] "step_date"          "step_depth"         "step_discretize"   
#> [13] "step_downsample"    "step_dummy"         "step_factor2string"
#> [16] "step_filter"        "step_geodist"       "step_holiday"      
#> [19] "step_hyperbolic"    "step_ica"           "step_integer"      
#> [22] "step_interact"      "step_intercept"     "step_inverse"      
#> [25] "step_invlogit"      "step_isomap"        "step_knnimpute"    
#> [28] "step_kpca"          "step_lag"           "step_lincomb"      
#> [31] "step_log"           "step_logit"         "step_lowerimpute"  
#> [34] "step_meanimpute"    "step_medianimpute"  "step_modeimpute"   
#> [37] "step_mutate"        "step_naomit"        "step_nnmf"         
#> [40] "step_novel"         "step_ns"            "step_num2factor"   
#> [43] "step_nzv"           "step_ordinalscore"  "step_other"        
#> [46] "step_pca"           "step_pls"           "step_poly"         
#> [49] "step_profile"       "step_range"         "step_ratio"        
#> [52] "step_regex"         "step_relu"          "step_rm"           
#> [55] "step_rollimpute"    "step_sample"        "step_scale"        
#> [58] "step_shuffle"       "step_slice"         "step_spatialsign"  
#> [61] "step_sqrt"          "step_string2factor" "step_unorder"      
#> [64] "step_upsample"      "step_window"        "step_YeoJohnson"   
#> [67] "step_zv"


Another type of operation that can be added to a recipes is a check. Checks conduct some sort of data validation and, if no issue is found, returns the data as-is; otherwise, an error is thrown.

For example, check_missing will fail if any of the variables selected for validation have missing values. This check is done when the recipe is prepared as well as when any data are baked. Checks are added in the same way as steps:

Currently, recipes includes:

#> [1] "check_cols"    "check_missing" "check_name"    "check_range"  
#> [5] "check_type"