Define priors for specific parameters or classes of parameters.
set_prior( prior, class = "b", coef = "", group = "", resp = "", dpar = "", nlpar = "", lb = NA, ub = NA, check = TRUE ) prior(prior, ...) prior_(prior, ...) prior_string(prior, ...) empty_prior()
A character string defining a distribution in Stan language
The parameter class. Defaults to
Name of the coefficient within the parameter class.
Grouping factor for group-level parameters.
Name of the response variable. Only used in multivariate models.
Name of a distributional parameter. Only used in distributional models.
Name of a non-linear parameter. Only used in non-linear models.
Lower bound for parameter restriction. Currently only allowed
Upper bound for parameter restriction. Currently only allowed
Logical; Indicates whether priors
should be checked for validity (as far as possible).
Arguments passed to
set_prior is used to define prior distributions for parameters
in brms models. The functions
prior_string are aliases of
set_prior each allowing
for a different kind of argument specification.
prior allows specifying arguments as expression without
quotation marks using non-standard evaluation.
prior_ allows specifying arguments as one-sided formulas
or wrapped in
prior_string allows specifying arguments as strings just
Below, we explain its usage and list some common prior distributions for parameters. A complete overview on possible prior distributions is given in the Stan Reference Manual available at https://mc-stan.org/.
To combine multiple priors, use
c(...) or the
(see 'Examples'). brms does not check if the priors are written
in correct Stan language. Instead, Stan will check their
syntactical correctness when the model is parsed to
returns an error if they are not.
This, however, does not imply that priors are always meaningful if they are
accepted by Stan. Although brms trys to find common problems
(e.g., setting bounded priors on unbounded parameters), there is no guarantee
that the defined priors are reasonable for the model.
Below, we list the types of parameters in brms models,
for which the user can specify prior distributions.
1. Population-level ('fixed') effects
Every Population-level effect has its own regression parameter
represents the name of the corresponding population-level effect.
Suppose, for instance, that
y is predicted by
y ~ x1 + x2 in formula syntax).
x2 have regression parameters
The default prior for population-level effects (including monotonic and
category specific effects) is an improper flat prior over the reals.
Other common options are normal priors or student-t priors.
If we want to have a normal prior with mean 0 and
standard deviation 5 for
x1, and a unit student-t prior with 10
degrees of freedom for
x2, we can specify this via
set_prior("normal(0,5)", class = "b", coef = "x1") and
set_prior("student_t(10, 0, 1)", class = "b", coef = "x2").
To put the same prior on all population-level effects at once,
we may write as a shortcut
set_prior("<prior>", class = "b").
This also leads to faster sampling, because priors can be vectorized in this case.
Both ways of defining priors can be combined using for instance
set_prior("normal(0, 2)", class = "b") and
set_prior("normal(0, 10)", class = "b", coef = "x1")
at the same time. This will set a
normal(0, 10) prior on
the effect of
x1 and a
normal(0, 2) prior
on all other population-level effects.
However, this will break vectorization and
may slow down the sampling procedure a bit.
In case of the default intercept parameterization
(discussed in the 'Details' section of
general priors on class
"b" will not affect
the intercept. Instead, the intercept has its own parameter class
"Intercept" and priors can thus be
set_prior("<prior>", class = "Intercept").
Setting a prior on the intercept will not break vectorization
of the other population-level effects.
Note that technically, this prior is set on an intercept that
results when internally centering all population-level predictors
around zero to improve sampling efficiency. On this centered
intercept, specifying a prior is actually much easier and
intuitive than on the original intercept, since the former
represents the expected response value when all predictors
are at their means. To treat the intercept as an ordinary
population-level effect and avoid the centering parameterization,
0 + Intercept on the right-hand side of the model formula.
A special shrinkage prior to be applied on population-level effects is the
(regularized) horseshoe prior and related priors. See
horseshoe for details. Another shrinkage prior is the
so-called lasso prior. See
lasso for details.
In non-linear models, population-level effects are defined separately
for each non-linear parameter. Accordingly, it is necessary to specify
the non-linear parameter in
set_prior so that priors
we can be assigned correctly.
If, for instance,
alpha is the parameter and
x the predictor
for which we want to define the prior, we can write
set_prior("<prior>", coef = "x", nlpar = "alpha").
As a shortcut we can use
set_prior("<prior>", nlpar = "alpha")
to set the same prior on all population-level effects of
alpha at once.
If desired, population-level effects can be restricted to fall only
within a certain interval using the
set_prior. This is often required when defining priors
that are not defined everywhere on the real line, such as uniform
or gamma priors. When defining a
you should write
set_prior("uniform(2,4)", lb = 2, ub = 4).
When using a prior that is defined on the positive reals only
(such as a gamma prior) set
lb = 0.
In most situations, it is not useful to restrict population-level
parameters through bounded priors
(non-linear models are an important exception),
but if you really want to this is the way to go.
2. Standard deviations of group-level ('random') effects
Each group-level effect of each grouping factor has a standard deviation named
sd_<group>_<coef>. Consider, for instance, the formula
y ~ x1 + x2 + (1 + x1 | g).
We see that the intercept as well as
x1 are group-level effects
nested in the grouping factor
The corresponding standard deviation parameters are named as
These parameters are restricted to be non-negative and, by default,
have a half student-t prior with 3 degrees of freedom and a
scale parameter that depends on the standard deviation of the response
after applying the link function. Minimally, the scale parameter is 2.5.
This prior is used (a) to be only weakly informative in order to influence
results as few as possible, while (b) providing at least some regularization
to considerably improve convergence and sampling efficiency.
To define a prior distribution only for standard deviations
of a specific grouping factor,
set_prior("<prior>", class = "sd", group = "<group>").
To define a prior distribution only for a specific standard deviation
of a specific grouping factor, you may write
set_prior("<prior>", class = "sd", group = "<group>", coef = "<coef>").
Recommendations on useful prior distributions for
standard deviations are given in Gelman (2006), but note that he
is no longer recommending uniform priors, anymore.
When defining priors on group-level parameters in non-linear models,
please make sure to specify the corresponding non-linear parameter
nlpar argument in the same way as
for population-level effects.
3. Correlations of group-level ('random') effects
If there is more than one group-level effect per grouping factor,
the correlations between those effects have to be estimated.
lkj_corr_cholesky(eta) or in short
eta > 0
is essentially the only prior for (Cholesky factors) of correlation matrices.
eta = 1 (the default) all correlations matrices
are equally likely a priori. If
eta > 1, extreme correlations
become less likely, whereas
0 < eta < 1 results in
higher probabilities for extreme correlations.
Correlation matrix parameters in
brms models are named as
g is the grouping factor).
To set the same prior on every correlation matrix,
use for instance
set_prior("lkj(2)", class = "cor").
Internally, the priors are transformed to be put on the Cholesky factors
of the correlation matrices to improve efficiency and numerical stability.
The corresponding parameter class of the Cholesky factors is
but it is not recommended to specify priors for this parameter class directly.
Splines are implemented in brms using the 'random effects'
formulation as explained in
Thus, each spline has its corresponding standard deviations
modeling the variability within this term. In brms, this
parameter class is called
sds and priors can
be specified via
set_prior("<prior>", class = "sds",
coef = "<term label>"). The default prior is the same as
for standard deviations of group-level effects.
5. Gaussian processes
Gaussian processes as currently implemented in brms have
two parameters, the standard deviation parameter
and characteristic length-scale parameter
gp for more details). The default prior
sdgp is the same as for standard deviations of
group-level effects. The default prior of
is an informative inverse-gamma prior specifically tuned
to the covariates of the Gaussian process (for more details see
This tuned prior may be overly informative in some cases, so please
consider other priors as well to make sure inference is
robust to the prior specification. If tuning fails, a half-normal prior
is used instead.
6. Autocorrelation parameters
The autocorrelation parameters currently implemented are named
ma (moving average),
deviation of latent residuals in latent ARMA models),
car (spatial conditional autoregression), as
errorsar (spatial simultaneous
Priors can be defined by
set_prior("<prior>", class = "ar") for
ar and similar for other autocorrelation parameters. By default,
ma are bounded between
errorsar are bounded
1. The default priors are flat over the
respective definition areas.
7. Distance parameters of monotonic effects
As explained in the details section of
monotonic effects make use of a special parameter vector to
estimate the 'normalized distances' between consecutive predictor
categories. This is realized in Stan using the
parameter type. This class is named
"simo" (short for
simplex monotonic) in brms.
The only valid prior for simplex parameters is the
dirichlet prior, which accepts a vector of length
K - 1
(K = number of predictor categories) as input defining the
'concentration' of the distribution. Explaining the dirichlet prior
is beyond the scope of this documentation, but we want to describe
how to define this prior syntactically correct.
If a predictor
K categories is modeled as monotonic,
we can define a prior on its corresponding simplex via
prior(dirichlet(<vector>), class = simo, coef = mox1).
1 in the end of
coef indicates that this is the first
simplex in this term. If interactions between multiple monotonic
variables are modeled, multiple simplexes per term are required.
<vector>, we can put in any
defining a vector of length
K - 1. The default is a uniform
<vector> = rep(1, K-1)) over all simplexes
of the respective dimension.
8. Parameters for specific families
Some families need additional parameters to be estimated.
gen_extreme_value need the parameter
sigma to account for the residual standard deviation.
sigma has a half student-t prior that scales
in the same way as the group-level standard deviations.
student needs the parameter
nu representing the degrees of freedom of students-t distribution.
nu has prior
and a fixed lower bound of
negbinomial need a
shape parameter that has a
gamma(0.01, 0.01) prior by default.
acat, and only if
threshold = "equidistant",
delta is used to model the distance between
two adjacent thresholds.
delta has an improper flat prior over the reals.
von_mises family needs the parameter
the concentration parameter. By default,
kappa has prior
Every family specific parameter has its own prior class, so that
set_prior("<prior>", class = "<parameter>") is the right way to go.
All of these priors are chosen to be weakly informative,
having only minimal influence on the estimations,
while improving convergence and sampling efficiency.
Fixing parameters to constants is possible by using the
function, for example,
constant(1) to fix a parameter to 1.
Broadcasting to vectors and matrices is done automatically.
Often, it may not be immediately clear, which parameters are present in the
model. To get a full list of parameters and parameter classes for which
priors can be specified (depending on the model) use function
An object of class
brmsprior to be used in the
prior: Alias of
set_prior allowing to
specify arguments as expressions without quotation marks.
prior_: Alias of
set_prior allowing to specify
arguments as as one-sided formulas or wrapped in
prior_string: Alias of
set_prior allowing to
specify arguments as strings.
empty_prior: Create an empty
Gelman A. (2006). Prior distributions for variance parameters in hierarchical models. Bayesian analysis, 1(3), 515 – 534.
## use alias functions (prior1 <- prior(cauchy(0, 1), class = sd)) (prior2 <- prior_(~cauchy(0, 1), class = ~sd)) (prior3 <- prior_string("cauchy(0, 1)", class = "sd")) identical(prior1, prior2) identical(prior1, prior3) # check which parameters can have priors get_prior(rating ~ treat + period + carry + (1|subject), data = inhaler, family = cumulative()) # define some priors bprior <- c(prior_string("normal(0,10)", class = "b"), prior(normal(1,2), class = b, coef = treat), prior_(~cauchy(0,2), class = ~sd, group = ~subject, coef = ~Intercept)) # verify that the priors indeed found their way into Stan's model code make_stancode(rating ~ treat + period + carry + (1|subject), data = inhaler, family = cumulative(), prior = bprior) # use the horseshoe prior to model sparsity in regression coefficients make_stancode(count ~ zAge + zBase * Trt, data = epilepsy, family = poisson(), prior = set_prior("horseshoe(3)")) # fix certain priors to constants bprior <- prior(constant(1), class = "b") + prior(constant(2), class = "b", coef = "zBase") + prior(constant(0.5), class = "sd") make_stancode(count ~ zAge + zBase + (1 | patient), data = epilepsy, prior = bprior) # pass priors to Stan without checking prior <- prior_string("target += normal_lpdf(b | 0, 1)", check = FALSE) make_stancode(count ~ Trt, data = epilepsy, prior = prior)
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.