Skip to content

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

Description

@luisquintanilla

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.

Activity

  1. changed the title [-]Changes to Anomaly Detection[/-] [+]DetectEntireAnomalyBySrCnn - No anomalies detected as of version 1.5.4 or greater[/+] on Jul 28, 2021
  2. michaelgsharp commented on Aug 19, 2021

    @michaelgsharp
    Contributor

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

  3. briacht commented on Aug 19, 2021

    @briacht
    Contributor

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

  4. michaelgsharp commented on Sep 27, 2021

    @michaelgsharp
    Contributor

    This is the PR that caused this bug #5202.

  5. added
    Priority:2Work that is important, but not critical for the release
    area-TimeSeriesTime series analysis and forecasting
    and removed on Sep 8, 2026
  6. matouskozak commented on Sep 22, 2026

    @matouskozak
    Member

    The current tests use sensitivity 87 nor 64 (test/Microsoft.ML.TimeSeries.Tests/TimeSeriesDirectApi.cs)

    This sample program should be updated https://github.com/dotnet/samples/blob/main/machine-learning/tutorials/PhoneCallsAnomalyDetection/Program.cs

    The code itself was fixed in #7610

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Priority:2Work that is important, but not critical for the releasearea-TimeSeriesTime series analysis and forecastingbugSomething isn't workingin-pruntriagedNew issue has not been triagedyellowmaintenance only

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions