Please provide complete information as applicable to your setup.
• Hardware Platform (Jetson / GPU) TX2 • DeepStream Version5.01
**• JetPack Version (valid for Jetson only)**4.4 • TensorRT Version • NVIDIA GPU Driver Version (valid for GPU only) • Issue Type( questions, new requirements, bugs) • How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing) • Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)
Hi,
When dealing with the over-crowding object level data which is vector std::string ocStatus, I found if I didn’t enable/configuration an area of [roi-filtering-stream] which overlapped of the [overcrowding-stream], I cannot get the correct OverCrowding labels. But I can get correct frame level ocStatus even if I disable the ROI area.
Has anybody encountered the same issue?
In my opinion, the configuration of roi-filtering and over-crowding are independent of each other. Is it a wrong idea or I missed something?
When I enabled roi-filtering(for area1), I could get the frame-level over-crowding alarm message as “Overcrowding status area2 =1” as well as object-level message as “object xxxx is in overcrowding area2 object yyyy is in overcrowding area2 …”
But if I disabled roi-filtering(for area1), I could still get frame-level alarming “Overcrowding status area2 =1”, but no object-level message any more.
The problem is if I want get object-level oc info, I have to setup and enable a roi-filtering area which encompasses the oc area.