Use digital barriers on a Axis - UK iLids approved. IMHO it just works :)
Axis Video Analytics Are Weak
Published Oct 05, 2015 04:00 AM
*** **** **** * ******, ***** analytics *** ********** *** ************ *****.
***, **** *** ******** ***** *** "****** ** ****** ***** ********* ************" that **** **** ***** ***** [**** no ****** *********]. *************, ****'* ******* shows **** ****' ***** ********* *** weak. ** ****** **** *** ***** and *** ****** **** *** ****** and ***** ************ ($*** **** **** but **** **-*** ***** ************ *** available **** [**** ** ****** *********]).
******** ** ****' ******** ******,*** *, **** ***** ***** ******* **** been ******* ** **********. ** *** tests, ***** ***** *** *** ******** blowing ******, *****, ** **** ** *******, occasional ******** ** *** *.
** **** ***, ******** ****, **********-****, calm *** *******, ********** ******** ****** slowly **** ***** ***** ****** **** ********** and ********.
*********
**** ***** ***** ** ****.
***** ******* *** ** *** ******, but **** ***** ***** ********* ** reliably ****** ***-***** **********. **** ****** **** world **********, ***** ********* *** ***** negatives ****** *********** **** ***** ***** struggling ** ********* **** ** * real ***** ** ******, *****, *******, etc. ***** ******** *** *** **** severe ************ (******)******** ******* (******).
*********** *** **** ** ************ ** * cumbersome ***** ******* **** ***** ******** controls ** ******* **** ***** **** compensate *** ****, ****** ********, ***** largely ******* **** *************, *** ***** ioimage **** ******** ************* ***** *** calibration ** ******* ***********.
Market ****** / ***************
** *** *** **** ***** ***** unless *** *** ** ** ****** indoor ****** ** ****** ** ** least *** **** ** ******* ** the ***** ******** *** **** ** use **. ******* ****' ****** ******, Guard ***** ** *** '******'.
** ****** *********** ***** **** ** be ********** ** *** **** *********** and *** ********* ** ******** **. We ** *** *** **** ***** widely ****, ******* **** ** ******** to ***** ** *** ***** ******** apps.
Performance ******
** **** ******* ** ***** **** *** key ****** ********* **** ***** ***** performance, ********* ***** ***** ******, ****** activations, *** ****, ** **** *****:
***** ***********
****' *********, **** *** * ****** it, ****** **** ******** ***** *********** from *****, ********, *******, *** ***** vegetation. ** *** ***** *****, *** brush ** *** ***** **** ** the *** ** **** ** ******* by *** ******, ******* *********** *** size *** ***********. **** ******** ** far ** ** ************ ***** ***** activations ** *** ******** **** ** the *****.
***** *********, **** ** ******** *** ioimage *** *** ********** ***** ******** activations.
****** ***********
** *** *******, ******** ******** * tripwire ***** **** ***** ***** **** often *** ********. ** *** ***** below, *** ****** ****** **** *** detect *** ******* ** ** ****** until ** ** **** *** ****. Avigilon's *** ****** *** ***% ******** using **** **** *****.
** ******* ******, **** *** **** worse, **** **** ******* ******* **** than **% ** *** ****, ***** Avigilon *** ********** >**%. ** *** example *****, ******* *** ******* ***** seen ** ** ****** ***** ** running, *** ****** ***** ** ****** him **** ** ****** ******.
**** **** ** ***** ****, **** more **** ** ****** *** ******* as * ***** ******, ******** *********** issues **** *** ** ****** ** *** examples *****. *******, **** ***** *** trouble ********* ******* ********, ******* **** about **% ** *** ****.
** *****, ****** ********** ** ****** speeds **** ********, ** ****, **** with *** ******* ** **** ***** higher ******** ***** ** *** *****, reviewed ** **** *****:
********* *****
***** * ~**° ********** ***** ** view, ***** ***** ********* **** ******** at * ******* ***** ** ***** 175' ***** *** ***** ***** ****** *** day. **** ** ***** **% **** ******** than *** ******** *** ******, ***** covered ~***' ****.
**** **** **** ** *** ******* where ******** ********* *** ******** (>**%). Beyond ****, ******** ** ****** ******* speeds are **** ********** ******, ****** ********* spotty.
Setup *** ***********
**** ***** ***** ********** *********** *********** *** found ** ***** ******** ************, **** as *** *, ******** ** ****** calculate ******** *** ****** **** ** measuring ******* ** *** ***.
**** ******** ******* ******** ** **** process, **** *********** ***** ** *** measurements "** ********* ********* **** *** camera."
******** ** *****
******** ** *****, ***** **** ******** calibration (******** **** ***), ***** *** several *** *********** ** **** *******:
- ** ******* ****/***** ***** ******:****' *********** ************ *** ********* ** a ***** ******, **** ** ****** to ********* **** ** ******* *** screen ** **** ********** ******* ******** as ** ***** (**** * ** the ***** *****). **** *** **** it ********* ** ****** ************ ** the ***** *** *** ****** ** an ******, ******** ********.
- ***** ********* ** ********:**** **** * **** ** ******* objects, **** * ***** *** ** either *** ***** ********* ****, ***** can ******* *** **** ** *** object ***** ********. ***** **** * capital * ***** (**** * *****) to ******* *** ****** ****** ***** adjustment ** ****, ****** ** ****** to ****** ** *** *** *** bottom ** ** ******.
- ** ******** ***********:**** ******** **** ****** ** *******, not ******** *********** ***** ** ***** (and *****'* ****** *** ********). (**** C ** ***** *****)
- ** ******* ****:***** ******** * ******* ****** ***** is **** ** ****** ****** *********** of *** ******, ** **** ** exclude ******* ** *** ***. **** does ***.
************, **** ******** ** ****** ************ tools ** ***** *** ******** ** measurements, **** ** ****** ** ********, to ****** ************ *** ********. ***** and ***** **** ******* **** *******.
*******, **** ******** ** ******* **** settings ** ******* **. ***** **************. All ******* *** ********, ********** ** size/shape.
*********** *************
** *** ***** ***** ** *********** the **** *********** ******* *** *** issues ***** *****:
VMS ***********
*********, **** ***** ***** ** ******* to ****** *********** *** *** ****** or ***** ***** ****. ** ** likely **** ************ **** ** ******** in *** **** *** ******, **** Axis *******:
"**** ***** ***** **** ** ********* by **** ****** ******* *** ******* *** ********* ******* *** Salient ******* ******* **** *******’ ***** stream, ***** ********* ******* **** ******* direct ***********. ******* ** ******* ****., Exacq ************ *** ***** ** ******* to ** ********* ** *** *** of ****."
** ** ***, ***** *** ******* alarm ****** ** ********** **** ** the ***** *** ****** ** *** camera, ** **** ** *** *** of *** ****** *****. ***** *** set * ****** **** ** ********* motion **** ** *** **** ***** this **** *******, *********** ******** ** the ******** ****:
***** *** **** **** *** ****** notifications **** *** ****** ** ***** which ****** ****. **** ** ************ in *** ***** ***** ***** ***** the *********** ** ***** ***** **** Exacq, **** ***** **** ********** *** ********** overlaid **** **** *****.
Comments (9)
UI
Undisclosed Integrator #1
Oct 05, 2015UI
Undisclosed Integrator #2
Oct 06, 2015The analytics developed by Axis was informed to target a low-end segment of VCA, although a step up from their VMD and simple cross-line it was not to become a high-end VCA (yet at least). The argument was not to compromise their open platform by competing with the 3rd party higher-end VCA solutions that can run on their cameras.
What I'm a little bit surprised about is the price, I had anticipated that they were going to offer this for a much lower cost, more in line with their previous Cross Line Detection.
JH
John Honovich
Oct 06, 2015I think it is dangerous to offer analytics for a 'low-end segment of VCA'. It is very hard to determine how poorly the analytics will work in different scenarios, which makes it likely that they are deployed in conditions they cannot handle well, which makes customers frustrated and causes integrators to lose lots of money troubleshooting / trying to optimize.
Axis lead marketing claims for Guard Suite is "Robust and reliable indoor and outdoor detection" that "Protect and detect around the clock". If they really wanted it to be 'low-end', then they should have avoided such claims. As is, they have set expectations that they cannot meet.
UI
Undisclosed Integrator #2
Oct 06, 2015Yes, unfortunately marketing talk will almost always over-sell products.
As for targeting the low-end, that's what they did with the Cross Line (in my opinion). It seemed to perform rather well compared to its competitors in the tests you performed. But I guess their marketing language wasn't as bold then.
http://ipvm.com/report/analytics-rain-axis-bosch-sony
http://ipvm.com/report/camera-analytics-tested
I would personally be extremely reluctant to use the Axis Cross Line in any outdoor environment since the consequences of missed alarms and a high false alarm rate would be devastating to our costs and brand value.
It will however be interesting to see how well the new Axis analytics perform. Hopefully it is a step up from the old Cross Line and you seemed to think that it at least reduced the false-alarm rate somewhat compared to VMD 3.0. Perhaps it can perform good enough in ideal, sterile environments (as you mentioned in the test).
If you have time for it, it would be interesting to see how the latest Bosch-analytics compares with the new Axis as the latest Bosch should be much better than the old.
Similarly to the Bosch analytics (as well as just about any other VCA on the market that is actively developed), I think we'll see improved performance over time with the new Axis solution, the question is when (or if) it will be a good enough to use in non-ideal scenarios as well and whether it will be enough to be competitive towards the other camera manufacturers. Only time will tell...
Ethan Ace
Oct 06, 2015Axis Crossline definitely had more false alert issues than you see in Guard Suite. I recall headlights, shadows, and blowing leaves being bigger issues than even what you see here. Guard Suite is at least far less susceptible to the headlights/shadows.
That being said, Crossline also didn't seem to have the same rate of missed objects that Guard Suite does. That's likely because it detected everything as an object, like debris/headlights/shadows, so it was less choosy and less likely to drop an object once detected.
TW
Tyson Wetzel
Oct 06, 2015I would love to see an on-board analytic shoot between Pelco, Axis, Samsung, Bosch etc..
AB
Alexander Bonch
Oct 14, 2015The placement of bars for calibration in you tests (see the "Axis Perspective Calibration" Figure) is certainly wrong because bars should be normal to the ground plane. Otherwise the data essential for calibration will be inaccurate. This is best seen with bars 1 and 2 drawn over the two cars. The bars should go along the front door vertical edge (which is not at all "vertical" in the picture).
I don't know if Axis has made a note of this fact in its manual but no calibration is possible with bars drawn at random.
Ethan Ace
Oct 14, 2015The bars are not drawn at random. The bars you see on the cars were drawn along the door line from the roof to the ground as you point out. However, Axis snaps the lines to vertical after they're drawn, but they remain the same length. I measured the cars those lines were drawn on, as well, to be accurate.
The cars themselves don't appear level due to the angle of view. The FOV overall is level, though, as you can see the poles in the background are vertical.
Also, this scene was later recalibrated when I moved cameras back to this point for further testing.
For reference, Axis gives little guidance as to what is right/wrong in this calibration, nor any best practice in their manual.
AB
Alexander Bonch
Oct 14, 2015Thanks for your clarification. Really strange that Axis "snaps" the bars to vertical... No way to double check the bars had been drawn correctly.