Skip to content

DetectEntireAnomalyBySrCnn - No anomalies detected as of version 1.5.4 or greater #5891

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.

Sign up for GitHub

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

Jump to bottom
Open
luisquintanilla opened this issue Jul 28, 2021 · 3 comments
Open

DetectEntireAnomalyBySrCnn - No anomalies detected as of version 1.5.4 or greater #5891

luisquintanilla opened this issue Jul 28, 2021 · 3 comments
Labels
anomaly Bugs related Anomaly Detection bug Something isn't working P2 Priority of the issue for triage purpose: Needs to be fixed at some point.

Comments

@luisquintanilla
Copy link
Contributor

luisquintanilla commented Jul 28, 2021 •
edited
Loading

System Information (please complete the following information):

  • OS & Version: Windows 10
  • ML.NET Version: ML.NET 1.5.4 and greater
  • .NET Version: .NET 5

Describe the bug

When using DetectEntireAnomalyBySrCnn with versions 1.5.4 or greater, no anomalies are detected when running the DetectAnomaly method from the phone call tutorial.

Changing options does nothing. Has anything changed with this algorithm that would suddenly make it stop working after 1.5.4?

If you run the sample using version 1.5.2 with the same data and options it works.

Related docs issue dotnet/docs#23888

To Reproduce

Follow the steps in the phone call tutorial. For reference, here's a completed code sample

Expected behavior

Anomalies are detected.
@luisquintanilla luisquintanilla mentioned this issue Jul 28, 2021
Closed
@luisquintanilla luisquintanilla changed the title Changes to Anomaly Detection DetectEntireAnomalyBySrCnn - No anomalies detected as of version 1.5.4 or greater Jul 28, 2021
@michaelgsharp michaelgsharp added anomaly Bugs related Anomaly Detection bug Something isn't working P2 Priority of the issue for triage purpose: Needs to be fixed at some point. labels Aug 19, 2021
@michaelgsharp
Copy link
Contributor

@luisquintanilla since this is a regression I would say its probably a higher priority. @briacht thoughts?

@briacht
Copy link
Contributor

briacht commented Aug 19, 2021

Yeah if the algorithm isn't working anymore we should definitely try and fix that

@luisquintanilla luisquintanilla mentioned this issue Aug 25, 2021
Draft
@michaelgsharp
Copy link
Contributor

This is the PR that caused this bug #5202.

@michaelgsharp michaelgsharp mentioned this issue Oct 14, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
anomaly Bugs related Anomaly Detection bug Something isn't working P2 Priority of the issue for triage purpose: Needs to be fixed at some point.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@briacht @luisquintanilla @michaelgsharp