Go to documentation repository
Documentation for Axxon One 2.0. Documentation for other versions of Axxon One is available too.
Previous page Next page
On the page:
Configuring the detector
To configure the Neural counter detector, do the following:
- Go to the Detectors tab.
Below the required camera, click Create… → Category: Retail → Neural counter.
By default, the detector is enabled and set to count the number of objects in a specified area using a neural network.
If necessary, you can change the detector parameters. The list of parameters is given in the table:
| Parameter | Value | Description |
|---|---|---|
| Object features | ||
| Record mask to archive | Yes | By default, the recording of the mask to the archive is disabled. To record the sensitivity scale of the detector to the archive (see Displaying information from a detector (mask)), select the Yes value |
| No | ||
| Video stream | Main stream | If the camera supports multistreaming, select the stream for which detection is needed |
| Other | ||
| Enable | Yes | By default, the detector is enabled. To disable, select the No value |
| No | ||
| Name | Neural counter | Enter the detector name or leave the default name |
| Decoder mode | Auto | Select a processing resource for decoding video streams. When you select a GPU, a stand-alone graphics card takes priority (when decoding with Nvidia NVDEC chips). If there is no appropriate GPU, the decoding will use the Intel Quick Sync Video technology. Otherwise, CPU resources are used for decoding |
| CPU | ||
| GPU | ||
| HuaweiNPU | ||
| Number of frames processed per second | 1 | Specify the number of frames for the detector to process per second. The value must be in the range [0.016, 100] Note The default values (3 output frames and 1 FPS) mean that the Neural counter analyzes one frame once per second. If the Neural counter detects the specified number of objects (or more) on 3 frames, an event from the detector is generated. |
| Type | Neural counter | Name of the detector type (non-editable field) |
| Advanced settings | ||
| Detected objects | Yes | By default, detected objects aren't highlighted in the preview window. If you want to highlight detected objects, select the Yes value |
| No | ||
| Neural network file | If you use a custom neural network, select the corresponding file Attention!
| |
| Number of measurements in a row to trigger detection | 3 | Specify the minimum number of frames on which the detector must detect a violation to generate an event. The value must be in the range [1, 20] |
| Selected object classes | If necessary, specify the class of the detected object. If you want to display tracks of several classes, specify them separated by a comma with a space. For example, 1, 10.
| |
| Scanning window | Yes | If detection of small objects or objects in areas far away from the camera is ineffective, you can use the scanning mode. The scanning mode doesn’t provide absolute detection accuracy, but it can improve detection performance. To enable the scanning mode, select the Yes value (see Configuring the scanning mode) |
| No | ||
| Scanning window height | 0 | The height and width of the scanning window are determined according to the actual size of the frame and the required number of windows. For example, the real frame size is 1920×1080 pixels. To divide the frame into four equal windows, set the width of the scanning window to 960 pixels and the height to 540 pixels |
| Scanning window step height | 0 | The scanning step determines the relative offset of the windows. If the step is equal to the height and width of the scanning window respectively, the segments will line up one after another. Reducing the height or width of the scanning step will increase the number of windows due to their overlapping each other with an offset. This will increase the detection accuracy, but will also increase the CPU load. Attention! The height and width of the scanning step must not be greater than the height and width of the scanning window—the detector won't operate with such settings. |
| Scanning window step width | 0 | |
| Scanning window width | 0 | The height and width of the scanning window are determined according to the actual size of the frame and the required number of windows. For example, the real frame size is 1920×1080 pixels. To divide the frame into four equal windows, set the width of the scanning window to 960 pixels and the height to 540 pixels |
| Basic settings | ||
| Detection threshold | 30 | Specify the Detection threshold for objects in percent. If the recognition probability falls below the specified value, the data is ignored. The higher the value, the higher the accuracy, but some events from the detector may not be considered. The value must be in the range [0.05, 100] |
| Mode | CPU | Select a processor for the neural network operation (see Hardware requirements for neural analytics operation, Selecting Nvidia GPU when configuring detectors). Attention!
|
| Nvidia GPU 0 | ||
| Nvidia GPU 1 | ||
| Nvidia GPU 2 | ||
| Nvidia GPU 3 | ||
| Intel NCS (not supported) | ||
| Intel HDDL (not supported) | ||
| Intel GPU | ||
| Intel Multi-GPU | ||
| Intel GPU 0 | ||
| Intel GPU 1 | ||
| Intel GPU 2 | ||
| Intel GPU 3 | ||
| Huawei NPU | ||
| Number of alarm objects | 5 | Specify the number of objects at which an event occurs. The value must be in the range [0, 100] |
| Detection neural network | Person | Select the detection neural network from the list. Neural networks are named taking into account the objects they detect. The names can include the size of the neural network (Nano, Medium, Large), which indicates the amount of consumed resources. The larger the neural network, the higher the accuracy of object recognition |
| Person (top-down view) | ||
| Person (top-down view Nano) | ||
| Person (top-down view Medium) | ||
| Person (top-down view Large) | ||
| Vehicle | ||
| Person and vehicle (Nano) | ||
| Person and vehicle (Medium) | ||
| Person and vehicle (Large) | ||
| Trigger to | Greater than or equal to threshold value | Select when you want to generate an event. The Neural counter will generate events from the threshold value set in the Number of alarm objects field |
| Less than or equal to threshold value | ||
| Change in readings | ||
By default, the entire frame is the detection area. In the preview window, you can specify the detection areas using the anchor points 
(see Configuring a detection area).
Note
- For convenience of configuration, you can "freeze" the frame. Click the
button. To cancel the action, click this button again. - The detection area is displayed by default. To hide it, click the
button. To cancel the action, click this button again.
To save the parameters of the detector, click the Apply 
button. To cancel the changes, click the Cancel 
button.
Configuring the Neural counter detector is complete. It is possible to display the sensor and the number of objects in the monitored area in the Surveillance window on the layout (see Displaying the number of detected objects).
Example of configuring the Neural counter detector for solving typical tasks
By default, the Neural counter is set to detect objects with a speed less than 0.3 m/s:
| Parameter | Value |
|---|---|
| Other | |
| Number of frames processed per second | 1 |
| Advanced settings | |
| Number of measurements in a row to trigger detection | 3 |
| Neural network file | Path to the *.ann neural network file. You can also select the value in the Detection neural network parameter. In this case, this field must be left blank |
| Basic settings | |
| Detection threshold | 30 |
To solve tasks in which object speed differs from 0.3 m/s, you must increase Number of frames processed per second or/and decrease Number of measurements in a row to trigger detection. You must select the values empirically depending on the task conditions.
Overview
Content Tools