Binary tree

File:Binary tree v2.svg

A labeled binary tree of size 9 (the number of nodes in the tree) and height 3 (the height of a tree defined as the number of edges or links from the top-most or root node to the farthest leaf node), with a root node whose value is 1. The above tree is unbalanced and not sorted.

In computer science, a binary tree is a tree data structure in which each node has at most two children, referred to as the left child and the right child. That is, it is a k-ary tree with Template:Math. A recursive definition using set theory is that a binary tree is a triple Template:Nowrap, where L and R are binary trees or the empty set and S is a singleton (a single–element set) containing the root.<ref name="GarnierTaylor2009">Template:Cite book</ref><ref name="Skiena2009">Template:Cite book</ref>

From a graph theory perspective, binary trees as defined here are arborescences.<ref name="Knuth1997">Template:Cite book</ref> A binary tree may thus be also called a bifurcating arborescence,<ref name="Knuth1997"/> a term which appears in some early programming books<ref name="Flores1971">Template:Cite book</ref> before the modern computer science terminology prevailed. It is also possible to interpret a binary tree as an undirected, rather than directed graph, in which case a binary tree is an ordered, rooted tree.<ref>Template:Cite book</ref> Some authors use rooted binary tree instead of binary tree to emphasize the fact that the tree is rooted, but as defined above, a binary tree is always rooted.<ref name="Mazur2010">Template:Cite book</ref>

In mathematics, what is termed binary tree can vary significantly from author to author. Some use the definition commonly used in computer science,<ref name="oem"/> but others define it as every non-leaf having exactly two children and don't necessarily label the children as left and right either.<ref name="Foulds1992">Template:Cite book</ref>

In computing, binary trees can be used in two very different ways:

• First, as a means of accessing nodes based on some value or label associated with each node.<ref name="Makinson2009b">Template:Cite book</ref> Binary trees labelled this way are used to implement binary search trees and binary heaps, and are used for efficient searching and sorting. The designation of non-root nodes as left or right child even when there is only one child present matters in some of these applications, in particular, it is significant in binary search trees.<ref name="Gross2007">Template:Cite book</ref> However, the arrangement of particular nodes into the tree is not part of the conceptual information. For example, in a normal binary search tree the placement of nodes depends almost entirely on the order in which they were added, and can be re-arranged (for example by balancing) without changing the meaning.
• Second, as a representation of data with a relevant bifurcating structure. In such cases, the particular arrangement of nodes under and/or to the left or right of other nodes is part of the information (that is, changing it would change the meaning). Common examples occur with Huffman coding and cladograms. The everyday division of documents into chapters, sections, paragraphs, and so on is an analogous example with n-ary rather than binary trees.

Definitions

Recursive definition

Template:Section rewrite To define a binary tree, the possibility that only one of the children may be empty must be acknowledged. An artifact, which in some textbooks is called an extended binary tree, is needed for that purpose. An extended binary tree is thus recursively defined as:<ref name="Rosen2011"/>

• the empty set is an extended binary tree
• if T₁ and T₂ are extended binary trees, then denote by T₁ • T₂ the extended binary tree obtained by Template:Clarify by adding edges when these sub-trees are non-empty.

Another way of imagining this construction (and understanding the terminology) is to consider instead of the empty set a different type of node—for instance square nodes if the regular ones are circles.<ref name="HuShing2002">Template:Cite book</ref>

Using graph theory concepts

A binary tree is a rooted tree that is also an ordered tree (a.k.a. plane tree) in which every node has at most two children. A rooted tree naturally imparts a notion of levels (distance from the root); thus, for every node, a notion of children may be defined as the nodes connected to it a level below. Ordering of these children (e.g., by drawing them on a plane) makes it possible to distinguish a left child from a right child.<ref name="HsuLin2008">Template:Cite book</ref> But this still does not distinguish between a node with left but not a right child from a node with right but no left child.

