Abstract

The distinction between modeling a variable as a fixed versus a random effect depends on the goal of the statistical analysis. While some theory and software make a strong distinction, `variancePartition`

and `dream`

take different approaches based on the goal of each type of analysis. Here we consider the distinction between fixed and random effects, and the usage of REML in `variancePartition`

and `dream`

.

`variancePartition`

In traditional statistics and biostatistics, there is a strong distinction between modeling categorical variants as fixed and random effects. Random effects correspond to a sample of units from a larger population, while fixed effects correspond to properties of specific individuals. Random effects are typically treated as nuisance variables and integrated out, and hypothesis testing is performed on the fixed effect.

The `r2glmm`

package fits into this traditional framework, by computing the variance fractions for a given fixed effect as: \[\begin{eqnarray}
\sigma^2_{fixed}/ \left(\sigma^2_{fixed} + \sigma^2_{error}\right)
\end{eqnarray}\]

Importantly, the random effects are not in the denominator. The fraction is only determined by fixed effects and residuals.

In my experience in bioinformatics, this was a problem. Making such distinctions between fixed and random effects seemed arbitrary. Variance in a phenotype could be due to age (fixed) or to variation across subject (random). Including all of the variables in the denominator produced more intuitive results so that 1) the variance fractions sum to one across all components and 2) fixed and random effects could be interpreted on the same scale 3) fractions could be compared across studies with different designs, 4) estimates of variance fractions were most accurate. So in variancePartition the fractions are defined as: \[\begin{eqnarray} \sigma^2_{X}/ \left(\sigma^2_{fixed} + \sigma^2_{random} + \sigma^2_{error}\right) \end{eqnarray}\]

just plugging the each variable in the numerator.

Thus the faction evaluated by variancePartition is different than `r2glmm`

by definition.

Here is some code explicitly demonstrating this difference:

```
library("variancePartition")
library("lme4")
library("r2glmm")
set.seed(1)
N <- 1000
beta <- 3
alpha <- c(1, 5, 7)
# generate 1 fixed variable and 1 random variable with 3 levels
data <- data.frame(X = rnorm(N), Subject = sample(c("A", "B", "C"), 100, replace = TRUE))
# simulate variable
# y = X\beta + Subject\alpha + \sigma^2
data$y <- data$X * beta + model.matrix(~ data$Subject) %*% alpha + rnorm(N, 0, 1)
# fit model
fit <- lmer(y ~ X + (1 | Subject), data, REML = FALSE)
# calculate variance fraction using variancePartition
# include the total sum in the denominator
frac <- calcVarPart(fit)
frac
```

```
Subject X Residuals
0.4505 0.4952 0.0543
```

```
# the variance fraction excluding the random effect from the denominator
# is the same as from r2glmm
frac[["X"]] / (frac[["X"]] + frac[["Residuals"]])
```

`[1] 0.901`

```
Effect Rsq upper.CL lower.CL
1 Model 0.896 0.904 0.886
2 X 0.896 0.904 0.886
```

So the formulas are different. But why require categorical variables as random effects?

At practical level, categorical variables with too many levels are problematic. Using a categorical variable with 200 categories as a fixed effect is statistically unstable. There are so many degrees of freedom that that variable will absorb a lot of variance even under the null. Statistically, estimating the variance fraction for a variable with many categories can be biased if that variable is a fixed effect. Therefore, `variancePartition`

requires all categorical variables to be random effects. Modeling this variable as a random effect produces unbiased estimates of variance fractions in practice. See simulations in the Supplement (section 1.5) of Hoffman and Schadt (2016).

The distinction between fixed and random effects is important in the formulation because it affects which variables are put in the denominator. So choosing to model a variable as a fixed versus random effect will definitely change the estimated fraction.

Yet for the `variancePartition`

formulation, all variables are in the denominator and it isn`t affected by the fixed/random decision. Moreover, using a random effect empirically reduces the bias of the estimated fraction.

Finally, why use maximum likelihood to estimate the paramters instead of the default REML ()? Maximum likelihood fits all parameters jointly so that it estimates the fixed and random effects together. This is essential if we want to compare fixed and random effects later. Conversely, REML estimates the random effects by removing the fixed effects from the response before estimation. This implicitly removes the fixed effects from the denominator when evaluating the variance fraction. REML treats fixed effects as nuisance variables, while `variancePartition`

considers fixed effects to be a core part of the analysis.

While REML produced unbiased estimates of the variance components, the goal of `variancePartition`

is to estimate the variance fractions for fixed and random effects jointly. In simulations from the Supplement (section 1.5) of Hoffman and Schadt (2016), REML produced biased estimates of the variance fractions while maximum likelihood estimates are unbiased.

`dream`

While `dream`

is also based on a linear mixed model, the goal of this analysis is to perform hypothesis testing on fixed effects. Random effects are treated as nuisance variables to be integrated out, and the approximate null distribution of a t- or F-statistic is constructed from the model fit.

Since the goal of the analysis is different, the consideration of using REML versus ML is different than above. While is required by called by when , can be used with as either or . Since the Kenward-Roger method gave the best power with an accurate control of false positive rate in our simulations, and since the Satterthwaite method with gives p-values that are slightly closer to the Kenward-Roger p-values, is set as the default.

```
R version 4.4.0 RC (2024-04-16 r86468)
Platform: x86_64-pc-linux-gnu
Running under: Ubuntu 22.04.4 LTS
Matrix products: default
BLAS: /home/biocbuild/bbs-3.20-bioc/R/lib/libRblas.so
LAPACK: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3.10.0
locale:
[1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C
[3] LC_TIME=en_GB LC_COLLATE=C
[5] LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8
[7] LC_PAPER=en_US.UTF-8 LC_NAME=C
[9] LC_ADDRESS=C LC_TELEPHONE=C
[11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C
time zone: America/New_York
tzcode source: system (glibc)
attached base packages:
[1] stats4 stats graphics grDevices utils datasets methods
[8] base
other attached packages:
[1] r2glmm_0.1.2 lme4_1.1-35.3 Matrix_1.7-0
[4] org.Hs.eg.db_3.19.1 msigdbr_7.5.1 GSEABase_1.67.0
[7] graph_1.83.0 annotate_1.83.0 XML_3.99-0.16.1
[10] AnnotationDbi_1.67.0 IRanges_2.39.0 S4Vectors_0.43.0
[13] Biobase_2.65.0 BiocGenerics_0.51.0 zenith_1.7.0
[16] tximportData_1.33.0 tximport_1.33.0 readr_2.1.5
[19] edgeR_4.3.4 pander_0.6.5 variancePartition_1.35.4
[22] BiocParallel_1.39.0 limma_3.61.1 ggplot2_3.5.1
[25] knitr_1.47
loaded via a namespace (and not attached):
[1] jsonlite_1.8.8 magrittr_2.0.3
[3] farver_2.1.2 nloptr_2.0.3
[5] rmarkdown_2.27 zlibbioc_1.51.1
[7] vctrs_0.6.5 memoise_2.0.1
[9] minqa_1.2.7 RCurl_1.98-1.14
[11] progress_1.2.3 S4Arrays_1.5.1
[13] htmltools_0.5.8.1 curl_5.2.1
[15] broom_1.0.6 SparseArray_1.5.8
[17] sass_0.4.9 KernSmooth_2.23-24
[19] bslib_0.7.0 pbkrtest_0.5.2
[21] plyr_1.8.9 cachem_1.1.0
[23] lifecycle_1.0.4 iterators_1.0.14
[25] pkgconfig_2.0.3 R6_2.5.1
[27] fastmap_1.2.0 MatrixGenerics_1.17.0
[29] GenomeInfoDbData_1.2.12 rbibutils_2.2.16
[31] digest_0.6.35 numDeriv_2016.8-1.1
[33] colorspace_2.1-0 GenomicRanges_1.57.1
[35] RSQLite_2.3.7 filelock_1.0.3
[37] labeling_0.4.3 RcppZiggurat_0.1.6
[39] fansi_1.0.6 abind_1.4-5
[41] httr_1.4.7 compiler_4.4.0
[43] bit64_4.0.5 aod_1.3.3
[45] withr_3.0.0 backports_1.5.0
[47] DBI_1.2.3 highr_0.11
[49] gplots_3.1.3.1 MASS_7.3-61
[51] DelayedArray_0.31.1 corpcor_1.6.10
[53] gtools_3.9.5 caTools_1.18.2
[55] tools_4.4.0 remaCor_0.0.18
[57] glue_1.7.0 nlme_3.1-165
[59] grid_4.4.0 reshape2_1.4.4
[61] generics_0.1.3 snow_0.4-4
[63] gtable_0.3.5 tzdb_0.4.0
[65] tidyr_1.3.1 hms_1.1.3
[67] utf8_1.2.4 XVector_0.45.0
[69] pillar_1.9.0 stringr_1.5.1
[71] babelgene_22.9 vroom_1.6.5
[73] splines_4.4.0 dplyr_1.1.4
[75] BiocFileCache_2.13.0 lattice_0.22-6
[77] bit_4.0.5 tidyselect_1.2.1
[79] locfit_1.5-9.9 Biostrings_2.73.1
[81] SummarizedExperiment_1.35.0 RhpcBLASctl_0.23-42
[83] xfun_0.44 statmod_1.5.0
[85] matrixStats_1.3.0 KEGGgraph_1.65.0
[87] stringi_1.8.4 UCSC.utils_1.1.0
[89] yaml_2.3.8 boot_1.3-30
[91] evaluate_0.24.0 codetools_0.2-20
[93] archive_1.1.8 tibble_3.2.1
[95] Rgraphviz_2.49.0 cli_3.6.2
[97] RcppParallel_5.1.7 xtable_1.8-4
[99] Rdpack_2.6 munsell_0.5.1
[101] jquerylib_0.1.4 Rcpp_1.0.12
[103] GenomeInfoDb_1.41.1 EnvStats_2.8.1
[105] dbplyr_2.5.0 png_0.1-8
[107] Rfast_2.1.0 parallel_4.4.0
[109] blob_1.2.4 prettyunits_1.2.0
[111] bitops_1.0-7 mvtnorm_1.2-5
[113] lmerTest_3.1-3 scales_1.3.0
[115] purrr_1.0.2 crayon_1.5.2
[117] fANCOVA_0.6-1 rlang_1.1.4
[119] EnrichmentBrowser_2.35.1 KEGGREST_1.45.0
```