-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Multiplicative Models/Seasonals #178
Comments
Impact on plots ? |
Demo notebook. |
Added a dataset for the demo notebook
First demo dataset : wineind: Australian total wine sales https://www.rdocumentation.org/packages/forecast/versions/8.1/topics/wineind |
Updated Optons. Only additive models are activated by default
Generate all models with all possible decomposition types.
Handle slow mode. XGBoost and LightGBM models are optional.
Properly compute the final/winning model.
Compute AR/Keras/Intermittent/Scikit models residues
Added sample jupyter notebooks with the same dataset and different model settings (T+S+R, TS+R, TSR, slow) WIP
Compute residues is not that easy!!!
Handle division by zeros in multiplicative models residues.
Added some tests (slooooooow, for debugging purposes)
Disable cross-validation by default in slow mode. Can be reenabled manually.
Update model complexity. Additive models are simpler than multiplicative ones.
Refactored model selection. Probably some issues correcetd with very large models. Added some backward-compatibility.
Summary of implementation details : Updated Options. Only additive models are activated by default |
Fixed. |
PyAF uses an additive signal decomposition of the type \Phi( Trend + Seasonal + AR), where \Phi is a signal transformation.
It is interesting to add multiplicative decompositions to allow more diverse models. A decomposition can be of the form \Phi( Trend * Seasonal + AR) or \Phi( Trend * Seasonal * AR). More general models can be generated this way and allow exploring more forecast types/spaces.
References :
Target Release : 2022-07-14
The text was updated successfully, but these errors were encountered: