Closed kkondaka closed 1 year ago
Indeed the PredictorCorrect was set as too aggressive -- changing
return thresholder.getAnomalyGrade(remainder dimensions / difference, previousIsPotentialAnomaly, triggerFactor) > 0; to return thresholder.getAnomalyGrade(remainder dimensions / difference, previousIsPotentialAnomaly) > 0
solves the issue (pushed to PR 354). Parametrized tests added to ThresholdedRandomCutForestTest.java
The expression (remainder * dimensions / difference) corresponds to an estimated contribution of the new input, including and after the gap. In the first expression, that contribution was evaluated against a more aggressive threshold determined by triggerFactor.
Resolved via PR 354.
Example sequence of events
example code