- Edited
Hi we have additional question about this issue.
we tested depth performance with OAK-D and OAK-D Pro. But based on our test results, OAK-D Pro is worse than OAK-D now.
<the result of OAK-D depth test>
actual measurement | measurement | standard deviation (last 30 data) unit: m
0.4 0.3996 0.0004
0.8 | 0.7984 | 0.0010
1.2 | 1.1994 | 0.0028
1.6 | 1.5965 | 0.0056
2.0 | 1.9874 | 0.0085
2.5 | 2.4747 | 0.0109
3.0 | 2.9966 | 0.0144
<the result of OAK-D-Pro depth test>
actual measurement measurement standard deviation (last 30 data) unit: m
0.4 | 0.4145 | 0.0004
0.8 | 0.8587 | 0.0016
1.2 | 1.3298 | 0.0026
1.6 | 1.8337 | 0.0059
2.0 | 2.3776 | 0.0084
2.5 | 3.1465 | 0.0196
3.0 | 3.9321 | 0.0334
So we tested OAK-D Pro with depth-preview.py.
<Bright environment>
<Without IR dot projector in a less bright environment>
<with IR dot projector in a less bright environment>
<ir dot projector>
I'm using depthai_ros noetic branch of gitgub, and I'm using stereo_inertial_node.launch from depthai_example package. But when i checked its hz(fps), it is working with 20hz. But we would expect 30 hz. i would like to cross-check it with you once more.
As a result of observing the depth for about 10 minutes at a specific distance (2m), it saw that the measured value gradually went down from 2.02m to 1.94m. do you have any solution for it?
i added all the back data for its investigation on the google drive. if you need anything more, please let us know we will follow up as soon as possible.
https://drive.google.com/drive/folders/1ECZGkdMZ8tsw4o2-hzUi-EzzWmKxVKS7?usp=share_link
Best regards,
Ryan.