Too many detection in anomaly unit detection runner #109

Open
opened 2 years ago by glitch4347 · 0 comments
glitch4347 commented 2 years ago (Migrated from github.com)
Owner

When detection runner starts with anomaly unit, it detects too many segments. For example, if I started DetectionRunner::run(1641685784), then the line let detections = a.detect(ms.clone(), t_from, t_to).await.unwrap(); works with t_from = 1641721134, but the first detection in detections is (1641685784, 1641685924), the second is (1641685934, 1641685984) and there are 375in thedetections`

When detection runner starts with anomaly unit, it detects too many segments. For example, if I started `DetectionRunner::run(1641685784)`, then the line `let detections = a.detect(ms.clone(), t_from, t_to).await.unwrap();` works with `t_from = 1641721134`, but the first detection in `detections` is `(1641685784, 1641685924)`, the second is `(1641685934, 1641685984) and there are `375` in the `detections`
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.