I’m using ZED 2i and ZED Box Xavier-NX for people detection and depth obstacle detection. I get this error very often and it’s causing my application to not detect people properly. When I assign a certain person a specific role in my application (based on his id) and I get this error, then that person is gone (gets a different id) and my computation can’t continue. However, when I disable the depth obstacle detection then I still get this error, but it’s drastically less frequent.
Any advice on how to fix this? Or at least what’s causing it?
When the person that you are tracking gets out of the scene, or it’s occluded, it exits the tracking queue, and when a new detection occurs a new ID is assigned to it.
In order to re-identify it, you must enable the “batching” feature, this example is a good starting point:
I’m afraid that this doesn’t solve my problem. The person I’m tracking is standing right in front of the camera and there is no obstacle or occlusion. The error that I mentioned in the intro is causing the problems. The tracking is working just fine otherwise but when the error pops up then the tracked person is re-identified without any reason. Can I prevent this somehow?
Hi @Gaba
I asked the team about your error and they replied that it’s related to the received data and to the elapsed time between the frames.
To recover from the error a new ID is assigned to the tracked object.
Can you please record an SVO in the same conditions in order to try to replicate and debug the issue in our laboratories?
The SVO must be long a few minutes, you can send it to support@stereolabs.com