UWA logoMaterial to support teaching in Environmental Science at The University of Western Australia

Units ENVT3361, ENVT4461, and ENVT5503

This guide is organised into 3 main sections:

  1. Setting up R to analyse time series data, and the associated data formats;
  2. Understanding the concepts, components and features of time series data;
  3. Forecasting time series using basic trend analysis and more complex ARIMA (and other) models – the type of content we would include in reports.

 

 

Set up the R environment for time series analysis

We will need the additional functions in several R packages for specialized time series and other functions in R...

...you may need to install them. You can skip the if(!require(packageName)) if you know your computer already has them installed.

# Conditionally install packages if they don't exist on your computer...
if(!require(zoo)) install.packages("zoo")
if(!require(tseries)) install.packages("tseries")
if(!require(Kendall)) install.packages("Kendall")
if(!require(trend)) install.packages("trend")
if(!require(forecast)) install.packages("forecast")
if(!require(lmtest)) install.packages("lmtest")
if(!require(car)) install.packages("car")
if(!require(viridis)) install.packages("viridis")
if(!require(ggplot2)) install.packages("ggplot2")

# Load the packages we need 
library(zoo)      # for basic irregular time series functions
library(tseries)  # for assessing stationarity using Augmented Dickey-Fuller test
library(Kendall)  # for trend analysis with Mann-Kendall test
library(trend)    # for trend analysis using the Sen slope
library(forecast) # for time series forecasting with ARIMA and exponential smoothing 
library(lmtest)   # for Breusch-Pagan heteroscedasticity test etc.
library(car)      # for various commonly-used functions
library(viridis)  # accessible colour palettes e.g. viridis, plasma, ...
library(ggplot2)  # alternative to base R plots

# (optional) make a better colour palette than the R default!
# use viridis for palette accessible to colour vision impairment

# the palette below shows the colours we get when...
palette(c("black","#0D0887","#5302A3","#8A09A5","#B7318A",
  "#DA5B6A","#F3864A","#FEBA2C","darkgray","white"))
# ...we use a palette from the viridis package

palette(c("black",plasma(7, end=0.85),"darkgray","white"))
par(mfrow=c(3,1), mar=c(4,4,1,1), mgp=c(1.7,0.3,0), tcl=0.25, font.lab=2)

1. How R reads and stores time series data

We first read the data into a data frame – this is how R often stores data – it's not the format we need, but we'll use it for comparison.

The data used are derived from autumn 2014 soil meteorological observations at the Murrumbidgee M2 (Canberra Airport) site, available in the OzNet data archive, and described by Smith et al. (2012). We will use a curated subset of the soil temperature data at a single depth (15 cm).

Non-time series object for comparison

git <- "https://raw.githubusercontent.com/Ratey-AtUWA/Learn-R-web/main/"
soiltemp <- read.csv(paste0(git,"soiltemp2.csv"))
colnames(soiltemp) <- c("Date","temp") # simplify column names

 

Do some checks of the (non-time series) data

summary(soiltemp) # simple summary of each column
cat("\n") # separate output with a blank line
str(soiltemp) # more detailed information about the R object 
# ('str'=structure, i.e. how the data are organised in the R object)
##         Date           temp      
##  Length   :1464   Min.   :10.40  
##  N.unique :1464   1st Qu.:12.45  
##  N.blank  :   0   Median :14.30  
##  Min.nchar:  19   Mean   :14.86  
##  Max.nchar:  19   3rd Qu.:17.41  
##                   Max.   :21.70  
## 
## 'data.frame':    1464 obs. of  2 variables:
##  $ Date: chr  "2014-04-01 00:00:00" "2014-04-01 01:00:00" "2014-04-01 02:00:00" "2014-04-01 03:00:00" ...
##  $ temp: num  20.1 19.8 19.6 19.2 19 ...

 

We can also check the general form of the data with a plot (Figure 1). From this plot and from the text summary output above, we can see that the Date column is not a date or time, or even really numeric.

par(mar=c(3,3,1,1), mgp=c(1.6,0.3,0), tcl=0.2, font.lab=2)
with(soiltemp, plot(temp, type = "l", col = 2, xlab="Index (= row number)"))
Figure 1: Plot of soil temperature time series data which is not (yet) formatted as a time series.

Figure 1: Plot of soil temperature time series data which is not (yet) formatted as a time series.

 

