Periodic Scan

[sumps]

I had to roll back to 6.0.0.1 ..
after the change in periodic scan in 6.0.1.13 I had noticed thatI would miss some alerts of vehicles driving by the camera..viewing the clip in the AI inspector it would show that theca's that were parked on the street were correctly identified as static (yellow box), however it would also mark the vehicle moving across the screen as static as well and would not trigger an alert ..This never occurred with the old periodic scan system..I have no idea how to fine tune this to try and figure out why a moving object is seen as static especially since its random and the new periodic scan no longer has any configuration aside from how often it scans (set at default 120 seconds)

Have anyone else experiencing this?

 

[The Automation Guy]

I would suggest moving to the latest version (6.0.1.28). .13 is pretty old given the fast pace of bugs being fixed and new features/functionality being added, including some specifically related to the periodic scan function (according to the release notes).

 

[sumps]

After almost a week back on 6.0.0.1 and having 0 issues with static object detection, I updated to the latest version 6.0.2.0 and only after a few hours the system started detecting moving cars and even people as static objects ... Not sure what is causing this, Periodic AI scanning settings are at their default timings (no real documentation on what the "scan at least" and "but no faster than" settings do) .. something has definitely changed for the worse unfortunately ... attached image shows a person walking that is marked as static (Yellow box) by the primary scan .. very odd behaviour

 

[Vettester]

I updated to the latest version 6.0.2.0 and only after a few hours the system started detecting moving cars and even people as static objects .

Which AI model are you using?

 

[sumps]

Which AI model are you using?

Typically use blue onyx, however in this particular situation I was using the built in AI with the yolo8s model ... I've experienced the same issue regardless of the AI I am using

 

[Vettester]

I've experienced the same issue regardless of the AI I am using

The reason I was asking is that I can't get it to work either and was hoping it was a model related issue.

 

[jrbeddow]

I've seen this too, even with periodic AI scanning turned off: my temporary/provisional workaround has been to lengthen the timings between each AI scan. I was originally running either 333ms or 500ms timings, but I am primarily concerned with detection of people and slow moving (in the process of parking) vehicles, so I have changed these to 750ms or 1 second timings now. My theory is that there isn't enough movement in the "bounding box" surrounding these object detections at relatively short/fast timings, and it has helped in my situation. Obviously these timings won't work for faster moving vehicles and/or LPR.

This might be worth sending questions to Ken though if you are consistently having issues in this area.

 

[MikeLud1]

My theory is that there isn't enough movement in the "bounding box" surrounding these object detections at relatively short/fast timings, and it has helped in my situation.

I agree with your theory.

 

[jrbeddow]

I agree with your theory.

OK, it's great to hear that someone with significant experience with the AI models agrees, but some questions remain. Why does the BI (built-in) AI respond so differently compared to CodeProject AI in this regard? I essentially never had this issue with CPAI.

 

[MikeLud1]

Why does the BI (built-in) AI respond so differently compared to CodeProject AI in this regard?

Because Ken changed the logic for static objects, I think he made it worst then the old logic

 

[jrbeddow]

Yes, I had seen that too. It's a shame it is worse than before, but I suspect you might be better positioned to persuade him of that than the average user, given your experience in this area.

 

[looney2ns]

The more that email him about this, the better.