-
Hi there, My guess is AutoARIMA expects a specific parameter to be set (like seasonality or something similar in pandas?) or the way statsforecast optimizes ARIMA parameters is not doing as good as pmd ARIMA. Your feedback and help is really appreciate it. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
Can you provide an example? |
Beta Was this translation helpful? Give feedback.
-
Sorry, I've worked on the issue since then and realized that when I set seasonality to 7 (there is weekly pattern) it captures the spikes. I have series of length 30 (small number of observations per series). Each are decomposed using SSA and get predicted individually. SSA decomposes each time series by eigen decomposition of the covariance matrix. The largest eigencomponent represents the trend and the smaller components will have quasi-periodic shapes and the smallest are simply noise. I'm not sure why ARIMA is expecting the seasonality parameter? Is seasonality used to define the lags search space? Not sure why it's needed as with SSA the seasonality is not necessary unless it's used for lags. I use this to predict each component:
Each time I forecast one component produced by SSA and then predict the component K steps. If I set stepwise=True, the prediction error becomes unacceptably large. There are only 30 observations per each series, and it is extremely slow. I'm not sure what I am missing here? |
Beta Was this translation helpful? Give feedback.
It will use 1 to 8. For the methods you can choose
ML
orCSS-ML