Closed haavarpb closed 2 years ago
Hi @haavarpb,
Thanks for reaching out to us.
Indeed, a detected and tracked object should have a constant ID over time (you need to make sure the enable_tracking
parameter is set to True
). However, "ID switching" can indeed happen sometimes, and as you said it can be dependent on various conditions and parameters.
If it is possible for you, could you please send us an SVO where this phenomenon happens ? You can send it to support@stereolabs.com if you feel more comfortable
Thanks
Hi, thanks for coming back to me.
I will come back to you with a recording if I come across something similar again, but for now, after tweaking the settings a bit and moving the camera to another position, it seems to have stabilized. Perhaps lighting also have an impact for tracking?
Regards
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment otherwise it will be automatically closed in 5 days
Preliminary Checks
Description
Hi,
I am posting this here as I am using the python API, but I think this is issue is independent of the API as it is tied to using the core functionality.
I am using ZED 2 for tracking human skeletons, and I notice that the object id's can change over time for the same object. Documentation is a bit limited, but in the object detection module on your site it is described that the object id will remain constant for a detected object. I have looked into using the uuid field instead, but those are constantly changing too. Is this intended behaviour? Is there something I can do to reduce the chance of the SDK recognizing a tracked object as a new object?
Regards, Håvard
Steps to Reproduce
Expected Result
Object ID remains constant for a detected object
Actual Result
Object ID sometimes changes
ZED Camera model
ZED2
Environment
Anything else?
Perhaps expand documentation on topics around object detection: how it works, under which conditions and parameters that have impact on the quality of tracking results.