it should read

'... to build and install OpenCV, update DYLD_LIBRARY_PATH ...'

instead of

'... to build and install OpenCV, update LD_LIBRARY_PATH ...'

(see 'man dyld')

"All the program examples in this book are based on OpenCV version 2.0." should be "... version 1.0."

The comment in the code :

// While loop (as in Example 2) capture & show video

This causes an error, the "capture" needs to be replaced with "g_capture", as this version of the code creates a global variable, and is prefaced with a "g_".

The code:

IplImage* out = cvCreateImage(
cvSize( cvGetSize( in ),
IPL_DEPTH_8U,
1
);

does not compile. cvGetSize takes two arguments. It can be fixed thusly:

IplImage* out = cvCreateImage(
cvGetSize( in ),
in->depth, //IPL_DEPTH_8U,
1);

This code is correct and compiles.

Two comments:

Ex 2-6, text "cvSize(" is not needed (and causes a compile time error).

Ex 2-7, Although the canny example specifies single channel only, it is my suggestion to add a function here to convert the image to single channel:

IplImage *doGrayscale(IplImage* in)
{
IplImage* out = cvCreateImage(
cvGetSize(in),
IPL_DEPTH_8U,
1
);
cvCvtColor(in, out, CV_BGR2GRAY);
return out;
}

Function definitions for absolute value functions should be

void cvAbs(
const CvArr* src1, CvArr* dst
);

void cvAbsDiff(
const CvArr* src1, const CvArr* src2, CvArr* dst
);

void cvAbsDiffS(
const CvArr* src, CvArr* dst, CvScalar value
);

In the prototype, function cvCalcCovarMatrix() is erroneously called cvAdd()

Macro aliases for common usage of cvGEMM() should be

cvMatMul(A, B, D) cvGEMM(A, B, 1, NULL, 0, D, 0)
cvMatMulAdd(A, B, C, D) cvGEMM(A, B, 1, C, 1, D, 0)

It's stated that cvGetSubRect(...) takes as it's second argument a CvArr* submat, where as it only takes CvMat *

"The closely related function cvSubS() does the same thing except that the constant scalar value is added to every element of src."

should be

"The closely related function cvSubS() does the same thing except that the constant scalar value is subtracted from every element of src."

cvSub has been explained twice in subsection "cvSub" and "cvSub, cvSubS and cvSubRS"

In the section on Polygons the functions cvFillPoly and cvPolyLine take a parameter contours. The meaning and/or use of this parameter isn't discussed in the text.

The above function takes two parameters as input, the second one being a CvRect struct which specifies the rectangle to draw. However, in the function itself the call to cvRectangle references box and makes no reference to rect. I think all of the references to box in this function should be references to rect.

The source code contains "cvScalar(0xff,0x00,0x00) /* red */".

However, channel order in OpenCV is BGR. OpenCV contains the CV_RGB macro for those more familiar with RGB.

The code should become: "CV_RGB(0xff,0x00,0x00) /* red */".

The method draw_box does not use the "rect" parameter. The box references should probably change into rect references.

"...you can pass -1 to cvCreateCameraCapture(), which will cause OpenCV to open a window that allows you to select the desired camera."

This is incorrect. As correctly stated on p26, a value of -1 means to just select the default camera.

Something is amiss with these two figures. My guess:

Either region A in Figure 5-6 should be smaller (similar to region B in Figure 5-7) or the line styles (solid vs. dotted) is reversed for Region B.

In Figure 5-6 both Image A and A-morph-B are the same. Image A should be the lightly dotted interior figure in Image A-morph-B.

The function prototypes for cvPyrDown and cvPyrUp list the third parameter, filter, as type IplFilter which as near as I can determine isn't defined. The actual prototypes in the software I have they are type 'int'.

In table 5-5, the Operation for the threshold type CV_THRESH_TRUNC has a mistake (probably typo?), uses M instead of T, it should read:

dst_i = (src_i > T) ? T : src_i

The result line is truncated for some of the charts. It should rise to max_value after the last vertical dotted line in the "Threshold Binary" chart. It should fall to zero after the last vertical dotted line in the "Threshold Binary, Inverted" and "Threshold to Zero, Inverted" charts.

There is an error in the correlation mathematical formula in the denominator:

A summation is missing, it must be sqrt(sum(H1'²)*sum(H2'²)) in the denominator (the second summation is missing in the book, or at least, in the PDF version).

Paragraph 3 sentence 3 states:

"The image or array back_project is a single-channel 8-bit or floating point image of the same size as the input images in the array."

In actuality the array back_project must be the same type as images in the input arrays.

The formular for the Cross Correlation shows, that the product of the template and image must be squared. But that's wrong. See: http://opencv.willowgarage.com/documentation/image_processing.html#matching

Figures 8-4 (pg 240) and 8-13 (page 261) have an error on the freeman chain code representation. The code that ends 5-6-6-6-6-7 should be
5-6-6-6-6-6-7; 5-sixes. This can be seen by two methods. In both figures the there are 5 left-horizontal arrows. Also in Fig 8-13 in the 45-degree view there are 5-UL arrows and the chain code ends 6-7-7-7-7-7-8; 5-sevens.

Also in comparing figure 8-3 CV_RETR_LIST to the related text: The text
says "retrieves all the contours". and "eight contours" are found". This happens to agree with the figure.

However the trees for CV_RETR_EXTERNAL, CV_RETR_CCOMP and CV_RETR_TREE ,
which also say "retrieves all the contours", have 9 contours. Also the
figure 8-2 shows 9 contours. The contour h000 is missing from the
CV_RETR_LIST tree.

Should CD->flConfidence[i] = Prob;

read

Should CD->flConfidence[i] = p;

CD->flConfidence[i] = Prob;

should be

CD->flConfidence[i] = p;

Tangential distortion equations should be

x_{corrected} = x + [2p_1xy + p_2(r^2+2x^2)]
y_{corrected} = y + [p_1(r^2+2y^2) + 2p_2xy]

Typing error, the equation should look like this:

x_p = f_x * X_w / Z_w + c_x
y_p = f_y * Y_w / Z_w + c_y

In the formula, it has y_{p} = f_{y} * X^{W}/Z^{W} + c_{y}.
It should have been y_{p} = f_{y} * Y^{W}/Z^{W} + c_{y}

matrix 'distortion_coeffs' should be created with 'cvCreateMat(4,1,CV_32F)' not with 'cvCreateMat(5,1,CV_32F)'.

...with p_l and p_r, which are the location of the point P in the coordinate frames of the two cameras.

->

...with P_l and P_r, which are the location of the point P in the coordinate frames of the two cameras.

The description of the RANSAC algorithm is really LMedS and vice versa. These should be swapped.

In the second paragraph that begins with "Correspondence is computed..." there is mention of the parameter subPixelDisparities near the end of the paragraph however this parameter can not be found in the OpenCV source. Thus there are only 16 subdisparities per pixel and it is currently not configurable.

I believe the following line is wrong:

cvPoint3D32f(i*squareSize, j*squareSize, 0);

shouldn't the x coordinate (j) be first?

cvPoint3D32f(j*squareSize, i*squareSize, 0);