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

Periodicity detection accuracy is very low #7289

Open
tappanajmera opened this issue Nov 7, 2024 · 3 comments
Open

Periodicity detection accuracy is very low #7289

tappanajmera opened this issue Nov 7, 2024 · 3 comments
Labels
Time Series untriaged New issue has not been triaged

Comments

@tappanajmera
Copy link

System Information (please complete the following information):

  • OS & Version: Windows 11
  • ML.NET Version: [e.g. ML.NET v1.5.5]
  • .NET Version: [e.g. .NET 5.0]

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.
Image

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?

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged label Nov 7, 2024
@LittleLittleCloud
Copy link
Contributor

Which trainer are you using

@amueller
Copy link

amueller commented Nov 8, 2024

@ericstj
Copy link
Member

ericstj commented Dec 4, 2024

@michaelgsharp @luisquintanilla do you have any suggestions here? Do we have a sample that shows how to use this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Time Series untriaged New issue has not been triaged
Projects
None yet
Development

No branches or pull requests

4 participants