Revision history [back]

The retVal I collected from StereoCalibrate() was huge, 39.0

indeed far too large (<1 would be ok). but the problem are usually the chessboard images, not the code. having 68 pairs is already quite a lot (can you show a few ?), so have a look at those, and throw out any where

• not all corners are visible or occluded
• specular highlights (white glares)

please also make sure,

• you have enough images from the corners of the frame, as most distortion happens there
• your chessboard is absolutely flat (no cheating here !!)

The retVal I collected from StereoCalibrate() was huge, 39.0

indeed far too large (<1 would be ok). but the problem are usually the chessboard images, not the code. having 68 pairs is already quite a lot (can you show a few ?), so have a look at those, and throw out any where

• not all corners are visible or occluded
• specular highlights (white glares)

please also make sure,

• you have enough images from the corners of the frame, as most distortion happens therethere
• enough variation in pose (all 3 axes)
• your chessboard is absolutely flat (no cheating here !!)

The retVal I collected from StereoCalibrate() was huge, 39.0

indeed far too large (<1 would be ok). but the problem are usually the chessboard images, not the code. having 68 pairs is already quite a lot (can you show a few ?), so have a look at those, and throw out any where

• not all corners are visible or occluded
• specular highlights (white glares)

please also make sure,

• you have enough images from the corners of the frame, as most distortion happens there
• enough variation in pose (all 3 axes)
• your chessboard is absolutely flat (no cheating here !!)
• chessboard is rectangular, not quadratic

The retVal I collected from StereoCalibrate() was huge, 39.0

indeed far too large (<1 would be ok). but the problem are usually the chessboard images, not the code. having 68 pairs is already quite a lot (can you show a few ?), so have a look at those, and throw out any where

• not all corners are visible or occluded
• specular highlights (white glares)

please also make sure,

• you have enough images from the corners of the frame, as most distortion happens there
• enough variation in pose (all 3 axes)
• your chessboard is absolutely flat (no cheating here !!)
• chessboard is rectangular, not quadratic
• sufficiently large white border (quiet zone) in your printed chessboard

The retVal I collected from StereoCalibrate() was huge, 39.0

indeed far too large (<1 would be ok). but the problem are usually the chessboard images, not the code. having 68 pairs is already quite a lot (can you show a few ?), so have a look at those, and throw out any where

• not all corners are visible or occluded
• specular highlights (white glares)

please also make sure,

• you have enough images from the corners of the frame, as most distortion happens there
• enough variation in pose (all 3 axes)axes) and distance
• your chessboard is absolutely flat (no cheating here !!)
• chessboard is rectangular, not quadratic
• sufficiently large white border (quiet zone) in your printed chessboard

The retVal I collected from StereoCalibrate() was huge, 39.0

indeed far too large (<1 would be ok). but the problem are usually the chessboard images, not the code. having 68 pairs is already quite a lot (can you show a few ?), so have a look at those, and throw out any where

• not all corners are visible or occluded
• specular highlights (white glares)

please also make sure,

• you have enough images from the corners of the frame, as most distortion happens there
• enough variation in pose (all 3 axes) and distance
• your chessboard is absolutely flat (no cheating here !!)
• chessboard is rectangular, not quadratic
• sufficiently large white border (quiet zone) in your printed chessboardchessboard (at least 1 square)