Reading and storing data as time series

We really want the data in a different type of R object! We use the read.zoo() function from the zoo package to read the data in as a time series. This gives a data object of class zoo which is much more flexible than the default time series object in R.

We need to specify a format that our date/time information is stored as. The character string "%Y-%m-%d %H:%M:%S" looks unusual but it should make sense (%Y is 4-digit year, and so on). If we have opened and saved our .csv file in Excel, the format will probably change, so we should try format = "%d/%m/%Y %H:%M:%S". If in doubt, try to match the format in the initial data frame (soiltemp in this example).

soiltemp_zoo <- read.zoo(soiltemp,
                         format = "%Y-%m-%d %H:%M:%S", 
                         tz = "Australia/Perth", 
                         index.column=1,
                         header = TRUE)
# do some quick checks of the new R object:
summary(soiltemp_zoo) ; cat("\n")
str(soiltemp_zoo) # POSIXct in the output is a date-time format
##      Index                      soiltemp_zoo  
##  Min.   :2014-04-01 00:00:00   Min.   :10.40  
##  1st Qu.:2014-04-16 05:45:00   1st Qu.:12.45  
##  Median :2014-05-01 11:30:00   Median :14.30  
##  Mean   :2014-05-01 11:30:00   Mean   :14.86  
##  3rd Qu.:2014-05-16 17:15:00   3rd Qu.:17.41  
##  Max.   :2014-05-31 23:00:00   Max.   :21.70  
## 
## 'zoo' series from 2014-04-01 to 2014-05-31 23:00:00
##   Data: num [1:1464] 20.1 19.8 19.6 19.2 19 ...
##   Index:  POSIXct[1:1464], format: "2014-04-01 00:00:00" "2014-04-01 01:00:00" "2014-04-01 02:00:00" "2014-04-01 03:00:00" ...

We can see that the column Date has now become Index, and it's correctly stored as date/time information, in a format called POSIXct (for more information, run ?DateTimeClasses in the Console. Again, it's usually useful to check our data with a plot (Figure 2).

plot(soiltemp_zoo, col = 3)
Figure 2: Plot of soil temperature time series data which is formatted as a zoo time series object.

Figure 2: Plot of soil temperature time series data which is formatted as a zoo time series object.

 

Time Series Regularity

There's something else important we should check - regularity. A time series is regular if the time steps are all the same length, preferably with no missing observations. There are also irregular time series, with unequal time steps, but these can cause problems for some sorts of time series analysis (more on this here). Let's check:

soiltemp_diffs <- diff(index(soiltemp_zoo))
unique(soiltemp_diffs)
## Time difference of 1 hours
cat("Number of unique differences between observations =", length(unique(soiltemp_diffs)))
## Number of unique differences between observations = 1

There is 1 unique difference between observations, so our time series is regular.

With a regular series, we can even use the base-R time series format instead of the more flexible zoo format (bearing in mind that we will lose the exact time information, since the base-R time series objects are more limited):

soilT.ts <- ts(soiltemp$temp, frequency = 24, start=c(1,0))

 

2. Exploratory data analysis and decomposition of time series

This section is designed to help you understand the features and components of time series, and some of the statistical methods that we use to analyse them. We also look at time series decomposition. The important issues are:

  • Do we need to transform our time series variable?
  • Is our time series stationary?
  • Can we separate out a trend in our variable vs. time?
  • Is our time series seasonal (periodic) and, if so, what is the periodic frequency?
  • Is there significant autocorrelation in our data?
  • What is left unexplained after we isolate the trend and periodicity?

Not all of these would need to be presented in a Report, but it's useful for us to understand time series concepts. This is especially true for autocorrelation and moving averages, which both rely [at least partially] on past observations to estimate current observations. From there it follows that we may be able to use past observations to predict future observations – i.e., forecasting.

We first examine a plot of the data in our time series object (which we made above in Figure 2).

Plotting the time series variable (with time as the independent variable!) can give us some initial clues about the overall trend in the data (in Figure 2, a negative overall slope) and if there is any periodicity (there do seem to be regular increases and decreases in soil temperature).

We often want to inspect plots of both the raw data and using common transformations (Figure 3). We compare with transformed time series data – we may need to do this to meet later modelling assumptions.

First we change the default plotting parameters using par(...), then plot the object and some transformed versions (with custom axis labels).

plot(soiltemp_zoo, ylab = "Temperature (\u00B0C)",
     xlab = "Date", col = 2, lwd = 2, cex.lab = 1.4)

plot(log10(soiltemp_zoo), 
     ylab = expression(bold(paste(log[10],"(Temperature, \u00B0C)"))),
     xlab = "Date", col = 3, lwd = 2, cex.lab = 1.4)

pt0 <- powerTransform(coredata(soiltemp_zoo))
if(pt0$lambda<0) {
  plot(
    -1 * (soiltemp_zoo ^ pt0$roundlam), # use rounded power term
    ylab = "power-transf. (Temp., \u00B0C)",
    xlab = "Date",
    col = 4, lwd = 2, cex.lab = 1.4
  )
} else {
  plot((soiltemp_zoo ^ pt0$roundlam), # use rounded power term
       ylab = "power-transf. (Temp., \u00B0C)",
       xlab = "Date",
       col = 4, lwd = 2, cex.lab = 1.4
  )
}
Figure 3: Plots of soil temperature time series data as untransformed, log10-transformed, and power transformed values.

Figure 3: Plots of soil temperature time series data as untransformed, log10-transformed, and power transformed values.

 

💡 Which of these plots looks like it might be homoscedastic, i.e., have constant variance regardless of time?

The R Cookbook (Long and Teetor, 2019) suggests Box-Cox (power) transforming the variable to "stabilize the variance" (i.e. reduce heteroscedasticity). This does work, but can be better to use log10[variable], as the values are easier to interpret.

There are tests for homoscedasticity, usually based on the residuals from fitting a model (e.g. the Breusch-Pagan test). For our purposes visual assessment is enough.

If we think a transformation is needed, then run something like the code below (which does a square root transformation, i.e. variable0.5). This is just an example – we may, for example, decide that the log10-transformation is more suitable. If we save the results of powerTransform() to an object, it's most convenient to use the rounded power term (e.g. pt0$roundlam).

soiltemp_zoo <- soiltemp_zoo^0.5 #### ❗ don't run this chunk of code...

 

Assessing if a time series variable is stationary

A stationary variable's mean and variance are not dependent on time. In other words, for a stationary series, the mean and variance at any time are representative of the whole series.

If there is a trend for the value of the variable to increase or decrease, or if there are periodic fluctuations, we don't have a stationary time series.

Many useful statistical analyses and models for time series models need a stationary time series as input, or a time series that can be made stationary with transformations or differencing.

 

Testing for stationarity

# we need the package 'tseries' for the Augmented Dickey–Fuller (adf) Test
d0 <- adf.test(soiltemp_zoo); print(d0)
## 
##  Augmented Dickey-Fuller Test
## 
## data:  soiltemp_zoo
## Dickey-Fuller = -3.9515, Lag order = 11, p-value = 0.01141
## alternative hypothesis: stationary
d1 <- adf.test(diff(soiltemp_zoo,1)); print(d1)
## 
##  Augmented Dickey-Fuller Test
## 
## data:  diff(soiltemp_zoo, 1)
## Dickey-Fuller = -16.143, Lag order = 11, p-value = 0.01
## alternative hypothesis: stationary
d2 <- adf.test(diff(diff(soiltemp_zoo,1),1)); print(d2)
## 
##  Augmented Dickey-Fuller Test
## 
## data:  diff(diff(soiltemp_zoo, 1), 1)
## Dickey-Fuller = -17.204, Lag order = 11, p-value = 0.01
## alternative hypothesis: stationary

 

Plot differencing for stationarity

The plots in Figure 4 below show that constant mean and variance (i.e. stationarity) is achieved after a single differencing step. The adf.test p-value suggests that the non-differenced series is already stationary, but the shape of the first sub-plot in Figure 4 does not seem to support this.

par(mfrow = c(3,1), mar = c(0,4,0,1), oma = c(4,0,1,0), cex.lab = 1.4,
    mgp = c(2.5,0.7,0), font.lab = 2)
plot(soiltemp_zoo, ylab = "Raw data, no differencing",
     xlab="", xaxt="n", col = 9)
lines(loess.smooth(index(soiltemp_zoo),coredata(soiltemp_zoo)), 
      col = 6, lwd = 2)
abline(lm(coredata(soiltemp_zoo) ~ index(soiltemp_zoo)), col = 2)
legend("topright", legend = c("soiltemp data", "Loess smoothing","Linear model"),
       cex = 1.8, col = c(9,6,2), lwd = c(1,2,1), bty = "n")
mtext(paste("adf.test p value =",signif(d0$p.value,3)), 
      side = 1, line = -1.2, adj = 0.05)
plot(diff(soiltemp_zoo,1),
     ylab = "First differencing",
     xlab="", xaxt="n", col = 9)
abline(h = 0, col = "grey", lty = 2)
lines(loess.smooth(index(diff(soiltemp_zoo,1)),coredata(diff(soiltemp_zoo,1))), 
      col = 6, lwd = 2)
abline(lm(coredata(diff(soiltemp_zoo,1)) ~
            index(diff(soiltemp_zoo,1))), col = 2)
mtext(paste("adf.test p value =",signif(d1$p.value,3)), 
      side = 1, line = -1.2, adj = 0.05)
plot(diff(diff(soiltemp_zoo,1),1),
     ylab = "Second differencing",
     xlab="Date", col = 9)
mtext("Date",side = 1, line = 2.2, font = 2)
abline(h = 0, col = "grey", lty = 2)
lines(loess.smooth(index(diff(diff(soiltemp_zoo,1),1)),
                   coredata(diff(diff(soiltemp_zoo,1),1))), 
      col = 6, lwd = 2)
abline(lm(coredata(diff(diff(soiltemp_zoo,1))) ~ 
            index(diff(diff(soiltemp_zoo,1)))), col = 2)
mtext(paste("adf.test p value =",signif(d2$p.value,3)), 
      side = 1, line = -1.2, adj = 0.05)
Figure 4: Plots of soil temperature time series data and its first and second differences, with each sub-plot showing the smoothed (Loess) and linear trends.

Figure 4: Plots of soil temperature time series data and its first and second differences, with each sub-plot showing the smoothed (Loess) and linear trends.

 

Finding the trend

A. Visualising a trend using a moving average

We create a new time series from a moving average for each 24 h to remove daily periodicity using the rollmean() function from the zoo package. We know these are hourly data with diurnal fluctuation, so a rolling mean for chunks of length 24 should be OK, and this seems to be true based on Figure 5. For regular time series the frequency() function can detect the periodic frequency for us. A moving average will always smooth our data, so a smooth curve doesn't necessarily mean that we have periodicity (seasonality).

Moving averages are important parts of the ARIMA family of predictive models for time series, and that's why we show them here first.

There are other ways of drawing smooth curves to represent our time series data... see below.

 

First detect the frequency

ff <- frequency(soilT.ts) # often an approximation!! check the data!
cat("Estimated frequency is",ff,"\n") # multiply by seconds/day
## Estimated frequency is 24

💡 Try applying frequency() to the zoo time series object. Can you work out what has happened?

soiltemp_movAv <- rollmean(soiltemp_zoo, ff)
plot(soiltemp_zoo, col=9, type="l", xlab="Date", ylab="Temp. (\u00B0C)") # original data
# add the moving average
lines(soiltemp_movAv, lwd = 2, col=2)
legend("topright", bty="n", legend = c("Data",paste("Moving average, \u0192 =", ff)), 
       col = c(9,2), lwd = c(1,2))
Figure 5: Plots of soil temperature time series data and the 24-hour moving average (ƒ = frequency).

Figure 5: Plots of soil temperature time series data and the 24-hour moving average (ƒ = frequency).

 

We can use the moving average idea to decompose our time series. Since the soil temperature time series is regular, we can use the ts object class from base R (and make a nice plot using ggplot2 - Figure 6):

make a regular time series object

# we have hourly data with daily periodicity
soilT.ts <- ts(soiltemp$temp, frequency = 24, start=c(1,0))

decomp_soilT <- decompose(soilT.ts, type = "additive")
par(mar=c(3,3,1,1), mgp=c(1.7,0.3,0), font.lab=2, col.main="white")
decompDF <- data.frame(Date=index(soiltemp_zoo),
                          Data=as.vector(decomp_soilT$x),
                          Seasonal=decomp_soilT$seasonal,
                          Trend=decomp_soilT$trend,
                          Error=decomp_soilT$random)
