cameraIntrinsicsFromOpenCV does not seem to account for differences in distortion model
3 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
Min seok Kang
el 10 de Nov. de 2021
Comentada: Min seok Kang
el 10 de Nov. de 2021
The function cameraIntrinsicsFromOpenCV in the Computer Vision toolbox seems to give out wrong distortion coefficients.
![Polynomial distortion](https://www.mathworks.com/matlabcentral/answers/uploaded_files/796134/Polynomial%20distortion.png)
![](https://www.mathworks.com/matlabcentral/answers/uploaded_files/796139/image.png)
And thus, the results of MATLAB's undistort functions do not seem to be right when using the camera intrinsics from OpenCV. Is there a way to undistort points manually?
0 comentarios
Respuesta aceptada
Giridharan Kumaravelu
el 10 de Nov. de 2021
The two equations mentioned in your question are essentially the same if the higher order radial distortion coefficients (k4-k6) in OpenCV are set to zero.
By default, OpenCV's calibration tools like cv.calibrateCamera calibrate for two radial distortion coefficients (k1 and k2) only. Often times, this is sufficient to model normal lenses.
Unless you have explicitly calibrated for more than 3 radial coefficients in OpenCV, you should be able to accurately import those camera parameters from OpenCV using cameraIntrinsicsFromOpenCV.
3 comentarios
Giridharan Kumaravelu
el 10 de Nov. de 2021
Unfortunately, CVT camera calibration tools currently do not support using more than 3 radial distortion coefficients. Isn't there a way to limit the number of radial distortion coefficients in the Azure Kinect SDK? If not, could you directly calibrate the camera using CVT's Camera Calibrator app or using the estimateCameraParameters function?
Más respuestas (0)
Ver también
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!