-
Notifications
You must be signed in to change notification settings - Fork 6k
No anomalies detected #23888
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
Comments
Sorry to hear you ran into issues. Would you be able to share the output / error you're getting. Thanks |
Thanks for raising this issue @robin-karlsson. I was able to reproduce 1.5.2 Output
1.5.5 Output
|
@guinao @michaelgsharp thoughts? |
@luisquintanilla I saw that you managed to reproduce now. Please give me a ping if you need me for something else. I can confirm that my output looked very similar to yours. Thanks |
Hi @robin-karlsson apologies for the delay on this. I just tried the latest version 1.6.0 to see if it works and the issue persist. This does not seem to be a documentation issue as you can get it working with version 1.5.2. I've raised an issue on the dotnet/machinelearning repo to track this. In the meantime, I'll update the document to specify you need to use version 1.5.2 and close the issue. To track the progress of this, please see dotnet/machinelearning#5891 Thanks again for bringing this to our attention. |
In the sample for phone calls anomaly detection we noticed that you won’t get any anomalies detected with version 5.5. Running the sample with version 5.3 works.
Not sure if this is an intended change in the library requiring an update of sample data or if this is due to a problem in the TimeSeries part?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: