knitr::opts_chunk$set(
  collapse = TRUE,
  comment = "#>",
  dev = "png",
  fig.width = 7,
  fig.height = 4,
  message = FALSE,
  warning = FALSE
)
options(width = 800)

pkgs <- c(
  "ggplot2",
  "lme4",
  "datawizard",
  "htmltools"
)

if (!all(vapply(pkgs, requireNamespace, quietly = TRUE, FUN.VALUE = logical(1L)))) {
  knitr::opts_chunk$set(eval = FALSE)
}
library(htmltools)
callout_tip <- function(header = NULL, ...) {
  div(
    class = "callout-tip",
    tags$h1(
      tags$img(src = "../man/figures/summary.png", width = "20", height = "17", style = "vertical-align:middle"), # nolint
      header
    ),
    ...
  )
}
includeCSS("../man/figures/callout.css")

Adjusted predictions and marginal means at specific values or levels

This vignettes shows how to calculate adjusted predictions at specific values or levels for the terms of interest. It is recommended to read the general introduction first, if you haven't done this yet.

The terms-argument not only defines the model terms (i.e. focal variables) of interest, but each model term can be limited to certain "meaningful" (or "representative") values. This allows to compute and plot adjusted predictions for (grouping) terms at specific values only, or to define values for the main effect of interest.

callout_tip(
  "Summary of most important points:",
  tags$ul(
    tags$li("The ", tags$code("terms"), " argument is not only used to define the focal terms, but also allows to specify meaningful values, at which predictions are calculated."), # nolint
    tags$li(tags$code("terms"), " can be a character vector, a list, a formula, or a data frame. If a character vector, the values for the focal terms are placed in square brackets directly after the term name."), # nolint
    tags$li("Although providing a list is probably the most R-native way to define the focal terms and meaningful values, providing a character vector additionally allows to use pre-defined \"shortcuts\". That's why this is the preferred way demonstrated throughout the package-documentation."), # nolint
    tags$li("Non-focal terms can be fixed at specific values using the ", tags$code("condition"), " argument.") # nolint
  )
)

There are several options to define these meaningful values:

When terms is specified as character vector, values always should be placed in square brackets directly after the term name and can vary for each model term. The following examples show how to specify values for the terms-argument.

  1. Concrete values are separated by a comma: terms = "c172code [1,3]". For factors, you could also use factor levels, e.g. terms = "Species [setosa,versicolor]". If terms is a named list, it would be specified like this: terms = list(c172code = c(1, 3)) or terms = list(c172code = c(1, 3), Species = c("setosa", "versicolor")). As a data frame, this would be:
terms <- data.frame(
  c172code = c(1, 3, 1, 3),
  Species = c("setosa", "setosa", "versicolor", "versicolor"),
  stringsAsFactors = FALSE
)
terms
  1. Ranges are specified with a colon: terms = c("c12hour [30:80]", "c172code [1,3]"). This would plot all values from 30 to 80 for the variable c12hour. By default, the step size is 1, i.e. [1:4] would create the range 1, 2, 3, 4. You can choose different step sizes with by, e.g. [1:4 by=.5]. As named list, this would be terms = list(c12hour = 30:80) or terms = list(c12hour = seq(1, 4, 0.5)).

  2. Convenient shortcuts to calculate common values like mean +/- 1 SD (terms = "c12hour [meansd]"), quartiles (terms = "c12hour [quartiles]") or minumum and maximum values (terms = "c12hour [minmax]"). See values_at() for the different options.

  3. A function name. The function is then applied to all unique values of the indicated variable, e.g. terms = "hp [exp]". You can also define own functions, and pass the name of it to the terms-values, e.g. terms = "hp [own_function]".

  4. A variable name. The values of the variable are then used to define the terms-values, e.g. first, a vector is defined: v = c(1000, 2000, 3000) and then, terms = "income [v]".

  5. If the first variable specified in terms is a numeric vector, for which no specific values are given, a "pretty range" is calculated (see pretty_range()), to avoid memory allocation problems for vectors with many unique values. To select all values, use the [all]-tag, e.g. terms = "mpg [all]". If a numeric vector is specified as second or third variable in term (i.e. if this vector represents a grouping structure), representative values (see values_at()) are chosen, which is typically mean +/- SD.

  6. To create a pretty range that should be smaller or larger than the default range (i.e. if no specific values would be given), use the n-tag, e.g. terms = "age [n=5]" or terms = "age [n = 12]". Larger values for n return a larger range of predicted values.

  7. Especially useful for plotting group levels of random effects with many levels, is the sample-option, e.g. terms = "Subject [sample=9]", which will sample nine values from all possible values of the variable Subject.

Specific values and value range

library(ggeffects)
library(ggplot2)
data(efc, package = "ggeffects")
fit <- lm(barthtot ~ c12hour + neg_c_7 + c161sex + c172code, data = efc)

mydf <- predict_response(fit, terms = c("c12hour [30:80]", "c172code [1,3]"))
mydf
ggplot(mydf, aes(x, predicted, colour = group)) + geom_line()

When variables are, for instance, log-transformed, ggeffects automatically back-transforms predictions to the original scale of the response and predictors, making the predictions directly interpretable. However, sometimes it might be useful to define own value ranges. In such situation, specify the range in the terms-argument.

data(mtcars)
mpg_model <- lm(mpg ~ log(hp), data = mtcars)

# x-values and predictions based on the full range of the original "hp"-values
predict_response(mpg_model, "hp")

