You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we are to put a forecasting tool in the hands of non-technical users, we need some way of automatically assess the quality of the forecasts and tell the user when they need to reach out for support. This can tricky: we want to be accurate, but we don't want too many false positives...
Here are two tests that we could implement:
Anomaly detection via Generalized ESD Test. See for example Twitter's package.
Ljung-Box test for autocorrelation in the residuals.
Another approach would be to fit a couple simple models and compare their accuracy with the overall model; if the simple models give better forecasts than prophet, that would be a good signal to contact a statistician.
The text was updated successfully, but these errors were encountered:
After some experimentation with the data, it seems that the the first approach would create a fair amount of false positives. In the second approach, we could restrict ourselves to a naive model with a seasonal component. If the accuracy of the prophet forecast over a certain horizon is worse than this naive model, that's a major red flag that something is wrong (e.g. overfitting recent changes).
If we are to put a forecasting tool in the hands of non-technical users, we need some way of automatically assess the quality of the forecasts and tell the user when they need to reach out for support. This can tricky: we want to be accurate, but we don't want too many false positives...
Here are two tests that we could implement:
Anomaly detection via Generalized ESD Test. See for example Twitter's package.
Ljung-Box test for autocorrelation in the residuals.
Another approach would be to fit a couple simple models and compare their accuracy with the overall model; if the simple models give better forecasts than
prophet
, that would be a good signal to contact a statistician.The text was updated successfully, but these errors were encountered: