4
$\begingroup$

I'm using Stereolabs ZED camera for my computer vision project. I did a small research about several sensors on the market and ultimately we decided to go with the ZED Camera.

However I'm finding that the precision of the camera isn't that great. And the Point Cloud takes too much storage space. Anyone found the same problems? And if so, how did you managed them?

$\endgroup$

closed as primarily opinion-based by Mark Booth Aug 12 '18 at 9:25

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • $\begingroup$ Can you state more explicitly what "good precision" would mean for you? What are your constraints in storage space (and why can't you just add more)? $\endgroup$ – Ian Apr 29 '16 at 18:40
  • $\begingroup$ On Stack exchange we prefer practical, answerable questions based on actual problems that you face, so questions which solicit experiences, ask for a list of approaches or a subjective recommendation on a method (for how to build something, how to accomplish something, what something is capable of, etc.) are off-topic. Please take a look at How to Ask & tour for more information on how stack exchange works. $\endgroup$ – Mark Booth Aug 12 '18 at 9:25
4
$\begingroup$

I don't know what you mean by "precision" and how do you measure it. The sensing accuracy will probably go back to the camera calibration precision and the stereo matching algorithm used. If they ship the device "calibrated" then no one knows what happened after the camera was calibrated in factory and before you got it (mechanical shock, temperature swings) - so you better re-calibrate it yourself (with OpenCV, Matlab etc.).

If you are interested in the depth accuracy from stereo vision itself then see the following equation:

dz = (z^2 * de) / (f * b)

where dz is the depth error in meters, z is the depth in meters, de is the disparity error in pixels, f is the focal length of the camera in pixels and b is the camera baseline in meters. The main message of the equation above is that the depth error grows with the square of depth (distance from camera) itself.

You get better depth accuracy the bigger f and b are. Given the ZED camera has both of these relatively small - baseline is "just" 120mm and f will be pretty small given the quite large FOV of 110 degrees in diagonal (f is "FOV inverted", so wider FOV gives smaller f). What is good for you is the high resolution which should mean smaller disparity error which could compensate for the bad f and b values.

Regarding point cloud size - this goes back to the rather high sensor resolution of the ZED camera. High resolution may not really be needed for stereo because 1) the stereo matching takes long time 2) the point cloud is huge 3) the depth accuracy may not be much better since the disparity is usually determined with sub-pixel precision anyways. So see what angular resolution you need for your project - you can calculate how many pixels per angle (horizontal, vertical) your camera (=sensor+lens) has. If that is too much, you can lower the angular resolution (=lower sensor resolution) without harming your computer vision results.

Hope this helps!

$\endgroup$
2
$\begingroup$

For improved precision try calibrating the camera with the Stereo Camera Calibrator app in MATLAB.

As far as the memory taken up by the point cloud, that really depends on how many points you have. You can always try reducing the resolution of the cameras, downsampling the point cloud itself, and/or using a lower precision data type to store the coordinates.

$\endgroup$

Not the answer you're looking for? Browse other questions tagged or ask your own question.