Skip to content
This repository was archived by the owner on Aug 16, 2022. It is now read-only.

Commit ba1720b

Browse files
Merge pull request #451 from ashwinkumar12345/AD_feature_limit
Impact of features on the accuracy of an AD model
2 parents 4c1368a + 1771677 commit ba1720b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/ad/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ In this case, a feature is the field in your index that you to check for anomali
5252

5353
For example, if you choose `min()`, the detector focuses on finding anomalies based on the minimum values of your feature. If you choose `average()`, the detector finds anomalies based on the average values of your feature.
5454

55-
You can add a maximum of five features for a detector.
55+
A multi-feature model correlates anomalies across all its features. The [curse of dimensionality](https://en.wikipedia.org/wiki/Curse_of_dimensionality) makes it less likely for multi-feature models to identify smaller anomalies as compared to a single-feature model. Adding more features might negatively impact the [precision and recall](https://en.wikipedia.org/wiki/Precision_and_recall) of a model. A higher proportion of noise in your data might further amplify this negative impact. We recommend adding fewer features to your detector for a higher accuracy. By default, the maximum number of features for a detector is 5. You can adjust this limit with the `opendistro.anomaly_detection.max_anomaly_features` setting.
5656
{: .note }
5757

5858
1. On the **Model configuration** page, enter the **Feature name**.

0 commit comments

Comments
 (0)