# Sophisticated models in emmeans

#### emmeans package, Version 1.3.4

This vignette gives a few examples of the use of the emmeans package to analyze other than the basic types of models provided by the stats package. Emphasis here is placed on accessing the optional capabilities that are typically not needed for the more basic models. A reference for all supported models is provided in the “models” vignette.

## Contents

1. Linear mixed models (lmer)
   1. System options for lmerMod models
2. Models with offsets
3. Ordinal models
4. Models fitted using MCMC methods
5. Reference for supported models

Index of all vignette topics

## Linear mixed models (lmer)

Linear mixed models are really important in statistics. Emphasis here is placed on those fitted using `lme4::lmer()`, but emmeans also supports other mixed-model packages such as nlme.

To illustrate, consider the `Oats` dataset in the nlme package. It has the results of a balanced split-plot experiment: experimental blocks are divided into plots that are randomly assigned to oat varieties, and the plots are subdivided into subplots that are randomly assigned to amounts of nitrogen within each plot. We will consider a linear mixed model for these data, excluding interaction (which is justified in this case). For sake of illustration, we will exclude a few observations.

    Oats.lmer <- lme4::lmer(yield ~ Variety + factor(nitro) + (1|Block/Variety),
                            data = nlme::Oats, subset = -c(1,2,3,5,8,13,21,34,55))

Let’s look at the EMMs for `nitro`:

    Oats.emm.n <- emmeans(Oats.lmer, "nitro")
    Oats.emm.n

    ##  nitro emmean   SE   df lower.CL upper.CL
    ##    0.0   78.9 7.29 7.78     62.0     95.8
    ##    0.2   97.0 7.14 7.19     80.3    113.8
    ##    0.4  114.2 7.14 7.19     97.4    131.0
    ##    0.6  124.1 7.07 6.95    107.3    140.8
    ##
    ## Results are averaged over the levels of: Variety
    ## Degrees-of-freedom method: kenward-roger
    ## Confidence level used: 0.95

You will notice that the degrees of freedom are fractional: that is due to the fact that whole-plot and subplot variations are combined when standard errors are estimated. Different degrees-of-freedom methods are available. By default, the Kenward-Roger method is used, and that’s why you see a message about the pbkrtest package being loaded, as it implements that method. We may specify a different degrees-of-freedom method via the optional argument `lmer.df`:

    emmeans(Oats.lmer, "nitro", lmer.df = "satterthwaite")

    ##  nitro emmean   SE   df lower.CL upper.CL
    ##    0.0   78.9 7.28 7.28     61.8       96
    ##    0.2   97.0 7.13 6.72     80.0      114
    ##    0.4  114.2 7.13 6.72     97.2      131
    ##    0.6  124.1 7.07 6.49    107.1      141
    ##
    ## Results are averaged over the levels of: Variety
    ## Degrees-of-freedom method: satterthwaite
    ## Confidence level used: 0.95

######

This latest result uses the Satterthwaite method, which is implemented in the lmerTest package. Note that, with this method, not only are the degrees of freedom slightly different, but so are the standard errors. That is because the Kenward-Roger method also entails making a bias adjustment to the covariance matrix of the fixed effects; that is the principal difference between the methods. A third possibility is `"asymptotic"`:

    emmeans(Oats.lmer, "nitro", lmer.df = "asymptotic")

    ##  nitro emmean   SE  df asymp.LCL asymp.UCL
    ##    0.0   78.9 7.28 Inf      64.6      93.2
    ##    0.2   97.0 7.13 Inf      83.1     111.0
    ##    0.4  114.2 7.13 Inf     100.2     128.2
    ##    0.6  124.1 7.07 Inf     110.2     137.9
    ##
    ## Results are averaged over the levels of: Variety
    ## Degrees-of-freedom method: asymptotic
    ## Confidence level used: 0.95

This just sets all the degrees of freedom to `Inf` – that’s emmeans’s way of using z statistics rather than t statistics. The asymptotic methods tend to make confidence intervals a bit too narrow and P values a bit too low; but they involve much, much less computation. Note that the SEs are the same as obtained using the Satterthwaite method.

Comparisons and contrasts are pretty much the same as with other models. As `nitro` has quantitative levels, we might want to test polynomial contrasts:

    contrast(Oats.emm.n, "poly")

    ##  contrast  estimate    SE   df t.ratio p.value
    ##  linear      152.69 15.58 43.2  9.802  <.0001
    ##  quadratic    -8.27  6.95 44.2 -1.190  0.2402
    ##  cubic        -6.32 15.21 42.8 -0.415  0.6800
    ##
    ## Results are averaged over the levels of: Variety

The interesting thing here is that the degrees of freedom are much larger than they are for the EMMs. The reason is because `nitro` within-plot factor, so inter-plot variations have little role in estimating contrasts among `nitro` levels. On the other hand, `Variety` is a whole-plot factor, and there is not much of a bump in degrees of freedom for comparisons:

    emmeans(Oats.lmer, pairwise ~ Variety)

    ## $emmeans
    ##  Variety     emmean   SE   df lower.CL upper.CL
    ##  Golden Rain  105.2 7.53 8.46     88.0      122
    ##  Marvellous   108.5 7.48 8.28     91.3      126
    ##  Victory       96.9 7.64 8.81     79.6      114
    ##
    ## Results are averaged over the levels of: nitro
    ## Degrees-of-freedom method: kenward-roger
    ## Confidence level used: 0.95
    ##
    ## $contrasts
    ##  contrast                 estimate   SE   df t.ratio p.value
    ##  Golden Rain - Marvellous    -3.23 6.55 9.56 -0.493  0.8764
    ##  Golden Rain - Victory        8.31 6.71 9.80  1.238  0.4595
    ##  Marvellous - Victory        11.54 6.67 9.80  1.729  0.2431
    ##
    ## Results are averaged over the levels of: nitro
    ## P value adjustment: tukey method for comparing a family of 3 estimates

### System options for lmerMod models

The computation required to compute the adjusted covariance matrix and degrees of freedom may become cumbersome. Some user options (i.e., `emm_options()` calls) make it possible to streamline these computations through default methods and limitations on them. First, the option `lmer.df`, which may have values of `"kenward-roger"`, `"satterthwaite"`, or `"asymptotic"` (partial matches are OK!) specifies the default degrees-of-freedom method.

The options `disable.pbkrtest` and `disable.lmerTest` may be `TRUE` or `FALSE`, and comprise another way of controlling which method is used (e.g., the Kenward-Roger method will not be used if `get_emm_option("disable.pbkrtest") == TRUE`). Finally, the options `pbkrtest.limit` and `lmerTest.limit`, which should be set to numeric values, enable the given package conditionally on whether the number of data rows does not exceed the given limit. The factory default is 3000 for both limits.

Back to Contents

## Models with offsets

If a model is fitted and its formula includes an `offset()` term, then by default, the offset is computed and included in the reference grid. To illustrate, consider a hypothetical dataset on insurance claims (used as an example in SAS’s documentation). There are classes of cars of varying counts (`n`), sizes (`size`), and age (`age`), and we record the number of insurance claims (`claims`). We fit a Poisson model to `claims` as a function of `size` and `age`. An offset of `log(n)` is included so that `n` functions as an “exposure” variable.

    ins <- data.frame(
        n = c(500, 1200, 100, 400, 500, 300),
        size = factor(rep(1:3,2), labels = c("S","M","L")),
        age = factor(rep(1:2, each = 3)),
        claims = c(42, 37, 1, 101, 73, 14))
    ins.glm <- glm(claims ~ size + age + offset(log(n)),
                   data = ins, family = "poisson")

First, let’s look at the reference grid obtained by default:

    ref_grid(ins.glm)

    ## 'emmGrid' object with variables:
    ##     size = S, M, L
    ##     age = 1, 2
    ##     n = 500
    ## Transformation: "log"

Note that `n` is included in the reference grid and that its average value of 500 is used for all predictions. Thus, if we obtain EMMs for, say, `age`, these are results are based on a pool of 500 cars:

    emmeans(ins.glm, "size", type = "response")

    ##  size rate   SE  df asymp.LCL asymp.UCL
    ##  S    69.3 6.25 Inf     58.03      82.7
    ##  M    34.6 3.34 Inf     28.67      41.9
    ##  L    11.9 3.14 Inf      7.07      19.9
    ##
    ## Results are averaged over the levels of: age
    ## Confidence level used: 0.95
    ## Intervals are back-transformed from the log scale

However, many users would like to ignore the offset for this kind of model, because then the estimates we obtain are rates per unit value of the (logged) offset. This may be accomplished by specifying an `offset` parameter in the call:

    emmeans(ins.glm, "size", type = "response", offset = 0)

    ##  size   rate      SE  df asymp.LCL asymp.UCL
    ##  S    0.1385 0.01250 Inf    0.1161    0.1653
    ##  M    0.0693 0.00669 Inf    0.0573    0.0837
    ##  L    0.0237 0.00627 Inf    0.0141    0.0398
    ##
    ## Results are averaged over the levels of: age
    ## Confidence level used: 0.95
    ## Intervals are back-transformed from the log scale

You may verify that the above estimates are 1/500th of the previous ones. You may also verify that the above results are identical to those obtained by setting `n` equal to 1:

    emmeans(ins.glm, "size", type = "response", at = list(n = 1))

However, those who use these types of models will be more comfortable directly setting the offset to zero.

By the way, you may set some other reference value for the rates. For example, if you want estimates of claims per 100 cars, simply use (results not shown):

    emmeans(ins.glm, "size", type = "response", offset = log(100))

Back to Contents

## Ordinal models

Ordinal-response models comprise an example where several options are available for obtaining EMMs. To illustrate, consider the `wine` data in the ordinal package. The response is a rating of bitterness on a five-point scale. we will consider a probit model in two factors during fermentation: `temp` (temperature) and `contact` (contact with grape skins), with the judge making the rating as a scale predictor:

    require("ordinal")

    ## Loading required package: ordinal

    wine.clm <- clm(rating ~ temp + contact, scale = ~ judge,
                    data = wine, link = "probit")

(in earlier modeling, we found little interaction between the factors.) Here are the EMMs for each factor using default options:

    emmeans(wine.clm, list(pairwise ~ temp, pairwise ~ contact))

    ## $`emmeans of temp`
    ##  temp emmean    SE  df asymp.LCL asymp.UCL
    ##  cold -0.884 0.290 Inf    -1.452    -0.316
    ##  warm  0.601 0.225 Inf     0.161     1.041
    ##
    ## Results are averaged over the levels of: contact, judge
    ## Confidence level used: 0.95
    ##
    ## $`pairwise differences of temp`
    ##  contrast    estimate    SE  df z.ratio p.value
    ##  cold - warm    -1.07 0.422 Inf -2.547  0.0109
    ##
    ## Results are averaged over the levels of: contact, judge
    ##
    ## $`emmeans of contact`
    ##  contact emmean    SE  df asymp.LCL asymp.UCL
    ##  no      -0.614 0.298 Inf   -1.1990   -0.0297
    ##  yes      0.332 0.201 Inf   -0.0632    0.7264
    ##
    ## Results are averaged over the levels of: temp, judge
    ## Confidence level used: 0.95
    ##
    ## $`pairwise differences of contact`
    ##  contrast estimate    SE  df z.ratio p.value
    ##  no - yes   -0.684 0.304 Inf -2.251  0.0244
    ##
    ## Results are averaged over the levels of: temp, judge

These results are on the “latent” scale; the idea is that there is a continuous random variable (in this case normal, due to the probit link) having a mean that depends on the predictors; and that the ratings are a discretization of the latent variable based on a fixed set of cut points (which are estimated). In this particular example, we also have a scale model that says that the variance of the latent variable depends on the judges. The latent results are quite a bit like those for measurement data, making them easy to interpret. The only catch is that they are not uniquely defined: we could apply a linear transformation to them, and the same linear transformation to the cut points, and the results would be the same.

######

The `clm` function actually fits the model using an ordinary probit model but with different intercepts for each cut point. We can get detailed information for this model by specifying `mode = "linear.predictor"`:

    tmp <- ref_grid(wine.clm, mode = "lin")
    tmp

    ## 'emmGrid' object with variables:
    ##     temp = cold, warm
    ##     contact = no, yes
    ##     judge = 1, 2, 3, 4, 5, 6, 7, 8, 9
    ##     cut = multivariate response levels: 1|2, 2|3, 3|4, 4|5
    ## Transformation: "probit"

