Ensemble forecasting with IBM Granite time-series models
- ID
- 38237
- Status
- summarized
- Published
- 22 Oct 2026, 3:51 PM
- Fetched
- 22 Oct 2026, 4:46 PM
- Provider
- Hugging Face Blog
- Category
- developer-ai
- Original URL
- https://huggingface.co/blog/ibm-research/granite-timeseries-ensemble-r1
- Source URL
- https://huggingface.co/blog/feed.xml
Summary
- Score
- 6.0
- Created
- 22 Oct 2026, 4:46 PM
- Tags
- Audience
- developersai_ml_learnerssaas_founders
What happened
IBM Research published a Granite Timeseries Ensemble recipe on Hugging Face that combines four Granite time-series models behind one interface and returns point plus quantile forecasts, with no retraining and no fitted ensemble weights. You use it via `pip install "granite-tsfm>=0.3.11"` and `QuantileEnsembleForecaster.from_pretrained("ibm-granite/granite-timeseries-ensemble-r1")`, with the demo running context_length 1024 and prediction_length 24 on the ETTh1 dataset. Two variants are offered: a default Probabilistic Ensemble using uniform probability pooling, and an adaptive IQR Ensemble; the recipe stores only the ensemble configuration, so the four member checkpoints are downloaded at runtime on first run.
Why it matters
If you're shipping forecasting into a product, this gives you a permissively licensed default that removes the 'which model do I pick' step for smooth industrial signals, noisy retail demand, and long seasonal horizons alike. The practical catch is stated in the post itself: because the recipe holds configuration rather than merged weights, your first invocation pulls four checkpoints, so budget for that in cold-start, serverless, or CI environments rather than assuming a single small download. The text contains no Malaysian or Southeast Asian angle, so treat this purely as a tooling decision.
Discussion angle
Weight-free ensembling: when does uniform median/quantile pooling actually beat picking one model or fitting weights — and what does the four-checkpoint runtime download cost you in a cold-start or CI pipeline?