scikit-learn/doc/tutorial/statistical_inference/supervised_learning.rst

585 lines
20 KiB
ReStructuredText
Raw Normal View History

.. _supervised_learning_tut:
=======================================================================================
Supervised learning: predicting an output variable from high-dimensional observations
=======================================================================================
.. topic:: The problem solved in supervised learning
2013-01-22 21:02:56 +08:00
:ref:`Supervised learning <supervised-learning>`
consists in learning the link between two
datasets: the observed data ``X`` and an external variable ``y`` that we
are trying to predict, usually called "target" or "labels". Most often,
``y`` is a 1D array of length ``n_samples``.
2013-01-22 21:02:56 +08:00
2015-12-03 07:16:40 +08:00
All supervised `estimators <https://en.wikipedia.org/wiki/Estimator>`_
in scikit-learn implement a ``fit(X, y)`` method to fit the model
and a ``predict(X)`` method that, given unlabeled observations ``X``,
returns the predicted labels ``y``.
.. topic:: Vocabulary: classification and regression
If the prediction task is to classify the observations in a set of
finite labels, in other words to "name" the objects observed, the task
is said to be a **classification** task. On the other hand, if the goal
is to predict a continuous target variable, it is said to be a
**regression** task.
When doing classification in scikit-learn, ``y`` is a vector of integers
or strings.
Note: See the :ref:`Introduction to machine learning with scikit-learn
Tutorial <introduction>` for a quick run-through on the basic machine
learning vocabulary used within scikit-learn.
Nearest neighbor and the curse of dimensionality
=================================================
.. topic:: Classifying irises:
2013-01-22 21:02:56 +08:00
.. image:: /auto_examples/datasets/images/sphx_glr_plot_iris_dataset_001.png
2012-05-07 05:28:06 +08:00
:target: ../../auto_examples/datasets/plot_iris_dataset.html
:align: right
:scale: 65
The iris dataset is a classification task consisting in identifying 3
different types of irises (Setosa, Versicolour, and Virginica) from
their petal and sepal length and width::
>>> import numpy as np
>>> from sklearn import datasets
>>> iris = datasets.load_iris()
>>> iris_X = iris.data
>>> iris_y = iris.target
>>> np.unique(iris_y)
array([0, 1, 2])
k-Nearest neighbors classifier
-------------------------------
2013-01-22 21:02:56 +08:00
The simplest possible classifier is the
2015-12-03 07:16:40 +08:00
`nearest neighbor <https://en.wikipedia.org/wiki/K-nearest_neighbor_algorithm>`_:
2013-01-22 21:02:56 +08:00
given a new observation ``X_test``, find in the training set (i.e. the data
used to train the estimator) the observation with the closest feature vector.
(Please see the :ref:`Nearest Neighbors section<neighbors>` of the online
Scikit-learn documentation for more information about this type of classifier.)
.. topic:: Training set and testing set
While experimenting with any learning algorithm, it is important not to
test the prediction of an estimator on the data used to fit the
estimator as this would not be evaluating the performance of the
estimator on **new data**. This is why datasets are often split into
*train* and *test* data.
**KNN (k nearest neighbors) classification example**:
.. image:: /auto_examples/neighbors/images/sphx_glr_plot_classification_001.png
:target: ../../auto_examples/neighbors/plot_classification.html
:align: center
:scale: 70
::
>>> # Split iris data in train and test data
>>> # A random permutation, to split the data randomly
>>> np.random.seed(0)
>>> indices = np.random.permutation(len(iris_X))
>>> iris_X_train = iris_X[indices[:-10]]
>>> iris_y_train = iris_y[indices[:-10]]
2018-10-05 22:51:42 +08:00
>>> iris_X_test = iris_X[indices[-10:]]
>>> iris_y_test = iris_y[indices[-10:]]
>>> # Create and fit a nearest-neighbor classifier
>>> from sklearn.neighbors import KNeighborsClassifier
>>> knn = KNeighborsClassifier()
2014-08-26 05:28:51 +08:00
>>> knn.fit(iris_X_train, iris_y_train) # doctest: +NORMALIZE_WHITESPACE
2013-07-08 11:24:00 +08:00
KNeighborsClassifier(algorithm='auto', leaf_size=30, metric='minkowski',
metric_params=None, n_jobs=None, n_neighbors=5, p=2,
weights='uniform')
>>> knn.predict(iris_X_test)
array([1, 2, 1, 0, 0, 0, 2, 1, 2, 0])
>>> iris_y_test
array([1, 1, 1, 0, 0, 0, 2, 1, 2, 0])
.. _curse_of_dimensionality:
The curse of dimensionality
-------------------------------
2013-01-22 21:02:56 +08:00
For an estimator to be effective, you need the distance between neighboring
points to be less than some value :math:`d`, which depends on the problem.
2017-04-19 20:28:49 +08:00
In one dimension, this requires on average :math:`n \sim 1/d` points.
In the context of the above :math:`k`-NN example, if the data is described by
just one feature with values ranging from 0 to 1 and with :math:`n` training
observations, then new data will be no further away than :math:`1/n`.
Therefore, the nearest neighbor decision rule will be efficient as soon as
:math:`1/n` is small compared to the scale of between-class feature variations.
2017-04-19 20:28:49 +08:00
If the number of features is :math:`p`, you now require :math:`n \sim 1/d^p`
points. Let's say that we require 10 points in one dimension: now :math:`10^p`
points are required in :math:`p` dimensions to pave the :math:`[0, 1]` space.
As :math:`p` becomes large, the number of training points required for a good
estimator grows exponentially.
2013-01-22 21:02:56 +08:00
For example, if each point is just a single number (8 bytes), then an
2017-04-19 20:28:49 +08:00
effective :math:`k`-NN estimator in a paltry :math:`p \sim 20` dimensions would
require more training data than the current estimated size of the entire
internet (±1000 Exabytes or so).
2013-01-22 21:02:56 +08:00
This is called the
2015-12-03 07:16:40 +08:00
`curse of dimensionality <https://en.wikipedia.org/wiki/Curse_of_dimensionality>`_
2012-03-20 15:49:35 +08:00
and is a core problem that machine learning addresses.
Linear model: from regression to sparsity
==========================================
.. topic:: Diabetes dataset
The diabetes dataset consists of 10 physiological variables (age,
sex, weight, blood pressure) measure on 442 patients, and an
indication of disease progression after one year::
>>> diabetes = datasets.load_diabetes()
>>> diabetes_X_train = diabetes.data[:-20]
>>> diabetes_X_test = diabetes.data[-20:]
>>> diabetes_y_train = diabetes.target[:-20]
>>> diabetes_y_test = diabetes.target[-20:]
2013-01-22 21:02:56 +08:00
2012-05-03 00:37:58 +08:00
The task at hand is to predict disease progression from physiological
2013-01-22 21:02:56 +08:00
variables.
Linear regression
------------------
2012-03-08 22:21:53 +08:00
.. currentmodule:: sklearn.linear_model
:class:`LinearRegression`,
2016-02-26 10:16:28 +08:00
in its simplest form, fits a linear model to the data set by adjusting
2013-01-22 21:02:56 +08:00
a set of parameters in order to make the sum of the squared residuals
of the model as small as possible.
2012-02-21 18:45:35 +08:00
.. image:: /auto_examples/linear_model/images/sphx_glr_plot_ols_001.png
:target: ../../auto_examples/linear_model/plot_ols.html
:scale: 40
:align: right
Linear models: :math:`y = X\beta + \epsilon`
* :math:`X`: data
* :math:`y`: target variable
* :math:`\beta`: Coefficients
* :math:`\epsilon`: Observation noise
2013-01-22 21:02:56 +08:00
::
2012-02-21 18:45:35 +08:00
>>> from sklearn import linear_model
>>> regr = linear_model.LinearRegression()
>>> regr.fit(diabetes_X_train, diabetes_y_train)
... # doctest: +NORMALIZE_WHITESPACE
LinearRegression(copy_X=True, fit_intercept=True, n_jobs=None,
normalize=False)
2013-02-12 06:11:57 +08:00
>>> print(regr.coef_)
2012-03-02 18:53:07 +08:00
[ 0.30349955 -237.63931533 510.53060544 327.73698041 -814.13170937
492.81458798 102.84845219 184.60648906 743.51961675 76.09517222]
2013-01-22 21:02:56 +08:00
[MRG] Add elastic net penalty to LogisticRegression (#11646) * First draft on elasticnet penaly for LogisticRegression * Some basic tests * Doc update * First draft for LogisticRegressionCV. It seems to be working for binary classification and for multiclass when multi_class='ovr'. I'm having a hard time figuring out the intricacies of multi_class='multinomial'. * Changed default to None for l1_ratio. added warning message is user sets l1_ratio while penalty is not elastic-net * Some more doc * Updated example to plot elastic net sparsity * Fixed flake8 * Fixed test by not modifying attribute in fit * Fixed doc issues * WIP * Partially fixed logistic_reg_CV for multinomial. Also added some comments that are hopefully clear. Still need to fix refit=False * Fixed doc issue * WIP * Fixed test for refit=False in LogisticRegressionCV * Fixed Python 2 numpy version issue * minor doc updates * Weird doc error... * Added test to ensure that elastic net is at least as good as L1 or L2 once l1_ratio has been optimized with grid search Also addressed minor reviews * Fixed test * addressed comments * Added back ignore warning on tests * Added a functional test * Scale data in test... Now failing * elastic-net --> elasticnet * Updated doc for some attributes and checked their shape in tests * Added l1_ratio dimension to coefs_paths and scores attr * improve example + fix test * FIX incorrect lagged_update in SAGA * Add non-regression test for SAGA's bug * FIX flake8 and warning * Re fixed warning * Updated some tests * Addressed comments * more comments and added dimension to LogisticRegressionCV.n_iter_ attribute * Updated whatsnew for 0.21 * better doc shape looks * Fixed whatnew entry after merges * Added dot * Addressed comments + standardized optional default param docstrings * Addessed comments * use swapaxes instead of unsupported moveaxis (hopefully fixes tests)
2018-11-22 09:23:57 +08:00
>>> # The mean square error
2018-10-05 22:51:42 +08:00
>>> np.mean((regr.predict(diabetes_X_test) - diabetes_y_test)**2)
... # doctest: +ELLIPSIS
2012-03-08 16:23:43 +08:00
2004.56760268...
>>> # Explained variance score: 1 is perfect prediction
>>> # and 0 means that there is no linear relationship
2016-07-16 14:39:10 +08:00
>>> # between X and y.
2012-03-08 16:06:51 +08:00
>>> regr.score(diabetes_X_test, diabetes_y_test) # doctest: +ELLIPSIS
2012-03-08 16:23:43 +08:00
0.5850753022690...
.. _shrinkage:
2013-01-22 21:02:56 +08:00
Shrinkage
----------
If there are few data points per dimension, noise in the observations
induces high variance:
.. image:: /auto_examples/linear_model/images/sphx_glr_plot_ols_ridge_variance_001.png
2012-03-08 22:21:53 +08:00
:target: ../../auto_examples/linear_model/plot_ols_ridge_variance.html
:scale: 70
:align: right
::
>>> X = np.c_[ .5, 1].T
>>> y = [.5, 1]
>>> test = np.c_[ 0, 2].T
>>> regr = linear_model.LinearRegression()
2013-01-22 21:02:56 +08:00
[MRG+1] Fix: Replace pylab with matplotlib.pyplot #6754 (#6762) * Fix: Replace pylab with matplotlib.pyplot #6754 - one instance of 22 occurrences of pylab replaced with matplotlib.pyplot - bench_glm.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - one instance of 21 remaining occurrences of pylab replaced with matplotlib.pyplot - bench_glmnet.py now free of pylab references - code does not execute for extraneous reason: ImportError: No module named glmnet.elastic_net * Fix: Replace pylab with matplotlib.pyplot #6754 - one instance of 19 occurrences of pylab replaced with matplotlib.pyplot - bench_lasso.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - one instance of 18 occurrences of pylab replaced with matplotlib.pyplot - bench_plot_neighbors.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - one instance of 17 occurrences of pylab replaced with matplotlib.pyplot - bench_plot_omp_lars.py now free of pylab references - code does not execute for extraneous reasons: - File "bench_plot_omp_lars.py", line 111, in <module> - ax = fig.add_subplot(1, 2, i) - ValueError: num must be 1 <= num <= 2, not 0 - line 111 should probably be ax = fig.add_subplot(1, 2, i+1) * Fix: Replace pylab with matplotlib.pyplot #6754 - bench_plot_parallel_pairwise.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - bench_plot_ward.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - bench_sgd_regression.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - bench_tree.py now free of pylab references - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_glm.py clean * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_glm.py clean of pl - code does not execute for extraneous reasons * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_lasso.py clean of pl - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_plot_neighbors.py clean of pl - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_plot_omp_lars.py clean of pl - code does not execute for extraneous reasons * fix: Fix bug that prevented graphs from displaying * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_plot_parallel_pairwise.py clean of pl - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_plot_ward.py clean of pl - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_sgd_regression.py clean of pl - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_tree.py clean of pl - code executes properly * docs: removed pylab references from comments * docs: removed all pylab references - replaced with matplotlib.pyplot - pl --> plt * docs: removed pylab references from comments - replaced with matplotlib.pyplot - pl --> plt * docs: removed all pylab references - replaced with matplotlib.pyplot - pl --> plt * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - mlcomp_sparse_document_classification.py clean of pl * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - plot_gpr_noisy_targets.py clean of pl - code does not execute for extraneous reasons - File "examples/gaussian_process/plot_gpr_noisy_targets.py", line 31, in <module> - from sklearn.gaussian_process import GaussianProcessRegressor - ImportError: cannot import name GaussianProcessRegressor * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - plot_gpc_isoprobability.py clean of pl - code does not execute for extraneous reasons - File "examples/gaussian_process/plot_gpc_isoprobability.py", line 24, in <module> - from sklearn.gaussian_process import GaussianProcessClassifier - ImportError: cannot import name GaussianProcessClassifier * docs: removed all pylab references - replaced with matplotlib.pyplot - pl --> plt * docs: removed all pylab references - replaced with matplotlib.pyplot * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - plot_sparse_coding.py clean of pl - code executes properly * docs: removed all pylab references - replaced with matplotlib.pyplot * docs: removed all pylab references - replaced with matplotlib.pyplot * style: Indent properly * style: indent properly * style: Indent properly * docs: Add missing .pyplot * docs: Fix typo * style: Indent properly
2016-05-10 17:34:33 +08:00
>>> import matplotlib.pyplot as plt # doctest: +SKIP
>>> plt.figure() # doctest: +SKIP
>>> np.random.seed(0)
>>> for _ in range(6): # doctest: +SKIP
2018-10-05 22:51:42 +08:00
... this_X = .1 * np.random.normal(size=(2, 1)) + X
... regr.fit(this_X, y)
... plt.plot(test, regr.predict(test)) # doctest: +SKIP
... plt.scatter(this_X, y, s=3) # doctest: +SKIP
A solution in high-dimensional statistical learning is to *shrink* the
regression coefficients to zero: any two randomly chosen set of
2012-03-08 22:21:53 +08:00
observations are likely to be uncorrelated. This is called :class:`Ridge`
regression:
.. image:: /auto_examples/linear_model/images/sphx_glr_plot_ols_ridge_variance_002.png
2012-03-08 22:21:53 +08:00
:target: ../../auto_examples/linear_model/plot_ols_ridge_variance.html
:scale: 70
:align: right
::
>>> regr = linear_model.Ridge(alpha=.1)
[MRG+1] Fix: Replace pylab with matplotlib.pyplot #6754 (#6762) * Fix: Replace pylab with matplotlib.pyplot #6754 - one instance of 22 occurrences of pylab replaced with matplotlib.pyplot - bench_glm.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - one instance of 21 remaining occurrences of pylab replaced with matplotlib.pyplot - bench_glmnet.py now free of pylab references - code does not execute for extraneous reason: ImportError: No module named glmnet.elastic_net * Fix: Replace pylab with matplotlib.pyplot #6754 - one instance of 19 occurrences of pylab replaced with matplotlib.pyplot - bench_lasso.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - one instance of 18 occurrences of pylab replaced with matplotlib.pyplot - bench_plot_neighbors.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - one instance of 17 occurrences of pylab replaced with matplotlib.pyplot - bench_plot_omp_lars.py now free of pylab references - code does not execute for extraneous reasons: - File "bench_plot_omp_lars.py", line 111, in <module> - ax = fig.add_subplot(1, 2, i) - ValueError: num must be 1 <= num <= 2, not 0 - line 111 should probably be ax = fig.add_subplot(1, 2, i+1) * Fix: Replace pylab with matplotlib.pyplot #6754 - bench_plot_parallel_pairwise.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - bench_plot_ward.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - bench_sgd_regression.py now free of pylab references - code executes properly * Fix: Replace pylab with matplotlib.pyplot #6754 - bench_tree.py now free of pylab references - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_glm.py clean * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_glm.py clean of pl - code does not execute for extraneous reasons * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_lasso.py clean of pl - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_plot_neighbors.py clean of pl - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_plot_omp_lars.py clean of pl - code does not execute for extraneous reasons * fix: Fix bug that prevented graphs from displaying * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_plot_parallel_pairwise.py clean of pl - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_plot_ward.py clean of pl - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_sgd_regression.py clean of pl - code executes properly * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - bench_tree.py clean of pl - code executes properly * docs: removed pylab references from comments * docs: removed all pylab references - replaced with matplotlib.pyplot - pl --> plt * docs: removed pylab references from comments - replaced with matplotlib.pyplot - pl --> plt * docs: removed all pylab references - replaced with matplotlib.pyplot - pl --> plt * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - mlcomp_sparse_document_classification.py clean of pl * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - plot_gpr_noisy_targets.py clean of pl - code does not execute for extraneous reasons - File "examples/gaussian_process/plot_gpr_noisy_targets.py", line 31, in <module> - from sklearn.gaussian_process import GaussianProcessRegressor - ImportError: cannot import name GaussianProcessRegressor * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - plot_gpc_isoprobability.py clean of pl - code does not execute for extraneous reasons - File "examples/gaussian_process/plot_gpc_isoprobability.py", line 24, in <module> - from sklearn.gaussian_process import GaussianProcessClassifier - ImportError: cannot import name GaussianProcessClassifier * docs: removed all pylab references - replaced with matplotlib.pyplot - pl --> plt * docs: removed all pylab references - replaced with matplotlib.pyplot * refactor: Replace pl with plt - replace instances of pl (as on import pylab as pl) with plt (as in import matplotlib.pyplot as plt) - plot_sparse_coding.py clean of pl - code executes properly * docs: removed all pylab references - replaced with matplotlib.pyplot * docs: removed all pylab references - replaced with matplotlib.pyplot * style: Indent properly * style: indent properly * style: Indent properly * docs: Add missing .pyplot * docs: Fix typo * style: Indent properly
2016-05-10 17:34:33 +08:00
>>> plt.figure() # doctest: +SKIP
>>> np.random.seed(0)
>>> for _ in range(6): # doctest: +SKIP
2018-10-05 22:51:42 +08:00
... this_X = .1 * np.random.normal(size=(2, 1)) + X
... regr.fit(this_X, y)
... plt.plot(test, regr.predict(test)) # doctest: +SKIP
... plt.scatter(this_X, y, s=3) # doctest: +SKIP
This is an example of **bias/variance tradeoff**: the larger the ridge
``alpha`` parameter, the higher the bias and the lower the variance.
We can choose ``alpha`` to minimize left out error, this time using the
2013-01-22 21:02:56 +08:00
diabetes dataset rather than our synthetic data::
>>> from __future__ import print_function
2018-10-05 22:51:42 +08:00
>>> alphas = np.logspace(-4, -1, 6)
>>> print([regr.set_params(alpha=alpha)
... .fit(diabetes_X_train, diabetes_y_train)
... .score(diabetes_X_test, diabetes_y_test)
... for alpha in alphas])
... # doctest: +ELLIPSIS, +NORMALIZE_WHITESPACE
[0.5851110683883..., 0.5852073015444..., 0.5854677540698...,
0.5855512036503..., 0.5830717085554..., 0.57058999437...]
.. note::
Capturing in the fitted parameters noise that prevents the model to
2013-01-22 21:02:56 +08:00
generalize to new data is called
2015-12-03 07:16:40 +08:00
`overfitting <https://en.wikipedia.org/wiki/Overfitting>`_. The bias introduced
2013-01-22 21:02:56 +08:00
by the ridge regression is called a
2015-12-03 07:16:40 +08:00
`regularization <https://en.wikipedia.org/wiki/Regularization_%28machine_learning%29>`_.
.. _sparsity:
Sparsity
----------
.. |diabetes_ols_1| image:: /auto_examples/linear_model/images/sphx_glr_plot_ols_3d_001.png
:target: ../../auto_examples/linear_model/plot_ols_3d.html
:scale: 65
.. |diabetes_ols_3| image:: /auto_examples/linear_model/images/sphx_glr_plot_ols_3d_003.png
:target: ../../auto_examples/linear_model/plot_ols_3d.html
:scale: 65
.. |diabetes_ols_2| image:: /auto_examples/linear_model/images/sphx_glr_plot_ols_3d_002.png
:target: ../../auto_examples/linear_model/plot_ols_3d.html
:scale: 65
.. rst-class:: centered
**Fitting only features 1 and 2**
2013-01-22 21:02:56 +08:00
.. centered:: |diabetes_ols_1| |diabetes_ols_3| |diabetes_ols_2|
.. note::
A representation of the full diabetes dataset would involve 11
dimensions (10 feature dimensions and one of the target variable). It
is hard to develop an intuition on such representation, but it may be
useful to keep in mind that it would be a fairly *empty* space.
We can see that, although feature 2 has a strong coefficient on the full
model, it conveys little information on ``y`` when considered with feature 1.
2013-01-22 21:02:56 +08:00
To improve the conditioning of the problem (i.e. mitigating the
:ref:`curse_of_dimensionality`), it would be interesting to select only the
informative features and set non-informative ones, like feature 2 to 0. Ridge
regression will decrease their contribution, but not set them to zero. Another
2013-01-22 21:02:56 +08:00
penalization approach, called :ref:`lasso` (least absolute shrinkage and
selection operator), can set some coefficients to zero. Such methods are
called **sparse method** and sparsity can be seen as an
application of Occam's razor: *prefer simpler models*.
2013-01-22 21:02:56 +08:00
::
2012-05-03 00:37:58 +08:00
>>> regr = linear_model.Lasso()
2018-10-05 22:51:42 +08:00
>>> scores = [regr.set_params(alpha=alpha)
... .fit(diabetes_X_train, diabetes_y_train)
... .score(diabetes_X_test, diabetes_y_test)
... for alpha in alphas]
2012-05-03 00:37:58 +08:00
>>> best_alpha = alphas[scores.index(max(scores))]
>>> regr.alpha = best_alpha
>>> regr.fit(diabetes_X_train, diabetes_y_train)
[MRG] Add pprint for estimators - continued (#11705) * add pprint for estimators * strip color from length, add color option * Minor cleaning, fixes, factoring and docs * Added some basic tests * Fixed line length issue * fixed flake8 and added visual test for review * Fixed test * Fixed Python 2 issues (inspect.signature import) * Trying to fix flake8 again * Added special repr for functions * Added some other visual tests * Changed _format_function in to _format_callable because callable() returns True also for class objects (which we want to reprensent with their name as well anyway) * Consistent output in Python 2 and 3 * WIP * Now using the builtin pprint module * pep8 * Added changed_only param * Fixed printing when string would fit in less than line width * Fixed printing of steps parameter * Fixed changed_only param for short estimators * fixed pep8 * Added some more description in docstring * changed_only is now an option from set_config() * Put _pprint.py into sklearn/utils, added tests * Added doctest NORMALIZE_WHITESPACE where needed * Fixed tests * fix test-doc * fixing test that passed before.... * Fixed tests * Added test for changed_only and long lines * typo * Added authors names * Added license file * Added ellipsis based on number of elements in sequence + added increasinly aggressive repr strategies * Updated whatsnew * dont use increaingly aggressive strategy * Fixed tests * Removed LICENSE file and put license text in _pprint.py * fixed test_base * Sorted parameters dictionary for consistent output in 3.5 * Actually using OrderedDict... * Addressed comments * Added test for NaN changed parameter * Update whatsnew * Added example to set_config() * Removed example * Added example in gallery * Spelling
2018-12-20 12:48:21 +08:00
... # doctest: +NORMALIZE_WHITESPACE
Lasso(alpha=0.025118864315095794, copy_X=True, fit_intercept=True,
max_iter=1000, normalize=False, positive=False, precompute=False,
random_state=None, selection='cyclic', tol=0.0001, warm_start=False)
>>> print(regr.coef_) # doctest: +NORMALIZE_WHITESPACE
[ 0. -212.43764548 517.19478111 313.77959962 -160.8303982 -0.
-187.19554705 69.38229038 508.66011217 71.84239008]
.. topic:: **Different algorithms for the same problem**
2012-05-07 05:33:55 +08:00
Different algorithms can be used to solve the same mathematical
problem. For instance the ``Lasso`` object in scikit-learn
2013-01-22 21:02:56 +08:00
solves the lasso regression problem using a
2017-02-12 23:53:58 +08:00
`coordinate descent <https://en.wikipedia.org/wiki/Coordinate_descent>`_ method,
that is efficient on large datasets. However, scikit-learn also
2017-02-18 18:29:07 +08:00
provides the :class:`LassoLars` object using the *LARS* algorithm,
which is very efficient for problems in which the weight vector estimated
is very sparse (i.e. problems with very few observations).
.. _clf_tut:
Classification
---------------
.. image:: /auto_examples/linear_model/images/sphx_glr_plot_logistic_001.png
:target: ../../auto_examples/linear_model/plot_logistic.html
:scale: 65
:align: right
2013-01-22 21:02:56 +08:00
For classification, as in the labeling
2015-12-03 07:16:40 +08:00
`iris <https://en.wikipedia.org/wiki/Iris_flower_data_set>`_ task, linear
2013-01-22 21:02:56 +08:00
regression is not the right approach as it will give too much weight to
data far from the decision frontier. A linear approach is to fit a sigmoid
function or **logistic** function:
.. math::
y = \textrm{sigmoid}(X\beta - \textrm{offset}) + \epsilon =
\frac{1}{1 + \textrm{exp}(- X\beta + \textrm{offset})} + \epsilon
::
>>> log = linear_model.LogisticRegression(solver='lbfgs', C=1e5,
... multi_class='multinomial')
>>> log.fit(iris_X_train, iris_y_train) # doctest: +NORMALIZE_WHITESPACE
2012-03-02 18:53:07 +08:00
LogisticRegression(C=100000.0, class_weight=None, dual=False,
[MRG] Add elastic net penalty to LogisticRegression (#11646) * First draft on elasticnet penaly for LogisticRegression * Some basic tests * Doc update * First draft for LogisticRegressionCV. It seems to be working for binary classification and for multiclass when multi_class='ovr'. I'm having a hard time figuring out the intricacies of multi_class='multinomial'. * Changed default to None for l1_ratio. added warning message is user sets l1_ratio while penalty is not elastic-net * Some more doc * Updated example to plot elastic net sparsity * Fixed flake8 * Fixed test by not modifying attribute in fit * Fixed doc issues * WIP * Partially fixed logistic_reg_CV for multinomial. Also added some comments that are hopefully clear. Still need to fix refit=False * Fixed doc issue * WIP * Fixed test for refit=False in LogisticRegressionCV * Fixed Python 2 numpy version issue * minor doc updates * Weird doc error... * Added test to ensure that elastic net is at least as good as L1 or L2 once l1_ratio has been optimized with grid search Also addressed minor reviews * Fixed test * addressed comments * Added back ignore warning on tests * Added a functional test * Scale data in test... Now failing * elastic-net --> elasticnet * Updated doc for some attributes and checked their shape in tests * Added l1_ratio dimension to coefs_paths and scores attr * improve example + fix test * FIX incorrect lagged_update in SAGA * Add non-regression test for SAGA's bug * FIX flake8 and warning * Re fixed warning * Updated some tests * Addressed comments * more comments and added dimension to LogisticRegressionCV.n_iter_ attribute * Updated whatsnew for 0.21 * better doc shape looks * Fixed whatnew entry after merges * Added dot * Addressed comments + standardized optional default param docstrings * Addessed comments * use swapaxes instead of unsupported moveaxis (hopefully fixes tests)
2018-11-22 09:23:57 +08:00
fit_intercept=True, intercept_scaling=1, l1_ratio=None, max_iter=100,
multi_class='multinomial', n_jobs=None, penalty='l2', random_state=None,
solver='lbfgs', tol=0.0001, verbose=0, warm_start=False)
2012-03-08 22:21:53 +08:00
This is known as :class:`LogisticRegression`.
.. image:: /auto_examples/linear_model/images/sphx_glr_plot_iris_logistic_001.png
:target: ../../auto_examples/linear_model/plot_iris_logistic.html
:scale: 83
.. topic:: Multiclass classification
If you have several classes to predict, an option often used is to fit
one-versus-all classifiers and then use a voting heuristic for the final
decision.
.. topic:: Shrinkage and sparsity with logistic regression
The ``C`` parameter controls the amount of regularization in the
:class:`LogisticRegression` object: a large value for ``C`` results in
2012-05-03 00:37:58 +08:00
less regularization.
``penalty="l2"`` gives :ref:`shrinkage` (i.e. non-sparse coefficients), while
``penalty="l1"`` gives :ref:`sparsity`.
2012-03-08 22:21:53 +08:00
.. topic:: **Exercise**
:class: green
2012-03-26 15:55:57 +08:00
Try classifying the digits dataset with nearest neighbors and a linear
model. Leave out the last 10% and test prediction performance on these
observations.
2017-06-28 23:00:13 +08:00
.. literalinclude:: ../../auto_examples/exercises/plot_digits_classification_exercise.py
:lines: 15-19
2017-06-28 23:00:13 +08:00
Solution: :download:`../../auto_examples/exercises/plot_digits_classification_exercise.py`
Support vector machines (SVMs)
================================
Linear SVMs
-------------
2012-03-08 22:21:53 +08:00
2013-01-22 21:02:56 +08:00
:ref:`svm` belong to the discriminant model family: they try to find a combination of
2012-03-08 22:21:53 +08:00
samples to build a plane maximizing the margin between the two classes.
Regularization is set by the ``C`` parameter: a small value for ``C`` means the margin
2012-05-03 00:37:58 +08:00
is calculated using many or all of the observations around the separating line
(more regularization);
a large value for ``C`` means the margin is calculated on observations close to
2012-05-03 00:37:58 +08:00
the separating line (less regularization).
2012-03-08 22:21:53 +08:00
.. currentmodule :: sklearn.svm
.. |svm_margin_unreg| image:: /auto_examples/svm/images/sphx_glr_plot_svm_margin_001.png
:target: ../../auto_examples/svm/plot_svm_margin.html
:scale: 70
.. |svm_margin_reg| image:: /auto_examples/svm/images/sphx_glr_plot_svm_margin_002.png
:target: ../../auto_examples/svm/plot_svm_margin.html
:scale: 70
.. rst-class:: centered
============================= ==============================
**Unregularized SVM** **Regularized SVM (default)**
============================= ==============================
|svm_margin_unreg| |svm_margin_reg|
============================= ==============================
2013-10-15 00:28:07 +08:00
.. topic:: Example:
- :ref:`sphx_glr_auto_examples_svm_plot_iris_svc.py`
2013-10-15 00:28:07 +08:00
2012-03-08 22:21:53 +08:00
SVMs can be used in regression --:class:`SVR` (Support Vector Regression)--, or in
2013-01-22 21:02:56 +08:00
classification --:class:`SVC` (Support Vector Classification).
::
2012-03-02 18:53:07 +08:00
>>> from sklearn import svm
>>> svc = svm.SVC(kernel='linear')
2012-10-16 22:46:48 +08:00
>>> svc.fit(iris_X_train, iris_y_train) # doctest: +NORMALIZE_WHITESPACE
SVC(C=1.0, cache_size=200, class_weight=None, coef0=0.0,
decision_function_shape='ovr', degree=3, gamma='auto_deprecated',
kernel='linear', max_iter=-1, probability=False, random_state=None,
shrinking=True, tol=0.001, verbose=False)
.. warning:: **Normalizing data**
For many estimators, including the SVMs, having datasets with unit
standard deviation for each feature is important to get good
prediction.
.. _using_kernels_tut:
Using kernels
--------------
2012-03-20 15:49:35 +08:00
Classes are not always linearly separable in feature space. The solution is to
2013-01-22 21:02:56 +08:00
build a decision function that is not linear but may be polynomial instead.
This is done using the *kernel trick* that can be seen as
creating a decision energy by positioning *kernels* on observations:
.. |svm_kernel_linear| image:: /auto_examples/svm/images/sphx_glr_plot_svm_kernels_001.png
:target: ../../auto_examples/svm/plot_svm_kernels.html
2013-01-22 21:02:56 +08:00
:scale: 65
.. |svm_kernel_poly| image:: /auto_examples/svm/images/sphx_glr_plot_svm_kernels_002.png
:target: ../../auto_examples/svm/plot_svm_kernels.html
:scale: 65
.. rst-class:: centered
.. list-table::
2013-01-22 21:02:56 +08:00
*
- **Linear kernel**
2013-01-22 21:02:56 +08:00
- **Polynomial kernel**
2013-01-22 21:02:56 +08:00
*
- |svm_kernel_linear|
- |svm_kernel_poly|
2013-01-22 21:02:56 +08:00
*
- ::
>>> svc = svm.SVC(kernel='linear')
- ::
2013-01-22 21:02:56 +08:00
>>> svc = svm.SVC(kernel='poly',
... degree=3)
>>> # degree: polynomial degree
.. |svm_kernel_rbf| image:: /auto_examples/svm/images/sphx_glr_plot_svm_kernels_003.png
:target: ../../auto_examples/svm/plot_svm_kernels.html
:scale: 65
.. rst-class:: centered
.. list-table::
2013-01-22 21:02:56 +08:00
*
- **RBF kernel (Radial Basis Function)**
2013-01-22 21:02:56 +08:00
*
- |svm_kernel_rbf|
2013-01-22 21:02:56 +08:00
*
- ::
2013-01-22 21:02:56 +08:00
>>> svc = svm.SVC(kernel='rbf')
>>> # gamma: inverse of size of
>>> # radial kernel
.. topic:: **Interactive example**
2016-01-25 07:50:40 +08:00
See the :ref:`SVM GUI <sphx_glr_auto_examples_applications_svm_gui.py>` to download
``svm_gui.py``; add data points of both classes with right and left button,
fit the model and change parameters and data.
.. image:: /auto_examples/datasets/images/sphx_glr_plot_iris_dataset_001.png
2012-05-07 05:28:06 +08:00
:target: ../../auto_examples/datasets/plot_iris_dataset.html
2012-03-08 16:06:51 +08:00
:align: right
:scale: 70
.. topic:: **Exercise**
:class: green
Try classifying classes 1 and 2 from the iris dataset with SVMs, with
the 2 first features. Leave out 10% of each class and test prediction
performance on these observations.
**Warning**: the classes are ordered, do not leave out the last 10%,
you would be testing on only one class.
**Hint**: You can use the ``decision_function`` method on a grid to get
intuitions.
.. literalinclude:: ../../auto_examples/exercises/plot_iris_exercise.py
2014-08-20 15:59:31 +08:00
:lines: 18-23
Solution: :download:`../../auto_examples/exercises/plot_iris_exercise.py`