Note that this reference grid involves an additional constructed predictor named `cut` that accounts for the different intercepts in the model. Let’s obtain EMMs for `temp` on the linear-predictor scale:

    emmeans(tmp, "temp")

    ##  temp emmean    SE  df asymp.LCL asymp.UCL
    ##  cold  0.884 0.290 Inf     0.316     1.452
    ##  warm -0.601 0.225 Inf    -1.041    -0.161
    ##
    ## Results are averaged over the levels of: contact, judge, cut
    ## Results are given on the probit (not the response) scale.
    ## Confidence level used: 0.95

These are just the negatives of the latent results obtained earlier (the sign is changed to make the comparisons go the right direction). Closely related to this is `mode = "cum.prob"` and `mode = "exc.prob"`, which simply transform the linear predictor to cumulative probabilities and exceedance (1 - cumulative) probabilities. These modes give us access to the details of the fitted model but are cumbersome to use for describing results. When they can become useful is when you want to work in terms of a particular cut point. Let’s look at `temp` again in terms of the probability that the rating will be at least 4:

    emmeans(wine.clm, ~ temp, mode = "exc.prob", at = list(cut = "3|4"))

    ##  temp exc.prob     SE  df asymp.LCL asymp.UCL
    ##  cold   0.0748 0.0318 Inf    0.0124     0.137
    ##  warm   0.4069 0.0706 Inf    0.2686     0.545
    ##
    ## Results are averaged over the levels of: contact, judge
    ## Confidence level used: 0.95

######

There are yet more modes! With `mode = "prob"`, we obtain estimates of the probability distribution of each rating. Its reference grid includes a factor with the same name as the model response – in this case `rating`. We usually want to use that as the primary factor, and the factors of interest as `by` variables:

    emmeans(wine.clm, ~ rating | temp, mode = "prob")

    ## temp = cold:
    ##  rating   prob     SE  df asymp.LCL asymp.UCL
    ##  1      0.1292 0.0625 Inf   0.00667    0.2518
    ##  2      0.4877 0.0705 Inf   0.34948    0.6259
    ##  3      0.3083 0.0594 Inf   0.19186    0.4248
    ##  4      0.0577 0.0238 Inf   0.01104    0.1043
    ##  5      0.0171 0.0127 Inf  -0.00768    0.0419
    ##
    ## temp = warm:
    ##  rating   prob     SE  df asymp.LCL asymp.UCL
    ##  1      0.0156 0.0129 Inf  -0.00961    0.0408
    ##  2      0.1473 0.0448 Inf   0.05959    0.2350
    ##  3      0.4302 0.0627 Inf   0.30723    0.5532
    ##  4      0.2685 0.0625 Inf   0.14593    0.3910
    ##  5      0.1384 0.0506 Inf   0.03923    0.2376
    ##
    ## Results are averaged over the levels of: contact, judge
    ## Confidence level used: 0.95

Using `mode = "mean.class"` obtains the average of these probability distributions as probabilities of the integers 1–5:

    emmeans(wine.clm, "temp", mode = "mean.class")

    ##  temp mean.class    SE  df asymp.LCL asymp.UCL
    ##  cold       2.35 0.144 Inf      2.06      2.63
    ##  warm       3.37 0.146 Inf      3.08      3.65
    ##
    ## Results are averaged over the levels of: contact, judge
    ## Confidence level used: 0.95

And there is a mode for the scale model too. In this example, the scale model involves only judges, and that is the only factor in the grid:

    summary(ref_grid(wine.clm, mode = "scale"), type = "response")

    ##  judge response    SE  df
    ##  1        1.000 0.000 Inf
    ##  2        1.043 0.570 Inf
    ##  3        1.053 0.481 Inf
    ##  4        0.710 0.336 Inf
    ##  5        0.663 0.301 Inf
    ##  6        0.758 0.341 Inf
    ##  7        1.071 0.586 Inf
    ##  8        0.241 0.179 Inf
    ##  9        0.533 0.311 Inf

