Hi Experts.
Do we have time consumption bench mark for IWRL6432 People counting demo?
Typically how long will processing chain/tracking/classification take to finish processing for each of these blocks?
Thanks
Ken
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi Experts.
Do we have time consumption bench mark for IWRL6432 People counting demo?
Typically how long will processing chain/tracking/classification take to finish processing for each of these blocks?
Thanks
Ken
Hi Ken,
We actually print this out in the stats TLV. You can enable this in the guiMonitor CLI command.
Best,
Nate
Hello Ken.
When the classification module is disabled (in the cfg file as explained in the tuning guide) and the default chirp configs in the SDK are used, the entire processing chain (detection and tracker) takes ~30-35ms for 3 tracks (depending on the size of point cloud, etc.). Each additional track needs ~0.5ms additional processing time.
When the classification is enabled:
- For the 2-layers CNN model, we expect ~3ms additional processing time per track
- For the 3-layers CNN model, we expect ~15ms additional processing time per track.
Here, 2-layers or 3-layers CNN model can be configured in compile time.
Regards.
Muhammet