opencv/doc/tutorials/others/non_linear_svms.markdown

Support Vector Machines for Non-Linearly Separable Data

@tableofcontents

@prev_tutorial{tutorial_introduction_to_svm} @next_tutorial{tutorial_introduction_to_pca}

Original author	Fernando Iglesias García
Compatibility	OpenCV >= 3.0

Goal

In this tutorial you will learn how to:

• Define the optimization problem for SVMs when it is not possible to separate linearly the training data.
• How to configure the parameters to adapt your SVM for this class of problems.

Motivation

Why is it interesting to extend the SVM optimization problem in order to handle non-linearly separable training data? Most of the applications in which SVMs are used in computer vision require a more powerful tool than a simple linear classifier. This stems from the fact that in these tasks the training data can be rarely separated using an hyperplane.

Consider one of these tasks, for example, face detection. The training data in this case is composed by a set of images that are faces and another set of images that are non-faces (every other thing in the world except from faces). This training data is too complex so as to find a representation of each sample (feature vector) that could make the whole set of faces linearly separable from the whole set of non-faces.

Extension of the Optimization Problem

Remember that using SVMs we obtain a separating hyperplane. Therefore, since the training data is now non-linearly separable, we must admit that the hyperplane found will misclassify some of the samples. This misclassification is a new variable in the optimization that must be taken into account. The new model has to include both the old requirement of finding the hyperplane that gives the biggest margin and the new one of generalizing the training data correctly by not allowing too many classification errors.

We start here from the formulation of the optimization problem of finding the hyperplane which maximizes the margin (this is explained in the previous tutorial (@ref tutorial_introduction_to_svm):

\f[\min_{\beta, \beta_{0}} L(\beta) = \frac{1}{2}||\beta||^{2} \text{ subject to } y_{i}(\beta^{T} x_{i} + \beta_{0}) \geq 1 \text{ } \forall i\f]

There are multiple ways in which this model can be modified so it takes into account the misclassification errors. For example, one could think of minimizing the same quantity plus a constant times the number of misclassification errors in the training data, i.e.:

\f[\min ||\beta||^{2} + C \text{(misclassification errors)}\f]

However, this one is not a very good solution since, among some other reasons, we do not distinguish between samples that are misclassified with a small distance to their appropriate decision region or samples that are not. Therefore, a better solution will take into account the distance of the misclassified samples to their correct decision regions, i.e.:

\f[\min ||\beta||^{2} + C \text{(distance of misclassified samples to their correct regions)}\f]

For each sample of the training data a new parameter \f$\xi_{i}\f$ is defined. Each one of these parameters contains the distance from its corresponding training sample to their correct decision region. The following picture shows non-linearly separable training data from two classes, a separating hyperplane and the distances to their correct regions of the samples that are misclassified.

@note Only the distances of the samples that are misclassified are shown in the picture. The distances of the rest of the samples are zero since they lay already in their correct decision region.

The red and blue lines that appear on the picture are the margins to each one of the decision regions. It is very important to realize that each of the \f$\xi_{i}\f$ goes from a misclassified training sample to the margin of its appropriate region.

Finally, the new formulation for the optimization problem is:

\f[\min_{\beta, \beta_{0}} L(\beta) = ||\beta||^{2} + C \sum_{i} {\xi_{i}} \text{ subject to } y_{i}(\beta^{T} x_{i} + \beta_{0}) \geq 1 - \xi_{i} \text{ and } \xi_{i} \geq 0 \text{ } \forall i\f]

How should the parameter C be chosen? It is obvious that the answer to this question depends on how the training data is distributed. Although there is no general answer, it is useful to take into account these rules:

• Large values of C give solutions with less misclassification errors but a smaller margin. Consider that in this case it is expensive to make misclassification errors. Since the aim of the optimization is to minimize the argument, few misclassifications errors are allowed.
• Small values of C give solutions with bigger margin and more classification errors. In this case the minimization does not consider that much the term of the sum so it focuses more on finding a hyperplane with big margin.

Source Code

You may also find the source code in samples/cpp/tutorial_code/ml/non_linear_svms folder of the OpenCV source library or download it from here.

@add_toggle_cpp

• Downloadable code: Click here

• Code at glance: @include samples/cpp/tutorial_code/ml/non_linear_svms/non_linear_svms.cpp @end_toggle

@add_toggle_java

• Downloadable code: Click here

• Code at glance: @include samples/java/tutorial_code/ml/non_linear_svms/NonLinearSVMsDemo.java @end_toggle

@add_toggle_python

• Downloadable code: Click here

• Code at glance: @include samples/python/tutorial_code/ml/non_linear_svms/non_linear_svms.py @end_toggle

Explanation

• Set up the training data

The training data of this exercise is formed by a set of labeled 2D-points that belong to one of two different classes. To make the exercise more appealing, the training data is generated randomly using a uniform probability density functions (PDFs).

We have divided the generation of the training data into two main parts.

In the first part we generate data for both classes that is linearly separable.

@add_toggle_cpp @snippet samples/cpp/tutorial_code/ml/non_linear_svms/non_linear_svms.cpp setup1 @end_toggle

@add_toggle_java @snippet samples/java/tutorial_code/ml/non_linear_svms/NonLinearSVMsDemo.java setup1 @end_toggle

@add_toggle_python @snippet samples/python/tutorial_code/ml/non_linear_svms/non_linear_svms.py setup1 @end_toggle

In the second part we create data for both classes that is non-linearly separable, data that overlaps.

@add_toggle_cpp @snippet samples/cpp/tutorial_code/ml/non_linear_svms/non_linear_svms.cpp setup2 @end_toggle

@add_toggle_java @snippet samples/java/tutorial_code/ml/non_linear_svms/NonLinearSVMsDemo.java setup2 @end_toggle

@add_toggle_python @snippet samples/python/tutorial_code/ml/non_linear_svms/non_linear_svms.py setup2 @end_toggle

• Set up SVM's parameters

@note In the previous tutorial @ref tutorial_introduction_to_svm there is an explanation of the attributes of the class @ref cv::ml::SVM that we configure here before training the SVM.

@add_toggle_cpp @snippet samples/cpp/tutorial_code/ml/non_linear_svms/non_linear_svms.cpp init @end_toggle

@add_toggle_java @snippet samples/java/tutorial_code/ml/non_linear_svms/NonLinearSVMsDemo.java init @end_toggle

@add_toggle_python @snippet samples/python/tutorial_code/ml/non_linear_svms/non_linear_svms.py init @end_toggle

There are just two differences between the configuration we do here and the one that was done in the previous tutorial (@ref tutorial_introduction_to_svm) that we use as reference.

• C. We chose here a small value of this parameter in order not to punish too much the misclassification errors in the optimization. The idea of doing this stems from the will of obtaining a solution close to the one intuitively expected. However, we recommend to get a better insight of the problem by making adjustments to this parameter.

  @note In this case there are just very few points in the overlapping region between classes. By giving a smaller value to FRAC_LINEAR_SEP the density of points can be incremented and the impact of the parameter C explored deeply.

• Termination Criteria of the algorithm. The maximum number of iterations has to be increased considerably in order to solve correctly a problem with non-linearly separable training data. In particular, we have increased in five orders of magnitude this value.

• Train the SVM

We call the method @ref cv::ml::SVM::train to build the SVM model. Watch out that the training process may take a quite long time. Have patiance when your run the program.

@add_toggle_cpp @snippet samples/cpp/tutorial_code/ml/non_linear_svms/non_linear_svms.cpp train @end_toggle

@add_toggle_java @snippet samples/java/tutorial_code/ml/non_linear_svms/NonLinearSVMsDemo.java train @end_toggle

@add_toggle_python @snippet samples/python/tutorial_code/ml/non_linear_svms/non_linear_svms.py train @end_toggle

• Show the Decision Regions

The method @ref cv::ml::SVM::predict is used to classify an input sample using a trained SVM. In this example we have used this method in order to color the space depending on the prediction done by the SVM. In other words, an image is traversed interpreting its pixels as points of the Cartesian plane. Each of the points is colored depending on the class predicted by the SVM; in dark green if it is the class with label 1 and in dark blue if it is the class with label 2.

@add_toggle_cpp @snippet samples/cpp/tutorial_code/ml/non_linear_svms/non_linear_svms.cpp show @end_toggle

@add_toggle_java @snippet samples/java/tutorial_code/ml/non_linear_svms/NonLinearSVMsDemo.java show @end_toggle

@add_toggle_python @snippet samples/python/tutorial_code/ml/non_linear_svms/non_linear_svms.py show @end_toggle

• Show the training data

The method @ref cv::circle is used to show the samples that compose the training data. The samples of the class labeled with 1 are shown in light green and in light blue the samples of the class labeled with 2.

@add_toggle_cpp @snippet samples/cpp/tutorial_code/ml/non_linear_svms/non_linear_svms.cpp show_data @end_toggle

@add_toggle_java @snippet samples/java/tutorial_code/ml/non_linear_svms/NonLinearSVMsDemo.java show_data @end_toggle

@add_toggle_python @snippet samples/python/tutorial_code/ml/non_linear_svms/non_linear_svms.py show_data @end_toggle

• Support vectors

We use here a couple of methods to obtain information about the support vectors. The method @ref cv::ml::SVM::getSupportVectors obtain all support vectors. We have used this methods here to find the training examples that are support vectors and highlight them.

@add_toggle_cpp @snippet samples/cpp/tutorial_code/ml/non_linear_svms/non_linear_svms.cpp show_vectors @end_toggle

@add_toggle_java @snippet samples/java/tutorial_code/ml/non_linear_svms/NonLinearSVMsDemo.java show_vectors @end_toggle

@add_toggle_python @snippet samples/python/tutorial_code/ml/non_linear_svms/non_linear_svms.py show_vectors @end_toggle

Results

• The code opens an image and shows the training examples of both classes. The points of one class are represented with light green and light blue ones are used for the other class.
• The SVM is trained and used to classify all the pixels of the image. This results in a division of the image in a blue region and a green region. The boundary between both regions is the separating hyperplane. Since the training data is non-linearly separable, it can be seen that some of the examples of both classes are misclassified; some green points lay on the blue region and some blue points lay on the green one.
• Finally the support vectors are shown using gray rings around the training examples.

You may observe a runtime instance of this on the YouTube here.

@youtube{vFv2yPcSo-Q}