[randyrand]

It should be a smaller problem than with the Kinect. The Kinect is not true time of flight like you said, whereas ouster is. If you know when photons actually arrived you know the first light pulse you receive is the one you care about, and the later longer paths you can ignore. The Kinect conflates these.

So, I don't think it will be a problem for them but it is something they need to consider when designing their DSP.

[nomel]

This makes me wonder how any of these systems handle the reflective surfaces of cars.

So you hit a chrome bumper or maybe a glossy black point. The later pulses could arrive at a much higher amplitude.

[CamperBob2]

They don't care about the amplitude, just the timing.

[nomel]

They're measuring the time to some amplitude at the sensor. There must be some amplitude threshold, otherwise would trigger on noise.

[CamperBob2]

The reality is somewhat more complicated than that. Signal processing at this level is statistical in nature, so the threshold itself is effectively timing-driven.

Hard to explain in a few words, but the principle of the lock-in amplifier is a good place to start.

[nomel]

I still don't understand how there is no threshold based on amplitude (correlation or not). Something like mist would show up as a noise floor, a speck of dust (that hangs around for long enough) may be one peak, a mirror another, and an object seen in the mirror will be another. You will have multiple peaks that may stay around longer than others and, but there will still be peaks, one of them being the "true" surface.

I don't see how there is no threshold.