# x-values and predictions based on "hp"-values ranging from 50 to 150
predict_response(mpg_model, "hp [50:150]")

By default, the step size for a range is 1, like 50, 51, 52, .... If you need a different step size, use by=<stepsize> inside the brackets, e.g. "hp [50:60 by=.5]". This would create a range from 50 to 60, with .5er steps.

# range for x-values with .5-steps
predict_response(mpg_model, "hp [50:60 by=.5]")

Choosing representative values

Especially in situations where we have two continuous variables in interaction terms, or where the "grouping" variable is continuous, it is helpful to select representative values of the grouping variable - else, predictions would be made for too many groups, which is no longer helpful when interpreting adjusted predictions.

You can use

data(efc, package = "ggeffects")
# short variable label, for plot
attr(efc$c12hour, "label") <- "hours of care"
fit <- lm(barthtot ~ c12hour * c161sex + neg_c_7, data = efc)

mydf <- predict_response(fit, terms = c("c161sex", "c12hour [meansd]"))
plot(mydf)

mydf <- predict_response(fit, terms = c("c161sex", "c12hour [quartiles]"))
plot(mydf)

Transforming values with functions

The brackets in the terms-argument also accept the name of a valid function, to (back-)transform predicted values. In this example, we define a custom function to get the original values of the focal predictor, multiplied by 2.

# x-values and predictions based on "hp"-values, multiplied by 2
hp_double <- function(x) 2 * x
predict_response(mpg_model, "hp [hp_double]")

Using a list, the terms argument in the above example would look like this: terms = list(hp = hp_double(seq(100, 700, 7))).

Using values from a variable (vector)

val <- c(100, 200, 300)
predict_response(mpg_model, "hp [val]")

Using a list, the terms argument in the above example would look like this: terms = list(hp = val).

Pretty value ranges

This section is intended to show some examples how the plotted output differs, depending on which value range is used. Some transformations, like polynomial or spline terms, but also quadratic or cubic terms, result in many predicted values. In such situation, predictions for some models lead to memory allocation problems. That is why predict_response() "prettifies" certain value ranges by default, at least for some model types (like mixed models).

To see the difference in the "curvilinear" trend, we use a quadratic term on a standardized variable.

library(datawizard)
library(lme4)
data(efc, package = "ggeffects")

efc$c12hour <- standardize(efc$c12hour)
efc$e15relat <- to_factor(efc$e15relat)

m <- lmer(
  barthtot ~ c12hour + I(c12hour^2) + neg_c_7 + c160age + c172code + (1 | e15relat),
  data = efc
)

me <- predict_response(m, terms = "c12hour")
plot(me)

Turn off "prettifying"

As said above, predict_response() "prettifies" the vector, resulting in a smaller set of unique values. This is less memory consuming and may be needed especially for more complex models.

You can turn off automatic "prettifying" by adding the "all"-shortcut to the terms-argument.

me <- predict_response(m, terms = "c12hour [all]")
plot(me)

This results in a smooth plot, as all values from the term of interest are taken into account.

Using different ranges for prettifying

To modify the "prettifying", add the "n"-shortcut to the terms-argument. This allows you to select a feasible range of values that is smaller (and hence less memory consuming) them "terms = ... [all]", but still produces smoother plots than the default prettyfing.

me <- predict_response(m, terms = "c12hour [n=2]")
plot(me)
me <- predict_response(m, terms = "c12hour [n=10]")
plot(me)

Adjusted predictions conditioned on specific values of the covariates

By default, the typical-argument determines the function that will be applied to the covariates to hold these terms at constant values. By default, this is the mean-value, but other options (like median or mode) are possible as well.

Use the condition-argument to define other values at which covariates should be held constant. condition requires a named vector, with the name indicating the covariate.

data(mtcars)
mpg_model <- lm(mpg ~ log(hp) + disp, data = mtcars)

# "disp" is hold constant at its mean
predict_response(mpg_model, "hp")

# "disp" is hold constant at value 200
predict_response(mpg_model, "hp", condition = c(disp = 200))

Adjusted predictions for each level of random effects (unit-level predictions)

Adjusted predictions can also be calculated for each group level in mixed models. Simply add the name of the related random effects term to the terms-argument, and set type = "random".

In the following example, we fit a linear mixed model and first plot the population-level predictions. Please see also the dedicated vignette for mixed models for further details and examples.

library(lme4)
data(efc, package = "ggeffects")
efc$e15relat <- to_factor(efc$e15relat)
m <- lmer(neg_c_7 ~ c12hour + c160age + c161sex + (1 | e15relat), data = efc)
me <- predict_response(m, terms = "c12hour")
plot(me)

To compute adjusted predictions for each grouping level (unit-level predictions), add the related random term to the terms-argument.

me <- predict_response(m, terms = c("c12hour", "e15relat"), type = "random")
plot(me)

Unit-level predictions can also be calculated for specific levels only. Add the related values into brackets after the variable name in the terms-argument.

me <- predict_response(m, terms = c("c12hour", "e15relat [child,sibling]"), type = "random")
plot(me)

If the group factor has too many levels, you can also take a random sample of all possible levels and plot the adjusted predictions for this subsample of group levels. To do this, use term = "<groupfactor> [sample=n]".

data("sleepstudy")
m <- lmer(Reaction ~ Days + (1 + Days | Subject), data = sleepstudy)
me <- predict_response(m, terms = c("Days", "Subject [sample=8]"), type = "random")
plot(me)


strengejacke/ggeffects documentation built on Dec. 24, 2024, 3:27 a.m.