ubms
is an R package for fitting models of wildlife
occurrence and abundance to with datasets where animals are not
individually marked. It provides a nearly identical interface to the
popular unmarked
package (Fiske, Chandler, and others 2011).
Instead of using maximum likelihood to fit models (as with
unmarked
), models are fit in a Bayesian framework using Stan (Carpenter et al. 2017). It is
generally expected that you are already familiar with
unmarked
when using ubms
. You can download
ubms
, report issues, or help with development on Github.
There are several advantages to using ubms
over
unmarked
. First, it is possible to include random effects
in ubms
models, which is not currently possible in
unmarked
. These are specified using the familiar syntax of
lme4 (Bates et al.
2015). Second, ubms
generates posterior
distributions for model parameters, including latent occupancy and
abundance parameters. These can be useful for post-hoc analyses and
diagnostics. Finally, fitting models with Stan gives you access to the
large ecosystem of Stan-related tools, such as LOO
(leave-one-out-cross validation; (Vehtari, Gelman, and Gabry
2017)).
Another alternative to ubms
would be to fit models in an
existing modeling language such as BUGS, JAGS, or directly in Stan.
ubms
abstracts away the complex process of defining and
writing custom models in these languages which need to be updated each
time you make changes to your model. It also provides many useful helper
functions (e.g. predict
) which would otherwise require
custom code. Finally, because of Stan’s efficient sampler (Hoffman and Gelman
2014) and because the underlying likelihoods in
ubms
are marginalized, ubms
will often fit
models much faster than equivalent models in BUGS or JAGS (Yackulic et al.
2020).
Relative to unmarked
, ubms
has fewer types
of models available. For example, models that incorporate temporary
emigration (like gdistsamp
) (Chandler, Royle, and King 2011) are
currently not available in ubms
. Models should run much
faster in unmarked
as well. If you do not need one of the
specific benefits of ubms
described above, it makes sense
to stick with unmarked
. Even if you do plan to use
ubms
, it makes sense to test the models in
unmarked
first. The similar interface between the two
packages makes this very easy, as you will see in the next section.
Relative to BUGS/JAGS/Stan, ubms
is less flexible
because you cannot customize your model structure. You are limited to
the provided model types. Furthermore, you cannot currently customize
prior distributions (although I plan to add this in the future in some
form). Finally, writing your own BUGS/JAGS model can be valuable for
gaining a deeper understanding of how a model works; ubms
,
like unmarked
, is essentially a black box.
To summarize the advantages and disadvantages: I see
ubms
as an intermediate step along the continuum from
unmarked
to custom models in BUGS/JAGS. It is not meant to
replace either approach but rather to supplement them, for situations
when a Bayesian framework is needed and “off-the-shelf” model structures
are adequate.
Occupancy models estimate the probability ψ that a species occupies a site, while accounting for detection probability p < 1 (MacKenzie et al. 2002). In order to estimate both p and ψ, repeated observations (detection/non-detection data) at each site are required.
First, load the dataset we’ll be using, which comes with
unmarked
:
The crossbill
dataset is a data.frame
with
many columns. It contains detection/non-detection data for the European
crossbill (Loxia curvirostra) in Switzerland (Schmid, Zbinden, and Keller
2004).
## [1] 267 58
## [1] "id" "ele" "forest" "surveys" "det991" "det992" "det993"
## [8] "det001" "det002" "det003" "det011" "det012" "det013" "det021"
## [15] "det022" "det023" "det031" "det032" "det033" "det041" "det042"
## [22] "det043" "det051" "det052" "det053" "det061" "det062" "det063"
## [29] "det071" "det072" "det073" "date991" "date992" "date993" "date001"
## [36] "date002" "date003" "date011" "date012" "date013" "date021" "date022"
## [43] "date023" "date031" "date032" "date033" "date041" "date042" "date043"
## [50] "date051" "date052" "date053" "date061" "date062" "date063" "date071"
## [57] "date072" "date073"
Check ?crossbill
for details about each column. The
first three columns id
, ele
, and
forest
are site covariates.
The following 27 columns beginning with det
are the
binary detection/non-detection data; 9 years with 3 observations per
year. For this example we want to fit a single-season occupancy model;
thus we will use only the first three columns (year 1) of
det
as our response variable y
.
## det991 det992 det993
## 1 0 0 0
## 2 0 0 0
## 3 NA NA NA
## 4 0 0 0
## 5 0 0 0
## 6 NA NA NA
Note that missing values are possible. The final 27 columns beginning
with date
are the Julian dates for each observation. As
with y
we want only the first three columns corresponding
to year 1.
Finally, we build our unmarkedFrame
object holding our
detection/non-detection data, site covariates, and observation
covariates. Since we will conduct a single-season occupancy analysis, we
need to use unmarkedFrameOccu
specifically. The resulting
unmarkedFrame
can be used by both unmarked
and
ubms
.
## Data frame representation of unmarkedFrame object.
## y.1 y.2 y.3 id ele forest date.1 date.2 date.3
## 1 0 0 0 1 450 3 34 59 65
## 2 0 0 0 2 450 21 17 33 65
## 3 NA NA NA 3 1050 32 NA NA NA
## 4 0 0 0 4 950 9 29 59 65
## 5 0 0 0 5 1150 35 24 45 65
## 6 NA NA NA 6 550 2 NA NA NA
## 7 0 0 0 7 750 6 26 54 74
## 8 0 0 0 8 650 60 23 43 71
## 9 0 0 0 9 550 5 21 36 56
## 10 0 0 0 10 550 13 37 62 75
First, we fit a null model (no covariates) in unmarked
using the occu
function. The occu
function
requires as input a double formula (for detection and occupancy,
respectively) along with our unmarkedFrame
.
##
## Call:
## occu(formula = ~1 ~ 1, data = umf)
##
## Occupancy:
## Estimate SE z P(>|z|)
## -0.546 0.218 -2.51 0.0121
##
## Detection:
## Estimate SE z P(>|z|)
## -0.594 0.208 -2.86 0.00426
##
## AIC: 511.2538
Next, we fit the same model in ubms
. The equivalent to
occu
in ubms
is stan_occu
.
Functions in ubms
generally use this stan_
prefix, based on the approach used in package rstanarm for
GLMs. We need to provide the same arguments to stan_occu
.
In addition, we will specify that we want 3 MCMC chains
(chains=3
), with 500 iterations per chain
(iter=500
) of which the first half will be warmup
iterations. It is beyond the scope of this vignette to discuss the
appropriate number or length of chains; see the
Stan user’s guide for more details. Generally 4 chains of 2000
iterations each is recommended (of which 1000 per chain are warmups).
Thus, 500 iterations per chain is probably not enough, but to keep
things running quickly it is sufficient for this vignette. Note that if
you are more familiar with BUGS or JAGS, Stan generally requires a
smaller number of iterations to reach convergence thanks to its default
NUTS sampler (Hoffman
and Gelman 2014). If you have a good multi-core CPU, you can
run chains in parallel. Tell Stan how many parallel cores you want to
use by assigning a value to the cores
argument.
##
## Call:
## stan_occu(formula = ~1 ~ 1, data = umf, chains = 3, iter = 500,
## refresh = 0, seed = 123)
##
## Occupancy (logit-scale):
## Estimate SD 2.5% 97.5% n_eff Rhat
## -0.483 0.234 -0.882 0.00981 236 1
##
## Detection (logit-scale):
## Estimate SD 2.5% 97.5% n_eff Rhat
## -0.642 0.226 -1.11 -0.229 285 1
##
## LOOIC: 511.954
## Runtime: 1.202 sec
The structure of the output from unmarked
and
ubms
is intentionally similar. Estimates of the occupancy
and detection parameters are also similar, but not identical. For a more
direct comparison, call the coef
function on both model
objects:
## unmarked stan
## psi(Int) -0.5461203 -0.4834253
## p(Int) -0.5939612 -0.6419488
Let’s look at the output from our fit_stan
model
again:
##
## Call:
## stan_occu(formula = ~1 ~ 1, data = umf, chains = 3, iter = 500,
## refresh = 0, seed = 123)
##
## Occupancy (logit-scale):
## Estimate SD 2.5% 97.5% n_eff Rhat
## -0.483 0.234 -0.882 0.00981 236 1
##
## Detection (logit-scale):
## Estimate SD 2.5% 97.5% n_eff Rhat
## -0.642 0.226 -1.11 -0.229 285 1
##
## LOOIC: 511.954
## Runtime: 1.202 sec
The first part (under Call:
) is the command we used to
get this model output. Underneath are two tables, one per submodel,
corresponding to the occupancy and detection parts of the model. Within
each table there is one row per parameter in the submodel. Since
fit_stan
had no covariates, there is only an intercept term
for each submodel. Model parameters in this summary table are always
shown on the appropriate transformed scale, in this case logit. To get
the corresponding probabilities, you can use the predict
function, which we will demonstrate later.
For each parameter, the mean and standard deviation of the posterior
distribution are given. Unlike unmarked
output, there is no
Z or p-value. Instead, there is a 95%
uncertainty interval provided.
The final two columns in each summary table n_eff
and
Rhat
are MCMC diagnostics. We will discuss their meaning
later.
To extract summary values into an R table for easy manipulation, use
the summary
method. Note that you have to specify which
submodel you want ("state"
for occupancy or
"det"
for detection).
## [1] -0.4834253
To extract the entire posterior for a parameter, use the
extract
method. To avoid name collisions you need to use
the full name of the parameter (which contains both the submodel and the
parameter name) when extracting. To see a list of the available full
parameter names, use the names
method.
## [1] "beta_state[(Intercept)]" "beta_det[(Intercept)]"
Now we’ll fit two candidate models to the crossbill
data
in ubms
and compare them.
Along with our previous null model, we’ll fit a “global” model with
both site and observation covariates. This is just an example; perhaps
other models should also be considered if we were preparing this
analysis for publication. In our model formulas, we have normalized all
covariates with scale
so they have a mean of 0 and a
standard deviation of 1. This can help improve model convergence and is
generally a good idea.
fit_null <- fit_stan
fit_global <- stan_occu(~scale(date)~scale(forest)+scale(ele), data=umf,
chains=3, iter=500, seed=123)
## Warning: Bulk Effective Samples Size (ESS) is too low, indicating posterior means and medians may be unreliable.
## Running the chains for more iterations may help. See
## https://mc-stan.org/misc/warnings.html#bulk-ess
## Warning: Tail Effective Samples Size (ESS) is too low, indicating posterior variances and tail quantiles may be unreliable.
## Running the chains for more iterations may help. See
## https://mc-stan.org/misc/warnings.html#tail-ess
The fit_global
model gave us some warnings about the
effective sample size (n_eff
) along with a suggested
solution. We will ignore this warning for now but normally it is a good
idea to pay close attention to these warnings.
First we combine the models into a fitList
:
Then we generate a model selection table:
## elpd nparam elpd_diff se_diff
## fit_global -236.776 5.984 0.000 0.000
## fit_null -255.977 2.524 -19.201 6.618
Instead of AIC, models are compared using leave-one-out
cross-validation (LOO) (Vehtari, Gelman, and Gabry 2017) via
the loo
package. Based on this cross-validation, the
expected predictive accuracy (elpd
) for each model is
calculated. The model with the largest elpd
(fit_global
) performed best. The elpd_diff
column shows the difference in elpd
between a model and the
top model; if this difference is several times larger than the standard
error of the difference (se_diff
), we are confident the
model with the larger elpd
performed better. LOO model
weights, analogous to AIC weights, are also calculated. We can see that
the fit_global
model is clearly the best performing
model.
You can obtain LOO information for a single model using the
loo
method:
##
## Computed from 750 by 245 log-likelihood matrix.
##
## Estimate SE
## elpd_loo -236.8 19.2
## p_loo 6.0 0.6
## looic 473.6 38.5
## ------
## MCSE of elpd_loo is 0.1.
## MCSE and ESS estimates assume MCMC draws (r_eff in [0.3, 1.5]).
##
## All Pareto k estimates are good (k < 0.65).
## See help('pareto-k-diagnostic') for details.
The looic
value is analogous to AIC.
You can also obtain the WAIC (Widely Applicable Information Criterion) if you prefer (Vehtari, Gelman, and Gabry 2017):
##
## Computed from 750 by 245 log-likelihood matrix.
##
## Estimate SE
## elpd_waic -236.7 19.2
## p_waic 5.9 0.6
## waic 473.5 38.5
We’ll define the global model as our top model:
##
## Call:
## stan_occu(formula = ~scale(date) ~ scale(forest) + scale(ele),
## data = umf, chains = 3, iter = 500, refresh = 0, seed = 123)
##
## Occupancy (logit-scale):
## Estimate SD 2.5% 97.5% n_eff Rhat
## (Intercept) -0.603 0.359 -1.1896 0.293 208 1.01
## scale(forest) 1.077 0.325 0.5595 1.925 211 1.01
## scale(ele) 0.566 0.245 0.0924 1.054 533 1.00
##
## Detection (logit-scale):
## Estimate SD 2.5% 97.5% n_eff Rhat
## (Intercept) -0.754 0.253 -1.290 -0.316 300 1.01
## scale(date) 0.558 0.170 0.233 0.883 1030 1.00
##
## LOOIC: 473.552
## Runtime: 1.746 sec
Again looking at the summary of fit_top
, we conclude
MCMC chains have converged if all R̂ > 1.05. To visualize
convergence, look at the traceplots:
The traceplots look a little messy. We may also get a warning that
n_eff
is lacking for some parameters. The rule of thumb is
to have n_eff
> 100 * number of chains (300). The easy
solution to both problems would be to re-run this model with more
iterations.
Calculating residuals is tricky for occupancy models. There isn’t one
widely accepted way of doing it. ubms
implements the
approach of Wright (Wright, Irvine, and Higgs 2019) in
which residuals are calculated separately for the state and observation
processes. To quickly plot residuals against fitted values, use the
plot
method:
Note that the residuals are automatically binned, which is
appropriate for a binomial response (Gelman and Hill 2007). If the model
fits the data well, you would expect 95% of the binned residual points
to fall within the shaded area. You can also plot residuals against
covariate values using the plot_residuals
function:
ubms
also supports goodness-of-fit tests (posterior
predictive checks) for some models. In the case of occupancy models,
there is support for the MacKenzie-Bailey (M-B) chi-square test (MacKenzie and Bailey
2004) via the gof
function. For each posterior
draw, the M-B statistic is calculated for the actual data and for a
simulated dataset. The proportion of draws for which the simulated
statistic is larger than the actual statistic should be near 0.5 if the
model fits well.
## MacKenzie-Bailey Chi-square
## Point estimate = 26.884
## Posterior predictive p = 0.04
Our model does not appear to fit well based on this posterior predictive check. The first step to addressing this would be to run the model for more iterations to make sure that isn’t the reason.
You can use the posterior_predict
function to simulate
new datasets, which you can use to calculate your own fit statistic. The
following command generates 100 simulated datasets.
## [1] 100 801
The output is a matrix with dimensions draws x observations (in site-major order). As an example, we can calculate the proportion of zeros in each simulated dataset
and compare that to the proportion of zeros in the actual dataset.
Based on the 95% uncertainty intervals, both forest and elevation
have a positive effect on occupancy probability (both intervals do not
contain 0). Similarly, Julian date has a positive impact on detection
probability. We can quickly visualize these marginal covariate effects
with the plot_effects
function:
As with unmarked
, we can get the predicted psi or p for each site or observation using
the predict
function. For example, to get occupancy:
## Predicted SD 2.5% 97.5%
## 1 0.08475341 0.04074847 0.02603972 0.1870306
## 2 0.15341676 0.06590045 0.05564030 0.3312959
## 3 0.30784613 0.07968393 0.18695527 0.5197789
## 4 0.14593709 0.04629648 0.07153534 0.2537933
## 5 0.35156491 0.08389258 0.22562494 0.5726406
## 6 0.08783817 0.04008446 0.02912174 0.1868335
You can also supply newdata as a data.frame
.
## Predicted SD 2.5% 97.5%
## 1 0.1401127 0.07725292 0.03806715 0.3547347
One of the advantages of BUGS/JAGS is that you can directly model
latent parameters, such as the true unobserved occupancy state of a site
z. Using the
posterior_predict
function in ubms
, you can
generate an equivalent posterior distribution of z.
## [1] 100 267
The output has one row per posterior draw, and one column per site. The posterior of z can be useful for post-hoc analyses. For example, suppose you wanted to test for a difference in mean occupancy probability between sites 1-50 and sites 51-100:
group1 <- rowMeans(zpost[,1:50], na.rm=TRUE)
group2 <- rowMeans(zpost[,51:100], na.rm=TRUE)
plot_dat <- rbind(data.frame(group="group1", occ=mean(group1),
lower=quantile(group1, 0.025),
upper=quantile(group1, 0.975)),
data.frame(group="group2", occ=mean(group2),
lower=quantile(group2, 0.025),
upper=quantile(group2, 0.975)))
Now plot the posterior distributions of the two means:
library(ggplot2)
ggplot(plot_dat, aes(x=group, y=occ)) +
geom_errorbar(aes(ymin=lower, ymax=upper), width=0.2) +
geom_point(size=3) +
ylim(0,1) +
labs(x="Group", y="Occupancy + 95% UI") +
theme_bw() +
theme(panel.grid.major=element_blank(), panel.grid.minor=element_blank(),
axis.text=element_text(size=12), axis.title=element_text(size=14))