View source: R/recipe_steps_preprocessing.R
| step_poisson_scale | R Documentation |
step_poisson_scale() creates a specification of a recipe step that
divides each selected column by the square root of its mean plus an
offset, as poisson_scale() does (column mode).
step_poisson_scale(
recipe,
...,
role = NA,
trained = FALSE,
offset = 3,
scales = NULL,
columns = NULL,
skip = FALSE,
id = recipes::rand_id("poisson_scale")
)
recipe |
A recipe object. The step will be added to the sequence of operations for this recipe. |
... |
One or more selector functions to choose the predictors (for
example, the spectral channels). See |
role |
Not used by this step, since no new variables are created. |
trained |
A logical indicating whether the step has been trained. |
offset |
The offset, in percent of the largest column mean. Default is 3. |
scales |
The scale of each column, stored once the step has been trained. |
columns |
The names of the selected columns, stored once the step has been trained. |
skip |
A logical. Should the step be skipped when the recipe is baked
by |
id |
A character string that is unique to this step. |
Poisson scaling suits count data, whose variance grows with the mean. The
scales \sqrt{\bar{x}_j + c} are estimated from the training data,
where the offset c is offset percent of the largest column mean,
and are applied unchanged to new data. tidy()
returns the selected terms, the scale each column is divided by (NA
before the step is trained) and id.
An updated version of recipe with the new step added to the
sequence of existing steps.
poisson_scale(), step_pareto_scale()
data(forageLIBS)
# potassium and the K I resonance lines
wl <- suppressWarnings(as.numeric(names(forageLIBS)))
dat <- forageLIBS[c(which(names(forageLIBS) == "K"), which(wl > 760 & wl < 780))]
rec <- recipes::recipe(K ~ ., data = dat[1:300, ]) |>
step_poisson_scale(recipes::all_predictors())
prepped <- recipes::prep(rec)
recipes::bake(prepped, new_data = dat[301:368, ])
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.