Stop analyzing when confirmed

[IconBycon]

I'm trying to get the AI settings to stop analyzing if one of the "To confirm" objects is found.

The way it works now is, it keeps checking each of the post trigger images, no matter what, and that is wasting time and resources in my case.

Is there a way to achieve what I need?

 

[Bruce_H]

If you click the help button you will find this tidbit

Hot objects may be specified in the to confirm box to immediately confirm the alert and
then cancel any outstanding analyses. For this, the confidence must begin with a 0, such as
person:0 or person:080.

 

[OSU_BuckeyesFan]

If you click the help button you will find this tidbit

Hot objects may be specified in the to confirm box to immediately confirm the alert and
then cancel any outstanding analyses. For this, the confidence must begin with a 0, such as
person:0 or person:080.

So if person:080 is in the to confirm box, once it has 80% confidence that it truly is a person, all the rest of the analyses? What about the min confidence % box, how is this still used?

 

[Bruce_H]

I only know what is in the help file, which is were I always look initially, but I would think that the person:080 would override that setting, but that is just an educated guess on my part!

 

[IconBycon]

I'll give it a test, and report soon.

Thanks!

 

[IconBycon]

If you click the help button you will find this tidbit

Hot objects may be specified in the to confirm box to immediately confirm the alert and
then cancel any outstanding analyses. For this, the confidence must begin with a 0, such as
person:0 or person:080.

So I tried what you suggested and it seems to work great...
But only on some of the cameras, and on some cameras it did make any difference and it behaved like before.

I'm seeing all this in the AI analysis.

There must be something or a prerequisite that needs to be in place, that is not allowing this to work, just can't figure out what it is.

Any ideas are welcomed.

 

[OSU_BuckeyesFan]

This made a big difference in PushOver notifications, with testing this afternoon I'm now getting my mobile notifications in 1-3 seconds.

 

[IconBycon]

As you can see in the highlighted, I set the confirm to person:080
however, even though it was confirmed @ T-2565 and many times after, it kept analyzing until T+933

Any idea how to make it stop analyzing when confirmed?

 

[OSU_BuckeyesFan]

As you can see in the highlighted, I set the confirm to person:080
however, even though it was confirmed @ T-2565 and many times after, it kept analyzing until T+933

Any idea how to make it stop analyzing when confirmed?

Your using ipcam-combined and ipcam-dark, what are you trying to detect? I use ipcam-general and seems to work well for people and vehicles. I would also lower your post-trigger images and see if that helps.

 

[IconBycon]

Your using ipcam-combined and ipcam-dark, what are you trying to detect? I use ipcam-general and seems to work well for people and vehicles. I would also lower your post-trigger images and see if that helps.

The weird thing is, I have the same setup with ipcam-combined and ipcam-dark on other cameras, with even more post-trigger images (which are very much needed) and it works great and stops when confirmed.

 

[Christikfa]

Interesting, im testing this at the moment and its only stopping after the first "person" detection if i use ipcam-general. The second i switch to Dark or combined its scanning more images.

Im using person:060 in the to confirm box.

 

[Spiro Chekano]

I just done some testing of this and it look like it is not cancelling on the pre-trigger images looking at the screen shot you have 10 or 11 pre-trigger and also it will not cancel if images are send to fast like in this example you need around 700ms to analyse one image and you are sending every 250ms image to be analysed

As you can see in the highlighted, I set the confirm to person:080
however, even though it was confirmed @ T-2565 and many times after, it kept analyzing until T+933

Any idea how to make it stop analyzing when confirmed?

 

[slabbel]

I just done some testing of this and it look like it is not cancelling on the pre-trigger images looking at the screen shot you have 10 or 11 pre-trigger and also it will not cancel if images are send to fast like in this example you need around 700ms to analyse one image and you are sending every 250ms image to be analysed

Release 5.9.9.33 resolves this issue affecting models with mixed case labels...

 

[PeteJ]

...glad I found this post. In 5.9.9.33 it seems to cancel very aggressively, my ALPR catches are down 50% because it no longer waits for the vehicle to get into frame.

 

[slabbel]

...glad I found this post. In 5.9.9.33 it seems to cancel very aggressively, my ALPR catches are down 50% because it no longer waits for the vehicle to get into frame.

@PeteJ, when using the CodeProject.AI-Custom-IPcam-Models license-plate model for example, try using DayPlate:30, NightPlate:30 in "To confirm" to continue AI analysis. DayPlate:030, NightPlate:030 will cancel AI analysis as soon as the object is detected with 30% or higher confidence

 

[PeteJ]

@PeteJ, when using the CodeProject.AI-Custom-IPcam-Models license-plate model for example, try using DayPlate:30, NightPlate:30 in "To confirm" to continue AI analysis. DayPlate:030, NightPlate:030 will cancel AI analysis as soon as the object is detected with 30% or higher confidence

Thanks for the suggestion, I'll give it a shot.

I moved back to .29 from .33 and it's no longer canceling the alerts. I added "confirm: *" to the config (it was blank before) and "fire only on confirmed" (was set to always). I am not sure if these were the needed changes, or if .29 is good.

 

[PeteJ]

@slabbel thank you for the suggestion, I played around with the setting and adding "*:30" to confirm seems to be helping a lot. It's been less than an hour with this setting, but so far, it seems to have fixed my issue, which was it was canceling the alert for no apparent reason. This seems to force it get at least into the post trigger images (whereas before it would essentially stop at the last pre-trigger image). I'm going to keep an eye on this and see if it holds. Thanks again!

 

[slabbel]

@slabbel thank you for the suggestion, I played around with the setting and adding "*:30" to confirm seems to be helping a lot. It's been less than an hour with this setting, but so far, it seems to have fixed my issue, which was it was canceling the alert for no apparent reason. This seems to force it get at least into the post trigger images (whereas before it would essentially stop at the last pre-trigger image). I'm going to keep an eye on this and see if it holds. Thanks again!

View attachment 217614

It's good to hear that it's working - A higher confidence level should result in more images processed. The AI Inspector (Ctrl+double click on any AI confirmed clip in the Clips list) provides useful information to dial in AI processing settings.

 

[PeteJ]

It's good to hear that it's working - A higher confidence level should result in more images processed. The AI Inspector (Ctrl+double click on any AI confirmed clip in the Clips list) provides useful information to dial in AI processing settings.

Yeah, that was the issue. It would just cancel before getting to the image with the plate. Before the change I made, it was very common to see this:



It would process the pre-trigger images and give up before getting to the post trigger.

 

[slabbel]

Yeah, that was the issue. It would just cancel before getting to the image with the plate. Before the change I made, it was very common to see this:

View attachment 217635

It would process the pre-trigger images and give up before getting to the post trigger.

@PeteJ Are you running against multiple AI models simultaneously? Images are sent every 200ms, each with a round trip of 7-9 seconds. This in itself will affect the number of images analysed due to the delayed AI results returned to BI