1
$\begingroup$

I'm a novice in using R and in forecasting. Right now I'm using a dataset with daily precipitation(mm) data from 2001 to mid 2022.

Using STL decomposition seems to suggest the data has a yearly seasonal component:

enter image description here

Here is the code I am running and the resulting graph:

train <- df_zero %>%
  filter_index("2001-01-01" ~ "2019-12-31")

train %>%
  model(
    ETS = ETS(precipitacaoTotal ~ error("A") + trend("A") + season("A")),
    ) %>%
  forecast(h="3 years") %>%
  autoplot(train)

enter image description here

I've seen some in questions related to ARIMA that you need to say to R that you want to use an early seasonality (365), but i'm having a hard time finding out how to do it for ETS, if i'm not wrong i'm using the fable package.

So, how to fix my forecast, so it can perceive the early seasonality?

$\endgroup$
2
  • $\begingroup$ You need to specify that your precipitacaoTotal time series has a frequency of 365. Would you be open to a solution in base R and the forecast package? I do not use tidyverse tools, I find them a completely useless piece of extra complexity I would need to wade through. In any case, do you have a specific reason to specify the error/trend/seasonality structure, rather than let ETS decide? It's very good at that. $\endgroup$ Commented Jul 18, 2022 at 6:14
  • $\begingroup$ Hello @StephanKolassa, Yes, I don't have problem with using another package. As for the arguments I passed to ETS, I was just testing different things, since it shows the straight line even without arguments. $\endgroup$
    – Guilherme
    Commented Jul 18, 2022 at 16:18

1 Answer 1

0
$\begingroup$

TL;DR: you can't run seasonal models with a seasonality of 365 days in ETS. Use stlf instead.


The best approach would be to specify your original time series (in your case, precipitacaoTotal) as seasonal. This is what you could do for monthly seasonality:

library(fable)
set.seed(1)
foo <- as_tsibble(ts(rnorm(1000),frequency=12))
foo %>% model(ETS(value~season(method="A"))) %>% forecast(h="3 years") %>% autoplot(foo)

forecast

Since I forced seasonality using season(method="A"), we get a (pedagogically useful, but of course nonsensical) seasonal forecast. If we let ETS decide on a model on white noise, it would of course not choose a seasonal one.

However, this will not work for longer periods. If we use the same idea with frequency=365,

set.seed(1)
as_tsibble(ts(rnorm(1000),frequency=365)) %>% model(ETS(value))

we get a rather unhelpful error message (formatted):

# A mable: 1 x 1
  `ETS(value)`
       <model>
1 <NULL model>
Warning message:
1 error encountered for ETS(value)
[1] .data contains implicit gaps in time. 
You should check your data and convert implicit gaps into explicit
missing values using `tsibble::fill_gaps()` if required.

I don't quite see where ETS sees implicit gaps, and have pinged the maintainers of fable.

However, the underlying reason is probably that ETS does not support seasonal periods longer than 24 periods: running

set.seed(1)
as_tsibble(ts(rnorm(1000))) %>% model(ETS(value~season(period=365)))

yields the much more informative warning message

# A mable: 1 x 1
  `ETS(value ~ season(period = 365))`
                              <model>
1                        <ETS(A,N,N)>
Warning message:
Seasonal periods (`period`) of length greather than 24 are not supported by ETS. 
Seasonality will be ignored. 

This is actually the same behavior as in the older forecast package. Running

library(forecast)
set.seed(1)
ets(ts(rnorm(1000),frequency=365))

yielded (among other outputs):

I can't handle data with frequency greater than 24.
Seasonality will be ignored. Try stlf() if you need seasonal forecasts.

And this actually makes a lot of sense. In exponential smoothing (whether in a state space framework or otherwise), having a seasonality of $k$ periods means you need to estimate $k$ initial conditions. 365 initial conditions is a lot. You would overfit massively. So go with stlf instead.

$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.