The Anomaly Detector tool automatically sets an anomaly score threshold when processing views. To check where the initial processing set the anomaly threshold, filter your view panel by score, either ascending or descending order.

You can adjust this threshold by setting upper or lower limits in the Processing Options. Setting different numbers for the two limits can result in a third, Unclassified result class. Both numbers must be a value between 0 and 100.

- A view is NG if the anomaly score is higher than the upper threshold limit.

- A view is OK if the anomaly score is lower than the lower threshold limit.

- A view is Unclassified if the anomaly score is in-between the two limits.

Setting only one of the limits results in the anomaly score threshold being that value. In the example below, views with an anomaly score lower than 56 are OK and views with an anomaly score of 56 or higher are NG. In this case of only setting one limit, there are no Unclassified view.

In the example below, the lower limit is set to 24 and the upper limit to 58, resulting in the views scoring in-between those two values being Unclassified.

You can use the Unclassified predictions, for example, in the following use cases:

- Manually review Unclassified labels and decide whether they are OK or NG

- Run Unclassified labels through inspection again

- Set Unclassified as the input class for a downstream A downstream tool requires a previously configured upstream tool and its configuration as input. The tool is placed after its upstream tool in the toolchain. tool for further refinement