Default recipe blueprint
This pages holds the details for the recipe preprocessing blueprint. This
is the blueprint used by default from mold() if x is a recipe.
default_recipe_blueprint( intercept = FALSE, allow_novel_levels = FALSE, fresh = TRUE, composition = "tibble" ) ## S3 method for class 'recipe' mold(x, data, ..., blueprint = NULL)
intercept |
A logical. Should an intercept be included in the
processed data? This information is used by the |
allow_novel_levels |
A logical. Should novel factor levels be allowed at
prediction time? This information is used by the |
fresh |
Should already trained operations be re-trained when |
composition |
Either "tibble", "matrix", or "dgCMatrix" for the format of the processed predictors. If "matrix" or "dgCMatrix" are chosen, all of the predictors must be numeric after the preprocessing method has been applied; otherwise an error is thrown. |
x |
An unprepped recipe created from |
data |
A data frame or matrix containing the outcomes and predictors. |
... |
Not used. |
blueprint |
A preprocessing |
For default_recipe_blueprint(), a recipe blueprint.
When mold() is used with the default recipe blueprint:
It calls recipes::prep() to prep the recipe.
It calls recipes::juice() to extract the outcomes and predictors. These
are returned as tibbles.
If intercept = TRUE, adds an intercept column to the predictors.
When forge() is used with the default recipe blueprint:
It calls shrink() to trim new_data to only the required columns and
coerce new_data to a tibble.
It calls scream() to perform validation on the structure of the columns
of new_data.
It calls recipes::bake() on the new_data using the prepped recipe
used during training.
It adds an intercept column onto new_data if intercept = TRUE.
library(recipes) # --------------------------------------------------------------------------- # Setup train <- iris[1:100,] test <- iris[101:150,] # --------------------------------------------------------------------------- # Recipes example # Create a recipe that logs a predictor rec <- recipe(Species ~ Sepal.Length + Sepal.Width, train) %>% step_log(Sepal.Length) processed <- mold(rec, train) # Sepal.Length has been logged processed$predictors processed$outcomes # The underlying blueprint is a prepped recipe processed$blueprint$recipe # Call forge() with the blueprint and the test data # to have it preprocess the test data in the same way forge(test, processed$blueprint) # Use `outcomes = TRUE` to also extract the preprocessed outcome! # This logged the Sepal.Length column of `new_data` forge(test, processed$blueprint, outcomes = TRUE) # --------------------------------------------------------------------------- # With an intercept # You can add an intercept with `intercept = TRUE` processed <- mold(rec, train, blueprint = default_recipe_blueprint(intercept = TRUE)) processed$predictors # But you also could have used a recipe step rec2 <- step_intercept(rec) mold(rec2, iris)$predictors # --------------------------------------------------------------------------- # Non standard roles # If you have custom recipe roles, they are processed and returned in # the `$extras$roles` slot of the return value of `mold()` and `forge()`. rec_roles <- recipe(train) %>% update_role(Sepal.Width, new_role = "predictor") %>% update_role(Species, new_role = "outcome") %>% update_role(Sepal.Length, new_role = "custom_role") %>% update_role(Petal.Length, new_role = "custom_role2") processed_roles <- mold(rec_roles, train) processed_roles$extras forge(test, processed_roles$blueprint) # --------------------------------------------------------------------------- # Matrix output for predictors # You can change the `composition` of the predictor data set bp <- default_recipe_blueprint(composition = "dgCMatrix") processed <- mold(rec, train, blueprint = bp) class(processed$predictors)
Please choose more modern alternatives, such as Google Chrome or Mozilla Firefox.