In RemPsyc/rempsyc: Convenience Functions for Psychology

library(knitr)

knitr::opts_chunk$set(
  fig.width = 5, fig.height = 3, warning = FALSE,
  message = FALSE, out.width = "70%"
)
knitr::opts_knit$set(root.dir = tempdir())

pkgs <- c("effectsize", "flextable", "interactions")
successfully_loaded <- vapply(pkgs, requireNamespace, FUN.VALUE = logical(1L), quietly = TRUE)
can_evaluate <- all(successfully_loaded)

if (can_evaluate) {
  knitr::opts_chunk$set(eval = TRUE)
  vapply(pkgs, require, FUN.VALUE = logical(1L), quietly = TRUE, character.only = TRUE)
} else {
  knitr::opts_chunk$set(eval = FALSE)
}

Sometimes in research, we want to know whether the effect of variable X on Y is affected by a third variable, variable Z. In other terms, we ask if there is an interaction between variables X and Z, and their effects on Z.

Note that this is different from mediation, where the mediator is the mechanism that explains the link between X and Y (rather than a variable that modifies an existing relationship like in moderation).

In R, we conduct moderation analyses using straight linear models with the lm function, and we specify interaction effects with the * operator. Not everyone is familiar with using lm however, so rempsyc provides a (relatively) simpler interface where it is straightforward what variable is the moderator, and which one is the predictor. Although it does not make a difference between the lm model, for some (e.g., that find the lm function scary), it can be helpful to think about these variables in this way. The other benefit is that it provides a useful effect size and its 95% confidence interval, and formats everything in a table ready to be exported to word through nice_table.

The topic of moderations and simple slopes can be a complex one. It is not the goal of this tutorial to describe the theory behind it, only to show a practical way to do them. For a more detailed reading on the topic, please see one of the existing excellent sources on the topic (1, 2, 3).

Getting started

Let's first load the demo data. This data set comes with base R (meaning you have it too and can directly type this command into your R console).

head(mtcars)

Load the rempsyc package:

library(rempsyc)

Note: If you haven't installed this package yet, you will need to install it via the following command: install.packages("rempsyc"). Furthermore, you may be asked to install the following packages if you haven't installed them already (you may decide to install them all now to avoid interrupting your workflow if you wish to follow this tutorial from beginning to end):

pkgs <- c("effectsize", "flextable", "interactions")
install_if_not_installed(pkgs)

---

For moderations and simple slopes, we usually want to standardize (or at least center) our variables.

mtcars2 <- lapply(mtcars, scale) |> as.data.frame()

Simple moderation: nice_mod

moderations <- nice_mod(
  data = mtcars2,
  response = "mpg",
  predictor = "gear",
  moderator = "wt"
)
moderations

If we want it to look nice

(my_table <- nice_table(moderations, highlight = TRUE))

Note: The sr2 (semi-partial correlation squared, also known as delta R-square) allows us to quantify the unique contribution (proportion of variance explained) of an independent variable on the dependent variable, over and above the other variables in the model. sr2 is often considered a better indicator of the practical relevance of a variable.

Open (or save) table to Word

Let's save it to word for use in a publication (optional).

# Open in Word
print(my_table, preview = "docx")

# Save in Word
flextable::save_as_docx(my_table, path = "moderations.docx")

Simple slopes: nice_slopes

You might have heard about "simple slopes" before. But what does that mean? Essentially, this means looking at the strength (regression coefficient) and significance of the slope, when subsetting for observations that are high, low, or average on a variable, typically the moderating variable. A bit further down, this will get clearer by looking at the plot of the interaction, which shows one slope for observations that are high on the wt (moderating) variable, a second slope for those that are low, and a third slope for those that are average.

Let's extract the simple slopes now, including the sr2.

slopes <- nice_slopes(
  data = mtcars2,
  response = "mpg",
  predictor = "gear",
  moderator = "wt"
)
slopes
nice_table(slopes, highlight = TRUE)

