Multi-Channel Object Detection Yolov3 C++ Demo¶
This demo provides an multi-channel inference pipeline for YOLO v3 Object Detection network.
Other demo objectives are:
Up to 16 cameras as inputs, via OpenCV*
Visualization of detected objects from all channels on a single screen
How It Works¶
On startup, the application reads command line parameters and loads the specified networks. The Yolo v3 Object Detection network is required.
By default, Open Model Zoo demos expect input with BGR channels order. If you trained your model to work with RGB order, you need to manually rearrange the default channels order in the demo application or reconvert your model using the Model Optimizer tool with the
--reverse_input_channels argument specified. For more information about the argument, refer to When to Reverse Input Channels section of Embedding Preprocessing Computation.
Preparing to Run¶
For demo input image or video files, refer to the section Media Files Available for Demos in the Open Model Zoo Demos Overview. The list of models supported by the demo is in
<omz_dir>/demos/multi_channel_object_detection_demo_yolov3/cpp/models.lst file. This file can be used as a parameter for Model Downloader and Converter to download and, if necessary, convert models to OpenVINO IR format (*.xml + *.bin). You can also review OpenVINO article to see how to convert the YOLO V3 and tiny YOLO V3 into IR model and execute this demo with converted IR model.
An example of using the Model Downloader:
omz_downloader --list models.lst
An example of using the Model Converter:
omz_converter --list models.lst
Refer to the tables Intel’s Pre-Trained Models Device Support and Public Pre-Trained Models Device Support for the details on models inference support at different devices.
Running the demo with
-h shows this help message:
[-h] Print a usage message -i A comma separated list of inputs to process. Each input must be a single image, a folder of images or anything that cv::VideoCapture can process. [-loop] Enable reading the inputs in a loop. [-duplicate_num] Multiply the inputs by the given factor. For example, if only one input is provided, but -duplicate_num is set to 2, the demo will split real input across channels, by interleaving frames between channels. -m <path> Path to an .xml file with a trained model. [-d <device>] Specify a target device to infer on (the list of available devices is shown below). Default value is CPU. Use "-d HETERO:<comma-separated_devices_list>" format to specify HETERO plugin. Use "-d MULTI:<comma-separated_devices_list>" format to specify MULTI plugin. The application looks for a suitable plugin for the specified device. [-n_iqs] Frame queue size for input channels [-fps_sp] FPS measurement sampling period between timepoints in msec [-n_sp] Number of sampling periods [-t] Probability threshold for detections [-no_show] Don't show output. [-show_stats] Enable statistics report [-real_input_fps] Disable input frames caching, for maximum throughput pipeline [-u] List of monitors to show initially.
To run the demo on CPU, with one single camera, use the following command:
./multi_channel_object_detection_demo_yolov3 -m <path_to_model>/model.xml -d CPU -i 0
Video files will be processed simultaneously.
Input Video Sources¶
General parameter for input source is
-i. You can run the demo on web cameras and video files simultaneously by specifying:
-i <webcam_id0>,<webcam_id1>,<video_file1>,<video_file2> with paths to webcams and video files separated by a comma. To run the demo with a single input source (a web camera or a video file), but several channels, specify an additional parameter,
duplicate_num, for example:
-duplicate_num 4. You will see four channels. With several input sources, the
-duplicate_num parameter will duplicate each of them.
Below are some examples of demo input specification:
To see all available web cameras, run the
ls /dev/video\* command. You will get output similar to the following:
user@user-PC:~ $ ls /dev/video\* /dev/video0 /dev/video1 /dev/video2
You can use
-i option to connect all the three web cameras:
To connect to IP cameras, use RTSP URIs:
The demo uses OpenCV to display the resulting frames with detections rendered as bounding boxes. The demo reports:
FPS : average rate of video frame processing (frames per second).
Latency : average time required to process one frame (from reading the frame to displaying the results).
You can also enable more detailed statistics in the output using the
-show_stats option while running the demos. You can use these metrics to measure application-level performance.