The necessary distinction can be made by first partitioning the edges; i.e., defining the binary tree as triplet (V, E₁, E₂), where (V, E₁ ∪ E₂) is a rooted tree (equivalently arborescence) and E₁ ∩ E₂ is empty, and also requiring that for all j ∈ { 1, 2 }, every node has at most one E_j child.<ref name="FlumGrohe2006">Template:Cite book</ref> A more informal way of making the distinction is to say, quoting the Encyclopedia of Mathematics, that "every node has a left child, a right child, neither, or both" and to specify that these "are all different" binary trees.<ref name="oem">Template:SpringerEOM also in print as Template:Cite book</ref>

Types of binary trees

Tree terminology is not well-standardized and therefore may vary among examples in the available literature.

• A Template:Visible anchor binary tree has a root node and every node has at most two children.

File:Full binary.svg

A full binary tree

File:Waldburg Ahnentafel.jpg

An ancestry chart which can be mapped to a perfect 4-level binary tree.

• A Template:Visible anchor binary tree (sometimes referred to as a proper,<ref>Template:Cite book</ref> plane, or strict binary tree)<ref>{{#invoke:citation/CS1|citation

|CitationClass=web }}</ref><ref>Richard Stanley, Enumerative Combinatorics, volume 2, p.36</ref> is a tree in which every node has either 0 or 2 children. Another way of defining a full binary tree is a recursive definition. A full binary tree is either:<ref name="Rosen2011">Template:Cite book</ref>

• • A single vertex (a single node as the root node).
  • A tree whose root node has two subtrees, both of which are full binary trees.
• A Template:Visible anchor binary tree is a binary tree in which all interior nodes have two children and all leaves have the same depth or same level (the level of a node defined as the number of edges or links from the root node to a node).<ref>{{#invoke:citation/CS1|citation

|CitationClass=web }}</ref> A perfect binary tree is a full binary tree.

