Positional tracking sample issues

[stereolabs]

Positional tracking sample issues

[adujardin]

Hi,
If I understand correctly there is a performance hit when using the ZED in USB (not SVO file) and/or possibly using the graphical interface in docker?

• ** I had also recorded an svo file and ran positional tracking on it, there was no loss at all.

Does this mean you tested an SVO file in docker with GUI and it worked as well as natively?

To be honest we didn't thoroughly bench the performances using Docker, but the fact that it works reasonably well but not completely is quite puzzling 😕

To check if the camera stream is identical in docker you can run the Diagnostic app (/usr/local/zed/tools/ZED\ Diagnostic ) within a Docker image to check for frame drops or any image issues.
You could also display the depth to visually check any potential obvious defect using ZED Depth Viewer.

Also, do your CPU and GPU usage appears to be similar when running the same sample in docker and natively? I'm thinking the extra load in docker could drop some frame in live mode.
You could actually test this by running the sample with a SVO in real-time mode. For this you have to set the InitParameters.svo_real_time_mode to true.

[orshefi]

I don't know what changed but the issue went away.

Also, I did run ZED Diagnostics, it runs with flying colors but alerts me on lens smudge.
You can imagine that I relentlessly tried to clean the lenses and nothing seems to solve it.
You should also know that this issue won't appear on the same container outside the docker container.

Any Ideas?

[github-actions]

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