Closed tankdeer closed 3 years ago
Just a super quick look, but change the minimum size percent to 0. Note the result on one of the cars is "TooSmallPercent" and that the PercentOfImage was .3, so that would have prevented the car from first being detected and prevented any duplicates after that from being relative. The percent of image calc doesnt seem right sometimes but as far as I can tell the math works out.
So I tried that, and re-processed the image, and as you thought, it did pick up the car across the street. However, it's still ignoring the main car that's in the actual driveway. To clarify, I don't care about cars parked on the street. I was thinking I would mask them, but seeing now that minimum size handles that nicely.
Parked car marked as relevant now:
But car pulling into driveway is still ignored as a duplicate
So perhaps I was confused and thought that "TooSmallPercent" was in reference to the confident limit, but is actually percent of image. If that's the case, I think that portion is ok.
Not triggering on the 56% match on the main car is the main problem
I'm going to try to tweak the order the detection are processed and duplicates removed since I think that may be the factor here.
If you have deepstack set to High, try Medium. And/or to reduce the number of duplicate items processed by aitool by enabling: History tab > Settings > Restrict Threshold at source. That way it wont even show the lower confidence predictions where it thinks your car is a truck or van. Or meat popsickle.
Deepstack is set to Medium, Restrict Threshold at source is already enabled.
I actually tried disabling that, and it did seem to pick up the car when I reprocessed the image. It still saw it as a duplicate truck with lower confidence, but it picked the main subject as car and alerted on that. It didn't see the car in the background, which is fine with me, and I think what you were saying.
Where we can find the last updatet Versions?
I found it linked in another open issue
Ok, so my wife just came home, and triggered the motion alert in the driveway again. I had left Restrict Threshold at source disabled from the other day, and the results were quite different this time. This time, it was flagged as a false alert (I am not sure what it does to consider that - no objects found?)
It looks like Blue Iris took 3 photos, but AI Tool only analyzed two of them - the first, from the pre-trigger, you can't really see much. The last, right before the trigger ended, which you can't really see much. But it ignored the middle one, where you can clearly see the car. I'm guessing this is a result of Restrict Threshold at source being disabled?
I believe normally, it would analyze all 3, and and Alert if one matched the conditions, right? At that point the cooldown timer starts?
If I manually add the middle image, the one that was missed. It sees the car at 64% (well over the threshold), but as before, marks it as irrelevant and a duplicate where it is also 19% sure it's a Truck.
So yeah, something wonky with duplicates it seems, and it seems to be an issue more with Vehicles, or at least that's all I've noticed it on
So this is remarkably consistent with vehicles in the driveway. One thing I noticed today, is of the several vehicles it thinks it might be, Truck is always among them. Which is fine, however Truck is marked as UnwantedObject. Which is not true. I have Truck enabled in the camera settings as seen in the first post
On one hand a car is not a truck, on the other I'd be happy it if alerted on any vehicle in the driveway. I tried changing the relevant objects around and re-testing, and it didn't make any difference. There's just something with vehicles
This one any better? I think I found a better way of dealing with duplicates and prioritizing the detected objects better.
Make a backup of your original folder just in case.
AITool-VorlonCD-v2.0.928.zip
Awesome, thank you so much.
I've installed that and ran a few of my saved images through it. So far it does seem to flag the car much better. We'll see how it does next time the camera is trigger for real.
One thing I did notice however, is the Relevant object settings are being duplicated for every camera. For example if I add 'Car' to Driveway, it gets checked on Front Porch too. I assume just overwriting for all by accident. Let me know if I should open a new issue for that or not.
Once I'm confident the duplicate is resolved I'll close this one. Thanks again
The relevant objects added to other cameras are by design so you have them available to "enable" if you like. They are being added as disabled, right?
No, they're enabled and overwriting whatever settings I put in. For example. I just enabled Person and Face on my Front Porch camera, with different thresholds:
Then I went to the driveway, and added a handful of vehicles, in addition to Person:
When I go back to Front Porch now, you can see it overwrote with the Driveway settings. Same for every camera
It's not specific to any camera. Any changes I make to one, is applied to all of them. Best I can tell it's just the relevant objects. Other changes seem ok
I've been seeing the same but it seems to be limited by the camera name somehow. I have a group of cameras named 'Workshop xxxx' and if I change one it applies it to all starting ''Workshop'', but not to those beginning say ''Drive xxxx''. It also seems to be mixing up the AITool camera name with the BI Camera name.
It may have been happening for a while but I've only just noticed it as the last commit meant i had to redo my Relevant objects which I've not done for a while.
In my case I don't have any groups defined but that's an interesting observation. No groups = duplicate across all. Groups = duplicate across group?
It only started with this last build. Prior to that, it seemed ok.
Speaking of this last build, so far so good on properly detecting vehicles. Snagged my wife's car just fine earlier today
Edit. Actually, something strange I didn't notice earlier. When my wife came home earlier, she triggered the camera and I got the alert. I have annotations merged at the moment, and saw the car flagged at 72%. Didn't think much other than yay, it's fixed. However I was just looking at the History in AI Tool, and it's not there. It's actually flagged internally as a false alert. I suspect it's just an issue with the history, since I got the notification just fine.
History:
Image from email notification
Again, please let me know if these should be opened as separate issues. I don't know which you prefer for tracking purposes.
This one should be working better for relevant objects. Note that if you were using a few builds back, that it should correctly migrate the list forward now, so the object list may be different if you made recent changes to it. AITool-VorlonCD-v2.0.942.zip
Dude, you're a badass. Best I can tell this fixed both the issue with the history & the object duplicates, and testing the duplicate vehicles seems to still work as well. Thank you so much. Please put up a donate link somewhere as you certainly earned a few beers/coffees.
As before, I'll run like this a couple days and then close the issue if all is (still) well
Cheers
Latest with a few more changes in relevant object editor: AITool-VorlonCD-v2.0.988.zip
I have my driveway camera configured for person and a handful of vehicle types. My wife just came home and triggered the camera, but the alert was marked as irrelevant, despite the car being picked up well over the confidence limit.
Confidence limits per object. All at default 30-100
Prediction Tolerances for the camera are pretty low. Not sure how this works when both are specified. Almost seems like they're cumulative based on some of the results I'm seeing?
Car was marked at 56%, which should trigger. But it also says duplicate, because it was also marked as a Truck, and a Bus at lower confidence
Is it being marked irrelevant because it thinks it's a duplicate? If so, I think that's a bug. If one of the duplicate items is over the confidence limit, it should Alert, and disregard the others.
Side note, the neighbor's car parked on the street (which I probably need to mask) was marked as 35%, but with the result of TooSmallPercent. This is what's making me wonder if they are cumulative, as it should Alert on that being over 30% too.
Here's the log from the detection:
I've only had all this setup for a couple days, so it's entirely possible I screwed something up, but my other cameras seem to be working fine, and this one works with Person, just the car is wonky.
Let me know if you need me to do anything, and thanks for an awesome tool