Judge 8’s ratings don’t vary much, relative to the others. The scale model is in terms of log(SD). Again, these are not uniquely identifiable, and the first level’s estimate is set to log(1) = 0. so, actually, each estimate shown is a comparison with judge 1.

Back to Contents

## Models fitted using MCMC methods

To illustrate emmeans’s support for models fitted using MCMC methods, consider the `example_model` available in the rstanarm package. The example concerns CBPP, a serious disease of cattle in Ethiopia. A generalized linear mixed model was fitted to the data using the code below. We subsequently obtain its reference grid in the usual way.

    example_model <- rstanarm::stan_glmer(
        cbind(incidence, size - incidence) ~ size + period + (1|herd),
        data = lme4::cbpp, family = binomial,
        chains = 2, cores = 1, seed = 12345, iter = 500)
    cbpp.rg <- ref_grid(example_model)

Here is the structure of the reference grid:

    cbpp.rg

    ## 'emmGrid' object with variables:
    ##     size = 15.036
    ##     period = 1, 2, 3, 4
    ## Transformation: "logit"

And, again in the usual way, we can obtain EMMs:

    period.emm <- emmeans(cbpp.rg, "period")
    period.emm

    ##  period emmean lower.HPD upper.HPD
    ##  1       -1.43     -1.96    -0.894
    ##  2       -2.39     -3.13    -1.823
    ##  3       -2.52     -3.19    -1.862
    ##  4       -2.97     -3.88    -1.998
    ##
    ## Results are given on the logit (not the response) scale.
    ## HPD interval probability: 0.95

The summary for EMMs of Bayesian models shows the median of the posterior distribution of each estimate, along with highest posterior density (HPD) intervals. Under the hood, the posterior sample of parameter estimates is used to compute a corresponding sample of posterior EMMs, and it is those that are summarized. (Technical note: the summary is actually rerouted to the `hpd.summary()` function, and it loads the coda package if it is not already loaded.

######

We can access the posterior EMMs via the `as.mcmc` method for `emmGrid` objects. This gives us an object of class `mcmc` (defined in the coda package), which can be summarized and explored as we please.

    require("coda")

    ## Loading required package: coda

    summary(as.mcmc(period.emm))

    ##
    ## Iterations = 1:250
    ## Thinning interval = 1
    ## Number of chains = 2
    ## Sample size per chain = 250
    ##
    ## 1. Empirical mean and standard deviation for each variable,
    ##    plus standard error of the mean:
    ##
    ##            Mean     SD Naive SE Time-series SE
    ## period 1 -1.435 0.2825  0.01264        0.01771
    ## period 2 -2.393 0.3374  0.01509        0.01620
    ## period 3 -2.516 0.3409  0.01524        0.01540
    ## period 4 -2.979 0.4634  0.02072        0.02793
    ##
    ## 2. Quantiles for each variable:
    ##
    ##            2.5%    25%    50%    75%  97.5%
    ## period 1 -1.969 -1.618 -1.430 -1.262 -0.903
    ## period 2 -3.122 -2.609 -2.395 -2.165 -1.746
    ## period 3 -3.199 -2.739 -2.516 -2.286 -1.870
    ## period 4 -3.890 -3.254 -2.968 -2.698 -2.003

Note that `as.mcmc` will actually produce an `mcmc.list` when there is more than one chain present, as in this example. The 2.5th and 97.5th quantiles are similar, but not identical, to the 95% confidence intervals in the frequentist summary. Here is a plot of the posterior EMMs, back-transformed:

    bayesplot::mcmc_areas(as.mcmc(regrid(period.emm)))

… and here are intervals for each period compared with its neighbor:

    contrast(period.emm, "consec", reverse = TRUE)

    ##  contrast estimate lower.HPD upper.HPD
    ##  1 - 2       0.954     0.375     1.533
    ##  2 - 3       0.133    -0.581     0.942
    ##  3 - 4       0.439    -0.477     1.671
    ##
    ## Results are given on the log odds ratio (not the response) scale.
    ## HPD interval probability: 0.95

The only interval that excludes zero is the one that compares periods 1 and 2.

In summary, to do Bayesian analysis in the emmeans package, use the same tools that are available for other models, extract the MCMC samples using `as.mcmc()`, and summarize or plot from there.

Back to Contents

Index of all vignette topics