match_rel_pose_ransac ( Image1, Image2 : : Rows1, Cols1, Rows2, Cols2, CamPar1, CamPar2, GrayMatchMethod, MaskSize, RowMove, ColMove, RowTolerance, ColTolerance, Rotation, MatchThreshold, EstimationMethod, DistanceThreshold, RandSeed : RelPose, CovRelPose, Error, Points1, Points2 )
Compute the relative orientation between two cameras by automatically
finding correspondences between image points.
Given a set of coordinates of characteristic points
(Rows1,Cols1) and (Rows2,Cols2)
in the stereo images Image1 and Image2
along with known internal camera parameters CamPar1 and
CamPar2,
match_rel_pose_ransac automatically determines the geometry
of the stereo setup and finds the correspondences between the characteristic
points. The geometry of the stereo setup is represented by the relative pose
RelPose and all corresponding points have to fulfill the epipolar
constraint.
RelPose indicates the relative pose of camera 1 with respect
to camera 2 (See create_pose for more information about
poses and their representations.). This is in accordance with the
explicit calibration of a stereo setup using the operator
binocular_calibration.
Now, let R,t be the rotation and translation
of the relative pose. Then, the essential matrix
E is defined as E=([t]_x R)^T, where
[t]_x denotes the 3x3 skew-symmetric
matrix realising the cross product with the vector t. The
pose can be determined from the epipolar constraint:
T
/ X2 \ T / X1 \ / 0 -t_z t_y \
| Y2 | * ([t]_x R) * | Y1 | = 0 where [t]_x = | t_z 0 -t_x | .
\ 1 / \ 1 / \ -t_y t_x 0 /
Note, that the essential matrix is a projective entity and thus is
defined up to a scaling factor. From this follows that the
translation vector of the relative pose can only be determined up to
scale too. In fact, the computed translation vector will always be
normalized to unit length. As a consequence, a subsequent
threedimensional reconstruction of the scene, using for instance
vector_to_rel_pose, can be carried out only
up to a single global scaling factor.
The operator match_rel_pose_ransac is designed to deal with
a camera model, that includes lens distortions. This is in contrast
to the operator match_essential_matrix_ransac, which
encompasses only straight line preserving cameras. The camera
parameters are passed in CamPar1 and CamPar2. The
3D direction vectors (X1,Y1,1) and
(X2,Y2,1) are calculated from the point
coordinates (Rows1,Cols1) and
(Rows2,Cols2) by inverting the process of
projection (see camera_calibration).
The matching process is based on characteristic points, which can be
extracted with point operators like points_foerstner or
points_harris.
The matching itself is carried out in two steps: first, gray value
correlations of mask windows around the input points in the first
and the second image are determined and an initial matching between
them is generated using the similarity of the windows in both images.
Then, the RANSAC algorithm is applied to find the relative pose
that maximizes the number of correspondences under the epipolar constraint.
The size of the mask windows is MaskSize x MaskSize. Three
metrics for the correlation can be selected. If
GrayMatchMethod has the value 'ssd', the sum of
the squared gray value differences is used, 'sad' means the
sum of absolute differences, and 'ncc' is the normalized
cross correlation. This metric is minimized ('ssd',
'sad') or maximized ('ncc') over all possible
point pairs. A thus found matching is only accepted if the value of
the metric is below the value of MatchThreshold
('ssd', 'sad') or above that value
('ncc').
To increase the speed of the algorithm, the search area for the
matchings can be limited. Only points within a window of 2*RowTolerance x
2*ColTolerance points are considered. The offset of the
center of the search window in the second image with respect to the
position of the current point in the first image is given by
RowMove and ColMove.
If the second camera is
rotated around the optical axis with respect to the first camera
the parameter Rotation may contain an estimate for the
rotation angle or an angle interval in radians. A good guess will
increase the quality of the gray value matching. If the actual
rotation differs too much from the specified estimate the matching
will typically fail. In this case, an angle interval should be
specified, and Rotation is a tuple with two elements. The
larger the given interval the slower the operator is since the
RANSAC algorithm is run over all angle increments within the
interval.
After the initial matching is completed a randomized search algorithm
(RANSAC) is used to determine the relative pose RelPose.
It tries to find the relative pose that is consistent
with a maximum number of correspondences.
For a point to be accepted, the distance to its corresponding epipolar line
must not exceed the threshold DistanceThreshold.
The parameter EstimationMethod decides whether the relative
orientation between the cameras is of a special type and which algorithm is
to be applied for its computation.
If EstimationMethod is either 'normalized_dlt' or
'gold_standard' the relative orientation is arbitrary.
Choosing 'trans_normalized_dlt' or 'trans_gold_standard'
means that the relative motion between the cameras is a pure translation.
The typical application for this special motion case is the
scenario of a single fixed camera looking onto a moving conveyor belt.
In order to get a unique solution in the correspondence problem the minimum
required number of corresponding points is six in the general case and three
in the special, translational case.
The relative pose is computed by a linear algorithm if
'normalized_dlt' or 'trans_normalized_dlt' is chosen.
With 'gold_standard' or 'trans_gold_standard'
the algorithm gives a statistically optimal result, and returns as well the
covariance of the relative pose CovRelPose.
Here, 'normalized_dlt' and 'gold_standard' stand for
direct-linear-transformation and gold-standard-algorithm respectively.
Note, that in general the found correspondences differ depending on the
deployed estimation method.
The value Error indicates the overall quality of the estimation
procedure and is the mean euclidian distance in pixels between the
points and their corresponding epipolar lines.
Point pairs consistent with the mentioned constraints are considered to be
in correspondences. Points1 contains the indices of the
matched input points from the first image and Points2 contains
the indices of the corresponding points in the second image.
For the operator match_rel_pose_ransac a special
configuration of scene points and cameras exists: if all 3D points lie in a
single plane and additionally are all closer to one of the two cameras then
the solution in the essential matrix is not unique but twofold.
As a consequence both solutions are computed and returned by the operator.
This means that the output parameters RelPose and
CovRelPose are of double length and the values of the second
solution are simply concatenated behind the values of the first one.
The parameter RandSeed can be used to control the
randomized nature of the RANSAC algorithm, and hence to obtain
reproducible results. If RandSeed is set to a positive
number the operator yields the same result on every call with the
same parameters because the internally used random number generator
is initialized with the RandSeed. If RandSeed =
0 the random number generator is initialized with the
current time. In this case the results may not be reproducible.
Parameters
Image1 (input_object)
|
singlechannelimage -> object : byte / uint2
|
|
Input image 1. |
Image2 (input_object)
|
singlechannelimage -> object : byte / uint2
|
|
Input image 2. |
Rows1 (input_control)
|
number-array -> real / integer
|
|
Row coordinates of characteristic points
in image 1. |
|
Restriction: (length(Rows1) >= 6) || (length(Rows1) >= 3) |
Cols1 (input_control)
|
number-array -> real / integer
|
|
Column coordinates of characteristic points
in image 1. |
|
Restriction: length(Cols1) == length(Rows1) |
Rows2 (input_control)
|
number-array -> real / integer
|
|
Row coordinates of characteristic points
in image 2. |
|
Restriction: (length(Rows2) >= 6) || (length(Rows2) >= 3) |
Cols2 (input_control)
|
number-array -> real / integer
|
|
Column coordinates of characteristic points
in image 2. |
|
Restriction: length(Cols2) == length(Rows2) |
CamPar1 (input_control)
|
number-array -> real / integer
|
|
Parameters of the 1st camera. |
CamPar2 (input_control)
|
number-array -> real / integer
|
|
Parameters of the 2nd camera. |
GrayMatchMethod (input_control)
|
string -> string
|
|
Gray value comparison metric. |
|
Default value: 'ssd' |
|
List of values: 'ssd', 'sad', 'ncc' |
MaskSize (input_control)
|
integer -> integer
|
|
Size of gray value masks. |
|
Default value: 10 |
|
Typical range of values: 3 <= MaskSize <= 15 |
|
Restriction: MaskSize >= 1 |
RowMove (input_control)
|
integer -> integer
|
|
Average row coordinate shift of corresponding points. |
|
Default value: 0 |
|
Typical range of values: 0 <= RowMove <= 200 |
ColMove (input_control)
|
integer -> integer
|
|
Average column coordinate shift of
corresponding points. |
|
Default value: 0 |
|
Typical range of values: 0 <= ColMove <= 200 |
RowTolerance (input_control)
|
integer -> integer
|
|
Half height of matching search window. |
|
Default value: 200 |
|
Typical range of values: 50 <= RowTolerance <= 200 |
|
Restriction: RowTolerance >= 1 |
ColTolerance (input_control)
|
integer -> integer
|
|
Half width of matching search window. |
|
Default value: 200 |
|
Typical range of values: 50 <= ColTolerance <= 200 |
|
Restriction: ColTolerance >= 1 |
Rotation (input_control)
|
number(-array) -> real / integer
|
|
Estimate of the relative orientation of the right image
with respect to the left image. |
|
Default value: 0.0 |
|
Suggested values: 0.0, 0.1, -0.1, 0.7854, 1.571, 3.142 |
MatchThreshold (input_control)
|
number -> integer / real
|
|
Threshold for gray value matching. |
|
Default value: 10 |
|
Suggested values: 10, 20, 50, 100, 0.9, 0.7 |
EstimationMethod (input_control)
|
string -> string
|
|
Algorithm for the computation of the
relative pose and for special pose types. |
|
Default value: 'normalized_dlt' |
|
List of values: 'normalized_dlt', 'gold_standard', 'trans_normalized_dlt', 'trans_gold_standard' |
DistanceThreshold (input_control)
|
number -> real / integer
|
|
Maximal deviation of a point from its epipolar line. |
|
Default value: 1 |
|
Typical range of values: 0.5 <= DistanceThreshold <= 5 |
|
Restriction: DistanceThreshold > 0 |
RandSeed (input_control)
|
integer -> integer
|
|
Seed for the random number generator. |
|
Default value: 0 |
RelPose (output_control)
|
pose-array -> real
|
|
Computed relative orientation of the cameras
(3D pose). |
CovRelPose (output_control)
|
real-array -> real
|
|
6x6 covariance matrix of the
relative orientation. |
Error (output_control)
|
real -> real
|
|
Root-Mean-Square of the epipolar distance error. |
Points1 (output_control)
|
integer-array -> integer
|
|
Indices of matched input points in image 1. |
Points2 (output_control)
|
integer-array -> integer
|
|
Indices of matched input points in image 2. |
Parallelization Information
match_rel_pose_ransac is reentrant and processed without parallelization.
Possible Predecessors
points_foerstner,
points_harris
Possible Successors
vector_to_rel_pose,
gen_binocular_rectification_map
See also
binocular_calibration,
match_fundamental_matrix_ransac,
match_essential_matrix_ransac,
create_pose
References
Richard Hartley, Andrew Zisserman: ``Multiple View Geometry in
Computer Vision''; Cambridge University Press, Cambridge; 2003.
Olivier Faugeras, Quang-Tuan Luong: ``The Geometry of Multiple
Images: The Laws That Govern the Formation of Multiple Images of a
Scene and Some of Their Applications''; MIT Press, Cambridge, MA;
2001.
Module
3D Metrology
Copyright © 1996-2008 MVTec Software GmbH