# R: Seasonal Periods

# R: Seasonal Periods

Join the DZone community and get the full member experience.

Join For FreeI get questions about this almost every week. Here is an example from a recent comment on this blog:

I have two large time series data. One is separated by seconds intervals and the other by minutes. The length of each time series is 180 days. I’m using R (3.1.1) for forecasting the data. I’d like to know the value of the “frequency” argument in the ts() function in R, for each data set. Since most of the examples and cases I’ve seen so far are for months or days at the most, it is quite confusing for me when dealing with equally separated seconds or minutes. According to my understanding, the “frequency” argument is the number of observations per season. So what is the “season” in the case of seconds/minutes? My guess is that since there are 86,400 seconds and 1440 minutes a day, these should be the values for the “freq” argument. Is that correct?

The same question was asked on crossvalidated.com.

Yes, the “frequency” is the number of observations per season. This is the opposite of the definition of frequency in physics, or in Fourier analysis, where “period” is the length of the cycle, and “frequency” is the inverse of period. When using the `ts()`

function in R, the following choices should be used.

Data | frequency |
---|---|

Annual | 1 |

Quarterly | 4 |

Monthly | 12 |

Weekly | 52 |

Actually, there are not 52 weeks in a year, but 365.25÷7 = 52.18 on average. But most functions which use

`ts`

objects require integer frequency.
Once the frequency of observations is smaller than a week, then there is usually more than one way of handling the frequency. For example, hourly data might have a daily seasonality (frequency=24), a weekly seasonality (frequency=24x7=168) and an annual seasonality (frequency=24x365.25=8766). If you want to use a `ts`

object, then you need to decide which of these is the most important.

An alternative is to use a `msts`

object (defined in the `forecast`

package) which handles multiple seasonality time series. Then you can specify all the frequencies that might be relevant. It is also flexible enough to handle non-integer frequencies.

Data | frequencies | ||||
---|---|---|---|---|---|

minute | hour | day | week | year | |

Daily | 7 | 365.25 | |||

Hourly | 24 | 168 | 8766 | ||

Half-hourly | 48 | 336 | 17532 | ||

Minutes | 60 | 1440 | 10080 | 525960 | |

Seconds | 60 | 3600 | 86400 | 604800 | 31557600 |

You won’t necessarily want to include all of these frequencies — just the ones that are likely to be present in the data. For example, any natural phenomena (e.g., sunshine hours) is unlikely to have a weekly period, and if your data are measured in one-minute intervals over a 3 month period, there is no point including an annual frequency.

For example, the `taylor`

data set from the `forecast`

package contains half-hourly electricity demand data from England and Wales over about 3 months in 2000. It was defined as

taylor <- msts(x, seasonal.periods=c(48,336)

One convenient model for multiple seasonal time series is a TBATS model:

taylor.fit <- tbats(taylor) plot(forecast(taylor.fit)) (Warning: this takes a few minutes.) If an ## Related Posts: |

Published at DZone with permission of Rob J Hyndman , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

## {{ parent.title || parent.header.title}}

{{ parent.tldr }}

## {{ parent.linkDescription }}

{{ parent.urlSource.name }}