Monitoring disturbances in time series models (with trend/season/regressor terms) at the end of time series (i.e., in near realtime). Based on a model for stable historical behaviour abnormal changes within newly acquired data can be detected. Different models are available for modeling the stable historical behavior. A seasontrend model (with harmonic seasonal pattern) is used as a default in the regresssion modelling.
1 2 3 4 5 
data 
A time series of class 
start 
numeric. The starting date of the monitoring period. Can either be
given as a float (e.g., 
formula 
formula for the regression model. The default is

order 
numeric. Order of the harmonic term, defaulting to 
lag 
numeric. Order of the autoregressive term, by default omitted. 
slag 
numeric. Order of the seasonal autoregressive term, by default omitted. 
history 
specification of the start of the stable history period. Can either
be a character, numeric, or a function. If character, then selection is possible
between reverseordered CUSUM ( 
type 
character specifying the type of monitoring process. By default, a MOSUM
process based on OLS residuals is employed. See 
h 
numeric scalar from interval (0,1) specifying the bandwidth relative to the sample size in MOSUM/ME monitoring processes. 
end 
numeric. Maximum time (relative to the history period) that will be monitored (in MOSUM/ME processes). Default is 10 times the history period. 
level 
numeric. Significance level of the monitoring (and ROC, if selected) procedure, i.e., probability of type I error. 
hpc 
character specifying the high performance computing support. Default is

verbose 
logical. Should information about the monitoring be printed during computation? 
plot 
logical. Should the result be plotted? 
bfastmonitor
provides monitoring of disturbances (or structural changes) in near
realtime based on a wide class of time series regression models with optional
season/trend/autoregressive/covariate terms. See Verbesselt at al. (2011) for details.
Based on a given time series (typically, but not necessarily, with frequency greater than 1),
the data is first preprocessed for regression modeling. Trend/season/autoregressive/covariate
terms are (optionally) computed using bfastpp
. Second, the data
is split into a history and monitoring period (starting with start
). Third, a subset
of the history period is determined which is considered to be stable (see also below).
Fourth, a regression model is fitted to the preprocessed data in the stable history period.
Fifth, a monitoring procedure is used to determine whether the observations in the monitoring
period conform with this stable regression model or whether a change is detected.
The regression model can be specified by the user. The default is to use a linear trend and
a harmonic season: response ~ trend + harmon
. However, all other terms set up by
bfastpp
can also be omitted/added, e.g., response ~ 1
(just a constant),
response ~ season
(seasonal dummies for each period), etc. Further terms precomputed
by bfastpp
can be lag
(autoregressive terms of specified order), slag
(seasonal autoregressive terms of specified order), xreg
(covariates, if data
has more than one column).
For determining the size of the stable history period, various approaches are available. First, the user can set a start date based on subjectmatter knowledge. Second, datadriven methods can be employed. By default, this is a reverseordered CUSUM test (ROC). Alternatively, breakpoints can be estimated (Bai and Perron method) and only the data after the last breakpoint are employed for the stable history. Finally, the user can also supply a function for his/her own datadriven method.
bfastmonitor
returns an object of class "bfastmonitor"
, i.e., a list with components as follows.
data 
original 
tspp 
preprocessed 
model 
fitted 
mefp 
fitted 
history 
start and end time of history period, 
monitor 
start and end time of monitoring period, 
breakpoint 
breakpoint detected (if any). 
magnitude 
median of the difference between the data and the model prediction in the monitoring period. 
Achim Zeileis, Jan Verbesselt
Verbesselt J, Zeileis A, Herold M (2012). Near realtime disturbance detection using satellite image time series. Remote Sensing Of Environment, 123, 98–108. http://dx.doi.org/10.1016/j.rse.2012.02.022
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86  ## See Fig. 6 a and b in Verbesselt et al. (2011)
## for more information about the data time series and acknowledgements
library(zoo)
NDVIa < as.ts(zoo(som$NDVI.a, som$Time))
plot(NDVIa)
## apply the bfast monitor function on the data
## start of the monitoring period is c(2010, 13)
## and the ROC method is used as a method to automatically identify a stable history
mona < bfastmonitor(NDVIa, start = c(2010, 13))
mona
plot(mona)
## fitted seasontrend model in history period
summary(mona$model)
## OLSbased MOSUM monitoring process
plot(mona$mefp, functional = NULL)
## the pattern in the running mean of residuals
## this illustrates the empirical fluctuation process
## and the significance of the detected break.
NDVIb < as.ts(zoo(som$NDVI.b, som$Time))
plot(NDVIb)
monb < bfastmonitor(NDVIb, start = c(2010, 13))
monb
plot(monb)
summary(monb$model)
plot(monb$mefp, functional = NULL)
## set the stable history period manually and use a 4th order harmonic model
bfastmonitor(NDVIb, start = c(2010, 13),
history = c(2008, 7), order = 4, plot = TRUE)
## just use a 6th order harmonic model without trend
mon < bfastmonitor(NDVIb, formula = response ~ harmon,
start = c(2010, 13), order = 6, plot = TRUE)
summary(mon$model)
## For more info
?bfastmonitor
## TUTORIAL for processing raster bricks (satellite image time series of 16day NDVI images)
f < system.file("extdata/modisraster.grd", package="bfast")
library("raster")
modisbrick < brick(f)
data < as.vector(modisbrick[1])
ndvi < bfastts(data, dates, type = c("16day"))
plot(ndvi/10000)
## derive median NDVI of a NDVI raster brick
medianNDVI < calc(modisbrick, fun=function(x) median(x, na.rm = TRUE))
plot(medianNDVI)
## helper function to be used with the calc() function
xbfastmonitor < function(x,dates) {
ndvi < bfastts(x, dates, type = c("16day"))
ndvi < window(ndvi,end=c(2011,14))/10000
## delete end of the time to obtain a dataset similar to RSE paper (Verbesselt et al.,2012)
bfm < bfastmonitor(data = ndvi, start=c(2010,12), history = c("ROC"))
return(cbind(bfm$breakpoint, bfm$magnitude))
}
## apply on one pixel for testing
ndvi < bfastts(as.numeric(modisbrick[1])/10000, dates, type = c("16day"))
plot(ndvi)
bfm < bfastmonitor(data = ndvi, start=c(2010,12), history = c("ROC"))
bfm$magnitude
plot(bfm)
xbfastmonitor(modisbrick[1], dates) ## helper function applied on one pixel
## Not run:
## apply the bfastmonitor function onto a raster brick
library(raster)
timeofbreak < calc(modisbrick, fun=function(x){
res < t(apply(x, 1, xbfastmonitor, dates))
return(res)
})
plot(timeofbreak) ## time of break and magnitude of change
plot(timeofbreak,2) ## magnitude of change
## create a KMZ file and look at the output
KML(timeofbreak, "timeofbreak.kmz")
## End(Not run)

Questions? Problems? Suggestions? Tweet to @rdrrHQ or email at ian@mutexlabs.com.
Please suggest features or report bugs with the GitHub issue tracker.
All documentation is copyright its authors; we didn't write any of that.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.