IP Cam Talk Custom Community DeepStack Model

MikeLud1

IPCT Contributor
Joined
Apr 5, 2017
Messages
2,219
Reaction score
4,265
Location
Brooklyn, NY
Not as well as I had hoped, but it is working. Detections seem about 10% lower confidence than the "original" dark. Keep in mind I have a difficult situation and even the original doesn't work at 100%. Combined, during the day, never misses though.
Are you using Low, Medium, or High mode. All my models are trained to use High for the best results, I am seeing better confidence compared to my general model even during the day
1653620935065.png
1653621117581.png
 

Sybertiger

Known around here
Joined
Jun 30, 2018
Messages
4,717
Reaction score
13,620
Location
Orlando
i5-8500 CPU version of Deepstack

I'm using the combined (Day) and dark (Night) and thought I was doing good until I noticed my detection times going up. I tried to get my detection times down but I must be in a mental block as my times keep going up...LOL. Take a look and please point out the obvious. And why it decided that the 80% detection was better than the 91% analysis is beyond me.

1653666533950.png

1653666573216.png

1653666823818.png

1653666691637.png

1653668144343.png

1653666747813.png

1653667086742.png
 

Attachments

Last edited:

MikeLud1

IPCT Contributor
Joined
Apr 5, 2017
Messages
2,219
Reaction score
4,265
Location
Brooklyn, NY
i5-8500 CPU version of Deepstack

I'm using the combined (Day) and dark (Night) and thought I was doing good until I noticed my detection times going up. I tried to get my detection times down but I must be in a mental block as my times keep going up...LOL. Take a look and please point out the obvious. And why it decided that the 80% detection was better than the 91% analysis is beyond me.

View attachment 129193

View attachment 129194

View attachment 129199

View attachment 129196

View attachment 129203

View attachment 129198

View attachment 129200
Try rebooting to see if the detection times come down. For the 80% detection was better than the 91% this is Blue Iris that makes the decision.
 

sebastiantombs

Known around here
Joined
Dec 28, 2019
Messages
11,511
Reaction score
27,696
Location
New Jersey
@MikeLud1 You're working with color at night. The scenes I have are B&W since there's nowhere nearly enough light for color even on a 5442. The headlight bloom, even with HLC at 100 is quite strong and there's only a frame or two where an actual vehicle shows in the frame without being obscured by the headlights. That's one of the things about models that can be problematic, they are based on nice images under the best conditions and probably shot with an SLR to boot.
 
Last edited:

jrbeddow

Getting comfortable
Joined
Oct 26, 2021
Messages
374
Reaction score
489
Location
USA
i5-8500 CPU version of Deepstack

I'm using the combined (Day) and dark (Night) and thought I was doing good until I noticed my detection times going up. I tried to get my detection times down but I must be in a mental block as my times keep going up...LOL. Take a look and please point out the obvious. And why it decided that the 80% detection was better than the 91% analysis is beyond me.

View attachment 129193

View attachment 129194

View attachment 129199

View attachment 129196

View attachment 129203

View attachment 129198

View attachment 129200
Our systems couldn't be a more exact match: same CPU (and I also run the CPU only DeepStack installation), same cameras, same substream settings, same medium setting for photo size on the Global Ai settings page. Yet my analysis times are dramatically lower, on the order of 90-350ms (per photo) generally. The only thing that stands out to me (and I could be wrong) is the syntax that insures that the default model isn't used at all: yes, I noticed you unchecked it in the Global AI dialog box, as did I, but I also include the "objects:0" in each AI trigger dialog. Also, why not just eliminate the references to the dark model on the profiles that won't use it (Daytime) and only use the "combined" model there?

Which version of DeepStack (Sept 2021 or early 2022)? I run the (much maligned) early 2022 version, but haven't had any problems with it so far.

I am not at the console at the moment, but could help later if you have any other comparisons you want to do.

Edit: I see your reboot helped tremendously...we cross posted.
 

jrbeddow

Getting comfortable
Joined
Oct 26, 2021
Messages
374
Reaction score
489
Location
USA
I am curious though: why run DeepStack on top of the built-in camera AI triggers? I consider those considerably more reliable than the BI motion detection triggers, and do the opposite: I run both types, but DS analysis only on the conventional motion triggers to filter out some of the noise (shadows, headlights across the parked cars in my driveway, etc..).
 

105437

BIT Beta Team
Joined
Jun 8, 2015
Messages
2,054
Reaction score
954
I have noticed BI presenting the lower percentage several times as well.


Sent from my iPhone using Tapatalk
I always thought as soon as BI sees the percentage threshold being reached by Deepstack object detection, it alerts and stops considering other images. This would not be the case if you include a cancel object that doesn't exist in the model.
 

Sybertiger

Known around here
Joined
Jun 30, 2018
Messages
4,717
Reaction score
13,620
Location
Orlando
I always thought as soon as BI sees the percentage threshold being reached by Deepstack object detection, it alerts and stops considering other images. This would not be the case if you include a cancel object that doesn't exist in the model.
I would think that BI would build a list (percentages) during the evaluation period then pick the best one and if it meets/exceeds the threshold then it would go with that one. If DS runs 3 evaluations and positively reports a car detection each time (i.e. 65%, 80%, 70%) then I would have thought BI would report the 80%.
 

105437

BIT Beta Team
Joined
Jun 8, 2015
Messages
2,054
Reaction score
954
Last edited:

Sybertiger

Known around here
Joined
Jun 30, 2018
Messages
4,717
Reaction score
13,620
Location
Orlando
@MikeLud1 You're working with color at night. The scenes I have are B&W since there's nowhere nearly enough light for color even on a 5442. The headlight bloom, even with HLC at 100 is quite strong and there's only a frame or two where an actual vehicle shows in the frame without being obscured by the headlights. That's one of the things about models that can be problematic, they are based on nice images under the best conditions and probably shot with an SLR to boot.
You are probably referring to pics like these. All come from 5442 cams that would not be able to operate in color for my situation. The dark model could not identify these. Typically, I see that black/dark colored vehicles are difficult for the dark model to detect although you can see a white police SUV in one pic was missed, maybe due the the reflective decals. These were all triggered by IVS in the 5442 cams for human/vehicle so we know the cams AI can detect them.

1653744431260.png
1653744535869.png
1653744596471.png
1653744721527.png
 

sebastiantombs

Known around here
Joined
Dec 28, 2019
Messages
11,511
Reaction score
27,696
Location
New Jersey
You're lucky with broadside shots and I would think that with a little tinkering DS using combined and dark would pick those up quite easily. The ones I get are much worse than those and I do get detections about 5% on one camera, cars west and 95%, or better, on cars east. Cars East has an advantage from a streetlight being in the scene providing better illumination.

cw 00-19.JPGcw 23-52.JPG
 
Top