Skip to content
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

[ML] Don't use higher resolution for cyclic component models than data bucketing supports #163

Merged
merged 2 commits into from
Jul 23, 2018

Conversation

tveasey
Copy link
Contributor

@tveasey tveasey commented Jul 23, 2018

As a result of #134, we now have the possibility that we can use more models for cyclic components (seasonal or calendar) than we have measurement buckets in their periods. This means (pigeonhole principle) we'll potentially end up with models which never get updated. To avoid this undesirable situation this change means we refuse to split into more than "measurement buckets per period" models.

This can affect results where the bucket length is long w.r.t. periodicities present in the data. Since this is a correction for unreleased code, it is marked as a non-issue.

Copy link
Contributor

@edsavage edsavage left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@tveasey tveasey merged commit a8f22e4 into elastic:master Jul 23, 2018
tveasey added a commit to tveasey/ml-cpp-1 that referenced this pull request Jul 23, 2018
tveasey added a commit that referenced this pull request Jul 24, 2018
@tveasey tveasey deleted the bug/dont-over-split-period branch April 10, 2019 10:49
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.

None yet

2 participants