Skip to content

[8.11][ML] Improve forecasting for time series with step changes #2597

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

Merged
merged 1 commit into from
Nov 22, 2023

Conversation

tveasey
Copy link
Contributor

@tveasey tveasey commented Nov 22, 2023

Backport #2591.

)

We model the level of a time series which we've observed having step discontinuities via a Markov process
for forecasting. Specifically, we estimate the historical step size distribution and the distribution of the steps
in time and as a function of the time series value. For this second part we use an online naive Bayes model
to estimate the probability that at any given point in a roll out for forecasting we will get a step.

This approach generally works well unless we're in the tails of the distribution values we've observed for
the time series historically when we roll out. In this case, our prediction probability are very sensitive to the
tail behaviour of the distributions we fit to the time series values where we saw a step and sometimes we
predict far too many steps as a result. We can detect this case: when we're in the tails of time series value
distribution.

This change does this and stops predicting changes in such cases, which avoids pathologies. This fixes elastic#2466.
@tveasey tveasey merged commit a392713 into elastic:8.11 Nov 22, 2023
@tveasey tveasey deleted the port/2591_to_8_11 branch November 22, 2023 17:46
pull bot pushed a commit to abitmore/ml-cpp that referenced this pull request Nov 22, 2023
…lastic#2598)

Release notes are correct on the 8.11 branch, but need updating
on main.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant