scikit-learn/doc/modules/tree.rst

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

604 lines
24 KiB
ReStructuredText
Raw Normal View History

.. _tree:
==============
Decision Trees
==============
2011-09-04 02:54:12 +08:00
.. currentmodule:: sklearn.tree
**Decision Trees (DTs)** are a non-parametric supervised learning method used
for :ref:`classification <tree_classification>` and :ref:`regression
<tree_regression>`. The goal is to create a model that predicts the value of a
target variable by learning simple decision rules inferred from the data
features. A tree can be seen as a piecewise constant approximation.
For instance, in the example below, decision trees learn from data to
approximate a sine curve with a set of if-then-else decision rules. The deeper
the tree, the more complex the decision rules and the fitter the model.
2016-01-25 07:13:05 +08:00
.. figure:: ../auto_examples/tree/images/sphx_glr_plot_tree_regression_001.png
:target: ../auto_examples/tree/plot_tree_regression.html
:scale: 75
:align: center
Some advantages of decision trees are:
- Simple to understand and to interpret. Trees can be visualised.
2011-09-24 01:48:33 +08:00
2011-10-05 16:16:51 +08:00
- Requires little data preparation. Other techniques often require data
normalisation, dummy variables need to be created and blank values to
be removed. Note however that this module does not support missing
values.
2011-10-05 16:16:51 +08:00
- The cost of using the tree (i.e., predicting data) is logarithmic in the
2011-09-25 23:51:07 +08:00
number of data points used to train the tree.
- Able to handle both numerical and categorical data. However scikit-learn
implementation does not support categorical variables for now. Other
techniques are usually specialised in analysing datasets that have only one type
of variable. See :ref:`algorithms <tree_algorithms>` for more
information.
2011-10-05 16:16:51 +08:00
2012-07-02 20:32:27 +08:00
- Able to handle multi-output problems.
- Uses a white box model. If a given situation is observable in a model,
2011-10-05 16:16:51 +08:00
the explanation for the condition is easily explained by boolean logic.
2013-06-27 21:09:16 +08:00
By contrast, in a black box model (e.g., in an artificial neural
2011-11-20 16:19:55 +08:00
network), results may be more difficult to interpret.
2011-10-05 16:16:51 +08:00
- Possible to validate a model using statistical tests. That makes it
possible to account for the reliability of the model.
2011-10-05 16:16:51 +08:00
- Performs well even if its assumptions are somewhat violated by
the true model from which the data were generated.
2012-07-09 23:36:28 +08:00
The disadvantages of decision trees include:
2011-10-05 16:16:51 +08:00
- Decision-tree learners can create over-complex trees that do not
generalise the data well. This is called overfitting. Mechanisms
such as pruning, setting the minimum number of samples required
at a leaf node or setting the maximum depth of the tree are
necessary to avoid this problem.
2011-10-05 16:16:51 +08:00
- Decision trees can be unstable because small variations in the
data might result in a completely different tree being generated.
This problem is mitigated by using decision trees within an
ensemble.
- Predictions of decision trees are neither smooth nor continuous, but
piecewise constant approximations as seen in the above figure. Therefore,
they are not good at extrapolation.
2011-10-05 16:16:51 +08:00
- The problem of learning an optimal decision tree is known to be
NP-complete under several aspects of optimality and even for simple
concepts. Consequently, practical decision-tree learning algorithms
are based on heuristic algorithms such as the greedy algorithm where
locally optimal decisions are made at each node. Such algorithms
cannot guarantee to return the globally optimal decision tree. This
2011-10-05 16:16:51 +08:00
can be mitigated by training multiple trees in an ensemble learner,
where the features and samples are randomly sampled with replacement.
2011-10-05 16:16:51 +08:00
- There are concepts that are hard to learn because decision trees
do not express them easily, such as XOR, parity or multiplexer problems.
- Decision tree learners create biased trees if some classes dominate.
It is therefore recommended to balance the dataset prior to fitting
with the decision tree.
2012-07-02 19:20:27 +08:00
.. _tree_classification:
Classification
==============
:class:`DecisionTreeClassifier` is a class capable of performing multi-class
classification on a dataset.
As with other classifiers, :class:`DecisionTreeClassifier` takes as input two arrays:
an array X, sparse or dense, of shape ``(n_samples, n_features)`` holding the
training samples, and an array Y of integer values, shape ``(n_samples,)``,
holding the class labels for the training samples::
2011-09-04 02:54:12 +08:00
>>> from sklearn import tree
>>> X = [[0, 0], [1, 1]]
>>> Y = [0, 1]
>>> clf = tree.DecisionTreeClassifier()
2011-09-23 23:51:30 +08:00
>>> clf = clf.fit(X, Y)
2011-09-13 19:52:41 +08:00
After being fitted, the model can then be used to predict the class of samples::
>>> clf.predict([[2., 2.]])
2012-12-05 15:23:53 +08:00
array([1])
In case that there are multiple classes with the same and highest
probability, the classifier will predict the class with the lowest index
amongst those classes.
As an alternative to outputting a specific class, the probability of each class
can be predicted, which is the fraction of training samples of the class in a
leaf::
>>> clf.predict_proba([[2., 2.]])
array([[0., 1.]])
:class:`DecisionTreeClassifier` is capable of both binary (where the
labels are [-1, 1]) classification and multiclass (where the labels are
[0, ..., K-1]) classification.
2011-09-13 19:52:41 +08:00
Using the Iris dataset, we can construct a tree as follows::
2011-09-13 19:52:41 +08:00
>>> from sklearn.datasets import load_iris
>>> from sklearn import tree
2021-03-22 01:07:24 +08:00
>>> iris = load_iris()
>>> X, y = iris.data, iris.target
>>> clf = tree.DecisionTreeClassifier()
>>> clf = clf.fit(X, y)
Once trained, you can plot the tree with the :func:`plot_tree` function::
[MRG] Matplotlib tree plotting (#9251) * add reingold tillford tree layout algorithm * add first silly implementation of matplotlib based plotting for trees * object oriented design for export_graphviz so it can be extended * add class for mlp export * add colors * separately scale x and y, add arrowheads, fix strings * implement max_depth * don't use alpha for coloring because it makes boxes transparent * remove unused variables * vertical center of boxes * fix/simplify newline trimming * somewhere in the middle of stuff trying to get rid of scalex, scaley * remove "find_longest_child" for now, fix tests * make scalex and scaley internal, and ax local. render everything once to get the bbox sizes, then again to actually plot it with known extents. * add some margin to the max bbox width * add _BaseTreeExporter baseclass * add docstring to plot_tree * use data coordinates so we can put the plot in a subplot, remove some hacks. * remove scalex, scaley, add automatic font size * use rendered stuff for setting limits (well nearly there) * import plot_tree into tree module * set limits before font size adjustment? * add tree plotting via matplotlib to iris example and to docs * pep8 fix * skip doctest on plot_tree because matplotlib is not installed on all CI machines * redo everything in axis pixel coordinates re-introduce scalex, scaley add max_extents to tree to get tree size before plotting * fix max-depth parent node positioning and don't consider deep nodes in layouting * consider height in fontsize computation in case someone gave us a very flat figure * fix error when max_depth is None * add docstring for tree plotting fontsize * starting on jnothman's review * renaming fixes * whatsnew for tree plotting * clear axes prior to doing anything. * fix doctests * skip matplotlib doctest * trying to debug circle failure * trying to show full traceback * more print debugging * remove debugging crud * hack around matplotlib <1.5 issues * copy bbox args because old matplotlib is weird. * pep8 fixes * add explicit boxstyle * more pep8 * even more pep8 * add comment about matplotlib version requirement * remove redundant file * add whatsnew entry that the merge lost * fix merge issue * more merge issues * whitespace ... * remove doctest skip to see what's happening * added some simple invariance tests buchheim function * refactor ___init__ into superclass * added some tests of plot_tree * put skip back in, fix typo, fix versionadded number * remove unused parameters special_characters and parallel_leaves from mpl plotting * rename tests to test_reingold_tilford * added license header from pymag-trees repo * remove duplicate test file.
2018-10-12 03:42:02 +08:00
>>> tree.plot_tree(clf)
[...]
[MRG] Matplotlib tree plotting (#9251) * add reingold tillford tree layout algorithm * add first silly implementation of matplotlib based plotting for trees * object oriented design for export_graphviz so it can be extended * add class for mlp export * add colors * separately scale x and y, add arrowheads, fix strings * implement max_depth * don't use alpha for coloring because it makes boxes transparent * remove unused variables * vertical center of boxes * fix/simplify newline trimming * somewhere in the middle of stuff trying to get rid of scalex, scaley * remove "find_longest_child" for now, fix tests * make scalex and scaley internal, and ax local. render everything once to get the bbox sizes, then again to actually plot it with known extents. * add some margin to the max bbox width * add _BaseTreeExporter baseclass * add docstring to plot_tree * use data coordinates so we can put the plot in a subplot, remove some hacks. * remove scalex, scaley, add automatic font size * use rendered stuff for setting limits (well nearly there) * import plot_tree into tree module * set limits before font size adjustment? * add tree plotting via matplotlib to iris example and to docs * pep8 fix * skip doctest on plot_tree because matplotlib is not installed on all CI machines * redo everything in axis pixel coordinates re-introduce scalex, scaley add max_extents to tree to get tree size before plotting * fix max-depth parent node positioning and don't consider deep nodes in layouting * consider height in fontsize computation in case someone gave us a very flat figure * fix error when max_depth is None * add docstring for tree plotting fontsize * starting on jnothman's review * renaming fixes * whatsnew for tree plotting * clear axes prior to doing anything. * fix doctests * skip matplotlib doctest * trying to debug circle failure * trying to show full traceback * more print debugging * remove debugging crud * hack around matplotlib <1.5 issues * copy bbox args because old matplotlib is weird. * pep8 fixes * add explicit boxstyle * more pep8 * even more pep8 * add comment about matplotlib version requirement * remove redundant file * add whatsnew entry that the merge lost * fix merge issue * more merge issues * whitespace ... * remove doctest skip to see what's happening * added some simple invariance tests buchheim function * refactor ___init__ into superclass * added some tests of plot_tree * put skip back in, fix typo, fix versionadded number * remove unused parameters special_characters and parallel_leaves from mpl plotting * rename tests to test_reingold_tilford * added license header from pymag-trees repo * remove duplicate test file.
2018-10-12 03:42:02 +08:00
.. figure:: ../auto_examples/tree/images/sphx_glr_plot_iris_dtc_002.png
:target: ../auto_examples/tree/plot_iris_dtc.html
[MRG] Matplotlib tree plotting (#9251) * add reingold tillford tree layout algorithm * add first silly implementation of matplotlib based plotting for trees * object oriented design for export_graphviz so it can be extended * add class for mlp export * add colors * separately scale x and y, add arrowheads, fix strings * implement max_depth * don't use alpha for coloring because it makes boxes transparent * remove unused variables * vertical center of boxes * fix/simplify newline trimming * somewhere in the middle of stuff trying to get rid of scalex, scaley * remove "find_longest_child" for now, fix tests * make scalex and scaley internal, and ax local. render everything once to get the bbox sizes, then again to actually plot it with known extents. * add some margin to the max bbox width * add _BaseTreeExporter baseclass * add docstring to plot_tree * use data coordinates so we can put the plot in a subplot, remove some hacks. * remove scalex, scaley, add automatic font size * use rendered stuff for setting limits (well nearly there) * import plot_tree into tree module * set limits before font size adjustment? * add tree plotting via matplotlib to iris example and to docs * pep8 fix * skip doctest on plot_tree because matplotlib is not installed on all CI machines * redo everything in axis pixel coordinates re-introduce scalex, scaley add max_extents to tree to get tree size before plotting * fix max-depth parent node positioning and don't consider deep nodes in layouting * consider height in fontsize computation in case someone gave us a very flat figure * fix error when max_depth is None * add docstring for tree plotting fontsize * starting on jnothman's review * renaming fixes * whatsnew for tree plotting * clear axes prior to doing anything. * fix doctests * skip matplotlib doctest * trying to debug circle failure * trying to show full traceback * more print debugging * remove debugging crud * hack around matplotlib <1.5 issues * copy bbox args because old matplotlib is weird. * pep8 fixes * add explicit boxstyle * more pep8 * even more pep8 * add comment about matplotlib version requirement * remove redundant file * add whatsnew entry that the merge lost * fix merge issue * more merge issues * whitespace ... * remove doctest skip to see what's happening * added some simple invariance tests buchheim function * refactor ___init__ into superclass * added some tests of plot_tree * put skip back in, fix typo, fix versionadded number * remove unused parameters special_characters and parallel_leaves from mpl plotting * rename tests to test_reingold_tilford * added license header from pymag-trees repo * remove duplicate test file.
2018-10-12 03:42:02 +08:00
:scale: 75
:align: center
We can also export the tree in `Graphviz
<https://www.graphviz.org/>`_ format using the :func:`export_graphviz`
exporter. If you use the `conda <https://conda.io>`_ package manager, the graphviz binaries
and the python package can be installed with `conda install python-graphviz`.
Alternatively binaries for graphviz can be downloaded from the graphviz project homepage,
and the Python wrapper installed from pypi with `pip install graphviz`.
Below is an example graphviz export of the above tree trained on the entire
iris dataset; the results are saved in an output file `iris.pdf`::
2012-12-17 02:30:15 +08:00
>>> import graphviz # doctest: +SKIP
>>> dot_data = tree.export_graphviz(clf, out_file=None) # doctest: +SKIP
>>> graph = graphviz.Source(dot_data) # doctest: +SKIP
>>> graph.render("iris") # doctest: +SKIP
The :func:`export_graphviz` exporter also supports a variety of aesthetic
options, including coloring nodes by their class (or value for regression) and
using explicit variable and class names if desired. Jupyter notebooks also
render these plots inline automatically::
2016-09-22 09:16:36 +08:00
>>> dot_data = tree.export_graphviz(clf, out_file=None, # doctest: +SKIP
2018-10-05 22:51:42 +08:00
... feature_names=iris.feature_names, # doctest: +SKIP
... class_names=iris.target_names, # doctest: +SKIP
... filled=True, rounded=True, # doctest: +SKIP
... special_characters=True) # doctest: +SKIP
>>> graph = graphviz.Source(dot_data) # doctest: +SKIP
>>> graph # doctest: +SKIP
.. only:: html
.. figure:: ../images/iris.svg
:align: center
.. only:: latex
.. figure:: ../images/iris.pdf
:align: center
.. figure:: ../auto_examples/tree/images/sphx_glr_plot_iris_dtc_001.png
:target: ../auto_examples/tree/plot_iris_dtc.html
:align: center
:scale: 75
Alternatively, the tree can also be exported in textual format with the
function :func:`export_text`. This method doesn't require the installation
of external libraries and is more compact:
>>> from sklearn.datasets import load_iris
>>> from sklearn.tree import DecisionTreeClassifier
>>> from sklearn.tree import export_text
>>> iris = load_iris()
>>> decision_tree = DecisionTreeClassifier(random_state=0, max_depth=2)
>>> decision_tree = decision_tree.fit(iris.data, iris.target)
>>> r = export_text(decision_tree, feature_names=iris['feature_names'])
>>> print(r)
|--- petal width (cm) <= 0.80
| |--- class: 0
|--- petal width (cm) > 0.80
| |--- petal width (cm) <= 1.75
| | |--- class: 1
| |--- petal width (cm) > 1.75
| | |--- class: 2
<BLANKLINE>
.. topic:: Examples:
* :ref:`sphx_glr_auto_examples_tree_plot_iris_dtc.py`
* :ref:`sphx_glr_auto_examples_tree_plot_unveil_tree_structure.py`
2012-07-02 19:20:27 +08:00
.. _tree_regression:
Regression
==========
2016-01-25 07:13:05 +08:00
.. figure:: ../auto_examples/tree/images/sphx_glr_plot_tree_regression_001.png
:target: ../auto_examples/tree/plot_tree_regression.html
:scale: 75
:align: center
Decision trees can also be applied to regression problems, using the
:class:`DecisionTreeRegressor` class.
As in the classification setting, the fit method will take as argument arrays X
and y, only that in this case y is expected to have floating point values
instead of integer values::
2011-09-04 02:54:12 +08:00
>>> from sklearn import tree
>>> X = [[0, 0], [2, 2]]
>>> y = [0.5, 2.5]
>>> clf = tree.DecisionTreeRegressor()
>>> clf = clf.fit(X, y)
>>> clf.predict([[1, 1]])
array([0.5])
.. topic:: Examples:
2016-01-25 07:18:26 +08:00
* :ref:`sphx_glr_auto_examples_tree_plot_tree_regression.py`
2012-07-02 19:20:27 +08:00
2012-07-02 20:32:27 +08:00
.. _tree_multioutput:
Multi-output problems
=====================
A multi-output problem is a supervised learning problem with several outputs
to predict, that is when Y is a 2d array of shape ``(n_samples, n_outputs)``.
2012-07-02 20:32:27 +08:00
When there is no correlation between the outputs, a very simple way to solve
this kind of problem is to build n independent models, i.e. one for each
2012-07-02 20:32:27 +08:00
output, and then to use those models to independently predict each one of the n
outputs. However, because it is likely that the output values related to the
same input are themselves correlated, an often better way is to build a single
2012-07-03 14:48:16 +08:00
model capable of predicting simultaneously all n outputs. First, it requires
lower training time since only a single estimator is built. Second, the
generalization accuracy of the resulting estimator may often be increased.
2012-07-02 20:32:27 +08:00
With regard to decision trees, this strategy can readily be used to support
multi-output problems. This requires the following changes:
2012-07-02 20:32:27 +08:00
- Store n output values in leaves, instead of 1;
- Use splitting criteria that compute the average reduction across all
n outputs.
2012-07-02 21:18:59 +08:00
This module offers support for multi-output problems by implementing this
2012-07-02 20:32:27 +08:00
strategy in both :class:`DecisionTreeClassifier` and
:class:`DecisionTreeRegressor`. If a decision tree is fit on an output array Y
of shape ``(n_samples, n_outputs)`` then the resulting estimator will:
2012-07-02 20:32:27 +08:00
2012-07-09 23:36:28 +08:00
* Output n_output values upon ``predict``;
* Output a list of n_output arrays of class probabilities upon
2012-07-02 20:32:27 +08:00
``predict_proba``.
2012-07-09 23:36:28 +08:00
The use of multi-output trees for regression is demonstrated in
2016-01-25 07:18:26 +08:00
:ref:`sphx_glr_auto_examples_tree_plot_tree_regression_multioutput.py`. In this example, the input
X is a single real value and the outputs Y are the sine and cosine of X.
2016-01-25 07:13:05 +08:00
.. figure:: ../auto_examples/tree/images/sphx_glr_plot_tree_regression_multioutput_001.png
:target: ../auto_examples/tree/plot_tree_regression_multioutput.html
:scale: 75
:align: center
The use of multi-output trees for classification is demonstrated in
:ref:`sphx_glr_auto_examples_miscellaneous_plot_multioutput_face_completion.py`. In this example, the inputs
2012-07-04 19:37:42 +08:00
X are the pixels of the upper half of faces and the outputs Y are the pixels of
the lower half of those faces.
.. figure:: ../auto_examples/miscellaneous/images/sphx_glr_plot_multioutput_face_completion_001.png
:target: ../auto_examples/miscellaneous/plot_multioutput_face_completion.html
2012-07-04 19:37:42 +08:00
:scale: 75
:align: center
.. topic:: Examples:
2016-01-25 07:18:26 +08:00
* :ref:`sphx_glr_auto_examples_tree_plot_tree_regression_multioutput.py`
* :ref:`sphx_glr_auto_examples_miscellaneous_plot_multioutput_face_completion.py`
2012-07-04 18:02:22 +08:00
.. topic:: References:
2012-12-05 15:23:53 +08:00
* M. Dumont et al, `Fast multi-class image annotation with random subwindows
and multiple output randomized trees
<http://www.montefiore.ulg.ac.be/services/stochastic/pubs/2009/DMWG09/dumont-visapp09-shortpaper.pdf>`_, International Conference on
Computer Vision Theory and Applications 2009
2012-07-02 20:32:27 +08:00
.. _tree_complexity:
Complexity
==========
2011-09-25 23:36:42 +08:00
In general, the run time cost to construct a balanced binary tree is
:math:`O(n_{samples}n_{features}\log(n_{samples}))` and query time
:math:`O(\log(n_{samples}))`. Although the tree construction algorithm attempts
to generate balanced trees, they will not always be balanced. Assuming that the
subtrees remain approximately balanced, the cost at each node consists of
searching through :math:`O(n_{features})` to find the feature that offers the
largest reduction in entropy. This has a cost of
:math:`O(n_{features}n_{samples}\log(n_{samples}))` at each node, leading to a
total cost over the entire trees (by summing the cost at each node) of
:math:`O(n_{features}n_{samples}^{2}\log(n_{samples}))`.
2011-10-05 16:16:51 +08:00
Tips on practical use
=====================
2012-07-02 19:20:27 +08:00
* Decision trees tend to overfit on data with a large number of features.
2011-10-05 16:16:51 +08:00
Getting the right ratio of samples to number of features is important, since
a tree with few samples in high dimensional space is very likely to overfit.
2011-10-05 16:16:51 +08:00
* Consider performing dimensionality reduction (:ref:`PCA <PCA>`,
:ref:`ICA <ICA>`, or :ref:`feature_selection`) beforehand to
give your tree a better chance of finding features that are discriminative.
2011-10-05 16:16:51 +08:00
* :ref:`sphx_glr_auto_examples_tree_plot_unveil_tree_structure.py` will help
in gaining more insights about how the decision tree makes predictions, which is
important for understanding the important features in the data.
* Visualise your tree as you are training by using the ``export``
function. Use ``max_depth=3`` as an initial tree depth to get a feel for
2011-10-05 16:16:51 +08:00
how the tree is fitting to your data, and then increase the depth.
* Remember that the number of samples required to populate the tree doubles
for each additional level the tree grows to. Use ``max_depth`` to control
2011-10-05 16:16:51 +08:00
the size of the tree to prevent overfitting.
* Use ``min_samples_split`` or ``min_samples_leaf`` to ensure that multiple
samples inform every decision in the tree, by controlling which splits will
be considered. A very small number will usually mean the tree will overfit,
whereas a large number will prevent the tree from learning the data. Try
``min_samples_leaf=5`` as an initial value. If the sample size varies
greatly, a float number can be used as percentage in these two parameters.
While ``min_samples_split`` can create arbitrarily small leaves,
``min_samples_leaf`` guarantees that each leaf has a minimum size, avoiding
low-variance, over-fit leaf nodes in regression problems. For
classification with few classes, ``min_samples_leaf=1`` is often the best
choice.
Note that ``min_samples_split`` considers samples directly and independent of
``sample_weight``, if provided (e.g. a node with m weighted samples is still
treated as having exactly m samples). Consider ``min_weight_fraction_leaf`` or
``min_impurity_decrease`` if accounting for sample weights is required at splits.
* Balance your dataset before training to prevent the tree from being biased
toward the classes that are dominant. Class balancing can be done by
sampling an equal number of samples from each class, or preferably by
normalizing the sum of the sample weights (``sample_weight``) for each
class to the same value. Also note that weight-based pre-pruning criteria,
such as ``min_weight_fraction_leaf``, will then be less biased toward
dominant classes than criteria that are not aware of the sample weights,
like ``min_samples_leaf``.
* If the samples are weighted, it will be easier to optimize the tree
structure using weight-based pre-pruning criterion such as
``min_weight_fraction_leaf``, which ensure that leaf nodes contain at least
a fraction of the overall sum of the sample weights.
2011-09-24 01:48:33 +08:00
2013-07-11 17:06:02 +08:00
* All decision trees use ``np.float32`` arrays internally.
If training data is not in this format, a copy of the dataset will be made.
* If the input matrix X is very sparse, it is recommended to convert to sparse
2015-10-31 18:19:31 +08:00
``csc_matrix`` before calling fit and sparse ``csr_matrix`` before calling
predict. Training time can be orders of magnitude faster for a sparse
matrix input compared to a dense matrix when features have zero values in
most of the samples.
2011-09-13 19:52:41 +08:00
.. _tree_algorithms:
Tree algorithms: ID3, C4.5, C5.0 and CART
2011-09-25 23:36:42 +08:00
==========================================
What are all the various decision tree algorithms and how do they differ
from each other? Which one is implemented in scikit-learn?
ID3_ (Iterative Dichotomiser 3) was developed in 1986 by Ross Quinlan.
The algorithm creates a multiway tree, finding for each node (i.e. in
a greedy manner) the categorical feature that will yield the largest
information gain for categorical targets. Trees are grown to their
maximum size and then a pruning step is usually applied to improve the
ability of the tree to generalise to unseen data.
C4.5 is the successor to ID3 and removed the restriction that features
must be categorical by dynamically defining a discrete attribute (based
on numerical variables) that partitions the continuous attribute value
into a discrete set of intervals. C4.5 converts the trained trees
(i.e. the output of the ID3 algorithm) into sets of if-then rules.
These accuracy of each rule is then evaluated to determine the order
in which they should be applied. Pruning is done by removing a rule's
precondition if the accuracy of the rule improves without it.
2011-10-05 16:16:51 +08:00
C5.0 is Quinlan's latest version release under a proprietary license.
It uses less memory and builds smaller rulesets than C4.5 while being
more accurate.
CART_ (Classification and Regression Trees) is very similar to C4.5, but
it differs in that it supports numerical target variables (regression) and
does not compute rule sets. CART constructs binary trees using the feature
and threshold that yield the largest information gain at each node.
2011-09-13 19:52:41 +08:00
scikit-learn uses an optimised version of the CART algorithm; however, scikit-learn
implementation does not support categorical variables for now.
2015-12-03 07:16:40 +08:00
.. _ID3: https://en.wikipedia.org/wiki/ID3_algorithm
.. _CART: https://en.wikipedia.org/wiki/Predictive_analytics#Classification_and_regression_trees_.28CART.29
2012-07-02 19:20:27 +08:00
.. _tree_mathematical_formulation:
Mathematical formulation
========================
2011-10-05 16:16:51 +08:00
Given training vectors :math:`x_i \in R^n`, i=1,..., l and a label vector
:math:`y \in R^l`, a decision tree recursively partitions the feature space
such that the samples with the same labels or similar target values are grouped
together.
Let the data at node :math:`m` be represented by :math:`Q_m` with :math:`N_m`
samples. For each candidate split :math:`\theta = (j, t_m)` consisting of a
feature :math:`j` and threshold :math:`t_m`, partition the data into
:math:`Q_m^{left}(\theta)` and :math:`Q_m^{right}(\theta)` subsets
.. math::
2011-10-05 16:16:51 +08:00
Q_m^{left}(\theta) = \{(x, y) | x_j <= t_m\}
2011-10-05 16:16:51 +08:00
Q_m^{right}(\theta) = Q_m \setminus Q_m^{left}(\theta)
The quality of a candidate split of node :math:`m` is then computed using an
impurity function or loss function :math:`H()`, the choice of which depends on
the task being solved (classification or regression)
.. math::
G(Q_m, \theta) = \frac{N_m^{left}}{N_m} H(Q_m^{left}(\theta))
+ \frac{N_m^{right}}{N_m} H(Q_m^{right}(\theta))
Select the parameters that minimises the impurity
.. math::
\theta^* = \operatorname{argmin}_\theta G(Q_m, \theta)
2011-10-05 16:16:51 +08:00
Recurse for subsets :math:`Q_m^{left}(\theta^*)` and
:math:`Q_m^{right}(\theta^*)` until the maximum allowable depth is reached,
2013-05-07 14:07:29 +08:00
:math:`N_m < \min_{samples}` or :math:`N_m = 1`.
Classification criteria
-----------------------
If a target is a classification outcome taking on values 0,1,...,K-1,
for node :math:`m`, let
.. math::
p_{mk} = 1/ N_m \sum_{y \in Q_m} I(y = k)
be the proportion of class k observations in node :math:`m`. If :math:`m` is a
terminal node, `predict_proba` for this region is set to :math:`p_{mk}`.
Common measures of impurity are the following.
Gini:
.. math::
H(Q_m) = \sum_k p_{mk} (1 - p_{mk})
Entropy:
.. math::
H(Q_m) = - \sum_k p_{mk} \log(p_{mk})
Misclassification:
.. math::
H(Q_m) = 1 - \max(p_{mk})
Regression criteria
-------------------
If the target is a continuous value, then for node :math:`m`, common
criteria to minimize as for determining locations for future splits are Mean
Squared Error (MSE or L2 error), Poisson deviance as well as Mean Absolute
Error (MAE or L1 error). MSE and Poisson deviance both set the predicted value
of terminal nodes to the learned mean value :math:`\bar{y}_m` of the node
whereas the MAE sets the predicted value of terminal nodes to the median
:math:`median(y)_m`.
Mean Squared Error:
.. math::
\bar{y}_m = \frac{1}{N_m} \sum_{y \in Q_m} y
H(Q_m) = \frac{1}{N_m} \sum_{y \in Q_m} (y - \bar{y}_m)^2
Half Poisson deviance:
.. math::
H(Q_m) = \frac{1}{N_m} \sum_{y \in Q_m} (y \log\frac{y}{\bar{y}_m}
- y + \bar{y}_m)
Setting `criterion="poisson"` might be a good choice if your target is a count
or a frequency (count per some unit). In any case, :math:`y >= 0` is a
necessary condition to use this criterion. Note that it fits much slower than
the MSE criterion.
2011-09-24 01:48:33 +08:00
Mean Absolute Error:
.. math::
median(y)_m = \underset{y \in Q_m}{\mathrm{median}}(y)
H(Q_m) = \frac{1}{N_m} \sum_{y \in Q_m} |y - median(y)_m|
Note that it fits much slower than the MSE criterion.
2011-09-13 19:52:41 +08:00
.. _minimal_cost_complexity_pruning:
Minimal Cost-Complexity Pruning
===============================
Minimal cost-complexity pruning is an algorithm used to prune a tree to avoid
over-fitting, described in Chapter 3 of [BRE]_. This algorithm is parameterized
by :math:`\alpha\ge0` known as the complexity parameter. The complexity
parameter is used to define the cost-complexity measure, :math:`R_\alpha(T)` of
a given tree :math:`T`:
.. math::
R_\alpha(T) = R(T) + \alpha|\widetilde{T}|
where :math:`|\widetilde{T}|` is the number of terminal nodes in :math:`T` and :math:`R(T)`
is traditionally defined as the total misclassification rate of the terminal
nodes. Alternatively, scikit-learn uses the total sample weighted impurity of
the terminal nodes for :math:`R(T)`. As shown above, the impurity of a node
depends on the criterion. Minimal cost-complexity pruning finds the subtree of
:math:`T` that minimizes :math:`R_\alpha(T)`.
The cost complexity measure of a single node is
:math:`R_\alpha(t)=R(t)+\alpha`. The branch, :math:`T_t`, is defined to be a
tree where node :math:`t` is its root. In general, the impurity of a node
is greater than the sum of impurities of its terminal nodes,
:math:`R(T_t)<R(t)`. However, the cost complexity measure of a node,
:math:`t`, and its branch, :math:`T_t`, can be equal depending on
:math:`\alpha`. We define the effective :math:`\alpha` of a node to be the
value where they are equal, :math:`R_\alpha(T_t)=R_\alpha(t)` or
:math:`\alpha_{eff}(t)=\frac{R(t)-R(T_t)}{|T|-1}`. A non-terminal node
with the smallest value of :math:`\alpha_{eff}` is the weakest link and will
be pruned. This process stops when the pruned tree's minimal
:math:`\alpha_{eff}` is greater than the ``ccp_alpha`` parameter.
.. topic:: Examples:
* :ref:`sphx_glr_auto_examples_tree_plot_cost_complexity_pruning.py`
.. topic:: References:
.. [BRE] L. Breiman, J. Friedman, R. Olshen, and C. Stone. Classification
and Regression Trees. Wadsworth, Belmont, CA, 1984.
2015-12-03 07:16:40 +08:00
* https://en.wikipedia.org/wiki/Decision_tree_learning
2015-12-03 07:16:40 +08:00
* https://en.wikipedia.org/wiki/Predictive_analytics
* J.R. Quinlan. C4. 5: programs for machine learning. Morgan
Kaufmann, 1993.
* T. Hastie, R. Tibshirani and J. Friedman. Elements of Statistical
Learning, Springer, 2009.