In this specific case, the interaction is significant but none of the simple slopes. This means that although the two slopes are significantly different from each other, taken individually, the slopes aren't significantly different from a straight line.

The neat thing is that you can add as many dependent variables at once as you want.

# Moderations
nice_mod(
  data = mtcars2,
  response = c("mpg", "disp", "hp"),
  predictor = "gear",
  moderator = "wt"
) |>
  nice_table(highlight = TRUE)

# Simple slopes
nice_slopes(
  data = mtcars2,
  response = c("mpg", "disp", "hp"),
  predictor = "gear",
  moderator = "wt"
) |>
  nice_table(highlight = TRUE)

Pro tip: Both the nice_mod() and nice_slopes() functions take the same argument, so you can just copy-paste the first and change the function call to save time!

Special cases

Covariates

You can also have more complicated models, like with added covariates.

Moderations

nice_mod(
  data = mtcars2,
  response = "mpg",
  predictor = "gear",
  moderator = "wt",
  covariates = c("am", "vs")
) |>
  nice_table(highlight = TRUE)

Simple slopes

nice_slopes(
  data = mtcars2,
  response = "mpg",
  predictor = "gear",
  moderator = "wt",
  covariates = c("am", "vs")
) |>
  nice_table(highlight = TRUE)

In this case, only the third row is significant, which means that those who are high on the wt variable (above one standard deviation) have significantly lower mpg the higher their gear. We can plot this in the more traditional way:

# First need to define model for plot function
mod <- lm(mpg ~ gear * wt + am + vs, data = mtcars2)

# Plot the model
library(interactions)
interact_plot(mod, pred = "gear", modx = "wt", interval = TRUE)

Note: If you haven't installed this package yet, you will need to install it via the following command: install.packages(interactions). Furthermore, know that this plot can be heavily customized with available arguments for publication purposes, but I won't be going into these details here.

Three-way interaction

Let's make a three-way interaction for example.

Note that for the simple slopes, for now, the second moderator needs to be a dichotomic variable (and the first moderator a continuous variable). We'll reset the am variable for this purpose for now.

mtcars2$am <- mtcars$am

Moderations

nice_mod(
  response = "mpg",
  predictor = "gear",
  moderator = "disp",
  moderator2 = "am",
  data = mtcars2
) |>
  nice_table(highlight = TRUE)

Simple slopes

nice_slopes(
  data = mtcars2,
  response = "mpg",
  predictor = "gear",
  moderator = "disp",
  moderator2 = "am"
) |>
  nice_table(highlight = TRUE)

Complex models: nice_lm

For more complicated models not supported by nice_mod, one can define the model in the traditional way and feed it to nice_lm and nice_lm_slopes instead. They support multiple lm models as well.

nice_lm

model1 <- lm(mpg ~ cyl + wt * hp, mtcars2)
model2 <- lm(qsec ~ disp + drat * carb, mtcars2)
my.models <- list(model1, model2)
nice_lm(my.models) |>
  nice_table(highlight = TRUE)

The same applies to simple slopes, this time we use the nice_lm_slopes function. It supports multiple lm models as well, but the predictor and moderator need to be the same for these models (the dependent variable can change).

nice_lm_slopes

model1 <- lm(mpg ~ gear * wt, mtcars2)
model2 <- lm(disp ~ gear * wt, mtcars2)
my.models <- list(model1, model2)
nice_lm_slopes(my.models, predictor = "gear", moderator = "wt") |>
  nice_table(highlight = TRUE)

Thanks for checking in

Make sure to check out this page again if you use the code after a time or if you encounter errors, as I periodically update or improve the code. Feel free to contact me for comments, questions, or requests to improve this function at https://github.com/rempsyc/rempsyc/issues. See all tutorials here: https://remi-theriault.com/tutorials.

RemPsyc/rempsyc documentation built on July 2, 2024, 9:41 p.m.