-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Periodicity detection accuracy is very low #7289
Comments
Which trainer are you using |
We're using https://learn.microsoft.com/en-us/dotnet/api/microsoft.ml.timeseriescatalog.detectseasonality?view=ml-dotnet if that was the question. |
@michaelgsharp @luisquintanilla do you have any suggestions here? Do we have a sample that shows how to use this? |
This issue has been marked |
This issue has been automatically marked |
System Information (please complete the following information):
Description

This is probably a question and not a bug.
We tested periodicity detection from ML .Net and compared against other approaches. The accuracy is very low.
Accuracy selected means "accuracy on those where it gave an answer". So ML.NET gives a periodicity only on 28% of cases, and on those 28% it's 85% accurate. Kusto gives an answer on 94% of cases, and is 78% accurate on that.
Is this expected behavior?
The text was updated successfully, but these errors were encountered: