How to ignore stationary false positives? #15407
Unanswered
raintonr
asked this question in
Ask A Question
Replies: 3 comments
-
BTW, I did think about increasing height and/or area necessary, but that would not work as sometimes the false positive is much larger: |
Beta Was this translation helpful? Give feedback.
0 replies
-
you can increase the min_score and threshold, that may help with falses. |
Beta Was this translation helpful? Give feedback.
0 replies
-
In 0.15 you'll be able to see the different moments an object was detected during its lifecycle to debug that |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have previously asked about ignoring false positive that seem to suddenly appear in part of the frame and do not move (see #10414). The answer at the time was that logic was already improved in 0.14. I have now been running 0.14.1-f4f3cfa for some time and still see this problem.
False positives occur more often at night and/or in bad weather (when there can be rain or snow on the lens). While I get that false positives can occur, what I do not understand is that when they appear in frame and don't move, why are they causing detections, when I was told in the issue above that an object had to move to be considered a valid detection?
Here's a couple of examples:
If Frigate does not flag objects as detections unless they move, it would be super useful to see the path that the object followed up to the point it was thought a valid target in order to investigate this further?
If the behaviour I am seeing is as designed, any suggestions as to how to avoid detections like this?
Beta Was this translation helpful? Give feedback.
All reactions