-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[DOC] add newer features to the hierarchical forecasting tutorial - grid search, metrics, ensembles, etc #4106
Comments
relevant recent discussion with @anthonygiorgio97 with some code that might be reducible to nice vignettes: |
Hi @fkiraly , |
Sure! Which topic would you like to work on, @nish-ahmd-it? |
@fkiraly shall i focus on use of the pooling parameter in make_reduction, as was added by recently ? |
Hi, @fkiraly, I am willing to work on this issue. Shall I work on |
Hello , @fkiraly , I would like to add the feature of |
@Aarthy153, yes, that would be great! @pranavvp16, that would be great! The focus should be using it in the hierarchical case. Same idea - a vignette somewhere suitable in the notebook. |
sktime
features for hierarchical and panel time series forecasting have progressed a bit since we presented our initial tutorial at pydata Berlin 2022.It would be nice if some of the newer features were added in "the right places" of the hierarchical forecasting tutorial https://github.com/sktime/sktime/blob/main/examples/01c_forecasting_hierarchical_global.ipynb.
Features I can think of:
pooling
parameter inmake_reduction
, as was added by recent PR of @danbartlget_fitted_params
in case of "hierarchical-by-broadcast"ForecastingGridSearchCV
to tune best models by instance or globallyForecastByLevel
for granular, custom control of hierarchical poolingReconcilerForecaster
that @ciaran-g added since then, with more reconciliation strategiesHierarchyEnsembleForecaster
by @VyomkeshVyas, if/once it's ready: [ENH]HierarchyEnsembleForecaster
for level- or node-wise application of forecasters on panel/hierarchical data #3905anything else that should be here? FYI @danbartl, @KishManani, @ciaran-g, @VyomkeshVyas, @topher-lo
I think this is a potential good first issue since each topic could be a small vignette, added in the right place, or modifying one of the existing vignettes. Contributors could pick one topic.
The text was updated successfully, but these errors were encountered: