Skip to content

Anomaly Detection Task output should include PredictedLabel #4024

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

Closed
colbylwilliams opened this issue Jul 19, 2019 · 1 comment · Fixed by #4107
Closed

Anomaly Detection Task output should include PredictedLabel #4024

colbylwilliams opened this issue Jul 19, 2019 · 1 comment · Fixed by #4107

Comments

@colbylwilliams
Copy link
Member

The Inputs and Output Columns section should have PredictedLabel in addition to Score. Note: There is an issue with the current release of ML.NET where PredictedLabel always evaluates to true.

Additionally, the description for Score reads:

The non-negative, unbounded score that was calculated by the anomaly detection model.

This does not indicate how the value returned by the model for Score should be interpreted. Should higher scores be interpreted as anomalies, or scores closer to zero?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@colbylwilliams
Copy link
Member Author

Confirmed here, Predictions that are anomalies will have higher scores than those that aren't anomalies.

What it is essentially computing is 1 minus the ratio of the length of the projected vector and the input vector. We expect the higher the scores the higher the chance of an anomaly because in case of no anomaly the data point should be able to be projected without changing the length much.

@ghost ghost locked as resolved and limited conversation to collaborators Mar 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant