3 ms·
No, it's like this: Radar, LIDAR, ultrasound: returning packets have X value, where X is run through a single algorithm to return depth. In the case of ultraso
by gamblor956 8y ago
No, it's like this:
Radar, LIDAR, ultrasound: returning packets have X value, where X is run through a single algorithm to return depth. In the case of ultrasound and radar, the strength of the return packet is generally directly proportional to depth (algorithmically). LIDAR systems might require an additional processing step depending on the type of LIDAR system used, since many systems use shifted-arrays or rotating frequencies.
Stereovision: returns two matrices of data (i.e., each image). Each matrix is run through edge-detection and object-detection algorithms, and the resultant data is then run through more algorithms to match and compare objects between the two images. Finally, once objects have been matched up, a parallax algorithm determines their 3d positioning. While this can all be done in hardware (i.e., ASICS), it's still multiple additional levels of processing that must be done before you can even get the data to the decision-making part of the system. Stereovision is thus always inherently laggier than a radar-based system when it comes to determining depth.
- ebg13 8y ago> Each matrix is run through edge-detection and object-detection algorithms, and the resultant data is then run through more algorithms to match and compare objects between the two images. Finally, once objects have been matched up, a parallax algorithm determines their 3d positioning. Where is your information coming from, and can you point me to a stereo algorithm that uses object detection?
- jeffreygoesto 8y agoRight, almost all stereo depth calculation is matching without object detection. Maybe doing both simultaneously counts? ;-) https://arxiv.org/abs/1902.09738 https://arxiv.org/abs/1902.09738
- pbreit 8y agoSure it’s laggier but with dedicated silicon that’s a non-issue. Fact is vision is more than adequate. And lidar is literally blind.
- underwater 8y agoThe problem is not lag, it's unpredictability. For example the white side of a truck trailer may have no distinguishing features, so in some situations the parallax-based depth algorithm returns incorrect information.
- ebg13 8y agoSure, and also that cameras only work if what they're looking at is sufficiently illuminated. And yet humans still drive based exclusively on stereopsis. The particular problem you mention is really a camera fidelity issue not a stereo issue, just like humans with poor eye function are also not allowed to drive.
- salty_biscuits 8y ago"the strength of the return packet is generally directly proportional to depth (algorithmically" Err, no it isn't. You send a tx pulse and correlate it with a rx pulse and use the time of flight and the wave speed to get a range. You need precise information about where the tx pulse was sent to turn the range into 3d point relative to the sensor. The correlation and orientation steps are algorithmic and fundamenally statistical. For ultrasound and radar you can put a code in the pulse to make matching them up easier (the pulse lengths are typically bigger than the resolution you require). All algorithms. All can and do go wrong. Old school stereo matching looks at cross correlation (or cross entropy) of image patches. If the cameras are orthorectified (translated with no rotation) then you just scan across the row of pixels to find the patch with the best match and how far across it is is proportional to the depth. Feature correspondence (with sift like features, very low level) might be used for getting relative rotation and translation info between the cameras for calibration and as a depth prior. People are doing the same sort of thing with NNs to get the depth map.