• A Template:Visible anchor binary tree is a binary tree in which every level, except possibly the last, is completely filled, and all nodes in the last level are as far left as possible. It can have between 1 and 2^h nodes at the last level h.<ref name="complete binary tree">{{#invoke:citation/CS1|citation

|CitationClass=web }}</ref> A perfect tree is therefore always complete but a complete tree is not always perfect. Some authors use the term complete to refer instead to a perfect binary tree as defined above, in which case they call this type of tree (with a possibly not filled last level) an almost complete binary tree or nearly complete binary tree.<ref name="almost complete binary tree">{{#invoke:citation/CS1|citation |CitationClass=web }}</ref><ref name="nearly complete binary tree">{{#invoke:citation/CS1|citation |CitationClass=web }}</ref> A complete binary tree can be efficiently represented using an array.<ref name="complete binary tree"/>

File:Complete binary2.svg

A complete binary tree (that is not full)

• The infinite complete binary tree is a tree with <math>{\aleph_0}</math> levels, where for each level d the number of existing nodes at level d is equal to 2^d. The cardinal number of the set of all levels is <math>{\aleph_0}</math> (countably infinite). The cardinal number of the set of all paths (the "leaves", so to speak) is uncountable, having the cardinality of the continuum.
• A balanced binary tree is a binary tree structure in which the left and right subtrees of every node differ in height (the number of edges from the top-most node to the farthest node in a subtree) by no more than 1 (or the skew is no greater than 1).<ref>Aaron M. Tenenbaum, et al. Data Structures Using C, Prentice Hall, 1990 Template:ISBN</ref> One may also consider binary trees where no leaf is much farther away from the root than any other leaf. (Different balancing schemes allow different definitions of "much farther".<ref>Paul E. Black (ed.), entry for data structure in Dictionary of Algorithms and Data Structures. U.S. National Institute of Standards and Technology. 15 December 2004. Online version Template:Webarchive Accessed 2010-12-19.</ref>)
• A degenerate (or pathological) tree is where each parent node has only one associated child node.<ref>{{#invoke:citation/CS1|citation

|CitationClass=web }}</ref> This means that the tree will behave like a linked list data structure. In this case, an advantage of using a binary tree is significantly reduced because it is essentially a linked list which time complexity is O(n) (n as the number of nodes and 'O()' being the Big O notation) and it has more data space than the linked list due to two pointers per node, while the complexity of Template:Nowrap for data search in a balanced binary tree is normally expected.

Properties of binary trees

• The number of nodes Template:Mvar in a full binary tree is at least <math>2h+1</math> and at most <math>2^{h+1}-1 </math> (i.e., the number of nodes in a perfect binary tree), where Template:Mvar is the height of the tree. A tree consisting of only a root node has a height of 0. The least number of nodes is obtained by adding only two children nodes per adding height so <math>2h+1</math> (1 for counting the root node). The maximum number of nodes is obtained by fully filling nodes at each level, i.e., it is a perfect tree. For a perfect tree, the number of nodes is <math>1 + 2 + 4 + \ldots + 2^h = 2^{h + 1} - 1</math>, where the last equality is from the geometric series sum.
• The number of leaf nodes Template:Mvar in a perfect binary tree is <math>l = (n + 1) / 2</math> (where Template:Mvar is the number of nodes in the tree) because <math>n={{2}^{h+1}}-1</math> (by using the above property) and the number of leaves is <math>2^h</math> so <math>n=2\cdot {{2}^{h}}-1=2l-1\to l=\left( n+1 \right)/2</math>. It also means that <math>n = 2l - 1</math>. In terms of the tree height Template:Mvar, <math>l = (2^{h+1}-1 + 1) / 2 = 2^h</math>.
• For any non-empty binary tree with <math>l </math> leaf nodes and <math>i_2 </math> nodes of degree 2 (internal nodes with two child nodes), <math>l = i_2 + 1 </math>.<ref>Template:Cite book</ref> The proof is the following. For a perfect binary tree, the total number of nodes is <math>n = 2^{h+1}-1 </math> (A perfect binary tree is a full binary tree.) and <math>l = 2^h</math>, so <math>i = n - l = (2^{h+1}-1) - 2^h = 2^h - 1 = l - 1 \to l = i + 1 </math>. To make a full binary tree from a perfect binary tree, a pair of two sibling nodes are removed one by one. This results in "two leaf nodes removed" and "one internal node removed" and "the removed internal node becoming a leaf node", so one leaf node and one internal node is removed per removing two sibling nodes. As a result, <math>l = i + 1</math> also holds for a full binary tree. To make a binary tree with a leaf node without its sibling, a single leaf node is removed from a full binary tree, then "one leaf node removed" and "one internal nodes with two children removed" so <math>l = i + 1</math> also holds. This relation now covers all non-empty binary trees.
• With given Template:Mvar nodes, the minimum possible tree height is <math>h_{\min} = \log_2 (n+1)-1 </math> with which the tree is a balanced full tree or perfect tree. With a given height Template:Mvar, the number of nodes can't exceed the <math>2^{h+1}-1 </math> as the number of nodes in a perfect tree. Thus <math>n \leq 2^{h + 1} - 1 \to h \geq \log _2 (n + 1) - 1</math>.
• A binary Tree with Template:Mvar leaves has at least the height <math>h_m = \log_2 (l)</math>. With a given height Template:Mvar, the number of leaves at that height can't exceed <math>2^h</math> as the number of leaves at the height in a perfect tree. Thus <math>l \leq 2^h \to h \geq \log_2 (l)</math>.
• In a non-empty binary tree, if Template:Mvar is the total number of nodes and Template:Mvar is the total number of edges, then <math>e = n - 1</math>. This is obvious because each node requires one edge except for the root node.
• The number of null links (i.e., absent children of the nodes) in a binary tree of Template:Mvar nodes is Template:Math.
• The number of internal nodes in a complete binary tree of Template:Mvar nodes is <math>\lfloor n/2\rfloor </math>.

Combinatorics

{{ safesubst:#invoke:Unsubst||date=__DATE__ |$B= {{ safesubst:#invoke:Unsubst||date=__DATE__ |$B= Template:Ambox }} }} In combinatorics, one considers the problem of counting the number of full binary trees of a given size. Here the trees have no values attached to their nodes (this would just multiply the number of possible trees by an easily determined factor), and trees are distinguished only by their structure; however, the left and right child of any node are distinguished (if they are different trees, then interchanging them will produce a tree distinct from the original one). The size of the tree is taken to be the number n of internal nodes (those with two children); the other nodes are leaf nodes and there are Template:Math of them. The number of such binary trees of size n is equal to the number of ways of fully parenthesizing a string of Template:Math symbols (representing leaves) separated by n binary operators (representing internal nodes), to determine the argument subexpressions of each operator. For instance for Template:Math one has to parenthesize a string like Template:Tmath, which is possible in five ways:

<math display=block>((X*X)*X)*X,\qquad (X*(X*X))*X,\qquad (X*X)*(X*X),\qquad X*((X*X)*X),\qquad X*(X*(X*X)).</math>

The correspondence to binary trees should be obvious, and the addition of redundant parentheses (around an already parenthesized expression or around the full expression) is disallowed (or at least not counted as producing a new possibility).

There is a unique binary tree of size 0 (consisting of a single leaf), and any other binary tree is characterized by the pair of its left and right children; if these have sizes i and j respectively, the full tree has size Template:Math. Therefore, the number <math>C_n</math> of binary trees of size n has the following recursive description <math>C_0=1</math>, and <math>\textstyle C_n=\sum_{i=0}^{n-1}C_iC_{n-1-i}</math> for any positive integer n. It follows that <math>C_n</math> is the Catalan number of index n.

The above parenthesized strings should not be confused with the set of words of length 2n in the Dyck language, which consist only of parentheses in such a way that they are properly balanced. The number of such strings satisfies the same recursive description (each Dyck word of length 2n is determined by the Dyck subword enclosed by the initial '(' and its matching ')' together with the Dyck subword remaining after that closing parenthesis, whose lengths 2i and 2j satisfy Template:Math); this number is therefore also the Catalan number <math>C_n</math>. So there are also five Dyck words of length 6:

Template:Math

These Dyck words do not correspond to binary trees in the same way. Instead, they are related by the following recursively defined bijection: the Dyck word equal to the empty string corresponds to the binary tree of size 0 with only one leaf. Any other Dyck word can be written as (<math>w_1</math>)<math>w_2</math>, where <math>w_1</math>,<math>w_2</math> are themselves (possibly empty) Dyck words and where the two written parentheses are matched. The bijection is then defined by letting the words <math>w_1</math> and <math>w_2</math> correspond to the binary trees that are the left and right children of the root.

A bijective correspondence can also be defined as follows: enclose the Dyck word in an extra pair of parentheses, so that the result can be interpreted as a Lisp list expression (with the empty list () as only occurring atom); then the dotted-pair expression for that proper list is a fully parenthesized expression (with NIL as symbol and '.' as operator) describing the corresponding binary tree (which is, in fact, the internal representation of the proper list).

The ability to represent binary trees as strings of symbols and parentheses implies that binary trees can represent the elements of a free magma on a singleton set.

Methods for storing binary trees

Binary trees can be constructed from programming language primitives in several ways.

Nodes and references

In a language with records and references, binary trees are typically constructed by having a tree node structure which contains some data and references to its left child and its right child. Sometimes it also contains a reference to its unique parent. If a node has fewer than two children, some of the child pointers may be set to a special null value, or to a special sentinel node. The C# class below can be used to represent a binary tree. <syntaxhighlight lang="c#" line="1"> class Node {

   int data; 
   Node leftChild; 
   Node rightChild; 

} </syntaxhighlight>This method of storing binary trees wastes a fair bit of memory, as the pointers will be null (or point to the sentinel) more than half the time; a more conservative representation alternative is threaded binary tree.<ref name="Samanta2004">Template:Cite book</ref>

In languages with tagged unions such as ML, a tree node is often a tagged union of two types of nodes, one of which is a 3-tuple of data, left child, and right child, and the other of which is a "leaf" node, which contains no data and functions much like the null value in a language with pointers. For example, the following line of code in OCaml (an ML dialect) defines a binary tree that stores a character in each node.<ref name="Scott2009">Template:Cite book</ref>

<syntaxhighlight lang="ocaml"> type chr_tree = Empty | Node of char * chr_tree * chr_tree </syntaxhighlight>

Arrays

Binary trees can also be stored in breadth-first order as an implicit data structure in arrays, and if the tree is a complete binary tree, this method wastes no space. In this compact arrangement, if a node has an index i, its children are found at indices <math>2i + 1</math> (for the left child) and <math>2i +2</math> (for the right), while its parent (if any) is found at index <math>\left \lfloor \frac{i-1}{2} \right \rfloor</math> (assuming the root has index zero). Alternatively, with a 1-indexed array, the implementation is simplified with children found at <math>2i</math> and <math>2i+1</math>, and parent found at <math>\lfloor i/2 \rfloor</math>.<ref>Template:Cite book</ref>

This method benefits from more compact storage and better locality of reference, particularly during a preorder traversal. It is often used for binary heaps.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>

A small complete binary tree stored in an array

Encodings

Succinct encodings

A succinct data structure is one which occupies close to minimum possible space, as established by information theoretical lower bounds. The number of different binary trees on <math>n</math> nodes is <math>\mathrm{C}_{n}</math>, the <math>n</math>th Catalan number (assuming we view trees with identical structure as identical). For large <math>n</math>, this is about <math>4^{n}</math>; thus we need at least about <math>\log_{2}4^{n} = 2n</math> bits to encode it. A succinct binary tree therefore would occupy Template:Nowrap bits (with 'o()' being the Little-o notation).

One simple representation which meets this bound is to visit the nodes of the tree in preorder, outputting "1" for an internal node and "0" for a leaf.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref> If the tree contains data, we can simply simultaneously store it in a consecutive array in preorder. This function accomplishes this:

function EncodeSuccinct(node n, bitstring structure, array data) {
    if n = nil then
        append 0 to structure;
    else
        append 1 to structure;
        append n.data to data;
        EncodeSuccinct(n.left, structure, data);
        EncodeSuccinct(n.right, structure, data);
}

The string structure has only <math>2n + 1</math> bits in the end, where <math>n</math> is the number of (internal) nodes; we don't even have to store its length. To show that no information is lost, we can convert the output back to the original tree like this:

function DecodeSuccinct(bitstring structure, array data) {
    remove first bit of structure and put it in b
    if b = 1 then
        create a new node n
        remove first element of data and put it in n.data
        n.left = DecodeSuccinct(structure, data)
        n.right = DecodeSuccinct(structure, data)
        return n
    else
        return nil
}

More sophisticated succinct representations allow not only compact storage of trees but even useful operations on those trees directly while they're still in their succinct form.

Encoding ordered trees as binary trees

There is a natural one-to-one correspondence between ordered trees and binary trees. It allows any ordered tree to be uniquely represented as a binary tree, and vice versa:

Let T be a node of an ordered tree, and let B denote T's image in the corresponding binary tree. Then B's left child represents T's first child, while the B's right child represents T's next sibling.

For example, the ordered tree on the left and the binary tree on the right correspond:

An example of converting an n-ary tree to a binary tree

In the pictured binary tree, the black, left, edges represent first child, while the blue, right, edges represent next sibling.

This representation is called a left-child right-sibling binary tree.

Common operations

File:BinaryTreeRotations.svg

Tree rotations are very common internal operations on self-balancing binary trees.

There are a variety of different operations that can be performed on binary trees. Some are mutator operations, while others simply return useful information about the tree.

Insertion

Nodes can be inserted into binary trees in between two other nodes or added after a leaf node. In binary trees, a node that is inserted is specified as to whose child it will be.

Leaf nodes

To add a new node after leaf node A, A assigns the new node as one of its children and the new node assigns node A as its parent.

Internal nodes

File:Insertion of binary tree node.svg

The process of inserting a node into a binary tree

Insertion on internal nodes is slightly more complex than on leaf nodes. Say that the internal node is node A and that node B is the child of A. (If the insertion is to insert a right child, then B is the right child of A, and similarly with a left child insertion.) A assigns its child to the new node and the new node assigns its parent to A. Then the new node assigns its child to B and B assigns its parent as the new node.

Deletion

Deletion is the process whereby a node is removed from the tree. Only certain nodes in a binary tree can be removed unambiguously.<ref name="rice">{{#invoke:citation/CS1|citation |CitationClass=web }} </ref>

Node with zero or one children

File:Deletion of internal binary tree node.svg

The process of deleting an internal node in a binary tree

Suppose that the node to delete is node A. If A has no children, deletion is accomplished by setting the child of A's parent to null. If A has one child, set the parent of A's child to A's parent and set the child of A's parent to A's child.

Node with two children

In a binary tree, a node with two children cannot be deleted unambiguously.<ref name="rice"/> However, in certain binary trees (including binary search trees) these nodes can be deleted, though with a rearrangement of the tree structure.

Traversal

{{#invoke:Labelled list hatnote|labelledList|Main article|Main articles|Main page|Main pages}}

Pre-order, in-order, and post-order traversal visit each node in a tree by recursively visiting each node in the left and right subtrees of the root. Below are the brief descriptions of above mentioned traversals.

Pre-order

In pre-order, we always visit the current node; next, we recursively traverse the current node's left subtree, and then we recursively traverse the current node's right subtree. The pre-order traversal is a topologically sorted one, because a parent node is processed before any of its child nodes is done.

In-order

In in-order, we always recursively traverse the current node's left subtree; next, we visit the current node, and lastly, we recursively traverse the current node's right subtree.

Post-order

In post-order, we always recursively traverse the current node's left subtree; next, we recursively traverse the current node's right subtree and then visit the current node. Post-order traversal can be useful to get postfix expression of a binary expression tree.<ref>{{#invoke:citation/CS1|citation |CitationClass=web }}</ref>

Depth-first order

In depth-first order, we always attempt to visit the node farthest from the root node that we can, but with the caveat that it must be a child of a node we have already visited. Unlike a depth-first search on graphs, there is no need to remember all the nodes we have visited, because a tree cannot contain cycles. Pre-order is a special case of this. See depth-first search for more information.

Breadth-first order

Contrasting with depth-first order is breadth-first order, which always attempts to visit the node closest to the root that it has not already visited. See breadth-first search for more information. Also called a level-order traversal.

In a complete binary tree, a node's breadth-index (i − (2^d − 1)) can be used as traversal instructions from the root. Reading bitwise from left to right, starting at bit d − 1, where d is the node's distance from the root (d = ⌊log₂(i+1)⌋) and the node in question is not the root itself (d > 0). When the breadth-index is masked at bit d − 1, the bit values Template:Mono and Template:Mono mean to step either left or right, respectively. The process continues by successively checking the next bit to the right until there are no more. The rightmost bit indicates the final traversal from the desired node's parent to the node itself. There is a time-space trade-off between iterating a complete binary tree this way versus each node having pointer(s) to its sibling(s).

References

Bibliography

• Donald Knuth. The Art of Computer Programming vol 1. Fundamental Algorithms, Third Edition. Addison-Wesley, 1997. Template:ISBN. Section 2.3, especially subsections 2.3.1–2.3.2 (pp. 318–348).

External links

• binary trees Template:Webarchive entry in the FindStat database
• Binary Tree Proof by Induction
• Balanced binary search tree on array How to create bottom-up an Ahnentafel list, or a balanced binary search tree on array
• Binary trees and Implementation of the same with working code examples
• Binary Tree JavaScript Implementation with source code