decomp4plot <- reshape2::melt(decompDF, id.vars="Date")
ggplot() +
  geom_line(aes(x=Date, y=value, col=variable), data=decomp4plot) +
  facet_wrap(vars(variable), scales="free_y", ncol=1) +
  labs(y="Soil temperature \u00b0C") +
  scale_color_viridis_d(name="Component", option="mako", begin=0.3, end=0.65) +
  guides(color="none") +
  theme_bw() + 
  theme(strip.background=element_rect(fill="#e0f8ff"),
        strip.text = element_text(size = 11, face="bold"))
Figure 6: Components of the soil temperature time series obtained by moving average (classical) decomposition. Note the different vertical scales which overemphasise the seasonal and error components.

Figure 6: Components of the soil temperature time series obtained by moving average (classical) decomposition. Note the different vertical scales which overemphasise the seasonal and error components.

B. Showing a trend using a linear (regression) model

This is just to visualize the trend. To find if a significant trend exists, we use the Mann-Kendall test or Sen's Slope test as described later. Linear regression is not valid for time series!

First we create a linear model of the time series...

lm0 <- lm(coredata(soiltemp_zoo) ~ index(soiltemp_zoo))
summary(lm0)
## 
## Call:
## lm(formula = coredata(soiltemp_zoo) ~ index(soiltemp_zoo))
## 
## Residuals:
##     Min      1Q  Median      3Q     Max 
## -3.9217 -1.0968  0.0743  1.0938  3.5318 
## 
## Coefficients:
##                       Estimate Std. Error t value Pr(>|t|)    
## (Intercept)          2.213e+03  3.370e+01   65.66   <2e-16 ***
## index(soiltemp_zoo) -1.571e-06  2.409e-08  -65.22   <2e-16 ***
## ---
## Signif. codes:  0 '***' 0.001 '**' 0.01 '*' 0.05 '.' 0.1 ' ' 1
## 
## Residual standard error: 1.402 on 1462 degrees of freedom
## Multiple R-squared:  0.7442, Adjusted R-squared:  0.744 
## F-statistic:  4253 on 1 and 1462 DF,  p-value: < 2.2e-16

...then use a plot (Figure 7) to look at the linear relationship.

soiltemp_lmfit <- zoo(lm0$fitted.values, index(soiltemp_zoo))
plot(soiltemp_zoo, col = 9, type = "l", xlab="Date", ylab="Temp. (\u00B0C)")
lines(soiltemp_lmfit, col = 4, lty = 2)
legend("topright", legend = c("Data","Linear trend"), col = c(9,4), lty = c(1,2))
Figure 7: Plots of soil temperature time series data and the overall trend shown by a linear model.

Figure 7: Plots of soil temperature time series data and the overall trend shown by a linear model.

 

Figure 7 shows that a linear model does not really capture the trend (even without considering the periodicity) very convincingly. Moving averages (or LOESS models, shown below) represent the trend more accurately and, since time series are nearly always autocorrelated, linear models are not statistically valid.

 

Time series periodicity

NOTE THAT TIME SERIES DON'T ALWAYS HAVE PERIODICITY !

 
To model the periodicity it is useful to understand the autocorrelation structure of the time series. We can do this graphically, first by running the autocorrelation function acf() which outputs a plot by default (Figure 8):

acf(soiltemp_zoo, main = "")
Figure 8: The autocorrelation function plot for soil temperature time series data (the horizontal axis is in units of seconds).

Figure 8: The autocorrelation function plot for soil temperature time series data (the horizontal axis is in units of seconds).

 

💡 What does Figure 8 tell you about autocorrelation in this time series?

Then inspect the partial autocorrelation function (pacf())

pacf(soiltemp_zoo, main = "")
Figure 9: The partial autocorrelation function plot for soil temperature time series data (horizontal axis units are seconds).

Figure 9: The partial autocorrelation function plot for soil temperature time series data (horizontal axis units are seconds).

 

Interpreting partial autocorrelations (Figure 9) is more complicated – refer to Long & Teetor (2019, Section 14.15). A good explanation I've found is from ‘Statistics by Jim’;
    “PACF represents the correlation at each lag that is not already explained by shorter lag times.”
Partial autocorrelation can allow us to identify which and how many autocorrelations will be needed to model the time series data.

 

Box-Pierce test for autocorrelation

The null hypothesis H0 for the Box-Pierce test (Box.test())is that no autocorrelation exists at any lag distance (so p ≤ 0.05 'rejects' H0):

