Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

Successfully reported this slideshow.

Like this presentation? Why not share!

3,986 views

Published on

Published in:
Data & Analytics

No Downloads

Total views

3,986

On SlideShare

0

From Embeds

0

Number of Embeds

556

Shares

0

Downloads

61

Comments

0

Likes

6

No embeds

No notes for slide

- 1. Automatic Forecasting at Scale Sean J. Taylor 12 Aug 2015 Joint Statistical Meetings
- 2. Many Forecasting Problems at Facebook • capacity planning: servers, switches, people, even food • user / advertiser growth • revenue • goal setting for teams (with respect to forecast) • detecting anomalies • “trending” units
- 3. Business Time Series Have Similar Attributes • comprised by multiple “units” (e.g. countries, users, advertisers, hardware units) • units are “born” at different times, can exit the sample • growth curves are common (e.g. saturating a market) • complex, human-scale seasonality, holidays and events • structural breaks as exogenous changes happen (e.g. new products, redesigns, site outages) • missing data
- 4. Thousands or millions of forecasts?
- 5. Mo’ Data, Mo’ Problems
- 6. A second (and third) kind of scale: many people and problems
- 7. Goal is to create technology: people who are not experts can use it easily with few decisions and trust the output
- 8. Technology?
- 9. Results of my search for forecasting advice ▪ carefully clean, scale, and fix missingness in data ▪ try many kinds of models ▪ use model selection procedures based on (penalized) goodness-of-fit or just ocular goodness-of-fit ▪ lots of tacit knowledge involved — experienced forecasters have earned a lot of credibility
- 10. Why is building a forecaster harder than building a classifier?
- 11. How most people build a classifier: 1. Choose a loss function. 2. Gather as much data as possible and construct potentially useful features. 3. Train models using different amounts of regularization. 4. Choose the one that predicts the best out-of-sample using some cross-validation procedure. With a ﬂexible enough learner, the only time a human needs to intervene is during feature construction!
- 12. Forecasting as (special) supervised learning Features ▪ state-features constructed from historical data ▪ time-based features for seasonality, events, etc. Training ▪ off-the-shelf regularized regression (glmnet, VW) Model selection ▪ use simulated forecasts to estimate expected loss
- 13. When you have a really awesome hammer, make everything look like a regularized regression. arg min ky X k2 + 1k k1 + 2k k2
- 14. A flexible extrapolation model
- 15. Fixed-Horizon Forecasting Regression Regressors are generated from paste state: yt+H = f(yt, yt 1, yt 2, . . .) yt+H = ↵yt + 1 t tX i=1 yi Last Value Mean Value
- 16. State features from one-sided kernel- weighted statistics t Can use any weighted statistic to generate features: mean, variance, quantiles, etc. past data
- 17. Assumption: local smoothness Assume parameters vary smoothly over forecast horizon (same as assuming forecast is locally smooth). yt+H = ↵H · yt + H · 1 t tX i=1 yi Different model for each horizon ↵H H0 Max Horizon
- 18. Adding Seasonality Features Add components to the model that represent deterministic functions of time: ▪ trend ▪ cyclic cubic splines for yearly seasonality ▪ day-of-week, day-of-year, hour-of-day dummy variables ▪ smooth curves around known holidays yt+H = f(yt, yt 1, yt 2, . . .) + g(t + H)
- 19. t y 1/1 5 1/2 9 1/3 16 t last mean 1/1 - - 1/2 5 5 1/3 9 7 t+H y Mon Tue 1/1 5 1 0 1/2 9 0 1 1/3 14 0 0 State Features Target + Time Features t+H t H y last mean Mon Tues 1/2 1/1 1 5 - - 0 1 1/3 1/1 2 9 - - 0 0 1/3 1/2 1 14 5 5 0 0 Input Data for Training Series
- 20. Making it hierarchical We want to borrow information about processes across units. Huge opportunity because: 1. We know more about “new” time series than we think if we are willing to assume they are generated from a similar process. 2. The more examples from a family of time series processes we have, the better we are able to learn about its structure. Example: stock market. 3. Precision gains from borrowing information.
- 21. One weird trick for hierarchical models Common Features United States Canada Mexico Global parameters Unit-speciﬁc yi,t+H = ↵yt + 1 t tX i=1 yi + ↵iyt + i 1 t tX i=1 yi
- 22. Training ▪ BIG DATA: optimization-based techniques are difficult to use here because ▪ Online learning using SGD/Adagrad/Adadelta work well here AND we can update parameters for different loss functions and regularization parameters at the same time. ▪ Other bonus for online learning: incremental learning on data sorted by time!
- 23. Model Selection via Forward Cross-Validation We have two sets of hyper-parameters: 1. regularization of the model coefficients. 2. amount of differencing we do before fitting. Just like in the classification version of the problem, we choose the model that empirically forecasts the best by selecting K simulated forecast dates. Training stream Testing stream Checkpoint Model 1 2 1 23
- 24. Predictive Intervals with Quantile Regression Very important to quantify uncertainty about a forecast. Often we’d prefer that people not even look at the point estimates. Once you’re in the land of regularized linear regression, we can get predictive intervals simply by changing loss function to quantile loss. Directly optimizing the model for the correct amount of empirical coverage!
- 25. Computational Tricks ▪ online feature scaling ▪ feature hashing ▪ stochastic gradient descent (and Adagrad, Adadelta) ▪ fitting several models simultaneously on the same data stream
- 26. Scaling to More People/Problems 1. Start with a single use-case and nail it. 2. Parameterize that solution — adding new problems should simple be configuration. 3. Work on model/fitting procedure, then run all previous models for diagnostics. 4. Provide easy tools for model criticism — top predictive errors, examples with under/over coverage, etc.
- 27. Conclusions ▪ Different kinds of “at scale” — people and problems are more important than size of data ▪ If a model/technique is hard to use, it’s worth thinking about what it would take for a non-expert to use it. ▪ Making problems look like regularized linear regression is GREAT. ▪ Forecasting can be made into a very special kind of supervised learning. ▪ Email me with comments/feedback: sjt@fb.com

No public clipboards found for this slide

Be the first to comment