2010-05-12 01:44:00 +08:00
|
|
|
/*M///////////////////////////////////////////////////////////////////////////////////////
|
|
|
|
//
|
|
|
|
// IMPORTANT: READ BEFORE DOWNLOADING, COPYING, INSTALLING OR USING.
|
|
|
|
//
|
|
|
|
// By downloading, copying, installing or using the software you agree to this license.
|
|
|
|
// If you do not agree to this license, do not download, install,
|
|
|
|
// copy or use the software.
|
|
|
|
//
|
|
|
|
//
|
2013-04-11 23:27:54 +08:00
|
|
|
// License Agreement
|
2010-05-12 01:44:00 +08:00
|
|
|
// For Open Source Computer Vision Library
|
|
|
|
//
|
|
|
|
// Copyright (C) 2000-2008, Intel Corporation, all rights reserved.
|
|
|
|
// Copyright (C) 2009, Willow Garage Inc., all rights reserved.
|
2013-03-22 05:05:30 +08:00
|
|
|
// Copyright (C) 2013, OpenCV Foundation, all rights reserved.
|
2010-05-12 01:44:00 +08:00
|
|
|
// Third party copyrights are property of their respective owners.
|
|
|
|
//
|
|
|
|
// Redistribution and use in source and binary forms, with or without modification,
|
|
|
|
// are permitted provided that the following conditions are met:
|
|
|
|
//
|
|
|
|
// * Redistribution's of source code must retain the above copyright notice,
|
|
|
|
// this list of conditions and the following disclaimer.
|
|
|
|
//
|
|
|
|
// * Redistribution's in binary form must reproduce the above copyright notice,
|
|
|
|
// this list of conditions and the following disclaimer in the documentation
|
|
|
|
// and/or other materials provided with the distribution.
|
|
|
|
//
|
|
|
|
// * The name of the copyright holders may not be used to endorse or promote products
|
|
|
|
// derived from this software without specific prior written permission.
|
|
|
|
//
|
|
|
|
// This software is provided by the copyright holders and contributors "as is" and
|
|
|
|
// any express or implied warranties, including, but not limited to, the implied
|
|
|
|
// warranties of merchantability and fitness for a particular purpose are disclaimed.
|
|
|
|
// In no event shall the Intel Corporation or contributors be liable for any direct,
|
|
|
|
// indirect, incidental, special, exemplary, or consequential damages
|
|
|
|
// (including, but not limited to, procurement of substitute goods or services;
|
|
|
|
// loss of use, data, or profits; or business interruption) however caused
|
|
|
|
// and on any theory of liability, whether in contract, strict liability,
|
|
|
|
// or tort (including negligence or otherwise) arising in any way out of
|
|
|
|
// the use of this software, even if advised of the possibility of such damage.
|
|
|
|
//
|
|
|
|
//M*/
|
|
|
|
|
2016-09-30 17:46:29 +08:00
|
|
|
#ifndef OPENCV_CALIB3D_HPP
|
|
|
|
#define OPENCV_CALIB3D_HPP
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2013-04-11 23:27:54 +08:00
|
|
|
#include "opencv2/core.hpp"
|
2013-03-13 20:22:44 +08:00
|
|
|
#include "opencv2/features2d.hpp"
|
2014-07-08 18:33:56 +08:00
|
|
|
#include "opencv2/core/affine.hpp"
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/**
|
|
|
|
@defgroup calib3d Camera Calibration and 3D Reconstruction
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
\f[s \; m' = A [R|t] M'\f]
|
|
|
|
|
|
|
|
or
|
|
|
|
|
|
|
|
\f[s \vecthree{u}{v}{1} = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}
|
|
|
|
\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}\f]
|
|
|
|
|
|
|
|
where:
|
|
|
|
|
|
|
|
- \f$(X, Y, Z)\f$ are the coordinates of a 3D point in the world coordinate space
|
|
|
|
- \f$(u, v)\f$ are the coordinates of the projection point in pixels
|
|
|
|
- \f$A\f$ is a camera matrix, or a matrix of intrinsic parameters
|
|
|
|
- \f$(cx, cy)\f$ is a principal point that is usually at the image center
|
|
|
|
- \f$fx, fy\f$ are the focal lengths expressed in pixel units.
|
|
|
|
|
|
|
|
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 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 \f$[R|t]\f$ 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 object in front of a still camera. That is, \f$[R|t]\f$ translates coordinates of a
|
|
|
|
point \f$(X, Y, Z)\f$ to a coordinate system, fixed with respect to the camera. The transformation above
|
|
|
|
is equivalent to the following (when \f$z \ne 0\f$ ):
|
|
|
|
|
|
|
|
\f[\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}\f]
|
|
|
|
|
2016-08-01 08:25:45 +08:00
|
|
|
The following figure illustrates the pinhole camera model.
|
|
|
|
|
|
|
|
![Pinhole camera model](pics/pinhole_camera_model.png)
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
Real lenses usually have some distortion, mostly radial distortion and slight tangential distortion.
|
|
|
|
So, the above model is extended as:
|
|
|
|
|
2015-10-14 18:07:28 +08:00
|
|
|
\f[\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) + s_1 r^2 + s_2 r^4 \\
|
|
|
|
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' + s_3 r^2 + s_4 r^4 \\
|
|
|
|
\text{where} \quad r^2 = x'^2 + y'^2 \\
|
|
|
|
u = f_x*x'' + c_x \\
|
|
|
|
v = f_y*y'' + c_y
|
|
|
|
\end{array}\f]
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
\f$k_1\f$, \f$k_2\f$, \f$k_3\f$, \f$k_4\f$, \f$k_5\f$, and \f$k_6\f$ are radial distortion coefficients. \f$p_1\f$ and \f$p_2\f$ are
|
|
|
|
tangential distortion coefficients. \f$s_1\f$, \f$s_2\f$, \f$s_3\f$, and \f$s_4\f$, are the thin prism distortion
|
2015-10-14 18:07:28 +08:00
|
|
|
coefficients. Higher-order coefficients are not considered in OpenCV.
|
|
|
|
|
2018-10-27 02:27:37 +08:00
|
|
|
The next figures show two common types of radial distortion: barrel distortion (typically \f$ k_1 < 0 \f$) and pincushion distortion (typically \f$ k_1 > 0 \f$).
|
2016-10-10 02:35:58 +08:00
|
|
|
|
|
|
|
![](pics/distortion_examples.png)
|
2018-10-27 02:27:37 +08:00
|
|
|
![](pics/distortion_examples2.png)
|
2016-10-10 02:35:58 +08:00
|
|
|
|
2015-10-14 18:07:28 +08:00
|
|
|
In some cases the image sensor may be tilted in order to focus an oblique plane in front of the
|
|
|
|
camera (Scheimpfug condition). This can be useful for particle image velocimetry (PIV) or
|
|
|
|
triangulation with a laser fan. The tilt causes a perspective distortion of \f$x''\f$ and
|
|
|
|
\f$y''\f$. This distortion can be modelled in the following way, see e.g. @cite Louhichi07.
|
|
|
|
|
|
|
|
\f[\begin{array}{l}
|
|
|
|
s\vecthree{x'''}{y'''}{1} =
|
|
|
|
\vecthreethree{R_{33}(\tau_x, \tau_y)}{0}{-R_{13}(\tau_x, \tau_y)}
|
|
|
|
{0}{R_{33}(\tau_x, \tau_y)}{-R_{23}(\tau_x, \tau_y)}
|
|
|
|
{0}{0}{1} R(\tau_x, \tau_y) \vecthree{x''}{y''}{1}\\
|
|
|
|
u = f_x*x''' + c_x \\
|
|
|
|
v = f_y*y''' + c_y
|
|
|
|
\end{array}\f]
|
|
|
|
|
|
|
|
where the matrix \f$R(\tau_x, \tau_y)\f$ is defined by two rotations with angular parameter \f$\tau_x\f$
|
|
|
|
and \f$\tau_y\f$, respectively,
|
2014-11-19 21:13:41 +08:00
|
|
|
|
2015-10-14 18:07:28 +08:00
|
|
|
\f[
|
|
|
|
R(\tau_x, \tau_y) =
|
|
|
|
\vecthreethree{\cos(\tau_y)}{0}{-\sin(\tau_y)}{0}{1}{0}{\sin(\tau_y)}{0}{\cos(\tau_y)}
|
|
|
|
\vecthreethree{1}{0}{0}{0}{\cos(\tau_x)}{\sin(\tau_x)}{0}{-\sin(\tau_x)}{\cos(\tau_x)} =
|
|
|
|
\vecthreethree{\cos(\tau_y)}{\sin(\tau_y)\sin(\tau_x)}{-\sin(\tau_y)\cos(\tau_x)}
|
|
|
|
{0}{\cos(\tau_x)}{\sin(\tau_x)}
|
|
|
|
{\sin(\tau_y)}{-\cos(\tau_y)\sin(\tau_x)}{\cos(\tau_y)\cos(\tau_x)}.
|
|
|
|
\f]
|
|
|
|
|
|
|
|
In the functions below the coefficients are passed or returned as
|
|
|
|
|
|
|
|
\f[(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6 [, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f]
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
vector. That is, if the vector contains four elements, it means that \f$k_3=0\f$ . 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. 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 \f$f_x\f$, \f$f_y\f$, \f$c_x\f$, and
|
|
|
|
\f$c_y\f$ need to be scaled appropriately.
|
|
|
|
|
|
|
|
The functions below use the above model to do the following:
|
|
|
|
|
|
|
|
- Project 3D points to the image plane given intrinsic and extrinsic parameters.
|
|
|
|
- Compute extrinsic parameters given intrinsic parameters, a few 3D points, and their
|
|
|
|
projections.
|
|
|
|
- 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.
|
|
|
|
|
|
|
|
@note
|
Merge pull request #12772 from xoox:calib-release-object
More accurate pinhole camera calibration with imperfect planar target (#12772)
43 commits:
* Add derivatives with respect to object points
Add an output parameter to calculate derivatives of image points with
respect to 3D coordinates of object points. The output jacobian matrix
is a 2Nx3N matrix where N is the number of points.
This commit introduces incompatibility to old function signature.
* Set zero for dpdo matrix before using
dpdo is a sparse matrix with only non-zero value close to major
diagonal. Set it to zero because only elements near major diagonal are
computed.
* Add jacobian columns to projectPoints()
The output jacobian matrix of derivatives with respect to coordinates of
3D object points are added. This might break callers who assume the
columns of jacobian matrix.
* Adapt test code to updated project functions
The test cases for projectPoints() and cvProjectPoints2() are updated to
fit new function signatures.
* Add accuracy test code for dpdo
* Add badarg test for dpdo
* Add new enum item for new calibration method
CALIB_RELEASE_OBJECT is used to whether to release 3D coordinates of
object points. The method was proposed in: K. H. Strobl and G. Hirzinger.
"More Accurate Pinhole Camera Calibration with Imperfect Planar Target".
In Proceedings of the IEEE International Conference on Computer Vision
(ICCV 2011), 1st IEEE Workshop on Challenges and Opportunities in Robot
Perception, Barcelona, Spain, pp. 1068-1075, November 2011.
* Add releasing object method into internal function
It's a simple extension of the standard calibration scheme. We choose to
fix the first and last object point and a user-selected fixed point.
* Add interfaces for extended calibration method
* Refine document for calibrateCamera()
When releasing object points, only the z coordinates of the
objectPoints[0].back is fixed.
* Add link to strobl2011iccv paper
* Improve documentation for calibrateCamera()
* Add implementations of wrapping calibrateCamera()
* Add checking for params of new calibration method
If input parameters are not qualified, then fall back to standard
calibration method.
* Add camera calibration method of releasing object
The current implementation is equal to or better than
https://github.com/xoox/calibrel
* Update doc for CALIB_RELEASE_OBJECT
CALIB_USE_QR or CALIB_USE_LU could be used for faster calibration with
potentially less precise and less stable in some rare cases.
* Add RELEASE_OBJECT calibration to tutorial code
To select the calibration method of releasing object points, a command
line parameter `-d=<number>` should be provided.
* Update tutorial doc for camera_calibration
If the method of releasing object points is merged into OpenCV. It will
be expected to be firstly released in 4.1, I think.
* Reduce epsilon for cornerSubPix()
Epsilon of 0.1 is a bigger one. Preciser corner positions are required
with calibration method of releasing object.
* Refine camera calibration tutorial
The hypothesis coordinates are used to indicate which distance must be
measured between two specified object points.
* Update sample calibration code method selection
Similar to camera_calibration tutorial application, a command line
argument `-dt=<number>` is used to select the calibration method.
* Add guard to flags of cvCalibrateCamera2()
cvCalibrateCamera2() doesn't accept CALIB_RELEASE_OBJECT unless overload
interface is added in the future.
* Simplify fallback when iFixedPoint is out of range
* Refactor projectPoints() to keep compatibilities
* Fix arg string "Bad rvecs header"
* Read calibration flags from test data files
Instead of being hard coded into source file, the calibration flags will
be read from test data files.
opencv_extra/testdata/cv/cameracalibration/calib?.dat must be sync with
the test code.
* Add new C interface of cvCalibrateCamera4()
With this new added C interface, the extended calibration method with
CALIB_RELEASE_OBJECT can be called by C API.
* Add regression test of extended calibration method
It has been tested with new added test data in xoox:calib-release-object
branch of opencv_extra.
* Fix assertion in test_cameracalibration.cpp
The total number of refined 3D object coordinates is checked.
* Add checker for iFixedPoint in cvCalibrateCamera4
If iFixedPoint is out of rational range, fall back to standard method.
* Fix documentation for overloaded calibrateCamera()
* Remove calibration flag of CALIB_RELEASE_OBJECT
The method selection is based on the range of the index of fixed point.
For minus values, standard calibration method will be chosen. Values in
a rational range will make the object-releasing calibration method
selected.
* Use new interfaces instead of function overload
Existing interfaces are preserved and new interfaces are added. Since
most part of the code base are shared, calibrateCamera() is now a
wrapper function of calibrateCameraRO().
* Fix exported name of calibrateCameraRO()
* Update documentation for calibrateCameraRO()
The circumstances where this method is mostly helpful are described.
* Add note on the rigidity of the calibration target
* Update documentation for calibrateCameraRO()
It is clarified that iFixedPoint is used as a switch to select
calibration method. If input data are not qualified, exceptions will be
thrown instead of fallback scheme.
* Clarify iFixedPoint as switch and remove fallback
iFixedPoint is now used as a switch for calibration method selection. No
fallback scheme is utilized anymore. If the input data are not
qualified, exceptions will be thrown.
* Add badarg test for object-releasing method
* Fix document format of sample list
List items of same level should be indented the same way. Otherwise they
will be formatted as nested lists by Doxygen.
* Add brief intro for objectPoints and imagePoints
* Sync tutorial to sample calibration code
* Update tutorial compatibility version to 4.0
2018-10-26 00:38:55 +08:00
|
|
|
- A calibration sample for 3 cameras in horizontal position can be found at
|
2014-11-21 16:28:14 +08:00
|
|
|
opencv_source_code/samples/cpp/3calibration.cpp
|
2014-11-19 21:13:41 +08:00
|
|
|
- A calibration sample based on a sequence of images can be found at
|
2014-11-21 16:28:14 +08:00
|
|
|
opencv_source_code/samples/cpp/calibration.cpp
|
2014-11-19 21:13:41 +08:00
|
|
|
- A calibration sample in order to do 3D reconstruction can be found at
|
2014-11-21 16:28:14 +08:00
|
|
|
opencv_source_code/samples/cpp/build3dmodel.cpp
|
2014-11-19 21:13:41 +08:00
|
|
|
- A calibration sample of an artificially generated camera and chessboard patterns can be
|
2014-11-21 16:28:14 +08:00
|
|
|
found at opencv_source_code/samples/cpp/calibration_artificial.cpp
|
2014-11-19 21:13:41 +08:00
|
|
|
- A calibration example on stereo calibration can be found at
|
2014-11-21 16:28:14 +08:00
|
|
|
opencv_source_code/samples/cpp/stereo_calib.cpp
|
2014-11-19 21:13:41 +08:00
|
|
|
- A calibration example on stereo matching can be found at
|
2014-11-21 16:28:14 +08:00
|
|
|
opencv_source_code/samples/cpp/stereo_match.cpp
|
2014-11-19 21:13:41 +08:00
|
|
|
- (Python) A camera calibration sample can be found at
|
2015-12-16 21:36:03 +08:00
|
|
|
opencv_source_code/samples/python/calibrate.py
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
@{
|
|
|
|
@defgroup calib3d_fisheye Fisheye camera model
|
|
|
|
|
|
|
|
Definitions: Let P be a point in 3D of coordinates X in the world reference frame (stored in the
|
|
|
|
matrix X) The coordinate vector of P in the camera reference frame is:
|
|
|
|
|
|
|
|
\f[Xc = R X + T\f]
|
|
|
|
|
|
|
|
where R is the rotation matrix corresponding to the rotation vector om: R = rodrigues(om); call x, y
|
|
|
|
and z the 3 coordinates of Xc:
|
|
|
|
|
|
|
|
\f[x = Xc_1 \\ y = Xc_2 \\ z = Xc_3\f]
|
|
|
|
|
2016-08-01 08:25:45 +08:00
|
|
|
The pinhole projection coordinates of P is [a; b] where
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
\f[a = x / z \ and \ b = y / z \\ r^2 = a^2 + b^2 \\ \theta = atan(r)\f]
|
|
|
|
|
|
|
|
Fisheye distortion:
|
|
|
|
|
|
|
|
\f[\theta_d = \theta (1 + k_1 \theta^2 + k_2 \theta^4 + k_3 \theta^6 + k_4 \theta^8)\f]
|
|
|
|
|
|
|
|
The distorted point coordinates are [x'; y'] where
|
|
|
|
|
2016-02-18 00:27:11 +08:00
|
|
|
\f[x' = (\theta_d / r) a \\ y' = (\theta_d / r) b \f]
|
2014-11-19 21:13:41 +08:00
|
|
|
|
2015-05-23 21:26:18 +08:00
|
|
|
Finally, conversion into pixel coordinates: The final pixel coordinates vector [u; v] where:
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
\f[u = f_x (x' + \alpha y') + c_x \\
|
2016-01-12 23:33:34 +08:00
|
|
|
v = f_y y' + c_y\f]
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
@defgroup calib3d_c C API
|
|
|
|
|
|
|
|
@}
|
|
|
|
*/
|
|
|
|
|
2013-04-11 23:27:54 +08:00
|
|
|
namespace cv
|
|
|
|
{
|
2010-11-30 07:56:33 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
//! @addtogroup calib3d
|
|
|
|
//! @{
|
|
|
|
|
2013-04-11 23:27:54 +08:00
|
|
|
//! type of the robust estimation algorithm
|
2018-01-19 20:23:09 +08:00
|
|
|
enum { LMEDS = 4, //!< least-median of squares algorithm
|
2014-11-18 04:02:18 +08:00
|
|
|
RANSAC = 8, //!< RANSAC algorithm
|
|
|
|
RHO = 16 //!< RHO algorithm
|
2013-04-11 23:27:54 +08:00
|
|
|
};
|
|
|
|
|
2014-08-11 22:28:09 +08:00
|
|
|
enum { SOLVEPNP_ITERATIVE = 0,
|
2015-12-11 06:01:00 +08:00
|
|
|
SOLVEPNP_EPNP = 1, //!< EPnP: Efficient Perspective-n-Point Camera Pose Estimation @cite lepetit2009epnp
|
|
|
|
SOLVEPNP_P3P = 2, //!< Complete Solution Classification for the Perspective-Three-Point Problem @cite gao2003complete
|
|
|
|
SOLVEPNP_DLS = 3, //!< A Direct Least-Squares (DLS) Method for PnP @cite hesch2011direct
|
2017-04-07 14:48:34 +08:00
|
|
|
SOLVEPNP_UPNP = 4, //!< Exhaustive Linearization for Robust Camera Pose and Focal Length Estimation @cite penate2013exhaustive
|
2017-07-20 05:32:32 +08:00
|
|
|
SOLVEPNP_AP3P = 5, //!< An Efficient Algebraic Solution to the Perspective-Three-Point Problem @cite Ke17
|
|
|
|
SOLVEPNP_MAX_COUNT //!< Used for count
|
2014-07-15 15:58:49 +08:00
|
|
|
};
|
2013-04-11 23:27:54 +08:00
|
|
|
|
|
|
|
enum { CALIB_CB_ADAPTIVE_THRESH = 1,
|
|
|
|
CALIB_CB_NORMALIZE_IMAGE = 2,
|
|
|
|
CALIB_CB_FILTER_QUADS = 4,
|
2018-09-25 22:06:46 +08:00
|
|
|
CALIB_CB_FAST_CHECK = 8,
|
|
|
|
CALIB_CB_EXHAUSTIVE = 16,
|
|
|
|
CALIB_CB_ACCURACY = 32
|
2013-04-11 23:27:54 +08:00
|
|
|
};
|
|
|
|
|
|
|
|
enum { CALIB_CB_SYMMETRIC_GRID = 1,
|
|
|
|
CALIB_CB_ASYMMETRIC_GRID = 2,
|
|
|
|
CALIB_CB_CLUSTERING = 4
|
|
|
|
};
|
|
|
|
|
|
|
|
enum { CALIB_USE_INTRINSIC_GUESS = 0x00001,
|
|
|
|
CALIB_FIX_ASPECT_RATIO = 0x00002,
|
|
|
|
CALIB_FIX_PRINCIPAL_POINT = 0x00004,
|
|
|
|
CALIB_ZERO_TANGENT_DIST = 0x00008,
|
|
|
|
CALIB_FIX_FOCAL_LENGTH = 0x00010,
|
|
|
|
CALIB_FIX_K1 = 0x00020,
|
|
|
|
CALIB_FIX_K2 = 0x00040,
|
|
|
|
CALIB_FIX_K3 = 0x00080,
|
|
|
|
CALIB_FIX_K4 = 0x00800,
|
|
|
|
CALIB_FIX_K5 = 0x01000,
|
|
|
|
CALIB_FIX_K6 = 0x02000,
|
|
|
|
CALIB_RATIONAL_MODEL = 0x04000,
|
|
|
|
CALIB_THIN_PRISM_MODEL = 0x08000,
|
|
|
|
CALIB_FIX_S1_S2_S3_S4 = 0x10000,
|
2015-10-14 18:07:28 +08:00
|
|
|
CALIB_TILTED_MODEL = 0x40000,
|
|
|
|
CALIB_FIX_TAUX_TAUY = 0x80000,
|
2016-08-23 21:35:03 +08:00
|
|
|
CALIB_USE_QR = 0x100000, //!< use QR instead of SVD decomposition for solving. Faster but potentially less precise
|
2017-06-07 21:42:24 +08:00
|
|
|
CALIB_FIX_TANGENT_DIST = 0x200000,
|
2013-04-11 23:27:54 +08:00
|
|
|
// only for stereo
|
|
|
|
CALIB_FIX_INTRINSIC = 0x00100,
|
|
|
|
CALIB_SAME_FOCAL_LENGTH = 0x00200,
|
|
|
|
// for stereo rectification
|
2015-12-11 06:26:37 +08:00
|
|
|
CALIB_ZERO_DISPARITY = 0x00400,
|
|
|
|
CALIB_USE_LU = (1 << 17), //!< use LU instead of SVD decomposition for solving. much faster but potentially less precise
|
2018-01-27 03:05:13 +08:00
|
|
|
CALIB_USE_EXTRINSIC_GUESS = (1 << 22), //!< for stereoCalibrate
|
2013-04-11 23:27:54 +08:00
|
|
|
};
|
2012-05-28 15:36:14 +08:00
|
|
|
|
2013-04-11 23:27:54 +08:00
|
|
|
//! the algorithm for finding fundamental matrix
|
|
|
|
enum { FM_7POINT = 1, //!< 7-point algorithm
|
|
|
|
FM_8POINT = 2, //!< 8-point algorithm
|
2018-01-19 20:23:09 +08:00
|
|
|
FM_LMEDS = 4, //!< least-median algorithm. 7-point algorithm is used.
|
|
|
|
FM_RANSAC = 8 //!< RANSAC algorithm. It needs at least 15 points. 7-point algorithm is used.
|
2013-04-11 23:27:54 +08:00
|
|
|
};
|
2011-12-26 20:59:07 +08:00
|
|
|
|
2012-05-28 15:36:14 +08:00
|
|
|
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Converts a rotation matrix to a rotation vector or vice versa.
|
|
|
|
|
|
|
|
@param src Input rotation vector (3x1 or 1x3) or rotation matrix (3x3).
|
|
|
|
@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.
|
|
|
|
|
|
|
|
\f[\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}\f]
|
|
|
|
|
|
|
|
Inverse transformation can be also done easily, since
|
|
|
|
|
|
|
|
\f[\sin ( \theta ) \vecthreethree{0}{-r_z}{r_y}{r_z}{0}{-r_x}{-r_y}{r_x}{0} = \frac{R - R^T}{2}\f]
|
|
|
|
|
|
|
|
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 used in the global 3D geometry
|
|
|
|
optimization procedures like calibrateCamera, stereoCalibrate, or solvePnP .
|
|
|
|
*/
|
2013-04-11 23:27:54 +08:00
|
|
|
CV_EXPORTS_W void Rodrigues( InputArray src, OutputArray dst, OutputArray jacobian = noArray() );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2018-08-03 02:22:58 +08:00
|
|
|
/** @example samples/cpp/tutorial_code/features2D/Homography/pose_from_homography.cpp
|
|
|
|
An example program about pose estimation from coplanar points
|
2017-12-18 18:44:11 +08:00
|
|
|
|
2018-08-03 02:22:58 +08:00
|
|
|
Check @ref tutorial_homography "the corresponding tutorial" for more details
|
|
|
|
*/
|
2017-12-18 18:44:11 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Finds a perspective transformation between two planes.
|
|
|
|
|
2014-11-21 16:28:14 +08:00
|
|
|
@param srcPoints Coordinates of the points in the original plane, a matrix of the type CV_32FC2
|
2014-11-19 21:13:41 +08:00
|
|
|
or vector\<Point2f\> .
|
2014-11-21 16:28:14 +08:00
|
|
|
@param dstPoints Coordinates of the points in the target plane, a matrix of the type CV_32FC2 or
|
2014-11-19 21:13:41 +08:00
|
|
|
a vector\<Point2f\> .
|
2018-01-18 19:40:59 +08:00
|
|
|
@param method Method used to compute a homography matrix. The following methods are possible:
|
|
|
|
- **0** - a regular method using all the points, i.e., the least squares method
|
2014-11-19 21:13:41 +08:00
|
|
|
- **RANSAC** - RANSAC-based robust method
|
|
|
|
- **LMEDS** - Least-Median robust method
|
2018-01-18 19:40:59 +08:00
|
|
|
- **RHO** - PROSAC-based robust method
|
2014-11-19 21:13:41 +08:00
|
|
|
@param ransacReprojThreshold Maximum allowed reprojection error to treat a point pair as an inlier
|
2015-02-04 11:55:40 +08:00
|
|
|
(used in the RANSAC and RHO methods only). That is, if
|
2018-01-18 19:40:59 +08:00
|
|
|
\f[\| \texttt{dstPoints} _i - \texttt{convertPointsHomogeneous} ( \texttt{H} * \texttt{srcPoints} _i) \|_2 > \texttt{ransacReprojThreshold}\f]
|
|
|
|
then the point \f$i\f$ is considered as an outlier. If srcPoints and dstPoints are measured in pixels,
|
2014-11-19 21:13:41 +08:00
|
|
|
it usually makes sense to set this parameter somewhere in the range of 1 to 10.
|
|
|
|
@param mask Optional output mask set by a robust method ( RANSAC or LMEDS ). Note that the input
|
|
|
|
mask values are ignored.
|
2018-01-18 19:40:59 +08:00
|
|
|
@param maxIters The maximum number of RANSAC iterations.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param confidence Confidence level, between 0 and 1.
|
|
|
|
|
2016-08-24 01:57:20 +08:00
|
|
|
The function finds and returns the perspective transformation \f$H\f$ between the source and the
|
2014-11-19 21:13:41 +08:00
|
|
|
destination planes:
|
|
|
|
|
|
|
|
\f[s_i \vecthree{x'_i}{y'_i}{1} \sim H \vecthree{x_i}{y_i}{1}\f]
|
|
|
|
|
|
|
|
so that the back-projection error
|
|
|
|
|
|
|
|
\f[\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\f]
|
|
|
|
|
|
|
|
is minimized. If the parameter method is set to the default value 0, the function 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 ( \f$srcPoints_i\f$, \f$dstPoints_i\f$ ) fit the rigid perspective
|
|
|
|
transformation (that is, there are some outliers), this initial estimate will be poor. In this case,
|
2015-02-04 11:55:40 +08:00
|
|
|
you can use one of the three robust methods. The methods RANSAC, LMeDS and RHO try many different
|
2018-01-18 19:40:59 +08:00
|
|
|
random subsets of the corresponding point pairs (of four pairs each, collinear pairs are discarded), estimate the homography matrix
|
|
|
|
using this subset and a simple least-squares algorithm, and then compute the quality/goodness of the
|
|
|
|
computed homography (which is the number of inliers for RANSAC or the least median re-projection error for
|
|
|
|
LMeDS). The best subset is then used to produce the initial estimate of the homography matrix and
|
2014-11-19 21:13:41 +08:00
|
|
|
the mask of inliers/outliers.
|
|
|
|
|
|
|
|
Regardless of the method, robust or not, the computed homography 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.
|
|
|
|
|
2015-02-04 11:55:40 +08:00
|
|
|
The methods RANSAC and RHO can handle practically any ratio of outliers but need a threshold to
|
2014-11-19 21:13:41 +08:00
|
|
|
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. Homography matrix is
|
2018-01-18 19:40:59 +08:00
|
|
|
determined up to a scale. Thus, it is normalized so that \f$h_{33}=1\f$. Note that whenever an \f$H\f$ matrix
|
2014-11-19 21:13:41 +08:00
|
|
|
cannot be estimated, an empty one will be returned.
|
|
|
|
|
|
|
|
@sa
|
Merge pull request #6933 from hrnr:gsoc_all
[GSOC] New camera model for stitching pipeline
* implement estimateAffine2D
estimates affine transformation using robust RANSAC method.
* uses RANSAC framework in calib3d
* includes accuracy test
* uses SVD decomposition for solving 3 point equation
* implement estimateAffinePartial2D
estimates limited affine transformation
* includes accuracy test
* stitching: add affine matcher
initial version of matcher that estimates affine transformation
* stitching: added affine transform estimator
initial version of estimator that simply chain transformations in homogeneous coordinates
* calib3d: rename estimateAffine3D test
test Calib3d_EstimateAffineTransform rename to Calib3d_EstimateAffine3D. This is more descriptive and prevents confusion with estimateAffine2D tests.
* added perf test for estimateAffine functions
tests both estimateAffine2D and estimateAffinePartial2D
* calib3d: compare error in square in estimateAffine2D
* incorporates fix from #6768
* rerun affine estimation on inliers
* stitching: new API for parallel feature finding
due to ABI breakage new functionality is added to `FeaturesFinder2`, `SurfFeaturesFinder2` and `OrbFeaturesFinder2`
* stitching: add tests for parallel feature find API
* perf test (about linear speed up)
* accuracy test compares results with serial version
* stitching: use dynamic_cast to overcome ABI issues
adding parallel API to FeaturesFinder breaks ABI. This commit uses dynamic_cast and hardcodes thread-safe finders to avoid breaking ABI.
This should be replaced by proper method similar to FeaturesMatcher on next ABI break.
* use estimateAffinePartial2D in AffineBestOf2NearestMatcher
* add constructor to AffineBestOf2NearestMatcher
* allows to choose between full affine transform and partial affine transform. Other params are the as for BestOf2NearestMatcher
* added protected field
* samples: stitching_detailed support affine estimator and matcher
* added new flags to choose matcher and estimator
* stitching: rework affine matcher
represent transformation in homogeneous coordinates
affine matcher: remove duplicite code
rework flow to get rid of duplicite code
affine matcher: do not center points to (0, 0)
it is not needed for affine model. it should not affect estimation in any way.
affine matcher: remove unneeded cv namespacing
* stitching: add stub bundle adjuster
* adds stub bundle adjuster that does nothing
* can be used in place of standard bundle adjusters to omit bundle adjusting step
* samples: stitching detailed, support no budle adjust
* uses new NoBundleAdjuster
* added affine warper
* uses R to get whole affine transformation and propagates rotation and translation to plane warper
* add affine warper factory class
* affine warper: compensate transformation
* samples: stitching_detailed add support for affine warper
* add Stitcher::create method
this method follows similar constructor methods and returns smart pointer. This allows constructing Stitcher according to OpenCV guidelines.
* supports multiple stitcher configurations (PANORAMA and SCANS) for convenient setup
* returns cv::Ptr
* stitcher: dynamicaly determine correct estimator
we need to use affine estimator for affine matcher
* preserves ABI (but add hints for ABI 4)
* uses dynamic_cast hack to inject correct estimator
* sample stitching: add support for multiple modes
shows how to use different configurations of stitcher easily (panorama stitching and scans affine model)
* stitcher: find features in parallel
use new FeatureFinder API to find features in parallel. Parallelized using TBB.
* stitching: disable parallel feature finding for OCL
it does not bring much speedup to run features finder in parallel when OpenCL is enabled, because finder needs to wait for OCL device.
Also, currently ORB is not thread-safe when OCL is enabled.
* stitching: move matcher tests
move matchers tests perf_stich.cpp -> perf_matchers.cpp
* stitching: add affine stiching integration test
test basic affine stitching (SCANS mode of stitcher) with images that have only translation between them
* enable surf for stitching tests
stitching.b12 test was failing with surf
investigated the issue, surf is producing good result. Transformation is only slightly different from ORB, so that resulting pano does not exactly match ORB's result. That caused sanity check to fail.
* added size checks similar to other tests
* sanity check will be applied only for ORB
* stitching: fix wrong estimator choice
if case was exactly wrong, estimators were chosen wrong
added logging for estimated transformation
* enable surf for matchers stitching tests
* enable SURF
* rework sanity checking. Check estimated transform instead of matches. Est. transform should be more stable and comparable between SURF and ORB.
* remove regression checking for VectorFeatures tests. It has a lot if data andtest is the same as previous except it test different vector size for performance, so sanity checking does not add any value here. Added basic sanity asserts instead.
* stitching tests: allow relative error for transform
* allows .01 relative error for estimated homography sanity check in stitching matchers tests
* fix VS warning
stitching tests: increase relative error
increase relative error to make it pass on all platforms (results are still good).
stitching test: allow bigger relative error
transformation can differ in small values (with small absolute difference, but large relative difference). transformation output still looks usable for all platforms. This difference affects only mac and windows, linux passes fine with small difference.
* stitching: add tests for affine matcher
uses s1, s2 images. added also new sanity data.
* stitching tests: use different data for matchers tests
this data should yeild more stable transformation (it has much more matches, especially for surf). Sanity data regenerated.
* stitching test: rework tests for matchers
* separated rotation and translations as they are different by scale.
* use appropriate absolute error for them separately. (relative error does not work for values near zero.)
* stitching: fix affine warper compensation
calculation of rotation and translation extracted for plane warper was wrong
* stitching test: enable surf for opencl integration tests
* enable SURF with correct guard (HAVE_OPENCV_XFEATURES2D)
* add OPENCL guard and correct namespace as usual for opencl tests
* stitching: add ocl accuracy test for affine warper
test consistent results with ocl on and off
* stitching: add affine warper ocl perf test
add affine warper to existing warper perf tests. Added new sanity data.
* stitching: do not overwrite inliers in affine matcher
* estimation is run second time on inliers only, inliers produces in second run will not be therefore correct for all matches
* calib3d: add Levenberg–Marquardt refining to estimateAffine2D* functions
this adds affine Levenberg–Marquardt refining to estimateAffine2D functions similar to what is done in findHomography.
implements Levenberg–Marquardt refinig for both full affine and partial affine transformations.
* stitching: remove reestimation step in affine matcher
reestimation step is not needed. estimateAffine2D* functions are running their own reestimation on inliers using the Levenberg-Marquardt algorithm, which is better than simply rerunning RANSAC on inliers.
* implement partial affine bundle adjuster
bundle adjuster that expect affine transform with 4DOF. Refines parameters for all cameras together.
stitching: fix bug in BundleAdjusterAffinePartial
* use the invers properly
* use static buffer for invers to speed it up
* samples: add affine bundle adjuster option to stitching_detailed
* add support for using affine bundle adjuster with 4DOF
* improve logging of initial intristics
* sttiching: add affine bundle adjuster test
* fix build warnings
* stitching: increase limit on sanity check
prevents spurious test failures on mac. values are still pretty fine.
* stitching: set affine bundle adjuster for SCANS mode
* fix bug with AffineBestOf2NearestMatcher (we want to select affine partial mode)
* select right bundle adjuster
* stitching: increase error bound for matcher tests
* this prevents failure on mac. tranformation is still ok.
* stitching: implement affine bundle adjuster
* implements affine bundle adjuster that is using full affine transform
* existing test case modified to test both affinePartial an full affine bundle adjuster
* add stitching tutorial
* show basic usage of stitching api (Stitcher class)
* stitching: add more integration test for affine stitching
* added new datasets to existing testcase
* removed unused include
* calib3d: move `haveCollinearPoints` to common header
* added comment to make that this also checks too close points
* calib3d: redone checkSubset for estimateAffine* callback
* use common function to check collinearity
* this also ensures that point will not be too close to each other
* calib3d: change estimateAffine* functions API
* more similar to `findHomography`, `findFundamentalMat`, `findEssentialMat` and similar
* follows standard recommended semantic INPUTS, OUTPUTS, FLAGS
* allows to disable refining
* supported LMEDS robust method (tests yet to come) along with RANSAC
* extended docs with some tips
* calib3d: rewrite estimateAffine2D test
* rewrite in googletest style
* parametrize to test both robust methods (RANSAC and LMEDS)
* get rid of boilerplate
* calib3d: rework estimateAffinePartial2D test
* rework in googletest style
* add testing for LMEDS
* calib3d: rework estimateAffine*2D perf test
* test for LMEDS speed
* test with/without Levenberg-Marquart
* remove sanity checking (this is covered by accuracy tests)
* calib3d: improve estimateAffine*2D tests
* test transformations in loop
* improves test by testing more potential transformations
* calib3d: rewrite kernels for estimateAffine*2D functions
* use analytical solution instead of SVD
* this version is faster especially for smaller amount of points
* calib3d: tune up perf of estimateAffine*2D functions
* avoid copying inliers
* avoid converting input points if not necessary
* check only `from` point for collinearity, as `to` does not affect stability of transform
* tutorials: add commands examples to stitching tutorials
* add some examples how to run stitcher sample code
* mention stitching_detailed.cpp
* calib3d: change computeError for estimateAffine*2D
* do error computing in floats instead of doubles
this have required precision + we were storing the result in float anyway. This make code faster and allows auto-vectorization by smart compilers.
* documentation: mention estimateAffine*2D function
* refer to new functions on appropriate places
* prefer estimateAffine*2D over estimateRigidTransform
* stitching: add camera models documentations
* mention camera models in module documentation to give user a better overview and reduce confusion
2016-10-23 00:10:42 +08:00
|
|
|
getAffineTransform, estimateAffine2D, estimateAffinePartial2D, getPerspectiveTransform, warpPerspective,
|
|
|
|
perspectiveTransform
|
2014-11-19 21:13:41 +08:00
|
|
|
*/
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W Mat findHomography( InputArray srcPoints, InputArray dstPoints,
|
2013-04-11 23:27:54 +08:00
|
|
|
int method = 0, double ransacReprojThreshold = 3,
|
2014-08-17 07:13:39 +08:00
|
|
|
OutputArray mask=noArray(), const int maxIters = 2000,
|
|
|
|
const double confidence = 0.995);
|
2011-04-23 20:49:14 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @overload */
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS Mat findHomography( InputArray srcPoints, InputArray dstPoints,
|
2013-04-11 23:27:54 +08:00
|
|
|
OutputArray mask, int method = 0, double ransacReprojThreshold = 3 );
|
2012-05-28 15:36:14 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Computes an RQ decomposition of 3x3 matrices.
|
|
|
|
|
|
|
|
@param src 3x3 input matrix.
|
|
|
|
@param mtxR Output 3x3 upper-triangular matrix.
|
|
|
|
@param mtxQ 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.
|
|
|
|
|
|
|
|
The function computes a RQ decomposition using the given rotations. This function is used in
|
|
|
|
decomposeProjectionMatrix to decompose the left 3x3 submatrix of a projection matrix into a camera
|
|
|
|
and a rotation matrix.
|
|
|
|
|
|
|
|
It optionally returns three rotation matrices, one for each axis, and the three Euler angles in
|
|
|
|
degrees (as the return value) that could be used in OpenGL. Note, there is always more than one
|
2016-10-06 20:09:26 +08:00
|
|
|
sequence of rotations about the three principal axes that results in the same orientation of an
|
2017-11-09 00:55:48 +08:00
|
|
|
object, e.g. see @cite Slabaugh . Returned tree rotation matrices and corresponding three Euler angles
|
2014-11-19 21:13:41 +08:00
|
|
|
are only one of the possible solutions.
|
|
|
|
*/
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W Vec3d RQDecomp3x3( InputArray src, OutputArray mtxR, OutputArray mtxQ,
|
2013-04-11 23:27:54 +08:00
|
|
|
OutputArray Qx = noArray(),
|
|
|
|
OutputArray Qy = noArray(),
|
|
|
|
OutputArray Qz = noArray());
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Decomposes a projection matrix into a rotation matrix and a camera matrix.
|
|
|
|
|
|
|
|
@param projMatrix 3x4 input projection matrix P.
|
|
|
|
@param cameraMatrix Output 3x3 camera matrix K.
|
|
|
|
@param rotMatrix Output 3x3 external rotation matrix R.
|
|
|
|
@param transVect Output 4x1 translation vector T.
|
|
|
|
@param rotMatrixX Optional 3x3 rotation matrix around x-axis.
|
|
|
|
@param rotMatrixY Optional 3x3 rotation matrix around y-axis.
|
|
|
|
@param rotMatrixZ Optional 3x3 rotation matrix around z-axis.
|
|
|
|
@param eulerAngles Optional three-element vector containing three Euler angles of rotation in
|
|
|
|
degrees.
|
|
|
|
|
|
|
|
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. Note, there is always more than one sequence of rotations about the three
|
2017-11-09 00:55:48 +08:00
|
|
|
principal axes that results in the same orientation of an object, e.g. see @cite Slabaugh . Returned
|
|
|
|
tree rotation matrices and corresponding three Euler angles are only one of the possible solutions.
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
The function is based on RQDecomp3x3 .
|
|
|
|
*/
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W void decomposeProjectionMatrix( InputArray projMatrix, OutputArray cameraMatrix,
|
2011-04-17 21:14:45 +08:00
|
|
|
OutputArray rotMatrix, OutputArray transVect,
|
2013-04-11 23:27:54 +08:00
|
|
|
OutputArray rotMatrixX = noArray(),
|
|
|
|
OutputArray rotMatrixY = noArray(),
|
|
|
|
OutputArray rotMatrixZ = noArray(),
|
|
|
|
OutputArray eulerAngles =noArray() );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Computes partial derivatives of the matrix product for each multiplied matrix.
|
|
|
|
|
|
|
|
@param A First multiplied matrix.
|
|
|
|
@param B Second multiplied matrix.
|
|
|
|
@param dABdA First output derivative matrix d(A\*B)/dA of size
|
|
|
|
\f$\texttt{A.rows*B.cols} \times {A.rows*A.cols}\f$ .
|
|
|
|
@param dABdB Second output derivative matrix d(A\*B)/dB of size
|
|
|
|
\f$\texttt{A.rows*B.cols} \times {B.rows*B.cols}\f$ .
|
|
|
|
|
|
|
|
The function computes partial derivatives of the elements of the matrix product \f$A*B\f$ with regard to
|
|
|
|
the elements of each of the two input matrices. The function is used to compute the Jacobian
|
|
|
|
matrices in stereoCalibrate but can also be used in any other similar optimization function.
|
|
|
|
*/
|
2013-04-11 23:27:54 +08:00
|
|
|
CV_EXPORTS_W void matMulDeriv( InputArray A, InputArray B, OutputArray dABdA, OutputArray dABdB );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Combines two rotation-and-shift transformations.
|
|
|
|
|
|
|
|
@param rvec1 First rotation vector.
|
|
|
|
@param tvec1 First translation vector.
|
|
|
|
@param rvec2 Second rotation vector.
|
|
|
|
@param tvec2 Second translation vector.
|
|
|
|
@param rvec3 Output rotation vector of the superposition.
|
|
|
|
@param tvec3 Output translation vector of the superposition.
|
|
|
|
@param dr3dr1
|
|
|
|
@param dr3dt1
|
|
|
|
@param dr3dr2
|
|
|
|
@param dr3dt2
|
|
|
|
@param dt3dr1
|
|
|
|
@param dt3dt1
|
|
|
|
@param dt3dr2
|
|
|
|
@param dt3dt2 Optional output derivatives of rvec3 or tvec3 with regard to rvec1, rvec2, tvec1 and
|
|
|
|
tvec2, respectively.
|
|
|
|
|
|
|
|
The functions compute:
|
|
|
|
|
|
|
|
\f[\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} ,\f]
|
|
|
|
|
|
|
|
where \f$\mathrm{rodrigues}\f$ denotes a rotation vector to a rotation matrix transformation, and
|
|
|
|
\f$\mathrm{rodrigues}^{-1}\f$ denotes the inverse transformation. See Rodrigues for details.
|
|
|
|
|
|
|
|
Also, the functions can compute the derivatives of the output vectors with regards to the input
|
|
|
|
vectors (see matMulDeriv ). The functions are used inside 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-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W void composeRT( InputArray rvec1, InputArray tvec1,
|
|
|
|
InputArray rvec2, InputArray tvec2,
|
2011-04-17 21:14:45 +08:00
|
|
|
OutputArray rvec3, OutputArray tvec3,
|
2013-04-11 23:27:54 +08:00
|
|
|
OutputArray dr3dr1 = noArray(), OutputArray dr3dt1 = noArray(),
|
|
|
|
OutputArray dr3dr2 = noArray(), OutputArray dr3dt2 = noArray(),
|
|
|
|
OutputArray dt3dr1 = noArray(), OutputArray dt3dt1 = noArray(),
|
|
|
|
OutputArray dt3dr2 = noArray(), OutputArray dt3dt2 = noArray() );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Projects 3D points to an image plane.
|
|
|
|
|
|
|
|
@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.
|
|
|
|
@param rvec Rotation vector. See Rodrigues for details.
|
|
|
|
@param tvec Translation vector.
|
|
|
|
@param cameraMatrix Camera matrix \f$A = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{_1}\f$ .
|
|
|
|
@param distCoeffs Input vector of distortion coefficients
|
2015-10-14 18:07:28 +08:00
|
|
|
\f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6 [, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$ of
|
|
|
|
4, 5, 8, 12 or 14 elements. If the vector is empty, the zero distortion coefficients are assumed.
|
2014-11-19 21:13:41 +08: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 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 extrinsic. The Jacobians are used during the global optimization in
|
|
|
|
calibrateCamera, solvePnP, and stereoCalibrate . The 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-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W void projectPoints( InputArray objectPoints,
|
|
|
|
InputArray rvec, InputArray tvec,
|
|
|
|
InputArray cameraMatrix, InputArray distCoeffs,
|
2011-04-17 21:14:45 +08:00
|
|
|
OutputArray imagePoints,
|
2013-04-11 23:27:54 +08:00
|
|
|
OutputArray jacobian = noArray(),
|
|
|
|
double aspectRatio = 0 );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2018-08-03 02:22:58 +08:00
|
|
|
/** @example samples/cpp/tutorial_code/features2D/Homography/homography_from_camera_displacement.cpp
|
|
|
|
An example program about homography from the camera displacement
|
2017-12-18 18:44:11 +08:00
|
|
|
|
2018-08-03 02:22:58 +08:00
|
|
|
Check @ref tutorial_homography "the corresponding tutorial" for more details
|
|
|
|
*/
|
2017-12-18 18:44:11 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Finds an object pose from 3D-2D point correspondences.
|
|
|
|
|
2016-01-12 17:14:19 +08:00
|
|
|
@param objectPoints Array of object points in the object coordinate space, Nx3 1-channel or
|
2014-11-19 21:13:41 +08:00
|
|
|
1xN/Nx1 3-channel, where N is the number of points. vector\<Point3f\> can be also passed here.
|
2016-01-12 17:14:19 +08:00
|
|
|
@param imagePoints Array of corresponding image points, Nx2 1-channel or 1xN/Nx1 2-channel,
|
2014-11-19 21:13:41 +08:00
|
|
|
where N is the number of points. vector\<Point2f\> can be also passed here.
|
|
|
|
@param cameraMatrix Input camera matrix \f$A = \vecthreethree{fx}{0}{cx}{0}{fy}{cy}{0}{0}{1}\f$ .
|
|
|
|
@param distCoeffs Input vector of distortion coefficients
|
2015-10-14 18:07:28 +08:00
|
|
|
\f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6 [, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$ of
|
|
|
|
4, 5, 8, 12 or 14 elements. If the vector is NULL/empty, the zero distortion coefficients are
|
|
|
|
assumed.
|
2017-05-27 06:31:09 +08:00
|
|
|
@param rvec Output rotation vector (see @ref Rodrigues ) that, together with tvec , brings points from
|
2014-11-19 21:13:41 +08:00
|
|
|
the model coordinate system to the camera coordinate system.
|
|
|
|
@param tvec Output translation vector.
|
2017-05-27 06:31:09 +08:00
|
|
|
@param useExtrinsicGuess Parameter used for #SOLVEPNP_ITERATIVE. If true (1), the function uses
|
2014-11-19 21:13:41 +08:00
|
|
|
the provided rvec and tvec values as initial approximations of the rotation and translation
|
|
|
|
vectors, respectively, and further optimizes them.
|
|
|
|
@param flags Method for solving a PnP problem:
|
2014-11-21 16:28:14 +08:00
|
|
|
- **SOLVEPNP_ITERATIVE** Iterative method is based on Levenberg-Marquardt optimization. In
|
2014-11-19 21:13:41 +08:00
|
|
|
this case the 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
|
|
|
|
projectPoints ) objectPoints .
|
2014-11-21 16:28:14 +08:00
|
|
|
- **SOLVEPNP_P3P** Method is based on the paper of X.S. Gao, X.-R. Hou, J. Tang, H.-F. Chang
|
2017-05-27 06:31:09 +08:00
|
|
|
"Complete Solution Classification for the Perspective-Three-Point Problem" (@cite gao2003complete).
|
|
|
|
In this case the function requires exactly four object and image points.
|
|
|
|
- **SOLVEPNP_AP3P** Method is based on the paper of T. Ke, S. Roumeliotis
|
|
|
|
"An Efficient Algebraic Solution to the Perspective-Three-Point Problem" (@cite Ke17).
|
|
|
|
In this case the function requires exactly four object and image points.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **SOLVEPNP_EPNP** Method has been introduced by F.Moreno-Noguer, V.Lepetit and P.Fua in the
|
2017-05-27 06:31:09 +08:00
|
|
|
paper "EPnP: Efficient Perspective-n-Point Camera Pose Estimation" (@cite lepetit2009epnp).
|
2014-11-21 16:28:14 +08:00
|
|
|
- **SOLVEPNP_DLS** Method is based on the paper of Joel A. Hesch and Stergios I. Roumeliotis.
|
2017-05-27 06:31:09 +08:00
|
|
|
"A Direct Least-Squares (DLS) Method for PnP" (@cite hesch2011direct).
|
2014-11-21 16:28:14 +08:00
|
|
|
- **SOLVEPNP_UPNP** Method is based on the paper of A.Penate-Sanchez, J.Andrade-Cetto,
|
2014-11-19 21:13:41 +08:00
|
|
|
F.Moreno-Noguer. "Exhaustive Linearization for Robust Camera Pose and Focal Length
|
2017-05-27 06:31:09 +08:00
|
|
|
Estimation" (@cite penate2013exhaustive). In this case the function also estimates the parameters \f$f_x\f$ and \f$f_y\f$
|
2014-11-19 21:13:41 +08:00
|
|
|
assuming that both have the same value. Then the cameraMatrix is updated with the estimated
|
|
|
|
focal length.
|
2017-06-28 20:27:30 +08:00
|
|
|
- **SOLVEPNP_AP3P** Method is based on the paper of Tong Ke and Stergios I. Roumeliotis.
|
2017-11-28 22:04:59 +08:00
|
|
|
"An Efficient Algebraic Solution to the Perspective-Three-Point Problem" (@cite Ke17). In this case the
|
2017-06-28 20:27:30 +08:00
|
|
|
function requires exactly four object and image points.
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
The function estimates the object pose given a set of object points, their corresponding image
|
2017-12-18 04:38:22 +08:00
|
|
|
projections, as well as the camera matrix and the distortion coefficients, see the figure below
|
|
|
|
(more precisely, the X-axis of the camera frame is pointing to the right, the Y-axis downward
|
|
|
|
and the Z-axis forward).
|
|
|
|
|
|
|
|
![](pnp.jpg)
|
|
|
|
|
|
|
|
Points expressed in the world frame \f$ \bf{X}_w \f$ are projected into the image plane \f$ \left[ u, v \right] \f$
|
|
|
|
using the perspective projection model \f$ \Pi \f$ and the camera intrinsic parameters matrix \f$ \bf{A} \f$:
|
|
|
|
|
|
|
|
\f[
|
|
|
|
\begin{align*}
|
|
|
|
\begin{bmatrix}
|
|
|
|
u \\
|
|
|
|
v \\
|
|
|
|
1
|
|
|
|
\end{bmatrix} &=
|
|
|
|
\bf{A} \hspace{0.1em} \Pi \hspace{0.2em} ^{c}\bf{M}_w
|
|
|
|
\begin{bmatrix}
|
|
|
|
X_{w} \\
|
|
|
|
Y_{w} \\
|
|
|
|
Z_{w} \\
|
|
|
|
1
|
|
|
|
\end{bmatrix} \\
|
|
|
|
\begin{bmatrix}
|
|
|
|
u \\
|
|
|
|
v \\
|
|
|
|
1
|
|
|
|
\end{bmatrix} &=
|
|
|
|
\begin{bmatrix}
|
|
|
|
f_x & 0 & c_x \\
|
|
|
|
0 & f_y & c_y \\
|
|
|
|
0 & 0 & 1
|
|
|
|
\end{bmatrix}
|
|
|
|
\begin{bmatrix}
|
|
|
|
1 & 0 & 0 & 0 \\
|
|
|
|
0 & 1 & 0 & 0 \\
|
|
|
|
0 & 0 & 1 & 0
|
|
|
|
\end{bmatrix}
|
|
|
|
\begin{bmatrix}
|
|
|
|
r_{11} & r_{12} & r_{13} & t_x \\
|
|
|
|
r_{21} & r_{22} & r_{23} & t_y \\
|
|
|
|
r_{31} & r_{32} & r_{33} & t_z \\
|
|
|
|
0 & 0 & 0 & 1
|
|
|
|
\end{bmatrix}
|
|
|
|
\begin{bmatrix}
|
|
|
|
X_{w} \\
|
|
|
|
Y_{w} \\
|
|
|
|
Z_{w} \\
|
|
|
|
1
|
|
|
|
\end{bmatrix}
|
|
|
|
\end{align*}
|
|
|
|
\f]
|
|
|
|
|
|
|
|
The estimated pose is thus the rotation (`rvec`) and the translation (`tvec`) vectors that allow to transform
|
|
|
|
a 3D point expressed in the world frame into the camera frame:
|
|
|
|
|
|
|
|
\f[
|
|
|
|
\begin{align*}
|
|
|
|
\begin{bmatrix}
|
|
|
|
X_c \\
|
|
|
|
Y_c \\
|
|
|
|
Z_c \\
|
|
|
|
1
|
|
|
|
\end{bmatrix} &=
|
|
|
|
\hspace{0.2em} ^{c}\bf{M}_w
|
|
|
|
\begin{bmatrix}
|
|
|
|
X_{w} \\
|
|
|
|
Y_{w} \\
|
|
|
|
Z_{w} \\
|
|
|
|
1
|
|
|
|
\end{bmatrix} \\
|
|
|
|
\begin{bmatrix}
|
|
|
|
X_c \\
|
|
|
|
Y_c \\
|
|
|
|
Z_c \\
|
|
|
|
1
|
|
|
|
\end{bmatrix} &=
|
|
|
|
\begin{bmatrix}
|
|
|
|
r_{11} & r_{12} & r_{13} & t_x \\
|
|
|
|
r_{21} & r_{22} & r_{23} & t_y \\
|
|
|
|
r_{31} & r_{32} & r_{33} & t_z \\
|
|
|
|
0 & 0 & 0 & 1
|
|
|
|
\end{bmatrix}
|
|
|
|
\begin{bmatrix}
|
|
|
|
X_{w} \\
|
|
|
|
Y_{w} \\
|
|
|
|
Z_{w} \\
|
|
|
|
1
|
|
|
|
\end{bmatrix}
|
|
|
|
\end{align*}
|
|
|
|
\f]
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
@note
|
|
|
|
- An example of how to use solvePnP for planar augmented reality can be found at
|
2015-12-16 21:36:03 +08:00
|
|
|
opencv_source_code/samples/python/plane_ar.py
|
2015-03-06 21:44:07 +08:00
|
|
|
- If you are using Python:
|
|
|
|
- Numpy array slices won't work as input because solvePnP requires contiguous
|
|
|
|
arrays (enforced by the assertion using cv::Mat::checkVector() around line 55 of
|
|
|
|
modules/calib3d/src/solvepnp.cpp version 2.4.9)
|
|
|
|
- The P3P algorithm requires image points to be in an array of shape (N,1,2) due
|
|
|
|
to its calling of cv::undistortPoints (around line 75 of modules/calib3d/src/solvepnp.cpp version 2.4.9)
|
|
|
|
which requires 2-channel information.
|
|
|
|
- Thus, given some data D = np.array(...) where D.shape = (N,M), in order to use a subset of
|
|
|
|
it as, e.g., imagePoints, one must effectively copy it into a new array: imagePoints =
|
|
|
|
np.ascontiguousarray(D[:,:2]).reshape((N,1,2))
|
2016-12-08 00:36:01 +08:00
|
|
|
- The methods **SOLVEPNP_DLS** and **SOLVEPNP_UPNP** cannot be used as the current implementations are
|
2017-10-31 00:13:59 +08:00
|
|
|
unstable and sometimes give completely wrong results. If you pass one of these two
|
2017-05-27 06:31:09 +08:00
|
|
|
flags, **SOLVEPNP_EPNP** method will be used instead.
|
2017-11-28 22:04:59 +08:00
|
|
|
- The minimum number of points is 4 in the general case. In the case of **SOLVEPNP_P3P** and **SOLVEPNP_AP3P**
|
2017-05-27 06:31:09 +08:00
|
|
|
methods, it is required to use exactly 4 points (the first 3 points are used to estimate all the solutions
|
|
|
|
of the P3P problem, the last one is used to retain the best solution that minimizes the reprojection error).
|
2017-11-28 22:04:59 +08:00
|
|
|
- With **SOLVEPNP_ITERATIVE** method and `useExtrinsicGuess=true`, the minimum number of points is 3 (3 points
|
|
|
|
are sufficient to compute a pose but there are up to 4 solutions). The initial solution should be close to the
|
|
|
|
global solution to converge.
|
2014-11-19 21:13:41 +08:00
|
|
|
*/
|
2011-12-26 20:59:07 +08:00
|
|
|
CV_EXPORTS_W bool solvePnP( InputArray objectPoints, InputArray imagePoints,
|
2011-06-06 22:51:27 +08:00
|
|
|
InputArray cameraMatrix, InputArray distCoeffs,
|
2011-04-17 21:14:45 +08:00
|
|
|
OutputArray rvec, OutputArray tvec,
|
2014-08-11 22:28:09 +08:00
|
|
|
bool useExtrinsicGuess = false, int flags = SOLVEPNP_ITERATIVE );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Finds an object pose from 3D-2D point correspondences using the RANSAC scheme.
|
|
|
|
|
2016-01-12 17:14:19 +08:00
|
|
|
@param objectPoints Array of object points in the object coordinate space, Nx3 1-channel or
|
2014-11-19 21:13:41 +08:00
|
|
|
1xN/Nx1 3-channel, where N is the number of points. vector\<Point3f\> can be also passed here.
|
2016-01-12 17:14:19 +08:00
|
|
|
@param imagePoints Array of corresponding image points, Nx2 1-channel or 1xN/Nx1 2-channel,
|
2014-11-19 21:13:41 +08:00
|
|
|
where N is the number of points. vector\<Point2f\> can be also passed here.
|
|
|
|
@param cameraMatrix Input camera matrix \f$A = \vecthreethree{fx}{0}{cx}{0}{fy}{cy}{0}{0}{1}\f$ .
|
|
|
|
@param distCoeffs Input vector of distortion coefficients
|
2015-10-14 18:07:28 +08:00
|
|
|
\f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6 [, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$ of
|
|
|
|
4, 5, 8, 12 or 14 elements. If the vector is NULL/empty, the zero distortion coefficients are
|
|
|
|
assumed.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param rvec Output rotation vector (see Rodrigues ) that, together with tvec , brings points from
|
|
|
|
the model coordinate system to the camera coordinate system.
|
|
|
|
@param tvec Output translation vector.
|
2014-11-21 16:28:14 +08:00
|
|
|
@param useExtrinsicGuess Parameter used for SOLVEPNP_ITERATIVE. If true (1), the function uses
|
2014-11-19 21:13:41 +08:00
|
|
|
the provided rvec and tvec values as initial approximations of the rotation and translation
|
|
|
|
vectors, respectively, and further optimizes them.
|
|
|
|
@param iterationsCount Number of iterations.
|
|
|
|
@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.
|
|
|
|
@param confidence The probability that the algorithm produces a useful result.
|
|
|
|
@param inliers Output vector that contains indices of inliers in objectPoints and imagePoints .
|
|
|
|
@param flags Method for solving a PnP problem (see solvePnP ).
|
|
|
|
|
|
|
|
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 projectPoints ) objectPoints. The use of RANSAC
|
|
|
|
makes the function resistant to outliers.
|
|
|
|
|
|
|
|
@note
|
|
|
|
- An example of how to use solvePNPRansac for object detection can be found at
|
2014-11-21 16:28:14 +08:00
|
|
|
opencv_source_code/samples/cpp/tutorial_code/calib3d/real_time_pose_estimation/
|
2017-07-04 03:55:11 +08:00
|
|
|
- The default method used to estimate the camera pose for the Minimal Sample Sets step
|
|
|
|
is #SOLVEPNP_EPNP. Exceptions are:
|
|
|
|
- if you choose #SOLVEPNP_P3P or #SOLVEPNP_AP3P, these methods will be used.
|
|
|
|
- if the number of input points is equal to 4, #SOLVEPNP_P3P is used.
|
|
|
|
- The method used to estimate the camera pose using all the inliers is defined by the
|
|
|
|
flags parameters unless it is equal to #SOLVEPNP_P3P or #SOLVEPNP_AP3P. In this case,
|
|
|
|
the method #SOLVEPNP_EPNP will be used instead.
|
2014-11-19 21:13:41 +08:00
|
|
|
*/
|
2014-07-09 16:37:37 +08:00
|
|
|
CV_EXPORTS_W bool solvePnPRansac( InputArray objectPoints, InputArray imagePoints,
|
2013-04-11 23:27:54 +08:00
|
|
|
InputArray cameraMatrix, InputArray distCoeffs,
|
|
|
|
OutputArray rvec, OutputArray tvec,
|
|
|
|
bool useExtrinsicGuess = false, int iterationsCount = 100,
|
2014-08-11 16:17:42 +08:00
|
|
|
float reprojectionError = 8.0, double confidence = 0.99,
|
2014-08-11 22:28:09 +08:00
|
|
|
OutputArray inliers = noArray(), int flags = SOLVEPNP_ITERATIVE );
|
2017-06-28 20:27:30 +08:00
|
|
|
/** @brief Finds an object pose from 3 3D-2D point correspondences.
|
|
|
|
|
|
|
|
@param objectPoints Array of object points in the object coordinate space, 3x3 1-channel or
|
|
|
|
1x3/3x1 3-channel. vector\<Point3f\> can be also passed here.
|
|
|
|
@param imagePoints Array of corresponding image points, 3x2 1-channel or 1x3/3x1 2-channel.
|
|
|
|
vector\<Point2f\> can be also passed here.
|
|
|
|
@param cameraMatrix Input camera matrix \f$A = \vecthreethree{fx}{0}{cx}{0}{fy}{cy}{0}{0}{1}\f$ .
|
|
|
|
@param distCoeffs Input vector of distortion coefficients
|
|
|
|
\f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6 [, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$ of
|
|
|
|
4, 5, 8, 12 or 14 elements. If the vector is NULL/empty, the zero distortion coefficients are
|
|
|
|
assumed.
|
|
|
|
@param rvecs Output rotation vectors (see Rodrigues ) that, together with tvecs , brings points from
|
|
|
|
the model coordinate system to the camera coordinate system. A P3P problem has up to 4 solutions.
|
|
|
|
@param tvecs Output translation vectors.
|
|
|
|
@param flags Method for solving a P3P problem:
|
|
|
|
- **SOLVEPNP_P3P** Method is based on the paper of X.S. Gao, X.-R. Hou, J. Tang, H.-F. Chang
|
2017-11-28 22:04:59 +08:00
|
|
|
"Complete Solution Classification for the Perspective-Three-Point Problem" (@cite gao2003complete).
|
2017-06-28 20:27:30 +08:00
|
|
|
- **SOLVEPNP_AP3P** Method is based on the paper of Tong Ke and Stergios I. Roumeliotis.
|
2017-11-28 22:04:59 +08:00
|
|
|
"An Efficient Algebraic Solution to the Perspective-Three-Point Problem" (@cite Ke17).
|
2017-06-28 20:27:30 +08:00
|
|
|
|
|
|
|
The function estimates the object pose given 3 object points, their corresponding image
|
|
|
|
projections, as well as the camera matrix and the distortion coefficients.
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W int solveP3P( InputArray objectPoints, InputArray imagePoints,
|
|
|
|
InputArray cameraMatrix, InputArray distCoeffs,
|
|
|
|
OutputArrayOfArrays rvecs, OutputArrayOfArrays tvecs,
|
|
|
|
int flags );
|
2011-03-05 08:18:49 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Finds an initial camera matrix from 3D-2D point correspondences.
|
|
|
|
|
|
|
|
@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
|
|
|
|
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 imageSize Image size in pixels used to initialize the principal point.
|
|
|
|
@param aspectRatio If it is zero or negative, both \f$f_x\f$ and \f$f_y\f$ are estimated independently.
|
|
|
|
Otherwise, \f$f_x = f_y * \texttt{aspectRatio}\f$ .
|
|
|
|
|
|
|
|
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-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W Mat initCameraMatrix2D( InputArrayOfArrays objectPoints,
|
|
|
|
InputArrayOfArrays imagePoints,
|
2013-04-11 23:27:54 +08:00
|
|
|
Size imageSize, double aspectRatio = 1.0 );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Finds the positions of internal corners of the chessboard.
|
|
|
|
|
|
|
|
@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
|
2018-09-13 20:43:04 +08:00
|
|
|
( patternSize = cv::Size(points_per_row,points_per_colum) = cv::Size(columns,rows) ).
|
2014-11-19 21:13:41 +08:00
|
|
|
@param corners Output array of detected corners.
|
|
|
|
@param flags Various operation flags that can be zero or a combination of the following values:
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_CB_ADAPTIVE_THRESH** Use adaptive thresholding to convert the image to black
|
2014-11-19 21:13:41 +08:00
|
|
|
and white, rather than a fixed threshold level (computed from the average image brightness).
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_CB_NORMALIZE_IMAGE** Normalize the image gamma with equalizeHist before
|
2014-11-19 21:13:41 +08:00
|
|
|
applying fixed or adaptive thresholding.
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_CB_FILTER_QUADS** Use additional criteria (like contour area, perimeter,
|
2014-11-19 21:13:41 +08:00
|
|
|
square-like shape) to filter out false quads extracted at the contour retrieval stage.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **CALIB_CB_FAST_CHECK** Run a fast check on the image that looks for chessboard corners,
|
2014-11-19 21:13:41 +08:00
|
|
|
and shortcut the call if none is found. This can drastically speed up the call in the
|
|
|
|
degenerate condition when no chessboard is observed.
|
|
|
|
|
|
|
|
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 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 cornerSubPix. You also may use the function cornerSubPix with
|
|
|
|
different parameters if returned coordinates are not accurate enough.
|
|
|
|
|
|
|
|
Sample usage of detecting and drawing chessboard corners: :
|
|
|
|
@code
|
|
|
|
Size patternsize(8,6); //interior number of corners
|
|
|
|
Mat gray = ....; //source image
|
|
|
|
vector<Point2f> corners; //this will be filled by the detected corners
|
|
|
|
|
|
|
|
//CALIB_CB_FAST_CHECK saves a lot of time on images
|
|
|
|
//that do not contain any chessboard corners
|
|
|
|
bool patternfound = findChessboardCorners(gray, patternsize, corners,
|
|
|
|
CALIB_CB_ADAPTIVE_THRESH + CALIB_CB_NORMALIZE_IMAGE
|
|
|
|
+ CALIB_CB_FAST_CHECK);
|
|
|
|
|
|
|
|
if(patternfound)
|
|
|
|
cornerSubPix(gray, corners, Size(11, 11), Size(-1, -1),
|
|
|
|
TermCriteria(CV_TERMCRIT_EPS + CV_TERMCRIT_ITER, 30, 0.1));
|
|
|
|
|
|
|
|
drawChessboardCorners(img, patternsize, Mat(corners), patternfound);
|
|
|
|
@endcode
|
|
|
|
@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.
|
|
|
|
*/
|
2013-04-11 23:27:54 +08:00
|
|
|
CV_EXPORTS_W bool findChessboardCorners( InputArray image, Size patternSize, OutputArray corners,
|
|
|
|
int flags = CALIB_CB_ADAPTIVE_THRESH + CALIB_CB_NORMALIZE_IMAGE );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2018-11-02 05:27:06 +08:00
|
|
|
/*
|
|
|
|
Checks whether the image contains chessboard of the specific size or not.
|
|
|
|
If yes, nonzero value is returned.
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W bool checkChessboard(InputArray img, Size size);
|
|
|
|
|
2018-09-13 20:43:04 +08:00
|
|
|
/** @brief Finds the positions of internal corners of the chessboard using a sector based approach.
|
|
|
|
|
|
|
|
@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 = cv::Size(points_per_row,points_per_colum) = cv::Size(columns,rows) ).
|
|
|
|
@param corners Output array of detected corners.
|
2018-09-25 22:06:46 +08:00
|
|
|
@param flags Various operation flags that can be zero or a combination of the following values:
|
|
|
|
- **CALIB_CB_NORMALIZE_IMAGE** Normalize the image gamma with equalizeHist before detection.
|
|
|
|
- **CALIB_CB_EXHAUSTIVE ** Run an exhaustive search to improve detection rate.
|
|
|
|
- **CALIB_CB_ACCURACY ** Up sample input image to improve sub-pixel accuracy due to aliasing effects.
|
|
|
|
This should be used if an accurate camera calibration is required.
|
2018-09-13 20:43:04 +08:00
|
|
|
|
|
|
|
The function is analog to findchessboardCorners but uses a localized radon
|
|
|
|
transformation approximated by box filters being more robust to all sort of
|
|
|
|
noise, faster on larger images and is able to directly return the sub-pixel
|
|
|
|
position of the internal chessboard corners. The Method is based on the paper
|
|
|
|
@cite duda2018 "Accurate Detection and Localization of Checkerboard Corners for
|
|
|
|
Calibration" demonstrating that the returned sub-pixel positions are more
|
|
|
|
accurate than the one returned by cornerSubPix allowing a precise camera
|
|
|
|
calibration for demanding applications.
|
|
|
|
|
|
|
|
@note The function requires a white boarder with roughly the same width as one
|
|
|
|
of the checkerboard fields around the whole board to improve the detection in
|
|
|
|
various environments. In addition, because of the localized radon
|
|
|
|
transformation it is beneficial to use round corners for the field corners
|
|
|
|
which are located on the outside of the board. The following figure illustrates
|
|
|
|
a sample checkerboard optimized for the detection. However, any other checkerboard
|
|
|
|
can be used as well.
|
|
|
|
![Checkerboard](pics/checkerboard_radon.png)
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W bool findChessboardCornersSB(InputArray image,Size patternSize, OutputArray corners,int flags=0);
|
|
|
|
|
2012-05-28 15:36:14 +08:00
|
|
|
//! finds subpixel-accurate positions of the chessboard corners
|
2013-04-11 23:27:54 +08:00
|
|
|
CV_EXPORTS bool find4QuadCornerSubpix( InputArray img, InputOutputArray corners, Size region_size );
|
2011-02-10 04:55:11 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Renders the detected chessboard corners.
|
|
|
|
|
|
|
|
@param image Destination image. It must be an 8-bit color image.
|
|
|
|
@param patternSize Number of inner corners per a chessboard row and column
|
2014-11-21 16:28:14 +08:00
|
|
|
(patternSize = cv::Size(points_per_row,points_per_column)).
|
2014-11-19 21:13:41 +08:00
|
|
|
@param corners Array of detected corners, the output of findChessboardCorners.
|
|
|
|
@param patternWasFound Parameter indicating whether the complete board was found or not. The
|
|
|
|
return value of findChessboardCorners should be passed here.
|
|
|
|
|
|
|
|
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-04-17 21:14:45 +08:00
|
|
|
CV_EXPORTS_W void drawChessboardCorners( InputOutputArray image, Size patternSize,
|
2011-06-06 22:51:27 +08:00
|
|
|
InputArray corners, bool patternWasFound );
|
2010-12-21 17:24:36 +08:00
|
|
|
|
2018-10-25 23:57:18 +08:00
|
|
|
/** @brief Draw axes of the world/object coordinate system from pose estimation. @sa solvePnP
|
|
|
|
|
|
|
|
@param image Input/output image. It must have 1 or 3 channels. The number of channels is not altered.
|
|
|
|
@param cameraMatrix Input 3x3 floating-point matrix of camera intrinsic parameters.
|
|
|
|
\f$A = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}\f$
|
|
|
|
@param distCoeffs Input vector of distortion coefficients
|
|
|
|
\f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6 [, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$ of
|
|
|
|
4, 5, 8, 12 or 14 elements. If the vector is empty, the zero distortion coefficients are assumed.
|
|
|
|
@param rvec Rotation vector (see @ref Rodrigues ) that, together with tvec , brings points from
|
|
|
|
the model coordinate system to the camera coordinate system.
|
|
|
|
@param tvec Translation vector.
|
|
|
|
@param length Length of the painted axes in the same unit than tvec (usually in meters).
|
|
|
|
@param thickness Line thickness of the painted axes.
|
|
|
|
|
|
|
|
This function draws the axes of the world/object coordinate system w.r.t. to the camera frame.
|
|
|
|
OX is drawn in red, OY in green and OZ in blue.
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W void drawFrameAxes(InputOutputArray image, InputArray cameraMatrix, InputArray distCoeffs,
|
|
|
|
InputArray rvec, InputArray tvec, float length, int thickness=3);
|
|
|
|
|
2017-03-01 18:52:25 +08:00
|
|
|
struct CV_EXPORTS_W_SIMPLE CirclesGridFinderParameters
|
|
|
|
{
|
|
|
|
CV_WRAP CirclesGridFinderParameters();
|
|
|
|
CV_PROP_RW cv::Size2f densityNeighborhoodSize;
|
|
|
|
CV_PROP_RW float minDensity;
|
|
|
|
CV_PROP_RW int kmeansAttempts;
|
|
|
|
CV_PROP_RW int minDistanceToAddKeypoint;
|
|
|
|
CV_PROP_RW int keypointScale;
|
|
|
|
CV_PROP_RW float minGraphConfidence;
|
|
|
|
CV_PROP_RW float vertexGain;
|
|
|
|
CV_PROP_RW float vertexPenalty;
|
|
|
|
CV_PROP_RW float existingVertexGain;
|
|
|
|
CV_PROP_RW float edgeGain;
|
|
|
|
CV_PROP_RW float edgePenalty;
|
|
|
|
CV_PROP_RW float convexHullFactor;
|
|
|
|
CV_PROP_RW float minRNGEdgeSwitchDist;
|
|
|
|
|
|
|
|
enum GridType
|
|
|
|
{
|
|
|
|
SYMMETRIC_GRID, ASYMMETRIC_GRID
|
|
|
|
};
|
|
|
|
GridType gridType;
|
2017-09-08 22:35:23 +08:00
|
|
|
|
|
|
|
CV_PROP_RW float squareSize; //!< Distance between two adjacent points. Used by CALIB_CB_CLUSTERING.
|
|
|
|
CV_PROP_RW float maxRectifiedDistance; //!< Max deviation from predicion. Used by CALIB_CB_CLUSTERING.
|
|
|
|
};
|
|
|
|
|
2018-03-22 21:19:47 +08:00
|
|
|
#ifndef DISABLE_OPENCV_3_COMPATIBILITY
|
|
|
|
typedef CirclesGridFinderParameters CirclesGridFinderParameters2;
|
|
|
|
#endif
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Finds centers in the grid of circles.
|
|
|
|
|
|
|
|
@param image grid view of input circles; it must be an 8-bit grayscale or color image.
|
|
|
|
@param patternSize number of circles per row and column
|
2014-11-21 16:28:14 +08:00
|
|
|
( patternSize = Size(points_per_row, points_per_colum) ).
|
2014-11-19 21:13:41 +08:00
|
|
|
@param centers output array of detected centers.
|
|
|
|
@param flags various operation flags that can be one of the following values:
|
2014-11-21 16:28:14 +08:00
|
|
|
- **CALIB_CB_SYMMETRIC_GRID** uses symmetric pattern of circles.
|
|
|
|
- **CALIB_CB_ASYMMETRIC_GRID** uses asymmetric pattern of circles.
|
|
|
|
- **CALIB_CB_CLUSTERING** uses a special algorithm for grid detection. It is more robust to
|
2014-11-19 21:13:41 +08:00
|
|
|
perspective distortions but much more sensitive to background clutter.
|
|
|
|
@param blobDetector feature detector that finds blobs like dark circles on light background.
|
2017-03-01 18:52:25 +08:00
|
|
|
@param parameters struct for finding circles in a grid pattern.
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
The function attempts to determine 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 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.
|
|
|
|
|
|
|
|
Sample usage of detecting and drawing the centers of circles: :
|
|
|
|
@code
|
|
|
|
Size patternsize(7,7); //number of centers
|
|
|
|
Mat gray = ....; //source image
|
|
|
|
vector<Point2f> centers; //this will be filled by the detected centers
|
|
|
|
|
|
|
|
bool patternfound = findCirclesGrid(gray, patternsize, centers);
|
|
|
|
|
|
|
|
drawChessboardCorners(img, patternsize, Mat(centers), patternfound);
|
|
|
|
@endcode
|
|
|
|
@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.
|
|
|
|
*/
|
2017-03-01 18:52:25 +08:00
|
|
|
CV_EXPORTS_W bool findCirclesGrid( InputArray image, Size patternSize,
|
|
|
|
OutputArray centers, int flags,
|
|
|
|
const Ptr<FeatureDetector> &blobDetector,
|
2018-03-22 21:19:47 +08:00
|
|
|
const CirclesGridFinderParameters& parameters);
|
2017-09-08 22:35:23 +08:00
|
|
|
|
2017-03-01 18:52:25 +08:00
|
|
|
/** @overload */
|
2012-03-12 19:40:46 +08:00
|
|
|
CV_EXPORTS_W bool findCirclesGrid( InputArray image, Size patternSize,
|
2013-04-11 23:27:54 +08:00
|
|
|
OutputArray centers, int flags = CALIB_CB_SYMMETRIC_GRID,
|
2014-10-17 18:22:02 +08:00
|
|
|
const Ptr<FeatureDetector> &blobDetector = SimpleBlobDetector::create());
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Finds the camera intrinsic and extrinsic parameters from several views of a calibration pattern.
|
|
|
|
|
2015-04-23 19:30:14 +08:00
|
|
|
@param objectPoints In the new interface it is a vector of vectors of calibration pattern points in
|
|
|
|
the calibration pattern coordinate space (e.g. std::vector<std::vector<cv::Vec3f>>). 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.
|
2014-11-19 21:13:41 +08:00
|
|
|
In the old interface all the vectors of object points from different views are concatenated
|
|
|
|
together.
|
2015-04-23 19:30:14 +08:00
|
|
|
@param imagePoints In the new interface it is a vector of vectors of the projections of calibration
|
|
|
|
pattern points (e.g. std::vector<std::vector<cv::Vec2f>>). imagePoints.size() and
|
|
|
|
objectPoints.size() and imagePoints[i].size() must be equal to objectPoints[i].size() for each i.
|
2014-11-19 21:13:41 +08:00
|
|
|
In the old interface all the vectors of object points from different views are concatenated
|
|
|
|
together.
|
|
|
|
@param imageSize Size of the image used only to initialize the intrinsic camera matrix.
|
|
|
|
@param cameraMatrix Output 3x3 floating-point camera matrix
|
|
|
|
\f$A = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}\f$ . If CV\_CALIB\_USE\_INTRINSIC\_GUESS
|
2017-05-24 20:50:41 +08:00
|
|
|
and/or CALIB_FIX_ASPECT_RATIO are specified, some or all of fx, fy, cx, cy must be
|
2014-11-19 21:13:41 +08:00
|
|
|
initialized before calling the function.
|
|
|
|
@param distCoeffs Output vector of distortion coefficients
|
2015-10-14 18:07:28 +08:00
|
|
|
\f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6 [, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$ of
|
|
|
|
4, 5, 8, 12 or 14 elements.
|
2015-04-23 19:30:14 +08:00
|
|
|
@param rvecs Output vector of rotation vectors (see Rodrigues ) estimated for each pattern view
|
|
|
|
(e.g. std::vector<cv::Mat>>). 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).
|
2014-11-19 21:13:41 +08:00
|
|
|
@param tvecs Output vector of translation vectors estimated for each pattern view.
|
2016-06-07 17:31:11 +08:00
|
|
|
@param stdDeviationsIntrinsics Output vector of standard deviations estimated for intrinsic parameters.
|
|
|
|
Order of deviations values:
|
|
|
|
\f$(f_x, f_y, c_x, c_y, k_1, k_2, p_1, p_2, k_3, k_4, k_5, k_6 , s_1, s_2, s_3,
|
|
|
|
s_4, \tau_x, \tau_y)\f$ If one of parameters is not estimated, it's deviation is equals to zero.
|
|
|
|
@param stdDeviationsExtrinsics Output vector of standard deviations estimated for extrinsic parameters.
|
|
|
|
Order of deviations values: \f$(R_1, T_1, \dotsc , R_M, T_M)\f$ where M is number of pattern views,
|
|
|
|
\f$R_i, T_i\f$ are concatenated 1x3 vectors.
|
2016-11-24 20:56:08 +08:00
|
|
|
@param perViewErrors Output vector of the RMS re-projection error estimated for each pattern view.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param flags Different flags that may be zero or a combination of the following values:
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_USE_INTRINSIC_GUESS** cameraMatrix contains valid initial values of
|
2014-11-19 21:13:41 +08:00
|
|
|
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 solvePnP instead.
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_FIX_PRINCIPAL_POINT** The principal point is not changed during the global
|
2014-11-19 21:13:41 +08:00
|
|
|
optimization. It stays at the center or at a different location specified when
|
2017-05-24 20:50:41 +08:00
|
|
|
CALIB_USE_INTRINSIC_GUESS is set too.
|
|
|
|
- **CALIB_FIX_ASPECT_RATIO** The functions considers only fy as a free parameter. The
|
2014-11-19 21:13:41 +08:00
|
|
|
ratio fx/fy stays the same as in the input cameraMatrix . When
|
2017-05-24 20:50:41 +08:00
|
|
|
CALIB_USE_INTRINSIC_GUESS is not set, the actual input values of fx and fy are
|
2014-11-19 21:13:41 +08:00
|
|
|
ignored, only their ratio is computed and used further.
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_ZERO_TANGENT_DIST** Tangential distortion coefficients \f$(p_1, p_2)\f$ are set
|
2014-11-19 21:13:41 +08:00
|
|
|
to zeros and stay zero.
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_FIX_K1,...,CALIB_FIX_K6** The corresponding radial distortion
|
|
|
|
coefficient is not changed during the optimization. If CALIB_USE_INTRINSIC_GUESS is
|
2014-11-19 21:13:41 +08:00
|
|
|
set, the coefficient from the supplied distCoeffs matrix is used. Otherwise, it is set to 0.
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_RATIONAL_MODEL** Coefficients k4, k5, and k6 are enabled. To provide the
|
2014-11-19 21:13:41 +08:00
|
|
|
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.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **CALIB_THIN_PRISM_MODEL** Coefficients s1, s2, s3 and s4 are enabled. To provide the
|
2014-11-19 21:13:41 +08:00
|
|
|
backward compatibility, this extra flag should be explicitly specified to make the
|
|
|
|
calibration function use the thin prism model and return 12 coefficients. If the flag is not
|
|
|
|
set, the function computes and returns only 5 distortion coefficients.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **CALIB_FIX_S1_S2_S3_S4** The thin prism distortion coefficients are not changed during
|
2017-05-24 20:50:41 +08:00
|
|
|
the optimization. If CALIB_USE_INTRINSIC_GUESS is set, the coefficient from the
|
2014-11-19 21:13:41 +08:00
|
|
|
supplied distCoeffs matrix is used. Otherwise, it is set to 0.
|
2015-10-14 18:07:28 +08:00
|
|
|
- **CALIB_TILTED_MODEL** Coefficients tauX and tauY are enabled. To provide the
|
|
|
|
backward compatibility, this extra flag should be explicitly specified to make the
|
|
|
|
calibration function use the tilted sensor model and return 14 coefficients. If the flag is not
|
|
|
|
set, the function computes and returns only 5 distortion coefficients.
|
|
|
|
- **CALIB_FIX_TAUX_TAUY** The coefficients of the tilted sensor model are not changed during
|
2017-05-24 20:50:41 +08:00
|
|
|
the optimization. If CALIB_USE_INTRINSIC_GUESS is set, the coefficient from the
|
2015-10-14 18:07:28 +08:00
|
|
|
supplied distCoeffs matrix is used. Otherwise, it is set to 0.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param criteria Termination criteria for the iterative optimization algorithm.
|
|
|
|
|
2016-11-24 20:56:08 +08:00
|
|
|
@return the overall RMS re-projection error.
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
The function estimates the intrinsic camera parameters and extrinsic parameters for each of the
|
2014-11-26 19:21:08 +08:00
|
|
|
views. The algorithm is based on @cite Zhang2000 and @cite BouguetMCT . The coordinates of 3D object
|
2014-11-19 21:13:41 +08:00
|
|
|
points and their corresponding 2D projections in each view must be specified. That may be achieved
|
|
|
|
by using an 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 rig (see findChessboardCorners ). Currently, initialization of intrinsic parameters
|
2017-05-24 20:50:41 +08:00
|
|
|
(when CALIB_USE_INTRINSIC_GUESS is not set) is only implemented for planar calibration
|
2014-11-19 21:13:41 +08:00
|
|
|
patterns (where Z-coordinates of the object points must be all zeros). 3D calibration rigs can also
|
|
|
|
be used as long as initial cameraMatrix is provided.
|
|
|
|
|
|
|
|
The algorithm performs the following steps:
|
|
|
|
|
|
|
|
- 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
|
2017-05-24 20:50:41 +08:00
|
|
|
zeros initially unless some of CALIB_FIX_K? are specified.
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
- Estimate the initial camera pose as if the intrinsic parameters have been already known. This is
|
|
|
|
done using 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 projectPoints for details.
|
|
|
|
|
|
|
|
@note
|
|
|
|
If you use a non-square (=non-NxN) grid and 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 \f$f_x\f$ and \f$f_y\f$ (ratios of 10:1 or more)),
|
|
|
|
then you have probably used patternSize=cvSize(rows,cols) instead of using
|
|
|
|
patternSize=cvSize(cols,rows) in findChessboardCorners .
|
|
|
|
|
|
|
|
@sa
|
Merge pull request #12772 from xoox:calib-release-object
More accurate pinhole camera calibration with imperfect planar target (#12772)
43 commits:
* Add derivatives with respect to object points
Add an output parameter to calculate derivatives of image points with
respect to 3D coordinates of object points. The output jacobian matrix
is a 2Nx3N matrix where N is the number of points.
This commit introduces incompatibility to old function signature.
* Set zero for dpdo matrix before using
dpdo is a sparse matrix with only non-zero value close to major
diagonal. Set it to zero because only elements near major diagonal are
computed.
* Add jacobian columns to projectPoints()
The output jacobian matrix of derivatives with respect to coordinates of
3D object points are added. This might break callers who assume the
columns of jacobian matrix.
* Adapt test code to updated project functions
The test cases for projectPoints() and cvProjectPoints2() are updated to
fit new function signatures.
* Add accuracy test code for dpdo
* Add badarg test for dpdo
* Add new enum item for new calibration method
CALIB_RELEASE_OBJECT is used to whether to release 3D coordinates of
object points. The method was proposed in: K. H. Strobl and G. Hirzinger.
"More Accurate Pinhole Camera Calibration with Imperfect Planar Target".
In Proceedings of the IEEE International Conference on Computer Vision
(ICCV 2011), 1st IEEE Workshop on Challenges and Opportunities in Robot
Perception, Barcelona, Spain, pp. 1068-1075, November 2011.
* Add releasing object method into internal function
It's a simple extension of the standard calibration scheme. We choose to
fix the first and last object point and a user-selected fixed point.
* Add interfaces for extended calibration method
* Refine document for calibrateCamera()
When releasing object points, only the z coordinates of the
objectPoints[0].back is fixed.
* Add link to strobl2011iccv paper
* Improve documentation for calibrateCamera()
* Add implementations of wrapping calibrateCamera()
* Add checking for params of new calibration method
If input parameters are not qualified, then fall back to standard
calibration method.
* Add camera calibration method of releasing object
The current implementation is equal to or better than
https://github.com/xoox/calibrel
* Update doc for CALIB_RELEASE_OBJECT
CALIB_USE_QR or CALIB_USE_LU could be used for faster calibration with
potentially less precise and less stable in some rare cases.
* Add RELEASE_OBJECT calibration to tutorial code
To select the calibration method of releasing object points, a command
line parameter `-d=<number>` should be provided.
* Update tutorial doc for camera_calibration
If the method of releasing object points is merged into OpenCV. It will
be expected to be firstly released in 4.1, I think.
* Reduce epsilon for cornerSubPix()
Epsilon of 0.1 is a bigger one. Preciser corner positions are required
with calibration method of releasing object.
* Refine camera calibration tutorial
The hypothesis coordinates are used to indicate which distance must be
measured between two specified object points.
* Update sample calibration code method selection
Similar to camera_calibration tutorial application, a command line
argument `-dt=<number>` is used to select the calibration method.
* Add guard to flags of cvCalibrateCamera2()
cvCalibrateCamera2() doesn't accept CALIB_RELEASE_OBJECT unless overload
interface is added in the future.
* Simplify fallback when iFixedPoint is out of range
* Refactor projectPoints() to keep compatibilities
* Fix arg string "Bad rvecs header"
* Read calibration flags from test data files
Instead of being hard coded into source file, the calibration flags will
be read from test data files.
opencv_extra/testdata/cv/cameracalibration/calib?.dat must be sync with
the test code.
* Add new C interface of cvCalibrateCamera4()
With this new added C interface, the extended calibration method with
CALIB_RELEASE_OBJECT can be called by C API.
* Add regression test of extended calibration method
It has been tested with new added test data in xoox:calib-release-object
branch of opencv_extra.
* Fix assertion in test_cameracalibration.cpp
The total number of refined 3D object coordinates is checked.
* Add checker for iFixedPoint in cvCalibrateCamera4
If iFixedPoint is out of rational range, fall back to standard method.
* Fix documentation for overloaded calibrateCamera()
* Remove calibration flag of CALIB_RELEASE_OBJECT
The method selection is based on the range of the index of fixed point.
For minus values, standard calibration method will be chosen. Values in
a rational range will make the object-releasing calibration method
selected.
* Use new interfaces instead of function overload
Existing interfaces are preserved and new interfaces are added. Since
most part of the code base are shared, calibrateCamera() is now a
wrapper function of calibrateCameraRO().
* Fix exported name of calibrateCameraRO()
* Update documentation for calibrateCameraRO()
The circumstances where this method is mostly helpful are described.
* Add note on the rigidity of the calibration target
* Update documentation for calibrateCameraRO()
It is clarified that iFixedPoint is used as a switch to select
calibration method. If input data are not qualified, exceptions will be
thrown instead of fallback scheme.
* Clarify iFixedPoint as switch and remove fallback
iFixedPoint is now used as a switch for calibration method selection. No
fallback scheme is utilized anymore. If the input data are not
qualified, exceptions will be thrown.
* Add badarg test for object-releasing method
* Fix document format of sample list
List items of same level should be indented the same way. Otherwise they
will be formatted as nested lists by Doxygen.
* Add brief intro for objectPoints and imagePoints
* Sync tutorial to sample calibration code
* Update tutorial compatibility version to 4.0
2018-10-26 00:38:55 +08:00
|
|
|
calibrateCameraRO, findChessboardCorners, solvePnP, initCameraMatrix2D, stereoCalibrate, undistort
|
2014-11-19 21:13:41 +08:00
|
|
|
*/
|
2016-06-07 17:31:11 +08:00
|
|
|
CV_EXPORTS_AS(calibrateCameraExtended) double calibrateCamera( InputArrayOfArrays objectPoints,
|
|
|
|
InputArrayOfArrays imagePoints, Size imageSize,
|
|
|
|
InputOutputArray cameraMatrix, InputOutputArray distCoeffs,
|
|
|
|
OutputArrayOfArrays rvecs, OutputArrayOfArrays tvecs,
|
|
|
|
OutputArray stdDeviationsIntrinsics,
|
|
|
|
OutputArray stdDeviationsExtrinsics,
|
|
|
|
OutputArray perViewErrors,
|
|
|
|
int flags = 0, TermCriteria criteria = TermCriteria(
|
|
|
|
TermCriteria::COUNT + TermCriteria::EPS, 30, DBL_EPSILON) );
|
|
|
|
|
Merge pull request #12772 from xoox:calib-release-object
More accurate pinhole camera calibration with imperfect planar target (#12772)
43 commits:
* Add derivatives with respect to object points
Add an output parameter to calculate derivatives of image points with
respect to 3D coordinates of object points. The output jacobian matrix
is a 2Nx3N matrix where N is the number of points.
This commit introduces incompatibility to old function signature.
* Set zero for dpdo matrix before using
dpdo is a sparse matrix with only non-zero value close to major
diagonal. Set it to zero because only elements near major diagonal are
computed.
* Add jacobian columns to projectPoints()
The output jacobian matrix of derivatives with respect to coordinates of
3D object points are added. This might break callers who assume the
columns of jacobian matrix.
* Adapt test code to updated project functions
The test cases for projectPoints() and cvProjectPoints2() are updated to
fit new function signatures.
* Add accuracy test code for dpdo
* Add badarg test for dpdo
* Add new enum item for new calibration method
CALIB_RELEASE_OBJECT is used to whether to release 3D coordinates of
object points. The method was proposed in: K. H. Strobl and G. Hirzinger.
"More Accurate Pinhole Camera Calibration with Imperfect Planar Target".
In Proceedings of the IEEE International Conference on Computer Vision
(ICCV 2011), 1st IEEE Workshop on Challenges and Opportunities in Robot
Perception, Barcelona, Spain, pp. 1068-1075, November 2011.
* Add releasing object method into internal function
It's a simple extension of the standard calibration scheme. We choose to
fix the first and last object point and a user-selected fixed point.
* Add interfaces for extended calibration method
* Refine document for calibrateCamera()
When releasing object points, only the z coordinates of the
objectPoints[0].back is fixed.
* Add link to strobl2011iccv paper
* Improve documentation for calibrateCamera()
* Add implementations of wrapping calibrateCamera()
* Add checking for params of new calibration method
If input parameters are not qualified, then fall back to standard
calibration method.
* Add camera calibration method of releasing object
The current implementation is equal to or better than
https://github.com/xoox/calibrel
* Update doc for CALIB_RELEASE_OBJECT
CALIB_USE_QR or CALIB_USE_LU could be used for faster calibration with
potentially less precise and less stable in some rare cases.
* Add RELEASE_OBJECT calibration to tutorial code
To select the calibration method of releasing object points, a command
line parameter `-d=<number>` should be provided.
* Update tutorial doc for camera_calibration
If the method of releasing object points is merged into OpenCV. It will
be expected to be firstly released in 4.1, I think.
* Reduce epsilon for cornerSubPix()
Epsilon of 0.1 is a bigger one. Preciser corner positions are required
with calibration method of releasing object.
* Refine camera calibration tutorial
The hypothesis coordinates are used to indicate which distance must be
measured between two specified object points.
* Update sample calibration code method selection
Similar to camera_calibration tutorial application, a command line
argument `-dt=<number>` is used to select the calibration method.
* Add guard to flags of cvCalibrateCamera2()
cvCalibrateCamera2() doesn't accept CALIB_RELEASE_OBJECT unless overload
interface is added in the future.
* Simplify fallback when iFixedPoint is out of range
* Refactor projectPoints() to keep compatibilities
* Fix arg string "Bad rvecs header"
* Read calibration flags from test data files
Instead of being hard coded into source file, the calibration flags will
be read from test data files.
opencv_extra/testdata/cv/cameracalibration/calib?.dat must be sync with
the test code.
* Add new C interface of cvCalibrateCamera4()
With this new added C interface, the extended calibration method with
CALIB_RELEASE_OBJECT can be called by C API.
* Add regression test of extended calibration method
It has been tested with new added test data in xoox:calib-release-object
branch of opencv_extra.
* Fix assertion in test_cameracalibration.cpp
The total number of refined 3D object coordinates is checked.
* Add checker for iFixedPoint in cvCalibrateCamera4
If iFixedPoint is out of rational range, fall back to standard method.
* Fix documentation for overloaded calibrateCamera()
* Remove calibration flag of CALIB_RELEASE_OBJECT
The method selection is based on the range of the index of fixed point.
For minus values, standard calibration method will be chosen. Values in
a rational range will make the object-releasing calibration method
selected.
* Use new interfaces instead of function overload
Existing interfaces are preserved and new interfaces are added. Since
most part of the code base are shared, calibrateCamera() is now a
wrapper function of calibrateCameraRO().
* Fix exported name of calibrateCameraRO()
* Update documentation for calibrateCameraRO()
The circumstances where this method is mostly helpful are described.
* Add note on the rigidity of the calibration target
* Update documentation for calibrateCameraRO()
It is clarified that iFixedPoint is used as a switch to select
calibration method. If input data are not qualified, exceptions will be
thrown instead of fallback scheme.
* Clarify iFixedPoint as switch and remove fallback
iFixedPoint is now used as a switch for calibration method selection. No
fallback scheme is utilized anymore. If the input data are not
qualified, exceptions will be thrown.
* Add badarg test for object-releasing method
* Fix document format of sample list
List items of same level should be indented the same way. Otherwise they
will be formatted as nested lists by Doxygen.
* Add brief intro for objectPoints and imagePoints
* Sync tutorial to sample calibration code
* Update tutorial compatibility version to 4.0
2018-10-26 00:38:55 +08:00
|
|
|
/** @overload */
|
|
|
|
CV_EXPORTS_W double calibrateCamera( InputArrayOfArrays objectPoints,
|
2016-06-07 17:31:11 +08:00
|
|
|
InputArrayOfArrays imagePoints, Size imageSize,
|
|
|
|
InputOutputArray cameraMatrix, InputOutputArray distCoeffs,
|
|
|
|
OutputArrayOfArrays rvecs, OutputArrayOfArrays tvecs,
|
|
|
|
int flags = 0, TermCriteria criteria = TermCriteria(
|
Merge pull request #12772 from xoox:calib-release-object
More accurate pinhole camera calibration with imperfect planar target (#12772)
43 commits:
* Add derivatives with respect to object points
Add an output parameter to calculate derivatives of image points with
respect to 3D coordinates of object points. The output jacobian matrix
is a 2Nx3N matrix where N is the number of points.
This commit introduces incompatibility to old function signature.
* Set zero for dpdo matrix before using
dpdo is a sparse matrix with only non-zero value close to major
diagonal. Set it to zero because only elements near major diagonal are
computed.
* Add jacobian columns to projectPoints()
The output jacobian matrix of derivatives with respect to coordinates of
3D object points are added. This might break callers who assume the
columns of jacobian matrix.
* Adapt test code to updated project functions
The test cases for projectPoints() and cvProjectPoints2() are updated to
fit new function signatures.
* Add accuracy test code for dpdo
* Add badarg test for dpdo
* Add new enum item for new calibration method
CALIB_RELEASE_OBJECT is used to whether to release 3D coordinates of
object points. The method was proposed in: K. H. Strobl and G. Hirzinger.
"More Accurate Pinhole Camera Calibration with Imperfect Planar Target".
In Proceedings of the IEEE International Conference on Computer Vision
(ICCV 2011), 1st IEEE Workshop on Challenges and Opportunities in Robot
Perception, Barcelona, Spain, pp. 1068-1075, November 2011.
* Add releasing object method into internal function
It's a simple extension of the standard calibration scheme. We choose to
fix the first and last object point and a user-selected fixed point.
* Add interfaces for extended calibration method
* Refine document for calibrateCamera()
When releasing object points, only the z coordinates of the
objectPoints[0].back is fixed.
* Add link to strobl2011iccv paper
* Improve documentation for calibrateCamera()
* Add implementations of wrapping calibrateCamera()
* Add checking for params of new calibration method
If input parameters are not qualified, then fall back to standard
calibration method.
* Add camera calibration method of releasing object
The current implementation is equal to or better than
https://github.com/xoox/calibrel
* Update doc for CALIB_RELEASE_OBJECT
CALIB_USE_QR or CALIB_USE_LU could be used for faster calibration with
potentially less precise and less stable in some rare cases.
* Add RELEASE_OBJECT calibration to tutorial code
To select the calibration method of releasing object points, a command
line parameter `-d=<number>` should be provided.
* Update tutorial doc for camera_calibration
If the method of releasing object points is merged into OpenCV. It will
be expected to be firstly released in 4.1, I think.
* Reduce epsilon for cornerSubPix()
Epsilon of 0.1 is a bigger one. Preciser corner positions are required
with calibration method of releasing object.
* Refine camera calibration tutorial
The hypothesis coordinates are used to indicate which distance must be
measured between two specified object points.
* Update sample calibration code method selection
Similar to camera_calibration tutorial application, a command line
argument `-dt=<number>` is used to select the calibration method.
* Add guard to flags of cvCalibrateCamera2()
cvCalibrateCamera2() doesn't accept CALIB_RELEASE_OBJECT unless overload
interface is added in the future.
* Simplify fallback when iFixedPoint is out of range
* Refactor projectPoints() to keep compatibilities
* Fix arg string "Bad rvecs header"
* Read calibration flags from test data files
Instead of being hard coded into source file, the calibration flags will
be read from test data files.
opencv_extra/testdata/cv/cameracalibration/calib?.dat must be sync with
the test code.
* Add new C interface of cvCalibrateCamera4()
With this new added C interface, the extended calibration method with
CALIB_RELEASE_OBJECT can be called by C API.
* Add regression test of extended calibration method
It has been tested with new added test data in xoox:calib-release-object
branch of opencv_extra.
* Fix assertion in test_cameracalibration.cpp
The total number of refined 3D object coordinates is checked.
* Add checker for iFixedPoint in cvCalibrateCamera4
If iFixedPoint is out of rational range, fall back to standard method.
* Fix documentation for overloaded calibrateCamera()
* Remove calibration flag of CALIB_RELEASE_OBJECT
The method selection is based on the range of the index of fixed point.
For minus values, standard calibration method will be chosen. Values in
a rational range will make the object-releasing calibration method
selected.
* Use new interfaces instead of function overload
Existing interfaces are preserved and new interfaces are added. Since
most part of the code base are shared, calibrateCamera() is now a
wrapper function of calibrateCameraRO().
* Fix exported name of calibrateCameraRO()
* Update documentation for calibrateCameraRO()
The circumstances where this method is mostly helpful are described.
* Add note on the rigidity of the calibration target
* Update documentation for calibrateCameraRO()
It is clarified that iFixedPoint is used as a switch to select
calibration method. If input data are not qualified, exceptions will be
thrown instead of fallback scheme.
* Clarify iFixedPoint as switch and remove fallback
iFixedPoint is now used as a switch for calibration method selection. No
fallback scheme is utilized anymore. If the input data are not
qualified, exceptions will be thrown.
* Add badarg test for object-releasing method
* Fix document format of sample list
List items of same level should be indented the same way. Otherwise they
will be formatted as nested lists by Doxygen.
* Add brief intro for objectPoints and imagePoints
* Sync tutorial to sample calibration code
* Update tutorial compatibility version to 4.0
2018-10-26 00:38:55 +08:00
|
|
|
TermCriteria::COUNT + TermCriteria::EPS, 30, DBL_EPSILON) );
|
|
|
|
|
|
|
|
/** @brief Finds the camera intrinsic and extrinsic parameters from several views of a calibration pattern.
|
|
|
|
|
|
|
|
This function is an extension of calibrateCamera() with the method of releasing object which was
|
|
|
|
proposed in @cite strobl2011iccv. In many common cases with inaccurate, unmeasured, roughly planar
|
|
|
|
targets (calibration plates), this method can dramatically improve the precision of the estimated
|
|
|
|
camera parameters. Both the object-releasing method and standard method are supported by this
|
|
|
|
function. Use the parameter **iFixedPoint** for method selection. In the internal implementation,
|
|
|
|
calibrateCamera() is a wrapper for this function.
|
|
|
|
|
|
|
|
@param objectPoints Vector of vectors of calibration pattern points in the calibration pattern
|
|
|
|
coordinate space. See calibrateCamera() for details. If the method of releasing object to be used,
|
|
|
|
the identical calibration board must be used in each view and it must be fully visible, and all
|
|
|
|
objectPoints[i] must be the same and all points should be roughly close to a plane. **The calibration
|
|
|
|
target has to be rigid, or at least static if the camera (rather than the calibration target) is
|
|
|
|
shifted for grabbing images.**
|
|
|
|
@param imagePoints Vector of vectors of the projections of calibration pattern points. See
|
|
|
|
calibrateCamera() for details.
|
|
|
|
@param imageSize Size of the image used only to initialize the intrinsic camera matrix.
|
|
|
|
@param iFixedPoint The index of the 3D object point in objectPoints[0] to be fixed. It also acts as
|
|
|
|
a switch for calibration method selection. If object-releasing method to be used, pass in the
|
|
|
|
parameter in the range of [1, objectPoints[0].size()-2], otherwise a value out of this range will
|
|
|
|
make standard calibration method selected. Usually the top-right corner point of the calibration
|
|
|
|
board grid is recommended to be fixed when object-releasing method being utilized. According to
|
|
|
|
\cite strobl2011iccv, two other points are also fixed. In this implementation, objectPoints[0].front
|
|
|
|
and objectPoints[0].back.z are used. With object-releasing method, accurate rvecs, tvecs and
|
|
|
|
newObjPoints are only possible if coordinates of these three fixed points are accurate enough.
|
|
|
|
@param cameraMatrix Output 3x3 floating-point camera matrix. See calibrateCamera() for details.
|
|
|
|
@param distCoeffs Output vector of distortion coefficients. See calibrateCamera() for details.
|
|
|
|
@param rvecs Output vector of rotation vectors estimated for each pattern view. See calibrateCamera()
|
|
|
|
for details.
|
|
|
|
@param tvecs Output vector of translation vectors estimated for each pattern view.
|
|
|
|
@param newObjPoints The updated output vector of calibration pattern points. The coordinates might
|
|
|
|
be scaled based on three fixed points. The returned coordinates are accurate only if the above
|
|
|
|
mentioned three fixed points are accurate. If not needed, noArray() can be passed in. This parameter
|
|
|
|
is ignored with standard calibration method.
|
|
|
|
@param stdDeviationsIntrinsics Output vector of standard deviations estimated for intrinsic parameters.
|
|
|
|
See calibrateCamera() for details.
|
|
|
|
@param stdDeviationsExtrinsics Output vector of standard deviations estimated for extrinsic parameters.
|
|
|
|
See calibrateCamera() for details.
|
|
|
|
@param stdDeviationsObjPoints Output vector of standard deviations estimated for refined coordinates
|
|
|
|
of calibration pattern points. It has the same size and order as objectPoints[0] vector. This
|
|
|
|
parameter is ignored with standard calibration method.
|
|
|
|
@param perViewErrors Output vector of the RMS re-projection error estimated for each pattern view.
|
|
|
|
@param flags Different flags that may be zero or a combination of some predefined values. See
|
|
|
|
calibrateCamera() for details. If the method of releasing object is used, the calibration time may
|
|
|
|
be much longer. CALIB_USE_QR or CALIB_USE_LU could be used for faster calibration with potentially
|
|
|
|
less precise and less stable in some rare cases.
|
|
|
|
@param criteria Termination criteria for the iterative optimization algorithm.
|
|
|
|
|
|
|
|
@return the overall RMS re-projection error.
|
|
|
|
|
|
|
|
The function estimates the intrinsic camera parameters and extrinsic parameters for each of the
|
|
|
|
views. The algorithm is based on @cite Zhang2000, @cite BouguetMCT and @cite strobl2011iccv. See
|
|
|
|
calibrateCamera() for other detailed explanations.
|
|
|
|
@sa
|
|
|
|
calibrateCamera, findChessboardCorners, solvePnP, initCameraMatrix2D, stereoCalibrate, undistort
|
2016-06-07 17:31:11 +08:00
|
|
|
*/
|
Merge pull request #12772 from xoox:calib-release-object
More accurate pinhole camera calibration with imperfect planar target (#12772)
43 commits:
* Add derivatives with respect to object points
Add an output parameter to calculate derivatives of image points with
respect to 3D coordinates of object points. The output jacobian matrix
is a 2Nx3N matrix where N is the number of points.
This commit introduces incompatibility to old function signature.
* Set zero for dpdo matrix before using
dpdo is a sparse matrix with only non-zero value close to major
diagonal. Set it to zero because only elements near major diagonal are
computed.
* Add jacobian columns to projectPoints()
The output jacobian matrix of derivatives with respect to coordinates of
3D object points are added. This might break callers who assume the
columns of jacobian matrix.
* Adapt test code to updated project functions
The test cases for projectPoints() and cvProjectPoints2() are updated to
fit new function signatures.
* Add accuracy test code for dpdo
* Add badarg test for dpdo
* Add new enum item for new calibration method
CALIB_RELEASE_OBJECT is used to whether to release 3D coordinates of
object points. The method was proposed in: K. H. Strobl and G. Hirzinger.
"More Accurate Pinhole Camera Calibration with Imperfect Planar Target".
In Proceedings of the IEEE International Conference on Computer Vision
(ICCV 2011), 1st IEEE Workshop on Challenges and Opportunities in Robot
Perception, Barcelona, Spain, pp. 1068-1075, November 2011.
* Add releasing object method into internal function
It's a simple extension of the standard calibration scheme. We choose to
fix the first and last object point and a user-selected fixed point.
* Add interfaces for extended calibration method
* Refine document for calibrateCamera()
When releasing object points, only the z coordinates of the
objectPoints[0].back is fixed.
* Add link to strobl2011iccv paper
* Improve documentation for calibrateCamera()
* Add implementations of wrapping calibrateCamera()
* Add checking for params of new calibration method
If input parameters are not qualified, then fall back to standard
calibration method.
* Add camera calibration method of releasing object
The current implementation is equal to or better than
https://github.com/xoox/calibrel
* Update doc for CALIB_RELEASE_OBJECT
CALIB_USE_QR or CALIB_USE_LU could be used for faster calibration with
potentially less precise and less stable in some rare cases.
* Add RELEASE_OBJECT calibration to tutorial code
To select the calibration method of releasing object points, a command
line parameter `-d=<number>` should be provided.
* Update tutorial doc for camera_calibration
If the method of releasing object points is merged into OpenCV. It will
be expected to be firstly released in 4.1, I think.
* Reduce epsilon for cornerSubPix()
Epsilon of 0.1 is a bigger one. Preciser corner positions are required
with calibration method of releasing object.
* Refine camera calibration tutorial
The hypothesis coordinates are used to indicate which distance must be
measured between two specified object points.
* Update sample calibration code method selection
Similar to camera_calibration tutorial application, a command line
argument `-dt=<number>` is used to select the calibration method.
* Add guard to flags of cvCalibrateCamera2()
cvCalibrateCamera2() doesn't accept CALIB_RELEASE_OBJECT unless overload
interface is added in the future.
* Simplify fallback when iFixedPoint is out of range
* Refactor projectPoints() to keep compatibilities
* Fix arg string "Bad rvecs header"
* Read calibration flags from test data files
Instead of being hard coded into source file, the calibration flags will
be read from test data files.
opencv_extra/testdata/cv/cameracalibration/calib?.dat must be sync with
the test code.
* Add new C interface of cvCalibrateCamera4()
With this new added C interface, the extended calibration method with
CALIB_RELEASE_OBJECT can be called by C API.
* Add regression test of extended calibration method
It has been tested with new added test data in xoox:calib-release-object
branch of opencv_extra.
* Fix assertion in test_cameracalibration.cpp
The total number of refined 3D object coordinates is checked.
* Add checker for iFixedPoint in cvCalibrateCamera4
If iFixedPoint is out of rational range, fall back to standard method.
* Fix documentation for overloaded calibrateCamera()
* Remove calibration flag of CALIB_RELEASE_OBJECT
The method selection is based on the range of the index of fixed point.
For minus values, standard calibration method will be chosen. Values in
a rational range will make the object-releasing calibration method
selected.
* Use new interfaces instead of function overload
Existing interfaces are preserved and new interfaces are added. Since
most part of the code base are shared, calibrateCamera() is now a
wrapper function of calibrateCameraRO().
* Fix exported name of calibrateCameraRO()
* Update documentation for calibrateCameraRO()
The circumstances where this method is mostly helpful are described.
* Add note on the rigidity of the calibration target
* Update documentation for calibrateCameraRO()
It is clarified that iFixedPoint is used as a switch to select
calibration method. If input data are not qualified, exceptions will be
thrown instead of fallback scheme.
* Clarify iFixedPoint as switch and remove fallback
iFixedPoint is now used as a switch for calibration method selection. No
fallback scheme is utilized anymore. If the input data are not
qualified, exceptions will be thrown.
* Add badarg test for object-releasing method
* Fix document format of sample list
List items of same level should be indented the same way. Otherwise they
will be formatted as nested lists by Doxygen.
* Add brief intro for objectPoints and imagePoints
* Sync tutorial to sample calibration code
* Update tutorial compatibility version to 4.0
2018-10-26 00:38:55 +08:00
|
|
|
CV_EXPORTS_AS(calibrateCameraROExtended) double calibrateCameraRO( InputArrayOfArrays objectPoints,
|
|
|
|
InputArrayOfArrays imagePoints, Size imageSize, int iFixedPoint,
|
|
|
|
InputOutputArray cameraMatrix, InputOutputArray distCoeffs,
|
|
|
|
OutputArrayOfArrays rvecs, OutputArrayOfArrays tvecs,
|
|
|
|
OutputArray newObjPoints,
|
|
|
|
OutputArray stdDeviationsIntrinsics,
|
|
|
|
OutputArray stdDeviationsExtrinsics,
|
|
|
|
OutputArray stdDeviationsObjPoints,
|
|
|
|
OutputArray perViewErrors,
|
|
|
|
int flags = 0, TermCriteria criteria = TermCriteria(
|
|
|
|
TermCriteria::COUNT + TermCriteria::EPS, 30, DBL_EPSILON) );
|
|
|
|
|
|
|
|
/** @overload */
|
|
|
|
CV_EXPORTS_W double calibrateCameraRO( InputArrayOfArrays objectPoints,
|
|
|
|
InputArrayOfArrays imagePoints, Size imageSize, int iFixedPoint,
|
2013-04-11 23:27:54 +08:00
|
|
|
InputOutputArray cameraMatrix, InputOutputArray distCoeffs,
|
2011-06-18 05:21:01 +08:00
|
|
|
OutputArrayOfArrays rvecs, OutputArrayOfArrays tvecs,
|
Merge pull request #12772 from xoox:calib-release-object
More accurate pinhole camera calibration with imperfect planar target (#12772)
43 commits:
* Add derivatives with respect to object points
Add an output parameter to calculate derivatives of image points with
respect to 3D coordinates of object points. The output jacobian matrix
is a 2Nx3N matrix where N is the number of points.
This commit introduces incompatibility to old function signature.
* Set zero for dpdo matrix before using
dpdo is a sparse matrix with only non-zero value close to major
diagonal. Set it to zero because only elements near major diagonal are
computed.
* Add jacobian columns to projectPoints()
The output jacobian matrix of derivatives with respect to coordinates of
3D object points are added. This might break callers who assume the
columns of jacobian matrix.
* Adapt test code to updated project functions
The test cases for projectPoints() and cvProjectPoints2() are updated to
fit new function signatures.
* Add accuracy test code for dpdo
* Add badarg test for dpdo
* Add new enum item for new calibration method
CALIB_RELEASE_OBJECT is used to whether to release 3D coordinates of
object points. The method was proposed in: K. H. Strobl and G. Hirzinger.
"More Accurate Pinhole Camera Calibration with Imperfect Planar Target".
In Proceedings of the IEEE International Conference on Computer Vision
(ICCV 2011), 1st IEEE Workshop on Challenges and Opportunities in Robot
Perception, Barcelona, Spain, pp. 1068-1075, November 2011.
* Add releasing object method into internal function
It's a simple extension of the standard calibration scheme. We choose to
fix the first and last object point and a user-selected fixed point.
* Add interfaces for extended calibration method
* Refine document for calibrateCamera()
When releasing object points, only the z coordinates of the
objectPoints[0].back is fixed.
* Add link to strobl2011iccv paper
* Improve documentation for calibrateCamera()
* Add implementations of wrapping calibrateCamera()
* Add checking for params of new calibration method
If input parameters are not qualified, then fall back to standard
calibration method.
* Add camera calibration method of releasing object
The current implementation is equal to or better than
https://github.com/xoox/calibrel
* Update doc for CALIB_RELEASE_OBJECT
CALIB_USE_QR or CALIB_USE_LU could be used for faster calibration with
potentially less precise and less stable in some rare cases.
* Add RELEASE_OBJECT calibration to tutorial code
To select the calibration method of releasing object points, a command
line parameter `-d=<number>` should be provided.
* Update tutorial doc for camera_calibration
If the method of releasing object points is merged into OpenCV. It will
be expected to be firstly released in 4.1, I think.
* Reduce epsilon for cornerSubPix()
Epsilon of 0.1 is a bigger one. Preciser corner positions are required
with calibration method of releasing object.
* Refine camera calibration tutorial
The hypothesis coordinates are used to indicate which distance must be
measured between two specified object points.
* Update sample calibration code method selection
Similar to camera_calibration tutorial application, a command line
argument `-dt=<number>` is used to select the calibration method.
* Add guard to flags of cvCalibrateCamera2()
cvCalibrateCamera2() doesn't accept CALIB_RELEASE_OBJECT unless overload
interface is added in the future.
* Simplify fallback when iFixedPoint is out of range
* Refactor projectPoints() to keep compatibilities
* Fix arg string "Bad rvecs header"
* Read calibration flags from test data files
Instead of being hard coded into source file, the calibration flags will
be read from test data files.
opencv_extra/testdata/cv/cameracalibration/calib?.dat must be sync with
the test code.
* Add new C interface of cvCalibrateCamera4()
With this new added C interface, the extended calibration method with
CALIB_RELEASE_OBJECT can be called by C API.
* Add regression test of extended calibration method
It has been tested with new added test data in xoox:calib-release-object
branch of opencv_extra.
* Fix assertion in test_cameracalibration.cpp
The total number of refined 3D object coordinates is checked.
* Add checker for iFixedPoint in cvCalibrateCamera4
If iFixedPoint is out of rational range, fall back to standard method.
* Fix documentation for overloaded calibrateCamera()
* Remove calibration flag of CALIB_RELEASE_OBJECT
The method selection is based on the range of the index of fixed point.
For minus values, standard calibration method will be chosen. Values in
a rational range will make the object-releasing calibration method
selected.
* Use new interfaces instead of function overload
Existing interfaces are preserved and new interfaces are added. Since
most part of the code base are shared, calibrateCamera() is now a
wrapper function of calibrateCameraRO().
* Fix exported name of calibrateCameraRO()
* Update documentation for calibrateCameraRO()
The circumstances where this method is mostly helpful are described.
* Add note on the rigidity of the calibration target
* Update documentation for calibrateCameraRO()
It is clarified that iFixedPoint is used as a switch to select
calibration method. If input data are not qualified, exceptions will be
thrown instead of fallback scheme.
* Clarify iFixedPoint as switch and remove fallback
iFixedPoint is now used as a switch for calibration method selection. No
fallback scheme is utilized anymore. If the input data are not
qualified, exceptions will be thrown.
* Add badarg test for object-releasing method
* Fix document format of sample list
List items of same level should be indented the same way. Otherwise they
will be formatted as nested lists by Doxygen.
* Add brief intro for objectPoints and imagePoints
* Sync tutorial to sample calibration code
* Update tutorial compatibility version to 4.0
2018-10-26 00:38:55 +08:00
|
|
|
OutputArray newObjPoints,
|
2013-04-11 23:27:54 +08:00
|
|
|
int flags = 0, TermCriteria criteria = TermCriteria(
|
|
|
|
TermCriteria::COUNT + TermCriteria::EPS, 30, DBL_EPSILON) );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Computes useful camera characteristics from the camera matrix.
|
|
|
|
|
|
|
|
@param cameraMatrix Input camera matrix that can be estimated by calibrateCamera or
|
|
|
|
stereoCalibrate .
|
|
|
|
@param imageSize Input image size in pixels.
|
|
|
|
@param apertureWidth Physical width in mm of the sensor.
|
|
|
|
@param apertureHeight Physical height in mm of the sensor.
|
|
|
|
@param fovx Output field of view in degrees along the horizontal sensor axis.
|
|
|
|
@param fovy Output field of view in degrees along the vertical sensor axis.
|
|
|
|
@param focalLength Focal length of the lens in mm.
|
|
|
|
@param principalPoint Principal point in mm.
|
|
|
|
@param aspectRatio \f$f_y/f_x\f$
|
|
|
|
|
|
|
|
The function computes various useful camera characteristics from the previously estimated camera
|
|
|
|
matrix.
|
|
|
|
|
|
|
|
@note
|
|
|
|
Do keep in mind that the unity measure 'mm' stands for whatever unit of measure one chooses for
|
|
|
|
the chessboard pitch (it can thus be any value).
|
|
|
|
*/
|
2013-04-11 23:27:54 +08:00
|
|
|
CV_EXPORTS_W void calibrationMatrixValues( InputArray cameraMatrix, Size imageSize,
|
|
|
|
double apertureWidth, double apertureHeight,
|
|
|
|
CV_OUT double& fovx, CV_OUT double& fovy,
|
|
|
|
CV_OUT double& focalLength, CV_OUT Point2d& principalPoint,
|
|
|
|
CV_OUT double& aspectRatio );
|
2010-05-25 23:59:48 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Calibrates the stereo camera.
|
|
|
|
|
|
|
|
@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:
|
|
|
|
\f$\vecthreethree{f_x^{(j)}}{0}{c_x^{(j)}}{0}{f_y^{(j)}}{c_y^{(j)}}{0}{0}{1}\f$ , \f$j = 0,\, 1\f$ . If
|
2017-05-24 20:50:41 +08:00
|
|
|
any of CALIB_USE_INTRINSIC_GUESS , CALIB_FIX_ASPECT_RATIO ,
|
|
|
|
CALIB_FIX_INTRINSIC , or CALIB_FIX_FOCAL_LENGTH are specified, some or all of the
|
2014-11-19 21:13:41 +08:00
|
|
|
matrix components must be initialized. See the flags description for details.
|
|
|
|
@param distCoeffs1 Input/output vector of distortion coefficients
|
2015-10-14 18:07:28 +08:00
|
|
|
\f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6 [, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$ of
|
|
|
|
4, 5, 8, 12 or 14 elements. The output vector length depends on the flags.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param cameraMatrix2 Input/output second camera matrix. The parameter is similar to cameraMatrix1
|
|
|
|
@param distCoeffs2 Input/output lens distortion coefficients for the second camera. The parameter
|
|
|
|
is similar to distCoeffs1 .
|
|
|
|
@param imageSize Size of the image used only to initialize intrinsic camera matrix.
|
|
|
|
@param R Output rotation matrix between the 1st and the 2nd camera coordinate systems.
|
|
|
|
@param T Output translation vector between the coordinate systems of the cameras.
|
|
|
|
@param E Output essential matrix.
|
|
|
|
@param F Output fundamental matrix.
|
2018-01-27 03:05:13 +08:00
|
|
|
@param perViewErrors Output vector of the RMS re-projection error estimated for each pattern view.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param flags Different flags that may be zero or a combination of the following values:
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_FIX_INTRINSIC** Fix cameraMatrix? and distCoeffs? so that only R, T, E , and F
|
2014-11-19 21:13:41 +08:00
|
|
|
matrices are estimated.
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_USE_INTRINSIC_GUESS** Optimize some or all of the intrinsic parameters
|
2014-11-19 21:13:41 +08:00
|
|
|
according to the specified flags. Initial values are provided by the user.
|
2018-01-27 03:05:13 +08:00
|
|
|
- **CALIB_USE_EXTRINSIC_GUESS** R, T contain valid initial values that are optimized further.
|
|
|
|
Otherwise R, T are initialized to the median value of the pattern views (each dimension separately).
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_FIX_PRINCIPAL_POINT** Fix the principal points during the optimization.
|
|
|
|
- **CALIB_FIX_FOCAL_LENGTH** Fix \f$f^{(j)}_x\f$ and \f$f^{(j)}_y\f$ .
|
|
|
|
- **CALIB_FIX_ASPECT_RATIO** Optimize \f$f^{(j)}_y\f$ . Fix the ratio \f$f^{(j)}_x/f^{(j)}_y\f$
|
2014-11-19 21:13:41 +08:00
|
|
|
.
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_SAME_FOCAL_LENGTH** Enforce \f$f^{(0)}_x=f^{(1)}_x\f$ and \f$f^{(0)}_y=f^{(1)}_y\f$ .
|
|
|
|
- **CALIB_ZERO_TANGENT_DIST** Set tangential distortion coefficients for each camera to
|
2014-11-19 21:13:41 +08:00
|
|
|
zeros and fix there.
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_FIX_K1,...,CALIB_FIX_K6** Do not change the corresponding radial
|
|
|
|
distortion coefficient during the optimization. If CALIB_USE_INTRINSIC_GUESS is set,
|
2014-11-19 21:13:41 +08:00
|
|
|
the coefficient from the supplied distCoeffs matrix is used. Otherwise, it is set to 0.
|
2017-05-24 20:50:41 +08:00
|
|
|
- **CALIB_RATIONAL_MODEL** Enable coefficients k4, k5, and k6. To provide the backward
|
2014-11-19 21:13:41 +08:00
|
|
|
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.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **CALIB_THIN_PRISM_MODEL** Coefficients s1, s2, s3 and s4 are enabled. To provide the
|
2014-11-19 21:13:41 +08:00
|
|
|
backward compatibility, this extra flag should be explicitly specified to make the
|
|
|
|
calibration function use the thin prism model and return 12 coefficients. If the flag is not
|
|
|
|
set, the function computes and returns only 5 distortion coefficients.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **CALIB_FIX_S1_S2_S3_S4** The thin prism distortion coefficients are not changed during
|
2017-05-24 20:50:41 +08:00
|
|
|
the optimization. If CALIB_USE_INTRINSIC_GUESS is set, the coefficient from the
|
2014-11-19 21:13:41 +08:00
|
|
|
supplied distCoeffs matrix is used. Otherwise, it is set to 0.
|
2015-10-14 18:07:28 +08:00
|
|
|
- **CALIB_TILTED_MODEL** Coefficients tauX and tauY are enabled. To provide the
|
|
|
|
backward compatibility, this extra flag should be explicitly specified to make the
|
|
|
|
calibration function use the tilted sensor model and return 14 coefficients. If the flag is not
|
|
|
|
set, the function computes and returns only 5 distortion coefficients.
|
|
|
|
- **CALIB_FIX_TAUX_TAUY** The coefficients of the tilted sensor model are not changed during
|
2017-05-24 20:50:41 +08:00
|
|
|
the optimization. If CALIB_USE_INTRINSIC_GUESS is set, the coefficient from the
|
2015-10-14 18:07:28 +08:00
|
|
|
supplied distCoeffs matrix is used. Otherwise, it is set to 0.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param criteria Termination criteria for the iterative optimization algorithm.
|
|
|
|
|
|
|
|
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 solvePnP ), then those poses definitely relate to each other.
|
|
|
|
This means that, given ( \f$R_1\f$,\f$T_1\f$ ), it should be possible to compute ( \f$R_2\f$,\f$T_2\f$ ). 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 ( \f$R\f$,\f$T\f$ ) so that:
|
|
|
|
|
2017-01-05 05:24:25 +08:00
|
|
|
\f[R_2=R*R_1\f]
|
|
|
|
\f[T_2=R*T_1 + T,\f]
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
Optionally, it computes the essential matrix E:
|
|
|
|
|
|
|
|
\f[E= \vecthreethree{0}{-T_2}{T_1}{T_2}{0}{-T_0}{-T_1}{T_0}{0} *R\f]
|
|
|
|
|
|
|
|
where \f$T_i\f$ are components of the translation vector \f$T\f$ : \f$T=[T_0, T_1, T_2]^T\f$ . And the function
|
|
|
|
can also compute the fundamental matrix F:
|
|
|
|
|
|
|
|
\f[F = cameraMatrix2^{-T} E cameraMatrix1^{-1}\f]
|
|
|
|
|
|
|
|
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
|
2017-05-24 20:50:41 +08:00
|
|
|
calibrateCamera ), you are recommended to do so and then pass CALIB_FIX_INTRINSIC flag to the
|
2014-11-19 21:13:41 +08:00
|
|
|
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
|
2017-05-24 20:50:41 +08:00
|
|
|
CALIB_SAME_FOCAL_LENGTH and CALIB_ZERO_TANGENT_DIST flags, which is usually a
|
2014-11-19 21:13:41 +08:00
|
|
|
reasonable assumption.
|
|
|
|
|
|
|
|
Similarly to 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.
|
|
|
|
*/
|
2018-01-27 03:05:13 +08:00
|
|
|
CV_EXPORTS_AS(stereoCalibrateExtended) double stereoCalibrate( InputArrayOfArrays objectPoints,
|
|
|
|
InputArrayOfArrays imagePoints1, InputArrayOfArrays imagePoints2,
|
|
|
|
InputOutputArray cameraMatrix1, InputOutputArray distCoeffs1,
|
|
|
|
InputOutputArray cameraMatrix2, InputOutputArray distCoeffs2,
|
|
|
|
Size imageSize, InputOutputArray R,InputOutputArray T, OutputArray E, OutputArray F,
|
|
|
|
OutputArray perViewErrors, int flags = CALIB_FIX_INTRINSIC,
|
|
|
|
TermCriteria criteria = TermCriteria(TermCriteria::COUNT+TermCriteria::EPS, 30, 1e-6) );
|
|
|
|
|
|
|
|
/// @overload
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W double stereoCalibrate( InputArrayOfArrays objectPoints,
|
2013-04-11 23:27:54 +08:00
|
|
|
InputArrayOfArrays imagePoints1, InputArrayOfArrays imagePoints2,
|
|
|
|
InputOutputArray cameraMatrix1, InputOutputArray distCoeffs1,
|
|
|
|
InputOutputArray cameraMatrix2, InputOutputArray distCoeffs2,
|
|
|
|
Size imageSize, OutputArray R,OutputArray T, OutputArray E, OutputArray F,
|
2013-12-17 13:53:44 +08:00
|
|
|
int flags = CALIB_FIX_INTRINSIC,
|
|
|
|
TermCriteria criteria = TermCriteria(TermCriteria::COUNT+TermCriteria::EPS, 30, 1e-6) );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Computes rectification transforms for each head of a calibrated stereo camera.
|
|
|
|
|
|
|
|
@param cameraMatrix1 First camera matrix.
|
|
|
|
@param distCoeffs1 First camera distortion parameters.
|
2015-12-09 06:28:32 +08:00
|
|
|
@param cameraMatrix2 Second camera matrix.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param distCoeffs2 Second camera distortion parameters.
|
|
|
|
@param imageSize Size of the image used for stereo calibration.
|
|
|
|
@param R Rotation matrix between the coordinate systems of the first and the second cameras.
|
|
|
|
@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.
|
|
|
|
@param Q Output \f$4 \times 4\f$ disparity-to-depth mapping matrix (see reprojectImageTo3D ).
|
2017-05-24 20:50:41 +08:00
|
|
|
@param flags Operation flags that may be zero or CALIB_ZERO_DISPARITY . If the flag is set,
|
2014-11-19 21:13:41 +08:00
|
|
|
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.
|
|
|
|
@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
|
2014-11-21 16:28:14 +08:00
|
|
|
initUndistortRectifyMap (see the stereo_calib.cpp sample in OpenCV samples directory). When (0,0)
|
2014-11-19 21:13:41 +08:00
|
|
|
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 validPixROI1 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).
|
|
|
|
@param validPixROI2 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).
|
|
|
|
|
|
|
|
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 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:
|
|
|
|
|
|
|
|
- **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:
|
|
|
|
|
|
|
|
\f[\texttt{P1} = \begin{bmatrix} f & 0 & cx_1 & 0 \\ 0 & f & cy & 0 \\ 0 & 0 & 1 & 0 \end{bmatrix}\f]
|
|
|
|
|
|
|
|
\f[\texttt{P2} = \begin{bmatrix} f & 0 & cx_2 & T_x*f \\ 0 & f & cy & 0 \\ 0 & 0 & 1 & 0 \end{bmatrix} ,\f]
|
|
|
|
|
|
|
|
where \f$T_x\f$ is a horizontal shift between the cameras and \f$cx_1=cx_2\f$ if
|
2017-05-24 20:50:41 +08:00
|
|
|
CALIB_ZERO_DISPARITY is set.
|
2014-11-19 21:13:41 +08: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:
|
|
|
|
|
|
|
|
\f[\texttt{P1} = \begin{bmatrix} f & 0 & cx & 0 \\ 0 & f & cy_1 & 0 \\ 0 & 0 & 1 & 0 \end{bmatrix}\f]
|
|
|
|
|
|
|
|
\f[\texttt{P2} = \begin{bmatrix} f & 0 & cx & 0 \\ 0 & f & cy_2 & T_y*f \\ 0 & 0 & 1 & 0 \end{bmatrix} ,\f]
|
|
|
|
|
2014-11-21 16:28:14 +08:00
|
|
|
where \f$T_y\f$ is a vertical shift between the cameras and \f$cy_1=cy_2\f$ if CALIB_ZERO_DISPARITY is
|
2014-11-19 21:13:41 +08:00
|
|
|
set.
|
|
|
|
|
|
|
|
As you can see, the first three columns of P1 and P2 will effectively be the new "rectified" camera
|
|
|
|
matrices. The matrices, together with R1 and R2 , can then be passed to initUndistortRectifyMap to
|
|
|
|
initialize the rectification map for each camera.
|
|
|
|
|
2014-11-21 16:28:14 +08:00
|
|
|
See below the screenshot from the stereo_calib.cpp sample. Some red horizontal lines pass through
|
2014-11-19 21:13:41 +08:00
|
|
|
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.
|
|
|
|
|
|
|
|
![image](pics/stereo_undistort.jpg)
|
|
|
|
*/
|
2011-10-05 08:14:43 +08:00
|
|
|
CV_EXPORTS_W void stereoRectify( InputArray cameraMatrix1, InputArray distCoeffs1,
|
2013-04-11 23:27:54 +08:00
|
|
|
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 = -1, Size newImageSize = Size(),
|
|
|
|
CV_OUT Rect* validPixROI1 = 0, CV_OUT Rect* validPixROI2 = 0 );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Computes a rectification transform for an uncalibrated stereo camera.
|
|
|
|
|
|
|
|
@param points1 Array of feature points in the first image.
|
|
|
|
@param points2 The corresponding points in the second image. The same formats as in
|
|
|
|
findFundamentalMat are supported.
|
|
|
|
@param F Input fundamental matrix. It can be computed from the same set of point pairs using
|
|
|
|
findFundamentalMat .
|
|
|
|
@param imgSize Size of the image.
|
|
|
|
@param H1 Output rectification homography matrix for the first image.
|
|
|
|
@param H2 Output rectification homography matrix for the second image.
|
|
|
|
@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 \f$|\texttt{points2[i]}^T*\texttt{F}*\texttt{points1[i]}|>\texttt{threshold}\f$ ) are
|
2017-11-09 00:55:48 +08:00
|
|
|
rejected prior to computing the homographies. Otherwise, all the points are considered inliers.
|
2014-11-19 21:13:41 +08: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 stereoRectify is that the function outputs not the rectification
|
|
|
|
transformations in the object (3D) space, but the planar perspective transformations encoded by the
|
2014-11-26 19:21:08 +08:00
|
|
|
homography matrices H1 and H2 . The function implements the algorithm @cite Hartley99 .
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
@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 calibrateCamera . Then, the images can be corrected using undistort , or
|
|
|
|
just the point coordinates can be corrected with undistortPoints .
|
|
|
|
*/
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W bool stereoRectifyUncalibrated( InputArray points1, InputArray points2,
|
|
|
|
InputArray F, Size imgSize,
|
2011-04-17 21:14:45 +08:00
|
|
|
OutputArray H1, OutputArray H2,
|
2013-04-11 23:27:54 +08:00
|
|
|
double threshold = 5 );
|
2010-10-28 02:26:39 +08:00
|
|
|
|
|
|
|
//! computes the rectification transformations for 3-head camera, where all the heads are on the same line.
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W float rectify3Collinear( InputArray cameraMatrix1, InputArray distCoeffs1,
|
|
|
|
InputArray cameraMatrix2, InputArray distCoeffs2,
|
|
|
|
InputArray cameraMatrix3, InputArray distCoeffs3,
|
|
|
|
InputArrayOfArrays imgpt1, InputArrayOfArrays imgpt3,
|
|
|
|
Size imageSize, InputArray R12, InputArray T12,
|
|
|
|
InputArray R13, InputArray T13,
|
2011-04-17 21:14:45 +08:00
|
|
|
OutputArray R1, OutputArray R2, OutputArray R3,
|
|
|
|
OutputArray P1, OutputArray P2, OutputArray P3,
|
|
|
|
OutputArray Q, double alpha, Size newImgSize,
|
2010-10-28 02:26:39 +08:00
|
|
|
CV_OUT Rect* roi1, CV_OUT Rect* roi2, int flags );
|
2012-05-28 15:36:14 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Returns the new camera matrix based on the free scaling parameter.
|
|
|
|
|
|
|
|
@param cameraMatrix Input camera matrix.
|
|
|
|
@param distCoeffs Input vector of distortion coefficients
|
2015-10-14 18:07:28 +08:00
|
|
|
\f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6 [, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$ of
|
|
|
|
4, 5, 8, 12 or 14 elements. If the vector is NULL/empty, the zero distortion coefficients are
|
|
|
|
assumed.
|
2014-11-19 21:13:41 +08: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
|
|
|
|
stereoRectify for details.
|
2017-11-09 00:55:48 +08:00
|
|
|
@param newImgSize Image size after rectification. By default, it is set to imageSize .
|
2014-11-19 21:13:41 +08:00
|
|
|
@param validPixROI Optional output rectangle that outlines all-good-pixels region in the
|
|
|
|
undistorted image. See roi1, roi2 description in 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.
|
2014-11-21 16:28:14 +08:00
|
|
|
@return new_camera_matrix Output new camera matrix.
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
The function computes and returns 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.
|
2017-11-09 00:55:48 +08:00
|
|
|
When alpha\>0 , the undistorted result is likely to have some black pixels corresponding to
|
2014-11-19 21:13:41 +08:00
|
|
|
"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
|
|
|
|
initUndistortRectifyMap to produce the maps for remap .
|
|
|
|
*/
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W Mat getOptimalNewCameraMatrix( InputArray cameraMatrix, InputArray distCoeffs,
|
2013-04-11 23:27:54 +08:00
|
|
|
Size imageSize, double alpha, Size newImgSize = Size(),
|
|
|
|
CV_OUT Rect* validPixROI = 0,
|
|
|
|
bool centerPrincipalPoint = false);
|
2010-05-12 15:33:21 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Converts points from Euclidean to homogeneous space.
|
|
|
|
|
|
|
|
@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).
|
|
|
|
*/
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W void convertPointsToHomogeneous( InputArray src, OutputArray dst );
|
2012-05-28 15:36:14 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Converts points from homogeneous to Euclidean space.
|
|
|
|
|
|
|
|
@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-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W void convertPointsFromHomogeneous( InputArray src, OutputArray dst );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Converts points to/from homogeneous coordinates.
|
|
|
|
|
|
|
|
@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
|
|
|
|
convertPointsToHomogeneous or convertPointsFromHomogeneous.
|
|
|
|
|
|
|
|
@note The function is obsolete. Use one of the previous two functions instead.
|
|
|
|
*/
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS void convertPointsHomogeneous( InputArray src, OutputArray dst );
|
2012-05-28 15:36:14 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Calculates a fundamental matrix from the corresponding points in two images.
|
|
|
|
|
|
|
|
@param points1 Array of N points from the first image. The point coordinates should be
|
|
|
|
floating-point (single or double precision).
|
|
|
|
@param points2 Array of the second image points of the same size and format as points1 .
|
|
|
|
@param method Method for computing a fundamental matrix.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **CV_FM_7POINT** for a 7-point algorithm. \f$N = 7\f$
|
|
|
|
- **CV_FM_8POINT** for an 8-point algorithm. \f$N \ge 8\f$
|
|
|
|
- **CV_FM_RANSAC** for the RANSAC algorithm. \f$N \ge 8\f$
|
|
|
|
- **CV_FM_LMEDS** for the LMedS algorithm. \f$N \ge 8\f$
|
2018-01-19 20:23:09 +08:00
|
|
|
@param ransacReprojThreshold Parameter used only for RANSAC. It is the maximum distance from a point to an epipolar
|
2014-11-19 21:13:41 +08:00
|
|
|
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.
|
2018-01-19 20:23:09 +08:00
|
|
|
@param confidence Parameter used for the RANSAC and LMedS methods only. It specifies a desirable level
|
2014-11-19 21:13:41 +08:00
|
|
|
of confidence (probability) that the estimated matrix is correct.
|
|
|
|
@param mask
|
|
|
|
|
|
|
|
The epipolar geometry is described by the following equation:
|
|
|
|
|
|
|
|
\f[[p_2; 1]^T F [p_1; 1] = 0\f]
|
|
|
|
|
|
|
|
where \f$F\f$ is a fundamental matrix, \f$p_1\f$ and \f$p_2\f$ are corresponding points in the first and the
|
|
|
|
second images, respectively.
|
|
|
|
|
|
|
|
The function calculates the fundamental matrix using one of four methods listed above and returns
|
|
|
|
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 ( \f$9 \times 3\f$ matrix that stores all 3
|
|
|
|
matrices sequentially).
|
|
|
|
|
|
|
|
The calculated fundamental matrix may be passed further to computeCorrespondEpilines that finds the
|
|
|
|
epipolar lines corresponding to the specified points. It can also be passed to
|
|
|
|
stereoRectifyUncalibrated to compute the rectification transformation. :
|
|
|
|
@code
|
|
|
|
// Example. Estimation of fundamental matrix using the RANSAC algorithm
|
|
|
|
int point_count = 100;
|
|
|
|
vector<Point2f> points1(point_count);
|
|
|
|
vector<Point2f> points2(point_count);
|
|
|
|
|
|
|
|
// initialize the points here ...
|
|
|
|
for( int i = 0; i < point_count; i++ )
|
|
|
|
{
|
|
|
|
points1[i] = ...;
|
|
|
|
points2[i] = ...;
|
|
|
|
}
|
|
|
|
|
|
|
|
Mat fundamental_matrix =
|
|
|
|
findFundamentalMat(points1, points2, FM_RANSAC, 3, 0.99);
|
|
|
|
@endcode
|
|
|
|
*/
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS_W Mat findFundamentalMat( InputArray points1, InputArray points2,
|
2013-04-11 23:27:54 +08:00
|
|
|
int method = FM_RANSAC,
|
2018-01-19 20:23:09 +08:00
|
|
|
double ransacReprojThreshold = 3., double confidence = 0.99,
|
2013-04-11 23:27:54 +08:00
|
|
|
OutputArray mask = noArray() );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @overload */
|
2011-06-06 22:51:27 +08:00
|
|
|
CV_EXPORTS Mat findFundamentalMat( InputArray points1, InputArray points2,
|
2013-04-11 23:27:54 +08:00
|
|
|
OutputArray mask, int method = FM_RANSAC,
|
2018-01-19 20:23:09 +08:00
|
|
|
double ransacReprojThreshold = 3., double confidence = 0.99 );
|
2011-04-23 20:49:14 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Calculates an essential matrix from the corresponding points in two images.
|
|
|
|
|
2015-06-03 15:50:33 +08:00
|
|
|
@param points1 Array of N (N \>= 5) 2D points from the first image. The point coordinates should
|
|
|
|
be floating-point (single or double precision).
|
|
|
|
@param points2 Array of the second image points of the same size and format as points1 .
|
|
|
|
@param cameraMatrix Camera matrix \f$K = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}\f$ .
|
|
|
|
Note that this function assumes that points1 and points2 are feature points from cameras with the
|
|
|
|
same camera matrix.
|
2017-10-31 00:13:59 +08:00
|
|
|
@param method Method for computing an essential matrix.
|
2015-06-03 15:50:33 +08:00
|
|
|
- **RANSAC** for the RANSAC algorithm.
|
2017-10-31 00:13:59 +08:00
|
|
|
- **LMEDS** for the LMedS algorithm.
|
2016-01-08 22:46:17 +08:00
|
|
|
@param prob Parameter used for the RANSAC or LMedS methods only. It specifies a desirable level of
|
|
|
|
confidence (probability) that the estimated matrix is correct.
|
2015-06-03 15:50:33 +08:00
|
|
|
@param threshold 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.
|
|
|
|
@param mask 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.
|
|
|
|
|
|
|
|
This function estimates essential matrix based on the five-point algorithm solver in @cite Nister03 .
|
|
|
|
@cite SteweniusCFS is also a related. The epipolar geometry is described by the following equation:
|
|
|
|
|
|
|
|
\f[[p_2; 1]^T K^{-T} E K^{-1} [p_1; 1] = 0\f]
|
|
|
|
|
|
|
|
where \f$E\f$ is an essential matrix, \f$p_1\f$ and \f$p_2\f$ are corresponding points in the first and the
|
|
|
|
second images, respectively. The result of this function may be passed further to
|
|
|
|
decomposeEssentialMat or recoverPose to recover the relative pose between cameras.
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W Mat findEssentialMat( InputArray points1, InputArray points2,
|
|
|
|
InputArray cameraMatrix, int method = RANSAC,
|
|
|
|
double prob = 0.999, double threshold = 1.0,
|
|
|
|
OutputArray mask = noArray() );
|
|
|
|
|
|
|
|
/** @overload
|
2014-11-19 21:13:41 +08:00
|
|
|
@param points1 Array of N (N \>= 5) 2D points from the first image. The point coordinates should
|
|
|
|
be floating-point (single or double precision).
|
|
|
|
@param points2 Array of the second image points of the same size and format as points1 .
|
|
|
|
@param focal focal length of the camera. Note that this function assumes that points1 and points2
|
2016-10-06 20:09:26 +08:00
|
|
|
are feature points from cameras with same focal length and principal point.
|
|
|
|
@param pp principal point of the camera.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param method Method for computing a fundamental matrix.
|
|
|
|
- **RANSAC** for the RANSAC algorithm.
|
2015-07-10 18:45:45 +08:00
|
|
|
- **LMEDS** for the LMedS algorithm.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param threshold 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.
|
|
|
|
@param prob Parameter used for the RANSAC or LMedS methods only. It specifies a desirable level of
|
|
|
|
confidence (probability) that the estimated matrix is correct.
|
|
|
|
@param mask 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.
|
|
|
|
|
2015-06-03 15:50:33 +08:00
|
|
|
This function differs from the one above that it computes camera matrix from focal length and
|
|
|
|
principal point:
|
2014-11-19 21:13:41 +08:00
|
|
|
|
2015-06-03 15:50:33 +08:00
|
|
|
\f[K =
|
2014-11-19 21:13:41 +08:00
|
|
|
\begin{bmatrix}
|
|
|
|
f & 0 & x_{pp} \\
|
|
|
|
0 & f & y_{pp} \\
|
|
|
|
0 & 0 & 1
|
|
|
|
\end{bmatrix}\f]
|
|
|
|
*/
|
2013-09-09 17:55:35 +08:00
|
|
|
CV_EXPORTS_W Mat findEssentialMat( InputArray points1, InputArray points2,
|
2013-04-11 23:27:54 +08:00
|
|
|
double focal = 1.0, Point2d pp = Point2d(0, 0),
|
|
|
|
int method = RANSAC, double prob = 0.999,
|
|
|
|
double threshold = 1.0, OutputArray mask = noArray() );
|
2012-12-27 01:58:50 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Decompose an essential matrix to possible rotations and translation.
|
|
|
|
|
|
|
|
@param E The input essential matrix.
|
|
|
|
@param R1 One possible rotation matrix.
|
|
|
|
@param R2 Another possible rotation matrix.
|
|
|
|
@param t One possible translation.
|
|
|
|
|
2014-11-26 19:21:08 +08:00
|
|
|
This function decompose an essential matrix E using svd decomposition @cite HartleyZ00 . Generally 4
|
2014-11-19 21:13:41 +08:00
|
|
|
possible poses exists for a given E. They are \f$[R_1, t]\f$, \f$[R_1, -t]\f$, \f$[R_2, t]\f$, \f$[R_2, -t]\f$. By
|
|
|
|
decomposing E, you can only get the direction of the translation, so the function returns unit t.
|
|
|
|
*/
|
2013-09-09 17:55:35 +08:00
|
|
|
CV_EXPORTS_W void decomposeEssentialMat( InputArray E, OutputArray R1, OutputArray R2, OutputArray t );
|
2012-12-27 01:58:50 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Recover relative camera rotation and translation from an estimated essential matrix and the
|
|
|
|
corresponding points in two images, using cheirality check. Returns the number of inliers which pass
|
|
|
|
the check.
|
|
|
|
|
|
|
|
@param E The input essential matrix.
|
|
|
|
@param points1 Array of N 2D points from the first image. The point coordinates should be
|
|
|
|
floating-point (single or double precision).
|
|
|
|
@param points2 Array of the second image points of the same size and format as points1 .
|
2015-06-03 15:50:33 +08:00
|
|
|
@param cameraMatrix Camera matrix \f$K = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}\f$ .
|
|
|
|
Note that this function assumes that points1 and points2 are feature points from cameras with the
|
|
|
|
same camera matrix.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param R Recovered relative rotation.
|
2017-11-09 00:55:48 +08:00
|
|
|
@param t Recovered relative translation.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param mask Input/output mask for inliers in points1 and points2.
|
|
|
|
: If it is not empty, then it marks inliers in points1 and points2 for then given essential
|
|
|
|
matrix E. Only these inliers will be used to recover pose. In the output mask only inliers
|
|
|
|
which pass the cheirality check.
|
|
|
|
This function decomposes an essential matrix using decomposeEssentialMat and then verifies possible
|
|
|
|
pose hypotheses by doing cheirality check. The cheirality check basically means that the
|
2014-11-26 19:21:08 +08:00
|
|
|
triangulated 3D points should have positive depth. Some details can be found in @cite Nister03 .
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
This function can be used to process output E and mask from findEssentialMat. In this scenario,
|
|
|
|
points1 and points2 are the same input for findEssentialMat. :
|
|
|
|
@code
|
|
|
|
// Example. Estimation of fundamental matrix using the RANSAC algorithm
|
|
|
|
int point_count = 100;
|
|
|
|
vector<Point2f> points1(point_count);
|
|
|
|
vector<Point2f> points2(point_count);
|
|
|
|
|
|
|
|
// initialize the points here ...
|
|
|
|
for( int i = 0; i < point_count; i++ )
|
|
|
|
{
|
|
|
|
points1[i] = ...;
|
|
|
|
points2[i] = ...;
|
|
|
|
}
|
|
|
|
|
2015-06-03 15:50:33 +08:00
|
|
|
// cametra matrix with both focal lengths = 1, and principal point = (0, 0)
|
|
|
|
Mat cameraMatrix = Mat::eye(3, 3, CV_64F);
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
Mat E, R, t, mask;
|
|
|
|
|
2015-06-03 15:50:33 +08:00
|
|
|
E = findEssentialMat(points1, points2, cameraMatrix, RANSAC, 0.999, 1.0, mask);
|
|
|
|
recoverPose(E, points1, points2, cameraMatrix, R, t, mask);
|
2014-11-19 21:13:41 +08:00
|
|
|
@endcode
|
|
|
|
*/
|
2015-06-03 15:50:33 +08:00
|
|
|
CV_EXPORTS_W int recoverPose( InputArray E, InputArray points1, InputArray points2,
|
|
|
|
InputArray cameraMatrix, OutputArray R, OutputArray t,
|
|
|
|
InputOutputArray mask = noArray() );
|
|
|
|
|
|
|
|
/** @overload
|
|
|
|
@param E The input essential matrix.
|
|
|
|
@param points1 Array of N 2D points from the first image. The point coordinates should be
|
|
|
|
floating-point (single or double precision).
|
|
|
|
@param points2 Array of the second image points of the same size and format as points1 .
|
|
|
|
@param R Recovered relative rotation.
|
2017-11-09 00:55:48 +08:00
|
|
|
@param t Recovered relative translation.
|
2015-06-03 15:50:33 +08:00
|
|
|
@param focal Focal length of the camera. Note that this function assumes that points1 and points2
|
2016-10-06 20:09:26 +08:00
|
|
|
are feature points from cameras with same focal length and principal point.
|
|
|
|
@param pp principal point of the camera.
|
2015-06-03 15:50:33 +08:00
|
|
|
@param mask Input/output mask for inliers in points1 and points2.
|
|
|
|
: If it is not empty, then it marks inliers in points1 and points2 for then given essential
|
|
|
|
matrix E. Only these inliers will be used to recover pose. In the output mask only inliers
|
|
|
|
which pass the cheirality check.
|
|
|
|
|
|
|
|
This function differs from the one above that it computes camera matrix from focal length and
|
|
|
|
principal point:
|
|
|
|
|
|
|
|
\f[K =
|
|
|
|
\begin{bmatrix}
|
|
|
|
f & 0 & x_{pp} \\
|
|
|
|
0 & f & y_{pp} \\
|
|
|
|
0 & 0 & 1
|
|
|
|
\end{bmatrix}\f]
|
|
|
|
*/
|
2013-09-09 17:55:35 +08:00
|
|
|
CV_EXPORTS_W int recoverPose( InputArray E, InputArray points1, InputArray points2,
|
2013-04-11 23:27:54 +08:00
|
|
|
OutputArray R, OutputArray t,
|
2013-03-13 20:22:44 +08:00
|
|
|
double focal = 1.0, Point2d pp = Point2d(0, 0),
|
2013-04-11 23:27:54 +08:00
|
|
|
InputOutputArray mask = noArray() );
|
2013-03-13 20:22:44 +08:00
|
|
|
|
2017-02-27 17:12:10 +08:00
|
|
|
/** @overload
|
|
|
|
@param E The input essential matrix.
|
|
|
|
@param points1 Array of N 2D points from the first image. The point coordinates should be
|
|
|
|
floating-point (single or double precision).
|
|
|
|
@param points2 Array of the second image points of the same size and format as points1.
|
|
|
|
@param cameraMatrix Camera matrix \f$K = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}\f$ .
|
|
|
|
Note that this function assumes that points1 and points2 are feature points from cameras with the
|
|
|
|
same camera matrix.
|
|
|
|
@param R Recovered relative rotation.
|
2017-11-09 00:55:48 +08:00
|
|
|
@param t Recovered relative translation.
|
2017-02-27 17:12:10 +08:00
|
|
|
@param distanceThresh threshold distance which is used to filter out far away points (i.e. infinite points).
|
|
|
|
@param mask Input/output mask for inliers in points1 and points2.
|
|
|
|
: If it is not empty, then it marks inliers in points1 and points2 for then given essential
|
|
|
|
matrix E. Only these inliers will be used to recover pose. In the output mask only inliers
|
|
|
|
which pass the cheirality check.
|
|
|
|
@param triangulatedPoints 3d points which were reconstructed by triangulation.
|
|
|
|
*/
|
|
|
|
|
|
|
|
CV_EXPORTS_W int recoverPose( InputArray E, InputArray points1, InputArray points2,
|
|
|
|
InputArray cameraMatrix, OutputArray R, OutputArray t, double distanceThresh, InputOutputArray mask = noArray(),
|
|
|
|
OutputArray triangulatedPoints = noArray());
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief For points in an image of a stereo pair, computes the corresponding epilines in the other image.
|
|
|
|
|
2014-11-21 16:28:14 +08:00
|
|
|
@param points Input points. \f$N \times 1\f$ or \f$1 \times N\f$ matrix of type CV_32FC2 or
|
2014-11-19 21:13:41 +08:00
|
|
|
vector\<Point2f\> .
|
|
|
|
@param whichImage Index of the image (1 or 2) that contains the points .
|
|
|
|
@param F Fundamental matrix that can be estimated using findFundamentalMat or stereoRectify .
|
|
|
|
@param lines Output vector of the epipolar lines corresponding to the points in the other image.
|
|
|
|
Each line \f$ax + by + c=0\f$ is encoded by 3 numbers \f$(a, b, c)\f$ .
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
From the fundamental matrix definition (see findFundamentalMat ), line \f$l^{(2)}_i\f$ in the second
|
|
|
|
image for the point \f$p^{(1)}_i\f$ in the first image (when whichImage=1 ) is computed as:
|
|
|
|
|
|
|
|
\f[l^{(2)}_i = F p^{(1)}_i\f]
|
|
|
|
|
|
|
|
And vice versa, when whichImage=2, \f$l^{(1)}_i\f$ is computed from \f$p^{(2)}_i\f$ as:
|
|
|
|
|
|
|
|
\f[l^{(1)}_i = F^T p^{(2)}_i\f]
|
|
|
|
|
|
|
|
Line coefficients are defined up to a scale. They are normalized so that \f$a_i^2+b_i^2=1\f$ .
|
|
|
|
*/
|
2013-06-25 18:08:23 +08:00
|
|
|
CV_EXPORTS_W void computeCorrespondEpilines( InputArray points, int whichImage,
|
|
|
|
InputArray F, OutputArray lines );
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Reconstructs points by triangulation.
|
|
|
|
|
|
|
|
@param projMatr1 3x4 projection matrix of the first camera.
|
|
|
|
@param projMatr2 3x4 projection matrix of the second camera.
|
|
|
|
@param projPoints1 2xN array of feature points in the first image. In case of c++ version it can
|
|
|
|
be also a vector of feature points or two-channel matrix of size 1xN or Nx1.
|
|
|
|
@param projPoints2 2xN array of corresponding points in the second image. In case of c++ version
|
|
|
|
it can be also a vector of feature points or two-channel matrix of size 1xN or Nx1.
|
|
|
|
@param points4D 4xN array of reconstructed points in homogeneous coordinates.
|
|
|
|
|
|
|
|
The function reconstructs 3-dimensional points (in homogeneous coordinates) by using their
|
|
|
|
observations with a stereo camera. Projections matrices can be obtained from stereoRectify.
|
|
|
|
|
|
|
|
@note
|
|
|
|
Keep in mind that all input data should be of float type in order for this function to work.
|
|
|
|
|
|
|
|
@sa
|
|
|
|
reprojectImageTo3D
|
|
|
|
*/
|
2012-03-29 18:39:06 +08:00
|
|
|
CV_EXPORTS_W void triangulatePoints( InputArray projMatr1, InputArray projMatr2,
|
|
|
|
InputArray projPoints1, InputArray projPoints2,
|
|
|
|
OutputArray points4D );
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Refines coordinates of corresponding points.
|
|
|
|
|
|
|
|
@param F 3x3 fundamental matrix.
|
|
|
|
@param points1 1xN array containing the first set of points.
|
|
|
|
@param points2 1xN array containing the second set of points.
|
|
|
|
@param newPoints1 The optimized points1.
|
|
|
|
@param newPoints2 The optimized points2.
|
|
|
|
|
|
|
|
The function implements the Optimal Triangulation Method (see Multiple View Geometry for details).
|
|
|
|
For each given point correspondence points1[i] \<-\> points2[i], and a fundamental matrix F, it
|
|
|
|
computes the corrected correspondences newPoints1[i] \<-\> newPoints2[i] that minimize the geometric
|
|
|
|
error \f$d(points1[i], newPoints1[i])^2 + d(points2[i],newPoints2[i])^2\f$ (where \f$d(a,b)\f$ is the
|
|
|
|
geometric distance between points \f$a\f$ and \f$b\f$ ) subject to the epipolar constraint
|
|
|
|
\f$newPoints2^T * F * newPoints1 = 0\f$ .
|
|
|
|
*/
|
2012-03-29 21:21:24 +08:00
|
|
|
CV_EXPORTS_W void correctMatches( InputArray F, InputArray points1, InputArray points2,
|
|
|
|
OutputArray newPoints1, OutputArray newPoints2 );
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Filters off small noise blobs (speckles) in the disparity map
|
|
|
|
|
|
|
|
@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.
|
|
|
|
*/
|
2013-04-11 23:27:54 +08:00
|
|
|
CV_EXPORTS_W void filterSpeckles( InputOutputArray img, double newVal,
|
|
|
|
int maxSpeckleSize, double maxDiff,
|
|
|
|
InputOutputArray buf = noArray() );
|
|
|
|
|
|
|
|
//! computes valid disparity ROI from the valid ROIs of the rectified images (that are returned by cv::stereoRectify())
|
|
|
|
CV_EXPORTS_W Rect getValidDisparityROI( Rect roi1, Rect roi2,
|
|
|
|
int minDisparity, int numberOfDisparities,
|
|
|
|
int SADWindowSize );
|
|
|
|
|
|
|
|
//! validates disparity using the left-right check. The matrix "cost" should be computed by the stereo correspondence algorithm
|
|
|
|
CV_EXPORTS_W void validateDisparity( InputOutputArray disparity, InputArray cost,
|
|
|
|
int minDisparity, int numberOfDisparities,
|
|
|
|
int disp12MaxDisp = 1 );
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Reprojects a disparity image to 3D space.
|
|
|
|
|
|
|
|
@param disparity Input single-channel 8-bit unsigned, 16-bit signed, 32-bit signed or 32-bit
|
2015-03-25 04:06:31 +08:00
|
|
|
floating-point disparity image. If 16-bit signed format is used, the values are assumed to have no
|
|
|
|
fractional bits.
|
2014-11-21 16:28:14 +08: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
|
2014-11-19 21:13:41 +08:00
|
|
|
map.
|
|
|
|
@param Q \f$4 \times 4\f$ perspective transformation matrix that can be obtained with 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 StereoMatcher::compute ) are transformed
|
|
|
|
to 3D points with a very large Z value (currently set to 10000).
|
2014-11-21 16:28:14 +08:00
|
|
|
@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.
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
The function transforms a single-channel disparity map to a 3-channel image representing a 3D
|
2017-10-31 00:13:59 +08:00
|
|
|
surface. That is, for each pixel (x,y) and the corresponding disparity d=disparity(x,y) , it
|
2014-11-19 21:13:41 +08:00
|
|
|
computes:
|
|
|
|
|
|
|
|
\f[\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}\f]
|
|
|
|
|
|
|
|
The matrix Q can be an arbitrary \f$4 \times 4\f$ matrix (for example, the one computed by
|
|
|
|
stereoRectify). To reproject a sparse set of points {(x,y,d),...} to 3D space, use
|
|
|
|
perspectiveTransform .
|
|
|
|
*/
|
2013-04-11 23:27:54 +08:00
|
|
|
CV_EXPORTS_W void reprojectImageTo3D( InputArray disparity,
|
|
|
|
OutputArray _3dImage, InputArray Q,
|
|
|
|
bool handleMissingValues = false,
|
|
|
|
int ddepth = -1 );
|
|
|
|
|
2015-09-04 22:16:39 +08:00
|
|
|
/** @brief Calculates the Sampson Distance between two points.
|
|
|
|
|
2018-01-19 20:23:09 +08:00
|
|
|
The function cv::sampsonDistance calculates and returns the first order approximation of the geometric error as:
|
|
|
|
\f[
|
|
|
|
sd( \texttt{pt1} , \texttt{pt2} )=
|
|
|
|
\frac{(\texttt{pt2}^t \cdot \texttt{F} \cdot \texttt{pt1})^2}
|
|
|
|
{((\texttt{F} \cdot \texttt{pt1})(0))^2 +
|
|
|
|
((\texttt{F} \cdot \texttt{pt1})(1))^2 +
|
|
|
|
((\texttt{F}^t \cdot \texttt{pt2})(0))^2 +
|
|
|
|
((\texttt{F}^t \cdot \texttt{pt2})(1))^2}
|
|
|
|
\f]
|
|
|
|
The fundamental matrix may be calculated using the cv::findFundamentalMat function. See @cite HartleyZ00 11.4.3 for details.
|
2015-09-04 22:16:39 +08:00
|
|
|
@param pt1 first homogeneous 2d point
|
|
|
|
@param pt2 second homogeneous 2d point
|
|
|
|
@param F fundamental matrix
|
2018-01-19 20:23:09 +08:00
|
|
|
@return The computed Sampson distance.
|
2015-09-04 22:16:39 +08:00
|
|
|
*/
|
|
|
|
CV_EXPORTS_W double sampsonDistance(InputArray pt1, InputArray pt2, InputArray F);
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Computes an optimal affine transformation between two 3D point sets.
|
|
|
|
|
2018-01-18 19:40:59 +08:00
|
|
|
It computes
|
|
|
|
\f[
|
|
|
|
\begin{bmatrix}
|
|
|
|
x\\
|
|
|
|
y\\
|
|
|
|
z\\
|
|
|
|
\end{bmatrix}
|
|
|
|
=
|
|
|
|
\begin{bmatrix}
|
|
|
|
a_{11} & a_{12} & a_{13}\\
|
|
|
|
a_{21} & a_{22} & a_{23}\\
|
|
|
|
a_{31} & a_{32} & a_{33}\\
|
|
|
|
\end{bmatrix}
|
|
|
|
\begin{bmatrix}
|
|
|
|
X\\
|
|
|
|
Y\\
|
|
|
|
Z\\
|
|
|
|
\end{bmatrix}
|
|
|
|
+
|
|
|
|
\begin{bmatrix}
|
|
|
|
b_1\\
|
|
|
|
b_2\\
|
|
|
|
b_3\\
|
|
|
|
\end{bmatrix}
|
|
|
|
\f]
|
|
|
|
|
|
|
|
@param src First input 3D point set containing \f$(X,Y,Z)\f$.
|
|
|
|
@param dst Second input 3D point set containing \f$(x,y,z)\f$.
|
|
|
|
@param out Output 3D affine transformation matrix \f$3 \times 4\f$ of the form
|
|
|
|
\f[
|
|
|
|
\begin{bmatrix}
|
|
|
|
a_{11} & a_{12} & a_{13} & b_1\\
|
|
|
|
a_{21} & a_{22} & a_{23} & b_2\\
|
|
|
|
a_{31} & a_{32} & a_{33} & b_3\\
|
|
|
|
\end{bmatrix}
|
|
|
|
\f]
|
|
|
|
@param inliers Output vector indicating which points are inliers (1-inlier, 0-outlier).
|
2014-11-19 21:13:41 +08:00
|
|
|
@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.
|
|
|
|
*/
|
2013-04-11 23:27:54 +08:00
|
|
|
CV_EXPORTS_W int estimateAffine3D(InputArray src, InputArray dst,
|
|
|
|
OutputArray out, OutputArray inliers,
|
|
|
|
double ransacThreshold = 3, double confidence = 0.99);
|
|
|
|
|
Merge pull request #6933 from hrnr:gsoc_all
[GSOC] New camera model for stitching pipeline
* implement estimateAffine2D
estimates affine transformation using robust RANSAC method.
* uses RANSAC framework in calib3d
* includes accuracy test
* uses SVD decomposition for solving 3 point equation
* implement estimateAffinePartial2D
estimates limited affine transformation
* includes accuracy test
* stitching: add affine matcher
initial version of matcher that estimates affine transformation
* stitching: added affine transform estimator
initial version of estimator that simply chain transformations in homogeneous coordinates
* calib3d: rename estimateAffine3D test
test Calib3d_EstimateAffineTransform rename to Calib3d_EstimateAffine3D. This is more descriptive and prevents confusion with estimateAffine2D tests.
* added perf test for estimateAffine functions
tests both estimateAffine2D and estimateAffinePartial2D
* calib3d: compare error in square in estimateAffine2D
* incorporates fix from #6768
* rerun affine estimation on inliers
* stitching: new API for parallel feature finding
due to ABI breakage new functionality is added to `FeaturesFinder2`, `SurfFeaturesFinder2` and `OrbFeaturesFinder2`
* stitching: add tests for parallel feature find API
* perf test (about linear speed up)
* accuracy test compares results with serial version
* stitching: use dynamic_cast to overcome ABI issues
adding parallel API to FeaturesFinder breaks ABI. This commit uses dynamic_cast and hardcodes thread-safe finders to avoid breaking ABI.
This should be replaced by proper method similar to FeaturesMatcher on next ABI break.
* use estimateAffinePartial2D in AffineBestOf2NearestMatcher
* add constructor to AffineBestOf2NearestMatcher
* allows to choose between full affine transform and partial affine transform. Other params are the as for BestOf2NearestMatcher
* added protected field
* samples: stitching_detailed support affine estimator and matcher
* added new flags to choose matcher and estimator
* stitching: rework affine matcher
represent transformation in homogeneous coordinates
affine matcher: remove duplicite code
rework flow to get rid of duplicite code
affine matcher: do not center points to (0, 0)
it is not needed for affine model. it should not affect estimation in any way.
affine matcher: remove unneeded cv namespacing
* stitching: add stub bundle adjuster
* adds stub bundle adjuster that does nothing
* can be used in place of standard bundle adjusters to omit bundle adjusting step
* samples: stitching detailed, support no budle adjust
* uses new NoBundleAdjuster
* added affine warper
* uses R to get whole affine transformation and propagates rotation and translation to plane warper
* add affine warper factory class
* affine warper: compensate transformation
* samples: stitching_detailed add support for affine warper
* add Stitcher::create method
this method follows similar constructor methods and returns smart pointer. This allows constructing Stitcher according to OpenCV guidelines.
* supports multiple stitcher configurations (PANORAMA and SCANS) for convenient setup
* returns cv::Ptr
* stitcher: dynamicaly determine correct estimator
we need to use affine estimator for affine matcher
* preserves ABI (but add hints for ABI 4)
* uses dynamic_cast hack to inject correct estimator
* sample stitching: add support for multiple modes
shows how to use different configurations of stitcher easily (panorama stitching and scans affine model)
* stitcher: find features in parallel
use new FeatureFinder API to find features in parallel. Parallelized using TBB.
* stitching: disable parallel feature finding for OCL
it does not bring much speedup to run features finder in parallel when OpenCL is enabled, because finder needs to wait for OCL device.
Also, currently ORB is not thread-safe when OCL is enabled.
* stitching: move matcher tests
move matchers tests perf_stich.cpp -> perf_matchers.cpp
* stitching: add affine stiching integration test
test basic affine stitching (SCANS mode of stitcher) with images that have only translation between them
* enable surf for stitching tests
stitching.b12 test was failing with surf
investigated the issue, surf is producing good result. Transformation is only slightly different from ORB, so that resulting pano does not exactly match ORB's result. That caused sanity check to fail.
* added size checks similar to other tests
* sanity check will be applied only for ORB
* stitching: fix wrong estimator choice
if case was exactly wrong, estimators were chosen wrong
added logging for estimated transformation
* enable surf for matchers stitching tests
* enable SURF
* rework sanity checking. Check estimated transform instead of matches. Est. transform should be more stable and comparable between SURF and ORB.
* remove regression checking for VectorFeatures tests. It has a lot if data andtest is the same as previous except it test different vector size for performance, so sanity checking does not add any value here. Added basic sanity asserts instead.
* stitching tests: allow relative error for transform
* allows .01 relative error for estimated homography sanity check in stitching matchers tests
* fix VS warning
stitching tests: increase relative error
increase relative error to make it pass on all platforms (results are still good).
stitching test: allow bigger relative error
transformation can differ in small values (with small absolute difference, but large relative difference). transformation output still looks usable for all platforms. This difference affects only mac and windows, linux passes fine with small difference.
* stitching: add tests for affine matcher
uses s1, s2 images. added also new sanity data.
* stitching tests: use different data for matchers tests
this data should yeild more stable transformation (it has much more matches, especially for surf). Sanity data regenerated.
* stitching test: rework tests for matchers
* separated rotation and translations as they are different by scale.
* use appropriate absolute error for them separately. (relative error does not work for values near zero.)
* stitching: fix affine warper compensation
calculation of rotation and translation extracted for plane warper was wrong
* stitching test: enable surf for opencl integration tests
* enable SURF with correct guard (HAVE_OPENCV_XFEATURES2D)
* add OPENCL guard and correct namespace as usual for opencl tests
* stitching: add ocl accuracy test for affine warper
test consistent results with ocl on and off
* stitching: add affine warper ocl perf test
add affine warper to existing warper perf tests. Added new sanity data.
* stitching: do not overwrite inliers in affine matcher
* estimation is run second time on inliers only, inliers produces in second run will not be therefore correct for all matches
* calib3d: add Levenberg–Marquardt refining to estimateAffine2D* functions
this adds affine Levenberg–Marquardt refining to estimateAffine2D functions similar to what is done in findHomography.
implements Levenberg–Marquardt refinig for both full affine and partial affine transformations.
* stitching: remove reestimation step in affine matcher
reestimation step is not needed. estimateAffine2D* functions are running their own reestimation on inliers using the Levenberg-Marquardt algorithm, which is better than simply rerunning RANSAC on inliers.
* implement partial affine bundle adjuster
bundle adjuster that expect affine transform with 4DOF. Refines parameters for all cameras together.
stitching: fix bug in BundleAdjusterAffinePartial
* use the invers properly
* use static buffer for invers to speed it up
* samples: add affine bundle adjuster option to stitching_detailed
* add support for using affine bundle adjuster with 4DOF
* improve logging of initial intristics
* sttiching: add affine bundle adjuster test
* fix build warnings
* stitching: increase limit on sanity check
prevents spurious test failures on mac. values are still pretty fine.
* stitching: set affine bundle adjuster for SCANS mode
* fix bug with AffineBestOf2NearestMatcher (we want to select affine partial mode)
* select right bundle adjuster
* stitching: increase error bound for matcher tests
* this prevents failure on mac. tranformation is still ok.
* stitching: implement affine bundle adjuster
* implements affine bundle adjuster that is using full affine transform
* existing test case modified to test both affinePartial an full affine bundle adjuster
* add stitching tutorial
* show basic usage of stitching api (Stitcher class)
* stitching: add more integration test for affine stitching
* added new datasets to existing testcase
* removed unused include
* calib3d: move `haveCollinearPoints` to common header
* added comment to make that this also checks too close points
* calib3d: redone checkSubset for estimateAffine* callback
* use common function to check collinearity
* this also ensures that point will not be too close to each other
* calib3d: change estimateAffine* functions API
* more similar to `findHomography`, `findFundamentalMat`, `findEssentialMat` and similar
* follows standard recommended semantic INPUTS, OUTPUTS, FLAGS
* allows to disable refining
* supported LMEDS robust method (tests yet to come) along with RANSAC
* extended docs with some tips
* calib3d: rewrite estimateAffine2D test
* rewrite in googletest style
* parametrize to test both robust methods (RANSAC and LMEDS)
* get rid of boilerplate
* calib3d: rework estimateAffinePartial2D test
* rework in googletest style
* add testing for LMEDS
* calib3d: rework estimateAffine*2D perf test
* test for LMEDS speed
* test with/without Levenberg-Marquart
* remove sanity checking (this is covered by accuracy tests)
* calib3d: improve estimateAffine*2D tests
* test transformations in loop
* improves test by testing more potential transformations
* calib3d: rewrite kernels for estimateAffine*2D functions
* use analytical solution instead of SVD
* this version is faster especially for smaller amount of points
* calib3d: tune up perf of estimateAffine*2D functions
* avoid copying inliers
* avoid converting input points if not necessary
* check only `from` point for collinearity, as `to` does not affect stability of transform
* tutorials: add commands examples to stitching tutorials
* add some examples how to run stitcher sample code
* mention stitching_detailed.cpp
* calib3d: change computeError for estimateAffine*2D
* do error computing in floats instead of doubles
this have required precision + we were storing the result in float anyway. This make code faster and allows auto-vectorization by smart compilers.
* documentation: mention estimateAffine*2D function
* refer to new functions on appropriate places
* prefer estimateAffine*2D over estimateRigidTransform
* stitching: add camera models documentations
* mention camera models in module documentation to give user a better overview and reduce confusion
2016-10-23 00:10:42 +08:00
|
|
|
/** @brief Computes an optimal affine transformation between two 2D point sets.
|
|
|
|
|
2018-01-18 19:40:59 +08:00
|
|
|
It computes
|
|
|
|
\f[
|
|
|
|
\begin{bmatrix}
|
|
|
|
x\\
|
|
|
|
y\\
|
|
|
|
\end{bmatrix}
|
|
|
|
=
|
|
|
|
\begin{bmatrix}
|
|
|
|
a_{11} & a_{12}\\
|
|
|
|
a_{21} & a_{22}\\
|
|
|
|
\end{bmatrix}
|
|
|
|
\begin{bmatrix}
|
|
|
|
X\\
|
|
|
|
Y\\
|
|
|
|
\end{bmatrix}
|
|
|
|
+
|
|
|
|
\begin{bmatrix}
|
|
|
|
b_1\\
|
|
|
|
b_2\\
|
|
|
|
\end{bmatrix}
|
|
|
|
\f]
|
|
|
|
|
|
|
|
@param from First input 2D point set containing \f$(X,Y)\f$.
|
|
|
|
@param to Second input 2D point set containing \f$(x,y)\f$.
|
|
|
|
@param inliers Output vector indicating which points are inliers (1-inlier, 0-outlier).
|
2017-10-31 00:13:59 +08:00
|
|
|
@param method Robust method used to compute transformation. The following methods are possible:
|
Merge pull request #6933 from hrnr:gsoc_all
[GSOC] New camera model for stitching pipeline
* implement estimateAffine2D
estimates affine transformation using robust RANSAC method.
* uses RANSAC framework in calib3d
* includes accuracy test
* uses SVD decomposition for solving 3 point equation
* implement estimateAffinePartial2D
estimates limited affine transformation
* includes accuracy test
* stitching: add affine matcher
initial version of matcher that estimates affine transformation
* stitching: added affine transform estimator
initial version of estimator that simply chain transformations in homogeneous coordinates
* calib3d: rename estimateAffine3D test
test Calib3d_EstimateAffineTransform rename to Calib3d_EstimateAffine3D. This is more descriptive and prevents confusion with estimateAffine2D tests.
* added perf test for estimateAffine functions
tests both estimateAffine2D and estimateAffinePartial2D
* calib3d: compare error in square in estimateAffine2D
* incorporates fix from #6768
* rerun affine estimation on inliers
* stitching: new API for parallel feature finding
due to ABI breakage new functionality is added to `FeaturesFinder2`, `SurfFeaturesFinder2` and `OrbFeaturesFinder2`
* stitching: add tests for parallel feature find API
* perf test (about linear speed up)
* accuracy test compares results with serial version
* stitching: use dynamic_cast to overcome ABI issues
adding parallel API to FeaturesFinder breaks ABI. This commit uses dynamic_cast and hardcodes thread-safe finders to avoid breaking ABI.
This should be replaced by proper method similar to FeaturesMatcher on next ABI break.
* use estimateAffinePartial2D in AffineBestOf2NearestMatcher
* add constructor to AffineBestOf2NearestMatcher
* allows to choose between full affine transform and partial affine transform. Other params are the as for BestOf2NearestMatcher
* added protected field
* samples: stitching_detailed support affine estimator and matcher
* added new flags to choose matcher and estimator
* stitching: rework affine matcher
represent transformation in homogeneous coordinates
affine matcher: remove duplicite code
rework flow to get rid of duplicite code
affine matcher: do not center points to (0, 0)
it is not needed for affine model. it should not affect estimation in any way.
affine matcher: remove unneeded cv namespacing
* stitching: add stub bundle adjuster
* adds stub bundle adjuster that does nothing
* can be used in place of standard bundle adjusters to omit bundle adjusting step
* samples: stitching detailed, support no budle adjust
* uses new NoBundleAdjuster
* added affine warper
* uses R to get whole affine transformation and propagates rotation and translation to plane warper
* add affine warper factory class
* affine warper: compensate transformation
* samples: stitching_detailed add support for affine warper
* add Stitcher::create method
this method follows similar constructor methods and returns smart pointer. This allows constructing Stitcher according to OpenCV guidelines.
* supports multiple stitcher configurations (PANORAMA and SCANS) for convenient setup
* returns cv::Ptr
* stitcher: dynamicaly determine correct estimator
we need to use affine estimator for affine matcher
* preserves ABI (but add hints for ABI 4)
* uses dynamic_cast hack to inject correct estimator
* sample stitching: add support for multiple modes
shows how to use different configurations of stitcher easily (panorama stitching and scans affine model)
* stitcher: find features in parallel
use new FeatureFinder API to find features in parallel. Parallelized using TBB.
* stitching: disable parallel feature finding for OCL
it does not bring much speedup to run features finder in parallel when OpenCL is enabled, because finder needs to wait for OCL device.
Also, currently ORB is not thread-safe when OCL is enabled.
* stitching: move matcher tests
move matchers tests perf_stich.cpp -> perf_matchers.cpp
* stitching: add affine stiching integration test
test basic affine stitching (SCANS mode of stitcher) with images that have only translation between them
* enable surf for stitching tests
stitching.b12 test was failing with surf
investigated the issue, surf is producing good result. Transformation is only slightly different from ORB, so that resulting pano does not exactly match ORB's result. That caused sanity check to fail.
* added size checks similar to other tests
* sanity check will be applied only for ORB
* stitching: fix wrong estimator choice
if case was exactly wrong, estimators were chosen wrong
added logging for estimated transformation
* enable surf for matchers stitching tests
* enable SURF
* rework sanity checking. Check estimated transform instead of matches. Est. transform should be more stable and comparable between SURF and ORB.
* remove regression checking for VectorFeatures tests. It has a lot if data andtest is the same as previous except it test different vector size for performance, so sanity checking does not add any value here. Added basic sanity asserts instead.
* stitching tests: allow relative error for transform
* allows .01 relative error for estimated homography sanity check in stitching matchers tests
* fix VS warning
stitching tests: increase relative error
increase relative error to make it pass on all platforms (results are still good).
stitching test: allow bigger relative error
transformation can differ in small values (with small absolute difference, but large relative difference). transformation output still looks usable for all platforms. This difference affects only mac and windows, linux passes fine with small difference.
* stitching: add tests for affine matcher
uses s1, s2 images. added also new sanity data.
* stitching tests: use different data for matchers tests
this data should yeild more stable transformation (it has much more matches, especially for surf). Sanity data regenerated.
* stitching test: rework tests for matchers
* separated rotation and translations as they are different by scale.
* use appropriate absolute error for them separately. (relative error does not work for values near zero.)
* stitching: fix affine warper compensation
calculation of rotation and translation extracted for plane warper was wrong
* stitching test: enable surf for opencl integration tests
* enable SURF with correct guard (HAVE_OPENCV_XFEATURES2D)
* add OPENCL guard and correct namespace as usual for opencl tests
* stitching: add ocl accuracy test for affine warper
test consistent results with ocl on and off
* stitching: add affine warper ocl perf test
add affine warper to existing warper perf tests. Added new sanity data.
* stitching: do not overwrite inliers in affine matcher
* estimation is run second time on inliers only, inliers produces in second run will not be therefore correct for all matches
* calib3d: add Levenberg–Marquardt refining to estimateAffine2D* functions
this adds affine Levenberg–Marquardt refining to estimateAffine2D functions similar to what is done in findHomography.
implements Levenberg–Marquardt refinig for both full affine and partial affine transformations.
* stitching: remove reestimation step in affine matcher
reestimation step is not needed. estimateAffine2D* functions are running their own reestimation on inliers using the Levenberg-Marquardt algorithm, which is better than simply rerunning RANSAC on inliers.
* implement partial affine bundle adjuster
bundle adjuster that expect affine transform with 4DOF. Refines parameters for all cameras together.
stitching: fix bug in BundleAdjusterAffinePartial
* use the invers properly
* use static buffer for invers to speed it up
* samples: add affine bundle adjuster option to stitching_detailed
* add support for using affine bundle adjuster with 4DOF
* improve logging of initial intristics
* sttiching: add affine bundle adjuster test
* fix build warnings
* stitching: increase limit on sanity check
prevents spurious test failures on mac. values are still pretty fine.
* stitching: set affine bundle adjuster for SCANS mode
* fix bug with AffineBestOf2NearestMatcher (we want to select affine partial mode)
* select right bundle adjuster
* stitching: increase error bound for matcher tests
* this prevents failure on mac. tranformation is still ok.
* stitching: implement affine bundle adjuster
* implements affine bundle adjuster that is using full affine transform
* existing test case modified to test both affinePartial an full affine bundle adjuster
* add stitching tutorial
* show basic usage of stitching api (Stitcher class)
* stitching: add more integration test for affine stitching
* added new datasets to existing testcase
* removed unused include
* calib3d: move `haveCollinearPoints` to common header
* added comment to make that this also checks too close points
* calib3d: redone checkSubset for estimateAffine* callback
* use common function to check collinearity
* this also ensures that point will not be too close to each other
* calib3d: change estimateAffine* functions API
* more similar to `findHomography`, `findFundamentalMat`, `findEssentialMat` and similar
* follows standard recommended semantic INPUTS, OUTPUTS, FLAGS
* allows to disable refining
* supported LMEDS robust method (tests yet to come) along with RANSAC
* extended docs with some tips
* calib3d: rewrite estimateAffine2D test
* rewrite in googletest style
* parametrize to test both robust methods (RANSAC and LMEDS)
* get rid of boilerplate
* calib3d: rework estimateAffinePartial2D test
* rework in googletest style
* add testing for LMEDS
* calib3d: rework estimateAffine*2D perf test
* test for LMEDS speed
* test with/without Levenberg-Marquart
* remove sanity checking (this is covered by accuracy tests)
* calib3d: improve estimateAffine*2D tests
* test transformations in loop
* improves test by testing more potential transformations
* calib3d: rewrite kernels for estimateAffine*2D functions
* use analytical solution instead of SVD
* this version is faster especially for smaller amount of points
* calib3d: tune up perf of estimateAffine*2D functions
* avoid copying inliers
* avoid converting input points if not necessary
* check only `from` point for collinearity, as `to` does not affect stability of transform
* tutorials: add commands examples to stitching tutorials
* add some examples how to run stitcher sample code
* mention stitching_detailed.cpp
* calib3d: change computeError for estimateAffine*2D
* do error computing in floats instead of doubles
this have required precision + we were storing the result in float anyway. This make code faster and allows auto-vectorization by smart compilers.
* documentation: mention estimateAffine*2D function
* refer to new functions on appropriate places
* prefer estimateAffine*2D over estimateRigidTransform
* stitching: add camera models documentations
* mention camera models in module documentation to give user a better overview and reduce confusion
2016-10-23 00:10:42 +08:00
|
|
|
- cv::RANSAC - RANSAC-based robust method
|
|
|
|
- cv::LMEDS - Least-Median robust method
|
|
|
|
RANSAC is the default method.
|
|
|
|
@param ransacReprojThreshold Maximum reprojection error in the RANSAC algorithm to consider
|
|
|
|
a point as an inlier. Applies only to RANSAC.
|
2018-01-18 19:40:59 +08:00
|
|
|
@param maxIters The maximum number of robust method iterations.
|
Merge pull request #6933 from hrnr:gsoc_all
[GSOC] New camera model for stitching pipeline
* implement estimateAffine2D
estimates affine transformation using robust RANSAC method.
* uses RANSAC framework in calib3d
* includes accuracy test
* uses SVD decomposition for solving 3 point equation
* implement estimateAffinePartial2D
estimates limited affine transformation
* includes accuracy test
* stitching: add affine matcher
initial version of matcher that estimates affine transformation
* stitching: added affine transform estimator
initial version of estimator that simply chain transformations in homogeneous coordinates
* calib3d: rename estimateAffine3D test
test Calib3d_EstimateAffineTransform rename to Calib3d_EstimateAffine3D. This is more descriptive and prevents confusion with estimateAffine2D tests.
* added perf test for estimateAffine functions
tests both estimateAffine2D and estimateAffinePartial2D
* calib3d: compare error in square in estimateAffine2D
* incorporates fix from #6768
* rerun affine estimation on inliers
* stitching: new API for parallel feature finding
due to ABI breakage new functionality is added to `FeaturesFinder2`, `SurfFeaturesFinder2` and `OrbFeaturesFinder2`
* stitching: add tests for parallel feature find API
* perf test (about linear speed up)
* accuracy test compares results with serial version
* stitching: use dynamic_cast to overcome ABI issues
adding parallel API to FeaturesFinder breaks ABI. This commit uses dynamic_cast and hardcodes thread-safe finders to avoid breaking ABI.
This should be replaced by proper method similar to FeaturesMatcher on next ABI break.
* use estimateAffinePartial2D in AffineBestOf2NearestMatcher
* add constructor to AffineBestOf2NearestMatcher
* allows to choose between full affine transform and partial affine transform. Other params are the as for BestOf2NearestMatcher
* added protected field
* samples: stitching_detailed support affine estimator and matcher
* added new flags to choose matcher and estimator
* stitching: rework affine matcher
represent transformation in homogeneous coordinates
affine matcher: remove duplicite code
rework flow to get rid of duplicite code
affine matcher: do not center points to (0, 0)
it is not needed for affine model. it should not affect estimation in any way.
affine matcher: remove unneeded cv namespacing
* stitching: add stub bundle adjuster
* adds stub bundle adjuster that does nothing
* can be used in place of standard bundle adjusters to omit bundle adjusting step
* samples: stitching detailed, support no budle adjust
* uses new NoBundleAdjuster
* added affine warper
* uses R to get whole affine transformation and propagates rotation and translation to plane warper
* add affine warper factory class
* affine warper: compensate transformation
* samples: stitching_detailed add support for affine warper
* add Stitcher::create method
this method follows similar constructor methods and returns smart pointer. This allows constructing Stitcher according to OpenCV guidelines.
* supports multiple stitcher configurations (PANORAMA and SCANS) for convenient setup
* returns cv::Ptr
* stitcher: dynamicaly determine correct estimator
we need to use affine estimator for affine matcher
* preserves ABI (but add hints for ABI 4)
* uses dynamic_cast hack to inject correct estimator
* sample stitching: add support for multiple modes
shows how to use different configurations of stitcher easily (panorama stitching and scans affine model)
* stitcher: find features in parallel
use new FeatureFinder API to find features in parallel. Parallelized using TBB.
* stitching: disable parallel feature finding for OCL
it does not bring much speedup to run features finder in parallel when OpenCL is enabled, because finder needs to wait for OCL device.
Also, currently ORB is not thread-safe when OCL is enabled.
* stitching: move matcher tests
move matchers tests perf_stich.cpp -> perf_matchers.cpp
* stitching: add affine stiching integration test
test basic affine stitching (SCANS mode of stitcher) with images that have only translation between them
* enable surf for stitching tests
stitching.b12 test was failing with surf
investigated the issue, surf is producing good result. Transformation is only slightly different from ORB, so that resulting pano does not exactly match ORB's result. That caused sanity check to fail.
* added size checks similar to other tests
* sanity check will be applied only for ORB
* stitching: fix wrong estimator choice
if case was exactly wrong, estimators were chosen wrong
added logging for estimated transformation
* enable surf for matchers stitching tests
* enable SURF
* rework sanity checking. Check estimated transform instead of matches. Est. transform should be more stable and comparable between SURF and ORB.
* remove regression checking for VectorFeatures tests. It has a lot if data andtest is the same as previous except it test different vector size for performance, so sanity checking does not add any value here. Added basic sanity asserts instead.
* stitching tests: allow relative error for transform
* allows .01 relative error for estimated homography sanity check in stitching matchers tests
* fix VS warning
stitching tests: increase relative error
increase relative error to make it pass on all platforms (results are still good).
stitching test: allow bigger relative error
transformation can differ in small values (with small absolute difference, but large relative difference). transformation output still looks usable for all platforms. This difference affects only mac and windows, linux passes fine with small difference.
* stitching: add tests for affine matcher
uses s1, s2 images. added also new sanity data.
* stitching tests: use different data for matchers tests
this data should yeild more stable transformation (it has much more matches, especially for surf). Sanity data regenerated.
* stitching test: rework tests for matchers
* separated rotation and translations as they are different by scale.
* use appropriate absolute error for them separately. (relative error does not work for values near zero.)
* stitching: fix affine warper compensation
calculation of rotation and translation extracted for plane warper was wrong
* stitching test: enable surf for opencl integration tests
* enable SURF with correct guard (HAVE_OPENCV_XFEATURES2D)
* add OPENCL guard and correct namespace as usual for opencl tests
* stitching: add ocl accuracy test for affine warper
test consistent results with ocl on and off
* stitching: add affine warper ocl perf test
add affine warper to existing warper perf tests. Added new sanity data.
* stitching: do not overwrite inliers in affine matcher
* estimation is run second time on inliers only, inliers produces in second run will not be therefore correct for all matches
* calib3d: add Levenberg–Marquardt refining to estimateAffine2D* functions
this adds affine Levenberg–Marquardt refining to estimateAffine2D functions similar to what is done in findHomography.
implements Levenberg–Marquardt refinig for both full affine and partial affine transformations.
* stitching: remove reestimation step in affine matcher
reestimation step is not needed. estimateAffine2D* functions are running their own reestimation on inliers using the Levenberg-Marquardt algorithm, which is better than simply rerunning RANSAC on inliers.
* implement partial affine bundle adjuster
bundle adjuster that expect affine transform with 4DOF. Refines parameters for all cameras together.
stitching: fix bug in BundleAdjusterAffinePartial
* use the invers properly
* use static buffer for invers to speed it up
* samples: add affine bundle adjuster option to stitching_detailed
* add support for using affine bundle adjuster with 4DOF
* improve logging of initial intristics
* sttiching: add affine bundle adjuster test
* fix build warnings
* stitching: increase limit on sanity check
prevents spurious test failures on mac. values are still pretty fine.
* stitching: set affine bundle adjuster for SCANS mode
* fix bug with AffineBestOf2NearestMatcher (we want to select affine partial mode)
* select right bundle adjuster
* stitching: increase error bound for matcher tests
* this prevents failure on mac. tranformation is still ok.
* stitching: implement affine bundle adjuster
* implements affine bundle adjuster that is using full affine transform
* existing test case modified to test both affinePartial an full affine bundle adjuster
* add stitching tutorial
* show basic usage of stitching api (Stitcher class)
* stitching: add more integration test for affine stitching
* added new datasets to existing testcase
* removed unused include
* calib3d: move `haveCollinearPoints` to common header
* added comment to make that this also checks too close points
* calib3d: redone checkSubset for estimateAffine* callback
* use common function to check collinearity
* this also ensures that point will not be too close to each other
* calib3d: change estimateAffine* functions API
* more similar to `findHomography`, `findFundamentalMat`, `findEssentialMat` and similar
* follows standard recommended semantic INPUTS, OUTPUTS, FLAGS
* allows to disable refining
* supported LMEDS robust method (tests yet to come) along with RANSAC
* extended docs with some tips
* calib3d: rewrite estimateAffine2D test
* rewrite in googletest style
* parametrize to test both robust methods (RANSAC and LMEDS)
* get rid of boilerplate
* calib3d: rework estimateAffinePartial2D test
* rework in googletest style
* add testing for LMEDS
* calib3d: rework estimateAffine*2D perf test
* test for LMEDS speed
* test with/without Levenberg-Marquart
* remove sanity checking (this is covered by accuracy tests)
* calib3d: improve estimateAffine*2D tests
* test transformations in loop
* improves test by testing more potential transformations
* calib3d: rewrite kernels for estimateAffine*2D functions
* use analytical solution instead of SVD
* this version is faster especially for smaller amount of points
* calib3d: tune up perf of estimateAffine*2D functions
* avoid copying inliers
* avoid converting input points if not necessary
* check only `from` point for collinearity, as `to` does not affect stability of transform
* tutorials: add commands examples to stitching tutorials
* add some examples how to run stitcher sample code
* mention stitching_detailed.cpp
* calib3d: change computeError for estimateAffine*2D
* do error computing in floats instead of doubles
this have required precision + we were storing the result in float anyway. This make code faster and allows auto-vectorization by smart compilers.
* documentation: mention estimateAffine*2D function
* refer to new functions on appropriate places
* prefer estimateAffine*2D over estimateRigidTransform
* stitching: add camera models documentations
* mention camera models in module documentation to give user a better overview and reduce confusion
2016-10-23 00:10:42 +08:00
|
|
|
@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.
|
|
|
|
@param refineIters Maximum number of iterations of refining algorithm (Levenberg-Marquardt).
|
|
|
|
Passing 0 will disable refining, so the output matrix will be output of robust method.
|
|
|
|
|
|
|
|
@return Output 2D affine transformation matrix \f$2 \times 3\f$ or empty matrix if transformation
|
2018-01-18 19:40:59 +08:00
|
|
|
could not be estimated. The returned matrix has the following form:
|
|
|
|
\f[
|
|
|
|
\begin{bmatrix}
|
|
|
|
a_{11} & a_{12} & b_1\\
|
|
|
|
a_{21} & a_{22} & b_2\\
|
|
|
|
\end{bmatrix}
|
|
|
|
\f]
|
Merge pull request #6933 from hrnr:gsoc_all
[GSOC] New camera model for stitching pipeline
* implement estimateAffine2D
estimates affine transformation using robust RANSAC method.
* uses RANSAC framework in calib3d
* includes accuracy test
* uses SVD decomposition for solving 3 point equation
* implement estimateAffinePartial2D
estimates limited affine transformation
* includes accuracy test
* stitching: add affine matcher
initial version of matcher that estimates affine transformation
* stitching: added affine transform estimator
initial version of estimator that simply chain transformations in homogeneous coordinates
* calib3d: rename estimateAffine3D test
test Calib3d_EstimateAffineTransform rename to Calib3d_EstimateAffine3D. This is more descriptive and prevents confusion with estimateAffine2D tests.
* added perf test for estimateAffine functions
tests both estimateAffine2D and estimateAffinePartial2D
* calib3d: compare error in square in estimateAffine2D
* incorporates fix from #6768
* rerun affine estimation on inliers
* stitching: new API for parallel feature finding
due to ABI breakage new functionality is added to `FeaturesFinder2`, `SurfFeaturesFinder2` and `OrbFeaturesFinder2`
* stitching: add tests for parallel feature find API
* perf test (about linear speed up)
* accuracy test compares results with serial version
* stitching: use dynamic_cast to overcome ABI issues
adding parallel API to FeaturesFinder breaks ABI. This commit uses dynamic_cast and hardcodes thread-safe finders to avoid breaking ABI.
This should be replaced by proper method similar to FeaturesMatcher on next ABI break.
* use estimateAffinePartial2D in AffineBestOf2NearestMatcher
* add constructor to AffineBestOf2NearestMatcher
* allows to choose between full affine transform and partial affine transform. Other params are the as for BestOf2NearestMatcher
* added protected field
* samples: stitching_detailed support affine estimator and matcher
* added new flags to choose matcher and estimator
* stitching: rework affine matcher
represent transformation in homogeneous coordinates
affine matcher: remove duplicite code
rework flow to get rid of duplicite code
affine matcher: do not center points to (0, 0)
it is not needed for affine model. it should not affect estimation in any way.
affine matcher: remove unneeded cv namespacing
* stitching: add stub bundle adjuster
* adds stub bundle adjuster that does nothing
* can be used in place of standard bundle adjusters to omit bundle adjusting step
* samples: stitching detailed, support no budle adjust
* uses new NoBundleAdjuster
* added affine warper
* uses R to get whole affine transformation and propagates rotation and translation to plane warper
* add affine warper factory class
* affine warper: compensate transformation
* samples: stitching_detailed add support for affine warper
* add Stitcher::create method
this method follows similar constructor methods and returns smart pointer. This allows constructing Stitcher according to OpenCV guidelines.
* supports multiple stitcher configurations (PANORAMA and SCANS) for convenient setup
* returns cv::Ptr
* stitcher: dynamicaly determine correct estimator
we need to use affine estimator for affine matcher
* preserves ABI (but add hints for ABI 4)
* uses dynamic_cast hack to inject correct estimator
* sample stitching: add support for multiple modes
shows how to use different configurations of stitcher easily (panorama stitching and scans affine model)
* stitcher: find features in parallel
use new FeatureFinder API to find features in parallel. Parallelized using TBB.
* stitching: disable parallel feature finding for OCL
it does not bring much speedup to run features finder in parallel when OpenCL is enabled, because finder needs to wait for OCL device.
Also, currently ORB is not thread-safe when OCL is enabled.
* stitching: move matcher tests
move matchers tests perf_stich.cpp -> perf_matchers.cpp
* stitching: add affine stiching integration test
test basic affine stitching (SCANS mode of stitcher) with images that have only translation between them
* enable surf for stitching tests
stitching.b12 test was failing with surf
investigated the issue, surf is producing good result. Transformation is only slightly different from ORB, so that resulting pano does not exactly match ORB's result. That caused sanity check to fail.
* added size checks similar to other tests
* sanity check will be applied only for ORB
* stitching: fix wrong estimator choice
if case was exactly wrong, estimators were chosen wrong
added logging for estimated transformation
* enable surf for matchers stitching tests
* enable SURF
* rework sanity checking. Check estimated transform instead of matches. Est. transform should be more stable and comparable between SURF and ORB.
* remove regression checking for VectorFeatures tests. It has a lot if data andtest is the same as previous except it test different vector size for performance, so sanity checking does not add any value here. Added basic sanity asserts instead.
* stitching tests: allow relative error for transform
* allows .01 relative error for estimated homography sanity check in stitching matchers tests
* fix VS warning
stitching tests: increase relative error
increase relative error to make it pass on all platforms (results are still good).
stitching test: allow bigger relative error
transformation can differ in small values (with small absolute difference, but large relative difference). transformation output still looks usable for all platforms. This difference affects only mac and windows, linux passes fine with small difference.
* stitching: add tests for affine matcher
uses s1, s2 images. added also new sanity data.
* stitching tests: use different data for matchers tests
this data should yeild more stable transformation (it has much more matches, especially for surf). Sanity data regenerated.
* stitching test: rework tests for matchers
* separated rotation and translations as they are different by scale.
* use appropriate absolute error for them separately. (relative error does not work for values near zero.)
* stitching: fix affine warper compensation
calculation of rotation and translation extracted for plane warper was wrong
* stitching test: enable surf for opencl integration tests
* enable SURF with correct guard (HAVE_OPENCV_XFEATURES2D)
* add OPENCL guard and correct namespace as usual for opencl tests
* stitching: add ocl accuracy test for affine warper
test consistent results with ocl on and off
* stitching: add affine warper ocl perf test
add affine warper to existing warper perf tests. Added new sanity data.
* stitching: do not overwrite inliers in affine matcher
* estimation is run second time on inliers only, inliers produces in second run will not be therefore correct for all matches
* calib3d: add Levenberg–Marquardt refining to estimateAffine2D* functions
this adds affine Levenberg–Marquardt refining to estimateAffine2D functions similar to what is done in findHomography.
implements Levenberg–Marquardt refinig for both full affine and partial affine transformations.
* stitching: remove reestimation step in affine matcher
reestimation step is not needed. estimateAffine2D* functions are running their own reestimation on inliers using the Levenberg-Marquardt algorithm, which is better than simply rerunning RANSAC on inliers.
* implement partial affine bundle adjuster
bundle adjuster that expect affine transform with 4DOF. Refines parameters for all cameras together.
stitching: fix bug in BundleAdjusterAffinePartial
* use the invers properly
* use static buffer for invers to speed it up
* samples: add affine bundle adjuster option to stitching_detailed
* add support for using affine bundle adjuster with 4DOF
* improve logging of initial intristics
* sttiching: add affine bundle adjuster test
* fix build warnings
* stitching: increase limit on sanity check
prevents spurious test failures on mac. values are still pretty fine.
* stitching: set affine bundle adjuster for SCANS mode
* fix bug with AffineBestOf2NearestMatcher (we want to select affine partial mode)
* select right bundle adjuster
* stitching: increase error bound for matcher tests
* this prevents failure on mac. tranformation is still ok.
* stitching: implement affine bundle adjuster
* implements affine bundle adjuster that is using full affine transform
* existing test case modified to test both affinePartial an full affine bundle adjuster
* add stitching tutorial
* show basic usage of stitching api (Stitcher class)
* stitching: add more integration test for affine stitching
* added new datasets to existing testcase
* removed unused include
* calib3d: move `haveCollinearPoints` to common header
* added comment to make that this also checks too close points
* calib3d: redone checkSubset for estimateAffine* callback
* use common function to check collinearity
* this also ensures that point will not be too close to each other
* calib3d: change estimateAffine* functions API
* more similar to `findHomography`, `findFundamentalMat`, `findEssentialMat` and similar
* follows standard recommended semantic INPUTS, OUTPUTS, FLAGS
* allows to disable refining
* supported LMEDS robust method (tests yet to come) along with RANSAC
* extended docs with some tips
* calib3d: rewrite estimateAffine2D test
* rewrite in googletest style
* parametrize to test both robust methods (RANSAC and LMEDS)
* get rid of boilerplate
* calib3d: rework estimateAffinePartial2D test
* rework in googletest style
* add testing for LMEDS
* calib3d: rework estimateAffine*2D perf test
* test for LMEDS speed
* test with/without Levenberg-Marquart
* remove sanity checking (this is covered by accuracy tests)
* calib3d: improve estimateAffine*2D tests
* test transformations in loop
* improves test by testing more potential transformations
* calib3d: rewrite kernels for estimateAffine*2D functions
* use analytical solution instead of SVD
* this version is faster especially for smaller amount of points
* calib3d: tune up perf of estimateAffine*2D functions
* avoid copying inliers
* avoid converting input points if not necessary
* check only `from` point for collinearity, as `to` does not affect stability of transform
* tutorials: add commands examples to stitching tutorials
* add some examples how to run stitcher sample code
* mention stitching_detailed.cpp
* calib3d: change computeError for estimateAffine*2D
* do error computing in floats instead of doubles
this have required precision + we were storing the result in float anyway. This make code faster and allows auto-vectorization by smart compilers.
* documentation: mention estimateAffine*2D function
* refer to new functions on appropriate places
* prefer estimateAffine*2D over estimateRigidTransform
* stitching: add camera models documentations
* mention camera models in module documentation to give user a better overview and reduce confusion
2016-10-23 00:10:42 +08:00
|
|
|
|
|
|
|
The function estimates an optimal 2D affine transformation between two 2D point sets using the
|
|
|
|
selected robust algorithm.
|
|
|
|
|
|
|
|
The computed transformation is then refined further (using only inliers) with the
|
|
|
|
Levenberg-Marquardt method to reduce the re-projection error even more.
|
|
|
|
|
|
|
|
@note
|
2018-01-18 19:40:59 +08:00
|
|
|
The RANSAC method can handle practically any ratio of outliers but needs a threshold to
|
Merge pull request #6933 from hrnr:gsoc_all
[GSOC] New camera model for stitching pipeline
* implement estimateAffine2D
estimates affine transformation using robust RANSAC method.
* uses RANSAC framework in calib3d
* includes accuracy test
* uses SVD decomposition for solving 3 point equation
* implement estimateAffinePartial2D
estimates limited affine transformation
* includes accuracy test
* stitching: add affine matcher
initial version of matcher that estimates affine transformation
* stitching: added affine transform estimator
initial version of estimator that simply chain transformations in homogeneous coordinates
* calib3d: rename estimateAffine3D test
test Calib3d_EstimateAffineTransform rename to Calib3d_EstimateAffine3D. This is more descriptive and prevents confusion with estimateAffine2D tests.
* added perf test for estimateAffine functions
tests both estimateAffine2D and estimateAffinePartial2D
* calib3d: compare error in square in estimateAffine2D
* incorporates fix from #6768
* rerun affine estimation on inliers
* stitching: new API for parallel feature finding
due to ABI breakage new functionality is added to `FeaturesFinder2`, `SurfFeaturesFinder2` and `OrbFeaturesFinder2`
* stitching: add tests for parallel feature find API
* perf test (about linear speed up)
* accuracy test compares results with serial version
* stitching: use dynamic_cast to overcome ABI issues
adding parallel API to FeaturesFinder breaks ABI. This commit uses dynamic_cast and hardcodes thread-safe finders to avoid breaking ABI.
This should be replaced by proper method similar to FeaturesMatcher on next ABI break.
* use estimateAffinePartial2D in AffineBestOf2NearestMatcher
* add constructor to AffineBestOf2NearestMatcher
* allows to choose between full affine transform and partial affine transform. Other params are the as for BestOf2NearestMatcher
* added protected field
* samples: stitching_detailed support affine estimator and matcher
* added new flags to choose matcher and estimator
* stitching: rework affine matcher
represent transformation in homogeneous coordinates
affine matcher: remove duplicite code
rework flow to get rid of duplicite code
affine matcher: do not center points to (0, 0)
it is not needed for affine model. it should not affect estimation in any way.
affine matcher: remove unneeded cv namespacing
* stitching: add stub bundle adjuster
* adds stub bundle adjuster that does nothing
* can be used in place of standard bundle adjusters to omit bundle adjusting step
* samples: stitching detailed, support no budle adjust
* uses new NoBundleAdjuster
* added affine warper
* uses R to get whole affine transformation and propagates rotation and translation to plane warper
* add affine warper factory class
* affine warper: compensate transformation
* samples: stitching_detailed add support for affine warper
* add Stitcher::create method
this method follows similar constructor methods and returns smart pointer. This allows constructing Stitcher according to OpenCV guidelines.
* supports multiple stitcher configurations (PANORAMA and SCANS) for convenient setup
* returns cv::Ptr
* stitcher: dynamicaly determine correct estimator
we need to use affine estimator for affine matcher
* preserves ABI (but add hints for ABI 4)
* uses dynamic_cast hack to inject correct estimator
* sample stitching: add support for multiple modes
shows how to use different configurations of stitcher easily (panorama stitching and scans affine model)
* stitcher: find features in parallel
use new FeatureFinder API to find features in parallel. Parallelized using TBB.
* stitching: disable parallel feature finding for OCL
it does not bring much speedup to run features finder in parallel when OpenCL is enabled, because finder needs to wait for OCL device.
Also, currently ORB is not thread-safe when OCL is enabled.
* stitching: move matcher tests
move matchers tests perf_stich.cpp -> perf_matchers.cpp
* stitching: add affine stiching integration test
test basic affine stitching (SCANS mode of stitcher) with images that have only translation between them
* enable surf for stitching tests
stitching.b12 test was failing with surf
investigated the issue, surf is producing good result. Transformation is only slightly different from ORB, so that resulting pano does not exactly match ORB's result. That caused sanity check to fail.
* added size checks similar to other tests
* sanity check will be applied only for ORB
* stitching: fix wrong estimator choice
if case was exactly wrong, estimators were chosen wrong
added logging for estimated transformation
* enable surf for matchers stitching tests
* enable SURF
* rework sanity checking. Check estimated transform instead of matches. Est. transform should be more stable and comparable between SURF and ORB.
* remove regression checking for VectorFeatures tests. It has a lot if data andtest is the same as previous except it test different vector size for performance, so sanity checking does not add any value here. Added basic sanity asserts instead.
* stitching tests: allow relative error for transform
* allows .01 relative error for estimated homography sanity check in stitching matchers tests
* fix VS warning
stitching tests: increase relative error
increase relative error to make it pass on all platforms (results are still good).
stitching test: allow bigger relative error
transformation can differ in small values (with small absolute difference, but large relative difference). transformation output still looks usable for all platforms. This difference affects only mac and windows, linux passes fine with small difference.
* stitching: add tests for affine matcher
uses s1, s2 images. added also new sanity data.
* stitching tests: use different data for matchers tests
this data should yeild more stable transformation (it has much more matches, especially for surf). Sanity data regenerated.
* stitching test: rework tests for matchers
* separated rotation and translations as they are different by scale.
* use appropriate absolute error for them separately. (relative error does not work for values near zero.)
* stitching: fix affine warper compensation
calculation of rotation and translation extracted for plane warper was wrong
* stitching test: enable surf for opencl integration tests
* enable SURF with correct guard (HAVE_OPENCV_XFEATURES2D)
* add OPENCL guard and correct namespace as usual for opencl tests
* stitching: add ocl accuracy test for affine warper
test consistent results with ocl on and off
* stitching: add affine warper ocl perf test
add affine warper to existing warper perf tests. Added new sanity data.
* stitching: do not overwrite inliers in affine matcher
* estimation is run second time on inliers only, inliers produces in second run will not be therefore correct for all matches
* calib3d: add Levenberg–Marquardt refining to estimateAffine2D* functions
this adds affine Levenberg–Marquardt refining to estimateAffine2D functions similar to what is done in findHomography.
implements Levenberg–Marquardt refinig for both full affine and partial affine transformations.
* stitching: remove reestimation step in affine matcher
reestimation step is not needed. estimateAffine2D* functions are running their own reestimation on inliers using the Levenberg-Marquardt algorithm, which is better than simply rerunning RANSAC on inliers.
* implement partial affine bundle adjuster
bundle adjuster that expect affine transform with 4DOF. Refines parameters for all cameras together.
stitching: fix bug in BundleAdjusterAffinePartial
* use the invers properly
* use static buffer for invers to speed it up
* samples: add affine bundle adjuster option to stitching_detailed
* add support for using affine bundle adjuster with 4DOF
* improve logging of initial intristics
* sttiching: add affine bundle adjuster test
* fix build warnings
* stitching: increase limit on sanity check
prevents spurious test failures on mac. values are still pretty fine.
* stitching: set affine bundle adjuster for SCANS mode
* fix bug with AffineBestOf2NearestMatcher (we want to select affine partial mode)
* select right bundle adjuster
* stitching: increase error bound for matcher tests
* this prevents failure on mac. tranformation is still ok.
* stitching: implement affine bundle adjuster
* implements affine bundle adjuster that is using full affine transform
* existing test case modified to test both affinePartial an full affine bundle adjuster
* add stitching tutorial
* show basic usage of stitching api (Stitcher class)
* stitching: add more integration test for affine stitching
* added new datasets to existing testcase
* removed unused include
* calib3d: move `haveCollinearPoints` to common header
* added comment to make that this also checks too close points
* calib3d: redone checkSubset for estimateAffine* callback
* use common function to check collinearity
* this also ensures that point will not be too close to each other
* calib3d: change estimateAffine* functions API
* more similar to `findHomography`, `findFundamentalMat`, `findEssentialMat` and similar
* follows standard recommended semantic INPUTS, OUTPUTS, FLAGS
* allows to disable refining
* supported LMEDS robust method (tests yet to come) along with RANSAC
* extended docs with some tips
* calib3d: rewrite estimateAffine2D test
* rewrite in googletest style
* parametrize to test both robust methods (RANSAC and LMEDS)
* get rid of boilerplate
* calib3d: rework estimateAffinePartial2D test
* rework in googletest style
* add testing for LMEDS
* calib3d: rework estimateAffine*2D perf test
* test for LMEDS speed
* test with/without Levenberg-Marquart
* remove sanity checking (this is covered by accuracy tests)
* calib3d: improve estimateAffine*2D tests
* test transformations in loop
* improves test by testing more potential transformations
* calib3d: rewrite kernels for estimateAffine*2D functions
* use analytical solution instead of SVD
* this version is faster especially for smaller amount of points
* calib3d: tune up perf of estimateAffine*2D functions
* avoid copying inliers
* avoid converting input points if not necessary
* check only `from` point for collinearity, as `to` does not affect stability of transform
* tutorials: add commands examples to stitching tutorials
* add some examples how to run stitcher sample code
* mention stitching_detailed.cpp
* calib3d: change computeError for estimateAffine*2D
* do error computing in floats instead of doubles
this have required precision + we were storing the result in float anyway. This make code faster and allows auto-vectorization by smart compilers.
* documentation: mention estimateAffine*2D function
* refer to new functions on appropriate places
* prefer estimateAffine*2D over estimateRigidTransform
* stitching: add camera models documentations
* mention camera models in module documentation to give user a better overview and reduce confusion
2016-10-23 00:10:42 +08:00
|
|
|
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.
|
|
|
|
|
|
|
|
@sa estimateAffinePartial2D, getAffineTransform
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W cv::Mat estimateAffine2D(InputArray from, InputArray to, OutputArray inliers = noArray(),
|
|
|
|
int method = RANSAC, double ransacReprojThreshold = 3,
|
|
|
|
size_t maxIters = 2000, double confidence = 0.99,
|
|
|
|
size_t refineIters = 10);
|
|
|
|
|
|
|
|
/** @brief Computes an optimal limited affine transformation with 4 degrees of freedom between
|
|
|
|
two 2D point sets.
|
|
|
|
|
|
|
|
@param from First input 2D point set.
|
|
|
|
@param to Second input 2D point set.
|
|
|
|
@param inliers Output vector indicating which points are inliers.
|
2017-10-31 00:13:59 +08:00
|
|
|
@param method Robust method used to compute transformation. The following methods are possible:
|
Merge pull request #6933 from hrnr:gsoc_all
[GSOC] New camera model for stitching pipeline
* implement estimateAffine2D
estimates affine transformation using robust RANSAC method.
* uses RANSAC framework in calib3d
* includes accuracy test
* uses SVD decomposition for solving 3 point equation
* implement estimateAffinePartial2D
estimates limited affine transformation
* includes accuracy test
* stitching: add affine matcher
initial version of matcher that estimates affine transformation
* stitching: added affine transform estimator
initial version of estimator that simply chain transformations in homogeneous coordinates
* calib3d: rename estimateAffine3D test
test Calib3d_EstimateAffineTransform rename to Calib3d_EstimateAffine3D. This is more descriptive and prevents confusion with estimateAffine2D tests.
* added perf test for estimateAffine functions
tests both estimateAffine2D and estimateAffinePartial2D
* calib3d: compare error in square in estimateAffine2D
* incorporates fix from #6768
* rerun affine estimation on inliers
* stitching: new API for parallel feature finding
due to ABI breakage new functionality is added to `FeaturesFinder2`, `SurfFeaturesFinder2` and `OrbFeaturesFinder2`
* stitching: add tests for parallel feature find API
* perf test (about linear speed up)
* accuracy test compares results with serial version
* stitching: use dynamic_cast to overcome ABI issues
adding parallel API to FeaturesFinder breaks ABI. This commit uses dynamic_cast and hardcodes thread-safe finders to avoid breaking ABI.
This should be replaced by proper method similar to FeaturesMatcher on next ABI break.
* use estimateAffinePartial2D in AffineBestOf2NearestMatcher
* add constructor to AffineBestOf2NearestMatcher
* allows to choose between full affine transform and partial affine transform. Other params are the as for BestOf2NearestMatcher
* added protected field
* samples: stitching_detailed support affine estimator and matcher
* added new flags to choose matcher and estimator
* stitching: rework affine matcher
represent transformation in homogeneous coordinates
affine matcher: remove duplicite code
rework flow to get rid of duplicite code
affine matcher: do not center points to (0, 0)
it is not needed for affine model. it should not affect estimation in any way.
affine matcher: remove unneeded cv namespacing
* stitching: add stub bundle adjuster
* adds stub bundle adjuster that does nothing
* can be used in place of standard bundle adjusters to omit bundle adjusting step
* samples: stitching detailed, support no budle adjust
* uses new NoBundleAdjuster
* added affine warper
* uses R to get whole affine transformation and propagates rotation and translation to plane warper
* add affine warper factory class
* affine warper: compensate transformation
* samples: stitching_detailed add support for affine warper
* add Stitcher::create method
this method follows similar constructor methods and returns smart pointer. This allows constructing Stitcher according to OpenCV guidelines.
* supports multiple stitcher configurations (PANORAMA and SCANS) for convenient setup
* returns cv::Ptr
* stitcher: dynamicaly determine correct estimator
we need to use affine estimator for affine matcher
* preserves ABI (but add hints for ABI 4)
* uses dynamic_cast hack to inject correct estimator
* sample stitching: add support for multiple modes
shows how to use different configurations of stitcher easily (panorama stitching and scans affine model)
* stitcher: find features in parallel
use new FeatureFinder API to find features in parallel. Parallelized using TBB.
* stitching: disable parallel feature finding for OCL
it does not bring much speedup to run features finder in parallel when OpenCL is enabled, because finder needs to wait for OCL device.
Also, currently ORB is not thread-safe when OCL is enabled.
* stitching: move matcher tests
move matchers tests perf_stich.cpp -> perf_matchers.cpp
* stitching: add affine stiching integration test
test basic affine stitching (SCANS mode of stitcher) with images that have only translation between them
* enable surf for stitching tests
stitching.b12 test was failing with surf
investigated the issue, surf is producing good result. Transformation is only slightly different from ORB, so that resulting pano does not exactly match ORB's result. That caused sanity check to fail.
* added size checks similar to other tests
* sanity check will be applied only for ORB
* stitching: fix wrong estimator choice
if case was exactly wrong, estimators were chosen wrong
added logging for estimated transformation
* enable surf for matchers stitching tests
* enable SURF
* rework sanity checking. Check estimated transform instead of matches. Est. transform should be more stable and comparable between SURF and ORB.
* remove regression checking for VectorFeatures tests. It has a lot if data andtest is the same as previous except it test different vector size for performance, so sanity checking does not add any value here. Added basic sanity asserts instead.
* stitching tests: allow relative error for transform
* allows .01 relative error for estimated homography sanity check in stitching matchers tests
* fix VS warning
stitching tests: increase relative error
increase relative error to make it pass on all platforms (results are still good).
stitching test: allow bigger relative error
transformation can differ in small values (with small absolute difference, but large relative difference). transformation output still looks usable for all platforms. This difference affects only mac and windows, linux passes fine with small difference.
* stitching: add tests for affine matcher
uses s1, s2 images. added also new sanity data.
* stitching tests: use different data for matchers tests
this data should yeild more stable transformation (it has much more matches, especially for surf). Sanity data regenerated.
* stitching test: rework tests for matchers
* separated rotation and translations as they are different by scale.
* use appropriate absolute error for them separately. (relative error does not work for values near zero.)
* stitching: fix affine warper compensation
calculation of rotation and translation extracted for plane warper was wrong
* stitching test: enable surf for opencl integration tests
* enable SURF with correct guard (HAVE_OPENCV_XFEATURES2D)
* add OPENCL guard and correct namespace as usual for opencl tests
* stitching: add ocl accuracy test for affine warper
test consistent results with ocl on and off
* stitching: add affine warper ocl perf test
add affine warper to existing warper perf tests. Added new sanity data.
* stitching: do not overwrite inliers in affine matcher
* estimation is run second time on inliers only, inliers produces in second run will not be therefore correct for all matches
* calib3d: add Levenberg–Marquardt refining to estimateAffine2D* functions
this adds affine Levenberg–Marquardt refining to estimateAffine2D functions similar to what is done in findHomography.
implements Levenberg–Marquardt refinig for both full affine and partial affine transformations.
* stitching: remove reestimation step in affine matcher
reestimation step is not needed. estimateAffine2D* functions are running their own reestimation on inliers using the Levenberg-Marquardt algorithm, which is better than simply rerunning RANSAC on inliers.
* implement partial affine bundle adjuster
bundle adjuster that expect affine transform with 4DOF. Refines parameters for all cameras together.
stitching: fix bug in BundleAdjusterAffinePartial
* use the invers properly
* use static buffer for invers to speed it up
* samples: add affine bundle adjuster option to stitching_detailed
* add support for using affine bundle adjuster with 4DOF
* improve logging of initial intristics
* sttiching: add affine bundle adjuster test
* fix build warnings
* stitching: increase limit on sanity check
prevents spurious test failures on mac. values are still pretty fine.
* stitching: set affine bundle adjuster for SCANS mode
* fix bug with AffineBestOf2NearestMatcher (we want to select affine partial mode)
* select right bundle adjuster
* stitching: increase error bound for matcher tests
* this prevents failure on mac. tranformation is still ok.
* stitching: implement affine bundle adjuster
* implements affine bundle adjuster that is using full affine transform
* existing test case modified to test both affinePartial an full affine bundle adjuster
* add stitching tutorial
* show basic usage of stitching api (Stitcher class)
* stitching: add more integration test for affine stitching
* added new datasets to existing testcase
* removed unused include
* calib3d: move `haveCollinearPoints` to common header
* added comment to make that this also checks too close points
* calib3d: redone checkSubset for estimateAffine* callback
* use common function to check collinearity
* this also ensures that point will not be too close to each other
* calib3d: change estimateAffine* functions API
* more similar to `findHomography`, `findFundamentalMat`, `findEssentialMat` and similar
* follows standard recommended semantic INPUTS, OUTPUTS, FLAGS
* allows to disable refining
* supported LMEDS robust method (tests yet to come) along with RANSAC
* extended docs with some tips
* calib3d: rewrite estimateAffine2D test
* rewrite in googletest style
* parametrize to test both robust methods (RANSAC and LMEDS)
* get rid of boilerplate
* calib3d: rework estimateAffinePartial2D test
* rework in googletest style
* add testing for LMEDS
* calib3d: rework estimateAffine*2D perf test
* test for LMEDS speed
* test with/without Levenberg-Marquart
* remove sanity checking (this is covered by accuracy tests)
* calib3d: improve estimateAffine*2D tests
* test transformations in loop
* improves test by testing more potential transformations
* calib3d: rewrite kernels for estimateAffine*2D functions
* use analytical solution instead of SVD
* this version is faster especially for smaller amount of points
* calib3d: tune up perf of estimateAffine*2D functions
* avoid copying inliers
* avoid converting input points if not necessary
* check only `from` point for collinearity, as `to` does not affect stability of transform
* tutorials: add commands examples to stitching tutorials
* add some examples how to run stitcher sample code
* mention stitching_detailed.cpp
* calib3d: change computeError for estimateAffine*2D
* do error computing in floats instead of doubles
this have required precision + we were storing the result in float anyway. This make code faster and allows auto-vectorization by smart compilers.
* documentation: mention estimateAffine*2D function
* refer to new functions on appropriate places
* prefer estimateAffine*2D over estimateRigidTransform
* stitching: add camera models documentations
* mention camera models in module documentation to give user a better overview and reduce confusion
2016-10-23 00:10:42 +08:00
|
|
|
- cv::RANSAC - RANSAC-based robust method
|
|
|
|
- cv::LMEDS - Least-Median robust method
|
|
|
|
RANSAC is the default method.
|
|
|
|
@param ransacReprojThreshold Maximum reprojection error in the RANSAC algorithm to consider
|
|
|
|
a point as an inlier. Applies only to RANSAC.
|
2018-01-18 19:40:59 +08:00
|
|
|
@param maxIters The maximum number of robust method iterations.
|
Merge pull request #6933 from hrnr:gsoc_all
[GSOC] New camera model for stitching pipeline
* implement estimateAffine2D
estimates affine transformation using robust RANSAC method.
* uses RANSAC framework in calib3d
* includes accuracy test
* uses SVD decomposition for solving 3 point equation
* implement estimateAffinePartial2D
estimates limited affine transformation
* includes accuracy test
* stitching: add affine matcher
initial version of matcher that estimates affine transformation
* stitching: added affine transform estimator
initial version of estimator that simply chain transformations in homogeneous coordinates
* calib3d: rename estimateAffine3D test
test Calib3d_EstimateAffineTransform rename to Calib3d_EstimateAffine3D. This is more descriptive and prevents confusion with estimateAffine2D tests.
* added perf test for estimateAffine functions
tests both estimateAffine2D and estimateAffinePartial2D
* calib3d: compare error in square in estimateAffine2D
* incorporates fix from #6768
* rerun affine estimation on inliers
* stitching: new API for parallel feature finding
due to ABI breakage new functionality is added to `FeaturesFinder2`, `SurfFeaturesFinder2` and `OrbFeaturesFinder2`
* stitching: add tests for parallel feature find API
* perf test (about linear speed up)
* accuracy test compares results with serial version
* stitching: use dynamic_cast to overcome ABI issues
adding parallel API to FeaturesFinder breaks ABI. This commit uses dynamic_cast and hardcodes thread-safe finders to avoid breaking ABI.
This should be replaced by proper method similar to FeaturesMatcher on next ABI break.
* use estimateAffinePartial2D in AffineBestOf2NearestMatcher
* add constructor to AffineBestOf2NearestMatcher
* allows to choose between full affine transform and partial affine transform. Other params are the as for BestOf2NearestMatcher
* added protected field
* samples: stitching_detailed support affine estimator and matcher
* added new flags to choose matcher and estimator
* stitching: rework affine matcher
represent transformation in homogeneous coordinates
affine matcher: remove duplicite code
rework flow to get rid of duplicite code
affine matcher: do not center points to (0, 0)
it is not needed for affine model. it should not affect estimation in any way.
affine matcher: remove unneeded cv namespacing
* stitching: add stub bundle adjuster
* adds stub bundle adjuster that does nothing
* can be used in place of standard bundle adjusters to omit bundle adjusting step
* samples: stitching detailed, support no budle adjust
* uses new NoBundleAdjuster
* added affine warper
* uses R to get whole affine transformation and propagates rotation and translation to plane warper
* add affine warper factory class
* affine warper: compensate transformation
* samples: stitching_detailed add support for affine warper
* add Stitcher::create method
this method follows similar constructor methods and returns smart pointer. This allows constructing Stitcher according to OpenCV guidelines.
* supports multiple stitcher configurations (PANORAMA and SCANS) for convenient setup
* returns cv::Ptr
* stitcher: dynamicaly determine correct estimator
we need to use affine estimator for affine matcher
* preserves ABI (but add hints for ABI 4)
* uses dynamic_cast hack to inject correct estimator
* sample stitching: add support for multiple modes
shows how to use different configurations of stitcher easily (panorama stitching and scans affine model)
* stitcher: find features in parallel
use new FeatureFinder API to find features in parallel. Parallelized using TBB.
* stitching: disable parallel feature finding for OCL
it does not bring much speedup to run features finder in parallel when OpenCL is enabled, because finder needs to wait for OCL device.
Also, currently ORB is not thread-safe when OCL is enabled.
* stitching: move matcher tests
move matchers tests perf_stich.cpp -> perf_matchers.cpp
* stitching: add affine stiching integration test
test basic affine stitching (SCANS mode of stitcher) with images that have only translation between them
* enable surf for stitching tests
stitching.b12 test was failing with surf
investigated the issue, surf is producing good result. Transformation is only slightly different from ORB, so that resulting pano does not exactly match ORB's result. That caused sanity check to fail.
* added size checks similar to other tests
* sanity check will be applied only for ORB
* stitching: fix wrong estimator choice
if case was exactly wrong, estimators were chosen wrong
added logging for estimated transformation
* enable surf for matchers stitching tests
* enable SURF
* rework sanity checking. Check estimated transform instead of matches. Est. transform should be more stable and comparable between SURF and ORB.
* remove regression checking for VectorFeatures tests. It has a lot if data andtest is the same as previous except it test different vector size for performance, so sanity checking does not add any value here. Added basic sanity asserts instead.
* stitching tests: allow relative error for transform
* allows .01 relative error for estimated homography sanity check in stitching matchers tests
* fix VS warning
stitching tests: increase relative error
increase relative error to make it pass on all platforms (results are still good).
stitching test: allow bigger relative error
transformation can differ in small values (with small absolute difference, but large relative difference). transformation output still looks usable for all platforms. This difference affects only mac and windows, linux passes fine with small difference.
* stitching: add tests for affine matcher
uses s1, s2 images. added also new sanity data.
* stitching tests: use different data for matchers tests
this data should yeild more stable transformation (it has much more matches, especially for surf). Sanity data regenerated.
* stitching test: rework tests for matchers
* separated rotation and translations as they are different by scale.
* use appropriate absolute error for them separately. (relative error does not work for values near zero.)
* stitching: fix affine warper compensation
calculation of rotation and translation extracted for plane warper was wrong
* stitching test: enable surf for opencl integration tests
* enable SURF with correct guard (HAVE_OPENCV_XFEATURES2D)
* add OPENCL guard and correct namespace as usual for opencl tests
* stitching: add ocl accuracy test for affine warper
test consistent results with ocl on and off
* stitching: add affine warper ocl perf test
add affine warper to existing warper perf tests. Added new sanity data.
* stitching: do not overwrite inliers in affine matcher
* estimation is run second time on inliers only, inliers produces in second run will not be therefore correct for all matches
* calib3d: add Levenberg–Marquardt refining to estimateAffine2D* functions
this adds affine Levenberg–Marquardt refining to estimateAffine2D functions similar to what is done in findHomography.
implements Levenberg–Marquardt refinig for both full affine and partial affine transformations.
* stitching: remove reestimation step in affine matcher
reestimation step is not needed. estimateAffine2D* functions are running their own reestimation on inliers using the Levenberg-Marquardt algorithm, which is better than simply rerunning RANSAC on inliers.
* implement partial affine bundle adjuster
bundle adjuster that expect affine transform with 4DOF. Refines parameters for all cameras together.
stitching: fix bug in BundleAdjusterAffinePartial
* use the invers properly
* use static buffer for invers to speed it up
* samples: add affine bundle adjuster option to stitching_detailed
* add support for using affine bundle adjuster with 4DOF
* improve logging of initial intristics
* sttiching: add affine bundle adjuster test
* fix build warnings
* stitching: increase limit on sanity check
prevents spurious test failures on mac. values are still pretty fine.
* stitching: set affine bundle adjuster for SCANS mode
* fix bug with AffineBestOf2NearestMatcher (we want to select affine partial mode)
* select right bundle adjuster
* stitching: increase error bound for matcher tests
* this prevents failure on mac. tranformation is still ok.
* stitching: implement affine bundle adjuster
* implements affine bundle adjuster that is using full affine transform
* existing test case modified to test both affinePartial an full affine bundle adjuster
* add stitching tutorial
* show basic usage of stitching api (Stitcher class)
* stitching: add more integration test for affine stitching
* added new datasets to existing testcase
* removed unused include
* calib3d: move `haveCollinearPoints` to common header
* added comment to make that this also checks too close points
* calib3d: redone checkSubset for estimateAffine* callback
* use common function to check collinearity
* this also ensures that point will not be too close to each other
* calib3d: change estimateAffine* functions API
* more similar to `findHomography`, `findFundamentalMat`, `findEssentialMat` and similar
* follows standard recommended semantic INPUTS, OUTPUTS, FLAGS
* allows to disable refining
* supported LMEDS robust method (tests yet to come) along with RANSAC
* extended docs with some tips
* calib3d: rewrite estimateAffine2D test
* rewrite in googletest style
* parametrize to test both robust methods (RANSAC and LMEDS)
* get rid of boilerplate
* calib3d: rework estimateAffinePartial2D test
* rework in googletest style
* add testing for LMEDS
* calib3d: rework estimateAffine*2D perf test
* test for LMEDS speed
* test with/without Levenberg-Marquart
* remove sanity checking (this is covered by accuracy tests)
* calib3d: improve estimateAffine*2D tests
* test transformations in loop
* improves test by testing more potential transformations
* calib3d: rewrite kernels for estimateAffine*2D functions
* use analytical solution instead of SVD
* this version is faster especially for smaller amount of points
* calib3d: tune up perf of estimateAffine*2D functions
* avoid copying inliers
* avoid converting input points if not necessary
* check only `from` point for collinearity, as `to` does not affect stability of transform
* tutorials: add commands examples to stitching tutorials
* add some examples how to run stitcher sample code
* mention stitching_detailed.cpp
* calib3d: change computeError for estimateAffine*2D
* do error computing in floats instead of doubles
this have required precision + we were storing the result in float anyway. This make code faster and allows auto-vectorization by smart compilers.
* documentation: mention estimateAffine*2D function
* refer to new functions on appropriate places
* prefer estimateAffine*2D over estimateRigidTransform
* stitching: add camera models documentations
* mention camera models in module documentation to give user a better overview and reduce confusion
2016-10-23 00:10:42 +08:00
|
|
|
@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.
|
|
|
|
@param refineIters Maximum number of iterations of refining algorithm (Levenberg-Marquardt).
|
|
|
|
Passing 0 will disable refining, so the output matrix will be output of robust method.
|
|
|
|
|
|
|
|
@return Output 2D affine transformation (4 degrees of freedom) matrix \f$2 \times 3\f$ or
|
|
|
|
empty matrix if transformation could not be estimated.
|
|
|
|
|
|
|
|
The function estimates an optimal 2D affine transformation with 4 degrees of freedom limited to
|
|
|
|
combinations of translation, rotation, and uniform scaling. Uses the selected algorithm for robust
|
|
|
|
estimation.
|
|
|
|
|
|
|
|
The computed transformation is then refined further (using only inliers) with the
|
|
|
|
Levenberg-Marquardt method to reduce the re-projection error even more.
|
|
|
|
|
|
|
|
Estimated transformation matrix is:
|
2018-01-18 19:40:59 +08:00
|
|
|
\f[ \begin{bmatrix} \cos(\theta) \cdot s & -\sin(\theta) \cdot s & t_x \\
|
|
|
|
\sin(\theta) \cdot s & \cos(\theta) \cdot s & t_y
|
Merge pull request #6933 from hrnr:gsoc_all
[GSOC] New camera model for stitching pipeline
* implement estimateAffine2D
estimates affine transformation using robust RANSAC method.
* uses RANSAC framework in calib3d
* includes accuracy test
* uses SVD decomposition for solving 3 point equation
* implement estimateAffinePartial2D
estimates limited affine transformation
* includes accuracy test
* stitching: add affine matcher
initial version of matcher that estimates affine transformation
* stitching: added affine transform estimator
initial version of estimator that simply chain transformations in homogeneous coordinates
* calib3d: rename estimateAffine3D test
test Calib3d_EstimateAffineTransform rename to Calib3d_EstimateAffine3D. This is more descriptive and prevents confusion with estimateAffine2D tests.
* added perf test for estimateAffine functions
tests both estimateAffine2D and estimateAffinePartial2D
* calib3d: compare error in square in estimateAffine2D
* incorporates fix from #6768
* rerun affine estimation on inliers
* stitching: new API for parallel feature finding
due to ABI breakage new functionality is added to `FeaturesFinder2`, `SurfFeaturesFinder2` and `OrbFeaturesFinder2`
* stitching: add tests for parallel feature find API
* perf test (about linear speed up)
* accuracy test compares results with serial version
* stitching: use dynamic_cast to overcome ABI issues
adding parallel API to FeaturesFinder breaks ABI. This commit uses dynamic_cast and hardcodes thread-safe finders to avoid breaking ABI.
This should be replaced by proper method similar to FeaturesMatcher on next ABI break.
* use estimateAffinePartial2D in AffineBestOf2NearestMatcher
* add constructor to AffineBestOf2NearestMatcher
* allows to choose between full affine transform and partial affine transform. Other params are the as for BestOf2NearestMatcher
* added protected field
* samples: stitching_detailed support affine estimator and matcher
* added new flags to choose matcher and estimator
* stitching: rework affine matcher
represent transformation in homogeneous coordinates
affine matcher: remove duplicite code
rework flow to get rid of duplicite code
affine matcher: do not center points to (0, 0)
it is not needed for affine model. it should not affect estimation in any way.
affine matcher: remove unneeded cv namespacing
* stitching: add stub bundle adjuster
* adds stub bundle adjuster that does nothing
* can be used in place of standard bundle adjusters to omit bundle adjusting step
* samples: stitching detailed, support no budle adjust
* uses new NoBundleAdjuster
* added affine warper
* uses R to get whole affine transformation and propagates rotation and translation to plane warper
* add affine warper factory class
* affine warper: compensate transformation
* samples: stitching_detailed add support for affine warper
* add Stitcher::create method
this method follows similar constructor methods and returns smart pointer. This allows constructing Stitcher according to OpenCV guidelines.
* supports multiple stitcher configurations (PANORAMA and SCANS) for convenient setup
* returns cv::Ptr
* stitcher: dynamicaly determine correct estimator
we need to use affine estimator for affine matcher
* preserves ABI (but add hints for ABI 4)
* uses dynamic_cast hack to inject correct estimator
* sample stitching: add support for multiple modes
shows how to use different configurations of stitcher easily (panorama stitching and scans affine model)
* stitcher: find features in parallel
use new FeatureFinder API to find features in parallel. Parallelized using TBB.
* stitching: disable parallel feature finding for OCL
it does not bring much speedup to run features finder in parallel when OpenCL is enabled, because finder needs to wait for OCL device.
Also, currently ORB is not thread-safe when OCL is enabled.
* stitching: move matcher tests
move matchers tests perf_stich.cpp -> perf_matchers.cpp
* stitching: add affine stiching integration test
test basic affine stitching (SCANS mode of stitcher) with images that have only translation between them
* enable surf for stitching tests
stitching.b12 test was failing with surf
investigated the issue, surf is producing good result. Transformation is only slightly different from ORB, so that resulting pano does not exactly match ORB's result. That caused sanity check to fail.
* added size checks similar to other tests
* sanity check will be applied only for ORB
* stitching: fix wrong estimator choice
if case was exactly wrong, estimators were chosen wrong
added logging for estimated transformation
* enable surf for matchers stitching tests
* enable SURF
* rework sanity checking. Check estimated transform instead of matches. Est. transform should be more stable and comparable between SURF and ORB.
* remove regression checking for VectorFeatures tests. It has a lot if data andtest is the same as previous except it test different vector size for performance, so sanity checking does not add any value here. Added basic sanity asserts instead.
* stitching tests: allow relative error for transform
* allows .01 relative error for estimated homography sanity check in stitching matchers tests
* fix VS warning
stitching tests: increase relative error
increase relative error to make it pass on all platforms (results are still good).
stitching test: allow bigger relative error
transformation can differ in small values (with small absolute difference, but large relative difference). transformation output still looks usable for all platforms. This difference affects only mac and windows, linux passes fine with small difference.
* stitching: add tests for affine matcher
uses s1, s2 images. added also new sanity data.
* stitching tests: use different data for matchers tests
this data should yeild more stable transformation (it has much more matches, especially for surf). Sanity data regenerated.
* stitching test: rework tests for matchers
* separated rotation and translations as they are different by scale.
* use appropriate absolute error for them separately. (relative error does not work for values near zero.)
* stitching: fix affine warper compensation
calculation of rotation and translation extracted for plane warper was wrong
* stitching test: enable surf for opencl integration tests
* enable SURF with correct guard (HAVE_OPENCV_XFEATURES2D)
* add OPENCL guard and correct namespace as usual for opencl tests
* stitching: add ocl accuracy test for affine warper
test consistent results with ocl on and off
* stitching: add affine warper ocl perf test
add affine warper to existing warper perf tests. Added new sanity data.
* stitching: do not overwrite inliers in affine matcher
* estimation is run second time on inliers only, inliers produces in second run will not be therefore correct for all matches
* calib3d: add Levenberg–Marquardt refining to estimateAffine2D* functions
this adds affine Levenberg–Marquardt refining to estimateAffine2D functions similar to what is done in findHomography.
implements Levenberg–Marquardt refinig for both full affine and partial affine transformations.
* stitching: remove reestimation step in affine matcher
reestimation step is not needed. estimateAffine2D* functions are running their own reestimation on inliers using the Levenberg-Marquardt algorithm, which is better than simply rerunning RANSAC on inliers.
* implement partial affine bundle adjuster
bundle adjuster that expect affine transform with 4DOF. Refines parameters for all cameras together.
stitching: fix bug in BundleAdjusterAffinePartial
* use the invers properly
* use static buffer for invers to speed it up
* samples: add affine bundle adjuster option to stitching_detailed
* add support for using affine bundle adjuster with 4DOF
* improve logging of initial intristics
* sttiching: add affine bundle adjuster test
* fix build warnings
* stitching: increase limit on sanity check
prevents spurious test failures on mac. values are still pretty fine.
* stitching: set affine bundle adjuster for SCANS mode
* fix bug with AffineBestOf2NearestMatcher (we want to select affine partial mode)
* select right bundle adjuster
* stitching: increase error bound for matcher tests
* this prevents failure on mac. tranformation is still ok.
* stitching: implement affine bundle adjuster
* implements affine bundle adjuster that is using full affine transform
* existing test case modified to test both affinePartial an full affine bundle adjuster
* add stitching tutorial
* show basic usage of stitching api (Stitcher class)
* stitching: add more integration test for affine stitching
* added new datasets to existing testcase
* removed unused include
* calib3d: move `haveCollinearPoints` to common header
* added comment to make that this also checks too close points
* calib3d: redone checkSubset for estimateAffine* callback
* use common function to check collinearity
* this also ensures that point will not be too close to each other
* calib3d: change estimateAffine* functions API
* more similar to `findHomography`, `findFundamentalMat`, `findEssentialMat` and similar
* follows standard recommended semantic INPUTS, OUTPUTS, FLAGS
* allows to disable refining
* supported LMEDS robust method (tests yet to come) along with RANSAC
* extended docs with some tips
* calib3d: rewrite estimateAffine2D test
* rewrite in googletest style
* parametrize to test both robust methods (RANSAC and LMEDS)
* get rid of boilerplate
* calib3d: rework estimateAffinePartial2D test
* rework in googletest style
* add testing for LMEDS
* calib3d: rework estimateAffine*2D perf test
* test for LMEDS speed
* test with/without Levenberg-Marquart
* remove sanity checking (this is covered by accuracy tests)
* calib3d: improve estimateAffine*2D tests
* test transformations in loop
* improves test by testing more potential transformations
* calib3d: rewrite kernels for estimateAffine*2D functions
* use analytical solution instead of SVD
* this version is faster especially for smaller amount of points
* calib3d: tune up perf of estimateAffine*2D functions
* avoid copying inliers
* avoid converting input points if not necessary
* check only `from` point for collinearity, as `to` does not affect stability of transform
* tutorials: add commands examples to stitching tutorials
* add some examples how to run stitcher sample code
* mention stitching_detailed.cpp
* calib3d: change computeError for estimateAffine*2D
* do error computing in floats instead of doubles
this have required precision + we were storing the result in float anyway. This make code faster and allows auto-vectorization by smart compilers.
* documentation: mention estimateAffine*2D function
* refer to new functions on appropriate places
* prefer estimateAffine*2D over estimateRigidTransform
* stitching: add camera models documentations
* mention camera models in module documentation to give user a better overview and reduce confusion
2016-10-23 00:10:42 +08:00
|
|
|
\end{bmatrix} \f]
|
2018-01-18 19:40:59 +08:00
|
|
|
Where \f$ \theta \f$ is the rotation angle, \f$ s \f$ the scaling factor and \f$ t_x, t_y \f$ are
|
Merge pull request #6933 from hrnr:gsoc_all
[GSOC] New camera model for stitching pipeline
* implement estimateAffine2D
estimates affine transformation using robust RANSAC method.
* uses RANSAC framework in calib3d
* includes accuracy test
* uses SVD decomposition for solving 3 point equation
* implement estimateAffinePartial2D
estimates limited affine transformation
* includes accuracy test
* stitching: add affine matcher
initial version of matcher that estimates affine transformation
* stitching: added affine transform estimator
initial version of estimator that simply chain transformations in homogeneous coordinates
* calib3d: rename estimateAffine3D test
test Calib3d_EstimateAffineTransform rename to Calib3d_EstimateAffine3D. This is more descriptive and prevents confusion with estimateAffine2D tests.
* added perf test for estimateAffine functions
tests both estimateAffine2D and estimateAffinePartial2D
* calib3d: compare error in square in estimateAffine2D
* incorporates fix from #6768
* rerun affine estimation on inliers
* stitching: new API for parallel feature finding
due to ABI breakage new functionality is added to `FeaturesFinder2`, `SurfFeaturesFinder2` and `OrbFeaturesFinder2`
* stitching: add tests for parallel feature find API
* perf test (about linear speed up)
* accuracy test compares results with serial version
* stitching: use dynamic_cast to overcome ABI issues
adding parallel API to FeaturesFinder breaks ABI. This commit uses dynamic_cast and hardcodes thread-safe finders to avoid breaking ABI.
This should be replaced by proper method similar to FeaturesMatcher on next ABI break.
* use estimateAffinePartial2D in AffineBestOf2NearestMatcher
* add constructor to AffineBestOf2NearestMatcher
* allows to choose between full affine transform and partial affine transform. Other params are the as for BestOf2NearestMatcher
* added protected field
* samples: stitching_detailed support affine estimator and matcher
* added new flags to choose matcher and estimator
* stitching: rework affine matcher
represent transformation in homogeneous coordinates
affine matcher: remove duplicite code
rework flow to get rid of duplicite code
affine matcher: do not center points to (0, 0)
it is not needed for affine model. it should not affect estimation in any way.
affine matcher: remove unneeded cv namespacing
* stitching: add stub bundle adjuster
* adds stub bundle adjuster that does nothing
* can be used in place of standard bundle adjusters to omit bundle adjusting step
* samples: stitching detailed, support no budle adjust
* uses new NoBundleAdjuster
* added affine warper
* uses R to get whole affine transformation and propagates rotation and translation to plane warper
* add affine warper factory class
* affine warper: compensate transformation
* samples: stitching_detailed add support for affine warper
* add Stitcher::create method
this method follows similar constructor methods and returns smart pointer. This allows constructing Stitcher according to OpenCV guidelines.
* supports multiple stitcher configurations (PANORAMA and SCANS) for convenient setup
* returns cv::Ptr
* stitcher: dynamicaly determine correct estimator
we need to use affine estimator for affine matcher
* preserves ABI (but add hints for ABI 4)
* uses dynamic_cast hack to inject correct estimator
* sample stitching: add support for multiple modes
shows how to use different configurations of stitcher easily (panorama stitching and scans affine model)
* stitcher: find features in parallel
use new FeatureFinder API to find features in parallel. Parallelized using TBB.
* stitching: disable parallel feature finding for OCL
it does not bring much speedup to run features finder in parallel when OpenCL is enabled, because finder needs to wait for OCL device.
Also, currently ORB is not thread-safe when OCL is enabled.
* stitching: move matcher tests
move matchers tests perf_stich.cpp -> perf_matchers.cpp
* stitching: add affine stiching integration test
test basic affine stitching (SCANS mode of stitcher) with images that have only translation between them
* enable surf for stitching tests
stitching.b12 test was failing with surf
investigated the issue, surf is producing good result. Transformation is only slightly different from ORB, so that resulting pano does not exactly match ORB's result. That caused sanity check to fail.
* added size checks similar to other tests
* sanity check will be applied only for ORB
* stitching: fix wrong estimator choice
if case was exactly wrong, estimators were chosen wrong
added logging for estimated transformation
* enable surf for matchers stitching tests
* enable SURF
* rework sanity checking. Check estimated transform instead of matches. Est. transform should be more stable and comparable between SURF and ORB.
* remove regression checking for VectorFeatures tests. It has a lot if data andtest is the same as previous except it test different vector size for performance, so sanity checking does not add any value here. Added basic sanity asserts instead.
* stitching tests: allow relative error for transform
* allows .01 relative error for estimated homography sanity check in stitching matchers tests
* fix VS warning
stitching tests: increase relative error
increase relative error to make it pass on all platforms (results are still good).
stitching test: allow bigger relative error
transformation can differ in small values (with small absolute difference, but large relative difference). transformation output still looks usable for all platforms. This difference affects only mac and windows, linux passes fine with small difference.
* stitching: add tests for affine matcher
uses s1, s2 images. added also new sanity data.
* stitching tests: use different data for matchers tests
this data should yeild more stable transformation (it has much more matches, especially for surf). Sanity data regenerated.
* stitching test: rework tests for matchers
* separated rotation and translations as they are different by scale.
* use appropriate absolute error for them separately. (relative error does not work for values near zero.)
* stitching: fix affine warper compensation
calculation of rotation and translation extracted for plane warper was wrong
* stitching test: enable surf for opencl integration tests
* enable SURF with correct guard (HAVE_OPENCV_XFEATURES2D)
* add OPENCL guard and correct namespace as usual for opencl tests
* stitching: add ocl accuracy test for affine warper
test consistent results with ocl on and off
* stitching: add affine warper ocl perf test
add affine warper to existing warper perf tests. Added new sanity data.
* stitching: do not overwrite inliers in affine matcher
* estimation is run second time on inliers only, inliers produces in second run will not be therefore correct for all matches
* calib3d: add Levenberg–Marquardt refining to estimateAffine2D* functions
this adds affine Levenberg–Marquardt refining to estimateAffine2D functions similar to what is done in findHomography.
implements Levenberg–Marquardt refinig for both full affine and partial affine transformations.
* stitching: remove reestimation step in affine matcher
reestimation step is not needed. estimateAffine2D* functions are running their own reestimation on inliers using the Levenberg-Marquardt algorithm, which is better than simply rerunning RANSAC on inliers.
* implement partial affine bundle adjuster
bundle adjuster that expect affine transform with 4DOF. Refines parameters for all cameras together.
stitching: fix bug in BundleAdjusterAffinePartial
* use the invers properly
* use static buffer for invers to speed it up
* samples: add affine bundle adjuster option to stitching_detailed
* add support for using affine bundle adjuster with 4DOF
* improve logging of initial intristics
* sttiching: add affine bundle adjuster test
* fix build warnings
* stitching: increase limit on sanity check
prevents spurious test failures on mac. values are still pretty fine.
* stitching: set affine bundle adjuster for SCANS mode
* fix bug with AffineBestOf2NearestMatcher (we want to select affine partial mode)
* select right bundle adjuster
* stitching: increase error bound for matcher tests
* this prevents failure on mac. tranformation is still ok.
* stitching: implement affine bundle adjuster
* implements affine bundle adjuster that is using full affine transform
* existing test case modified to test both affinePartial an full affine bundle adjuster
* add stitching tutorial
* show basic usage of stitching api (Stitcher class)
* stitching: add more integration test for affine stitching
* added new datasets to existing testcase
* removed unused include
* calib3d: move `haveCollinearPoints` to common header
* added comment to make that this also checks too close points
* calib3d: redone checkSubset for estimateAffine* callback
* use common function to check collinearity
* this also ensures that point will not be too close to each other
* calib3d: change estimateAffine* functions API
* more similar to `findHomography`, `findFundamentalMat`, `findEssentialMat` and similar
* follows standard recommended semantic INPUTS, OUTPUTS, FLAGS
* allows to disable refining
* supported LMEDS robust method (tests yet to come) along with RANSAC
* extended docs with some tips
* calib3d: rewrite estimateAffine2D test
* rewrite in googletest style
* parametrize to test both robust methods (RANSAC and LMEDS)
* get rid of boilerplate
* calib3d: rework estimateAffinePartial2D test
* rework in googletest style
* add testing for LMEDS
* calib3d: rework estimateAffine*2D perf test
* test for LMEDS speed
* test with/without Levenberg-Marquart
* remove sanity checking (this is covered by accuracy tests)
* calib3d: improve estimateAffine*2D tests
* test transformations in loop
* improves test by testing more potential transformations
* calib3d: rewrite kernels for estimateAffine*2D functions
* use analytical solution instead of SVD
* this version is faster especially for smaller amount of points
* calib3d: tune up perf of estimateAffine*2D functions
* avoid copying inliers
* avoid converting input points if not necessary
* check only `from` point for collinearity, as `to` does not affect stability of transform
* tutorials: add commands examples to stitching tutorials
* add some examples how to run stitcher sample code
* mention stitching_detailed.cpp
* calib3d: change computeError for estimateAffine*2D
* do error computing in floats instead of doubles
this have required precision + we were storing the result in float anyway. This make code faster and allows auto-vectorization by smart compilers.
* documentation: mention estimateAffine*2D function
* refer to new functions on appropriate places
* prefer estimateAffine*2D over estimateRigidTransform
* stitching: add camera models documentations
* mention camera models in module documentation to give user a better overview and reduce confusion
2016-10-23 00:10:42 +08:00
|
|
|
translations in \f$ x, y \f$ axes respectively.
|
|
|
|
|
|
|
|
@note
|
|
|
|
The RANSAC method can handle practically any ratio of outliers but need 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.
|
|
|
|
|
|
|
|
@sa estimateAffine2D, getAffineTransform
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W cv::Mat estimateAffinePartial2D(InputArray from, InputArray to, OutputArray inliers = noArray(),
|
|
|
|
int method = RANSAC, double ransacReprojThreshold = 3,
|
|
|
|
size_t maxIters = 2000, double confidence = 0.99,
|
|
|
|
size_t refineIters = 10);
|
|
|
|
|
2018-08-03 02:22:58 +08:00
|
|
|
/** @example samples/cpp/tutorial_code/features2D/Homography/decompose_homography.cpp
|
|
|
|
An example program with homography decomposition.
|
2017-12-20 05:45:35 +08:00
|
|
|
|
2018-08-03 02:22:58 +08:00
|
|
|
Check @ref tutorial_homography "the corresponding tutorial" for more details.
|
|
|
|
*/
|
2017-12-20 05:45:35 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Decompose a homography matrix to rotation(s), translation(s) and plane normal(s).
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
@param H The input homography matrix between two images.
|
|
|
|
@param K The input intrinsic camera calibration matrix.
|
|
|
|
@param rotations Array of rotation matrices.
|
|
|
|
@param translations Array of translation matrices.
|
|
|
|
@param normals Array of plane normal matrices.
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
This function extracts relative camera motion between two views observing a planar object from the
|
|
|
|
homography H induced by the plane. The intrinsic camera matrix K must also be provided. The function
|
|
|
|
may return up to four mathematical solution sets. At least two of the solutions may further be
|
|
|
|
invalidated if point correspondences are available by applying positive depth constraint (all points
|
2014-11-26 19:21:08 +08:00
|
|
|
must be in front of the camera). The decomposition method is described in detail in @cite Malis .
|
2014-11-19 21:13:41 +08:00
|
|
|
*/
|
2014-04-28 01:02:36 +08:00
|
|
|
CV_EXPORTS_W int decomposeHomographyMat(InputArray H,
|
|
|
|
InputArray K,
|
|
|
|
OutputArrayOfArrays rotations,
|
|
|
|
OutputArrayOfArrays translations,
|
|
|
|
OutputArrayOfArrays normals);
|
2013-03-25 03:09:17 +08:00
|
|
|
|
2018-06-27 21:47:35 +08:00
|
|
|
/** @brief Filters homography decompositions based on additional information.
|
|
|
|
|
|
|
|
@param rotations Vector of rotation matrices.
|
|
|
|
@param normals Vector of plane normal matrices.
|
|
|
|
@param beforePoints Vector of (rectified) visible reference points before the homography is applied
|
|
|
|
@param afterPoints Vector of (rectified) visible reference points after the homography is applied
|
|
|
|
@param possibleSolutions Vector of int indices representing the viable solution set after filtering
|
|
|
|
@param pointsMask optional Mat/Vector of 8u type representing the mask for the inliers as given by the findHomography function
|
|
|
|
|
|
|
|
This function is intended to filter the output of the decomposeHomographyMat based on additional
|
|
|
|
information as described in @cite Malis . The summary of the method: the decomposeHomographyMat function
|
|
|
|
returns 2 unique solutions and their "opposites" for a total of 4 solutions. If we have access to the
|
|
|
|
sets of points visible in the camera frame before and after the homography transformation is applied,
|
|
|
|
we can determine which are the true potential solutions and which are the opposites by verifying which
|
|
|
|
homographies are consistent with all visible reference points being in front of the camera. The inputs
|
|
|
|
are left unchanged; the filtered solution set is returned as indices into the existing one.
|
|
|
|
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W void filterHomographyDecompByVisibleRefpoints(InputArrayOfArrays rotations,
|
|
|
|
InputArrayOfArrays normals,
|
|
|
|
InputArray beforePoints,
|
|
|
|
InputArray afterPoints,
|
|
|
|
OutputArray possibleSolutions,
|
|
|
|
InputArray pointsMask = noArray());
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief The base class for stereo correspondence algorithms.
|
|
|
|
*/
|
2013-03-01 06:24:46 +08:00
|
|
|
class CV_EXPORTS_W StereoMatcher : public Algorithm
|
|
|
|
{
|
|
|
|
public:
|
2013-04-11 23:27:54 +08:00
|
|
|
enum { DISP_SHIFT = 4,
|
|
|
|
DISP_SCALE = (1 << DISP_SHIFT)
|
|
|
|
};
|
2013-03-22 05:05:30 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Computes disparity map for the specified stereo pair
|
|
|
|
|
|
|
|
@param left Left 8-bit single-channel image.
|
|
|
|
@param right Right image of the same size and the same type as the left one.
|
|
|
|
@param disparity Output disparity map. It has the same size as the input images. Some algorithms,
|
|
|
|
like StereoBM or StereoSGBM compute 16-bit fixed-point disparity map (where each disparity value
|
|
|
|
has 4 fractional bits), whereas other algorithms output 32-bit floating-point disparity map.
|
|
|
|
*/
|
2013-03-01 06:24:46 +08:00
|
|
|
CV_WRAP virtual void compute( InputArray left, InputArray right,
|
|
|
|
OutputArray disparity ) = 0;
|
2012-05-28 15:36:14 +08:00
|
|
|
|
2013-03-22 05:05:30 +08:00
|
|
|
CV_WRAP virtual int getMinDisparity() const = 0;
|
|
|
|
CV_WRAP virtual void setMinDisparity(int minDisparity) = 0;
|
2013-03-01 06:24:46 +08:00
|
|
|
|
2013-03-22 05:05:30 +08:00
|
|
|
CV_WRAP virtual int getNumDisparities() const = 0;
|
|
|
|
CV_WRAP virtual void setNumDisparities(int numDisparities) = 0;
|
2013-03-13 20:22:44 +08:00
|
|
|
|
2013-03-22 05:05:30 +08:00
|
|
|
CV_WRAP virtual int getBlockSize() const = 0;
|
|
|
|
CV_WRAP virtual void setBlockSize(int blockSize) = 0;
|
2013-03-01 06:24:46 +08:00
|
|
|
|
2013-03-22 05:05:30 +08:00
|
|
|
CV_WRAP virtual int getSpeckleWindowSize() const = 0;
|
|
|
|
CV_WRAP virtual void setSpeckleWindowSize(int speckleWindowSize) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual int getSpeckleRange() const = 0;
|
|
|
|
CV_WRAP virtual void setSpeckleRange(int speckleRange) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual int getDisp12MaxDiff() const = 0;
|
|
|
|
CV_WRAP virtual void setDisp12MaxDiff(int disp12MaxDiff) = 0;
|
|
|
|
};
|
2013-03-01 06:24:46 +08:00
|
|
|
|
2013-03-25 03:09:17 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Class for computing stereo correspondence using the block matching algorithm, introduced and
|
|
|
|
contributed to OpenCV by K. Konolige.
|
|
|
|
*/
|
2013-03-22 05:05:30 +08:00
|
|
|
class CV_EXPORTS_W StereoBM : public StereoMatcher
|
2010-05-12 01:44:00 +08:00
|
|
|
{
|
|
|
|
public:
|
2013-04-11 23:27:54 +08:00
|
|
|
enum { PREFILTER_NORMALIZED_RESPONSE = 0,
|
|
|
|
PREFILTER_XSOBEL = 1
|
|
|
|
};
|
2013-03-22 05:05:30 +08:00
|
|
|
|
|
|
|
CV_WRAP virtual int getPreFilterType() const = 0;
|
|
|
|
CV_WRAP virtual void setPreFilterType(int preFilterType) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual int getPreFilterSize() const = 0;
|
|
|
|
CV_WRAP virtual void setPreFilterSize(int preFilterSize) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual int getPreFilterCap() const = 0;
|
|
|
|
CV_WRAP virtual void setPreFilterCap(int preFilterCap) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual int getTextureThreshold() const = 0;
|
|
|
|
CV_WRAP virtual void setTextureThreshold(int textureThreshold) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual int getUniquenessRatio() const = 0;
|
|
|
|
CV_WRAP virtual void setUniquenessRatio(int uniquenessRatio) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual int getSmallerBlockSize() const = 0;
|
|
|
|
CV_WRAP virtual void setSmallerBlockSize(int blockSize) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual Rect getROI1() const = 0;
|
|
|
|
CV_WRAP virtual void setROI1(Rect roi1) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual Rect getROI2() const = 0;
|
|
|
|
CV_WRAP virtual void setROI2(Rect roi2) = 0;
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Creates StereoBM object
|
|
|
|
|
|
|
|
@param numDisparities the disparity search range. For each pixel algorithm will find the best
|
|
|
|
disparity from 0 (default minimum disparity) to numDisparities. The search range can then be
|
|
|
|
shifted by changing the minimum disparity.
|
|
|
|
@param blockSize 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 function create StereoBM object. You can then call StereoBM::compute() to compute disparity for
|
|
|
|
a specific stereo pair.
|
|
|
|
*/
|
2014-10-19 00:44:26 +08:00
|
|
|
CV_WRAP static Ptr<StereoBM> create(int numDisparities = 0, int blockSize = 21);
|
|
|
|
};
|
2010-05-12 01:44:00 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief The class implements the modified H. Hirschmuller algorithm @cite HH08 that differs from the original
|
|
|
|
one as follows:
|
|
|
|
|
|
|
|
- By default, the algorithm is single-pass, which means that you consider only 5 directions
|
2014-11-21 16:28:14 +08:00
|
|
|
instead of 8. Set mode=StereoSGBM::MODE_HH in createStereoSGBM to run the full variant of the
|
2014-11-19 21:13:41 +08:00
|
|
|
algorithm but beware that it may consume a lot of memory.
|
|
|
|
- The algorithm matches blocks, not individual pixels. Though, setting blockSize=1 reduces the
|
|
|
|
blocks to single pixels.
|
|
|
|
- Mutual information cost function is not implemented. Instead, a simpler Birchfield-Tomasi
|
|
|
|
sub-pixel metric from @cite BT98 is used. Though, the color images are supported as well.
|
|
|
|
- Some pre- and post- processing steps from K. Konolige algorithm StereoBM are included, for
|
2014-11-21 16:28:14 +08:00
|
|
|
example: pre-filtering (StereoBM::PREFILTER_XSOBEL type) and post-filtering (uniqueness
|
2014-11-19 21:13:41 +08:00
|
|
|
check, quadratic interpolation and speckle filtering).
|
|
|
|
|
|
|
|
@note
|
|
|
|
- (Python) An example illustrating the use of the StereoSGBM matching algorithm can be found
|
2015-12-16 21:36:03 +08:00
|
|
|
at opencv_source_code/samples/python/stereo_match.py
|
2014-11-19 21:13:41 +08:00
|
|
|
*/
|
2013-03-22 05:05:30 +08:00
|
|
|
class CV_EXPORTS_W StereoSGBM : public StereoMatcher
|
2010-05-12 01:44:00 +08:00
|
|
|
{
|
|
|
|
public:
|
2014-10-19 00:44:26 +08:00
|
|
|
enum
|
|
|
|
{
|
|
|
|
MODE_SGBM = 0,
|
2015-07-08 04:23:51 +08:00
|
|
|
MODE_HH = 1,
|
2017-03-21 22:51:19 +08:00
|
|
|
MODE_SGBM_3WAY = 2,
|
2017-04-22 08:00:08 +08:00
|
|
|
MODE_HH4 = 3
|
2014-10-19 00:44:26 +08:00
|
|
|
};
|
2013-03-22 05:05:30 +08:00
|
|
|
|
|
|
|
CV_WRAP virtual int getPreFilterCap() const = 0;
|
|
|
|
CV_WRAP virtual void setPreFilterCap(int preFilterCap) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual int getUniquenessRatio() const = 0;
|
|
|
|
CV_WRAP virtual void setUniquenessRatio(int uniquenessRatio) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual int getP1() const = 0;
|
|
|
|
CV_WRAP virtual void setP1(int P1) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual int getP2() const = 0;
|
|
|
|
CV_WRAP virtual void setP2(int P2) = 0;
|
|
|
|
|
|
|
|
CV_WRAP virtual int getMode() const = 0;
|
|
|
|
CV_WRAP virtual void setMode(int mode) = 0;
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Creates StereoSGBM object
|
|
|
|
|
|
|
|
@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.
|
|
|
|
@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.
|
|
|
|
@param blockSize 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
|
2014-11-21 16:28:14 +08:00
|
|
|
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).
|
2014-11-19 21:13:41 +08: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.
|
|
|
|
@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.
|
|
|
|
@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.
|
|
|
|
@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.
|
|
|
|
@param speckleRange Maximum disparity variation within each connected component. If you do speckle
|
|
|
|
filtering, set the parameter to a positive value, it will be implicitly multiplied by 16.
|
|
|
|
Normally, 1 or 2 is good enough.
|
2014-11-21 16:28:14 +08:00
|
|
|
@param mode Set it to StereoSGBM::MODE_HH to run the full-scale two-pass dynamic programming
|
2014-11-19 21:13:41 +08:00
|
|
|
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 .
|
|
|
|
|
|
|
|
The first constructor initializes StereoSGBM with all the default parameters. So, you only have to
|
|
|
|
set StereoSGBM::numDisparities at minimum. The second constructor enables you to set each parameter
|
|
|
|
to a custom value.
|
|
|
|
*/
|
2017-04-30 03:38:06 +08:00
|
|
|
CV_WRAP static Ptr<StereoSGBM> create(int minDisparity = 0, int numDisparities = 16, int blockSize = 3,
|
2014-10-19 00:44:26 +08:00
|
|
|
int P1 = 0, int P2 = 0, int disp12MaxDiff = 0,
|
|
|
|
int preFilterCap = 0, int uniquenessRatio = 0,
|
|
|
|
int speckleWindowSize = 0, int speckleRange = 0,
|
|
|
|
int mode = StereoSGBM::MODE_SGBM);
|
|
|
|
};
|
2013-03-22 05:05:30 +08:00
|
|
|
|
2018-10-03 05:51:29 +08:00
|
|
|
|
|
|
|
//! cv::undistort mode
|
|
|
|
enum UndistortTypes
|
|
|
|
{
|
|
|
|
PROJ_SPHERICAL_ORTHO = 0,
|
|
|
|
PROJ_SPHERICAL_EQRECT = 1
|
|
|
|
};
|
|
|
|
|
|
|
|
/** @brief Transforms an image to compensate for lens distortion.
|
|
|
|
|
|
|
|
The function transforms an image to compensate radial and tangential lens distortion.
|
|
|
|
|
|
|
|
The function is simply a combination of #initUndistortRectifyMap (with unity R ) and #remap
|
|
|
|
(with bilinear interpolation). See the former function for details of the transformation being
|
|
|
|
performed.
|
|
|
|
|
|
|
|
Those pixels in the destination image, for which there is no correspondent pixels in the source
|
|
|
|
image, are filled with zeros (black color).
|
|
|
|
|
|
|
|
A particular subset of the source image that will be visible in the corrected image can be regulated
|
|
|
|
by newCameraMatrix. You can use #getOptimalNewCameraMatrix to compute the appropriate
|
|
|
|
newCameraMatrix depending on your requirements.
|
|
|
|
|
|
|
|
The camera matrix and the distortion parameters can be determined using #calibrateCamera. If
|
|
|
|
the resolution of images is different from the resolution used at the calibration stage, \f$f_x,
|
|
|
|
f_y, c_x\f$ and \f$c_y\f$ need to be scaled accordingly, while the distortion coefficients remain
|
|
|
|
the same.
|
|
|
|
|
|
|
|
@param src Input (distorted) image.
|
|
|
|
@param dst Output (corrected) image that has the same size and type as src .
|
|
|
|
@param cameraMatrix Input camera matrix \f$A = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}\f$ .
|
|
|
|
@param distCoeffs Input vector of distortion coefficients
|
|
|
|
\f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6[, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$
|
|
|
|
of 4, 5, 8, 12 or 14 elements. If the vector is NULL/empty, the zero distortion coefficients are assumed.
|
|
|
|
@param newCameraMatrix Camera matrix of the distorted image. By default, it is the same as
|
|
|
|
cameraMatrix but you may additionally scale and shift the result by using a different matrix.
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W void undistort( InputArray src, OutputArray dst,
|
|
|
|
InputArray cameraMatrix,
|
|
|
|
InputArray distCoeffs,
|
|
|
|
InputArray newCameraMatrix = noArray() );
|
|
|
|
|
|
|
|
/** @brief Computes the undistortion and rectification transformation map.
|
|
|
|
|
|
|
|
The function computes the joint undistortion and rectification transformation and represents the
|
|
|
|
result in the form of maps for remap. The undistorted image looks like original, as if it is
|
|
|
|
captured with a camera using the camera matrix =newCameraMatrix and zero distortion. In case of a
|
|
|
|
monocular camera, newCameraMatrix is usually equal to cameraMatrix, or it can be computed by
|
|
|
|
#getOptimalNewCameraMatrix for a better control over scaling. In case of a stereo camera,
|
|
|
|
newCameraMatrix is normally set to P1 or P2 computed by #stereoRectify .
|
|
|
|
|
|
|
|
Also, this new camera is oriented differently in the coordinate space, according to R. That, for
|
|
|
|
example, helps to align two heads of a stereo camera so that the epipolar lines on both images
|
|
|
|
become horizontal and have the same y- coordinate (in case of a horizontally aligned stereo camera).
|
|
|
|
|
|
|
|
The function actually builds the maps for the inverse mapping algorithm that is used by remap. That
|
|
|
|
is, for each pixel \f$(u, v)\f$ in the destination (corrected and rectified) image, the function
|
|
|
|
computes the corresponding coordinates in the source image (that is, in the original image from
|
|
|
|
camera). The following process is applied:
|
|
|
|
\f[
|
|
|
|
\begin{array}{l}
|
|
|
|
x \leftarrow (u - {c'}_x)/{f'}_x \\
|
|
|
|
y \leftarrow (v - {c'}_y)/{f'}_y \\
|
|
|
|
{[X\,Y\,W]} ^T \leftarrow R^{-1}*[x \, y \, 1]^T \\
|
|
|
|
x' \leftarrow X/W \\
|
|
|
|
y' \leftarrow Y/W \\
|
|
|
|
r^2 \leftarrow x'^2 + y'^2 \\
|
|
|
|
x'' \leftarrow 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}
|
|
|
|
+ 2p_1 x' y' + p_2(r^2 + 2 x'^2) + s_1 r^2 + s_2 r^4\\
|
|
|
|
y'' \leftarrow 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' + s_3 r^2 + s_4 r^4 \\
|
|
|
|
s\vecthree{x'''}{y'''}{1} =
|
|
|
|
\vecthreethree{R_{33}(\tau_x, \tau_y)}{0}{-R_{13}((\tau_x, \tau_y)}
|
|
|
|
{0}{R_{33}(\tau_x, \tau_y)}{-R_{23}(\tau_x, \tau_y)}
|
|
|
|
{0}{0}{1} R(\tau_x, \tau_y) \vecthree{x''}{y''}{1}\\
|
|
|
|
map_x(u,v) \leftarrow x''' f_x + c_x \\
|
|
|
|
map_y(u,v) \leftarrow y''' f_y + c_y
|
|
|
|
\end{array}
|
|
|
|
\f]
|
|
|
|
where \f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6[, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$
|
|
|
|
are the distortion coefficients.
|
|
|
|
|
|
|
|
In case of a stereo camera, this function is called twice: once for each camera head, after
|
|
|
|
stereoRectify, which in its turn is called after #stereoCalibrate. But if the stereo camera
|
|
|
|
was not calibrated, it is still possible to compute the rectification transformations directly from
|
|
|
|
the fundamental matrix using #stereoRectifyUncalibrated. For each camera, the function computes
|
|
|
|
homography H as the rectification transformation in a pixel domain, not a rotation matrix R in 3D
|
|
|
|
space. R can be computed from H as
|
|
|
|
\f[\texttt{R} = \texttt{cameraMatrix} ^{-1} \cdot \texttt{H} \cdot \texttt{cameraMatrix}\f]
|
|
|
|
where cameraMatrix can be chosen arbitrarily.
|
|
|
|
|
|
|
|
@param cameraMatrix Input camera matrix \f$A=\vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}\f$ .
|
|
|
|
@param distCoeffs Input vector of distortion coefficients
|
|
|
|
\f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6[, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$
|
|
|
|
of 4, 5, 8, 12 or 14 elements. If the vector is NULL/empty, the zero distortion coefficients are assumed.
|
|
|
|
@param R Optional rectification transformation in the object space (3x3 matrix). R1 or R2 ,
|
|
|
|
computed by #stereoRectify can be passed here. If the matrix is empty, the identity transformation
|
|
|
|
is assumed. In cvInitUndistortMap R assumed to be an identity matrix.
|
|
|
|
@param newCameraMatrix New camera matrix \f$A'=\vecthreethree{f_x'}{0}{c_x'}{0}{f_y'}{c_y'}{0}{0}{1}\f$.
|
|
|
|
@param size Undistorted image size.
|
|
|
|
@param m1type Type of the first output map that can be CV_32FC1, CV_32FC2 or CV_16SC2, see #convertMaps
|
|
|
|
@param map1 The first output map.
|
|
|
|
@param map2 The second output map.
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W
|
|
|
|
void initUndistortRectifyMap(InputArray cameraMatrix, InputArray distCoeffs,
|
|
|
|
InputArray R, InputArray newCameraMatrix,
|
|
|
|
Size size, int m1type, OutputArray map1, OutputArray map2);
|
|
|
|
|
|
|
|
//! initializes maps for #remap for wide-angle
|
|
|
|
CV_EXPORTS
|
|
|
|
float initWideAngleProjMap(InputArray cameraMatrix, InputArray distCoeffs,
|
|
|
|
Size imageSize, int destImageWidth,
|
|
|
|
int m1type, OutputArray map1, OutputArray map2,
|
|
|
|
enum UndistortTypes projType = PROJ_SPHERICAL_EQRECT, double alpha = 0);
|
|
|
|
static inline
|
|
|
|
float initWideAngleProjMap(InputArray cameraMatrix, InputArray distCoeffs,
|
|
|
|
Size imageSize, int destImageWidth,
|
|
|
|
int m1type, OutputArray map1, OutputArray map2,
|
|
|
|
int projType, double alpha = 0)
|
|
|
|
{
|
|
|
|
return initWideAngleProjMap(cameraMatrix, distCoeffs, imageSize, destImageWidth,
|
|
|
|
m1type, map1, map2, (UndistortTypes)projType, alpha);
|
|
|
|
}
|
|
|
|
|
|
|
|
/** @brief Returns the default new camera matrix.
|
|
|
|
|
|
|
|
The function returns the camera matrix that is either an exact copy of the input cameraMatrix (when
|
|
|
|
centerPrinicipalPoint=false ), or the modified one (when centerPrincipalPoint=true).
|
|
|
|
|
|
|
|
In the latter case, the new camera matrix will be:
|
|
|
|
|
|
|
|
\f[\begin{bmatrix} f_x && 0 && ( \texttt{imgSize.width} -1)*0.5 \\ 0 && f_y && ( \texttt{imgSize.height} -1)*0.5 \\ 0 && 0 && 1 \end{bmatrix} ,\f]
|
|
|
|
|
|
|
|
where \f$f_x\f$ and \f$f_y\f$ are \f$(0,0)\f$ and \f$(1,1)\f$ elements of cameraMatrix, respectively.
|
|
|
|
|
|
|
|
By default, the undistortion functions in OpenCV (see #initUndistortRectifyMap, #undistort) do not
|
|
|
|
move the principal point. However, when you work with stereo, it is important to move the principal
|
|
|
|
points in both views to the same y-coordinate (which is required by most of stereo correspondence
|
|
|
|
algorithms), and may be to the same x-coordinate too. So, you can form the new camera matrix for
|
|
|
|
each view where the principal points are located at the center.
|
|
|
|
|
|
|
|
@param cameraMatrix Input camera matrix.
|
|
|
|
@param imgsize Camera view image size in pixels.
|
|
|
|
@param centerPrincipalPoint Location of the principal point in the new camera matrix. The
|
|
|
|
parameter indicates whether this location should be at the image center or not.
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W
|
|
|
|
Mat getDefaultNewCameraMatrix(InputArray cameraMatrix, Size imgsize = Size(),
|
|
|
|
bool centerPrincipalPoint = false);
|
|
|
|
|
|
|
|
/** @brief Computes the ideal point coordinates from the observed point coordinates.
|
|
|
|
|
|
|
|
The function is similar to #undistort and #initUndistortRectifyMap but it operates on a
|
|
|
|
sparse set of points instead of a raster image. Also the function performs a reverse transformation
|
|
|
|
to projectPoints. In case of a 3D object, it does not reconstruct its 3D coordinates, but for a
|
|
|
|
planar object, it does, up to a translation vector, if the proper R is specified.
|
|
|
|
|
|
|
|
For each observed point coordinate \f$(u, v)\f$ the function computes:
|
|
|
|
\f[
|
|
|
|
\begin{array}{l}
|
|
|
|
x^{"} \leftarrow (u - c_x)/f_x \\
|
|
|
|
y^{"} \leftarrow (v - c_y)/f_y \\
|
|
|
|
(x',y') = undistort(x^{"},y^{"}, \texttt{distCoeffs}) \\
|
|
|
|
{[X\,Y\,W]} ^T \leftarrow R*[x' \, y' \, 1]^T \\
|
|
|
|
x \leftarrow X/W \\
|
|
|
|
y \leftarrow Y/W \\
|
|
|
|
\text{only performed if P is specified:} \\
|
|
|
|
u' \leftarrow x {f'}_x + {c'}_x \\
|
|
|
|
v' \leftarrow y {f'}_y + {c'}_y
|
|
|
|
\end{array}
|
|
|
|
\f]
|
|
|
|
|
|
|
|
where *undistort* is an approximate iterative algorithm that estimates the normalized original
|
|
|
|
point coordinates out of the normalized distorted point coordinates ("normalized" means that the
|
|
|
|
coordinates do not depend on the camera matrix).
|
|
|
|
|
|
|
|
The function can be used for both a stereo camera head or a monocular camera (when R is empty).
|
|
|
|
|
|
|
|
@param src Observed point coordinates, 1xN or Nx1 2-channel (CV_32FC2 or CV_64FC2).
|
|
|
|
@param dst Output ideal point coordinates after undistortion and reverse perspective
|
|
|
|
transformation. If matrix P is identity or omitted, dst will contain normalized point coordinates.
|
|
|
|
@param cameraMatrix Camera matrix \f$\vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}\f$ .
|
|
|
|
@param distCoeffs Input vector of distortion coefficients
|
|
|
|
\f$(k_1, k_2, p_1, p_2[, k_3[, k_4, k_5, k_6[, s_1, s_2, s_3, s_4[, \tau_x, \tau_y]]]])\f$
|
|
|
|
of 4, 5, 8, 12 or 14 elements. If the vector is NULL/empty, the zero distortion coefficients are assumed.
|
|
|
|
@param R Rectification transformation in the object space (3x3 matrix). R1 or R2 computed by
|
|
|
|
#stereoRectify can be passed here. If the matrix is empty, the identity transformation is used.
|
|
|
|
@param P New camera matrix (3x3) or new projection matrix (3x4) \f$\begin{bmatrix} {f'}_x & 0 & {c'}_x & t_x \\ 0 & {f'}_y & {c'}_y & t_y \\ 0 & 0 & 1 & t_z \end{bmatrix}\f$. P1 or P2 computed by
|
|
|
|
#stereoRectify can be passed here. If the matrix is empty, the identity new camera matrix is used.
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_W
|
|
|
|
void undistortPoints(InputArray src, OutputArray dst,
|
|
|
|
InputArray cameraMatrix, InputArray distCoeffs,
|
|
|
|
InputArray R = noArray(), InputArray P = noArray());
|
|
|
|
/** @overload
|
|
|
|
@note Default version of #undistortPoints does 5 iterations to compute undistorted points.
|
|
|
|
*/
|
|
|
|
CV_EXPORTS_AS(undistortPointsIter)
|
|
|
|
void undistortPoints(InputArray src, OutputArray dst,
|
|
|
|
InputArray cameraMatrix, InputArray distCoeffs,
|
|
|
|
InputArray R, InputArray P, TermCriteria criteria);
|
|
|
|
|
2014-11-26 19:21:08 +08:00
|
|
|
//! @} calib3d
|
2014-11-19 21:13:41 +08:00
|
|
|
|
|
|
|
/** @brief The methods in this namespace use a so-called fisheye camera model.
|
|
|
|
@ingroup calib3d_fisheye
|
|
|
|
*/
|
2014-07-08 18:33:56 +08:00
|
|
|
namespace fisheye
|
|
|
|
{
|
2014-11-19 21:13:41 +08:00
|
|
|
//! @addtogroup calib3d_fisheye
|
|
|
|
//! @{
|
|
|
|
|
2014-07-08 18:33:56 +08:00
|
|
|
enum{
|
2016-04-26 18:15:53 +08:00
|
|
|
CALIB_USE_INTRINSIC_GUESS = 1 << 0,
|
|
|
|
CALIB_RECOMPUTE_EXTRINSIC = 1 << 1,
|
|
|
|
CALIB_CHECK_COND = 1 << 2,
|
|
|
|
CALIB_FIX_SKEW = 1 << 3,
|
|
|
|
CALIB_FIX_K1 = 1 << 4,
|
|
|
|
CALIB_FIX_K2 = 1 << 5,
|
|
|
|
CALIB_FIX_K3 = 1 << 6,
|
|
|
|
CALIB_FIX_K4 = 1 << 7,
|
|
|
|
CALIB_FIX_INTRINSIC = 1 << 8,
|
|
|
|
CALIB_FIX_PRINCIPAL_POINT = 1 << 9
|
2014-07-08 18:33:56 +08:00
|
|
|
};
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Projects points using fisheye model
|
|
|
|
|
|
|
|
@param objectPoints Array of object points, 1xN/Nx1 3-channel (or vector\<Point3f\> ), where N is
|
|
|
|
the number of points in the view.
|
|
|
|
@param imagePoints Output array of image points, 2xN/Nx2 1-channel or 1xN/Nx1 2-channel, or
|
|
|
|
vector\<Point2f\>.
|
|
|
|
@param affine
|
|
|
|
@param K Camera matrix \f$K = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{_1}\f$.
|
|
|
|
@param D Input vector of distortion coefficients \f$(k_1, k_2, k_3, k_4)\f$.
|
|
|
|
@param alpha The skew coefficient.
|
|
|
|
@param jacobian Optional output 2Nx15 jacobian matrix of derivatives of image points with respect
|
|
|
|
to components of the focal lengths, coordinates of the principal point, distortion coefficients,
|
|
|
|
rotation vector, translation vector, and the skew. In the old interface different components of
|
|
|
|
the jacobian are returned via different output parameters.
|
|
|
|
|
|
|
|
The function computes projections of 3D points to the image plane given intrinsic and extrinsic
|
|
|
|
camera 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 extrinsic.
|
|
|
|
*/
|
2014-07-08 18:33:56 +08:00
|
|
|
CV_EXPORTS void projectPoints(InputArray objectPoints, OutputArray imagePoints, const Affine3d& affine,
|
|
|
|
InputArray K, InputArray D, double alpha = 0, OutputArray jacobian = noArray());
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @overload */
|
2015-01-09 17:05:36 +08:00
|
|
|
CV_EXPORTS_W void projectPoints(InputArray objectPoints, OutputArray imagePoints, InputArray rvec, InputArray tvec,
|
2014-07-08 18:33:56 +08:00
|
|
|
InputArray K, InputArray D, double alpha = 0, OutputArray jacobian = noArray());
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Distorts 2D points using fisheye model.
|
|
|
|
|
|
|
|
@param undistorted Array of object points, 1xN/Nx1 2-channel (or vector\<Point2f\> ), where N is
|
|
|
|
the number of points in the view.
|
|
|
|
@param K Camera matrix \f$K = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{_1}\f$.
|
|
|
|
@param D Input vector of distortion coefficients \f$(k_1, k_2, k_3, k_4)\f$.
|
|
|
|
@param alpha The skew coefficient.
|
|
|
|
@param distorted Output array of image points, 1xN/Nx1 2-channel, or vector\<Point2f\> .
|
2016-02-24 22:44:32 +08:00
|
|
|
|
2017-10-31 00:13:59 +08:00
|
|
|
Note that the function assumes the camera matrix of the undistorted points to be identity.
|
2016-02-24 22:44:32 +08:00
|
|
|
This means if you want to transform back points undistorted with undistortPoints() you have to
|
|
|
|
multiply them with \f$P^{-1}\f$.
|
2014-11-19 21:13:41 +08:00
|
|
|
*/
|
2015-01-09 17:05:36 +08:00
|
|
|
CV_EXPORTS_W void distortPoints(InputArray undistorted, OutputArray distorted, InputArray K, InputArray D, double alpha = 0);
|
2014-07-08 18:33:56 +08:00
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Undistorts 2D points using fisheye model
|
|
|
|
|
|
|
|
@param distorted Array of object points, 1xN/Nx1 2-channel (or vector\<Point2f\> ), where N is the
|
|
|
|
number of points in the view.
|
|
|
|
@param K Camera matrix \f$K = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{_1}\f$.
|
|
|
|
@param D Input vector of distortion coefficients \f$(k_1, k_2, k_3, k_4)\f$.
|
|
|
|
@param R Rectification transformation in the object space: 3x3 1-channel, or vector: 3x1/1x3
|
|
|
|
1-channel or 1x1 3-channel
|
|
|
|
@param P New camera matrix (3x3) or new projection matrix (3x4)
|
|
|
|
@param undistorted Output array of image points, 1xN/Nx1 2-channel, or vector\<Point2f\> .
|
|
|
|
*/
|
2015-01-09 17:05:36 +08:00
|
|
|
CV_EXPORTS_W void undistortPoints(InputArray distorted, OutputArray undistorted,
|
2014-07-08 18:33:56 +08:00
|
|
|
InputArray K, InputArray D, InputArray R = noArray(), InputArray P = noArray());
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Computes undistortion and rectification maps for image transform by cv::remap(). If D is empty zero
|
|
|
|
distortion is used, if R or P is empty identity matrixes are used.
|
|
|
|
|
|
|
|
@param K Camera matrix \f$K = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{_1}\f$.
|
|
|
|
@param D Input vector of distortion coefficients \f$(k_1, k_2, k_3, k_4)\f$.
|
|
|
|
@param R Rectification transformation in the object space: 3x3 1-channel, or vector: 3x1/1x3
|
|
|
|
1-channel or 1x1 3-channel
|
|
|
|
@param P New camera matrix (3x3) or new projection matrix (3x4)
|
|
|
|
@param size Undistorted image size.
|
2014-11-21 16:28:14 +08:00
|
|
|
@param m1type Type of the first output map that can be CV_32FC1 or CV_16SC2 . See convertMaps()
|
2014-11-19 21:13:41 +08:00
|
|
|
for details.
|
|
|
|
@param map1 The first output map.
|
|
|
|
@param map2 The second output map.
|
|
|
|
*/
|
2015-01-09 17:05:36 +08:00
|
|
|
CV_EXPORTS_W void initUndistortRectifyMap(InputArray K, InputArray D, InputArray R, InputArray P,
|
2014-07-08 18:33:56 +08:00
|
|
|
const cv::Size& size, int m1type, OutputArray map1, OutputArray map2);
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Transforms an image to compensate for fisheye lens distortion.
|
|
|
|
|
|
|
|
@param distorted image with fisheye lens distortion.
|
|
|
|
@param undistorted Output image with compensated fisheye lens distortion.
|
|
|
|
@param K Camera matrix \f$K = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{_1}\f$.
|
|
|
|
@param D Input vector of distortion coefficients \f$(k_1, k_2, k_3, k_4)\f$.
|
|
|
|
@param Knew Camera matrix of the distorted image. By default, it is the identity matrix but you
|
|
|
|
may additionally scale and shift the result by using a different matrix.
|
|
|
|
@param new_size
|
|
|
|
|
|
|
|
The function transforms an image to compensate radial and tangential lens distortion.
|
|
|
|
|
|
|
|
The function is simply a combination of fisheye::initUndistortRectifyMap (with unity R ) and remap
|
|
|
|
(with bilinear interpolation). See the former function for details of the transformation being
|
|
|
|
performed.
|
|
|
|
|
|
|
|
See below the results of undistortImage.
|
2014-11-21 16:28:14 +08:00
|
|
|
- a\) result of undistort of perspective camera model (all possible coefficients (k_1, k_2, k_3,
|
|
|
|
k_4, k_5, k_6) of distortion were optimized under calibration)
|
|
|
|
- b\) result of fisheye::undistortImage of fisheye camera model (all possible coefficients (k_1, k_2,
|
|
|
|
k_3, k_4) of fisheye distortion were optimized under calibration)
|
2014-11-19 21:13:41 +08:00
|
|
|
- c\) original image was captured with fisheye lens
|
|
|
|
|
|
|
|
Pictures a) and b) almost the same. But if we consider points of image located far from the center
|
|
|
|
of image, we can notice that on image a) these points are distorted.
|
|
|
|
|
|
|
|
![image](pics/fisheye_undistorted.jpg)
|
|
|
|
*/
|
2015-01-09 17:05:36 +08:00
|
|
|
CV_EXPORTS_W void undistortImage(InputArray distorted, OutputArray undistorted,
|
2014-07-08 18:33:56 +08:00
|
|
|
InputArray K, InputArray D, InputArray Knew = cv::noArray(), const Size& new_size = Size());
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Estimates new camera matrix for undistortion or rectification.
|
|
|
|
|
|
|
|
@param K Camera matrix \f$K = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{_1}\f$.
|
|
|
|
@param image_size
|
|
|
|
@param D Input vector of distortion coefficients \f$(k_1, k_2, k_3, k_4)\f$.
|
|
|
|
@param R Rectification transformation in the object space: 3x3 1-channel, or vector: 3x1/1x3
|
|
|
|
1-channel or 1x1 3-channel
|
|
|
|
@param P New camera matrix (3x3) or new projection matrix (3x4)
|
|
|
|
@param balance Sets the new focal length in range between the min focal length and the max focal
|
|
|
|
length. Balance is in range of [0, 1].
|
|
|
|
@param new_size
|
|
|
|
@param fov_scale Divisor for new focal length.
|
|
|
|
*/
|
2015-01-09 17:05:36 +08:00
|
|
|
CV_EXPORTS_W void estimateNewCameraMatrixForUndistortRectify(InputArray K, InputArray D, const Size &image_size, InputArray R,
|
2014-07-08 18:33:56 +08:00
|
|
|
OutputArray P, double balance = 0.0, const Size& new_size = Size(), double fov_scale = 1.0);
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Performs camera calibaration
|
|
|
|
|
|
|
|
@param objectPoints vector of vectors of calibration pattern points in the calibration pattern
|
|
|
|
coordinate space.
|
|
|
|
@param imagePoints 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.
|
2014-11-21 16:28:14 +08:00
|
|
|
@param image_size Size of the image used only to initialize the intrinsic camera matrix.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param K Output 3x3 floating-point camera matrix
|
|
|
|
\f$A = \vecthreethree{f_x}{0}{c_x}{0}{f_y}{c_y}{0}{0}{1}\f$ . If
|
2014-11-21 16:28:14 +08:00
|
|
|
fisheye::CALIB_USE_INTRINSIC_GUESS/ is specified, some or all of fx, fy, cx, cy must be
|
2014-11-19 21:13:41 +08:00
|
|
|
initialized before calling the function.
|
|
|
|
@param D Output vector of distortion coefficients \f$(k_1, k_2, k_3, k_4)\f$.
|
|
|
|
@param rvecs Output vector of rotation vectors (see 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).
|
|
|
|
@param tvecs Output vector of translation vectors estimated for each pattern view.
|
|
|
|
@param flags Different flags that may be zero or a combination of the following values:
|
2014-11-21 16:28:14 +08:00
|
|
|
- **fisheye::CALIB_USE_INTRINSIC_GUESS** cameraMatrix contains valid initial values of
|
2014-11-19 21:13:41 +08:00
|
|
|
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.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **fisheye::CALIB_RECOMPUTE_EXTRINSIC** Extrinsic will be recomputed after each iteration
|
2014-11-19 21:13:41 +08:00
|
|
|
of intrinsic optimization.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **fisheye::CALIB_CHECK_COND** The functions will check validity of condition number.
|
|
|
|
- **fisheye::CALIB_FIX_SKEW** Skew coefficient (alpha) is set to zero and stay zero.
|
2016-04-26 18:15:53 +08:00
|
|
|
- **fisheye::CALIB_FIX_K1..fisheye::CALIB_FIX_K4** Selected distortion coefficients
|
|
|
|
are set to zeros and stay zero.
|
|
|
|
- **fisheye::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 CALIB_USE_INTRINSIC_GUESS is set too.
|
2014-11-19 21:13:41 +08:00
|
|
|
@param criteria Termination criteria for the iterative optimization algorithm.
|
|
|
|
*/
|
2015-01-09 17:05:36 +08:00
|
|
|
CV_EXPORTS_W double calibrate(InputArrayOfArrays objectPoints, InputArrayOfArrays imagePoints, const Size& image_size,
|
2014-07-08 18:33:56 +08:00
|
|
|
InputOutputArray K, InputOutputArray D, OutputArrayOfArrays rvecs, OutputArrayOfArrays tvecs, int flags = 0,
|
|
|
|
TermCriteria criteria = TermCriteria(TermCriteria::COUNT + TermCriteria::EPS, 100, DBL_EPSILON));
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Stereo rectification for fisheye camera model
|
|
|
|
|
|
|
|
@param K1 First camera matrix.
|
|
|
|
@param D1 First camera distortion parameters.
|
|
|
|
@param K2 Second camera matrix.
|
|
|
|
@param D2 Second camera distortion parameters.
|
|
|
|
@param imageSize Size of the image used for stereo calibration.
|
|
|
|
@param R Rotation matrix between the coordinate systems of the first and the second
|
|
|
|
cameras.
|
|
|
|
@param tvec 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.
|
|
|
|
@param Q Output \f$4 \times 4\f$ disparity-to-depth mapping matrix (see reprojectImageTo3D ).
|
2017-05-24 20:50:41 +08:00
|
|
|
@param flags Operation flags that may be zero or CALIB_ZERO_DISPARITY . If the flag is set,
|
2014-11-19 21:13:41 +08:00
|
|
|
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.
|
|
|
|
@param newImageSize New image resolution after rectification. The same size should be passed to
|
2014-11-21 16:28:14 +08:00
|
|
|
initUndistortRectifyMap (see the stereo_calib.cpp sample in OpenCV samples directory). When (0,0)
|
2014-11-19 21:13:41 +08:00
|
|
|
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 balance Sets the new focal length in range between the min focal length and the max focal
|
|
|
|
length. Balance is in range of [0, 1].
|
|
|
|
@param fov_scale Divisor for new focal length.
|
|
|
|
*/
|
2015-01-09 17:05:36 +08:00
|
|
|
CV_EXPORTS_W void stereoRectify(InputArray K1, InputArray D1, InputArray K2, InputArray D2, const Size &imageSize, InputArray R, InputArray tvec,
|
2014-07-08 18:33:56 +08:00
|
|
|
OutputArray R1, OutputArray R2, OutputArray P1, OutputArray P2, OutputArray Q, int flags, const Size &newImageSize = Size(),
|
|
|
|
double balance = 0.0, double fov_scale = 1.0);
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
/** @brief Performs stereo calibration
|
|
|
|
|
|
|
|
@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 K1 Input/output first camera matrix:
|
|
|
|
\f$\vecthreethree{f_x^{(j)}}{0}{c_x^{(j)}}{0}{f_y^{(j)}}{c_y^{(j)}}{0}{0}{1}\f$ , \f$j = 0,\, 1\f$ . If
|
2017-05-24 20:50:41 +08:00
|
|
|
any of fisheye::CALIB_USE_INTRINSIC_GUESS , fisheye::CALIB_FIX_INTRINSIC are specified,
|
2014-11-19 21:13:41 +08:00
|
|
|
some or all of the matrix components must be initialized.
|
|
|
|
@param D1 Input/output vector of distortion coefficients \f$(k_1, k_2, k_3, k_4)\f$ of 4 elements.
|
|
|
|
@param K2 Input/output second camera matrix. The parameter is similar to K1 .
|
|
|
|
@param D2 Input/output lens distortion coefficients for the second camera. The parameter is
|
|
|
|
similar to D1 .
|
|
|
|
@param imageSize Size of the image used only to initialize intrinsic camera matrix.
|
|
|
|
@param R Output rotation matrix between the 1st and the 2nd camera coordinate systems.
|
|
|
|
@param T Output translation vector between the coordinate systems of the cameras.
|
|
|
|
@param flags Different flags that may be zero or a combination of the following values:
|
2017-05-24 20:50:41 +08:00
|
|
|
- **fisheye::CALIB_FIX_INTRINSIC** Fix K1, K2? and D1, D2? so that only R, T matrices
|
2014-11-19 21:13:41 +08:00
|
|
|
are estimated.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **fisheye::CALIB_USE_INTRINSIC_GUESS** K1, K2 contains valid initial values of
|
2014-11-19 21:13:41 +08:00
|
|
|
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.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **fisheye::CALIB_RECOMPUTE_EXTRINSIC** Extrinsic will be recomputed after each iteration
|
2014-11-19 21:13:41 +08:00
|
|
|
of intrinsic optimization.
|
2014-11-21 16:28:14 +08:00
|
|
|
- **fisheye::CALIB_CHECK_COND** The functions will check validity of condition number.
|
|
|
|
- **fisheye::CALIB_FIX_SKEW** Skew coefficient (alpha) is set to zero and stay zero.
|
|
|
|
- **fisheye::CALIB_FIX_K1..4** Selected distortion coefficients are set to zeros and stay
|
2014-11-19 21:13:41 +08:00
|
|
|
zero.
|
|
|
|
@param criteria Termination criteria for the iterative optimization algorithm.
|
|
|
|
*/
|
2015-01-09 17:05:36 +08:00
|
|
|
CV_EXPORTS_W double stereoCalibrate(InputArrayOfArrays objectPoints, InputArrayOfArrays imagePoints1, InputArrayOfArrays imagePoints2,
|
2014-07-08 18:33:56 +08:00
|
|
|
InputOutputArray K1, InputOutputArray D1, InputOutputArray K2, InputOutputArray D2, Size imageSize,
|
2015-01-09 17:05:36 +08:00
|
|
|
OutputArray R, OutputArray T, int flags = fisheye::CALIB_FIX_INTRINSIC,
|
2014-07-08 18:33:56 +08:00
|
|
|
TermCriteria criteria = TermCriteria(TermCriteria::COUNT + TermCriteria::EPS, 100, DBL_EPSILON));
|
|
|
|
|
2014-11-19 21:13:41 +08:00
|
|
|
//! @} calib3d_fisheye
|
2018-01-19 20:23:09 +08:00
|
|
|
} // end namespace fisheye
|
2014-07-08 18:33:56 +08:00
|
|
|
|
2018-01-19 20:23:09 +08:00
|
|
|
} //end namespace cv
|
2010-05-12 01:44:00 +08:00
|
|
|
|
|
|
|
#endif
|