Box.test(soilT.ts)
## 
##  Box-Pierce test
## 
## data:  soilT.ts
## X-squared = 1436.3, df = 1, p-value < 2.2e-16
Box.test(diff(soilT.ts,1)) # 1 difference
## 
##  Box-Pierce test
## 
## data:  diff(soilT.ts, 1)
## X-squared = 15.658, df = 1, p-value = 7.589e-05
Box.test(diff(diff(soilT.ts,1),1)) # 2 differences
## 
##  Box-Pierce test
## 
## data:  diff(diff(soilT.ts, 1), 1)
## X-squared = 357.45, df = 1, p-value < 2.2e-16

 

Using loess smoothing for time series decomposition

We can make use of other base-R built-in functions to decompose regular time series using loess smoothing. We'll start with the ts object we made earlier, and apply the stl() function which implements Seasonal Decomposition
of Time Series by Loess.

[The loess method fits polynomial functions to sections of x-y type data. The smoothness of the resulting curve is controlled by how 'wide' the sections of x-y data are, defined by a bandwidth parameter.]

We can visualise the STL decomposition simply using plot(stl_soilT), but here we'll also make a prettier decomposition plot (Figure 10) using ggplot after wrangling the data into a long-form data frame:

# Seasonal Decomposition of Time Series by Loess
stl_soilT <- stl(soilT.ts, "periodic")

# pull data from stl object
plotdata <- data.frame(Date=index(stl_soilT$time.series), 
                        observed=soiltemp$temp, 
                        trend=stl_soilT$time.series[,2], 
                        seasonal=stl_soilT$time.series[,1], 
                        random=stl_soilT$time.series[,3])
plotdata <- reshape2::melt(plotdata, id.vars = c("Date")) # make long-form

ggplot(data=plotdata) +
  geom_line(aes(x=Date, y=value, col=variable)) +
  facet_wrap(vars(variable), scales="free_y", ncol=1) +
  labs(y="Soil temperature \u00b0C") +
  scale_x_continuous(breaks=c(0,20,40,60), labels=c("1 Apr","21 Apr","11 May","31 May")) +
  scale_color_viridis_d(name="Component", option="mako", begin=0.3, end=0.65) +
  guides(color="none") +
  theme_bw() + 
  theme(strip.background=element_rect(fill="#e0f8ff"),
        strip.text = element_text(size = 11, face="bold"))
Figure 10: The components of the soil temperature time series obtained by STL (seasonal decomposition of time series by loess).

Figure 10: The components of the soil temperature time series obtained by STL (seasonal decomposition of time series by loess).

 

You might want to compare Figure 10 with the moving-average-based decomposition in Figure 6. Sometimes we can't use stl() decomposition, for example if we have an irregular time series. It's possible, with a bit of trial-and-error, to use a manual loess-based approach to end up with the decomposition we want... but that's not for here

With the traditional or LTS decomposition results, we're now in a position to estimate homoscedasticity of our time series. It's not a formal method and a bit ‘hacky’ 😎, but we can predict the raw time series from the smoothed trend+periodicity, then apply the Breusch-Pagan test to our model (we need the lmtest package loaded earlier for the bptest() function):

pred <- rowSums(stl_soilT$time.series[,1:2])
lm1 <- lm(coredata(soilT.ts) ~ pred)
# slope should be ~ 1; R² should be as high as possible!
cat(paste("slope=",round(lm1$coefficients[2],3), 
          " R² =",signif(summary(lm1)$adj.r,3))) 
bptest(lm1) |> print() 
## slope= 1.004  R² = 0.984
##  studentized Breusch-Pagan test
## 
## data:  lm1
## BP = 0.36975, df = 1, p-value = 0.5431

The bptest() p-value is > 0.05 so, by this hacky estimate, our time series is homoscedastic.

We should remember that:

  • this time series was relatively easy to decompose into its components, but not all time series will be so 'well-behaved';
  • there are different ways in which we can describe the trend and periodicity (we have just used the loess smoothing functions for clear visualization).

This ends our exploratory data analysis of time series, which leads us into Part 3: Time series models, including trend and ARIMA forecast modelling.

The results of our analyses in Part 3 are the type of outputs that would typically find their way into reports...

 


CC-BY-SA • All content by Ratey-AtUWA. My employer does not necessarily know about or endorse the content of this website.
Created with rmarkdown in RStudio. Currently using the free yeti theme from Bootswatch.