find3d with undistort introduces new axis to `xy`

[hop-soellingeraj]

pymvg/pymvg/multi_camera_system.py

Line 215 in 2b99ccb

xy = cam.undistort( [xy] )

There is a bug in the case where find3d(..., undistort=False). I am not sure what the correct fix is. After running through undistort, the point gets wrapped in a new array. This is a conflict because I can't pass find3d the same data structure when with the find3d(..., undistort=True) vs with the find3d(..., undistort=False)

Please advise

[astraw]

Thanks for reporting this. I am open to suggestions for fixes.

[hop-soellingeraj]

One way, potentially you will not like because it will break some of the existing code using pymvg. This just requires the user of pymvg.find3d to input the same data structure as cam.undistort outputs, which is a matrix with a single x,y pair. E.g. [[13, 54]] where as now, it expects [13, 54]