Anyone experienced the type of systematic depth errors documented here?
We’re seeing similar effects, with depth reported up to 20cm off when near the edge of the field of view with a Persee. We can measure and correct for this by measuring and building a distortion correction map but I would be interested if there is a better way to address this, or if there is some way to coax the API into doing it automatically?
Thanks