opencv/modules/calib3d/doc/camera_calibration_and_3d_reconstruction.rst

1416 lines
82 KiB
ReStructuredText
Raw Normal View History

Camera Calibration and 3D Reconstruction
========================================
.. highlight:: cpp
2011-05-15 21:16:53 +02:00
The functions in this section use a so-called pinhole camera model. In this model, a scene view is formed by projecting 3D points into the image plane
using a perspective transformation.
.. math::
2011-02-26 12:05:10 +01:00
s \; m' = A [R|t] M'
or
.. math::
s \vecthree{u}{v}{1} = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}
2011-03-03 08:29:55 +01:00
\begin{bmatrix}
r_{11} & r_{12} & r_{13} & t_1 \\
r_{21} & r_{22} & r_{23} & t_2 \\
r_{31} & r_{32} & r_{33} & t_3
\end{bmatrix}
\begin{bmatrix}
X \\
Y \\
Z \\
1
\end{bmatrix}
2011-02-26 12:05:10 +01:00
2011-05-15 21:16:53 +02:00
where:
* :math:`(X, Y, Z)` are the coordinates of a 3D point in the world coordinate space
* :math:`(u, v)` are the coordinates of the projection point in pixels
* :math:`A` is a camera matrix, or a matrix of intrinsic parameters
* :math:`(cx, cy)` is a principal point that is usually at the image center
* :math:`fx, fy` are the focal lengths expressed in pixel-related units
2011-05-15 21:16:53 +02:00
Thus, if an image from the camera is
scaled by a factor, all of these parameters should
be scaled (multiplied/divided, respectively) by the same factor. The
2011-05-15 21:16:53 +02:00
matrix of intrinsic parameters does not depend on the scene viewed. So,
once estimated, it can be re-used as long as the focal length is fixed (in
case of zoom lens). The joint rotation-translation matrix
2011-02-26 12:05:10 +01:00
:math:`[R|t]` is called a matrix of extrinsic parameters. It is used to describe the
camera motion around a static scene, or vice versa, rigid motion of an
2011-05-15 21:16:53 +02:00
object in front of a still camera. That is,
2011-02-26 12:05:10 +01:00
:math:`[R|t]` translates
coordinates of a point
2011-05-15 21:16:53 +02:00
:math:`(X, Y, Z)` to a coordinate system,
fixed with respect to the camera. The transformation above is equivalent
2011-02-26 12:05:10 +01:00
to the following (when
:math:`z \ne 0` ):
.. math::
2011-03-03 08:29:55 +01:00
\begin{array}{l}
\vecthree{x}{y}{z} = R \vecthree{X}{Y}{Z} + t \\
x' = x/z \\
y' = y/z \\
u = f_x*x' + c_x \\
v = f_y*y' + c_y
\end{array}
Real lenses usually have some distortion, mostly
radial distortion and slight tangential distortion. So, the above model
is extended as:
.. math::
2011-02-26 12:05:10 +01:00
\begin{array}{l} \vecthree{x}{y}{z} = R \vecthree{X}{Y}{Z} + t \\ x' = x/z \\ y' = y/z \\ x'' = x' \frac{1 + k_1 r^2 + k_2 r^4 + k_3 r^6}{1 + k_4 r^2 + k_5 r^4 + k_6 r^6} + 2 p_1 x' y' + p_2(r^2 + 2 x'^2) \\ y'' = y' \frac{1 + k_1 r^2 + k_2 r^4 + k_3 r^6}{1 + k_4 r^2 + k_5 r^4 + k_6 r^6} + p_1 (r^2 + 2 y'^2) + 2 p_2 x' y' \\ \text{where} \quad r^2 = x'^2 + y'^2 \\ u = f_x*x'' + c_x \\ v = f_y*y'' + c_y \end{array}
2011-05-15 21:16:53 +02:00
:math:`k_1`,
:math:`k_2`,
:math:`k_3`,
:math:`k_4`,
:math:`k_5`, and
:math:`k_6` are radial distortion coefficients.
:math:`p_1` and
:math:`p_2` are tangential distortion coefficients.
2011-02-26 12:05:10 +01:00
Higher-order coefficients are not considered in OpenCV. In the functions below the coefficients are passed or returned as
.. math::
2011-02-26 12:05:10 +01:00
(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6]])
2011-05-15 21:16:53 +02:00
vector. That is, if the vector contains four elements, it means that
2011-02-26 12:05:10 +01:00
:math:`k_3=0` .
The distortion coefficients do not depend on the scene viewed. Thus, they also belong to the intrinsic camera parameters. And they remain the same regardless of the captured image resolution.
2011-05-15 21:16:53 +02:00
If, for example, a camera has been calibrated on images of
``320 x 240`` resolution, absolutely the same distortion coefficients can
be used for ``640 x 480`` images from the same camera while
2011-05-15 21:16:53 +02:00
:math:`f_x`,
:math:`f_y`,
:math:`c_x`, and
:math:`c_y` need to be scaled appropriately.
2011-05-15 21:16:53 +02:00
The functions below use the above model to do the following:
2011-05-15 21:16:53 +02:00
* Project 3D points to the image plane given intrinsic and extrinsic parameters.
2011-05-15 21:16:53 +02:00
* Compute extrinsic parameters given intrinsic parameters, a few 3D points, and their projections.
2011-05-15 21:16:53 +02:00
* Estimate intrinsic and extrinsic camera parameters from several views of a known calibration pattern (every view is described by several 3D-2D point correspondences).
* Estimate the relative position and orientation of the stereo camera "heads" and compute the *rectification* transformation that makes the camera optical axes parallel.
2011-03-08 23:22:24 +01:00
calibrateCamera
---------------
Finds the camera intrinsic and extrinsic parameters from several views of a calibration pattern.
2011-03-08 23:22:24 +01:00
2011-06-23 13:46:14 +02:00
.. ocv:function:: double calibrateCamera( InputArrayOfArrays objectPoints, InputArrayOfArrays imagePoints, Size imageSize, InputOutputArray cameraMatrix, InputOutputArray distCoeffs, OutputArrayOfArrays rvecs, OutputArrayOfArrays tvecs, int flags=0 )
.. ocv:pyfunction:: cv2.calibrateCamera(objectPoints, imagePoints, imageSize, cameraMatrix, distCoeffs[, rvecs[, tvecs[, flags]]]) -> retval, cameraMatrix, distCoeffs, rvecs, tvecs
.. ocv:cfunction:: double cvCalibrateCamera2( const CvMat* objectPoints, const CvMat* imagePoints, const CvMat* pointCounts, CvSize imageSize, CvMat* cameraMatrix, CvMat* distCoeffs, CvMat* rvecs=NULL, CvMat* tvecs=NULL, int flags=0 )
.. ocv:pyoldfunction:: cv.CalibrateCamera2(objectPoints, imagePoints, pointCounts, imageSize, cameraMatrix, distCoeffs, rvecs, tvecs, flags=0)-> None
:param objectPoints: In the new interface it is a vector of vectors of calibration pattern points in the calibration pattern coordinate space. The outer vector contains as many elements as the number of the pattern views. If the same calibration pattern is shown in each view and it is fully visible, all the vectors will be the same. Although, it is possible to use partially occluded patterns, or even different patterns in different views. Then, the vectors will be different. The points are 3D, but since they are in a pattern coordinate system, then, if the rig is planar, it may make sense to put the model to a XY coordinate plane so that Z-coordinate of each input object point is 0.
In the old interface all the vectors of object points from different views are concatenated together.
:param imagePoints: In the new interface it is a vector of vectors of the projections of calibration pattern points. ``imagePoints.size()`` and ``objectPoints.size()`` and ``imagePoints[i].size()`` must be equal to ``objectPoints[i].size()`` for each ``i``.
In the old interface all the vectors of object points from different views are concatenated together.
:param pointCounts: In the old interface this is a vector of integers, containing as many elements, as the number of views of the calibration pattern. Each element is the number of points in each view. Usually, all the elements are the same and equal to the number of feature points on the calibration pattern.
2011-05-15 21:16:53 +02:00
:param imageSize: Size of the image used only to initialize the intrinsic camera matrix.
2011-05-15 21:16:53 +02:00
:param cameraMatrix: Output 3x3 floating-point camera matrix :math:`A = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}` . If ``CV_CALIB_USE_INTRINSIC_GUESS`` and/or ``CV_CALIB_FIX_ASPECT_RATIO`` are specified, some or all of ``fx, fy, cx, cy`` must be initialized before calling the function.
2011-05-15 21:16:53 +02:00
:param distCoeffs: Output vector of distortion coefficients :math:`(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6]])` of 4, 5, or 8 elements.
2011-02-26 12:05:10 +01:00
:param rvecs: Output vector of rotation vectors (see :ocv:func:`Rodrigues` ) estimated for each pattern view. That is, each k-th rotation vector together with the corresponding k-th translation vector (see the next output parameter description) brings the calibration pattern from the model coordinate space (in which object points are specified) to the world coordinate space, that is, a real position of the calibration pattern in the k-th pattern view (k=0.. *M* -1).
2011-02-26 12:05:10 +01:00
2011-06-23 13:46:14 +02:00
:param tvecs: Output vector of translation vectors estimated for each pattern view.
2011-02-26 12:05:10 +01:00
2011-05-15 21:16:53 +02:00
:param flags: Different flags that may be zero or a combination of the following values:
* **CV_CALIB_USE_INTRINSIC_GUESS** ``cameraMatrix`` contains valid initial values of ``fx, fy, cx, cy`` that are optimized further. Otherwise, ``(cx, cy)`` is initially set to the image center ( ``imageSize`` is used), and focal distances are computed in a least-squares fashion. Note, that if intrinsic parameters are known, there is no need to use this function just to estimate extrinsic parameters. Use :ocv:func:`solvePnP` instead.
2011-05-15 21:16:53 +02:00
* **CV_CALIB_FIX_PRINCIPAL_POINT** The principal point is not changed during the global optimization. It stays at the center or at a different location specified when ``CV_CALIB_USE_INTRINSIC_GUESS`` is set too.
2011-05-15 21:16:53 +02:00
* **CV_CALIB_FIX_ASPECT_RATIO** The functions considers only ``fy`` as a free parameter. The ratio ``fx/fy`` stays the same as in the input ``cameraMatrix`` . When ``CV_CALIB_USE_INTRINSIC_GUESS`` is not set, the actual input values of ``fx`` and ``fy`` are ignored, only their ratio is computed and used further.
2011-05-15 21:16:53 +02:00
* **CV_CALIB_ZERO_TANGENT_DIST** Tangential distortion coefficients :math:`(p_1, p_2)` are set to zeros and stay zero.
2011-02-26 12:05:10 +01:00
2011-05-15 21:16:53 +02:00
* **CV_CALIB_FIX_K1,...,CV_CALIB_FIX_K6** The corresponding radial distortion coefficient is not changed during the optimization. If ``CV_CALIB_USE_INTRINSIC_GUESS`` is set, the coefficient from the supplied ``distCoeffs`` matrix is used. Otherwise, it is set to 0.
2011-02-26 12:05:10 +01:00
2011-05-15 21:16:53 +02:00
* **CV_CALIB_RATIONAL_MODEL** Coefficients k4, k5, and k6 are enabled. To provide the backward compatibility, this extra flag should be explicitly specified to make the calibration function use the rational model and return 8 coefficients. If the flag is not set, the function computes and returns only 5 distortion coefficients.
The function estimates the intrinsic camera
parameters and extrinsic parameters for each of the views. The algorithm is based on [Zhang2000] and [BoughuetMCT]. The coordinates of 3D object points and their corresponding 2D projections
in each view must be specified. That may be achieved by using an
2011-05-15 21:16:53 +02:00
object with a known geometry and easily detectable feature points.
Such an object is called a calibration rig or calibration pattern,
and OpenCV has built-in support for a chessboard as a calibration
2011-02-26 12:05:10 +01:00
rig (see
:ocv:func:`findChessboardCorners` ). Currently, initialization
2011-02-26 12:05:10 +01:00
of intrinsic parameters (when ``CV_CALIB_USE_INTRINSIC_GUESS`` is not set) is only implemented for planar calibration patterns
2011-05-15 21:16:53 +02:00
(where Z-coordinates of the object points must be all zeros). 3D
2011-02-26 12:05:10 +01:00
calibration rigs can also be used as long as initial ``cameraMatrix`` is provided.
2011-05-15 21:16:53 +02:00
The algorithm performs the following steps:
#.
2011-05-15 21:16:53 +02:00
Compute the initial intrinsic parameters (the option only available for planar calibration patterns) or read them from the input parameters. The distortion coefficients are all set to zeros initially unless some of ``CV_CALIB_FIX_K?`` are specified.
#.
2011-05-15 21:16:53 +02:00
Estimate the initial camera pose as if the intrinsic parameters have been already known. This is done using
:ocv:func:`solvePnP` .
#.
Run the global Levenberg-Marquardt optimization algorithm to minimize the reprojection error, that is, the total sum of squared distances between the observed feature points ``imagePoints`` and the projected (using the current estimates for camera parameters and the poses) object points ``objectPoints``. See :ocv:func:`projectPoints` for details.
2011-02-26 12:05:10 +01:00
The function returns the final re-projection error.
2011-05-15 21:16:53 +02:00
.. note::
2011-05-15 21:16:53 +02:00
If you use a non-square (=non-NxN) grid and :ocv:func:`findChessboardCorners` for calibration, and ``calibrateCamera`` returns bad values (zero distortion coefficients, an image center very far from ``(w/2-0.5,h/2-0.5)``, and/or large differences between :math:`f_x` and :math:`f_y` (ratios of 10:1 or more)), then you have probably used ``patternSize=cvSize(rows,cols)`` instead of using ``patternSize=cvSize(cols,rows)`` in :ocv:func:`findChessboardCorners` .
2011-02-26 12:05:10 +01:00
.. seealso::
:ocv:func:`FindChessboardCorners`,
:ocv:func:`solvePnP`,
:ocv:func:`initCameraMatrix2D`,
:ocv:func:`stereoCalibrate`,
:ocv:func:`undistort`
2011-03-08 23:22:24 +01:00
2011-03-08 23:22:24 +01:00
calibrationMatrixValues
-----------------------
Computes useful camera characteristics from the camera matrix.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void calibrationMatrixValues( InputArray cameraMatrix, Size imageSize, double apertureWidth, double apertureHeight, double& fovx, double& fovy, double& focalLength, Point2d& principalPoint, double& aspectRatio )
.. ocv:pyfunction:: cv2.calibrationMatrixValues(cameraMatrix, imageSize, apertureWidth, apertureHeight) -> fovx, fovy, focalLength, principalPoint, aspectRatio
:param cameraMatrix: Input camera matrix that can be estimated by :ocv:func:`calibrateCamera` or :ocv:func:`stereoCalibrate` .
2011-03-08 23:22:24 +01:00
2011-05-15 21:16:53 +02:00
:param imageSize: Input image size in pixels.
2011-05-15 21:16:53 +02:00
:param apertureWidth: Physical width of the sensor.
2011-05-15 21:16:53 +02:00
:param apertureHeight: Physical height of the sensor.
2011-05-15 21:16:53 +02:00
:param fovx: Output field of view in degrees along the horizontal sensor axis.
2011-05-15 21:16:53 +02:00
:param fovy: Output field of view in degrees along the vertical sensor axis.
2011-05-15 21:16:53 +02:00
:param focalLength: Focal length of the lens in mm.
2011-05-15 21:16:53 +02:00
:param principalPoint: Principal point in pixels.
2011-02-26 12:05:10 +01:00
:param aspectRatio: :math:`f_y/f_x`
The function computes various useful camera characteristics from the previously estimated camera matrix.
2011-03-08 23:22:24 +01:00
composeRT
-------------
Combines two rotation-and-shift transformations.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void composeRT( InputArray rvec1, InputArray tvec1, InputArray rvec2, InputArray tvec2, OutputArray rvec3, OutputArray tvec3, OutputArray dr3dr1=noArray(), OutputArray dr3dt1=noArray(), OutputArray dr3dr2=noArray(), OutputArray dr3dt2=noArray(), OutputArray dt3dr1=noArray(), OutputArray dt3dt1=noArray(), OutputArray dt3dr2=noArray(), OutputArray dt3dt2=noArray() )
.. ocv:pyfunction:: cv2.composeRT(rvec1, tvec1, rvec2, tvec2[, rvec3[, tvec3[, dr3dr1[, dr3dt1[, dr3dr2[, dr3dt2[, dt3dr1[, dt3dt1[, dt3dr2[, dt3dt2]]]]]]]]]]) -> rvec3, tvec3, dr3dr1, dr3dt1, dr3dr2, dr3dt2, dt3dr1, dt3dt1, dt3dr2, dt3dt2
:param rvec1: First rotation vector.
:param tvec1: First translation vector.
:param rvec2: Second rotation vector.
:param tvec2: Second translation vector.
2011-05-15 21:16:53 +02:00
:param rvec3: Output rotation vector of the superposition.
2011-05-15 21:16:53 +02:00
:param tvec3: Output translation vector of the superposition.
:param d*d*: Optional output derivatives of ``rvec3`` or ``tvec3`` with regard to ``rvec1``, ``rvec2``, ``tvec1`` and ``tvec2``, respectively.
2011-02-26 12:05:10 +01:00
The functions compute:
.. math::
2011-02-26 12:05:10 +01:00
\begin{array}{l} \texttt{rvec3} = \mathrm{rodrigues} ^{-1} \left ( \mathrm{rodrigues} ( \texttt{rvec2} ) \cdot \mathrm{rodrigues} ( \texttt{rvec1} ) \right ) \\ \texttt{tvec3} = \mathrm{rodrigues} ( \texttt{rvec2} ) \cdot \texttt{tvec1} + \texttt{tvec2} \end{array} ,
2011-05-15 21:16:53 +02:00
where :math:`\mathrm{rodrigues}` denotes a rotation vector to a rotation matrix transformation, and
:math:`\mathrm{rodrigues}^{-1}` denotes the inverse transformation. See :ocv:func:`Rodrigues` for details.
Also, the functions can compute the derivatives of the output vectors with regards to the input vectors (see :ocv:func:`matMulDeriv` ).
The functions are used inside :ocv:func:`stereoCalibrate` but can also be used in your own code where Levenberg-Marquardt or another gradient-based solver is used to optimize a function that contains a matrix multiplication.
2011-03-08 23:22:24 +01:00
computeCorrespondEpilines
-----------------------------
For points in an image of a stereo pair, computes the corresponding epilines in the other image.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void computeCorrespondEpilines( InputArray points, int whichImage, InputArray F, OutputArray lines )
.. ocv:cfunction:: void cvComputeCorrespondEpilines( const CvMat* points, int whichImage, const CvMat* F, CvMat* lines)
.. ocv:pyoldfunction:: cv.ComputeCorrespondEpilines(points, whichImage, F, lines) -> None
2011-05-15 21:16:53 +02:00
:param points: Input points. :math:`N \times 1` or :math:`1 \times N` matrix of type ``CV_32FC2`` or ``vector<Point2f>`` .
2011-05-15 21:16:53 +02:00
:param whichImage: Index of the image (1 or 2) that contains the ``points`` .
:param F: Fundamental matrix that can be estimated using :ocv:func:`findFundamentalMat` or :ocv:func:`StereoRectify` .
2011-05-15 21:16:53 +02:00
:param lines: Output vector of the epipolar lines corresponding to the points in the other image. Each line :math:`ax + by + c=0` is encoded by 3 numbers :math:`(a, b, c)` .
2011-05-15 21:16:53 +02:00
For every point in one of the two images of a stereo pair, the function finds the equation of the
corresponding epipolar line in the other image.
2011-02-26 12:05:10 +01:00
From the fundamental matrix definition (see
:ocv:func:`findFundamentalMat` ),
2011-02-26 12:05:10 +01:00
line
:math:`l^{(2)}_i` in the second image for the point
2011-05-15 21:16:53 +02:00
:math:`p^{(1)}_i` in the first image (when ``whichImage=1`` ) is computed as:
.. math::
2011-02-26 12:05:10 +01:00
l^{(2)}_i = F p^{(1)}_i
2011-05-15 21:16:53 +02:00
And vice versa, when ``whichImage=2``,
:math:`l^{(1)}_i` is computed from
2011-02-26 12:05:10 +01:00
:math:`p^{(2)}_i` as:
.. math::
2011-02-26 12:05:10 +01:00
l^{(1)}_i = F^T p^{(2)}_i
2011-05-15 21:16:53 +02:00
Line coefficients are defined up to a scale. They are normalized so that
2011-02-26 12:05:10 +01:00
:math:`a_i^2+b_i^2=1` .
convertPointsToHomogeneous
--------------------------
Converts points from Euclidean to homogeneous space.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void convertPointsToHomogeneous( InputArray src, OutputArray dst )
.. ocv:pyfunction:: cv2.convertPointsToHomogeneous(src[, dst]) -> dst
:param src: Input vector of ``N``-dimensional points.
:param dst: Output vector of ``N+1``-dimensional points.
The function converts points from Euclidean to homogeneous space by appending 1's to the tuple of point coordinates. That is, each point ``(x1, x2, ..., xn)`` is converted to ``(x1, x2, ..., xn, 1)``.
convertPointsFromHomogeneous
----------------------------
Converts points from homogeneous to Euclidean space.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void convertPointsFromHomogeneous( InputArray src, OutputArray dst )
.. ocv:pyfunction:: cv2.convertPointsFromHomogeneous(src[, dst]) -> dst
:param src: Input vector of ``N``-dimensional points.
:param dst: Output vector of ``N-1``-dimensional points.
The function converts points homogeneous to Euclidean space using perspective projection. That is, each point ``(x1, x2, ... x(n-1), xn)`` is converted to ``(x1/xn, x2/xn, ..., x(n-1)/xn)``. When ``xn=0``, the output point coordinates will be ``(0,0,0,...)``.
2011-03-08 23:22:24 +01:00
convertPointsHomogeneous
------------------------
Converts points to/from homogeneous coordinates.
2011-03-08 23:22:24 +01:00
2011-06-16 14:48:23 +02:00
.. ocv:function:: void convertPointsHomogeneous( InputArray src, OutputArray dst )
.. ocv:pyfunction:: cv2.convertPointsHomogeneous(src[, dst]) -> dst
.. ocv:cfunction:: void cvConvertPointsHomogeneous( const CvMat* src, CvMat* dst )
.. ocv:pyoldfunction:: cv.ConvertPointsHomogeneous( src, dst ) -> None
:param src: Input array or vector of 2D, 3D, or 4D points.
:param dst: Output vector of 2D, 3D, or 4D points.
The function converts 2D or 3D points from/to homogeneous coordinates by calling either :ocv:func:`convertPointsToHomogeneous` or :ocv:func:`convertPointsFromHomogeneous`.
.. note:: The function is obsolete. Use one of the previous two functions instead.
2011-03-08 23:22:24 +01:00
decomposeProjectionMatrix
--------------------------
Decomposes a projection matrix into a rotation matrix and a camera matrix.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void decomposeProjectionMatrix( InputArray projMatrix, OutputArray cameraMatrix, OutputArray rotMatrix, OutputArray transVect, OutputArray rotMatrixX=noArray(), OutputArray rotMatrixY=noArray(), OutputArray rotMatrixZ=noArray(), OutputArray eulerAngles=noArray() )
.. ocv:pyfunction:: cv2.decomposeProjectionMatrix(projMatrix[, cameraMatrix[, rotMatrix[, transVect[, rotMatrixX[, rotMatrixY[, rotMatrixZ[, eulerAngles]]]]]]]) -> cameraMatrix, rotMatrix, transVect, rotMatrixX, rotMatrixY, rotMatrixZ, eulerAngles
.. ocv:cfunction:: void cvDecomposeProjectionMatrix( const CvMat *projMatrix, CvMat *cameraMatrix, CvMat *rotMatrix, CvMat *transVect, CvMat *rotMatrX=NULL, CvMat *rotMatrY=NULL, CvMat *rotMatrZ=NULL, CvPoint3D64f *eulerAngles=NULL)
.. ocv:pyoldfunction:: cv.DecomposeProjectionMatrix(projMatrix, cameraMatrix, rotMatrix, transVect, rotMatrX=None, rotMatrY=None, rotMatrZ=None) -> eulerAngles
2011-05-15 21:16:53 +02:00
:param projMatrix: 3x4 input projection matrix P.
:param cameraMatrix: Output 3x3 camera matrix K.
2011-05-15 21:16:53 +02:00
:param rotMatrix: Output 3x3 external rotation matrix R.
2011-05-15 21:16:53 +02:00
:param transVect: Output 4x1 translation vector T.
2011-05-15 21:16:53 +02:00
:param rotMatrX: Optional 3x3 rotation matrix around x-axis.
2011-05-15 21:16:53 +02:00
:param rotMatrY: Optional 3x3 rotation matrix around y-axis.
2011-05-15 21:16:53 +02:00
:param rotMatrZ: Optional 3x3 rotation matrix around z-axis.
:param eulerAngles: Optional three-element vector containing three Euler angles of rotation.
2011-05-15 21:16:53 +02:00
The function computes a decomposition of a projection matrix into a calibration and a rotation matrix and the position of a camera.
It optionally returns three rotation matrices, one for each axis, and three Euler angles that could be used in OpenGL.
2011-02-26 12:05:10 +01:00
The function is based on
:ocv:func:`RQDecomp3x3` .
2011-03-08 23:22:24 +01:00
drawChessboardCorners
-------------------------
Renders the detected chessboard corners.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void drawChessboardCorners( InputOutputArray image, Size patternSize, InputArray corners, bool patternWasFound )
.. ocv:pyfunction:: cv2.drawChessboardCorners(image, patternSize, corners, patternWasFound) -> None
.. ocv:cfunction:: void cvDrawChessboardCorners( CvArr* image, CvSize patternSize, CvPoint2D32f* corners, int count, int patternWasFound )
.. ocv:pyoldfunction:: cv.DrawChessboardCorners(image, patternSize, corners, patternWasFound)-> None
2011-05-15 21:16:53 +02:00
:param image: Destination image. It must be an 8-bit color image.
:param patternSize: Number of inner corners per a chessboard row and column ``(patternSize = cv::Size(points_per_row,points_per_column))``.
:param corners: Array of detected corners, the output of ``findChessboardCorners``.
2011-06-16 14:48:23 +02:00
:param patternWasFound: Parameter indicating whether the complete board was found or not. The return value of :ocv:func:`findChessboardCorners` should be passed here.
2011-05-15 21:16:53 +02:00
The function draws individual chessboard corners detected either as red circles if the board was not found, or as colored corners connected with lines if the board was found.
2011-03-08 23:22:24 +01:00
findChessboardCorners
-------------------------
Finds the positions of internal corners of the chessboard.
2011-06-16 14:48:23 +02:00
.. ocv:function:: bool findChessboardCorners( InputArray image, Size patternSize, OutputArray corners, int flags=CV_CALIB_CB_ADAPTIVE_THRESH+CV_CALIB_CB_NORMALIZE_IMAGE )
.. ocv:pyfunction:: cv2.findChessboardCorners(image, patternSize[, corners[, flags]]) -> retval, corners
.. ocv:cfunction:: int cvFindChessboardCorners( const void* image, CvSize patternSize, CvPoint2D32f* corners, int* cornerCount=NULL, int flags=CV_CALIB_CB_ADAPTIVE_THRESH )
.. ocv:pyoldfunction:: cv.FindChessboardCorners(image, patternSize, flags=CV_CALIB_CB_ADAPTIVE_THRESH) -> corners
2011-05-15 21:16:53 +02:00
:param image: Source chessboard view. It must be an 8-bit grayscale or color image.
:param patternSize: Number of inner corners per a chessboard row and column ``( patternSize = cvSize(points_per_row,points_per_colum) = cvSize(columns,rows) )``.
2011-05-15 21:16:53 +02:00
:param corners: Output array of detected corners.
2011-05-15 21:16:53 +02:00
:param flags: Various operation flags that can be zero or a combination of the following values:
2011-05-15 21:16:53 +02:00
* **CV_CALIB_CB_ADAPTIVE_THRESH** Use adaptive thresholding to convert the image to black and white, rather than a fixed threshold level (computed from the average image brightness).
* **CV_CALIB_CB_NORMALIZE_IMAGE** Normalize the image gamma with :ocv:func:`EqualizeHist` before applying fixed or adaptive thresholding.
* **CV_CALIB_CB_FILTER_QUADS** Use additional criteria (like contour area, perimeter, square-like shape) to filter out false quads extracted at the contour retrieval stage.
2011-05-15 21:16:53 +02:00
* **CALIB_CB_FAST_CHECK** Run a fast check on the image that looks for chessboard corners, and shortcut the call if none is found. This can drastically speed up the call in the degenerate condition when no chessboard is observed.
2011-02-26 12:05:10 +01:00
The function attempts to determine
whether the input image is a view of the chessboard pattern and
locate the internal chessboard corners. The function returns a non-zero
2011-05-15 21:16:53 +02:00
value if all of the corners are found and they are placed
in a certain order (row by row, left to right in every row). Otherwise, if the function fails to find all the corners or reorder
them, it returns 0. For example, a regular chessboard has 8 x 8
squares and 7 x 7 internal corners, that is, points where the black squares touch each other.
The detected coordinates are approximate, and to determine their positions more accurately, the function calls :ocv:func:`cornerSubPix`.
You also may use the function :ocv:func:`cornerSubPix` with different parameters if returned coordinates are not accurate enough.
2011-02-26 12:05:10 +01:00
Sample usage of detecting and drawing chessboard corners: ::
Size patternsize(8,6); //interior number of corners
Mat gray = ....; //source image
vector<Point2f> corners; //this will be filled by the detected corners
2011-02-26 12:05:10 +01:00
//CALIB_CB_FAST_CHECK saves a lot of time on images
2011-05-15 21:16:53 +02:00
//that do not contain any chessboard corners
2011-02-26 12:05:10 +01:00
bool patternfound = findChessboardCorners(gray, patternsize, corners,
CALIB_CB_ADAPTIVE_THRESH + CALIB_CB_NORMALIZE_IMAGE
+ CALIB_CB_FAST_CHECK);
2011-02-26 12:05:10 +01:00
if(patternfound)
2011-02-26 12:05:10 +01:00
cornerSubPix(gray, corners, Size(11, 11), Size(-1, -1),
TermCriteria(CV_TERMCRIT_EPS + CV_TERMCRIT_ITER, 30, 0.1));
2011-02-26 12:05:10 +01:00
drawChessboardCorners(img, patternsize, Mat(corners), patternfound);
.. note:: The function requires white space (like a square-thick border, the wider the better) around the board to make the detection more robust in various environments. Otherwise, if there is no border and the background is dark, the outer black squares cannot be segmented properly and so the square grouping and ordering algorithm fails.
2011-03-08 23:22:24 +01:00
findCirclesGrid
-------------------
Finds the centers in the grid of circles.
2011-06-16 14:48:23 +02:00
.. ocv:function:: bool findCirclesGrid( InputArray image, Size patternSize, OutputArray centers, int flags=CALIB_CB_SYMMETRIC_GRID, const Ptr<FeatureDetector> &blobDetector = new SimpleBlobDetector() )
.. ocv:pyfunction:: cv2.findCirclesGridDefault(image, patternSize[, centers[, flags]]) -> centers
2011-05-15 21:16:53 +02:00
:param image: Grid view of source circles. It must be an 8-bit grayscale or color image.
2011-05-15 21:16:53 +02:00
:param patternSize: Number of circles per a grid row and column ``( patternSize = Size(points_per_row, points_per_colum) )`` .
2011-05-15 21:16:53 +02:00
:param centers: Output array of detected centers.
2011-05-15 21:16:53 +02:00
:param flags: Various operation flags that can be one of the following values:
2011-05-15 21:16:53 +02:00
* **CALIB_CB_SYMMETRIC_GRID** Use symmetric pattern of circles.
2011-05-15 21:16:53 +02:00
* **CALIB_CB_ASYMMETRIC_GRID** Use asymmetric pattern of circles.
2011-06-08 14:26:30 +02:00
* **CALIB_CB_CLUSTERING** Use a special algorithm for grid detection. It is more robust to perspective distortions but much more sensitive to background clutter.
:param blobDetector: FeatureDetector that finds blobs like dark circles on light background
The function attempts to determine
2011-06-08 14:26:30 +02:00
whether the input image contains a grid of circles. If it is, the function locates centers of the circles. The function returns a
non-zero value if all of the centers have been found and they have been placed
2011-05-15 21:16:53 +02:00
in a certain order (row by row, left to right in every row). Otherwise, if the function fails to find all the corners or reorder
them, it returns 0.
2011-05-15 21:16:53 +02:00
Sample usage of detecting and drawing the centers of circles: ::
Size patternsize(7,7); //number of centers
Mat gray = ....; //source image
vector<Point2f> centers; //this will be filled by the detected centers
2011-02-26 12:05:10 +01:00
bool patternfound = findCirclesGrid(gray, patternsize, centers);
2011-02-26 12:05:10 +01:00
drawChessboardCorners(img, patternsize, Mat(centers), patternfound);
.. note:: The function requires white space (like a square-thick border, the wider the better) around the board to make the detection more robust in various environments.
2011-03-08 23:22:24 +01:00
solvePnP
------------
Finds an object pose from 3D-2D point correspondences.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void solvePnP( InputArray objectPoints, InputArray imagePoints, InputArray cameraMatrix, InputArray distCoeffs, OutputArray rvec, OutputArray tvec, bool useExtrinsicGuess=false )
.. ocv:pyfunction:: cv2.solvePnP(objectPoints, imagePoints, cameraMatrix, distCoeffs[, rvec[, tvec[, useExtrinsicGuess]]]) -> rvec, tvec
.. ocv:cfunction:: void cvFindExtrinsicCameraParams2( const CvMat* objectPoints, const CvMat* imagePoints, const CvMat* cameraMatrix, const CvMat* distCoeffs, CvMat* rvec, CvMat* tvec, int useExtrinsicGuess=0)
.. ocv:pyoldfunction:: cv.FindExtrinsicCameraParams2(objectPoints, imagePoints, cameraMatrix, distCoeffs, rvec, tvec, useExtrinsicGuess=0)-> None
2011-05-15 21:16:53 +02:00
:param objectPoints: Array of object points in the object coordinate space, 3xN/Nx3 1-channel or 1xN/Nx1 3-channel, where N is the number of points. ``vector<Point3f>`` can be also passed here.
2011-05-15 21:16:53 +02:00
:param imagePoints: Array of corresponding image points, 2xN/Nx2 1-channel or 1xN/Nx1 2-channel, where N is the number of points. ``vector<Point2f>`` can be also passed here.
2011-05-15 21:16:53 +02:00
:param cameraMatrix: Input camera matrix :math:`A = \vecthreethree{fx}{0}{cx}{0}{fy}{cy}{0}{0}{1}` .
2011-05-15 21:16:53 +02:00
:param distCoeffs: Input vector of distortion coefficients :math:`(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6]])` of 4, 5, or 8 elements. If the vector is NULL/empty, the zero distortion coefficients are assumed.
:param rvec: Output rotation vector (see :ocv:func:`Rodrigues` ) that, together with ``tvec`` , brings points from the model coordinate system to the camera coordinate system.
2011-05-15 21:16:53 +02:00
:param tvec: Output translation vector.
2011-05-15 21:16:53 +02:00
:param useExtrinsicGuess: If true (1), the function uses the provided ``rvec`` and ``tvec`` values as initial approximations of the rotation and translation vectors, respectively, and further optimizes them.
2011-05-15 21:16:53 +02:00
The function estimates the object pose given a set of object points, their corresponding image projections, as well as the camera matrix and the distortion coefficients. This function finds such a pose that minimizes reprojection error, that is, the sum of squared distances between the observed projections ``imagePoints`` and the projected (using
:ocv:func:`projectPoints` ) ``objectPoints`` .
2011-03-05 01:18:49 +01:00
2011-03-08 23:22:24 +01:00
solvePnPRansac
------------------
Finds an object pose from 3D-2D point correspondences using the RANSAC scheme.
2011-03-08 23:22:24 +01:00
2011-06-16 14:48:23 +02:00
.. ocv:function:: void solvePnPRansac( InputArray objectPoints, InputArray imagePoints, InputArray cameraMatrix, InputArray distCoeffs, OutputArray rvec, OutputArray tvec, bool useExtrinsicGuess=false, int iterationsCount = 100, float reprojectionError = 8.0, int minInliersCount = 100, OutputArray inliers = noArray() )
2011-03-05 01:18:49 +01:00
.. ocv:pyfunction:: cv2.solvePnPRansac(objectPoints, imagePoints, cameraMatrix, distCoeffs[, rvec[, tvec[, useExtrinsicGuess[, iterationsCount[, reprojectionError[, minInliersCount[, inliers]]]]]]]) -> rvec, tvec, inliers
2011-03-05 01:18:49 +01:00
2011-05-15 21:16:53 +02:00
:param objectPoints: Array of object points in the object coordinate space, 3xN/Nx3 1-channel or 1xN/Nx1 3-channel, where N is the number of points. ``vector<Point3f>`` can be also passed here.
2011-03-05 01:18:49 +01:00
2011-05-15 21:16:53 +02:00
:param imagePoints: Array of corresponding image points, 2xN/Nx2 1-channel or 1xN/Nx1 2-channel, where N is the number of points. ``vector<Point2f>`` can be also passed here.
2011-03-05 01:18:49 +01:00
2011-05-15 21:16:53 +02:00
:param cameraMatrix: Input camera matrix :math:`A = \vecthreethree{fx}{0}{cx}{0}{fy}{cy}{0}{0}{1}` .
2011-03-08 23:22:24 +01:00
2011-05-15 21:16:53 +02:00
:param distCoeffs: Input vector of distortion coefficients :math:`(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6]])` of 4, 5, or 8 elements. If the vector is NULL/empty, the zero distortion coefficients are assumed.
2011-03-05 01:18:49 +01:00
:param rvec: Output rotation vector (see :ocv:func:`Rodrigues` ) that, together with ``tvec`` , brings points from the model coordinate system to the camera coordinate system.
2011-03-05 01:18:49 +01:00
2011-05-15 21:16:53 +02:00
:param tvec: Output translation vector.
2011-03-05 01:18:49 +01:00
2011-05-15 21:16:53 +02:00
:param useExtrinsicGuess: If true (1), the function uses the provided ``rvec`` and ``tvec`` values as initial approximations of the rotation and translation vectors, respectively, and further optimizes them.
2011-03-05 01:18:49 +01:00
2011-05-15 21:16:53 +02:00
:param iterationsCount: Number of iterations.
2011-03-05 01:18:49 +01:00
:param reprojectionError: Inlier threshold value used by the RANSAC procedure. The parameter value is the maximum allowed distance between the observed and computed point projections to consider it an inlier.
2011-03-05 01:18:49 +01:00
:param minInliersCount: Number of inliers. If the algorithm at some stage finds more inliers than ``minInliersCount`` , it finishes.
2011-03-05 01:18:49 +01:00
2011-05-15 21:16:53 +02:00
:param inliers: Output vector that contains indices of inliers in ``objectPoints`` and ``imagePoints`` .
2011-03-05 01:18:49 +01:00
2011-05-15 21:16:53 +02:00
The function estimates an object pose given a set of object points, their corresponding image projections, as well as the camera matrix and the distortion coefficients. This function finds such a pose that minimizes reprojection error, that is, the sum of squared distances between the observed projections ``imagePoints`` and the projected (using
:ocv:func:`projectPoints` ) ``objectPoints``. The use of RANSAC makes the function resistant to outliers.
2011-03-05 01:18:49 +01:00
2011-03-08 23:22:24 +01:00
findFundamentalMat
----------------------
Calculates a fundamental matrix from the corresponding points in two images.
2011-06-16 14:48:23 +02:00
.. ocv:function:: Mat findFundamentalMat( InputArray points1, InputArray points2, int method=FM_RANSAC, double param1=3., double param2=0.99, OutputArray mask=noArray() )
.. ocv:pyfunction:: cv2.findFundamentalMat(points1, points2[, method[, param1[, param2[, mask]]]]) -> retval, mask
.. ocv:cfunction:: int cvFindFundamentalMat( const CvMat* points1, const CvMat* points2, CvMat* fundamentalMatrix, int method=CV_FM_RANSAC, double param1=1., double param2=0.99, CvMat* status=NULL)
.. ocv:pyoldfunction:: cv.FindFundamentalMat(points1, points2, fundamentalMatrix, method=CV_FM_RANSAC, param1=1., param2=0.99, status=None) -> None
2011-05-15 21:16:53 +02:00
:param points1: Array of ``N`` points from the first image. The point coordinates should be floating-point (single or double precision).
2011-05-15 21:16:53 +02:00
:param points2: Array of the second image points of the same size and format as ``points1`` .
2011-05-15 21:16:53 +02:00
:param method: Method for computing a fundamental matrix.
2011-02-26 12:05:10 +01:00
* **CV_FM_7POINT** for a 7-point algorithm. :math:`N = 7`
* **CV_FM_8POINT** for an 8-point algorithm. :math:`N \ge 8`
* **CV_FM_RANSAC** for the RANSAC algorithm. :math:`N \ge 8`
* **CV_FM_LMEDS** for the LMedS algorithm. :math:`N \ge 8`
2011-05-15 21:16:53 +02:00
:param param1: Parameter used for RANSAC. It is the maximum distance from a point to an epipolar line in pixels, beyond which the point is considered an outlier and is not used for computing the final fundamental matrix. It can be set to something like 1-3, depending on the accuracy of the point localization, image resolution, and the image noise.
2011-05-15 21:16:53 +02:00
:param param2: Parameter used for the RANSAC or LMedS methods only. It specifies a desirable level of confidence (probability) that the estimated matrix is correct.
2011-05-15 21:16:53 +02:00
:param status: Output array of N elements, every element of which is set to 0 for outliers and to 1 for the other points. The array is computed only in the RANSAC and LMedS methods. For other methods, it is set to all 1's.
2011-02-26 12:05:10 +01:00
The epipolar geometry is described by the following equation:
.. math::
2011-02-26 12:05:10 +01:00
[p_2; 1]^T F [p_1; 1] = 0
2011-02-26 12:05:10 +01:00
where
2011-05-15 21:16:53 +02:00
:math:`F` is a fundamental matrix,
2011-02-26 12:05:10 +01:00
:math:`p_1` and
:math:`p_2` are corresponding points in the first and the second images, respectively.
2011-02-26 12:05:10 +01:00
The function calculates the fundamental matrix using one of four methods listed above and returns
2011-05-15 21:16:53 +02:00
the found fundamental matrix. Normally just one matrix is found. But in case of the 7-point algorithm, the function may return up to 3 solutions (
2011-02-26 12:05:10 +01:00
:math:`9 \times 3` matrix that stores all 3 matrices sequentially).
The calculated fundamental matrix may be passed further to
:ocv:func:`ComputeCorrespondEpilines` that finds the epipolar lines
2011-02-26 12:05:10 +01:00
corresponding to the specified points. It can also be passed to
:ocv:func:`StereoRectifyUncalibrated` to compute the rectification transformation. ::
2011-05-15 21:16:53 +02:00
// Example. Estimation of fundamental matrix using the RANSAC algorithm
int point_count = 100;
vector<Point2f> points1(point_count);
vector<Point2f> points2(point_count);
2011-02-26 12:05:10 +01:00
// initialize the points here ... */
for( int i = 0; i < point_count; i++ )
{
points1[i] = ...;
points2[i] = ...;
}
2011-02-26 12:05:10 +01:00
Mat fundamental_matrix =
findFundamentalMat(points1, points2, FM_RANSAC, 3, 0.99);
2011-03-08 23:22:24 +01:00
findHomography
------------------
Finds a perspective transformation between two planes.
2011-06-16 14:48:23 +02:00
.. ocv:function:: Mat findHomography( InputArray srcPoints, InputArray dstPoints, int method=0, double ransacReprojThreshold=3, OutputArray mask=noArray() )
.. ocv:pyfunction:: cv2.findHomography(srcPoints, dstPoints[, method[, ransacReprojThreshold[, mask]]]) -> retval, mask
.. ocv:cfunction:: void cvFindHomography( const CvMat* srcPoints, const CvMat* dstPoints, CvMat* H, int method=0, double ransacReprojThreshold=3, CvMat* status=NULL)
.. ocv:pyoldfunction:: cv.FindHomography(srcPoints, dstPoints, H, method, ransacReprojThreshold=3.0, status=None)-> None
2011-05-15 21:16:53 +02:00
:param srcPoints: Coordinates of the points in the original plane, a matrix of the type ``CV_32FC2`` or ``vector<Point2f>`` .
2011-05-15 21:16:53 +02:00
:param dstPoints: Coordinates of the points in the target plane, a matrix of the type ``CV_32FC2`` or a ``vector<Point2f>`` .
2011-05-15 21:16:53 +02:00
:param method: Method used to computed a homography matrix. The following methods are possible:
2011-05-15 21:16:53 +02:00
* **0** - a regular method using all the points
2011-05-15 21:16:53 +02:00
* **CV_RANSAC** - RANSAC-based robust method
2011-05-15 21:16:53 +02:00
* **CV_LMEDS** - Least-Median robust method
2011-05-15 21:16:53 +02:00
:param ransacReprojThreshold: Maximum allowed reprojection error to treat a point pair as an inlier (used in the RANSAC method only). That is, if
2011-02-26 12:05:10 +01:00
.. math::
\| \texttt{dstPoints} _i - \texttt{convertPointsHomogeneous} ( \texttt{H} * \texttt{srcPoints} _i) \| > \texttt{ransacReprojThreshold}
2011-05-15 21:16:53 +02:00
then the point :math:`i` is considered an outlier. If ``srcPoints`` and ``dstPoints`` are measured in pixels, it usually makes sense to set this parameter somewhere in the range of 1 to 10.
2011-05-15 21:16:53 +02:00
:param status: Optional output mask set by a robust method ( ``CV_RANSAC`` or ``CV_LMEDS`` ). Note that the input mask values are ignored.
The functions find and return the perspective transformation :math:`H` between the source and the destination planes:
.. math::
2011-02-26 12:05:10 +01:00
s_i \vecthree{x'_i}{y'_i}{1} \sim H \vecthree{x_i}{y_i}{1}
2011-05-15 21:16:53 +02:00
so that the back-projection error
2011-02-26 12:05:10 +01:00
.. math::
2011-02-26 12:05:10 +01:00
\sum _i \left ( x'_i- \frac{h_{11} x_i + h_{12} y_i + h_{13}}{h_{31} x_i + h_{32} y_i + h_{33}} \right )^2+ \left ( y'_i- \frac{h_{21} x_i + h_{22} y_i + h_{23}}{h_{31} x_i + h_{32} y_i + h_{33}} \right )^2
2011-02-26 12:05:10 +01:00
is minimized. If the parameter ``method`` is set to the default value 0, the function
2011-05-15 21:16:53 +02:00
uses all the point pairs to compute an initial homography estimate with a simple least-squares scheme.
However, if not all of the point pairs (
2011-05-15 21:16:53 +02:00
:math:`srcPoints_i`,:math:`dstPoints_i` ) fit the rigid perspective transformation (that is, there
are some outliers), this initial estimate will be poor.
2011-05-15 21:16:53 +02:00
In this case, you can use one of the two robust methods. Both methods, ``RANSAC`` and ``LMeDS`` , try many different random subsets
of the corresponding point pairs (of four pairs each), estimate
the homography matrix using this subset and a simple least-square
2011-05-15 21:16:53 +02:00
algorithm, and then compute the quality/goodness of the computed homography
(which is the number of inliers for RANSAC or the median re-projection
error for LMeDs). The best subset is then used to produce the initial
estimate of the homography matrix and the mask of inliers/outliers.
Regardless of the method, robust or not, the computed homography
2011-05-15 21:16:53 +02:00
matrix is refined further (using inliers only in case of a robust
method) with the Levenberg-Marquardt method to reduce the
re-projection error even more.
2011-05-15 21:16:53 +02:00
The method ``RANSAC`` can handle practically any ratio of outliers
but it needs a threshold to distinguish inliers from outliers.
The method ``LMeDS`` does not need any threshold but it works
correctly only when there are more than 50% of inliers. Finally,
if there are no outliers and the noise is rather small, use the default method (``method=0``).
The function is used to find initial intrinsic and extrinsic matrices.
2011-05-15 21:16:53 +02:00
Homography matrix is determined up to a scale. Thus, it is normalized so that
2011-02-26 12:05:10 +01:00
:math:`h_{33}=1` .
.. seealso::
:ocv:func:`GetAffineTransform`,
:ocv:func:`GetPerspectiveTransform`,
:ocv:func:`EstimateRigidMotion`,
:ocv:func:`WarpPerspective`,
:ocv:func:`PerspectiveTransform`
2011-05-15 21:16:53 +02:00
estimateAffine3D
--------------------
Computes an optimal affine transformation between two 3D point sets.
.. ocv:function:: int estimateAffine3D(InputArray srcpt, InputArray dstpt, OutputArray out, OutputArray inliers, double ransacThreshold = 3.0, double confidence = 0.99)
.. ocv:pyfunction:: cv2.estimateAffine3D(_from, _to[, _out[, _inliers[, param1[, param2]]]]) -> retval, _out, _inliers
.. ocv:pyfunction:: cv2.estimateAffine3D(from, to[, dst[, outliers[, param1[, param2]]]]) -> retval, dst, outliers
:param srcpt: First input 3D point set.
:param dstpt: Second input 3D point set.
:param out: Output 3D affine transformation matrix :math:`3 \times 4` .
:param inliers: Output vector indicating which points are inliers.
:param ransacThreshold: Maximum reprojection error in the RANSAC algorithm to consider a point as an inlier.
:param confidence: Confidence level, between 0 and 1, for the estimated transformation. Anything between 0.95 and 0.99 is usually good enough. Values too close to 1 can slow down the estimation significantly. Values lower than 0.8-0.9 can result in an incorrectly estimated transformation.
The function estimates an optimal 3D affine transformation between two 3D point sets using the RANSAC algorithm.
filterSpeckles
--------------
Filters off small noise blobs (speckles) in the disparity map
.. ocv:function:: void filterSpeckles( InputOutputArray img, double newVal, int maxSpeckleSize, double maxDiff, InputOutputArray buf=noArray() )
.. ocv:pyfunction:: cv2.filterSpeckles(img, newVal, maxSpeckleSize, maxDiff[, buf]) -> None
:param img: The input 16-bit signed disparity image
:param newVal: The disparity value used to paint-off the speckles
:param maxSpeckleSize: The maximum speckle size to consider it a speckle. Larger blobs are not affected by the algorithm
:param maxDiff: Maximum difference between neighbor disparity pixels to put them into the same blob. Note that since StereoBM, StereoSGBM and may be other algorithms return a fixed-point disparity map, where disparity values are multiplied by 16, this scale factor should be taken into account when specifying this parameter value.
:param buf: The optional temporary buffer to avoid memory allocation within the function.
2011-03-08 23:22:24 +01:00
getOptimalNewCameraMatrix
-----------------------------
Returns the new camera matrix based on the free scaling parameter.
.. ocv:function:: Mat getOptimalNewCameraMatrix( InputArray cameraMatrix, InputArray distCoeffs, Size imageSize, double alpha, Size newImageSize=Size(), Rect* validPixROI=0, bool centerPrincipalPoint=false)
.. ocv:pyfunction:: cv2.getOptimalNewCameraMatrix(cameraMatrix, distCoeffs, imageSize, alpha[, newImgSize[, centerPrincipalPoint]]) -> retval, validPixROI
.. ocv:cfunction:: void cvGetOptimalNewCameraMatrix( const CvMat* cameraMatrix, const CvMat* distCoeffs, CvSize imageSize, double alpha, CvMat* newCameraMatrix, CvSize newImageSize=cvSize(0, 0), CvRect* validPixROI=0, int centerPrincipalPoint=0)
.. ocv:pyoldfunction:: cv.GetOptimalNewCameraMatrix(cameraMatrix, distCoeffs, imageSize, alpha, newCameraMatrix, newImageSize=(0, 0), validPixROI=0) -> None
2011-05-15 21:16:53 +02:00
:param cameraMatrix: Input camera matrix.
2011-05-15 21:16:53 +02:00
:param distCoeffs: Input vector of distortion coefficients :math:`(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6]])` of 4, 5, or 8 elements. If the vector is NULL/empty, the zero distortion coefficients are assumed.
2011-05-15 21:16:53 +02:00
:param imageSize: Original image size.
:param alpha: Free scaling parameter between 0 (when all the pixels in the undistorted image are valid) and 1 (when all the source image pixels are retained in the undistorted image). See :ocv:func:`stereoRectify` for details.
2011-05-15 21:16:53 +02:00
:param newCameraMatrix: Output new camera matrix.
2011-05-15 21:16:53 +02:00
:param newImageSize: Image size after rectification. By default,it is set to ``imageSize`` .
:param validPixROI: Optional output rectangle that outlines all-good-pixels region in the undistorted image. See ``roi1, roi2`` description in :ocv:func:`StereoRectify` .
:param centerPrincipalPoint: Optional flag that indicates whether in the new camera matrix the principal point should be at the image center or not. By default, the principal point is chosen to best fit a subset of the source image (determined by ``alpha``) to the corrected image.
The function computes and returns
2011-05-15 21:16:53 +02:00
the optimal new camera matrix based on the free scaling parameter. By varying this parameter, you may retrieve only sensible pixels ``alpha=0`` , keep all the original image pixels if there is valuable information in the corners ``alpha=1`` , or get something in between. When ``alpha>0`` , the undistortion result is likely to have some black pixels corresponding to "virtual" pixels outside of the captured distorted image. The original camera matrix, distortion coefficients, the computed new camera matrix, and ``newImageSize`` should be passed to
:ocv:func:`initUndistortRectifyMap` to produce the maps for
:ocv:func:`remap` .
2011-03-08 23:22:24 +01:00
initCameraMatrix2D
----------------------
Finds an initial camera matrix from 3D-2D point correspondences.
2011-06-16 14:48:23 +02:00
.. ocv:function:: Mat initCameraMatrix2D( InputArrayOfArrays objectPoints, InputArrayOfArrays imagePoints, Size imageSize, double aspectRatio=1.)
.. ocv:pyfunction:: cv2.initCameraMatrix2D(objectPoints, imagePoints, imageSize[, aspectRatio]) -> retval
.. ocv:cfunction:: void cvInitIntrinsicParams2D( const CvMat* objectPoints, const CvMat* imagePoints, const CvMat* pointCounts, CvSize imageSize, CvMat* cameraMatrix, double aspectRatio=1.)
.. ocv:pyoldfunction:: cv.InitIntrinsicParams2D(objectPoints, imagePoints, pointCounts, imageSize, cameraMatrix, aspectRatio=1.) -> None
:param objectPoints: Vector of vectors of the calibration pattern points in the calibration pattern coordinate space. In the old interface all the per-view vectors are concatenated. See :ocv:func:`calibrateCamera` for details.
:param imagePoints: Vector of vectors of the projections of the calibration pattern points. In the old interface all the per-view vectors are concatenated.
:param npoints: The integer vector of point counters for each view.
2011-05-15 21:16:53 +02:00
:param imageSize: Image size in pixels used to initialize the principal point.
2011-05-15 21:16:53 +02:00
:param aspectRatio: If it is zero or negative, both :math:`f_x` and :math:`f_y` are estimated independently. Otherwise, :math:`f_x = f_y * \texttt{aspectRatio}` .
2011-05-15 21:16:53 +02:00
The function estimates and returns an initial camera matrix for the camera calibration process.
Currently, the function only supports planar calibration patterns, which are patterns where each object point has z-coordinate =0.
2011-03-08 23:22:24 +01:00
matMulDeriv
---------------
Computes partial derivatives of the matrix product for each multiplied matrix.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void matMulDeriv( InputArray A, InputArray B, OutputArray dABdA, OutputArray dABdB )
.. ocv:pyfunction:: cv2.matMulDeriv(A, B[, dABdA[, dABdB]]) -> dABdA, dABdB
:param A: First multiplied matrix.
:param B: Second multiplied matrix.
:param dABdA: First output derivative matrix ``d(A*B)/dA`` of size :math:`\texttt{A.rows*B.cols} \times {A.rows*A.cols}` .
:param dABdA: Second output derivative matrix ``d(A*B)/dB`` of size :math:`\texttt{A.rows*B.cols} \times {B.rows*B.cols}` .
2011-05-15 21:16:53 +02:00
The function computes partial derivatives of the elements of the matrix product
:math:`A*B` with regard to the elements of each of the two input matrices. The function is used to compute the Jacobian matrices in
:ocv:func:`stereoCalibrate` but can also be used in any other similar optimization function.
2011-03-08 23:22:24 +01:00
projectPoints
-----------------
Projects 3D points to an image plane.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void projectPoints( InputArray objectPoints, InputArray rvec, InputArray tvec, InputArray cameraMatrix, InputArray distCoeffs, OutputArray imagePoints, OutputArray jacobian=noArray(), double aspectRatio=0 )
.. ocv:pyfunction:: cv2.projectPoints(objectPoints, rvec, tvec, cameraMatrix, distCoeffs[, imagePoints[, jacobian[, aspectRatio]]]) -> imagePoints, jacobian
.. ocv:cfunction:: void cvProjectPoints2( const CvMat* objectPoints, const CvMat* rvec, const CvMat* tvec, const CvMat* cameraMatrix, const CvMat* distCoeffs, CvMat* imagePoints, CvMat* dpdrot=NULL, CvMat* dpdt=NULL, CvMat* dpdf=NULL, CvMat* dpdc=NULL, CvMat* dpddist=NULL )
.. ocv:pyoldfunction:: cv.ProjectPoints2(objectPoints, rvec, tvec, cameraMatrix, distCoeffs, imagePoints, dpdrot=None, dpdt=None, dpdf=None, dpdc=None, dpddist=None)-> None
2011-05-15 21:16:53 +02:00
:param objectPoints: Array of object points, 3xN/Nx3 1-channel or 1xN/Nx1 3-channel (or ``vector<Point3f>`` ), where N is the number of points in the view.
2011-02-26 12:05:10 +01:00
:param rvec: Rotation vector. See :ocv:func:`Rodrigues` for details.
2011-05-15 21:16:53 +02:00
:param tvec: Translation vector.
2011-02-26 12:05:10 +01:00
2011-05-15 21:16:53 +02:00
:param cameraMatrix: Camera matrix :math:`A = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{_1}` .
2011-05-15 21:16:53 +02:00
:param distCoeffs: Input vector of distortion coefficients :math:`(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6]])` of 4, 5, or 8 elements. If the vector is NULL/empty, the zero distortion coefficients are assumed.
2011-05-15 21:16:53 +02:00
:param imagePoints: Output array of image points, 2xN/Nx2 1-channel or 1xN/Nx1 2-channel, or ``vector<Point2f>`` .
:param jacobian: Optional output 2Nx(10+<numDistCoeffs>) jacobian matrix of derivatives of image points with respect to components of the rotation vector, translation vector, focal lengths, coordinates of the principal point and the distortion coefficients. In the old interface different components of the jacobian are returned via different output parameters.
:param aspectRatio: Optional "fixed aspect ratio" parameter. If the parameter is not 0, the function assumes that the aspect ratio (*fx/fy*) is fixed and correspondingly adjusts the jacobian matrix.
The function computes projections of 3D
points to the image plane given intrinsic and extrinsic camera
2011-05-15 21:16:53 +02:00
parameters. Optionally, the function computes Jacobians - matrices
of partial derivatives of image points coordinates (as functions of all the
input parameters) with respect to the particular parameters, intrinsic and/or
2011-05-15 21:16:53 +02:00
extrinsic. The Jacobians are used during the global optimization
2011-02-26 12:05:10 +01:00
in
:ocv:func:`calibrateCamera`,
:ocv:func:`solvePnP`, and
:ocv:func:`stereoCalibrate` . The
2011-05-15 21:16:53 +02:00
function itself can also be used to compute a re-projection error given the
current intrinsic and extrinsic parameters.
.. note:: By setting ``rvec=tvec=(0,0,0)`` or by setting ``cameraMatrix`` to a 3x3 identity matrix, or by passing zero distortion coefficients, you can get various useful partial cases of the function. This means that you can compute the distorted coordinates for a sparse set of points or apply a perspective transformation (and also compute the derivatives) in the ideal zero-distortion setup.
2011-03-08 23:22:24 +01:00
reprojectImageTo3D
----------------------
Reprojects a disparity image to 3D space.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void reprojectImageTo3D( InputArray disparity, OutputArray _3dImage, InputArray Q, bool handleMissingValues=false, int depth=-1 )
.. ocv:pyfunction:: cv2.reprojectImageTo3D(disparity, Q[, _3dImage[, handleMissingValues[, ddepth]]]) -> _3dImage
.. ocv:cfunction:: void cvReprojectImageTo3D( const CvArr* disparity, CvArr* _3dImage, const CvMat* Q, int handleMissingValues=0)
.. ocv:pyoldfunction:: cv.ReprojectImageTo3D(disparity, _3dImage, Q, handleMissingValues=0) -> None
2011-05-15 21:16:53 +02:00
:param disparity: Input single-channel 16-bit signed or 32-bit floating-point disparity image.
2011-05-15 21:16:53 +02:00
:param _3dImage: Output 3-channel floating-point image of the same size as ``disparity`` . Each element of ``_3dImage(x,y)`` contains 3D coordinates of the point ``(x,y)`` computed from the disparity map.
:param Q: :math:`4 \times 4` perspective transformation matrix that can be obtained with :ocv:func:`StereoRectify` .
:param handleMissingValues: Indicates, whether the function should handle missing values (i.e. points where the disparity was not computed). If ``handleMissingValues=true``, then pixels with the minimal disparity that corresponds to the outliers (see :ocv:func:`StereoBM::operator()` ) are transformed to 3D points with a very large Z value (currently set to 10000).
:param ddepth: The optional output array depth. If it is ``-1``, the output image will have ``CV_32F`` depth. ``ddepth`` can also be set to ``CV_16S``, ``CV_32S`` or ``CV_32F``.
2011-05-15 21:16:53 +02:00
The function transforms a single-channel disparity map to a 3-channel image representing a 3D surface. That is, for each pixel ``(x,y)`` andthe corresponding disparity ``d=disparity(x,y)`` , it computes:
.. math::
2011-02-26 12:05:10 +01:00
\begin{array}{l} [X \; Y \; Z \; W]^T = \texttt{Q} *[x \; y \; \texttt{disparity} (x,y) \; 1]^T \\ \texttt{\_3dImage} (x,y) = (X/W, \; Y/W, \; Z/W) \end{array}
2011-05-15 21:16:53 +02:00
The matrix ``Q`` can be an arbitrary
:math:`4 \times 4` matrix (for example, the one computed by
:ocv:func:`StereoRectify`). To reproject a sparse set of points {(x,y,d),...} to 3D space, use
:ocv:func:`PerspectiveTransform` .
2011-03-08 23:22:24 +01:00
RQDecomp3x3
---------------
Computes an RQ decomposition of 3x3 matrices.
2011-06-16 14:48:23 +02:00
.. ocv:function:: Vec3d RQDecomp3x3( InputArray M, OutputArray R, OutputArray Q, OutputArray Qx=noArray(), OutputArray Qy=noArray(), OutputArray Qz=noArray() )
.. ocv:pyfunction:: cv2.RQDecomp3x3(src[, mtxR[, mtxQ[, Qx[, Qy[, Qz]]]]]) -> retval, mtxR, mtxQ, Qx, Qy, Qz
.. ocv:cfunction:: void cvRQDecomp3x3( const CvMat *M, CvMat *R, CvMat *Q, CvMat *Qx=NULL, CvMat *Qy=NULL, CvMat *Qz=NULL, CvPoint3D64f *eulerAngles=NULL)
.. ocv:pyoldfunction:: cv.RQDecomp3x3(M, R, Q, Qx=None, Qy=None, Qz=None) -> eulerAngles
2011-05-15 21:16:53 +02:00
:param M: 3x3 input matrix.
2011-05-15 21:16:53 +02:00
:param R: Output 3x3 upper-triangular matrix.
2011-05-15 21:16:53 +02:00
:param Q: Output 3x3 orthogonal matrix.
:param Qx: Optional output 3x3 rotation matrix around x-axis.
:param Qy: Optional output 3x3 rotation matrix around y-axis.
:param Qz: Optional output 3x3 rotation matrix around z-axis.
2011-02-26 12:05:10 +01:00
The function computes a RQ decomposition using the given rotations. This function is used in
:ocv:func:`DecomposeProjectionMatrix` to decompose the left 3x3 submatrix of a projection matrix into a camera and a rotation matrix.
2011-02-26 12:05:10 +01:00
It optionally returns three rotation matrices, one for each axis, and the three Euler angles
(as the return value)
that could be used in OpenGL.
2011-03-08 23:22:24 +01:00
Rodrigues
-------------
Converts a rotation matrix to a rotation vector or vice versa.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void Rodrigues(InputArray src, OutputArray dst, OutputArray jacobian=noArray())
.. ocv:pyfunction:: cv2.Rodrigues(src[, dst[, jacobian]]) -> dst, jacobian
.. ocv:cfunction:: int cvRodrigues2( const CvMat* src, CvMat* dst, CvMat* jacobian=0 )
.. ocv:pyoldfunction:: cv.Rodrigues2(src, dst, jacobian=0)-> None
2011-05-15 21:16:53 +02:00
:param src: Input rotation vector (3x1 or 1x3) or rotation matrix (3x3).
2011-05-15 21:16:53 +02:00
:param dst: Output rotation matrix (3x3) or rotation vector (3x1 or 1x3), respectively.
:param jacobian: Optional output Jacobian matrix, 3x9 or 9x3, which is a matrix of partial derivatives of the output array components with respect to the input array components.
.. math::
2011-02-26 12:05:10 +01:00
\begin{array}{l} \theta \leftarrow norm(r) \\ r \leftarrow r/ \theta \\ R = \cos{\theta} I + (1- \cos{\theta} ) r r^T + \sin{\theta} \vecthreethree{0}{-r_z}{r_y}{r_z}{0}{-r_x}{-r_y}{r_x}{0} \end{array}
2011-05-15 21:16:53 +02:00
Inverse transformation can be also done easily, since
.. math::
2011-02-26 12:05:10 +01:00
\sin ( \theta ) \vecthreethree{0}{-r_z}{r_y}{r_z}{0}{-r_x}{-r_y}{r_x}{0} = \frac{R - R^T}{2}
2011-05-15 21:16:53 +02:00
A rotation vector is a convenient and most compact representation of a rotation matrix
(since any rotation matrix has just 3 degrees of freedom). The representation is
2011-02-26 12:05:10 +01:00
used in the global 3D geometry optimization procedures like
:ocv:func:`calibrateCamera`,
:ocv:func:`stereoCalibrate`, or
:ocv:func:`solvePnP` .
StereoBM
--------
.. ocv:class:: StereoBM
Class for computing stereo correspondence using the block matching algorithm. ::
2011-05-15 21:16:53 +02:00
// Block matching stereo correspondence algorithm class StereoBM
{
enum { NORMALIZED_RESPONSE = CV_STEREO_BM_NORMALIZED_RESPONSE,
BASIC_PRESET=CV_STEREO_BM_BASIC,
FISH_EYE_PRESET=CV_STEREO_BM_FISH_EYE,
NARROW_PRESET=CV_STEREO_BM_NARROW };
2011-02-26 12:05:10 +01:00
StereoBM();
// the preset is one of ..._PRESET above.
// ndisparities is the size of disparity range,
// in which the optimal disparity at each pixel is searched for.
// SADWindowSize is the size of averaging window used to match pixel blocks
// (larger values mean better robustness to noise, but yield blurry disparity maps)
StereoBM(int preset, int ndisparities=0, int SADWindowSize=21);
// separate initialization function
void init(int preset, int ndisparities=0, int SADWindowSize=21);
// computes the disparity for the two rectified 8-bit single-channel images.
// the disparity will be 16-bit signed (fixed-point) or 32-bit floating-point image of the same size as left.
void operator()( InputArray left, InputArray right, OutputArray disparity, int disptype=CV_16S );
2011-02-26 12:05:10 +01:00
Ptr<CvStereoBMState> state;
};
The class is a C++ wrapper for the associated functions. In particular, ``StereoBM::operator()`` is the wrapper for
:ocv:func:`StereoBM::operator()`.
StereoBM::StereoBM
---------------------
The constructors.
.. ocv:function:: StereoBM::StereoBM()
.. ocv:function:: StereoBM::StereoBM(int preset, int ndisparities=0, int SADWindowSize=21)
.. ocv:pyfunction:: cv2.StereoBM.StereoBM(preset[, ndisparities[, SADWindowSize]]) -> <StereoBM object>
2011-03-08 23:22:24 +01:00
.. ocv:cfunction:: CvStereoBMState* cvCreateStereoBMState( int preset=CV_STEREO_BM_BASIC, int ndisparities=0 )
2011-03-08 23:22:24 +01:00
.. ocv:pyoldfunction:: cv.CreateStereoBMState(preset=CV_STEREO_BM_BASIC, ndisparities=0)-> StereoBMState
:param preset: specifies the whole set of algorithm parameters, one of:
* BASIC_PRESET - parameters suitable for general cameras
* FISH_EYE_PRESET - parameters suitable for wide-angle cameras
* NARROW_PRESET - parameters suitable for narrow-angle cameras
After constructing the class, you can override any parameters set by the preset.
:param ndisparities: the disparity search range. For each pixel algorithm will find the best disparity from 0 (default minimum disparity) to ``ndisparities``. The search range can then be shifted by changing the minimum disparity.
:param SADWindowSize: the linear size of the blocks compared by the algorithm. The size should be odd (as the block is centered at the current pixel). Larger block size implies smoother, though less accurate disparity map. Smaller block size gives more detailed disparity map, but there is higher chance for algorithm to find a wrong correspondence.
The constructors initialize ``StereoBM`` state. You can then call ``StereoBM::operator()`` to compute disparity for a specific stereo pair.
.. note:: In the C API you need to deallocate ``CvStereoBM`` state when it is not needed anymore using ``cvReleaseStereoBMState(&stereobm)``.
2011-03-08 23:22:24 +01:00
StereoBM::operator()
2011-03-08 23:22:24 +01:00
-----------------------
Computes disparity using the BM algorithm for a rectified stereo pair.
2011-03-08 23:22:24 +01:00
2011-06-16 14:48:23 +02:00
.. ocv:function:: void StereoBM::operator()(InputArray left, InputArray right, OutputArray disp, int disptype=CV_16S )
2011-03-08 23:22:24 +01:00
.. ocv:pyfunction:: cv2.StereoBM.compute(left, right[, disparity[, disptype]]) -> disparity
.. ocv:cfunction:: void cvFindStereoCorrespondenceBM( const CvArr* left, const CvArr* right, CvArr* disparity, CvStereoBMState* state )
.. ocv:pyoldfunction:: cv.FindStereoCorrespondenceBM(left, right, disparity, state)-> None
2011-03-08 23:22:24 +01:00
2011-05-15 21:16:53 +02:00
:param left: Left 8-bit single-channel or 3-channel image.
2011-03-08 23:22:24 +01:00
2011-05-15 21:16:53 +02:00
:param right: Right image of the same size and the same type as the left one.
2011-03-08 23:22:24 +01:00
:param disp: Output disparity map. It has the same size as the input images. When ``disptype==CV_16S``, the map is a 16-bit signed single-channel image, containing disparity values scaled by 16. To get the true disparity values from such fixed-point representation, you will need to divide each ``disp`` element by 16. If ``disptype==CV_32F``, the disparity map will already contain the real disparity values on output.
2011-03-08 23:22:24 +01:00
2011-05-15 21:16:53 +02:00
:param disptype: Type of the output disparity map, ``CV_16S`` (default) or ``CV_32F``.
:param state: The pre-initialized ``CvStereoBMState`` structure in the case of the old API.
2011-03-08 23:22:24 +01:00
2011-05-15 21:16:53 +02:00
The method executes the BM algorithm on a rectified stereo pair. See the ``stereo_match.cpp`` OpenCV sample on how to prepare images and call the method. Note that the method is not constant, thus you should not use the same ``StereoBM`` instance from within different threads simultaneously.
2011-03-08 23:22:24 +01:00
StereoSGBM
----------
2011-03-08 23:22:24 +01:00
.. ocv:class:: StereoSGBM
Class for computing stereo correspondence using the semi-global block matching algorithm. ::
class StereoSGBM
{
StereoSGBM();
StereoSGBM(int minDisparity, int numDisparities, int SADWindowSize,
int P1=0, int P2=0, int disp12MaxDiff=0,
int preFilterCap=0, int uniquenessRatio=0,
int speckleWindowSize=0, int speckleRange=0,
bool fullDP=false);
virtual ~StereoSGBM();
2011-02-26 12:05:10 +01:00
virtual void operator()(InputArray left, InputArray right, OutputArray disp);
2011-02-26 12:05:10 +01:00
int minDisparity;
int numberOfDisparities;
int SADWindowSize;
int preFilterCap;
int uniquenessRatio;
int P1, P2;
int speckleWindowSize;
int speckleRange;
int disp12MaxDiff;
bool fullDP;
2011-02-26 12:05:10 +01:00
...
};
2011-05-15 21:16:53 +02:00
The class implements the modified H. Hirschmuller algorithm HH08 that differs from the original one as follows:
2011-05-15 21:16:53 +02:00
* By default, the algorithm is single-pass, which means that you consider only 5 directions instead of 8. Set ``fullDP=true`` to run the full variant of the algorithm but beware that it may consume a lot of memory.
2011-05-15 21:16:53 +02:00
* The algorithm matches blocks, not individual pixels. Though, setting ``SADWindowSize=1`` reduces the blocks to single pixels.
2011-05-15 21:16:53 +02:00
* Mutual information cost function is not implemented. Instead, a simpler Birchfield-Tomasi sub-pixel metric from BT96 is used. Though, the color images are supported as well.
* Some pre- and post- processing steps from K. Konolige algorithm :ocv:func:`StereoBM::operator()` are included, for example: pre-filtering (``CV_STEREO_BM_XSOBEL`` type) and post-filtering (uniqueness check, quadratic interpolation and speckle filtering).
2011-03-08 23:22:24 +01:00
StereoSGBM::StereoSGBM
--------------------------
2011-06-16 14:48:23 +02:00
.. ocv:function:: StereoSGBM::StereoSGBM()
2011-06-16 14:48:23 +02:00
.. ocv:function:: StereoSGBM::StereoSGBM( int minDisparity, int numDisparities, int SADWindowSize, int P1=0, int P2=0, int disp12MaxDiff=0, int preFilterCap=0, int uniquenessRatio=0, int speckleWindowSize=0, int speckleRange=0, bool fullDP=false)
.. ocv:pyfunction:: cv2.StereoSGBM.StereoSGBM(minDisparity, numDisparities, SADWindowSize[, P1[, P2[, disp12MaxDiff[, preFilterCap[, uniquenessRatio[, speckleWindowSize[, speckleRange[, fullDP]]]]]]]]) -> <StereoSGBM object>
Initializes ``StereoSGBM`` and sets parameters to custom values.??
2011-05-15 21:16:53 +02:00
:param minDisparity: Minimum possible disparity value. Normally, it is zero but sometimes rectification algorithms can shift images, so this parameter needs to be adjusted accordingly.
2011-05-15 21:16:53 +02:00
:param numDisparities: Maximum disparity minus minimum disparity. The value is always greater than zero. In the current implementation, this parameter must be divisible by 16.
2011-05-15 21:16:53 +02:00
:param SADWindowSize: Matched block size. It must be an odd number ``>=1`` . Normally, it should be somewhere in the ``3..11`` range.
:param P1: The first parameter controlling the disparity smoothness. See below.
:param P2: The second parameter controlling the disparity smoothness. The larger the values are, the smoother the disparity is. ``P1`` is the penalty on the disparity change by plus or minus 1 between neighbor pixels. ``P2`` is the penalty on the disparity change by more than 1 between neighbor pixels. The algorithm requires ``P2 > P1`` . See ``stereo_match.cpp`` sample where some reasonably good ``P1`` and ``P2`` values are shown (like ``8*number_of_image_channels*SADWindowSize*SADWindowSize`` and ``32*number_of_image_channels*SADWindowSize*SADWindowSize`` , respectively).
2011-05-15 21:16:53 +02:00
:param disp12MaxDiff: Maximum allowed difference (in integer pixel units) in the left-right disparity check. Set it to a non-positive value to disable the check.
2011-02-26 12:05:10 +01:00
:param preFilterCap: Truncation value for the prefiltered image pixels. The algorithm first computes x-derivative at each pixel and clips its value by ``[-preFilterCap, preFilterCap]`` interval. The result values are passed to the Birchfield-Tomasi pixel cost function.
2011-05-15 21:16:53 +02:00
:param uniquenessRatio: Margin in percentage by which the best (minimum) computed cost function value should "win" the second best value to consider the found match correct. Normally, a value within the 5-15 range is good enough.
2011-05-15 21:16:53 +02:00
:param speckleWindowSize: Maximum size of smooth disparity regions to consider their noise speckles and invalidate. Set it to 0 to disable speckle filtering. Otherwise, set it somewhere in the 50-200 range.
2011-05-15 21:16:53 +02:00
:param speckleRange: Maximum disparity variation within each connected component. If you do speckle filtering, set the parameter to a positive value, multiple of 16. Normally, 16 or 32 is good enough.
2011-05-15 21:16:53 +02:00
:param fullDP: Set it to ``true`` to run the full-scale two-pass dynamic programming algorithm. It will consume O(W*H*numDisparities) bytes, which is large for 640x480 stereo and huge for HD-size pictures. By default, it is set to ``false`` .
2011-05-15 21:16:53 +02:00
The first constructor initializes ``StereoSGBM`` with all the default parameters. So, you only have to set ``StereoSGBM::numberOfDisparities`` at minimum. The second constructor enables you to set each parameter to a custom value.
2011-03-08 23:22:24 +01:00
StereoSGBM::operator ()
-----------------------
2011-06-16 14:48:23 +02:00
.. ocv:function:: void StereoSGBM::operator()(InputArray left, InputArray right, OutputArray disp)
.. ocv:pyfunction:: cv2.StereoSGBM.compute(left, right[, disp]) -> disp
2011-05-15 21:16:53 +02:00
Computes disparity using the SGBM algorithm for a rectified stereo pair.
2011-05-15 21:16:53 +02:00
:param left: Left 8-bit single-channel or 3-channel image.
2011-05-15 21:16:53 +02:00
:param right: Right image of the same size and the same type as the left one.
2011-05-15 21:16:53 +02:00
:param disp: Output disparity map. It is a 16-bit signed single-channel image of the same size as the input image. It contains disparity values scaled by 16. So, to get the floating-point disparity map, you need to divide each ``disp`` element by 16.
2011-05-15 21:16:53 +02:00
The method executes the SGBM algorithm on a rectified stereo pair. See ``stereo_match.cpp`` OpenCV sample on how to prepare images and call the method.
.. note:: The method is not constant, so you should not use the same ``StereoSGBM`` instance from different threads simultaneously.
2011-03-08 23:22:24 +01:00
stereoCalibrate
-------------------
Calibrates the stereo camera.
.. ocv:function:: double stereoCalibrate( InputArrayOfArrays objectPoints, InputArrayOfArrays imagePoints1, InputArrayOfArrays imagePoints2, InputOutputArray cameraMatrix1, InputOutputArray distCoeffs1, InputOutputArray cameraMatrix2, InputOutputArray distCoeffs2, Size imageSize, OutputArray R, OutputArray T, OutputArray E, OutputArray F, TermCriteria term_crit = TermCriteria(TermCriteria::COUNT+ TermCriteria::EPS, 30, 1e-6), int flags=CALIB_FIX_INTRINSIC )
.. ocv:pyfunction:: cv2.stereoCalibrate(objectPoints, imagePoints1, imagePoints2, cameraMatrix1, distCoeffs1, cameraMatrix2, distCoeffs2, imageSize[, R[, T[, E[, F[, criteria[, flags]]]]]]) -> retval, cameraMatrix1, distCoeffs1, cameraMatrix2, distCoeffs2, R, T, E, F
.. ocv:cfunction:: double cvStereoCalibrate( const CvMat* objectPoints, const CvMat* imagePoints1, const CvMat* imagePoints2, const CvMat* pointCounts, CvMat* cameraMatrix1, CvMat* distCoeffs1, CvMat* cameraMatrix2, CvMat* distCoeffs2, CvSize imageSize, CvMat* R, CvMat* T, CvMat* E=0, CvMat* F=0, CvTermCriteria termCrit=cvTermCriteria( CV_TERMCRIT_ITER+CV_TERMCRIT_EPS, 30, 1e-6), int flags=CV_CALIB_FIX_INTRINSIC )
.. ocv:pyoldfunction:: cv.StereoCalibrate( objectPoints, imagePoints1, imagePoints2, pointCounts, cameraMatrix1, distCoeffs1, cameraMatrix2, distCoeffs2, imageSize, R, T, E=None, F=None, termCrit=(CV_TERMCRIT_ITER+CV_TERMCRIT_EPS, 30, 1e-6), flags=CV_CALIB_FIX_INTRINSIC)-> None
:param objectPoints: Vector of vectors of the calibration pattern points.
:param imagePoints1: Vector of vectors of the projections of the calibration pattern points, observed by the first camera.
:param imagePoints2: Vector of vectors of the projections of the calibration pattern points, observed by the second camera.
:param cameraMatrix1: Input/output first camera matrix: :math:`\vecthreethree{f_x^{(j)}}{0}{c_x^{(j)}}{0}{f_y^{(j)}}{c_y^{(j)}}{0}{0}{1}` , :math:`j = 0,\, 1` . If any of ``CV_CALIB_USE_INTRINSIC_GUESS`` , ``CV_CALIB_FIX_ASPECT_RATIO`` , ``CV_CALIB_FIX_INTRINSIC`` , or ``CV_CALIB_FIX_FOCAL_LENGTH`` are specified, some or all of the matrix components must be initialized. See the flags description for details.
:param distCoeffs1: Input/output vector of distortion coefficients :math:`(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6]])` of 4, 5, or 8 elements. The output vector length depends on the flags.
2011-05-15 21:16:53 +02:00
:param cameraMatrix2: Input/output second camera matrix. The parameter is similar to ``cameraMatrix1`` .
2011-05-15 21:16:53 +02:00
:param distCoeffs2: Input/output lens distortion coefficients for the second camera. The parameter is similar to ``distCoeffs1`` .
2011-05-15 21:16:53 +02:00
:param imageSize: Size of the image used only to initialize intrinsic camera matrix.
2011-05-15 21:16:53 +02:00
:param R: Output rotation matrix between the 1st and the 2nd camera coordinate systems.
2011-05-15 21:16:53 +02:00
:param T: Output translation vector between the coordinate systems of the cameras.
2011-05-15 21:16:53 +02:00
:param E: Output essential matrix.
2011-05-15 21:16:53 +02:00
:param F: Output fundamental matrix.
2011-05-15 21:16:53 +02:00
:param term_crit: Termination criteria for the iterative optimization algorithm.
2011-05-15 21:16:53 +02:00
:param flags: Different flags that may be zero or a combination of the following values:
2011-05-15 21:16:53 +02:00
* **CV_CALIB_FIX_INTRINSIC** Fix ``cameraMatrix?`` and ``distCoeffs?`` so that only ``R, T, E`` , and ``F`` matrices are estimated.
2011-05-15 21:16:53 +02:00
* **CV_CALIB_USE_INTRINSIC_GUESS** Optimize some or all of the intrinsic parameters according to the specified flags. Initial values are provided by the user.
2011-05-15 21:16:53 +02:00
* **CV_CALIB_FIX_PRINCIPAL_POINT** Fix the principal points during the optimization.
2011-05-15 21:16:53 +02:00
* **CV_CALIB_FIX_FOCAL_LENGTH** Fix :math:`f^{(j)}_x` and :math:`f^{(j)}_y` .
2011-05-15 21:16:53 +02:00
* **CV_CALIB_FIX_ASPECT_RATIO** Optimize :math:`f^{(j)}_y` . Fix the ratio :math:`f^{(j)}_x/f^{(j)}_y` .
2011-05-15 21:16:53 +02:00
* **CV_CALIB_SAME_FOCAL_LENGTH** Enforce :math:`f^{(0)}_x=f^{(1)}_x` and :math:`f^{(0)}_y=f^{(1)}_y` .
2011-05-15 21:16:53 +02:00
* **CV_CALIB_ZERO_TANGENT_DIST** Set tangential distortion coefficients for each camera to zeros and fix there.
2011-05-15 21:16:53 +02:00
* **CV_CALIB_FIX_K1,...,CV_CALIB_FIX_K6** Do not change the corresponding radial distortion coefficient during the optimization. If ``CV_CALIB_USE_INTRINSIC_GUESS`` is set, the coefficient from the supplied ``distCoeffs`` matrix is used. Otherwise, it is set to 0.
2011-05-15 21:16:53 +02:00
* **CV_CALIB_RATIONAL_MODEL** Enable coefficients k4, k5, and k6. To provide the backward compatibility, this extra flag should be explicitly specified to make the calibration function use the rational model and return 8 coefficients. If the flag is not set, the function computes and returns only 5 distortion coefficients.
2011-05-15 21:16:53 +02:00
The function estimates transformation between two cameras making a stereo pair. If you have a stereo camera where the relative position and orientation of two cameras is fixed, and if you computed poses of an object relative to the first camera and to the second camera, (R1, T1) and (R2, T2), respectively (this can be done with
:ocv:func:`solvePnP` ), then those poses definitely relate to each other. This means that, given (
2011-05-15 21:16:53 +02:00
:math:`R_1`,:math:`T_1` ), it should be possible to compute (
:math:`R_2`,:math:`T_2` ). You only need to know the position and orientation of the second camera relative to the first camera. This is what the described function does. It computes (
:math:`R`,:math:`T` ) so that:
2011-02-26 12:05:10 +01:00
.. math::
R_2=R*R_1
T_2=R*T_1 + T,
Optionally, it computes the essential matrix E:
.. math::
2011-02-26 12:05:10 +01:00
E= \vecthreethree{0}{-T_2}{T_1}{T_2}{0}{-T_0}{-T_1}{T_0}{0} *R
2011-02-26 12:05:10 +01:00
where
:math:`T_i` are components of the translation vector
:math:`T` :
2011-05-15 21:16:53 +02:00
:math:`T=[T_0, T_1, T_2]^T` . And the function can also compute the fundamental matrix F:
2011-02-26 12:05:10 +01:00
.. math::
2011-02-26 12:05:10 +01:00
F = cameraMatrix2^{-T} E cameraMatrix1^{-1}
2011-05-15 21:16:53 +02:00
Besides the stereo-related information, the function can also perform a full calibration of each of two cameras. However, due to the high dimensionality of the parameter space and noise in the input data, the function can diverge from the correct solution. If the intrinsic parameters can be estimated with high accuracy for each of the cameras individually (for example, using
:ocv:func:`calibrateCamera` ), you are recommended to do so and then pass ``CV_CALIB_FIX_INTRINSIC`` flag to the function along with the computed intrinsic parameters. Otherwise, if all the parameters are estimated at once, it makes sense to restrict some parameters, for example, pass ``CV_CALIB_SAME_FOCAL_LENGTH`` and ``CV_CALIB_ZERO_TANGENT_DIST`` flags, which is usually a reasonable assumption.
2011-02-26 12:05:10 +01:00
Similarly to :ocv:func:`calibrateCamera` , the function minimizes the total re-projection error for all the points in all the available views from both cameras. The function returns the final value of the re-projection error.
2011-03-08 23:22:24 +01:00
stereoRectify
-----------------
Computes rectification transforms for each head of a calibrated stereo camera.
2011-06-16 14:48:23 +02:00
.. ocv:function:: void stereoRectify( InputArray cameraMatrix1, InputArray distCoeffs1, InputArray cameraMatrix2, InputArray distCoeffs2, Size imageSize, InputArray R, InputArray T, OutputArray R1, OutputArray R2, OutputArray P1, OutputArray P2, OutputArray Q, int flags=CALIB_ZERO_DISPARITY, double alpha, Size newImageSize=Size(), Rect* roi1=0, Rect* roi2=0 )
.. ocv:cfunction:: void cvStereoRectify( const CvMat* cameraMatrix1, const CvMat* cameraMatrix2, const CvMat* distCoeffs1, const CvMat* distCoeffs2, CvSize imageSize, const CvMat* R, const CvMat* T, CvMat* R1, CvMat* R2, CvMat* P1, CvMat* P2, CvMat* Q=0, int flags=CV_CALIB_ZERO_DISPARITY, double alpha=-1, CvSize newImageSize=cvSize(0, 0), CvRect* roi1=0, CvRect* roi2=0)
.. ocv:pyoldfunction:: cv.StereoRectify( cameraMatrix1, cameraMatrix2, distCoeffs1, distCoeffs2, imageSize, R, T, R1, R2, P1, P2, Q=None, flags=CV_CALIB_ZERO_DISPARITY, alpha=-1, newImageSize=(0, 0))-> (roi1, roi2)
:param cameraMatrix1: First camera matrix.
:param cameraMatrix2: Second camera matrix.
:param distCoeffs1: First camera distortion parameters.
:param distCoeffs2: Second camera distortion parameters.
2011-02-26 12:05:10 +01:00
:param imageSize: Size of the image used for stereo calibration.
2011-05-15 21:16:53 +02:00
:param R: Rotation matrix between the coordinate systems of the first and the second cameras.
2011-05-15 21:16:53 +02:00
:param T: Translation vector between coordinate systems of the cameras.
:param R1: Output 3x3 rectification transform (rotation matrix) for the first camera.
:param R2: Output 3x3 rectification transform (rotation matrix) for the second camera.
:param P1: Output 3x4 projection matrix in the new (rectified) coordinate systems for the first camera.
:param P2: Output 3x4 projection matrix in the new (rectified) coordinate systems for the second camera.
2011-02-26 12:05:10 +01:00
:param Q: Output :math:`4 \times 4` disparity-to-depth mapping matrix (see :ocv:func:`reprojectImageTo3D` ).
2011-05-15 21:16:53 +02:00
:param flags: Operation flags that may be zero or ``CV_CALIB_ZERO_DISPARITY`` . If the flag is set, the function makes the principal points of each camera have the same pixel coordinates in the rectified views. And if the flag is not set, the function may still shift the images in the horizontal or vertical direction (depending on the orientation of epipolar lines) to maximize the useful image area.
2011-05-15 21:16:53 +02:00
:param alpha: Free scaling parameter. If it is -1 or absent, the function performs the default scaling. Otherwise, the parameter should be between 0 and 1. ``alpha=0`` means that the rectified images are zoomed and shifted so that only valid pixels are visible (no black areas after rectification). ``alpha=1`` means that the rectified image is decimated and shifted so that all the pixels from the original images from the cameras are retained in the rectified images (no source image pixels are lost). Obviously, any intermediate value yields an intermediate result between those two extreme cases.
:param newImageSize: New image resolution after rectification. The same size should be passed to :ocv:func:`initUndistortRectifyMap` (see the ``stereo_calib.cpp`` sample in OpenCV samples directory). When (0,0) is passed (default), it is set to the original ``imageSize`` . Setting it to larger value can help you preserve details in the original image, especially when there is a big radial distortion.
:param roi1:
:param roi2: Optional output rectangles inside the rectified images where all the pixels are valid. If ``alpha=0`` , the ROIs cover the whole images. Otherwise, they are likely to be smaller (see the picture below).
2011-05-15 21:16:53 +02:00
The function computes the rotation matrices for each camera that (virtually) make both camera image planes the same plane. Consequently, this makes all the epipolar lines parallel and thus simplifies the dense stereo correspondence problem. The function takes the matrices computed by
:ocv:func:`stereoCalibrate` as input. As output, it provides two rotation matrices and also two projection matrices in the new coordinates. The function distinguishes the following two cases:
#.
2011-05-15 21:16:53 +02:00
**Horizontal stereo**: the first and the second camera views are shifted relative to each other mainly along the x axis (with possible small vertical shift). In the rectified images, the corresponding epipolar lines in the left and right cameras are horizontal and have the same y-coordinate. P1 and P2 look like:
2011-02-26 12:05:10 +01:00
.. math::
2011-02-26 12:05:10 +01:00
\texttt{P1} = \begin{bmatrix} f & 0 & cx_1 & 0 \\ 0 & f & cy & 0 \\ 0 & 0 & 1 & 0 \end{bmatrix}
.. math::
2011-02-26 12:05:10 +01:00
\texttt{P2} = \begin{bmatrix} f & 0 & cx_2 & T_x*f \\ 0 & f & cy & 0 \\ 0 & 0 & 1 & 0 \end{bmatrix} ,
where
2011-05-15 21:16:53 +02:00
:math:`T_x` is a horizontal shift between the cameras and
2011-02-26 12:05:10 +01:00
:math:`cx_1=cx_2` if ``CV_CALIB_ZERO_DISPARITY`` is set.
#.
2011-05-15 21:16:53 +02:00
**Vertical stereo**: the first and the second camera views are shifted relative to each other mainly in vertical direction (and probably a bit in the horizontal direction too). The epipolar lines in the rectified images are vertical and have the same x-coordinate. P1 and P2 look like:
2011-02-26 12:05:10 +01:00
.. math::
2011-02-26 12:05:10 +01:00
\texttt{P1} = \begin{bmatrix} f & 0 & cx & 0 \\ 0 & f & cy_1 & 0 \\ 0 & 0 & 1 & 0 \end{bmatrix}
2011-02-26 12:05:10 +01:00
.. math::
2011-02-26 12:05:10 +01:00
\texttt{P2} = \begin{bmatrix} f & 0 & cx & 0 \\ 0 & f & cy_2 & T_y*f \\ 0 & 0 & 1 & 0 \end{bmatrix} ,
2011-02-26 12:05:10 +01:00
where
2011-05-15 21:16:53 +02:00
:math:`T_y` is a vertical shift between the cameras and
2011-02-26 12:05:10 +01:00
:math:`cy_1=cy_2` if ``CALIB_ZERO_DISPARITY`` is set.
2011-05-15 21:16:53 +02:00
As you can see, the first three columns of ``P1`` and ``P2`` will effectively be the new "rectified" camera matrices.
2011-02-26 12:05:10 +01:00
The matrices, together with ``R1`` and ``R2`` , can then be passed to
:ocv:func:`initUndistortRectifyMap` to initialize the rectification map for each camera.
2011-05-15 21:16:53 +02:00
See below the screenshot from the ``stereo_calib.cpp`` sample. Some red horizontal lines pass through the corresponding image regions. This means that the images are well rectified, which is what most stereo correspondence algorithms rely on. The green rectangles are ``roi1`` and ``roi2`` . You see that their interiors are all valid pixels.
2011-03-03 08:29:55 +01:00
.. image:: pics/stereo_undistort.jpg
2011-03-08 23:22:24 +01:00
stereoRectifyUncalibrated
-----------------------------
Computes a rectification transform for an uncalibrated stereo camera.
.. ocv:function:: bool stereoRectifyUncalibrated( InputArray points1, InputArray points2, InputArray F, Size imgSize, OutputArray H1, OutputArray H2, double threshold=5 )
.. ocv:pyfunction:: cv2.stereoRectifyUncalibrated(points1, points2, F, imgSize[, H1[, H2[, threshold]]]) -> retval, H1, H2
.. ocv:cfunction:: void cvStereoRectifyUncalibrated( const CvMat* points1, const CvMat* points2, const CvMat* F, CvSize imageSize, CvMat* H1, CvMat* H2, double threshold=5 )
.. ocv:pyoldfunction:: cv.StereoRectifyUncalibrated(points1, points2, F, imageSize, H1, H2, threshold=5)-> None
:param points1: Array of feature points in the first image.
:param points2: The corresponding points in the second image. The same formats as in :ocv:func:`findFundamentalMat` are supported.
:param F: Input fundamental matrix. It can be computed from the same set of point pairs using :ocv:func:`findFundamentalMat` .
2011-02-26 12:05:10 +01:00
:param imageSize: Size of the image.
:param H1: Output rectification homography matrix for the first image.
:param H2: Output rectification homography matrix for the second image.
2011-05-15 21:16:53 +02:00
:param threshold: Optional threshold used to filter out the outliers. If the parameter is greater than zero, all the point pairs that do not comply with the epipolar geometry (that is, the points for which :math:`|\texttt{points2[i]}^T*\texttt{F}*\texttt{points1[i]}|>\texttt{threshold}` ) are rejected prior to computing the homographies. Otherwise,all the points are considered inliers.
2011-02-26 12:05:10 +01:00
2011-05-15 21:16:53 +02:00
The function computes the rectification transformations without knowing intrinsic parameters of the cameras and their relative position in the space, which explains the suffix "uncalibrated". Another related difference from
:ocv:func:`StereoRectify` is that the function outputs not the rectification transformations in the object (3D) space, but the planar perspective transformations encoded by the homography matrices ``H1`` and ``H2`` . The function implements the algorithm
[Hartley99]_.
.. note::
While the algorithm does not need to know the intrinsic parameters of the cameras, it heavily depends on the epipolar geometry. Therefore, if the camera lenses have a significant distortion, it would be better to correct it before computing the fundamental matrix and calling this function. For example, distortion coefficients can be estimated for each head of stereo camera separately by using :ocv:func:`calibrateCamera` . Then, the images can be corrected using :ocv:func:`undistort` , or just the point coordinates can be corrected with :ocv:func:`undistortPoints` .
.. [BouguetMCT] J.Y.Bouguet. MATLAB calibration tool. http://www.vision.caltech.edu/bouguetj/calib_doc/
2011-07-07 18:59:09 +02:00
.. [Hartley99] Hartley, R.I., Theory and Practice of Projective Rectification. IJCV 35 2, pp 115-127 (1999)
2011-05-15 21:16:53 +02:00
.. [Zhang2000] Z. Zhang. A Flexible New Technique for Camera Calibration. IEEE Transactions on Pattern Analysis and Machine Intelligence, 22(11):1330-1334, 2000.