AI Cancelling Alerts - False Negatives

Jun 19, 2016
7
0
I'm experiencing intermittent cancelled alerts on a couple of my cameras. As you can see in the two AI Analysis screenshots, the first analysis typically detects the person, but then the one BI is using thinks the person is static. I'm not sure how BI chooses which analysis to use, but I thought that if any of the analyzed frames contained a person, it would alert. I'm also assuming the asterisk indicates the chosen frame, but I'm not certain there. The time to analyze seems a little high, but I'm not sure if that would have this effect. Any ideas how to improve upon this? I've seen some mention about using "unicorn" in the cancel field, but I want my alerts fired off ASAP.

Thanks!

AI1.pngai2.pngai3.png
 
Update: I was running YOLOv5 6.2 and switch to YOLOv5 .NET, and my analysis ties have come down to 100-200ms. I'm on an Intel I9-12900HK, so this seems the more appropriate model. Running model size 'Large.' Going to test to see if this resolves the issue.
 
I'm also assuming the asterisk indicates the chosen frame, but I'm not certain there. The time to analyze seems a little high, but I'm not sure if that would have this effect.
Per the help PDF…
An asterisk (*) marks the image that was ultimately used to confirm or cancel the alert.
 
It's probably due to the long processing times. Take a look at the timings - you've got timings approaching 5,000 msecs. They ideally should be under 200ms. Unsure what processing methods / pc you're using but appears whatever they are, they're struggling to process the images.

Could be a pc issue, model or setting issue.

However, either way, 5,000ms processing times will wreak havoc as the images are cancelled after 750ms according to your settings (that one is correct but I believe I use 500ms) as the whole AI system will lag out rom one image to another. Don't forget 5,000ms is 5 secs!

Post your pc specs and exactly the AI model you're using and whether you're processing by cpu or gpu and others will probably respond.
 
Processing times are much better now, but I'm still seeing some strangeness. You can see the frame with the asterisk has both a static person(incorrect) and an active make, but the alert is still cancelled.

.ai1.pngai2.png