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

[AnomalyDetection] confidence bound should include non-anomaly points #5379

Closed
lisahua opened this issue Aug 31, 2020 · 0 comments · Fixed by #5374
Closed

[AnomalyDetection] confidence bound should include non-anomaly points #5379

lisahua opened this issue Aug 31, 2020 · 0 comments · Fixed by #5374
Labels
anomaly Bugs related Anomaly Detection P2 Priority of the issue for triage purpose: Needs to be fixed at some point.

Comments

@lisahua
Copy link
Contributor

lisahua commented Aug 31, 2020

System information

  • OS version/distro: ML.Net 1.5.1
  • .NET Version (eg., dotnet --info):

Issue

  • What did you do?
    We use the API DetectEntireAnomalyBySrCnn

  • What happened?

We see some points are outside of the confidence bound yet not detected as anomalies. This is a bit confusing on why these points are not anomalies.

image

  • What did you expect?

The non-anomaly points should be included in the confidence bound.

Source code / logs

PR: #5374

Proposed change: Adjust the confidence bound so that it includes the non-anomaly points
image

@guinao guinao mentioned this issue Sep 1, 2020
4 tasks
@mstfbl mstfbl added anomaly Bugs related Anomaly Detection P2 Priority of the issue for triage purpose: Needs to be fixed at some point. labels Sep 2, 2020
@mstfbl mstfbl linked a pull request Sep 2, 2020 that will close this issue
4 tasks
@dotnet dotnet locked as resolved and limited conversation to collaborators Mar 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
anomaly Bugs related Anomaly Detection P2 Priority of the issue for triage purpose: Needs to be fixed at some point.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants