The first step to handling errors is to quantify them. Make sure that
your data’s “dilution of precision” (DOP) and error columns import
correctly into ctmm. In the following wood turtle dataset,
we have some calibration data and a turtle track. Note that the
calibration data must be collected from the same model device as the
tracking data, and their data formatting bust be similar enough that the
same location classes are detected by as.telemetry.
library(ctmm)
data(turtle)
names(turtle[[1]]) # data are not yet calibrated, but HDOP and location class is present## [1] "t" "HDOP" "class" "x" "y"
## [1] "60s" "90s" "F231" "F403"
The uere command is used to estimate the RMS UERE
parameter(s) from calibration data. Do not use this command on animal
tracking data.
## , , horizontal
##
## low est high
## 2D 22.786528 29.598802 36.397467
## 3D 6.477391 6.946024 7.414237
For GPS data, the RMS UERE will typically be 10-15 meters. Here we
have two location classes, “2D” and “3D”, which for this device have
substantially different RMS UERE values. The UERE parameters can then be
assigned to a dataset with the uere()<- command.
## , , horizontal
##
## low est high
## 2D 22.786528 29.598802 36.397467
## 3D 6.477391 6.946024 7.414237
If you have Argos data, they will import with calibration already applied to the horizontal dimensions, but not the vertical dimension.
## [1] "gps" "argos"
## [1] "timestamp" "longitude" "latitude" "t" "COV.angle" "HDOP"
## [7] "COV.major" "COV.minor" "VAR.xy" "class" "z" "VDOP"
## [13] "x" "y" "COV.x.x" "COV.x.y" "COV.y.y"
Not all GPS devices provide reliable DOP values and sometimes it is
not obvious what error information will prove to be the most predictive.
Generally speaking, as.telemetry will attempt to import the
“best” column from among those that estimate error, DOP value, number of
satellites and fix type, including timed-out fixes (see the
timeout argument in help(as.telemetry)).
Researchers may want to import their data with different error
information, run uere.fit for each error model, and then
select among the candidate models. Here we do this by comparing the
turtle calibration data with and without HDOP values.
First, we consider whether or not the HDOP and location class information are informative.
t.noHDOP <- lapply(turtle,function(t){ t$HDOP <- NULL; t })
t.noclass <- lapply(turtle,function(t){ t$class <- NULL; t })
t.nothing <- lapply(turtle,function(t){ t$HDOP <- NULL; t$class <- NULL; t })In other cases, manipulation will need to be performed before
importing, so that as.telemetry can format the
telemetry object properly. Running uere.fit
now results in errors calibrated under the assumption of homoskedastic
errors.
UERE.noHDOP <- uere.fit(t.noHDOP[1:2])
UERE.noclass <- uere.fit(t.noclass[1:2])
UERE.nothing <- uere.fit(t.nothing[1:2])We can now apply model selection to the UERE model fits by summarizing them in a list.
## ΔAICc Z[red]²
## HDOP.class 0.0000 2.366617
## HDOP 286.5747 3.908826
## class 418.5174 3.696585
## homoskedastic 637.2580 4.681067
We can see that the combination of location class and HDOP values yield the best error model, both in terms of AICc and in terms of reduced Z squared. Reduced Z squared is a goodness-of-fit statistic akin to reduced chi squared, but designed for comparing error models.
We had two calibration datasets, so we can also see if there is any substantial difference between the two GPS tags. We do this by making a list of individual UERE objects to compare to the previous joint UERE model.
## ΔAICc Z[red]²
## joint 0.000000 2.366617
## individual 3.314758 2.367412
In this case, performance of the individualized and joint error models are comparable, and AICc selects the joint model.
Now we come to the task of identifying outliers. The
outlie function uses error information to estimate
straight-line speeds between sampled times and distances from the bulk
of the data.
High-speed segments are colored in blue, while distant locations are
colored in red. More emphasis is placed on the more extreme locations in
the outlie plot. Visually we can see at least one outlier
in the wood turtle data. The output of outlie also contains
the error-informed speed and distance estimates (in SI units) used to
generate the plot.
A sustained speed of 0.1 m/s is not biologically implausible for a wood turtle, but this location is highly suspicious, both in terms of speed and lack of proximity. After removing the outlier, we can check the data again.
BAD <- OUT$speed>0.08 # not appropriate for other species!
turtle[[3]] <- turtle[[3]][!BAD,]
outlie(turtle[[3]]) -> OUTDatasets may have multiple outliers. In pathological situations, there may be no clear separation between the normative data and the outliers. This necessitates a better error model, either by improving inadequate (or absent) HDOP estimates or by employing a heavier tailed error distribution (not yet supported).
If we were working with Argos data or high resolution GPS data on a small animal, then we can get a “nugget” effect in the variogram that looks like an initial discontinuity at short time lags.
The height of this initial discontinuity corresponds to the variance of uncorrelated location errors. The second plot is the kind of initial discontinuity one has with detector array data. The end of the (slope) discontinuity is highlighted with a circle. This discontinuity is smooth because the movement and detection are correlated. The height of this initial discontinuity is also (at least roughly) the variance of the location errors.
Because of some convenient mathematical relations, fitting with
telemetry errors involves numerically fitting 1-4 more parameters and
is, therefore, slower and less reliable at converging on the MLE than
fitting without telemetry error. Therefore, by default, telemetry error
is not turned on in ctmm models (error=FALSE).
Furthermore, in cases with an error model, ctmm.select() is
safer to use than direct applicaiton of ctmm.fit(), because
ctmm.select() will start with the simplest “compatible”
model and then consider further model features that require numerical
optimization in stepwise fashion.
For calibrated errors, we have to set error=TRUE in the
model guess to fit with telemetry error accounted for.
# automated guesstimate for calibrated data
GUESS <- ctmm.guess(turtle[[3]],CTMM=ctmm(error=TRUE),interactive=FALSE)
# stepwise fitting # CRAN policy limits us to 2 cores
FIT <- ctmm.select(turtle[[3]],GUESS,trace=TRUE,cores=2)## * Fitting model OUF error
## * Fitting model OUF anisotropic error
## * Fitting model IID anisotropic error
## $name
## [1] "OU anisotropic error"
##
## $DOF
## mean area diffusion speed
## 13.90248 23.94114 194.84094 0.00000
##
## $CI
## low est high
## area (hectares) 13.619552 21.269611 30.597464
## τ[position] (days) 3.561602 5.684257 9.071979
## diffusion (square meters/day) 4663.866568 5394.813573 6178.191288
## error 2D (meters) 18.539405 21.885536 25.225761
## error 3D (meters) 6.590229 7.063690 7.536729
trace=TRUE allows us to see the models considered.
verbose=TRUE would save each model. Since we started with a
finite amount of calibration data, the location-error parameter
estimates were updated by the tracking data, and we can compare the
results here with the previous estimates in
summary(UERE).
Fitting with unknown errors is a method of last resort. We have to
provide an initial guess for error, which will be the
device’s RMS UERE. error=10 is usually a good guess for GPS
data (other than e-obs). Unlike uere.fit,
ctmm.fit is not yet coded to use the location classes, as
simultaneous fitting is a method of last resort that becomes
increasingly dangerous with more location classes.
The only difference is that you have to provide an initial guess for the RMS UERE. Otherwise, the steps are the same.
# automated guesstimate for uncalibrated data (with 10 meter RMS UERE guess)
GUESS <- ctmm.guess(turtle[[3]],CTMM=ctmm(error=10),interactive=FALSE)
# fit and select models # CRAN policy limits us to 2 cores
FIT <- ctmm.select(turtle[[3]],GUESS,trace=TRUE,cores=2)## * Fitting model OUF error
## * Fitting model OUF anisotropic error
## * Fitting model IID anisotropic error
## $name
## [1] "OU anisotropic error"
##
## $DOF
## mean area diffusion speed
## 12.85422 21.90135 140.47113 0.00000
##
## $CI
## low est high
## area (hectares) 13.034832 20.823800 30.40787
## τ[position] (days) 3.734221 6.186522 10.24927
## diffusion (square meters/day) 4229.452765 5026.247775 5890.78884
## error 2D (meters) 7.750801 10.815998 13.87603
## error 3D (meters) 6.940389 8.749023 10.55404
Here, fitting the RMS UERE simultaneously with the movement model produced a largely consistent result. This will not always be the case.
An alternative method of last resort is to simply assign a range of credible RMS UERE values to the data. Again, 10-meter error is usually a good guess for 3D GPS data. For e-obs, and other devices that report error in meters, a number on the order of 1 is usually more relevant.
## , , horizontal
##
## low est high
## 2D 0 1 Inf
## 3D 0 1 Inf
# assign 20-meter 2D RMS UERE and 10-meter 3D RMS UERE
uere(turtle) <- c(20,10)
# for one location class, the above would likely be unnecessary, but would look like
# uere(turtle) <- 10
# the default uncertainty is none for numerical assignments
UERE <- uere(turtle)
summary(UERE)## , , horizontal
##
## low est high
## 2D 20 20 20
## 3D 10 10 10
## horizontal
## 2D Inf
## 3D Inf
# here I set the DOF to a smaller value
UERE$DOF[] <- 2
# which now gives plausible credible intervals
summary(UERE)## , , horizontal
##
## low est high
## 2D 6.960018 20 33.38156
## 3D 3.480009 10 16.69078
# assign the prior to the data
uere(turtle) <- UERE
# automated guesstimate for calibrated data
GUESS <- ctmm.guess(turtle[[3]],CTMM=ctmm(error=TRUE),interactive=FALSE)
# stepwise fitting # CRAN policy limits us to 2 cores
FIT <- ctmm.select(turtle[[3]],GUESS,trace=TRUE,cores=2)## * Fitting model OUF error
## * Fitting model OUF anisotropic error
## * Fitting model IID anisotropic error
## $name
## [1] "OU anisotropic error"
##
## $DOF
## mean area diffusion speed
## 12.70944 21.64700 143.50516 0.00000
##
## $CI
## low est high
## area (hectares) 12.966264 20.777972 30.40180
## τ[position] (days) 3.773824 6.262931 10.39378
## diffusion (square meters/day) 4197.637193 4978.901444 5825.85549
## error 2D (meters) 9.462808 12.388810 15.30900
## error 3D (meters) 7.186895 8.889036 10.58783
This method is still being developed and so this material is subject to change.