Missing range estimates in range.csv

There’s a few missing values for the range estimates.

For example:

Is this intentional? Should we be able to deal with missing range values?

Hi @mohsaad, yes, this is intentional. The idea is that in reality the rangefinder does not always get a reading.

1 Like