Intro To Graph Theory

Algorithmic Graph Theory
David Joyner, Minh Van Nguyen, Nathann Cohen

Version 0.7-r1843
2011 May 01
Copyright 2010 David Joyner <wdjoyner@gmail.com>

Copyright 20092011 Minh Van Nguyen <nguyenminh2@gmail.com>
Copyright 2010 Nathann Cohen <nathann.cohen@gmail.com>
Permission is granted to copy, distribute and/or modify this document under the terms
of the GNU Free Documentation License, Version 1.3 or any later version published by
the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no
Back-Cover Texts. A copy of the license is included in the section entitled GNU Free
Documentation License.
The latest version of the book is available from its website at
http://code.google.com/p/graph-theory-algorithms-book/
Edition
Version 0.7-r1843
2011 May 01
Contents
Acknowledgments
iv
1 Introduction to Graph Theory

1.1 Graphs and digraphs . . . . . . .
1.2 Subgraphs and other graph types
1.3 Representing graphs as matrices .
1.4 Isomorphic graphs . . . . . . . .
1.5 New graphs from old . . . . . . .
1.6 Common applications . . . . . . .
1.7 Application: finite automata . . .
1.8 Problems . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
1
2
10
17
22
27
36
38
45
.
.
.
.
.
.
.
.
52
53
58
69
72
76
77
84
86
.
.
.
.
.
.
.
104
104
111
115
126
133
139
144
.
.
.
.
.
.
152
153
154
164
172
179
189
.
.
.
.
.
.
.
.
2 Graph Algorithms
2.1 Representing graphs in a computer
2.2 Graph searching . . . . . . . . . . .
2.3 Weights and distances . . . . . . .
2.4 Dijkstras algorithm . . . . . . . . .
2.5 Bellman-Ford algorithm . . . . . .
2.6 Floyd-Roy-Warshall algorithm . . .
2.7 Johnsons algorithm . . . . . . . . .
2.8 Problems . . . . . . . . . . . . . . .
3 Trees and Forests
3.1 Definitions and examples
3.2 Properties of trees . . . .
3.3 Minimum spanning trees
3.4 Binary trees . . . . . . .
3.5 Huffman codes . . . . .
3.6 Tree traversals . . . . . .
3.7 Problems . . . . . . . . .
4 Tree Data Structures
4.1 Priority queues . .
4.2 Binary heaps . . .
4.3 Binomial heaps . .
4.4 Binary search trees
4.5 AVL trees . . . . .
4.6 Problems . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
i
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
ii
5 Distance and Connectivity
5.1 Paths and distance . . . . . .
5.2 Vertex and edge connectivity .
5.3 Mengers theorem . . . . . . .
5.4 Whitneys Theorem . . . . . .
5.5 Centrality of a vertex . . . . .
5.6 Network reliability . . . . . .
5.7 Problems . . . . . . . . . . . .
Contents
.
.
.
.
.
.
.
196
196
201
206
209
210
211
211
.
.
.
.
215
215
215
215
216
7 Planar Graphs
7.1 Planarity and Eulers Formula . . . . . . . . . . . . . . . . . . . . . . . .
7.2 Kuratowskis Theorem . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3 Planarity algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
217
217
217
219
8 Graph Coloring
8.1 Vertex coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.2 Edge coloring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.3 Applications of graph coloring . . . . . . . . . . . . . . . . . . . . . . . .
220
220
221
221
9 Network Flows
9.1 Flows and cuts . . . . . . . . . .
9.2 Ford-Fulkerson theorem . . . . .
9.3 Edmonds and Karps algorithm .
9.4 Goldberg and Tarjans algorithm
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
223
223
223
228
228
10 Random Graphs
10.1 Network statistics . . . . . . .
10.2 Binomial random graph model
10.3 Erdos-Renyi model . . . . . .
10.4 Small-world networks . . . . .
10.5 Scale-free networks . . . . . .
10.6 Problems . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
229
229
234
240
241
247
252
11 Graph Problems and Their LP

11.1 Maximum average degree . . .
11.2 Traveling Salesman Problem .
11.3 Edge-disjoint spanning trees .
11.4 Steiner tree . . . . . . . . . .
11.5 Linear arboricity . . . . . . .
11.6 H-minor . . . . . . . . . . . .
Formulations
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
.
.
.
.
.
.
258
258
259
261
262
264
266
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6 Optimal Graph Traversals

6.1 Eulerian graphs . . . . . . . . . .
6.2 Hamiltonian graphs . . . . . . . .
6.3 The Chinese Postman Problem .
6.4 The Traveling Salesman Problem
A Asymptotic Growth
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
270
Contents
B GNU Free Documentation License
1. APPLICABILITY AND DEFINITIONS . . . . . . . . .
2. VERBATIM COPYING . . . . . . . . . . . . . . . . .
3. COPYING IN QUANTITY . . . . . . . . . . . . . . . .
4. MODIFICATIONS . . . . . . . . . . . . . . . . . . . .
5. COMBINING DOCUMENTS . . . . . . . . . . . . . .
6. COLLECTIONS OF DOCUMENTS . . . . . . . . . . .
7. AGGREGATION WITH INDEPENDENT WORKS . .
8. TRANSLATION . . . . . . . . . . . . . . . . . . . . . .
9. TERMINATION . . . . . . . . . . . . . . . . . . . . . .
10. FUTURE REVISIONS OF THIS LICENSE . . . . . .
11. RELICENSING . . . . . . . . . . . . . . . . . . . . . .
ADDENDUM: How to use this License for your documents
iii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
271
271
273
273
274
275
276
276
276
277
277
277
278
Bibliography
279
Index
288
Acknowledgments
Fidel Barrera-Cruz: reported typos in Chapter 3. See changeset 101. Suggested
making a note about disregarding the direction of edges in undirected graphs. See
changeset 277.
Daniel Black: reported a typo in Chapter 1. See changeset 61.
Kevin Brintnall: reported typos in the definition of iadj(v) oadj(v); see changesets 240 and 242. Solution to Example 1.12(2); see changeset 246.
Aaron Dutle: reported a typo in Figure 1.14. See changeset 125.
Peter L. Erd
os (http://www.renyi.hu/~elp) for informing us of the reference [71]
on the Havel-Hakimi theorem for directed graphs.
Noel Markham: reported a typo in Algorithm 2.5. See changeset 131 and Issue 2.
Caroline Melles: clarify definitions of various graph types (weighted graphs, multigraphs, and weighted multigraphs); clarify definitions of degree, isolated vertices,
and pendant and using the butterfly graph with 5 vertices (see Figure 1.9) to
illustrate these definitions; clarify definitions of trails, closed paths, and cycles;
see changeset 448. Some rearrangements of materials in Chapter 1 to make the
reading flow better and a few additions of missing definitions; see changeset 584.
Clarifications about unweighted and weighted degree of a vertex in a multigraph;
notational convention about a graph being simple unless otherwise stated; an example on graph minor; see changeset 617.
Pravin Paratey: simplify the sentence formation in the definition of digraphs; see
changeset 714 and Issue 7.
The world map in Figure 2.15 was adapted from an SVG image file from Wikipedia.
The original SVG file was accessed on 2010-10-01 at http://en.wikipedia.org/
wiki/File:Worldmap_location_NED_50m.svg.
iv
Chapter 1
Introduction to Graph Theory
Spiked Math, http://spikedmath.com/120.html
Our journey into graph theory starts with a puzzle that was solved over 250 years ago by
Leonhard Euler (17071783). The Pregel River flowed through the town of Konigsberg,
which is present day Kaliningrad in Russia. Two islands protruded from the river.
On either side of the mainland, two bridges joined one side of the mainland with one
island and a third bridge joined the same side of the mainland with the other island. A
bridge connected the two islands. In total, seven bridges connected the two islands with
both sides of the mainland. A popular exercise among the citizens of Konigsberg was
determining if it was possible to cross each bridge exactly once during a single walk. For
historical perspectives on this puzzle and Eulers solution, see Gribkovskaia et al. [87]
and Hopkins and Wilson [100].
To visualize this puzzle in a slightly different way, consider Figure 1.1. Imagine that
points a and c are either sides of the mainland, with points b and d being the two islands.
Place the tip of your pencil on any of the points a, b, c, d. Can you trace all the lines
in the figure exactly once, without lifting your pencil? Known as the seven bridges of
Konigsberg puzzle, Euler solved this problem in 1735 and with his solution he laid the
foundation of what is now known as graph theory.
Chapter 1. Introduction to Graph Theory

c
Figure 1.1: The seven bridges of Konigsberg puzzle.
1.1
Graphs and digraphs

When I use a word, it means just what I choose it to meanneither more nor less.
Humpty Dumpty in Lewis Carrolls Through the Looking Glass
The word graph is commonly understood to mean a visual representation of a dataset,

such as a bar chart, a histogram, a scatterplot, or a plot of a function. Examples of such
graphs are shown in Figure 1.2.
1
0.5
f (x)
0.5
0.5
0.5
1
6
0
x
(a) Plots of functions.
0
x
(b) A scatterplot.
Figure 1.2: Visual representations of datasets as plots.

This book is not about graphs in the sense of plots of functions or datasets. Rather,
our focus is on combinatorial graphs or graphs for short. A graph in the combinatorial
sense is a collection of discrete interconnected elements, an example of which is shown
in Figure 1.1. How can we elaborate on this brief description of combinatorial graphs?
To paraphrase what Felix Klein said about curves,1 it is easy to define a graph until we
realize the countless number of exceptions. There are directed graphs, weighted graphs,
multigraphs, simple graphs, and so on. Where do we begin?
Notation If S is a set, let S (n) denote the set of unordered n-tuples (with possible
repetition). We shall sometimes refer to an unordered n-tuple as an n-set.
1
Everyone knows what a curve is, until he has studied enough mathematics to become confused
through the countless number of possible exceptions.
1.1. Graphs and digraphs
We start by calling a graph what some call an unweighted, undirected graph without
multiple edges.
Definition 1.1. A graph G = (V, E) is an ordered pair of finite sets. Elements of V are
called vertices or nodes, and elements of E V (2) are called edges or arcs. We refer to
V as the vertex set of G, with E being the edge set. The cardinality of V is called the
order of G, and |E| is called the size of G. We usually disregard any direction of the
edges and consider (u, v) and (v, u) as one and the same edge in G. In that case, G is
referred to as an undirected graph.
One can label a graph by attaching labels to its vertices. If (v1 , v2 ) E is an edge of
a graph G = (V, E), we say that v1 and v2 are adjacent vertices. For ease of notation, we
write the edge (v1 , v2 ) as v1 v2 . The edge v1 v2 is also said to be incident with the vertices
v1 and v2 .
a
Figure 1.3: A house graph.

Example 1.2. Consider the graph in Figure 1.3.
1. List the vertex and edge sets of the graph.
2. For each vertex, list all vertices that are adjacent to it.
3. Which vertex or vertices have the largest number of adjacent vertices? Similarly,
which vertex or vertices have the smallest number of adjacent vertices?
4. If all edges of the graph are removed, is the resulting figure still a graph? Why or
why not?
5. If all vertices of the graph are removed, is the resulting figure still a graph? Why
or why not?
Solution. (1) Let G = (V, E) denote the graph in Figure 1.3. Then the vertex set of G
is V = {a, b, c, d, e}. The edge set of G is given by
E = {ab, ae, ba, bc, be, cb, cd, dc, de, ed, eb, ea}.
We can also use Sage to construct the graph G and list its vertex and edge sets:
(1.1)
sage : G = Graph ({ " a " :[ " b " ," e " ] , " b " :[ " a " ," c " ," e " ] , " c " :[ " b " ," d " ] ,
...
" d " :[ " c " ," e " ] , " e " :[ " a " ," b " ," d " ]})
sage : G
Graph on 5 vertices
sage : G . vertices ()
[ a , b , c , d , e ]
sage : G . edges ( labels = False )
[( a , b ) , ( a , e ) , ( b , e ) , ( c , b ) , ( c , d ) , ( e , d )]
The graph G is undirected, meaning that we do not impose direction on any edges.
Without any direction on the edges, the edge ab is the same as the edge ba. That is why
G.edges() returns six edges instead of the 12 edges listed in (1.1).
(2) Let adj(v) be the set of all vertices that are adjacent to v. Then we have
adj(a) = {b, e}
adj(b) = {a, c, e}
adj(c) = {b, d}
adj(d) = {c, e}
adj(e) = {a, b, d}.
The vertices adjacent to v are also referred to as its neighbors. We can use the function
G.neighbors() to list all the neighbors of each vertex.
sage :
[ b ,
sage :
[ a ,
sage :
[ b ,
sage :
[ c ,
sage :
[ a ,
G . neighbors ( " a " )

e ]
G . neighbors ( " b " )
c , e ]
G . neighbors ( " c " )
d ]
G . neighbors ( " d " )
e ]
G . neighbors ( " e " )
b , d ]
(3) Taking the cardinalities of the above five sets, we get |adj(a)| = |adj(c)| =
|adj(d)| = 2 and |adj(b)| = |adj(e)| = 3. Thus a, c and d have the smallest number
of adjacent vertices, while b and e have the largest number of adjacent vertices.
(4) If all the edges in G are removed, the result is still a graph, although one without
any edges. By definition, the edge set of any graph is a subset of V (2) . Removing all
edges of G leaves us with the empty set , which is a subset of every set.
(5) Say we remove all of the vertices from the graph in Figure 1.3 and in the process
all edges are removed as well. The result is that both of the vertex and edge sets are
empty. This is a special graph known as the empty or null graph.
Example 1.3. Consider the illustration in Figure 1.4. Does Figure 1.4 represent a
graph? Why or why not?
Solution. If V = {a, b, c} and E = {aa, bc}, it is clear that E V (2) . Then (V, E) is a
graph. The edge aa is called a self-loop of the graph. In general, any edge of the form
vv is a self-loop.
In Figure 1.3, the edges ae and ea represent one and the same edge. If we do not
consider the direction of the edges in the graph of Figure 1.3, then the graph has six
edges. However, if the direction of each edge is taken into account, then there are 12 edges
as listed in (1.1). The following definition captures the situation where the direction of
the edges are taken into account.
A directed edge is an edge such that one vertex incident with it is designated as
the head vertex and the other incident vertex is designated as the tail vertex. In this
5
a
Figure 1.4: A figure with a self-loop.

situation, we may assume that the set of edges is a subset of the ordered pairs V V .
A directed edge uv is said to be directed from its tail u to its head v. A directed graph
or digraph G is a graph each of whose edges is directed. The indegree id(v) of a vertex
v V (G) counts the number of edges such that v is the head of those edges. The
outdegree od(v) of a vertex v V (G) is the number of edges such that v is the tail of
those edges. The degree deg(v) of a vertex v of a digraph is the sum of the indegree and
the outdegree of v.
Let G be a graph without self-loops and multiple edges. It is important to distinguish
a graph G as being directed or undirected. If G is undirected and uv E(G), then uv
and vu represent the same edge. In case G is a digraph, then uv and vu are different
directed edges. For a digraph G = (V, E) and a vertex v V , all the neighbors of v
in G are contained in adj(v), i.e. the set of all neighbors of v. Just as we distinguish
between indegree and outdegree for a vertex in a digraph, we also distinguish between inneighbors and out-neighbors. The set of in-neighbors iadj(v) adj(v) of v V consists
of all those vertices that contribute to the indegree of v. Similarly, the set of out-neighbors
oadj(v) adj(v) of v V are those vertices that contribute to the outdegree of v. Then
iadj(v) oadj(v) = {u | uv E and vu E}
and adj(v) = iadj(v) oadj(v).
1.1.1
Multigraphs
This subsection presents a larger class of graphs. For simplicity of presentation, in this
book we shall assume usually that a graph is not a multigraph. In other words, when you
read a property of graphs later in the book, it will be assumed (unless stated explicitly
otherwise) that the graph is not a multigraph. However, as multigraphs and weighted
graphs are very important in many applications, we will try to keep them in the back
of our mind. When appropriate, we will add as a remark how an interesting property of
ordinary graphs extends to the multigraph or weighted graph case.
An important class of graphs consist of those graphs having multiple edges between
pairs of vertices. A multigraph is a graph in which there are multiple edges between a
pair of vertices. A multi-undirected graph is a multigraph that is undirected. Similarly,
a multidigraph is a directed multigraph.
As we indicated above, a graph may have weighted edges.
Definition 1.4. A weighted graph is a graph G = (V, E) where each set V and E is a
pair consisting of a vertex and a real number called the weight.
The illustration in Figure 1.1 is actually a multigraph, a graph with multiple edges,
called the Konigsberg graph.
Definition 1.5. For a weighted multigraph G, we are given:

A finite set V whose elements are pairs (v, wv ), where v is called a vertex and
wv R is called its weight. (Sometimes, the pair (v, wv ) is called the vertex.)
A finite set E whose elements are called edges. We do not necessarily assume that
E V (2) , where V (2) is the set of unordered pairs of vertices.2
An incidence function
i : E V (2) .
(1.2)
Such a multigraph is denoted G = (V, E, i). An orientation on G is a function

h : E V
(1.3)
where h(e) i(e) for all e E. The element v = h(e) is called the head of i(e). If G has
no self-loops, then i(e) is a set having exactly two elements denoted i(e) = {h(e), t(e)}.
The element v = t(e) is called the tail of i(e). For self-loops, we set t(e) = h(e). A
multigraph with an orientation can therefore be described as the 4-tuple (V, E, i, h).
In other words, G = (V, E, i, h) is a multidigraph. Figure 1.5 illustrates a weighted
multigraph.
1
v3
v4
2
3
1
1
v5
3
3
v2
v1
Figure 1.5: An example of a weighted multigraph.

The degree of a weighted multigraph must be defined. There is a weighted degree and
an unweighted degree. Let G be a graph as in Definition 1.5. The unweighted indegree
of a vertex v V counts the edges going into v:
X
deg+ (v) =
1.
eE
h(e)=v
The unweighted outdegree of a vertex v V counts the edges going out of v:

X
1.
deg (v) =
eE
vi(e)={v,v 0 }
h(e)=v 0
However, we always assume that E R V (2) , where the R-component is called the weight of the
edge.
The unweighted degree deg(v) of a vertex v of a weighted multigraph is the sum of the
unweighted indegree and the unweighted outdegree of v:
deg(v) = deg+ (v) + deg (v).
Loops are counted twice.
Similarly, there is the set of in-neighbors
iadj(v) = {w V | for some e E, i(e) = {v, w}, h(e) = v}
and the set of out-neighbors
oadj(v) = {w V | for some e E, i(e) = {v, w}, h(e) = w}.
Define the adjacency of v to be the union of these:
adj(v) = iadj(v) oadj(v).
It is clear that deg+ (v) = | iadj(v)| and deg (v) = | oadj(v)|.
The weighted indegree of a vertex v V counts the weights of edges going into v:
X
wv .
wdeg + (v) =
eE
h(e)=v
The weighted outdegree of a vertex v V counts the weights of edges going out of v:
X
wv .
wdeg (v) =
eE
vi(e)={v,v 0 }
h(e)=v 0
The weighted degree of a vertex of a weighted multigraph is the sum of the weighted
indegree and the weighted outdegree of that vertex. In other words, it is the sum of
the weights of the edges incident to that vertex, regarding the graph as an undirected
weighted graph.
1.1.2
Simple graphs
Our life is frittered away by detail. . . . Simplify, simplify. Instead of three meals a day, if
it be necessary eat but one; instead of a hundred dishes, five; and reduce other things in
proportion.
Henry David Thoreau, Walden, 1854, Chapter 2: Where I Lived, and What I Lived For
A simple graph is a graph with no self-loops and no multiple edges. Figure 1.6 illustrates
a simple graph and its digraph version, together with a multidigraph version of the
Konigsberg graph. The edges of a digraph can be visually represented as directed arrows,
similar to the digraph in Figure 1.6(b) and the multidigraph in Figure 1.6(c). The digraph
in Figure 1.6(b) has the vertex set {a, b, c} and the edge set {ab, bc, ca}. There is an arrow
from vertex a to vertex b, hence ab is in the edge set. However, there is no arrow from
b to a, so ba is not in the edge set of the graph in Figure 1.6(b). The family Sh(n) of
Shannon multigraphs is illustrated in Figure 1.7 for integers 2 n 7. These graphs
are named after Claude E. Shannon (19162001). Each Shannon multigraph consists of
three vertices, giving rise to a total of three distinct unordered pairs. Two of these pairs
are connected by bn/2c edges and the third pair of vertices is connected by b(n + 1)/2c
edges.
(a) Simple graph.
(b) Digraph.
(c) Multidigraph.
Figure 1.6: A simple graph, its digraph version, and a multidigraph.
(a) Sh(2)
(b) Sh(3)
(c) Sh(4)
(d) Sh(5)
(e) Sh(6)
(f) Sh(7)
Figure 1.7: The family of Shannon multigraphs Sh(n) for n = 2, . . . , 7.
Notational convention Unless stated otherwise, all graphs are simple graphs in the
remainder of this book.
Definition 1.6. For any vertex v in a graph G = (V, E), the cardinality of adj(v) is
called the degree of v and written as deg(v) = | adj(v)|. The degree of v counts the
number of vertices in G that are adjacent to v. If deg(v) = 0, then v is not incident to
any edge and we say that v is an isolated vertex. If G has no loops and deg(v) = 1, then
v is called a pendant.
Some examples would put the above definition in concrete terms. Consider again
the graph in Figure 1.4. Note that no vertices are isolated. Even though vertex a is
not incident to any vertex other than a itself, note that deg(a) = 2 and so by definition
a is not isolated. Furthermore, each of b and c is a pendant. For the house graph in
Figure 1.3, we have deg(b) = 3. For the graph in Figure 1.6(b), we have deg(b) = 2.
If V 6= and E = , then G is a graph consisting entirely of isolated vertices. From
Example 1.2 we know that the vertices a, c, d in Figure 1.3 have the smallest degree in
the graph of that figure, while b, e have the largest degree.
The minimum degree among all vertices in G is denoted (G), whereas the maximum
degree is written as (G).
Thus, if G denotes the graph in Figure 1.3 then we have (G) = 2 and (G) = 3. In
the following Sage session, we construct the digraph in Figure 1.6(b) and computes its
maximum and minimum number of degrees.
sage : G = DiGraph ({ " a " : " b " , " b " : " c " , " c " : " a " })
sage : G
Digraph on 3 vertices
sage : G . degree ( " a " )
2
sage : G . degree ( " b " )
2
sage : G . degree ( " c " )
2
So for the graph G in Figure 1.6, we have (G) = (G) = 2.

The graph G in Figure 1.6 has the special property that its minimum degree is the
same as its maximum degree, i.e. (G) = (G). Graphs with this property are referred
to as regular . An r-regular graph is a regular graph each of whose vertices has degree r.
For instance, G is a 2-regular graph. The following result, due to Euler, counts the total
number of degrees in any graph.
P
Theorem 1.7. Euler 1736. If G = (V, E) is a graph, then vV deg(v) = 2|E|.
Proof. Each edge e = v1 v2 E is incident with two vertices, so e is counted twice

towards the total sum of degrees. The first time, we count e towards the degree of vertex
v1 and the second time we count e towards the degree of v2 .
Theorem 1.7 is sometimes called the handshaking lemma, due to its interpretation
as in the following story. Suppose you go into a room. Suppose there are n people in the
room (including yourself) and some people shake hands with others and some do not.
Create the graph with n vertices, where each vertex is associated with a different person.
Draw an edge between two people if they shook hands. The degree of a vertex is the
number of times that person has shaken hands (we assume that there are no multiple
edges, i.e. that no two people shake hands twice). The theorem above simply says that
the total number of handshakes is even. This is obvious when you look at it this way
since each handshake is counted twice (A shaking Bs hand is counted, and B shaking As
10
hand is counted as well, since the sum in the theorem is over all vertices). To interpret
Theorem 1.7 in a slightly different way within the context of the same room of people,
there is an even number of people who shook hands with an odd number of other people.
This consequence of Theorem 1.7 is recorded in the following corollary.
Corollary 1.8. A graph G = (V, E) contains an even number of vertices with odd
degrees.
Proof. Partition V into two disjoint subsets: Ve is the subset of V that contains only
vertices with even degrees; and Vo is the subset of V with only vertices of odd degrees.
That is, V = Ve Vo and Ve Vo = . From Theorem 1.7, we have
X
X
X
deg(v) =
deg(v) +
deg(v) = 2|E|
vV
vVe
which can be re-arranged as

X
vVo
As
vV
deg(v) and
vVe
deg(v) =
vVo
X
vV
deg(v)
deg(v).
vVe
deg(v) are both even, their difference is also even.
As E V (2) , then E can be the empty set, in which case the total degree of G =
(V, E) is zero. Where E 6= , then the total degree of G is greater than zero. By
Theorem 1.7, the total degree of G is nonnegative and even. This result is an immediate
consequence of Theorem 1.7 and is captured in the following corollary.
Corollary 1.9. If G is a graph, then the sum of its degrees is nonnegative and even.
If G = (V, E) is an r-regular graph with n vertices and m edges, it is clear by definition
of r-regular graphs that the total degree of G is rn. By Theorem 1.7 we have 2m = rn
and therefore m = rn/2. This result is captured in the following corollary.
Corollary 1.10. If G = (V, E) is an r-regular graph having n vertices and m edges,
then m = rn/2.
1.2
Subgraphs and other graph types
We now consider several common types of graphs. Along the way, we also present basic
properties of graphs that could be used to distinguish different types of graphs.
Let G be a multigraph as in Definition 1.5, with vertex set V (G) and edge set E(G).
Consider a graph H such that V (H) V (G) and E(H) E(G). Furthermore, if
e E(H) and i(e) = {u, v}, then u, v V (H). Under these conditions, H is called a
subgraph of G.
1.2.1
Walks, trails, and paths
I like long walks, especially when they are taken by people who annoy me.
Noel Coward
1.2. Subgraphs and other graph types
11
If u and v are two vertices in a graph G, a u-v walk is an alternating sequence of vertices
and edges starting with u and ending at v. Consecutive vertices and edges are incident.
Formally, a walk W of length n 0 can be defined as
W : v0 , e1 , v1 , e2 , v2 , . . . , vn1 , en , vn
where each edge ei = vi1 vi and the length n refers to the number of (not necessarily
distinct) edges in the walk. The vertex v0 is the starting vertex of the walk and vn is
the end vertex, so we refer to W as a v0 -vn walk. The trivial walk is the walk of length
n = 0 in which the start and end vertices are one and the same vertex. If the graph has
no multiple edges then, for brevity, we omit the edges in a walk and usually write the
walk as the following sequence of vertices:
W : v0 , v1 , v2 , . . . , vn1 , vn .
For the graph in Figure 1.8, an example of a walk is an a-e walk: a, b, c, b, e. In other
words, we start at vertex a and travel to vertex b. From b, we go to c and then back to
b again. Then we end our journey at e. Notice that consecutive vertices in a walk are
adjacent to each other. One can think of vertices as destinations and edges as footpaths,
say. We are allowed to have repeated vertices and edges in a walk. The number of edges
in a walk is called its length. For instance, the walk a, b, c, b, e has length 4.
a
c
g
Figure 1.8: Walking along a graph.

A trail is a walk with no repeating edges. For example, the a-b walk a, b, c, d, f, g, b in
Figure 1.8 is a trail. It does not contain any repeated edges, but it contains one repeated
vertex, i.e. b. Nothing in the definition of a trail restricts a trail from having repeated
vertices. A walk with no repeating vertices, except possibly the first and last, is called a
path. Without any repeating vertices, a path cannot have repeating edges, hence a path
is also a trail.
Proposition 1.11. Let G = (V, E) be a simple (di)graph of order n = |V |. Any path in
G has length at most n 1.
Proof. Let V = {v1 , v2 , . . . , vn } be the vertex set of G. Without loss of generality, we can
assume that each pair of vertices in the digraph G is connected by an edge, giving a total
of n2 possible edges for E = V V . We can remove self-loops from E, which now leaves
us with an edge set E1 that consists of n2 n edges. Start our path from any vertex,
say, v1 . To construct a path of length 1, choose an edge v1 vj1 E1 such that vj1
/ {v1 }.
12
Remove from E1 all v1 vk such that vj1 6= vk . This results in a reduced edge set E2 of
n2 n (n 2) elements and we now have the path P1 : v1 , vj1 of length 1. Repeat the
same process for vj1 vj2 E2 to obtain a reduced edge set E3 of n2 n 2(n 2) elements
and a path P2 : v1 , vj1 , vj2 of length 2. In general, let Pr : v1 , vj1 , vj2 , . . . , vjr be a path of
length r < n and let Er+1 be our reduced edge set of n2 n r(n 2) elements. Repeat
the above process until we have constructed a path Pn1 : v1 , vj1 , vj2 , . . . , vjn1 of length
n 1 with reduced edge set En of n2 n (n 1)(n 2) elements. Adding another
vertex to Pn1 means going back to a vertex that was previously visited, because Pn1
already contains all vertices of V .
A walk of length n 3 whose start and end vertices are the same is called a closed
walk . A trail of length n 3 whose start and end vertices are the same is called a closed
trail . A path of length n 3 whose start and end vertices are the same is called a closed
path or a cycle (with apologies for slightly abusing terminology).3 For example, the
walk a, b, c, e, a in Figure 1.8 is a closed path. A path whose length is odd is called odd ,
otherwise it is referred to as even. Thus the walk a, b, e, a in Figure 1.8 is a cycle. It is
easy to see that if you remove any edge from a cycle, then the resulting walk contains no
closed walks. An Euler subgraph of a graph G is either a cycle or an edge-disjoint union
of cycles in G. An example of a closed walk which is not a cycle is given in Figure 1.9.
0
Figure 1.9: Butterfly graph with 5 vertices.

The length of the shortest cycle in a graph is called the girth of the graph. By
convention, an acyclic graph is said to have infinite girth.
Example 1.12. Consider the graph in Figure 1.8.
1. Find two distinct walks that are not trails and determine their lengths.
2. Find two distinct trails that are not paths and determine their lengths.
3. Find two distinct paths and determine their lengths.
4. Find a closed trail that is not a cycle.
5. Find a closed walk C which has an edge e such that C e contains a cycle.
Solution. (1) Here are two distinct walks that are not trails: w1 : g, b, e, a, b, e and
w2 : f, d, c, e, f, d. The length of walk w1 is 5 and the length of walk w2 is also 5.
(2) Here are two distinct trails that are not paths: t1 : a, b, c, e, b and t2 : b, e, f, d, c, e.
The length of trail t1 is 4 and the length of trail t2 is 5.
(3) Here are two distinct paths: p1 : a, b, c, d, f, e and p2 : g, b, a, e, f, d. The length of
path p1 is 5 and the length of path p2 is also 5.
(4) Here is a closed trail that is not a cycle: d, c, e, b, a, e, f, d.
(5) Left to the reader.
3
A cycle in a graph is sometimes also called a circuit. Since that terminology unfortunately
conflicts with the closely related notion of a circuit of a matroid, we do not use it here.
13
Theorem 1.13. Every u-v walk in a graph contains a u-v path.

Proof. A walk of length n = 0 is the trivial path. So assume that W is a u-v walk of
length n > 0 in a graph G:
W : u = v0 , v1 , . . . , vn = v.
It is possible that a vertex in W is assigned two different labels. If W has no repeated
vertices, then W is already a path. Otherwise W has at least one repeated vertex. Let
0 i, j n be two distinct integers with i < j such that vi = vj . Deleting the vertices
vi , vi+1 , . . . , vj1 from W results in a u-v walk W1 whose length is less than n. If W1 is
a path, then we are done. Otherwise we repeat the above process to obtain a u-v walk
shorter than W1 . As W is a finite sequence, we only need to apply the above process a
finite number of times to arrive at a u-v path.
A graph is said to be connected if for every pair of distinct vertices u, v there is a
u-v path joining them. A graph that is not connected is referred to as disconnected .
The empty graph is disconnected and so is any nonempty graph with an isolated vertex.
However, the graph in Figure 1.6 is connected. A geodesic path or shortest path between
two distinct vertices u, v of a graph is a u-v path of minimum length. A nonempty graph
may have several shortest paths between some distinct pair of vertices. For the graph
in Figure 1.8, both a, b, c and a, e, c are geodesic paths between a and c. Let H be a
connected subgraph of a graph G such that H is not a proper subgraph of any connected
subgraph of G. Then H is said to be a component of G. We also say that H is a maximal
connected subgraph of G. Any connected graph is its own component. The number of
connected components of a graph G will be denoted (G).
The following is an immediate consequence of Corollary 1.8.
Proposition 1.14. Suppose that exactly two vertices of a graph have odd degree. Then
those two vertices are connected by a path.
Proof. Let G be a graph all of whose vertices are of even degree, except for u and v.
Let C be a component of G containing u. By Corollary 1.8, C also contains v, the only
remaining vertex of odd degree. As u and v belong to the same component, they are
connected by a path.
Example 1.15. Determine whether or not the graph in Figure 1.8 is connected. Find a
shortest path from g to d.
Solution. In the following Sage session, we first construct the graph in Figure 1.8 and
use the method is_connected() to determine whether or not the graph is connected.
Finally, we use the method shortest_path() to find a geodesic path between g and d.
sage :
...
...
sage :
True
sage :
[ g ,
g = Graph ({ " a " :[ " b " ," e " ] , " b " :[ " a " ," g " ," e " ," c " ] , \
" c " :[ " b " ," e " ," d " ] , " d " :[ " c " ," f " ] , " e " :[ " f " ," a " ," b " ," c " ] , \
" f " :[ " g " ," d " ," e " ] , " g " :[ " b " ," f " ]})
g . is_connected ()
g . shortest_path ( " g " , " d " )
f , d ]
This shows that g, f, d is a shortest path from g to d. In fact, any other g-d path has
length greater than 2, so we can say that g, f, d is the shortest path between g and d.
14
Remark 1.16. We will explain Dijkstras algorithm in Chapter 2, which gives one of
the best algorithms for finding shortest paths between two vertices in a connected graph.
What is very remarkable is that, at the present state of knowledge, finding the shortest
path from a vertex v to a particular (but arbitrarily given) vertex w appears to be as
hard as finding the shortest path from a vertex v to all other vertices in the graph!
Trees are a special type of graphs that are used in modelling structures that have
some form of hierarchy. For example, the hierarchy within an organization can be drawn
as a tree structure, similar to the family tree in Figure 1.10. Formally, a tree is an
undirected graph that is connected and has no cycles. If one vertex of a tree is specially
designated as the root vertex , then the tree is called a rooted tree. Chapter 3 covers trees
in more details.
grandma
mum
me
sister
brother
uncle
aunt
cousin1
cousin2
Figure 1.10: A family tree.
1.2.2
Subgraphs, complete and bipartite graphs
Let G be a graph with vertex set V (G) and edge set E(G). Suppose we have a graph
H such that V (H) V (G) and E(H) E(G). Furthermore, suppose the incidence
function i of G, when restricted to E(H), has image in V (H)(2) . Then H is a subgraph
of G. In this situation, G is referred to as a supergraph of H.
Starting from G, one can obtain its subgraph H by deleting edges and/or vertices
from G. Note that when a vertex v is removed from G, then all edges incident with
v are also removed. If V (H) = V (G), then H is called a spanning subgraph of G. In
Figure 1.11, let G be the left-hand side graph and let H be the right-hand side graph.
Then it is clear that H is a spanning subgraph of G. To obtain a spanning subgraph
from a given graph, we delete edges from the given graph.
(a)
(b)
Figure 1.11: A graph and one of its subgraphs.
15
We now consider several standard classes of graphs. The complete graph Kn on n

vertices is a graph such that any two distinct vertices are adjacent. As |V (Kn )| = n,
then |E(Kn )| is equivalent to the total number of 2-combinations from a set of n objects:

n
n(n 1)
|E(Kn )| =
=
.
2
2
(1.4)
Thus for any simple graph G with n vertices, its total number of edges |E(G)| is bounded
above by
n(n 1)
|E(G)|
.
(1.5)
2
Figure 1.12 shows complete graphs each of whose total number of vertices is bounded by
1 n 5. The complete graph K1 has one vertex with no edges. It is also called the
trivial graph.
(a) K5
(b) K4
(c) K3
(d) K2
(e) K1
Figure 1.12: Complete graphs Kn for 1 n 5.

The following result is an application of inequality (1.5).
Theorem 1.17. Let G be a simple graph with n vertices and k components. Then G
has at most 21 (n k)(n k + 1) edges.
Proof. If ni is the number of vertices in component i, then ni > 0 and it can be shown (see
the proof of Lemma 2.1 in [77, pp.2122]) that
X
n2i
X
ni
2
X

(k 1) 2
ni k .
(1.6)
(This
result holds true for any nonempty but finite set of positive integers.) Note that
P
ni = n and by (1.5) each component i has at most 21 ni (ni 1) edges. Apply (1.6) to
get
X ni (ni 1)
2
as required.
1X 2 1X
ni
ni
2
2
1
1
(n2 2nk + k 2 + 2n k) n
2
2
(n k)(n k + 1)
=
2
=
16
(a) C6
(b) C5
(c) C4
(d) C3
Figure 1.13: Cycle graphs Cn for 3 n 6.

The cycle graph on n 3 vertices, denoted Cn , is the connected 2-regular graph on n
vertices. Each vertex in Cn has degree exactly 2 and Cn is connected. Figure 1.13 shows
cycles graphs Cn where 3 n 6. The path graph on n 1 vertices is denoted Pn . For
n = 1, 2 we have P1 = K1 and P2 = K2 . Where n 3, then Pn is a spanning subgraph
of Cn obtained by deleting one edge.
A bipartite graph G is a graph with at least two vertices such that V (G) can be split
into two disjoint subsets V1 and V2 , both nonempty. Every edge uv E(G) is such that
u V1 and v V2 , or v V1 and u V2 . See Kalman [113] for an application of bipartite
graphs to the problem of allocating satellites to radio stations.
Theorem 1.18. A graph is bipartite if and only if it has no odd cycles.
Proof. Necessity (=): Assume G to be bipartite. Traversing each edge involves going
from one side of the bipartition to the other. For a walk to be closed, it must have
even length in order to return to the side of the bipartition from which the walk started.
Thus, any cycle in G must have even length.
Sufficiency (=): Assume G = (V, E) has order n 2 and no odd cycles. If G is
connected, choose any vertex u V and define a partition of V thus:
X = {x V | d(u, x) is even},
Y = {y V | d(u, y) is odd}
where d(u, v) denotes the distance (or length of the shortest path) from u to v. If (X, Y )
is a bipartition of G, then we are done. Otherwise, (X, Y ) is not a bipartition of G.
Then one of X and Y has two vertices v, w joined by an edge e. Let P1 be a shortest
u-v path and P2 be a shortest u-w path. By definition of X and Y , both P1 and P2 have
even lengths or both have odd lengths. From u, let x be the last vertex common to both
P1 and P2 . The subpath u-x of P1 and u-x of P2 have equal length. That is, the subpath
x-v of P1 and x-w of P2 both have even or odd lengths. Construct a cycle C from the
paths x-v and x-w, and the edge e joining v and w. Since x-v and x-w both have even
or odd lengths, the cycle C has odd length, contradicting our hypothesis that G has no
odd cycles. Hence, (X, Y ) is a bipartition of G.
Finally, if G is disconnected, each of its components has no odd cycles. Repeat the
above argument for each component to conclude that G is bipartite.
The complete bipartite graph Km,n is the bipartite graph whose vertex set is partitioned into two nonempty disjoint sets V1 and V2 with |V1 | = m and |V2 | = n. Any
vertex in V1 is adjacent to each vertex in V2 , and any two distinct vertices in Vi are not
adjacent to each other. If m = n, then Kn,n is n-regular. Where m = 1 then K1,n is
1.3. Representing graphs as matrices
17
called the star graph. Figure 1.14 shows a bipartite graph together with the complete
bipartite graphs K4,3 and K3,3 , and the star graph K1,4 .
(a) bipartite
(b) K4,3
(c) K3,3
(d) K1,4
Figure 1.14: Bipartite, complete bipartite, and star graphs.

As an example of K3,3 , suppose that there are 3 boys and 3 girls dancing in a room.
The boys and girls naturally partition the set of all people in the room. Construct a
graph having 6 vertices, each vertex corresponding to a person in the room, and draw
an edge form one vertex to another if the two people dance together. If each girl dances
three times, once with with each of the three boys, then the resulting graph is K3,3 .
1.3
Representing graphs as matrices

Neo: What is the Matrix?
Morpheus: Unfortunately, no one can be told what the Matrix is. You have to see it for
yourself.
From the movie The Matrix, 1999
An m n matrix A can be represented as
a11 a12 a1n

a21 a22 a2n
A=
. . . . . . . . . . . . . . . . . . . .
am1 am2 amn
The positive integers m and n are the row and column dimensions of A, respectively.
The entry in row i column j is denoted aij . Where the dimensions of A are clear from
context, A is also written as A = [aij ].
Representing a graph as a matrix is very inefficient in some cases and not so in
other cases. Imagine you walk into a large room full of people and you consider the
handshaking graph discussed in connection with Theorem 1.7. If not many people
shake hands in the room, it is a waste of time recording all the handshakes and also all
the non-handshakes. This is basically what the adjacency matrix does. In this kind
of sparse graph situation, it would be much easier to simply record the handshakes as
a Python dictionary.4 This section requires some concepts and techniques from linear
algebra, especially matrix theory. See introductory texts on linear algebra and matrix
theory [19] for coverage of such concepts and techniques.
4
A Python dictionary is basically an indexed set. See the reference manual at http://www.python.
org for further details.
18
1.3.1
Adjacency matrix
Let G be an undirected graph with vertices V = {v1 , . . . , vn } and edge set E. The
adjacency matrix of G is the n n matrix A = [aij ] defined by
(
1, if vi vj E,
aij =
0, otherwise.
As G is an undirected graph, then A is a symmetric matrix. That is, A is a square
matrix such that aij = aji .
Now let G be a directed graph with vertices V = {v1 , . . . , vn } and edge set E. The
(0, 1, 1)-adjacency matrix of G is the n n matrix A = [aij ] defined by
if vi vj E,
1,
aij = 1, if vj vi E,
0,
otherwise.
3
(a)
(b)
Figure 1.15: What are the adjacency matrices of these graphs?

Example 1.19. Compute the adjacency matrices of the graphs in Figure 1.15.
Solution. Define the graphs in Figure 1.15 using DiGraph and Graph. Then call the
method adjacency_matrix().
sage : G1 = DiGraph ({1:[2] , 2:[1] , 3:[2 ,6] , 4:[1 ,5] , 5:[6] , 6:[5]})
sage : G2 = Graph ({ " a " :[ " b " ," c " ] , " b " :[ " a " ," d " ] , " c " :[ " a " ," e " ] , \
...
" d " :[ " b " ," f " ] , " e " :[ " c " ," f " ] , " f " :[ " d " ," e " ]})
sage : m1 = G1 . adjacency_matrix (); m1
[0 1 0 0 0 0]
[1 0 0 0 0 0]
[0 1 0 0 0 1]
[1 0 0 0 1 0]
[0 0 0 0 0 1]
[0 0 0 0 1 0]
sage : m2 = G2 . adjacency_matrix (); m2
[0 1 1 0 0 0]
[1 0 0 1 0 0]
[1 0 0 0 1 0]
[0 1 0 0 0 1]
[0 0 1 0 0 1]
[0 0 0 1 1 0]
sage : m1 . is_symmetric ()
False
sage : m2 . is_symmetric ()
True
19
In general, the adjacency matrix of a digraph is not symmetric, while that of an undirected graph is symmetric.
More generally, if G is an undirected multigraph with edge eij = vi vj having multiplicity wij , or a weighted graph with edge eij = vi vj having weight wij , then we can
define the (weighted) adjacency matrix A = [aij ] by
aij =
(
wij , if vi vj E,
0,
otherwise.
For example, Sage allows you to easily compute a weighted adjacency matrix.
sage : G = Graph ( sparse = True , weighted = True )
sage : G . add_edges ([(0 ,1 ,1) , (1 ,2 ,2) , (0 ,2 ,3) , (0 ,3 ,4)])
sage : M = G . w e i g h t e d _ a d ja c e n c y _ m a t r i x (); M
[0 1 3 4]
[1 0 2 0]
[3 2 0 0]
[4 0 0 0]
Bipartite case
Suppose G = (V, E) is an undirected bipartite graph and V = V1 V2 is the partition
of the vertices into n1 vertices in V1 and n2 vertices in V2 , so |V | = n1+ n2 . Then
the

A1 0
adjacency matrix A of G can be realized as a block diagonal matrix A =
, where
0 A2
A1 is an n1 n2 matrix and A2 is an n2 n1 matrix. Since G is undirected, A2 = AT1 .
The matrix is called a reduced adjacency matrix or a bi-adjacency matrix (the literature
also uses the terms transfer matrix or the ambiguous term adjacency matrix).
Tanner graphs
If H is an m n (0, 1)-matrix, then the Tanner graph of H is the bipartite graph
G = (V, E) whose set of vertices V = V1 V2 is partitioned into two sets: V1 corresponding
to the m rows of H and V2 corresponding to the n columns of H. For any i, j with
1 i m and 1 j n, there is an edge ij E if and only if the (i, j)-th entry of
H is 1. This matrix H is sometimes called the reduced adjacency matrix or the check
matrix of the Tanner graph. Tanner graphs are used in the theory of error-correcting
codes. For example, Sage allows you to easily compute such a bipartite graph from its
matrix.
sage : H = Matrix ([(1 ,1 ,1 ,0 ,0) , (0 ,0 ,1 ,0 ,1) , (1 ,0 ,0 ,1 ,1)])
sage : B = BipartiteGraph ( H )
sage : B . r ed u c e d_ a d j ac e n c y_ m a t ri x ()
[1 1 1 0 0]
[0 0 1 0 1]
[1 0 0 1 1]
sage : B . plot ( graph_border = True )
The corresponding graph is similar to that in Figure 1.16.

Theorem 1.20. Let A be the adjacency matrix of a graph G with vertex set V =
{v1 , v2 , . . . , vp }. For each positive integer n, the ij-th entry of An counts the number
of vi -vj walks of length n in G.
20

1
Figure 1.16: A Tanner graph.

Proof. We shall prove by induction on n. For the base case n = 1, the ij-th entry of
A1 counts the number of walks of length 1 from vi to vj . This is obvious because A1 is
merely the adjacency matrix A.
Suppose for induction that for some positive integer k 1, the ij-th entry of Ak
counts the number of walks of length k from vi to vj . We need to show that the ij-th
entry of Ak+1 counts the number of vi -vj walks of length k + 1. Let A = [aij ], Ak = [bij ],
and Ak+1 = [cij ]. Since Ak+1 = AAk , then
cij =
p
X
air brj
r=1
for i, j = 1, 2, . . . , p. Note that air is the number of edges from vi to vr , and brj is the
number of vr -vj walks of length k. Any edge from vi to vr can be joined with any vr -vj
walk to create a walk vi , vr , . . . , vj of length k + 1. Then for each r = 1, 2, . . . , p, the
value air brj counts the number of vi -vj walks of length k + 1 with vr being the second
vertex in the walk. Thus cij counts the total number of vi -vj walks of length k + 1.
1.3.2
Incidence matrix
The relationship between edges and vertices provides a very strong constraint on the
data structure, much like the relationship between points and blocks in a combinatorial
design or points and lines in a finite plane geometry. This incidence structure gives rise
to another way to describe a graph using a matrix.
Let G be a digraph with edge set E = {e1 , . . . , em } and vertex set V = {v1 , . . . , vn }.
The incidence matrix of G is the n m matrix B = [bij ] defined by
1, if vi is the tail of ej ,
1,
if vi is the head of ej ,
(1.7)
bij =
2,
if ej is a self-loop at vi ,
0,
otherwise.
Each column of B corresponds to an edge and each row corresponds to a vertex. The
definition of incidence matrix of a digraph as contained in expression (1.7) is applicable
to digraphs with self-loops as well as multidigraphs.
For the undirected case, let G be an undirected graph with edge set E = {e1 , . . . , em }
and vertex set V = {v1 , . . . , vn }. The unoriented incidence matrix of G is the n m
21
matrix B = [bij ] defined by
1, if vi is incident to ej ,
bij = 2, if ej is a self-loop at vi ,
0, otherwise.
An orientation of an undirected graph G is an assignment of direction to each edge of G.

The oriented incidence matrix of G is defined similarly to the case where G is a digraph:
it is the incidence matrix of any orientation of G. For each column of B, we have 1 as
an entry in the row corresponding to one vertex of the edge under consideration and 1
as an entry in the row corresponding to the other vertex. Similarly, bij = 2 if ej is a
self-loop at vi .
1.3.3
Laplacian matrix
The degree matrix of a graph G = (V, E) is an n n diagonal matrix D whose i-th

diagonal entry is the degree of the i-th vertex in V . The Laplacian matrix L of G is the
difference between the degree matrix and the adjacency matrix:
L = D A.
In other words, for an undirected unweighted simple graph, L = [ìj ] is given by
1, if i 6= j and vi vj E,
ìj = di , if i = j,
0,
otherwise,
where di = deg(vi ) is the degree of vertex vi .
Sage allows you to compute the Laplacian matrix of a graph:
sage : G = Graph ({1:[2 ,4] , 2:[1 ,4] , 3:[2 ,6] , 4:[1 ,3] , 5:[4 ,2] , 6:[3 ,1]})
sage : G . laplacian_matrix ()
[ 3 -1 0 -1 0 -1]
[ -1 4 -1 -1 -1 0]
[ 0 -1 3 -1 0 -1]
[ -1 -1 -1 4 -1 0]
[ 0 -1 0 -1 2 0]
[ -1 0 -1 0 0 2]
There are many remarkable properties of the Laplacian matrix. It shall be discussed
further in Chapter 5.
1.3.4
Distance matrix
Recall that the distance (or geodesic distance) d(v, w) between two vertices v, w V in a
connected graph G = (V, E) is the number of edges in a shortest path connecting them.
The n n matrix [d(vi , vj )] is the distance matrix of G. Sage helps you to compute the
distance matrix of a graph:
sage : G = Graph ({1:[2 ,4] , 2:[1 ,4] , 3:[2 ,6] , 4:[1 ,3] , 5:[4 ,2] , 6:[3 ,1]})
sage : d = [[ G . distance (i , j ) for i in range (1 ,7)] for j in range (1 ,7)]
sage : matrix ( d )
[0 1 2 1 2 1]
[1 0 1 1 1 2]
[2 1 0 1 2 1]
[1 1 1 0 1 2]
[2 1 2 1 0 3]
[1 2 1 2 3 0]
22
The distance matrix is an important quantity which allows one to better understand
the connectivity of a graph. Distance and connectivity will be discussed in more detail
in Chapters 5 and 10.
1.4
Isomorphic graphs
Determining whether or not two graphs are, in some sense, the same is a hard but
important problem. Two graphs G and H are isomorphic if there is a bijection f :
V (G) V (H) such that whenever uv E(G) then f (u)f (v) E(H). The function
f is an isomorphism between G and H. Otherwise, G and H are non-isomorphic. If G
and H are isomorphic, we write G
= H.
(a)
(b)
Figure 1.17: Two representations of the Franklin graph.
(a) C6
(b) G1
(c) G2
Figure 1.18: Isomorphic and nonisomorphic graphs.

A graph G is isomorphic to a graph H if these two graphs can be labelled in such a
way that if u and v are adjacent in G, then their counterparts in V (H) are also adjacent
in H. To determine whether or not two graphs are isomorphic is to determine if they are
structurally equivalent. Graphs G and H may be drawn differently so that they seem
different. However, if G
= H then the isomorphism f : V (G) V (H) shows that both
of these graphs are fundamentally the same. In particular, the order and size of G are
equal to those of H, the isomorphism f preserves adjacencies, and deg(v) = deg(f (v)) for
all v G. Since f preserves adjacencies, then adjacencies along a given geodesic path are
preserved as well. That is, if v1 , v2 , v3 , . . . , vk is a shortest path between v1 , vk V (G),
then f (v1 ), f (v2 ), f (v3 ), . . . , f (vk ) is a geodesic path between f (v1 ), f (vk ) V (H). For
example, the two graphs in Figure 1.17 are isomorphic to each other.
1.4. Isomorphic graphs
23
Example 1.21. Consider the graphs in Figure 1.18. Which pair of graphs are isomorphic, and which two graphs are non-isomorphic?
Solution. If G is a Sage graph, one can use the method G.is_isomorphic() to determine
whether or not the graph G is isomorphic to another graph. The following Sage session
illustrates how to use G.is_isomorphic().
sage :
...
sage :
...
sage :
...
sage :
True
sage :
False
sage :
False
C6 = Graph ({ " a " :[ " b " ," c " ] , " b " :[ " a " ," d " ] , " c " :[ " a " ," e " ] , \
" d " :[ " b " ," f " ] , " e " :[ " c " ," f " ] , " f " :[ " d " ," e " ]})
G1 = Graph ({1:[2 ,4] , 2:[1 ,3] , 3:[2 ,6] , 4:[1 ,5] , \
5:[4 ,6] , 6:[3 ,5]})
G2 = Graph ({ " a " :[ " d " ," e " ] , " b " :[ " c " ," f " ] , " c " :[ " b " ," f " ] , \
" d " :[ " a " ," e " ] , " e " :[ " a " ," d " ] , " f " :[ " b " ," c " ]})
C6 . is_isomorphic ( G1 )
C6 . is_isomorphic ( G2 )
G1 . is_isomorphic ( G2 )
Thus, for the graphs C6 , G1 and G2 in Figure 1.18, C6 and G1 are isomorphic, but G1
and G2 are not isomorphic.
An important notion in graph theory is the idea of an invariant. An invariant is
an object f = f (G) associated to a graph G which has the property
G
= H = f (G) = f (H).
For example, the number of vertices of a graph, f (G) = |V (G)|, is an invariant.
1.4.1
Adjacency matrices
Two n n matrices A1 and A2 are permutation equivalent if there is a permutation

matrix P such that A1 = P A2 P 1 . In other words, A1 is the same as A2 after a suitable
re-ordering of the rows and a corresponding re-ordering of the columns. This notion of
permutation equivalence is an equivalence relation.
To show that two undirected graphs are isomorphic depends on the following result.
Theorem 1.22. Consider two directed or undirected graphs G1 and G2 with respective
adjacency matrices A1 and A2 . Then G1 and G2 are isomorphic if and only if A1 is
permutation equivalent to A2 .
This says that the permutation equivalence class of the adjacency matrix is an invariant.
Define an ordering on the set of nn (0, 1)-matrices as follows: we say A1 < A2 if the
list of entries of A1 is less than or equal to the list of entries of A2 in the lexicographical
ordering. Here, the list of entries of a (0, 1)-matrix is obtained by concatenating the
entries of the matrix, row-by-row. For example,

1 1
1 1
<
.
0 1
1 1
Algorithm 1.1 is an immediate consequence of Theorem 1.22. The lexicographically
maximal element of the permutation equivalence class of the adjacency matrix of G is
called the canonical label of G. Thus, to check if two undirected graphs are isomorphic,
we simply check if their canonical labels are equal. This idea for graph isomorphism
checking is presented in Algorithm 1.1.
24
Algorithm 1.1: Computing graph isomorphism using canonical labels.

Input: Two undirected simple graphs G1 and G2 , each having n vertices.
Output: True if G1
= G2 ; False otherwise.
1
2
3
4
5
6
7
for i 1, 2 do
Ai adjacency matrix of Gi
pi permutation equivalence class of Ai
A0i lexicographically maximal element of pi
if A01 = A02 then
return True
return False
1.4.2
Degree sequence
Let G be a graph with n vertices. The degree sequence of G is the ordered n-tuple of the
vertex degrees of G arranged in non-increasing order.
The degree sequence of G may contain the same degrees, repeated as often as they
occur. For example, the degree sequence of C6 is 2, 2, 2, 2, 2, 2 and the degree sequence
of the house graph in Figure 1.3 is 3, 3, 2, 2, 2. If n 3 then the cycle graph Cn has the
degree sequence
2, 2, 2, . . . , 2 .
{z
}
|
n copies of 2
The path Pn , for n 3, has the degree sequence
2, 2, 2, . . . , 2, 1, 1 .
|
{z
}
n2 copies of 2
For positive integer values of n and m, the complete graph Kn has the degree sequence
n 1, n 1, n 1, . . . , n 1
|
{z
}
n copies of n1
and the complete bipartite graph Km,n has the degree sequence
n, n, n, . . . , n, m, m, m, . . . , m .
|
{z
}|
{z
}
m copies of n
n copies of m
Let S be a non-increasing sequence of non-negative integers. Then S is said to be

graphical if it is the degree sequence of some graph. If G is a graph with degree sequence
S, we say that G realizes S.
Let S = (d1 , d2 , . . . , dn ) be a graphical sequence,
i.e. di dj for all i j such that
P
1 i, j n. From Corollary 1.9 we see that di S di = 2k for some integer k 0. In
other words, the sum of a graphical sequence is nonnegative and even. In 1961, Erdos
and Gallai [68] used this observation as part of a theorem that provides necessary and
sufficient conditions for a sequence to be realized by a simple graph. The result is stated
in Theorem 1.23, but the original paper of Erdos and Gallai [68] does not provide an
algorithm to construct a simple graph with a given degree sequence. For a simple graph
that has a degree sequence with repeated elements, e.g. the degree sequences of Cn ,
Pn , Kn , and Km,n , it is redundant to verify inequality (1.8) for repeated elements of
that sequence. In 2003, Tripathi and Vijay [182] showed that one only needs to verify
inequality (1.8) for as many times as there are distinct terms in S.
1.4. Isomorphic graphs
25
Theorem 1.23. Erd

os & Gallai 1961 [68]. Let d = (d1 , d2 , . . . , dn ) be a sequence
of P
positive integers such that di di+1 . Then d is realized by a simple graph if and only
if i di is even and
k
n
X
X
di k(k + 1) +
min{k, di }
(1.8)
i=1
j=k+1
for all 1 k n 1.
As noted above, Theorem 1.23 is an existence result showing that something exists without providing a construction of the object under consideration. Havel [95] and
Hakimi [93, 94] independently provided an algorithmic approach that allows for constructing a simple graph with a given degree sequence. See Sierksma and Hoogeveen [171]
for a coverage of seven criteria for a sequence of integers to be graphic. See Erdos et al. [71]
for an extension of the Havel-Hakimi theorem to digraphs.
Theorem 1.24. Havel 1955 [95] & Hakimi 19623 [93, 94]. Consider the nonincreasing sequence S1 = (d1 , d2 , . . . , dn ) of nonnegative integers, where n 2 and d1 1.
Then S1 is graphical if and only if the sequence
S2 = (d2 1, d3 1, . . . , dd1 +1 1, dd1 +2 , . . . , dn )
is graphical.
Proof. Suppose S2 is graphical. Let G2 = (V2 , E2 ) be a graph of order n 1 with vertex
set V2 = {v2 , v3 , . . . , vn } such that
(
di 1, if 2 i d1 + 1,
deg(vi ) =
di ,
if d1 + 2 i n.
Construct a new graph G1 with degree sequence S1 as follows. Add another vertex v1
to V2 and add to E2 the edges v1 vi for 2 i d1 + 1. It is clear that deg(v1 ) = d1 and
deg(vi ) = di for 2 i n. Thus G1 has the degree sequence S1 .
On the other hand, suppose S1 is graphical and let G1 be a graph with degree sequence
S1 such that
(i) The graph G1 has the vertex set V (G1 ) = {v1 , v2 , . . . , vn } and deg(vi ) = di for
i = 1, . . . , n.
(ii) The degree sum of all vertices adjacent to v1 is a maximum.
To obtain a contradiction, suppose v1 is not adjacent to vertices having degrees
d2 , d3 , . . . , dd1 +1 .
Then there exist vertices vi and vj with dj > di such that v1 vi E(G1 ) but v1 vj 6 E(G1 ).
As dj > di , there is a vertex vk such that vj vk E(G1 ) but vi vk 6 E(G1 ). Replacing the
edges v1 vi and vj vk with v1 vj and vi vk , respectively, results in a new graph H whose degree
sequence is S1 . However, the graph H is such that the degree sum of vertices adjacent to
v1 is greater than the corresponding degree sum in G1 , contradicting property (ii) in our
choice of G1 . Consequently, v1 is adjacent to d1 other vertices of largest degree. Then
S2 is graphical because G1 v1 has degree sequence S2 .
26
The proof of Theorem 1.24 can be adapted into an algorithm to determine whether
or not a sequence of nonnegative integers can be realized by a simple graph. If G is
a simple graph, the degree of any vertex in V (G) cannot exceed the order of G. By
the handshaking lemma (Theorem 1.7), the sum of all terms in the sequence cannot be
odd. Once the sequence passes these two preliminary tests, we then adapt the proof of
Theorem 1.24 to successively reduce the original sequence to a smaller sequence. These
ideas are summarized in Algorithm 1.2.
Algorithm 1.2: Havel-Hakimi test for sequences realizable by simple graphs.
Input: A nonincreasing sequence S = (d1 , d2 , . . . , dn ) of nonnegative integers,
where n 2.
Output: True if S is realizable by a simple graph; False otherwise.
P
1 if
i di is odd then
2
return False
3 while True do
4
if min(S) < 0 then
5
return False
6
if max(S) = 0 then
7
return True
8
if max(S) > length(S) 1 then
9
return False
10
S (d2 1, d3 1, . . . , dd1 +1 1, dd1 +2 , . . . , dlength(S) )
11
sort S in nonincreasing order
We now show that Algorithm 1.2 determines whether or not a sequence of integers
is realizable by a simple graph. Our input is a sequence S = (d1 , d2 , . . . , dn ) arranged
in non-increasing order, where each di 0. The first test as contained in the if block,
otherwise known as a conditional, on line 1 uses the handshaking lemma (Theorem 1.7).
During the first run of the while loop, the conditional on line 4 ensures that the sequence
S only consists of nonnegative integers. At the conditional on line 6, we know that S
is arranged in non-increasing order and has nonnegative integers. If this conditional
holds true, then S is a sequence of zeros and it is realizable by a graph with only isolated
vertices. Such a graph is simple by definition. The conditional on line 8 uses the following
property of simple graphs: If G is a simple graph, then the degree of each vertex of G
is less than the order of G. By the time we reach line 10, we know that S has n terms,
max(S) > 0, and 0 di n 1 for all i = 1, 2, . . . , n. After applying line 10, S is now a
sequence of n 1 terms with max(S) > 0 and 0 di n 2 for all i = 1, 2, . . . , n 1. In
general, after k rounds of the while loop, S is a sequence of n k terms with max(S) > 0
and 0 di n k 1 for all i = 1, 2, . . . , n k. And after n 1 rounds of the while
loop, the resulting sequence has one term whose value is zero. In other words, eventually
Algorithm 1.2 produces a sequence with a negative term or a sequence of zeros.
1.4.3
Invariants revisited
In some cases, one can distinguish non-isomorphic graphs by considering graph invariants.
For instance, the graphs C6 and G1 in Figure 1.18 are isomorphic so they have the same
number of vertices and edges. Also, G1 and G2 in Figure 1.18 are non-isomorphic because
1.5. New graphs from old
27
the former is connected, while the latter is not connected. To prove that two graphs
are non-isomorphic, one could show that they have different values for a given graph
invariant. The following list contains some items to check off when showing that two
graphs are non-isomorphic:
1. the number of vertices,
2. the number of edges,
3. the degree sequence,
4. the length of a geodesic path,
5. the length of the longest path,
6. the number of connected components of a graph.
1.5
New graphs from old
This section provides a brief survey of operations on graphs to obtain new graphs from
old graphs. Such graph operations include unions, products, edge addition, edge deletion,
vertex addition, and vertex deletion. Several of these are briefly described below.
1.5.1
Union, intersection, and join
The disjoint union of graphs is defined as follows. For two graphs G1 = (V1 , E1 ) and
G2 = (V2 , E2 ) with disjoint vertex sets, their disjoint union is the graph
G1 G2 = (V1 V2 , E1 E2 ).
For example, Figure 1.19 shows the vertex disjoint union of the complete bipartite graph
K1,5 with the wheel graph W4 . The adjacency matrix A of the disjoint union of two
graphs G1 and G2 is the diagonal block matrix obtained from the adjacency matrices A1
and A2 , respectively. Namely,

A1 0
A=
.
0 A2
Sage can compute graph unions, as the following example shows.
sage : G1 = Graph ({1:[2 ,4] , 2:[1 ,3] , 3:[2 ,6] , 4:[1 ,5] , 5:[4 ,6] , 6:[3 ,5]})
sage : G2 = Graph ({7:[8 ,10] , 8:[7 ,10] , 9:[8 ,12] , 10:[7 ,9] , 11:[10 ,8] , 12:[9 ,7]})
sage : G1u2 = G1 . union ( G2 )
sage : G1u2 . adjacency_matrix ()
[0 1 0 1 0 0 0 0 0 0 0 0]
[1 0 1 0 0 0 0 0 0 0 0 0]
[0 1 0 0 0 1 0 0 0 0 0 0]
[1 0 0 0 1 0 0 0 0 0 0 0]
[0 0 0 1 0 1 0 0 0 0 0 0]
[0 0 1 0 1 0 0 0 0 0 0 0]
[0 0 0 0 0 0 0 1 0 1 0 1]
[0 0 0 0 0 0 1 0 1 1 1 0]
[0 0 0 0 0 0 0 1 0 1 0 1]
[0 0 0 0 0 0 1 1 1 0 1 0]
[0 0 0 0 0 0 0 1 0 1 0 0]
[0 0 0 0 0 0 1 0 1 0 0 0]
28
In the case where V1 = V2 , then G1 G2 is simply the graph consisting of all edges in G1
or in G2 . In general, the union of two graphs G1 = (V1 , E1 ) and G2 = (V2 , E2 ) is defined
as
G1 G2 = (V1 V2 , E1 E2 )
where V1 V2 , V2 V1 , V1 = V2 , or V1 V2 = . Figure 1.20(c) illustrates the graph

union where one vertex set is a proper subset of the other. If G1 , G2 , . . . , Gn are the
components
S of a graph G, then G is obtained by the disjoint union of its components,
i.e. G = Gi .
Figure 1.19: The vertex disjoint union K1,5 W4 .

3
3
1
4
1
4
2
(a) G1
(b) G2
(c) G1 G2
(d) G1 G2
Figure 1.20: The union and intersection of graphs with overlapping vertex sets.
The intersection of graphs is defined as follows. For two graphs G1 = (V1 , E1 ) and
G2 = (V2 , E2 ), their intersection is the graph
G1 G2 = (V1 V2 , E1 E2 ).
Figure 1.20(d) illustrates the intersection of two graphs whose vertex sets overlap.
The symmetric difference of graphs is defined as follows. For two graphs G1 = (V1 , E1 )
and G2 = (V2 , E2 ), their symmetric difference is the graph
G1 G2 = (V, E)
where V = V1 V2 and the edge set is given by
E = (E1 E2 )\{uv | u V1 V2
or v V1 V2 }.
Recall that the symmetric difference of two sets S1 and S2 is defined by

S1 S2 = {x S1 S2 | x
/ S1 S2 }.
In the case where V1 = V2 , then G1 G2 is simply the empty graph. See Figure 1.21 for
an illustration of the symmetric difference of two graphs.
The join of two disjoint graphs G1 and G2 , denoted G1 +G2 , is their graph union, with
each vertex of one graph connecting to each vertex of the other graph. For example, the
join of the cycle graph Cn1 with a single vertex graph is the wheel graph Wn . Figure 1.22
shows various wheel graphs.
29
5
5
3
7
4
1
(a) G1
(b) G2
(c) G1 G2
Figure 1.21: The symmetric difference of graphs.
(a) W4
(b) W5
(c) W6
(d) W7
(e) W8
(f) W9
Figure 1.22: The wheel graphs Wn for n = 4, . . . , 9.
30
1.5.2
Edge or vertex deletion/insertion
Vertex deletion subgraph

If G = (V, E) is any graph with at least 2 vertices, then the vertex deletion subgraph is
the subgraph obtained from G by deleting a vertex v V and also all the edges incident
to that vertex. The vertex deletion subgraph of G is sometimes denoted G {v}. Sage
can compute vertex deletions, as the following example shows.
sage : G = Graph ({1:[2 ,4] , 2:[1 ,4] , 3:[2 ,6] , 4:[1 ,3] , 5:[4 ,2] , 6:[3 ,1]})
[1 , 2 , 3 , 4 , 5 , 6]
sage : E1 = Set ( G . edges ( labels = False )); E1
{(1 , 2) , (4 , 5) , (1 , 4) , (2 , 3) , (3 , 6) , (1 , 6) , (2 , 5) , (3 , 4) , (2 , 4)}
sage : E4 = Set ( G . edges_incident ( vertices =[4] , labels = False )); E4
{(4 , 5) , (3 , 4) , (2 , 4) , (1 , 4)}
sage : G . delete_vertex (4)
[1 , 2 , 3 , 5 , 6]
{(1 , 2) , (1 , 6) , (2 , 5) , (2 , 3) , (3 , 6)}
sage : E1 . difference ( E2 ) == E4
True
Figure 1.23 presents a sequence of subgraphs obtained by repeatedly deleting vertices.

As the figure shows, when a vertex is deleted from a graph, all edges incident on that
vertex are deleted as well.
c
(b) G {b}
(a) G
c
(c) G {a, b}
(d) G {a, b, e}
(e) G {a, b, c, d, e}
Figure 1.23: Obtaining subgraphs via repeated vertex deletion.
31
Edge deletion subgraph

If G = (V, E) is any graph with at least 1 edge, then the edge deletion subgraph is the
subgraph obtained from G by deleting an edge e E, but not the vertices incident to
that edge. The edge deletion subgraph of G is sometimes denoted G {e}. Sage can
compute edge deletions, as the following example shows.
sage : G = Graph ({1:[2 ,4] , 2:[1 ,4] , 3:[2 ,6] , 4:[1 ,3] , 5:[4 ,2] , 6:[3 ,1]})
{(1 , 2) , (4 , 5) , (1 , 4) , (2 , 3) , (3 , 6) , (1 , 6) , (2 , 5) , (3 , 4) , (2 , 4)}
sage : V1 = G . vertices (); V1
[1 , 2 , 3 , 4 , 5 , 6]
sage : E14 = Set ([(1 ,4)]); E14
{(1 , 4)}
sage : G . delete_edge ([1 ,4])
{(1 , 2) , (4 , 5) , (2 , 3) , (3 , 6) , (1 , 6) , (2 , 5) , (3 , 4) , (2 , 4)}
sage : E1 . difference ( E2 ) == E14
True
Figure 1.24 shows a sequence of graphs resulting from edge deletion. Unlike vertex
deletion, when an edge is deleted the vertices incident on that edge are left intact.
b
(a) G
(b) G {ac}
(c) G {ab, ac, bc}
Figure 1.24: Obtaining subgraphs via repeated edge deletion.
Vertex cut, cut vertex, or cutpoint

A vertex cut (or separating set) of a connected graph G = (V, E) is a subset W V
such that the vertex deletion subgraph G W is disconnected. In fact, if v1 , v2 V are
two non-adjacent vertices, then you can ask for a vertex cut W for which v1 , v2 belong
to different components of G W . Sages vertex_cut method allows you to compute a
minimal cut having this property. For many connected graphs, the removal of a single
vertex is sufficient for the graph to be disconnected (see Figure 1.24(c)).
Edge cut, cut edge, or bridge
If deleting a single, specific edge would disconnect a graph G, that edge is called a
bridge. More generally, the edge cut (or disconnecting set or seg) of a connected graph
G = (V, E) is a set of edges F E whose removal yields an edge deletion subgraph
G F that is disconnected. A minimal edge cut is called a cut set or a bond . In fact, if
v1 , v2 V are two vertices, then you can ask for an edge cut F for which v1 , v2 belong
to different components of G F . Sages edge_cut method allows you to compute a
minimal cut having this property. For example, any of the three edges in Figure 1.24(c)
qualifies as a bridge and those three edges form an edge cut for the graph in question.
Theorem 1.25. Let G be a connected graph. An edge e E(G) is a bridge of G if and
only if e does not lie on a cycle of G.
32
Proof. First, assume that e = uv is a bridge of G. Suppose for contradiction that e lies
on a cycle
C : u, v, w1 , w2 , . . . , wk , u.
Then G e contains a u-v path u, wk , . . . , w2 , w1 , v. Let u1 , v1 be any two vertices in
G e. By hypothesis, G is connected so there is a u1 -v1 path P in G. If e does not lie
on P , then P is also a path in G e so that u1 , v1 are connected, which contradicts our
assumption of e being a bridge. On the other hand, if e lies on P , then express P as
u1 , . . . , u, v, . . . , v1
or u1 , . . . , v, u, . . . , v1 .
Now
u1 , . . . , u, wk , . . . , w2 , w1 , v, . . . , v1
or u1 , . . . , v, w1 , w2 , . . . , wk , u, . . . , v1
respectively is a u1 -v1 walk in G e. By Theorem 1.13, G e contains a u1 -v1 path,

which contradicts our assumption about e being a bridge.
Conversely, let e = uv be an edge that does not lie on any cycles of G. If G e has no
u-v paths, then we are done. Otherwise, assume for contradiction that G e has a u-v
path P . Then P with uv produces a cycle in G. This cycle contains e, in contradiction
of our assumption that e does not lie on any cycles of G.
Edge contraction
An edge contraction is an operation which, like edge deletion, removes an edge from a
graph. However, unlike edge deletion, edge contraction also merges together the two
vertices the edge used to connect. For a graph G = (V, E) and an edge uv = e E, the
edge contraction G/e is the graph obtained as follows:
1. Delete the vertices u, v from G.
2. In place of u, v is a new vertex ve .
3. The vertex ve is adjacent to vertices that were adjacent to u, v, or both u and v.

The vertex set of G/e = (V 0 , E 0 ) is defined as V 0 = V \{u, v} {ve } and its edge set is

E 0 = wx E | {w, x} {u, v} = ve w | uw E\{e} or vw E\{e} .
Make the substitutions

E1 = wx E | {w, x} {u, v} =

E2 = ve w | uw E\{e} or vw E\{e} .
Let G be the wheel graph W6 in Figure 1.25(a) and consider the edge contraction G/ab,
where ab is the gray colored edge in that figure. Then the edge set E1 denotes all those
edges in G each of which is not incident on a, b, or both a and b. These are precisely
those edges that are colored red. The edge set E2 means that we consider those edges in
G each of which is incident on exactly one of a or b, but not both. The blue colored edges
in Figure 1.25(a) are precisely those edges that E2 suggests for consideration. The result
of the edge contraction G/ab is the wheel graph W5 in Figure 1.25(b). Figures 1.25(a)
to 1.25(f) present a sequence of edge contractions that starts with W6 and repeatedly
contracts it to the trivial graph K1 .
33
d
d
d
f
e
c
f
vab = g
(a) G1
vcg = h
(b) G2 = G1 /ab
(c) G3 = G2 /cg
vdh = i
(d) G4 = G3 /dh
vf i = j
(e) G5 = G4 /f i
vej
(f) G6 = G5 /ej
Figure 1.25: Contracting the wheel graph W6 to the trivial graph K1 .
1.5.3
Complements
The complement of a simple graph has the same vertices, but exactly those edges that
are not in the original graph. In other words, if Gc = (V, E c ) is the complement of
G = (V, E), then two distinct vertices v, w V are adjacent in Gc if and only if they are
not adjacent in G. We also write the complement of G as G. The sum of the adjacency
matrix of G and that of Gc is the matrix with 1s everywhere, except for 0s on the
main diagonal. A simple graph that is isomorphic to its complement is called a selfcomplementary graph. Let H be a subgraph of G. The relative complement of G and H
is the edge deletion subgraph G E(H). That is, we delete from G all edges in H. Sage
can compute edge complements, as the following example shows.
sage : G = Graph ({1:[2 ,4] , 2:[1 ,4] , 3:[2 ,6] , 4:[1 ,3] , 5:[4 ,2] , 6:[3 ,1]})
sage : Gc = G . complement ()
sage : EG = Set ( G . edges ( labels = False )); EG
{(1 , 2) , (4 , 5) , (1 , 4) , (2 , 3) , (3 , 6) , (1 , 6) , (2 , 5) , (3 , 4) , (2 , 4)}
sage : EGc = Set ( Gc . edges ( labels = False )); EGc
{(1 , 5) , (2 , 6) , (4 , 6) , (1 , 3) , (5 , 6) , (3 , 5)}
sage : EG . difference ( EGc ) == EG
True
sage : EGc . difference ( EG ) == EGc
True
sage : EG . intersection ( EGc )
{}
Theorem 1.26. If G = (V, E) is self-complementary, then the order of G is |V | = 4k

or |V | = 4k + 1 for some nonnegative integer k. Furthermore, if n = |V | is the order of
G, then the size of G is |E| = n(n 1)/4.
Proof. Let G be a self-complementary graph of order n. Each of G and Gc contains half
the number of edges in Kn . From (1.4), we have
|E(G)| = |E(Gc )| =
n(n 1)
1 n(n 1)
=
.
2
2
4
34
Then n | n(n 1), with one of n and n 1 being even and the other odd. If n is even,
n 1 is odd so gcd(4, n 1) = 1, hence by [170, Theorem 1.9] we have 4 | n and so
n = 4k for some nonnegative k Z. If n 1 is even, use a similar argument to conclude
that n = 4k + 1 for some nonnegative k Z.
Theorem 1.27. A graph and its complement cannot be both disconnected.
Proof. If G is connected, then we are done. Without loss of generality, assume that G
is disconnected and let G be the complement of G. Let u, v be vertices in G. If u, v
are in different components of G, then they are adjacent in G. If both u, v belong to
some component Ci of G, let w be a vertex in a different component Cj of G. Then u, w
are adjacent in G, and similarly for v and w. That is, u and v are connected in G and
therefore G is connected.
1.5.4
Cartesian product
The Cartesian product GH of graphs G and H is a graph such that the vertex set of
GH is the Cartesian product
V (GH) = V (G) V (H).
Any two vertices (u, u0 ) and (v, v 0 ) are adjacent in GH if and only if either
1. u = v and u0 is adjacent with v 0 in H; or
2. u0 = v 0 and u is adjacent with v in G.
The vertex set of GH is V (GH) and the edge set of GH is

E(GH) = V (G) E(H) E(G) V (H) .
Sage can compute Cartesian products, as the following example shows.

sage : Z = graphs . CompleteGraph (2); len ( Z . vertices ()); len ( Z . edges ())
2
1
sage : C = graphs . CycleGraph (5); len ( C . vertices ()); len ( C . edges ())
5
5
sage : P = C . cartesian_product ( Z ); len ( P . vertices ()); len ( P . edges ())
10
15
The path graph Pn is a tree with n vertices V = {v1 , v2 , . . . , vn } and edges E =

{(vi , vi+1 ) | 1 i n 1}. In this case, deg(v1 ) = deg(vn ) = 1 and deg(vi ) = 2 for
1 < i < n. The path graph Pn can be obtained from the cycle graph Cn by deleting
one edge of Cn . The ladder graph Ln is the Cartesian product of path graphs, i.e.
Ln = Pn P1 .
The Cartesian product of two graphs G1 and G2 can be visualized as follows. Let V1 =
{u1 , u2 , . . . , um } and V2 = {v1 , v2 , . . . , vn } be the vertex sets of G1 and G2 , respectively.
Let H1 , H2 , . . . , Hn be n copies of G1 . Place each Hi at the location of vi in G2 . Then
ui V (Hj ) is adjacent to ui V (Hk ) if and only if vjk E(G2 ). See Figure 1.26 for an
illustration of obtaining the Cartesian product of K3 and P3 .
The hypercube graph Qn is the n-regular graph having vertex set

V = (1 , . . . , n ) | i {0, 1}
of cardinality 2n . That is, each vertex of Qn is a bit string of length n. Two vertices
v, w V are connected by an edge if and only if v and w differ in exactly one coordinate.5
5
In other words, the Hamming distance between v and w is equal to 1.
35
(a) K3
(b) P3
(c) K3 P3
Figure 1.26: The Cartesian product of K3 and P3 .

The Cartesian product of n edge graphs K2 is a hypercube:
(K2 )n = Qn .
Figure 1.27 illustrates the hypercube graphs Qn for n = 1, . . . , 4.
(a) Q1
(b) Q2
(c) Q3
(d) Q4
Figure 1.27: Hypercube graphs Qn for n = 1, . . . , 4.

Example 1.28. The Cartesian product of two hypercube graphs is another hypercube,
i.e. Qi Qj = Qi+j .
Another family of graphs that can be constructed via Cartesian product is the mesh.
Such a graph is also referred to as grid or lattice. The 2-mesh is denoted M (m, n) and
is defined as the Cartesian product M (m, n) = Pm Pn . Similarly, the 3-mesh is defined
as M (k, m, n) = Pk Pm Pn . In general, for a sequence a1 , a2 , . . . , an of n > 0 positive
integers, the n-mesh is given by
M (a1 , a2 , . . . , an ) = Pa1 Pa2 Pan
where the 1-mesh is simply the path graph M (k) = Pk for some positive integer k.
Figure 1.28(a) illustrates the 2-mesh M (3, 4) = P3 P4 , while the 3-mesh M (3, 2, 3) =
P3 P2 P3 is presented in Figure 1.28(b).
36
(a) M (3, 4)
(b) M (3, 2, 3)
Figure 1.28: The 2-mesh M (3, 4) and the 3-mesh M (3, 2, 3).
1.5.5
Graph minors
A graph H is called a minor of a graph G if H is isomorphic to a graph obtained by a

sequence of edge contractions on a subgraph of G. The order in which a sequence of such
contractions is performed on G does not affect the resulting graph H. A graph minor is
not in general a subgraph. However, if G1 is a minor of G2 and G2 is a minor of G3 , then
G1 is a minor of G3 . Therefore, the relation being a minor of is a partial ordering on
the set of graphs. For example, the graph in Figure 1.25(c) is a minor of the graph in
Figure 1.25(a).
The following non-intuitive fact about graph minors was proven by Neil Robertson
and Paul Seymour in a series of 20 papers spanning 1983 to 2004. This result is known
by various names including the Robertson-Seymour theorem, the graph minor theorem,
or Wagners conjecture (named after Klaus Wagner).
Theorem 1.29. Robertson & Seymour 19832004. If an infinite list G1 , G2 , . . .
of finite graphs is given, then there always exist two indices i < j such that Gi is a minor
of Gj .
Many classes of graphs can be characterized by forbidden minors: a graph belongs
to the class if and only if it does not have a minor from a certain specified list. We shall
see examples of this in Chapter 7.
1.6
Common applications
(a) 2,4,4-trimethylheptane
(b) naphthalene
Figure 1.29: Two molecular graphs.

Graph theory, and especially undirected graphs, is used in chemistry to study the structure of molecules. The graph theoretical representation of the structure of a molecule
1.6. Common applications
37
is called a molecular graph; two such examples are illustrated in Figure 1.29. Below we
list a few common problems arising in applications of graph theory. See Foulds [77] and
Walther [187] for surveys of applications of graph theory in science, engineering, social
sciences, economics, and operation research.
If the edge weights are all nonnegative, find a cheapest closed path which contains
all the vertices. This is related to the famous traveling salesman problem and is
further discussed in Chapters 2 and 6.
Find a walk that visits each vertex, but contains as few edges as possible and
contains no cycles. This type of problem is related to spanning trees and is discussed
in further details in Chapter 3.
Determine which vertices are more central than others. This is connected with
various applications to social network analysis and is covered in more details in
Chapters 5 and 10. An example of a social network is shown in Figure 1.30, which
illustrates the marriage ties among Renaissance Florentine families [29]. Note that
one family has been removed because its inclusion would create a disconnected
graph.
Pazzi
Ginori
Salviati
Albizzi
Medici
Acciaiuol
Lambertes
Barbadori
Ridolfi
Strozzi
Castellan
Bischeri
Peruzzi
Tornabuon
Guadagni
Figure 1.30: Marriage ties among Renaissance Florentine families.

A planar graph is a graph that can be drawn on the plane in such a way that its
edges intersect only at their endpoints. Can a graph be drawn entirely in the plane,
with no crossing edges? In other words, is a given graph planar? This problem is
important for designing computer chips and wiring diagrams. Further discussion
is contained in Chapter 7.
Can you label or color all the vertices of a graph in such a way that no adjacent
vertices have the same color? If so, this is called a vertex coloring. Can you label
or color all the edges of a graph in such a way that no incident edges have the same
color? If so, this is called an edge coloring. Figure 1.31(a) shows a vertex coloring
of the wheel graph W4 using two colors; Figure 1.31(b) shows a vertex coloring
of the Petersen graph using three colors. Graph coloring has several remarkable
applications, one of which is to scheduling of jobs relying on a shared resource.
This is discussed further in Chapter 8.
38
(a)
(b)
Figure 1.31: Vertex coloring with two and three colors.

In some fields, such as operations research, a directed graph with nonnegative edge
weights is called a network , the vertices are called nodes, the edges are called arcs,
and the weight on an edge is called its capacity. A network flow must satisfy
the restriction that the amount of flow into a node equals the amount of flow out
of it, except when it is a source node, which has more outgoing flow, or a sink
node, which has more incoming flow. The flow along an edge must not exceed the
capacity. What is the maximum flow on a network and how to you find it? This
problem, which has many industrial applications, is discussed in Chapter 9.
1.7
Application: finite automata
In theoretical computer science, automata are used as idealized mathematical models

of computation. The studies of computability (i.e. what can be computed) and complexity (i.e. the time and space requirements of a computation) are based on automata
theory to provide precise mathematical models of computers. For an intuitive appreciation of automata, consider a vending machine that dispenses food or beverages. We
insert a fixed amount of money into the vending machine and make our choice of food
or beverage by pressing buttons that correspond to our choice. If the amount of money
inserted is sufficient to cover the cost of our choice of food or beverage, the machine
dispenses the item of our choice. Otherwise we need to insert more money until the
required amount is reached and then make our selection again. Embodied in the above
vending machine example are notions of input (money), machine states (has a selection
been made? has sufficient money been inserted?), state transition (move from money
insertion state to food/beverage selection state), and output (dispense item of choice).
In the above vending machine example, we should note that the vending machine
only accepts a finite number of objects as legitimate input. The vending machine can
accept dollar bills and coins of a fixed variety of denominations and belonging to a specific
locale, e.g. Australia. Thus we say that the vending machine has finite input and the
automaton that models the vending machine is referred to as a finite automaton having
a finite alphabet.
1.7. Application: finite automata
39
20
50
0
20
50
40
70
20
60
90
40
50
70 $1
80 $1
60
70
90 $1
80 $1 $1
90 $1 $1
$1 $1 $1
Table 1.1: Transition table of a simple vending machine.
1.7.1
Automaton and language
Before presenting a precise definition of finite automata, we take a detour to describe

notations associated with valid input to finite automata. Let be a nonempty finite
alphabet. By we mean the set of all finite strings over . Each element of is a
string or word of finite length whose components are elements of . That is, if w
then w = w1 w2 wn for some integer n 0 and each wi . It follows that .
We also consider the empty string as a valid string over . The string is sometimes
called the null string.
Definition 1.30. Finite automata. Let Q and be nonempty finite sets. A finite
automaton is a 5-tuple A = (Q, , , q0 , F ) where
1. Q is a finite set of states.
2. is a finite set of input alphabet.
3. : Q Q is the transition function.
4. q0 Q is the start or initial state.
5. F Q is the set of accepting or final states.

For each possible combination of state and input symbol, the transition function
specifies exactly one subsequent or next state. The finite automaton A must have at least
one initial state, but this lower bound does not necessarily apply to its set of final states.
It is possible that the set of final states be empty, in which case A has no accepting
states.
Example 1.31. Figure 1.32 illustrates a finite-automaton representation of a basic vending machine. The initial state is depicted as a circle with an arrow pointing to it, with
no other state at the tail of the arrow. The final state is shown as a circle with two
concentric rings. We can consider the visual representation in Figure 1.32, also called
a state diagram, as a multidigraph where each vertex is a state and each directed edge
is a transition from one state to another. The state diagram can also be represented in
tabular form as shown in Table 1.1.
Let q1 , q2 Q. The finite-state automaton A is said to be a deterministic finite-state
automaton (DFA) if for all (q, a) Q , the mappings (q, a) 7 q1 and (q, a) 7 q2
imply that q1 = q2 . Furthermore, for each state q Q and each input symbol a , we
have (q, a) 7 q 0 for some q 0 Q. In other words |(q, a)| = 1.
40

20
20
20
40
60
20
20
50
50
80
20
70
20
20
50
90
50
20
50
50
50
50
$1
50
20, 50
Figure 1.32: State diagram of a simple vending machine.

Definition 1.32. Nondeterministic finite-state automata. A nondeterministic
finite-state automaton (NFA) is a 5-tuple A = (Q, , , Q0 , F ) where
1. Q is a finite set of states.
2. is a finite set of input alphabet.
3. is a transition function defined by : Q 2Q , where 2Q is the power set
of Q.
4. Q0 Q is a set of initial states.
5. F Q is a set of accepting or final states.
Intuitively, A is said to be an NFA if there exist some (q, a) Q and q1 , q2 Q
such that the transitions (q, a) 7 q1 and (q, a) 7 q2 imply q1 6= q2 . That is, corresponding to each state/input pair is a multitude of subsequent states. Note the contrast to
DFA, where it is required that each state/input pair has at most one subsequent state.
Example 1.33. Let A = (Q, , , q0 , F ) be defined by Q = {1, 2}, = {a, b}, q0 = 1,
F = {2} and the transition function given by
(1, a) = 1,
(1, b) = 2,
(2, a) = 2,
(2, b) = 2.
Figure 1.33 shows a digraph representation of A. It is easily verifiable by definition that

A is indeed a DFA.
Figure 1.33: A deterministic finite-state automaton.
41
Example 1.34. Let A = (Q, , , Q0 , F ) be defined by Q = {1, 2}, = {a, b}, Q0 = {1},
F = {2}, and the transition function given by
(1, a) = 1,
(1, a) = 2,
(2, a) = 2,
(2, b) = 2.
Figure 1.34 shows a digraph representation of A. Note that (1, a) = 1 and (1, a) = 2.
It follows by definition that A is an NFA.
Figure 1.34: A nondeterministic finite-state automaton.

We can inductively define a transition function of a DFA A = (Q, , , q0 , F ) operating on finite strings over . That is,
: Q Q.
(1.9)
) = q.
Let q Q and let s = s1 s2 sn . In the case of the empty string, define (q,
s1 ) = (q, s1 ). For 1 < i n, define
When i = 1, we have (q,

(q, s1 s2 si ) = (q, s1 s2 si1 ), si .
s). Where (q0 , s) F , we say that the

For convenience, we write (q, s) instead of (q,
string s is accepted by A. Any subset of is said to be a language over . The language
L of A is the set of all finite strings accepted by A, i.e.
L(A) = {s | (q0 , s) F } .
The special language L(A) is also referred to as a regular language. Referring back to
example 1.33, any string accepted by A has zero or more a, followed by exactly one b,
and finally zero or more occurrences of a or b. We can describe this language using the
regular expression a b(a|b) .
For NFAs, we can similarly define a transition function operating on finite strings.
Each input is a string over and the transition function returns a subset of Q. Formally,
our transition function for NFAs operating on finite strings is the map
: Q 2Q .
Let q Q and let w = xa, where x and a . The input symbol a can be
interpreted as being the very last symbol in the string w. Then x is interpreted as being
the substring of w excluding the symbol a. In the case of the empty string, we have
) = {q}. For the inductive case, assume that (q,
x) = {p1 , p2 , . . . , pk } where each
(q,
pi Q. Then (q, w) is defined by

w) = (q,
x), a
(q,
= ({p1 , p2 , . . . , pk }, a)
=
k
[
(pi , a).
i=1
It may happen that for some state pi , there are no transitions from pi with input a. We
cater for this possibility by writing (pi , a) = .
42
1.7.2
Simulating NFAs using DFAs
Any NFA can be simulated by a DFA. One way of accomplishing this is to allow the DFA
to keep track of all the states that the NFA can be in after reading an input symbol.
The formal proof depends on this construction of an equivalent DFA and then showing
that the language of the DFA is the same as that of the NFA.
Theorem 1.35. Determinize an NFA. If A is a nondeterministic finite-state automaton, then there exists a deterministic finite-state automaton A0 such that L(A) =
L(A0 ).
Proof. Let the NFA A be defined by A = (Q, , , Q0 , F ) and define a DFA A0 =

(Q0 , , 0 , q00 , F 0 ) as follows. The state space of A0 is the power set of Q, i.e. Q0 = 2Q .
The accepting state space F 0 of A0 is a subset of Q0 , where each f F 0 is a set containing
at least an accepting state of A. In symbols, we write F 0 Q0 where
F 0 = {q Q0 | p F for some p q} .
Denote each element q Q0 by q = [q1 , q2 , . . . , qi ] where q1 , q2 , . . . , qi Q. Thus the

initial state of A0 is q00 = [Q0 ]. Now define the transition function 0 by
0 ([q1 , q2 , . . . , qi ], s) = [p1 , p2 , . . . , pj ]
({q1 , q2 , . . . , qi }, s) =
i
[
(qk , s) = {p1 , p2 , . . . , pj }.
(1.10)
k=1
For any input string w, we now show by induction on the length of w that
0 (q00 , w) = [q1 , q2 , . . . , qi ]
(Q0 , w) = {q1 , q2 , . . . , qi }.
(1.11)
For the basis step, let |w| = 0 so that w = . Then it is clear that
0 (q00 , w) = 0 (q00 , ) = [q00 ]
(Q0 , w) = (Q0 , ) = Q0 .
Next, assume for induction that statement (1.11) holds for all strings of length less than
or equal to m > 0. Let w be a string of length m and let a so that |wa| = m + 1.
Then 0 (q00 , wa) = 0 0 (q00 , w), a . By our inductive hypothesis, we have
0 (q00 , w) = [p1 , p2 , . . . , pj ]
(Q0 , w) = {p1 , p2 , . . . , pj }
and applying (1.11) we get

0 ([p1 , p2 , . . . , pj ], a) = [r1 , r2 , . . . , rk ]
({p1 , p2 , . . . , pj }, a) = {r1 , r2 , . . . , rk }.
Hence
0 (q00 , wa) = [r1 , r2 , . . . , rk ]
(Q0 , wa) = {r1 , r2 , . . . , rk }
which establishes that statement (1.11) holds for all finite strings over . Finally,
0 (q00 , w) F 0 if and only if there is some p (Q0 , w) such that p F . Therefore
L(A) = L(A0 ).
43
Theorem 1.35 tells us that any NFA corresponds to some DFA that accepts the
same language. For this reason, the theorem is said to provide us with a procedure
for determinizing NFAs. The actual procedure itself is contained in the proof of the
theorem, although it must be noted that the procedure is inefficient since it potentially
yields transitions from states that are unreachable from the initial state. If q Q0 is
a state of A0 that is unreachable from q00 , then there are no input strings w such that
0 (q00 , w) = q. Such unreachable states are redundant insofar as they do not affect L(A0 ).
Another inefficiency of the procedure in the proof of Theorem 1.35 is the problem of
state space explosion. As Q0 = 2Q is the power set of Q, the resulting DFA can potentially
have exponentially more states than the NFA it is simulating. In the worse case, each
element of Q0 is a state of the resulting DFA that is reachable from q00 = [Q0 ]. The
best-case scenario is when each state of the DFA is a singleton, hence the DFA has the
same number of states as its corresponding NFA. However, according to the procedure
in the proof of Theorem 1.35, we generate all the possible 2n states of the DFA, where
n = |Q|. After considering all the transitions whose starting states are singletons, we
then consider all transitions starting from each of the remaining 2n n elements in Q0 .
In the best-case, none of those remaining 2n n states are reachable from q00 , hence it is
redundant to generate transitions starting at each of those 2n n states. Example 1.36
concretizes our discussion.
Example 1.36. Use the procedure in Theorem 1.35 to determinize the NFA in Figure 1.35.
a
b
a
c
3
Figure 1.35: An NFA with 3 states and 3 input symbols.

Solution. The NFA A = (Q, , , q0 , F ) in Figure 1.35 has the states Q = {1, 2, 3}, the
initial state q0 = 1, the final state set F = {3}, and the input alphabet = {a, b, c}.
Its transitions are contained in Table 1.2. To determinize A, we construct a DFA A0 =
a
1 {1, 2}
{2}
c
{3}
{3}
Table 1.2: Transition table for the NFA in Figure 1.35.

(Q0 , , 0 , q00 , F 0 ). As Q0 is the power set of Q, then all the possible states of A0 are
contained in Q0 = {, [1], [2], [3], [1, 2], [1, 3], [2, 3], [1, 2, 3]}. The alphabet of A0 is the
same as the alphabet of A, namely . The initial state of A0 is q00 = [q0 ] = [1]. All
the possible accepting states of A0 are contained in F 0 = {[3], [1, 3], [2, 3], [1, 2, 3]}. Next,
44
we apply (1.10) to construct all the possible transitions of A0 . These transitions are
contained in Table 1.3. Using those transitions, we obtain the digraph representation in
Figure 1.36, from which it is clear that the states [1], [2], [3], and [1, 2] are the only states
0
[1]
a
[1, 2]
[2]
[1, 2]
[1, 2]
[2]
[3]
[1, 3]
[1, 2]
[3]
[2, 3]
[2]
[3]
[2]
[3]
[3]
[1, 2, 3] [1, 2]
c
[3]
[2]
[3]
Table 1.3: Transition table of a deterministic version of the NFA in Figure 1.35.
reachable from the initial state q00 = [1]. The remaining states [1, 3], [2, 3], and [1, 2, 3]
are not reachable from q00 = [1]. In other words, starting at q00 = [1] there are no input
strings that would result in a transition to any of [1, 3], [2, 3], and [1, 2, 3]. Therefore these
states, and the transitions starting from them, can be deleted from Figure 1.36 without
affecting the language of A0 . Figure 1.37 shows an equivalent DFA with redundant states
removed.
a
a
c
1, 2
3
c
1, 2, 3
a
b
b
2, 3
1, 3
Figure 1.36: A DFA accepting the same language as the NFA in Figure 1.35.
1.8. Problems
45
a
c
a
1, 2
3
c
Figure 1.37: A DFA equivalent to that in Figure 1.36, with redundant states removed.
1.8
Problems
A problem left to itself dries up or goes rotten. But fertilize a problem with a solution
youll hatch out dozens.
N. F. Simpson, A Resounding Tinkle, 1958
1.1. For each graph in Figure 1.6, do the following:

(a) Construct the graph using Sage.
(b) Find its adjacency matrix.
(c) Find its node and edge sets.
(d) How many nodes and edges are in the graph?
(e) If applicable, find all of each nodes in-coming and out-going edges. Hence
find the nodes indegree and outdegree.
Alice
Bob
Carol
Figure 1.38: Graph representation of a social network.

1.2. In the friendship network of Figure 1.38, Carol is a mutual friend of Alice and Bob.
How many possible ways are there to remove exactly one edge such that, in the
resulting network, Carol is no longer a mutual friend of Alice and Bob?
1.3. The routing network of German cities in Figure 1.39 shows that each pair of distinct
cities are connected by a flight path. The weight of each edge is the flight distance
in kilometers between the two corresponding cities. In particular, there is a flight
path connecting Karlsruhe and Stuttgart. What is the shortest route between
Karlsruhe and Stuttgart? Suppose we can remove at least one edge from this
network. How many possible ways are there to remove edges such that, in the
resulting network, Karlsruhe is no longer connected to Stuttgart via a flight path?
1.4. Let D = (V, E) be a digraph of size q. Show that
X
X
id(v) =
od(v) = q.
vV
vV
46
Karlsruhe
197
54
Augsburg
Mannheim
57
72
Munich
383
Kassel
149
97
Nuremberg
157
Stuttgart
Frankfurt
145
90
W
urzburg
154
Erfurt
Figure 1.39: Graph representation of a routing network.
1.8. Problems
47
1.5. If G is a simple graph of order n > 0, show that deg(v) < n for all v V (G).
1.6. Let G be a graph of order n and size m. Then G is called an overfull graph if
m > (G) bn/2c. If m = (G) bn/2c + 1, then G is said to be just overfull.
It can be shown that overfull graphs have odd order. Equivalently, let G be of
odd order. We can define G to be overfull if m > (G) (n 1)/2, and G is just
overfull if m = (G) (n 1)/2 + 1. Find an overfull graph and a graph that is
just overfull. Some basic results on overfull graphs are presented in Chetwynd and
Hilton [49].
1.7. Fix a positive integer n and denote by (n) the number of simple graphs on n
vertices. Show that
n
(n) = 2( 2 ) = 2n(n1)/2 .
1.8. Let G be an undirected graph whose unoriented incidence matrix is Mu and whose
oriented incidence matrix is Mo .
(a) Show that the sum of the entries in any row of Mu is the degree of the
corresponding vertex.
(b) Show that the sum of the entries in any column of Mu is equal to 2.
(c) If G has no self-loops, show that each column of Mo sums to zero.
1.9. Let G be a loopless digraph and let M be its incidence matrix.
(a) If r is a row of M , show that the number of occurrences of 1 in r counts
the outdegree of the vertex corresponding to r. Show that the number of
occurrences of 1 in r counts the indegree of the vertex corresponding to r.
(b) Show that each column of M sums to 0.
1.10. Let G be a digraph and let M be its incidence matrix. For any row r of M , let m
be the frequency of 1 in r, let p be the frequency of 1 in r, and let t be twice the
frequency of 2 in r. If v is the vertex corresponding to r, show that the degree of
v is deg(v) = m + p + t.
1.11. Let G be an undirected graph without self-loops and let M and its oriented incidence matrix. Show that the Laplacian matrix L of G satisfies L = M M T ,
where M T is the transpose of M .
1.12. Let J1 denote the incidence matrix of G1 and let J2 denote the incidence matrix of
G2 . Find matrix theoretic criteria on J1 and J2 which hold if and only if G1
= G2 .
In other words, find the analog of Theorem 1.22 for incidence matrices.
1.13. Show that the complement of an edgeless graph is a complete graph.
1.14. Let GH be the Cartesian product of two graphs G and H. Show that |E(GH)| =
|V (G)| |E(H)| + |E(G)| |V (H)|.
1.15. In 1751, Leonhard Euler posed a problem to Christian Goldbach, a problem that
now bears the name Eulers polygon division problem. Given a plane convex
polygon having n sides, how many ways are there to divide the polygon into triangles using only diagonals? For our purposes, we consider only regular polygons
48
Figure 1.40: Eulers polygon division problem for the hexagon.

having n sides for n 3 and any two diagonals must not cross each other. For
example, the triangle is a regular 3-gon, the square a regular 4-gon, the pentagon
a regular 5-gon, etc. In the case of the hexagon considered as the cycle graph C6 ,
there are 14 ways to divide it into triangles, as shown in Figure 1.40, resulting in
14 graphs. However, of those 14 graphs only 3 are nonisomorphic to each other.
(a) What is the number of ways to divide a pentagon into triangles using only
diagonals? List all such divisions. If each of the resulting so divided pentagons
is considered a graph, how many of those graphs are nonisomorphic to each
other?
(b) Repeat the above exercise for the heptagon.
(c) Let En be the number of ways to divide an n-gon into triangles using only
diagonals. For n 1, the Catalan numbers Cn are defined as

2n
1
.
Cn =
n+1 n
Dorrie [62, pp.2127] showed that En is related to the Catalan numbers via
the equation En = Cn1 . Show that

1
2n + 2
Cn =
.
4n + 2 n + 1
For k 2, show that the Catalan numbers satisfy the recurrence relation
Ck =
4k 2
Ck1 .
k+1
1.16. A graph is said to be planar if it can be drawn on the plane in such a way that
no two edges cross each other. For example, the complete graph Kn is planar for
n = 1, 2, 3, 4, but K5 is not planar (see Figure 1.12). Draw a planar version of K4 as
1.8. Problems
49
presented in Figure 1.12(b). Is the graph in Figure 1.8 planar? For n = 1, 2, . . . , 5,

enumerate all simple nonisomorphic graphs on n vertices that are planar; only work
with undirected graphs.
1.17. If n 3, show that the join of Cn and K1 is the wheel graph Wn+1 . In other words,
show that Cn + K1 = Wn+1 .
1.18. A common technique for generating random numbers is the linear congruential
method, a generalization of the Lehmer generator [131] introduced in 1949. First,
we choose four integers:
m,
modulus,
0<m
a,
multiplier,
c,
increment,
0a<m
X0 ,
seed,
0c<m
0 X0 < m
where the value X0 is also referred to as the starting value. Then iterate the
relation
Xn+1 = (aXn + c) mod m,
n0
and halt when the relation produces the seed X0 or when it produces an integer
Xk such that Xk = Xi for some 0 i < k. The resulting sequence
S = (X0 , X1 , . . . , Xn )
is called a linear congruential sequence. Define a graph theoretic representation
of S as follows: let the vertex set be V = {X0 , X1 , . . . , Xn } and let the edge set
be E = {Xi Xi+1 | 0 i < n}. The resulting graph G = (V, E) is called the
linear congruential graph of the linear congruential sequence S. See chapter 3 of
Knuth [119] for other techniques for generating random numbers.
(a) Compute the linear congruential sequences Si with the following parameters:
(i)
(ii)
(iii)
(iv)
S1 :
S2 :
S3 :
S4 :
m = 10,
m = 10,
m = 10,
m = 10,
a = c = X0 = 7
a = 5, c = 7, X0 = 0
a = 3, c = 7, X0 = 2
a = 2, c = 5, X0 = 3
(b) Let Gi be the linear congruential graph of Si . Draw each of the graphs Gi .
Draw the graph resulting from the union
[
Gi .
i
(c) Let m, a, c, and X0 be the parameters of a linear congruential sequence where

(i) c is relatively prime to m;
(ii) b = a 1 is a multiple of p for each prime p that divides m; and
(iii) 4 divides b if 4 divides m.
Show that the corresponding linear congruential graph is the wheel graph Wm
on m vertices.
50
1.19. We want to generate a random bipartite graph whose first and second partitions
have n1 and n2 vertices, respectively. Describe and present pseudocode to generate
the required random bipartite graph. What is the worst-case runtime of your
algorithm? Modify your algorithm to account for a third parameter m that specifies
the number of edges in the resulting bipartite graph.
1.20. Describe and present pseudocode to generate a random regular graph. What is the
worst-case runtime of your algorithm?
1.21. The Cantor-Schroder-Bernstein theorem states that if A, B are sets and we have
an injection f : A B and an injection g : B A, then there is a bijection
between A and B, thus proving that A and B have the same cardinality. Here
we use bipartite graphs and other graph theoretic concepts to prove the CantorSchroder-Bernstein theorem. The full proof can be found in Yegnanarayanan [199].
(a) Is it possible for A and B to be bipartitions of V and yet satisfy A B 6= ?
(b) Now assume that A B = and define a bipartite graph G = (V, E) with A
and B being the two partitions of V , where for any x A and y B we have
xy E if and only if either f (x) = y or g(y) = x. Show that deg(v) = 1 or
deg(v) = 2 for each v V .
(c) Let C be a component of G and let A0 A and B 0 B contain all vertices
in the component C. Show that |A0 | = |B 0 |.
1.22. Fermats little theorem states that if p is prime and a is an integer not divisible
by p, then p divides ap a. Here we cast the problem within the context of graph
theory and prove it using graph theoretic concepts. The full proof can be found in
Heinrich and Horak [96] and Yegnanarayanan [199].
(a) Let G = (V, E) be a graph with V being the set of all sequences (a1 , a2 , . . . , ap )
of integers 1 ai a and aj 6= ak for some j 6= k. Show that G has ap a
vertices.
(b) Define the edge set of G as follows. If u, v V such that u = (u1 , u2 , . . . , up )
and v = (up , u1 , . . . , up1 ), then uv E. Show that each component of G is a
cycle of length p.
(c) Show that G has (ap a)/p components.
1.23. For the finite automaton in Figure 1.32, identify the following:
(a) The states set Q.
(b) The alphabet set .
(c) The transition function : Q Q.
(d) The initial state q0 Q.
(e) The set of final states F Q.
1.24. The cycle graph Cn is a 2-regular graph. If 2 < r < n/2, unlike the cycle graph
there are various realizations of an r-regular graph; see Figure 1.41 for the case of
r = 3 and n = 10. The k-circulant graph on n vertices can be considered as an
intermediate graph between Cn and a k-regular graph. Let k and n be positive
1.8. Problems
51
3
1
9
7
(a)
3
1
9
7
9
7
(b)
(c)
Figure 1.41: Various 3-regular graphs on 10 vertices.
(a) k = 4
(b) k = 6
(c) k = 8
Figure 1.42: Various k-circulant graphs for k = 4, 6, 8.

integers satisfying k < n/2 with k being even. Suppose G = (V, E) is a simple
undirected graph with vertex set V = {0, 1, . . . , n 1}. Define the edge set of G
as follows. Each i V is incident with each of i + j mod n and i j mod n for
j {1, 2, . . . , k/2}. With the latter edge set, G is said to be a k-circulant graph, a
type of graphs used in constructing small-world networks (see section 10.4). Refer
to Figure 1.42 for examples of k-circulant graphs.
(a) Describe and provide pseudocode of an algorithm to construct a k-circulant
graph on n vertices.
(b) Show that the cycle graph Cn is 2-circulant.
(c) Show that the sum of all degrees of a k-circulant graph on n vertices is nk.
(d) Show that a k-circulant graph is k-regular.
(e) Let C be the collection of all k-regular graphs on n vertices. If each k-regular
graph from C is equally likely to be chosen, what is the probability that a
k-circulant graph be chosen from C?
Chapter 2
Graph Algorithms
Randall Munroe, xkcd, http://xkcd.com/518/
Graph algorithms have many applications. Suppose you are a salesman with a product
you would like to sell in several cities. To determine the cheapest travel route from cityto-city, you must effectively search a graph having weighted edges for the cheapest
route visiting each city once. Each vertex denotes a city you must visit and each edge
has a weight indicating either the distance from one city to another or the cost to travel
from one city to another.
Shortest path algorithms are some of the most important algorithms in algorithmic
graph theory. In this chapter, we first examine several common graph traversal algorithms and some basic data structures underlying these algorithms. A data structure is
a combination of methods for structuring a collection of data (e.g. vertices and edges)
and protocols for accessing the data. We then consider a number of common shortest
path algorithms, which rely in one way or another on graph traversal techniques and
basic data structures for organizing and managing vertices and edges.
52
2.1. Representing graphs in a computer
2.1
53
Representing graphs in a computer

To err is human but to really foul things up requires a computer.
Anonymous, Farmers Almanac for 1978, Capsules of Wisdom
In section 1.3, we discussed how to use matrices for representing graphs and digraphs. If
A = [aij ] is an mn matrix, the adjacency matrix representation of a graph would require
representing all the mn entries of A. Alternative graph representations exist that are
much more efficient than representing all entries of a matrix. The graph representation
used can be influenced by the size of a graph or the purpose of the representation. Section 2.1.1 discusses the adjacency list representation that can result in less storage space
requirement than the adjacency matrix representation. The graph6 format discussed in
section 2.1.3 provides a compact means of storing graphs for archival purposes.
2.1.1
Adjacency lists
A list is a sequence of objects. Unlike sets, a list may contain multiple copies of the same
object. Each object in a list is referred to as an element of the list. A list L of n 0
elements is written as L = [a1 , a2 , . . . , an ], where the i-th element ai can be indexed
as L[i]. In case n = 0, the list L = [ ] is referred to as the empty list. Two lists are
equivalent if they both contain the same elements at exactly the same positions.
Define the adjacency lists of a graph as follows. Let G be a graph with vertex set
V = {v1 , v2 , . . . , vn }. Assign to each vertex vi a list Li containing all the vertices that
are adjacent to vi . The list Li associated with vi is referred to as the adjacency list of
vi . Then Li = [ ] if and only if vi is an isolated vertex. We say that Li is the adjacency
list of vi because any permutation of the elements of Li results in a list that contains
the same vertices adjacent to vi . We are mainly concerned with the neighbors of vi , but
disregard the position where each neighbor is located in Li . If each adjacency list Li
contains si elements where 0 si n, we say that Li has length
si . The adjacency
P
list representation of the graph G requires that we represent i si = 2 |E(G)| n2
elements in a computers memory, since each edge appears twice in the adjacency list
representation. An adjacency list is explicit about which vertices are adjacent to a vertex
and implicit about which vertices are not adjacent to that same vertex. Without knowing
the graph G, given the adjacency lists L1 , L2 , . . . , Ln , we can reconstruct G. For example,
Figure 2.1 shows a graph and its adjacency list representation.
4
3
7
L1 = [2, 8]
L5 = [6, 8]
L2 = [1, 6]
L6 = [2, 5, 8]
L3 = [4]
L7 = [ ]
L4 = [3]
L8 = [1, 5, 6]
Figure 2.1: A graph and its adjacency lists.

Example 2.1. The Kneser graph with parameters (n, k), also known as the (n, k)-Kneser
graph, is the graph whose vertices are all the k-subsets of {1, 2, . . . , n}. Furthermore, two
54
Chapter 2. Graph Algorithms
vertices are adjacent if their corresponding sets are disjoint. Draw the (5, 2)-Kneser
graph and find its order and adjacency lists. In general, if n and k are positive, what is
the order of the (n, k)-Kneser graph?
Solution. The (5, 2)-Kneser graph is the graph whose vertices are the 2-subsets
{1, 2}, {1, 3}, {1, 4}, {1, 5}, {2, 3}, {2, 4}, {2, 5}, {3, 4}, {3, 5}, {4, 5}
of {1, 2, 3, 4, 5}. That is, each vertex of the (5, 2)-Kneser graph
a 2-combination of the
is54
5
set {1, 2, 3, 4, 5} and therefore the graph itself has order 2 = 2! = 10. The edges of
this graph are
({1, 3}, {2, 4}), ({2, 4}, {1, 5}), ({2, 4}, {3, 5}), ({1, 3}, {4, 5}), ({1, 3}, {2, 5})
({3, 5}, {1, 4}), ({3, 5}, {1, 2}), ({1, 4}, {2, 3}), ({1, 4}, {2, 5}), ({4, 5}, {2, 3})
({4, 5}, {1, 2}), ({1, 5}, {2, 3}), ({1, 5}, {3, 4}), ({3, 4}, {1, 2}), ({3, 4}, {2, 5})
from which we obtain the following adjacency lists:
L{1,2} = [{3, 4}, {3, 5}, {4, 5}],
L{1,3} = [{2, 4}, {2, 5}, {4, 5}],
L{1,4} = [{2, 3}, {3, 5}, {2, 5}],
L{1,5} = [{2, 4}, {3, 4}, {2, 3}],
L{2,3} = [{1, 5}, {1, 4}, {4, 5}],
L{2,4} = [{1, 3}, {1, 5}, {3, 5}],
L{2,5} = [{1, 3}, {3, 4}, {1, 4}],
L{3,4} = [{1, 2}, {1, 5}, {2, 5}],
L{3,5} = [{2, 4}, {1, 2}, {1, 4}],
L{4,5} = [{1, 3}, {1, 2}, {2, 3}].
The (5, 2)-Kneser graph itself is shown in Figure 2.2. Using Sage, we have
sage : K = graphs . KneserGraph (5 , 2); K
Kneser graph with parameters 5 ,2: Graph on 10 vertices
sage : for v in K . vertices ():
...
print (v , K . neighbors ( v ))
...
({4 , 5} , [{1 , 3} , {1 , 2} , {2 , 3}])
({1 , 3} , [{2 , 4} , {2 , 5} , {4 , 5}])
({2 , 5} , [{1 , 3} , {3 , 4} , {1 , 4}])
({2 , 3} , [{1 , 5} , {1 , 4} , {4 , 5}])
({3 , 4} , [{1 , 2} , {1 , 5} , {2 , 5}])
({3 , 5} , [{2 , 4} , {1 , 2} , {1 , 4}])
({1 , 4} , [{2 , 3} , {3 , 5} , {2 , 5}])
({1 , 5} , [{2 , 4} , {3 , 4} , {2 , 3}])
({1 , 2} , [{3 , 4} , {3 , 5} , {4 , 5}])
({2 , 4} , [{1 , 3} , {1 , 5} , {3 , 5}])
If n and k are positive integers, then the (n, k)-Kneser graph has

n
n(n 1) (n k + 1)
=
k!
k
vertices.
We can categorize a graph G = (V, E) as dense or sparse
based upon its size. A dense
2
2
graph has size |E| that is close to |V | , i.e. |E| = |V | , in which case it is feasible to
2
represent G as an
adjacency matrix. The size of a sparse graph is much less than |V | ,
i.e. |E| = |V | , which renders the adjacency matrix representation as unsuitable. For
a sparse graph, an adjacency list representation can require less storage space than an
adjacency matrix representation of the same graph.
55
{3, 4}
{1, 2}
{1, 5}
{2, 5}
{2, 3}
{3, 5}
{4, 5}
{1, 4}
{2, 4}
{1, 3}
Figure 2.2: The (5, 2)-Kneser graph.
2.1.2
Edge lists
Lists can also be used to store the edges of a graph. To create an edge list L for a graph
G, if uv is an edge of G then we let uv or the ordered pair (u, v) be an element of L. In
general, let
v0 v1 , v2 v3 , . . . , vk vk+1
be all the edges of G, where k is even. Then the edge list of G is given by
L = [v0 v1 , v2 v3 , . . . , vk vk+1 ].
In some cases, it is desirable to have the edges of G be in contiguous list representation.
If the edge list L of G is as given above, the contiguous edge list representation of the
edges of G is
[v0 , v1 , v2 , v3 , . . . , vk , vk+1 ].
That is, if 0 i k is even then vi vi+1 is an edge of G.
2.1.3
The graph6 format
The graph formats graph6 and sparse6 were developed by Brendan McKay [139] at
The Australian National University as a compact way to represent graphs. These two
formats use bit vectors and printable characters of the American Standard Code for
Information Interchange (ASCII) encoding scheme. The 64 printable ASCII characters
used in graph6 and sparse6 are those ASCII characters with decimal codes from 63 to
126, inclusive, as shown in Table 2.1. This section shall only cover the graph6 format.
For full specification on both of the graph6 and sparse6 formats, see McKay [139].
Bit vectors
Before discussing how graph6 and sparse6 represent graphs using printable ASCII characters, we first present encoding schemes used by these two formats. A bit vector is, as
56
binary decimal
0111111
63
1000000
64
1000001
65
1000010
66
1000011
67
1000100
68
1000101
69
1000110
70
1000111
71
1001000
72
1001001
73
1001010
74
1001011
75
1001100
76
1001101
77
1001110
78
1001111
79
1010000
80
1010001
81
1010010
82
1010011
83
1010100
84
1010101
85
1010110
86
1010111
87
1011000
88
1011001
89
1011010
90
1011011
91
1011100
92
1011101
93
1011110
94
glyph
?
@
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
[
\
]
^
binary decimal
1011111
95
1100000
96
1100001
97
1100010
98
1100011
99
1100100
100
1100101
101
1100110
102
1100111
103
1101000
104
1101001
105
1101010
106
1101011
107
1101100
108
1101101
109
1101110
110
1101111
111
1110000
112
1110001
113
1110010
114
1110011
115
1110100
116
1110101
117
1110110
118
1110111
119
1111000
120
1111001
121
1111010
122
1111011
123
1111100
124
1111101
125
1111110
126
glyph
_
a
b
c
d
e
f
g
h
i
j
k
l
m
n
o
p
q
r
s
t
u
v
w
x
y
z
{
|
}
~
Table 2.1: ASCII printable characters used by graph6 and sparse6.
57
its name suggests, a vector whose elements are 1s and 0s. It can be represented as a list
of bits, e.g. E can be represented as the ASCII bit vector [1, 0, 0, 0, 1, 0, 1]. For brevity,
we write a bit vector in a compact form such as 1000101. The length of a bit vector
is its number of bits. The most significant bit of a bit vector v is the bit position with
the largest value among all the bit positions in v. Similarly, the least significant bit is
the bit position in v having the least value among all the bit positions in v. The least
significant bit of v is usually called the parity bit because when v is interpreted as an
integer the parity bit determines whether the integer is even or odd. Reading 1000101
from left to right, the first bit 1 is the most significant bit, followed by the second bit 0
which is the second most significant bit, and so on all the way down to the seventh bit
1 which is the least significant bit.
The order in which we process the bits of a bit vector
v = bn1 bn2 b0
(2.1)
is referred to as endianness. Processing v in big-endian order means that we first process

the most significant bit of v, followed by the second most significant bit, and so on all the
way down to the least significant bit of v. Thus, in big-endian order we read the bits bi of
v from left to right in increasing order of powers of 2. Table 2.2 illustrates the big-endian
interpretation of the ASCII binary representation of E. Little-endian order means that
we first process the least significant bit, followed by the second least significant bit, and
so on all the way up to the most significant bit. In little-endian order, the bits bi are read
from right to left in increasing order of powers of 2. Table 2.3 illustrates the little-endian
interpretation of the ASCII binary representation of E. In his novel Gullivers Travels
first published in 1726, Jonathan Swift used the terms big- and little-endian in satirizing
politicians who squabbled over whether to break an egg at the big end or the little end.
Danny Cohen [51, 52] first used the terms in 1980 as an April fools joke in the context
of computer architecture.
Suppose the bit vector (2.1) is read in big-endian order. To determine the integer
representation of v, multiply each bit value by its corresponding position value, then add
up all the results. Thus, if v is read in big-endian order, the integer representation of v
is obtained by evaluating the polynomial
p(x) =
n1
X
i=0
xi bi = xn1 bn1 + xn2 bn2 + + xb1 + b0 .
(2.2)
at x = 2. See problem 2.2 for discussion of an efficient method to compute the integer
representation of a bit vector.
position
bit value
position value
0
1
20
1
0
21
2
0
22
3
0
23
4
1
24
5
0
25
6
1
26
Table 2.2: Big-endian order of the ASCII binary code of E.

In graph6 and sparse6 formats, the length of a bit vector must be a multiple of 6.
Suppose v is a bit vector of length k such that 6 - k. To transform v into a bit vector
having length a multiple of 6, let r = k mod 6 be the remainder upon dividing k by 6,
and pad 6 r zeros to the right of v.
58

position
bit value
position value
0
1
26
1
0
25
2
0
24
3
0
23
4
1
22
5
0
21
6
1
20
Table 2.3: Little-endian order of the ASCII binary code of E.

Suppose v = b1 b2 bk is a bit vector of length k, where 6 | k. We split v into k/6
bit vectors vi , each of length 6. For 0 i k/6, the i-th bit vector is given by
vi = b6i5 b6i4 b6i3 b6i2 b6i1 b6i .
Consider each vi as the big-endian binary representation of a positive integer. Use (2.2)
to obtain the integer representation Ni of each vi . Then add 63 to each Ni to obtain Ni0
and store Ni0 in one byte of memory. That is, each Ni0 can be represented as a bit vector
of length 8. Thus the required number of bytes to store v is dk/6e. Let Bi be the byte
representation of Ni0 so that
R(v) = B1 B2 Bdk/6e
(2.3)
denotes the representation of v as a sequence of dk/6e bytes.
We now discuss how to encode an integer n in the range 0 n 236 1 using (2.3)
and denote such an encoding of n as N (n). Let v be the big-endian binary representation
of n. Then N (n) is given by
n + 63,
if 0 n 62,
N (n) = 126 R(v),

(2.4)
if 63 n 258047,
126 126 R(v), if 258048 n 236 1.

Note that n + 63 requires one byte of storage memory, while 126 R(v) and 126 126 R(v)
require 4 and 8 bytes, respectively.
The graph6 format
The graph6 format is used to represent simple, undirected graphs of order from 0 to
236 1, inclusive. Let G be a simple, undirected graph of order 0 n 236 1. If
n = 0, then G is represented in graph6 format as ?. Suppose n > 0. Let M = [aij ]
be the adjacency matrix of G. Consider the upper triangle of M , excluding the main
diagonal, and write that upper triangle as the bit vector
v = a0,1 a0,2 a1,2 a0,3 a1,3 a2,3 a0,i a1,i ai1,i a0,n a1,n an1,n
|
{z
}
|
{z
}
|{z} | {z } | {z }
c1
c2
c3
ci
cn
where ci denotes the entries a0,i a1,i ai1,i in column i of M . Then the graph6 representation of G is N (n)R(v), where R(v) and N (n) are as in (2.3) and (2.4), respectively.
That is, N (n) encodes the order of G and R(v) encodes the edges of G.
2.2
Graph searching
Errors, like straws, upon the surface flow;
He who would search for pearls must dive below.
John Dryden, All for Love, 1678
2.2. Graph searching
59
This section discusses two fundamental algorithms for graph traversal: breadth-first
search and depth-first search. The word search used in describing these two algorithms
is rather misleading. It would be more accurate to describe them as algorithms for
constructing trees using the adjacency information of a given graph. However, the names
breadth-first search and depth-first search are entrenched in literature on graph
theory and computer science. From hereon, we use these two names as given above,
bearing in mind their intended purposes.
2.2.1
Breadth-first search
Breadth-first search (BFS) is a strategy for running through the vertices of a graph. It
was presented by Moore [146] in 1959 within the context of traversing mazes. Lee [130]
independently discovered the same algorithm in 1961 in his work on routing wires on
circuit boards. In the physics literature, BFS is also known as a burning algorithm in
view of the analogy of a fire burning and spreading through an area, a piece of paper,
fabric, etc.
The basic BFS algorithm can be described as follows. Starting from a given vertex
v of a graph G, we first explore the neighborhood of v by visiting all vertices that are
adjacent to v. We then apply the same strategy to each of the neighbors of v. The
strategy of exploring the neighborhood of a vertex is applied to all vertices of G. The
result is a tree rooted at v and this tree is a subgraph of G. Algorithm 2.1 presents a
general template for the BFS strategy. The tree resulting from the BFS algorithm is
called a breadth-first search tree.
Algorithm 2.1: A general breadth-first search template.
Input: A directed or undirected graph G = (V, E) of order n > 0. A vertex s
from which to start the search. The vertices are numbered from 1 to
n = |V |, i.e. V = {1, 2, . . . , n}.
Output: A list D of distances of all vertices from s. A tree T rooted at s.
1
2
3
4
5
6
7
8
9
10
11
12
Q [s]
/* queue of nodes to visit */
D [, , . . . , ]
/* n copies of */
D[s] 0
T []
while length(Q) > 0 do
v dequeue(Q)
for each w adj(v) do
if D[w] = then
D[w] D[v] + 1
enqueue(Q, w)
append(T, vw)
return (D, T )
The breadth-first search algorithm makes use of a special type of list called a queue.
This is analogous to a queue of people waiting in line to be served. A person may enter
the queue by joining the rear of the queue. The person who is in the queue the longest
amount of time is served first, followed by the person who has waited the second longest
time, and so on. Formally, a queue Q is a list of elements. At any time, we only have
60
access to the first element of Q, known as the front or start of the queue. We insert
a new element into Q by appending the new element to the rear or end of the queue.
The operation of removing the front of Q is referred to as dequeue, while the operation
of appending to the rear of Q is called enqueue. That is, a queue implements a first-in
first-out (FIFO) protocol for adding and removing elements. As with lists, the length of
a queue is its total number of elements.
1
7
4
6
(a) Original undirected graph.

1
(b) First iteration of while loop.
7
4
6
(c) Second iteration of while loop.
(d) Third iteration of while loop.

1
2
2
3
7
4
6
(e) Fourth iteration of while loop.
(f) Final BFS tree.
Figure 2.3: Breadth-first search tree for an undirected graph.

Note that the BFS Algorithm 2.1 works on both undirected and directed graphs. For
an undirected graph, line 7 means that we explore all the neighbors of vertex v, i.e. the
set adj(v) of vertices adjacent to v. In the case of a digraph, we replace w adj(v)
on line 7 with w oadj(v) because we only want to explore all vertices that are outneighbors of v. The algorithm returns two lists D and T . The list T contains a subset
of edges in E(G) that make up a tree rooted at the given start vertex s. As trees are
connected graphs without cycles, we may take the vertices comprising the edges of T to
be the vertex set of the tree. It is clear that T represents a tree by means of a list of
edges, which allows us to identify the tree under consideration as the edge list T . The
list D has the same number of elements as the order of G = (V, E), i.e. length(D) = |V |.
61
7
4
6
(a) Original digraph.

1
7
4
6

4
2
3
3
7
2
4
6
(f) Final BFS tree.
Figure 2.4: Breadth-first search tree for a digraph.
62
The i-th element D[i] counts the number of edges in T between the vertices s and vi . In
other words, D[i] is the length of the s-vi path in T . It can be shown that D[i] = if
and only if G is disconnected. After one application of Algorithm 2.1, it may happen that
D[i] = for at least one vertex vi V . To traverse those vertices that are unreachable
from s, again we apply Algorithm 2.1 on G with starting vertex vi . Repeat this algorithm
as often as necessary until all vertices of G are visited. The result may be a tree that
contains all the vertices of G or a collection of trees, each of which contains a subset of
V (G). Figures 2.3 and 2.4 present BFS trees resulting from applying Algorithm 2.1 on
an undirected graph and a digraph, respectively.
Theorem 2.2. The worst-case time complexity of Algorithm 2.1 is O(|V | + |E|).
Proof. Without loss of generality, we can assume that G = (V, E) is connected. The
initialization steps in lines 1 to 4 take O(|V |) time. After initialization, all but one
vertex are labelled . Line 8 ensures that each vertex is enqueued at most once and
hence dequeued at most once. Each of enqueuing and dequeuing takes constant time.
The total time devoted to queue operations is O(|V |). The adjacency list of a vertex
is scanned after dequeuing that vertex, so each adjacency list is scanned at most once.
Summing the lengths of the adjacency lists, we have (|E|) and therefore we require
O(|E|) time to scan the adjacency lists. After the adjacency list of a vertex is scanned,
at most k edges are added to the list T , where k is the length of the adjacency list under
consideration. Like queue operations, appending to a list takes constant time, hence we
require O(|E|) time to build the list T . Therefore, BFS runs in O(|V | + |E|) time.
Theorem 2.3. For the list D resulting from Algorithm 2.1, let s be a starting vertex
and let v be a vertex such that D[v] 6= . Then D[v] is the length of any shortest path
from s to v.
Proof. It is clear that D[v] = if and only if there are no paths from s to v. Let v be
a vertex such that D[v] 6= . As v can be reached from s by a path of length D[v], the
length d(s, v) of any shortest s-v path satisfies d(s, v) D[v]. Use induction on d(s, v) to
show that equality holds. For the base case s = v, we have d(s, v) = D[v] = 0 since the
trivial path has length zero. Assume for induction that if d(s, v) = k, then d(s, v) = D[v].
Let d(s, u) = k + 1 with the corresponding shortest s-u path being (s, v1 , v2 , . . . , vk , u).
By our induction hypothesis, (s, v1 , v2 , . . . , vk ) is a shortest path from s to vk of length
d(s, vk ) = D[vk ] = k. In other words, D[vk ] < D[u] and the while loop spanning lines 5
to 11 processes vk before processing u. The graph under consideration has the edge vk u.
When examining the adjacency list of vk , BFS reaches u (if u is not reached earlier) and
so D[u] k + 1. Hence, D[u] = k + 1 and therefore d(s, u) = D[u] = k + 1.
In the proof of Theorem 2.3, we used d(u, v) to denote the length of the shortest path
from u to v. This shortest path length is also known as the distance from u to v, and
will be discussed in further details in section 2.3 and Chapter 5. The diameter diam(G)
of a graph G = (V, E) is defined as
diam(G) = max d(u, v).
u,vV
u6=v
(2.5)
Using the above definition, to find the diameter we first determine the distance between
each pair of distinct vertices, then we compute the maximum of all such distances.
63
Breadth-first search is a useful technique for finding the diameter: we simply run breadthfirst search from each vertex. An interesting application of the diameter appears in the
small-world phenomenon [117, 144, 192], which contends that a certain special class of
sparse graphs have low diameter.
2.2.2
Depth-first search
A depth-first search (DFS) is a graph traversal strategy similar to breadth-first search.

Both BFS and DFS differ in how they explore each vertex. Whereas BFS explores
the neighborhood of a vertex v before moving on to explore the neighborhoods of the
neighbors, DFS explores as deep as possible a path starting at v. One can think of BFS
as exploring the immediate surrounding, while DFS prefers to see what is on the other
side of the hill. In the 19th century, Lucas [137] and Tarry [178] investigated DFS as
a strategy for traversing mazes. Fundamental properties of DFS were discovered in the
early 1970s by Hopcroft and Tarjan [98, 177].
To get an intuitive appreciation for DFS, suppose we have an 8 8 chessboard in
front of us. We place a single knight piece on a fixed square of the board, as shown in
Figure 2.5(a). Our objective is to find a sequence of knight moves that visits each and
every square exactly once, while obeying the rules of chess that govern the movement
of the knight piece. Such a sequence of moves, if one exists, is called a knights tour .
How do we find such a tour? We could make one knight move after another, recording
each move to ensure that we do not step on a square that is already visited, until we
could not make any more moves. Acknowledging defeat when encountering a dead end,
it might make sense to backtrack a few moves and try again, hoping we would not get
stuck. If we fail again, we try backtracking a few more moves and traverse yet another
64
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0m0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
(a) The knights initial position.
(b) A knights tour.
(c) Graph representation of tour.
Figure 2.5: The knights tour from a given starting position.
65
path, hoping to make further progress. Repeat this strategy until a tour is found or until
we have exhausted all possible moves. The above strategy for finding a knights tour
is an example of depth-first search, sometimes called backtracking. Figure 2.5(b) shows
a knights tour with the starting position as shown in Figure 2.5(a); and Figure 2.5(c)
is a graph representation of this tour. The black-filled nodes indicate the endpoints
of the tour. A more interesting question is: What is the number of knights tours
on an 8 8 chessboard? Loebbing and Wegener [136] announced in 1996 that this
number is 33,439,123,484,294. The answer was later corrected by McKay [140] to be
13,267,364,410,532. See [66] for a discussion of the knights tour and its relationship to
mathematics.
Algorithm 2.2: A general depth-first search template.
Input: A directed or undirected graph G = (V, E) of order n > 0. A vertex s
from which to start the search. The vertices are numbered from 1 to
n = |V |, i.e. V = {1, 2, . . . , n}.
Output: A list D of distances of all vertices from s. A tree T rooted at s.
1
2
3
4
5
6
7
8
9
10
11
12
S [s]
/* stack of nodes to visit */
D [, , . . . , ]
/* n copies of */
D[s] 0
T []
while length(S) > 0 do
v pop(S)
if D[w] = then
D[w] D[v] + 1
push(S, w)
append(T, vw)
return (D, T )
Algorithm 2.2 formalizes the above description of depth-first search. The tree resulting from applying DFS on a graph is called a depth-first search tree. The general
structure of this algorithm bears close resemblance to Algorithm 2.1. A significant difference is that instead of using a queue to structure and organize vertices to be visited,
DFS uses another special type of list called a stack . To understand how elements of a
stack are organized, we use the analogy of a stack of cards. A new card is added to
the stack by placing it on top of the stack. Any time we want to remove a card, we
are only allowed to remove the top-most card that is on the top of the stack. A list
L = [a1 , a2 , . . . , ak ] of k elements is a stack when we impose the same rules for element
insertion and removal. The top and bottom of the stack are L[k] and L[1], respectively.
The operation of removing the top element of the stack is referred to as popping the
element off the stack. Inserting an element into the stack is called pushing the element
onto the stack. In other words, a stack implements a last-in first-out (LIFO) protocol
for element insertion and removal, in contrast to the FIFO policy of a queue. We also
use the term length to refer to the number of elements in the stack.
The depth-first search Algorithm 2.2 can be analyzed similar to how we analyzed
Algorithm 2.3. Just as BFS is applicable to both directed and undirected graphs, we
can also have undirected graphs and digraphs as input to DFS. For the case of an
66
7
4
6

1
7
4
6

1
(e) Final DFS tree.
Figure 2.6: Depth-first search tree for an undirected graph.
67
3
7
3
7
4
6

1
3
7
3
7
4
6

4
2
3
3
7
5
4
6
(f) Final DFS tree.
Figure 2.7: Depth-first search tree for a digraph.
68
undirected graph, line 7 of Algorithm 2.2 considers all vertices adjacent to the current
vertex v. In case the input graph is directed, we replace w adj(v) on line 7 with
w oadj(v) to signify that we only want to consider the out-neighbors of v. If any
neighbors (respectively, out-neighbors) of v are labelled as , we know that we have
not explored any paths starting from any of those vertices. So we label each of those
unexplored vertices with a positive integer and push them onto the stack S, where
they will wait for later processing. We also record the paths leading from v to each of
those unvisited neighbors, i.e. the edges vw for each vertex w adj(v) (respectively,
w oadj(v)) are appended to the list T . The test on line 8 ensures that we do not push
onto S any vertices on the path that lead to v. When we resume another round of the
while loop that starts on line 5, the previous vertex v have been popped off S and the
neighbors (respectively, out-neighbors) of v have been pushed onto S. To explore a path
starting at v, we choose any unexplored neighbors of v by popping an element off S and
repeat the for loop starting on line 7. Repeat the DFS algorithm as often as required in
order to traverse all vertices of the input graph. The output of DFS consists of two lists
D and T : T is a tree rooted at the starting vertex s; and each D[i] counts the length
of the s-vi path in T . Figures 2.6 and 2.7 show the DFS trees resulting from running
Algorithm 2.2 on an undirected graph and a digraph, respectively. The worst-case time
complexity of DFS can be analyzed using an argument similar to that in Theorem 2.2.
Arguing along the same lines as in the proof of Theorem 2.3, we can also show that the
list D returned by DFS contains lengths of any shortest paths from the starting vertex
s to any other vertex in the tree T .
0
5
1
4
6
Figure 2.8: The Petersen graph.
Example 2.4. In 1898, Julius Petersen published [157] a graph that now bears his name:
the Petersen graph shown in Figure 2.8. Compare the search trees resulting from running
breadth- and depth-first searches on the Petersen graph with starting vertex 0.
Solution. The Petersen graph in Figure 2.8 can be constructed and searched as follows.
sage : g = graphs . PetersenGraph (); g
Petersen graph : Graph on 10 vertices
sage : list ( g . breadth_first_search (0))
[0 , 1 , 4 , 5 , 2 , 6 , 3 , 9 , 7 , 8]
sage : list ( g . depth_first_search (0))
[0 , 5 , 8 , 6 , 9 , 7 , 2 , 3 , 4 , 1]
69
From the above Sage session, we see that starting from vertex 0 breadth-first search
yields the edge list
[01, 04, 05, 12, 16, 43, 49, 57, 58]
and depth-first search produces the corresponding edge list
[05, 58, 86, 69, 97, 72, 23, 34, 01].
Our results are illustrated in Figure 2.9.
0
4
6
(a) Breadth-first search.
(b) Depth-first search.
Figure 2.9: Traversing the Petersen graph starting from vertex 0.
2.2.3
Connectivity of a graph
Both BFS and DFS can be used to determine if an undirected graph is connected. Let
G = (V, E) be an undirected graph of order n > 0 and let s be an arbitrary vertex
of G. We initialize a counter c 1 to mean that we are starting our exploration at
s, hence we have already visited one vertex, i.e. s. We apply either BFS or DFS,
treating G and s as input to any of these algorithms. Each time we visit a vertex that
was previously unvisited, we increment the counter c. At the end of the algorithm, we
compare c with n. If c = n, we know that we have visited all vertices of G and conclude
that G is connected. Otherwise, we conclude that G is disconnected. This procedure is
summarized in Algorithm 2.3.
Note that Algorithm 2.3 uses the BFS template of Algorithm 2.1, with some minor
changes. Instead of initializing the list D with n = |V | copies of , we use n copies of
0. Each time we have visited a vertex w, we make the assignment D[w] 1, instead
of incrementing the value D[v] of ws parent vertex and
Passign that value to D[w]. At
the end of the while loop, we have the equality c =
dD d. The value of this sum
could be used in the test starting from line 12. However, the value of the counter c
is incremented immediately after we have visited an unvisited vertex. An advantage is
that we do not need to perform a separate summation outside of the while loop. To
use the DFS template for determining graph connectivity, we simply replace the queue
implementation in Algorithm 2.3 with a stack implementation (see problem 2.19).
70
Algorithm 2.3: Determining whether an undirected graph is connected.

Input: An undirected graph G = (V, E) of order n > 0. A vertex s from which to
start the search. The vertices are numbered from 1 to n = |V |,
i.e. V = {1, 2, . . . , n}.
Output: True if G is connected; False otherwise.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Q [s]
/* queue of nodes to visit */
D [0, 0, . . . , 0]
/* n copies of 0 */
D[s] 1
c1
v dequeue(Q)
if D[w] = 0 then
D[w] 1
cc+1
enqueue(Q, w)
if c = |V | then
return True
return False
2.3
Weights and distances
In Chapter 1, we briefly mentioned some applications of weighted graphs, but we did

not define the concept of weighted graphs. A graph is said to be weighted when we
assign a numeric label or weight to each of its edges. Depending on the application,
we can let the vertices represent physical locations and interpret the weight of an edge
as the distance separating two adjacent vertices. There might be a cost involved in
traveling from a vertex to one of its neighbors, in which case the weight assigned to the
corresponding edge can represent such a cost. The concept of weighted digraphs can be
similarly defined. When no explicit weights are assigned to the edges of an undirected
graph or digraph, it is usually convenient to consider each edge as having a weight of
one or unit weight.
Based on the concept of weighted graphs, we now define what it means for a path
to be a shortest path. Let G = (V, E) be a (di)graph with nonnegative edge weights
w(e) R for each edge e E. The length or distance d(P ) of a u-v path P from u V
to v V is the sum of the edge weights for edges in P . Denote by d(u, v) the smallest
value of d(P ) for all paths P from u to v. When we regard edge weights as physical
distances, a u-v path that realizes d(u, v) is sometimes called a shortest path from u to v.
The above definitions of distance and shortest path also apply to graphs with negative
edge weights. Unless otherwise specified, where the weight of an edge is not explicitly
given, we usually consider the edge to have unit weight.
The distance function d on a graph with nonnegative edge weights is known as a
metric function. Intuitively, the distance between two physical locations is greater than
zero. When these two locations coincide, i.e. they are one and the same location, the
distance separating them is zero. Regardless of whether we are measuring the distance
from location a to b or from b to a, we would obtain the same distance. Imagine now
a third location c. The distance from a to b plus the distance from b to c is greater
2.3. Weights and distances
71
than or equal to the distance from a to c. The latter principle is known as the triangle
inequality. In summary, given three vertices u, v, w in a graph G, the distance function
d on G satisfies the following property.
Lemma 2.5. Path distance as metric function. Let G = (V, E) be a graph with
weight function w : E R. Define a distance function d : V V R given by
(
,
if there are no paths from u to v,
d(u, v) =
min{w(W ) | W is a u-v walk}, otherwise.
Then d is a metric on V if it satisfies the following properties:
1. Nonnegativity: d(u, v) 0 with d(u, v) = 0 if and only if u = v.
2. Symmetry: d(u, v) = d(v, u).
3. Triangle inequality: d(u, v) + d(v, w) d(u, w).
The pair (V, d) is called a metric space, where the word metric refers to the distance
function d. Any graphs we consider are assumed to have finite sets of vertices. For this
reason, (V, d) is also known as a finite metric space. The distance matrix D = [d(vi , vj )]
of a connected graph is the distance matrix of its finite metric space. The topic of metric
space is covered in further details in topology texts such as Runde [164] and Shirali and
Vasudeva [169]. See Buckley and Harary [40] for an in-depth coverage of the distance
concept in graph theory.
Many different algorithms exist for computing a shortest path in a weighted graph.
Some only work if the graph has no negative weight cycles. Some assume that there is a
single start or source vertex. Some compute the shortest paths from any vertex to any
other and also detect if the graph has a negative weight cycle. No matter what algorithm
is used for the special case of nonnegative weights, the length of the shortest path can
neither equal nor exceed the order of the graph.
Lemma 2.6. Fix a vertex v in a connected graph G = (V, E) of order n = |V |. If there
are no negative weight cycles in G, then there exists a shortest path from v to any other
vertex w V that uses at most n 1 edges.
Proof. Suppose that G contains no negative weight cycles. Observe that at most n 1
edges are required to construct a path from v to any vertex w (Proposition 1.11). Let P
denote such a path:
P : v0 = v, v1 , v2 , . . . , vk = w.
Since G has no negative weight cycles, the weight of P is no less than the weight of
P 0 , where P 0 is the same as P except that all cycles have been removed. Thus, we can
remove all cycles from P and obtain a v-w path P 0 of lower weight. Since the final path
is acyclic, it must have no more than n 1 edges.
Having defined weights and distances, we are now ready to discuss shortest path
algorithms for weighted graphs. The breadth-first search Algorithm 2.1 can be applied
where each edge has unit weight. Moving on to the general case of graphs with positive
edge weights, algorithms for determining shortest paths in such graphs can be classified
as weight-setting or weight-correcting [81]. A weight-setting method traverses a graph
72
Algorithm 2.4: A template for shortest path algorithms.

Input: A weighted graph or digraph G = (V, E), where the vertices are numbered
as V = {1, 2, . . . , n}. A starting vertex s.
Output: A list D of distances from s to all other vertices. A list P of parent
vertices such that P [v] is the parent of v.
1
2
3
4
5
6
7
8
9
10
11
12
D [, , . . . , ]
/* n copies of */
C list of candidate vertices to visit
while length(C) > 0 do
select v C
C remove(C, v)
for each u adj(v) do
if D[u] > D[v] + w(vu) then
D[u] D[v] + w(vu)
P [u] v
if u
/ C then
add u to C
return (D, P )
and assigns weights that, once assigned, remain unchanged for the duration of the algorithm. Weight-setting algorithms cannot deal with negative weights. On the other
hand, a weight-correcting method is able to change the value of a weight many times
while traversing a graph. In contrast to a weight-setting algorithm, a weight-correcting
algorithm is able to deal with negative weights, provided that the weight sum of any
cycle is nonnegative. The term negative cycle refers to the weight sum s of a cycle such
that s < 0. Some algorithms halt upon detecting a negative cycle; examples of such
algorithms include the Bellman-Ford and Johnsons algorithms.
Algorithm 2.4 is a general template for many shortest path algorithms. With a tweak
here and there, one could modify it to suit the problem at hand. Note that w(vu) is the
weight of the edge vu. If the input graph is undirected, line 6 considers all the neighbors
of v. For digraphs, we are interested in out-neighbors of v and accordingly we replace
u adj(v) in line 6 with u oadj(v). The general flow of Algorithm 2.4 follows the
same pattern as depth-first and breadth-first searches.
2.4
Dijkstras algorithm
2.4. Dijkstras algorithm
73
Dijkstras algorithm [58], discovered by E. W. Dijkstra in 1959, is a graph search algorithm that solves the single-source shortest path problem for a graph with nonnegative
edge weights. The algorithm is a generalization of breadth-first search. Imagine that
the vertices of a weighted graph represent cities and edge weights represent distances
between pairs of cities connected by a direct road. Dijkstras algorithm can be used to
find a shortest route from a fixed city to any other city.
Let G = (V, E) be a (di)graph with nonnegative edge weights. Fix a start or source
vertex s V . Dijkstras Algorithm 2.5 performs a number of steps, basically one step
for each vertex in V . First, we initialize a list D with n copies of and then assign 0 to
D[s]. The purpose of the symbol is to denote the largest possible value. The list D is
to store the distances of all shortest paths from s to any other vertices in G, where we
take the distance of s to itself to be zero. The list P of parent vertices is initially empty
and the queue Q is initialized to all vertices in G. We now consider each vertex in Q,
removing any vertex after we have visited it. The while loop starting on line 5 runs until
we have visited all vertices. Line 6 chooses which vertex to visit, preferring a vertex v
whose distance value D[v] from s is minimal. After we have determined such a vertex v,
we remove it from the queue Q to signify that we have visited v. The for loop starting
on line 8 adjusts the distance values of each neighbor u of v such that u is also in Q. If
G is directed, we only consider out-neighbors of v that are also in Q. The conditional
starting on line 9 is where the adjustment takes place. The expression D[v] + w(vu)
sums the distance from s to v and the distance from v to u. If this total sum is less than
the distance D[u] from s to u, we assign this lesser distance to D[u] and let v be the
parent vertex of u. In this way, we are choosing a neighbor vertex that results in minimal
distance from s. Each pass through the while loop decreases the number of elements in
Q by one without adding any elements to Q. Eventually, we would exit the while loop
and the algorithm returns the lists D and P .
Algorithm 2.5: A general template for Dijkstras algorithm.
Input: An undirected or directed graph G = (V, E) that is weighted and has no
self-loops. The order of G is n > 0. A vertex s V from which to start
the search. Vertices are numbered from 1 to n, i.e. V = {1, 2, . . . , n}.
Output: A list D of distances such that D[v] is the distance of a shortest path
from s to v. A list P of vertex parents such that P [v] is the parent of v,
i.e. v is adjacent from P [v].
1
2
3
4
5
6
7
8
9
10
11
12
D [, , . . . , ]
/* n copies of */
D[s] 0
P []
QV
/* list of nodes to visit */
find v Q such that D[v] is minimal
Q remove(Q, v)
for each u adj(v) Q do
if D[u] > D[v] + w(vu) then
D[u] D[v] + w(vu)
P [u] v
return (D, P )
74
v2
v4
v2
10
v4
1
10
v1
v3
v5
v1
v3
v5
v2
v4
v2
10
v4
1
10
v1
v3
v5
v1
9
v3
v5
2
v2
v4
v2
10
v4
7
8
4
v1
9
v3
4
v5
v1
v3
3
v5
2
(f) Final shortest paths graph.
Figure 2.10: Searching a weighted digraph using Dijkstras algorithm.
v1
(0, )
v2
v3
(, ) (, )
(10, v1 ) (3, v1 )
(7, v3 )
v4
v5
(, ) (, )
(11, v3 ) (5, v3 )
(9, v2 )
Table 2.4: Stepping through Dijkstras algorithm.
2.4. Dijkstras algorithm
75
Example 2.7. Apply Dijkstras algorithm to the graph in Figure 2.10(a), with starting
vertex v1 .
Solution. Dijkstras Algorithm 2.5 applied to the graph in Figure 2.10(a) yields the
sequence of intermediary graphs shown in Figure 2.10, culminating in the final shortest
paths graph of Figure 2.10(f) and Table 2.4. For any column vi in the table, each 2-tuple
represents the distance and parent vertex of vi . As we move along the graph, processing
vertices according to Dijkstras algorithm, the distance and parent vertex of a column
are updated. The underlined 2-tuple represents the final distance and parent vertex
produced by Dijkstras algorithm. From Table 2.4, we have the following shortest paths
and distances:
v1 -v2 : v1 , v3 , v2
d(v1 , v2 ) = 7
v1 -v3 : v1 , v3
d(v1 , v3 ) = 3
v1 -v4 : v1 , v3 , v2 , v4
d(v1 , v4 ) = 9
v1 -v5 : v1 , v3 , v5
d(v1 , v5 ) = 5
Intermediary vertices for a u-v path are obtained by starting from v and work backward
using the parent of v, then the parent of the parent, and so on.
Dijkstras algorithm is an example of a greedy algorithm. Whenever it tries to find the
next vertex, it chooses only that vertex that minimizes the total weight so far. Greedy
algorithms may not produce the best possible result. However, as the following theorem
shows, Dijkstras algorithm does indeed produce shortest paths.
Theorem 2.8. Correctness of Algorithm 2.5. Let G = (V, E) be a weighted
(di)graph with a nonnegative weight function w. When Dijkstras algorithm is applied to
G with source vertex s V , the algorithm terminates with D[u] = d(s, u) for all u V .
Furthermore, if D[v] 6= and v 6= s, then s = u1 , u2 , . . . , uk = v is a shortest s-v path
such that ui1 = P [ui ] for i = 2, 3, . . . , k.
Proof. If G is disconnected, then any v V that cannot be reached from s has distance
D[v] = upon algorithm termination. Hence, it suffices to consider the case where G
is connected. Let V = {s = v1 , v2 , . . . , vn } and use induction on i to show that after
visiting vi we have
D[v] = d(s, v)
for all v Vi = {v1 , v2 , . . . , vi }.
(2.6)
For i = 1, equality holds. Assume for induction that (2.6) holds for some 1 i n 1,
so that now our task is to show that (2.6) holds for i + 1. To verify D[vi+1 ] = d(s, vi+1 ),
note that by our inductive hypothesis,
D[vi+1 ] = min {d(s, v) + w(vu) | v Vi and u adj(v) (Q\Vi )}
and respectively
D[vi+1 ] = min {d(s, v) + w(vu) | v Vi and u oadj(v) (Q\Vi )}
if G is directed. Therefore, D[vi+1 ] = d(s, vi+1 ).
Let v V such that D[v] 6= and v 6= s. We now construct an s-v path. When
Algorithm 2.5 terminates, we have D[v] = D[v1 ] + w(v1 v), where P [v] = v1 and d(s, v) =
d(s, v1 ) + w(v1 v). This means that v1 is the second-to-last vertex in a shortest s-v path.
Repeated application of this process using the parent list P , we eventually produce a
shortest s-v path s = vm , vm1 , . . . , v1 , v, where P [vi ] = vi+1 for i = 1, 2, . . . , m 1.
76
To analyze the worst case time complexity of Algorithm 2.5, note that initializing D
takes O(n + 1) and initializing Q takes O(n), for a total of O(n) devoted to initialization.
Each extraction of a vertex v with minimal D[v] requires O(n) since we search through
the entire list Q to determine the minimum value, for a total of O(n2 ). Each insertion
into D requires constant time and the same holds for insertion into P . Thus, insertion
into D and P takes O(|E| + |E|) = O(|E|), which require at most O(n) time. In the
worst case, Dijkstras Algorithm 2.5 has running time O(n2 + n) = O(n2 ).
Can we improve the run time of Dijkstras algorithm? The time complexity of Dijkstras algorithm depends on its implementation. With a simple list implementation as
presented in Algorithm 2.5, we have a worst case time complexity of O(n2 ), where n is
the order of the graph under consideration. Let m be the size of the graph. Table 2.5
presents time complexities of Dijkstras algorithm for various implementations. Out of
all the four implementations in this table, the heap implementations are much more
efficient than the list implementation presented in Algorithm 2.5. A heap is a type of
tree, a topic which will be covered in Chapter 3. Of all the heap implementations in
Table 2.5, the Fibonacci heap implementation [80] yields the best runtime. Chapter 4
discusses how to use trees for efficient implementations of priority queues via heaps.
Implementation Time complexity
list
O(n2 )

binary heap
O (n + m) ln n

n
k-ary heap
O (kn + m) ln
ln k
Fibonacci heap
O(n ln n + m)
Table 2.5: Implementation specific worst-case time complexity of Dijkstras algorithm.
2.5
Bellman-Ford algorithm
A disadvantage of Dijkstras Algorithm 2.5 is that it cannot handle graphs with negative
edge weights. The Bellman-Ford algorithm computes single-source shortest paths in
a weighted graph or digraph, where some of the edge weights may be negative. This
algorithm is a modification of the one published in 1957 by Richard E. Bellman [21] and
that by Lester Randolph Ford, Jr. [76] in 1956. Shimbel [168] independently discovered
the same method in 1955, and Moore [146] in 1959. In contrast to the greedy approach
that Dijkstras algorithm takes, i.e. searching for the cheapest path, the Bellman-Ford
algorithm searches over all edges and keeps track of the shortest one found as it searches.
The Bellman-Ford Algorithm 2.6 runs in time O(mn), where m and n are the size
and order of an input graph, respectively. To see this, note that the initialization on
2.6. Floyd-Roy-Warshall algorithm
77
Algorithm 2.6: The Bellman-Ford algorithm.

self-loops. Negative edge weights are allowed. The order of G is n > 0. A
vertex s V from which to start the search. Vertices are numbered from
1 to n, i.e. V = {1, 2, . . . , n}.
i.e. v is adjacent from P [v]. If G has negative-weight cycles, then return
False. Otherwise, return D and P .
1
2
3
4
5
6
7
8
9
10
11
12
D [, , . . . , ]
D[s] 0
P []
for i 1, 2, . . . , n 1 do
for each edge uv E do
if D[v] > D[u] + w(uv) then
D[v] D[u] + w(uv)
P [v] u
return False
return (D, P )
/* n copies of */
lines 1 to 3 takes O(n). Each of the n 1 rounds of the for loop starting on line 4 takes
O(m), for a total of O(mn) time. Finally, the for loop starting on line 9 takes O(m).
The loop starting on line 4 performs at most n 1 updates of the distance D[v] of
each head of an edge. Many graphs have sizes that are less then n 1, resulting in
a number of redundant rounds of updates. To avoid such redundancy, we could add
an extra check in the outer loop spanning lines 4 to 8 to immediately terminate that
outer loop after any round that did not result in an update of any D[v]. Algorithm 2.7
presents a modification of the Bellman-Ford Algorithm 2.6 that avoids redundant rounds
of updates.
2.6
Floyd-Roy-Warshall algorithm
The shortest distance between two points is not a very interesting journey.
R. Goldberg
Let D be a weighted digraph of order n and size m. Dijkstras Algorithm 2.5 and
the Bellman-Ford Algorithm 2.6 can be used to determine shortest paths from a single
source vertex to all other vertices of D. To determine a shortest path between each pair
of distinct vertices in D, we repeatedly apply either of these algorithms to each vertex
of D. Such repeated application of Dijkstras and the Bellman-Ford algorithms results
in algorithms that run in time O(n3 ) and O(n2 m), respectively.
The Floyd-Roy-Warshall algorithm (FRW), or the Floyd-Warshall algorithm, is an
algorithm for finding shortest paths in a weighted, directed graph. Like the BellmanFord algorithm, it allows for negative edge weights and detects a negative weight cycle
if one exists. Assuming that there are no negative weight cycles, a single execution of
78
Algorithm 2.7: The Bellman-Ford algorithm with checks for redundant updates.
self-loops. Negative edge weights are allowed. The order of G is n > 0. A
vertex s V from which to start the search. Vertices are numbered from
1 to n, i.e. V = {1, 2, . . . , n}.
i.e. v is adjacent from P [v]. If G has negative-weight cycles, then return
False. Otherwise, return D and P .
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
D [, , . . . , ]
D[s] 0
P []
for i 1, 2, . . . , n 1 do
updated False
D[v] D[u] + w(uv)
P [v] u
updated True
if updated = False then
exit the loop
return False
return (D, P )
/* n copies of */
79
the FRW algorithm will find the shortest paths between all pairs of vertices. It was
discovered independently by Bernard Roy [163] in 1959, Robert Floyd [75] in 1962, and
by Stephen Warshall [188] in 1962.
In some sense, the FRW algorithm is an example of dynamic programming, which
allows one to break the computation into simpler steps using some sort of recursive
procedure. The rough idea is as follows. Temporarily label the vertices of a weighted
digraph G as V = {1, 2, . . . , n} with n = |V (G)|. Let W = [w(i, j)] be the weight matrix
of G where
w(ij), if ij E(G),
w(i, j) = 0,
(2.7)
if i = j,
,
otherwise.
Let Pk (i, j) be a shortest path from i to j such that its intermediate vertices are in
{1, 2, . . . , k}. Let Dk (i, j) be the weight (or distance) of Pk (i, j). If no shortest i-j
paths exist, define Pk (i, j) = and Dk (i, j) = for all k {1, 2, . . . , n}. If k = 0,
then P0 (i, j) : i, j since no intermediate vertices are allowed in the path and hence
D0 (i, j) = w(i, j). In other words, if i and j are adjacent, a shortest i-j path is the
edge ij itself and the weight of this path is simply the weight of ij. Now consider
Pk (i, j) for k > 0. Either Pk (i, j) passes through k or it does not. If k is not on the
path Pk (i, j), then the intermediate vertices of Pk (i, j) are in {1, 2, . . . , k 1}, as are
the vertices of Pk1 (i, j). In case Pk (i, j) contains the vertex k, then Pk (i, j) traverses
k exactly once by the definition of path. The i-k subpath in Pk (i, j) is a shortest i-k
path whose intermediate vertices are drawn from {1, 2, . . . , k 1}, which is also the set
of intermediate vertices for the k-j subpath in Pk (i, j). That is, to obtain Pk (i, j), we
take the union of the paths Pk1 (i, k) and Pk1 (k, j). We compute the weight Dk (i, j)
of Pk (i, j) using the expression
(
w(i, j),
if k = 0,
Dk (i, j) =
(2.8)
min{Dk1 (i, j), Dk1 (i, k) + Dk1 (k, j)}, if k > 0.
The key to the Floyd-Roy-Warshall algorithm lies in exploiting expression (2.8). If
n = |V |, then this is a O(n3 ) time algorithm. For comparison, the Bellman-Ford algorithm has complexity O(|V | |E|), which is O(n3 ) time for dense graphs. However,
Bellman-Ford only yields the shortest paths emanating from a single vertex. To achieve
comparable output, we would need to iterate Bellman-Ford over all vertices, which would
be an O(n4 ) time algorithm for dense graphs. Except possibly for sparse graphs, FloydRoy-Warshall is better than an iterated implementation of Bellman-Ford. Note that
Pk (i, k) = Pk1 (i, k) and Pk (k, i) = Pk1 (k, i), consequently Dk (i, k) = Dk1 (i, k) and
Dk (k, i) = Dk1 (k, i). This observation allows us to replace Pk (i, j) with P (i, j) for
k = 1, 2, . . . , n. The final results of P (i, j) and D(i, k) are the same as Pn (i, j) and
Dn (i, j), respectively. Algorithm 2.8 summarizes the above discussion into an algorithmic presentation.
Like the Bellman-Ford algorithm, the Floyd-Roy-Warshall algorithm can also detect
the presence of negative weight cycles. If G is a weighted digraph without self-loops,
by (2.7) we have D(i, i) = 0 for i = 1, 2, . . . , n. Any path p starting and ending at i
could only improve upon the initial weight of 0 if the weight sum of p is less than zero, i.e.
a negative weight cycle. Upon termination of Algorithm 2.8, if D(i, i) < 0, we conclude
that there is a path starting and ending at i whose weight sum is negative.
80
Algorithm 2.8: The Floyd-Roy-Warshall algorithm for all-pairs shortest paths.

Input: A weighted digraph G = (V, E) that has no self-loops. Negative edge
weights are allowed. The order of G is n > 0. Vertices are numbered from
1 to n, i.e. V = {1, 2, . . . , n}. The weight matrix W = [w(i, j)] of G as
defined in (2.7).
Output: A matrix P = [aij ] of shortest paths in G. A matrix D = [aij ] of
distances where D[i, j] is the weight (or distance) of a shortest i-j path
in G.
1
2
3
4
5
6
7
8
9
10
n |V |
P [aij ] an n n zero matrix
D[aij ] W [w(i, j)]
for k 1, 2, . . . , n do
for i 1, 2, . . . , n do
for j 1, 2, . . . , n do
if D[i, j] > D[i, k] + D[k, j] then
P [i, j] k
D[i, j] D[i, k] + D[k, j]
return (P, D)
Here is an implementation in Sage.

def fl oy d_roy_warshall ( A ):
"""
Shortest paths
INPUT :
- A -- weighted adjacency matrix
OUTPUT :
- dist -- a matrix of distances of shortest paths .
- paths -- a matrix of shortest paths .
"""
G = Graph (A , format = " w e i g h t e d _ a d j a c e n c y _ m a tr i x " )
V = G . vertices ()
E = [( e [0] , e [1]) for e in G . edges ()]
n = len ( V )
dist = [[0]* n for i in range ( n )]
paths = [[ -1]* n for i in range ( n )]
# initialization step
for i in range ( n ):
for j in range ( n ):
if (i , j ) in E :
paths [ i ][ j ] = j
if i == j :
dist [ i ][ j ] = 0
elif A [ i ][ j ] < >0:
dist [ i ][ j ] = A [ i ][ j ]
else :
dist [ i ][ j ] = infinity
# iteratively finding the shortest path
for j in range ( n ):
if i <> j :
for k in range ( n ):
if k <> j :
if dist [ i ][ k ] > dist [ i ][ j ]+ dist [ j ][ k ]:
paths [ i ][ k ] = V [ j ]
dist [ i ][ k ] = min ( dist [ i ][ k ] , dist [ i ][ j ] + dist [ j ][ k ])
if dist [ i ][ i ] < 0:
raise ValueError , " A negative edge weight cycle exists . "
81
return dist , matrix ( paths )
Here are some examples.

sage : A = matrix ([[0 ,1 ,2 ,3] , [0 ,0 ,2 ,1] , [ -5 ,0 ,0 ,3] , [1 ,0 ,1 ,0]]); A
sage : f lo yd_roy_warshall ( A )
Traceback ( click to the left of this block for traceback )
...
ValueError : A negative edge weight cycle exists .
The plot of this weighted digraph with four vertices appears in Figure 2.11.
1
Figure 2.11: Demonstrating the Floyd-Roy-Warshall algorithm.

sage :
sage :
([[0 ,
[ -1
[ 2
[ -1
[ 2
A = matrix ([[0 ,1 ,2 ,3] , [0 ,0 ,2 ,1] , [ -1/2 ,0 ,0 ,3] , [1 ,0 ,1 ,0]]); A

f lo yd_roy_warshall ( A )
1 , 2 , 2] , [3/2 , 0 , 2 , 1] , [ -1/2 , 1/2 , 0 , 3/2] , [1/2 , 3/2 , 1 , 0]] ,
1 2 1]
-1 2 3]
0 -1 1]
2 -1 -1])
The plot of this weighted digraph with four vertices appears in Figure 2.12.
Example 2.9. Section 1.6 briefly presented the concept of molecular graphs in chemistry. The Wiener number of a molecular graph was first published in 1947 by Harold
Wiener [195] who used it in chemistry to study properties of alkanes. Other applications [92] of the Wiener number to chemistry are now known. If G = (V, E) is a
connected graph with vertex set V = {v1 , v2 , . . . , vn }, then the Wiener number W of G is
defined by
X
W (G) =
d(vi , vj )
(2.9)
i<j
where d(vi , vj ) is the distance from vi to vj . What is the Wiener number of the molecular
graph in Figure 2.13?
Solution. Consider the molecular graph in Figure 2.13 as directed with unit weight.
To compute the Wiener number of this graph, use the Floyd-Roy-Warshall algorithm to
obtain a distance matrix D = [di,j ], where di,j is the distance from vi to vj , and apply the
definition (2.9). The distance matrix resulting from the Floyd-Roy-Warshall algorithm
82
0.5
1
3
Figure 2.12: Another demonstration of the Floyd-Roy-Warshall algorithm.
Figure 2.13: Molecular graph of 1,1,3-trimethylcyclobutane.

is
0
2
M =
2
3
2
4
83
2
0
1
2
3
2
4
1
1
0
1
2
1
3
2
2
1
0
1
2
2
3
3
2
1
0
1
1
2
2
1
2
1
0
2
4
4
2
.
1
2
0
Sum all entries in the upper (or lower) triangular of M to obtain the Wiener number
W = 42. Using Sage, we have
sage :
sage :
sage :
sage :
sage :
sage :
...
...
sage :
42
G =
D =
M =
M =
W =
for
Graph ({1:[3] , 2:[3] , 3:[4 ,6] , 4:[5] , 6:[5] , 5:[7]})

G . sh or t es t _p at h _a l l_ pa i rs ()[0]
[ D [ i ][ j ] for i in D for j in D [ i ]]
matrix (M , nrows =7 , ncols =7)
0
i in range ( M . nrows () - 1):
for j in range ( i +1 , M . ncols ()):
W += M [i , j ]
which verifies our computation above. See Gutman et al. [92] for a survey of some results
concerning the Wiener number.
2.6.1
Transitive closure
Consider a digraph G = (V, E) of order n = |V |. The transitive closure of G is defined

as the digraph G = (V, E ) having the same vertex set as G. However, the edge set
E of G consists of all edges uv such that there is a u-v path in G and uv
/ E. The
transitive closure G answers an important question about G: If u and v are two distinct
vertices of G, are they connected by a path with length 1?
To compute the transitive closure of G, we let each edge of G be of unit weight and
apply the Floyd-Roy-Warshall Algorithm 2.8 on G. By Proposition 1.11, for any i-j path
in G we have D[i, j] < n, and if there are no paths from i to j in G, we have D[i, j] = .
This procedure for computing transitive closure runs in time O(n3 ).
Modifying the Floyd-Roy-Warshall algorithm slightly, we obtain an algorithm for
computing transitive closure that, in practice, is more efficient than Algorithm 2.8 in
terms of time and space. Instead of using the operations min and + as is the case in the
Floyd-Roy-Warshall algorithm, we replace these operations with the logical operations
(logical OR) and (logical AND), respectively. For i, j, k = 1, 2, . . . , n, define Tk (i, j) = 1
if there is an i-j path in G with all intermediate vertices belonging to {1, 2, . . . , k}, and
Tk (i, j) = 0 otherwise. Thus, the edge ij belongs to the transitive closure G if and only
if Tk (i, j) = 1. The definition of Tk (i, j) can be cast in the form of a recursive definition
as follows. For k = 0, we have
(
0, if i 6= j and ij
/ E,
T0 (i, j) =
1, if i = j or ij E
and for k > 0, we have

Tk (i, j) = Tk1 (i, j) Tk1 (i, k) Tk1 (k, j) .
We need not use the subscript k at all and instead let T be a boolean matrix such that
T [i, j] = 1 if and only if there is an i-j path in G, and T [i, j] = 0 otherwise. Using
84
the above notations, the Floyd-Roy-Warshall algorithm is translated to Algorithm 2.9

for obtaining the boolean matrix T . We can then use T and the definition of transitive
closure to obtain the edge set E in the transitive closure G = (V, E ) of G = (V, E).
A more efficient transitive closure algorithm can be found in the PhD thesis of Esko
Nuutila [155]. See also the method of four Russians [2, 8]. The transitive closure algorithm as presented in Algorithm 2.9 is due to Stephen Warshall [188]. It is a special
case of a more general algorithm in automata theory due to Stephen Kleene [116], called
Kleenes algorithm.
Algorithm 2.9: Variant of the Floyd-Roy-Warshall algorithm for transitive closure.
Input: A digraph G = (V, E) that has no self-loops. Vertices are numbered from
1 to n, i.e. V = {1, 2, . . . , n}.
Output: The boolean matrix T such that T [i, j] = 1 if and only if there is an i-j
path in G, and T [i, j] = 0 otherwise.
1
2
3
4
5
6
7
n |V |
T adjacency matrix of G
for k 1, 2, . . . , n do
for i 1, 2, . . . , n do
for j 1, 2, . . . , n do

T [i, j] T [i, j] T [i, k] T [k, j]
return T
2.7
Johnsons algorithm
The shortest distance between two points is under construction.
Noelie Altito
Let G = (V, E) be a sparse digraph with edge weights but no negative cycles. Johnsons
algorithm [109] finds a shortest path between each pair of vertices in G. First published
in 1977 by Donald B. Johnson, the main insight of Johnsons algorithm is to combine
the technique of edge reweighting with the Bellman-Ford and Dijkstras algorithms. The
Bellman-Ford algorithm is first used to ensure that G has no negative cycles. Next,
we reweight edges in such a manner as to preserve shortest paths. The final stage
makes use of Dijkstras algorithm for computing shortest paths between all vertex pairs.
Pseudocode for Johnsons algorithm is presented in Algorithm 2.10. With a Fibonacci
heap implementation of the minimum-priority queue, the time complexity for sparse
graphs is O(|V |2 log |V | + |V | |E|), where n = |V | is the number of vertices of the
original graph G.
To prove the correctness of Algorithm 2.10, we need to show that the new set of edge
weights produced by w must satisfy two properties:
1. The reweighted edges preserve shortest paths. That is, let p be a u-v path for
u, v V . Then p is a shortest weighted path using weight function w if and only
if p is also a shortest weighted path using weight function w.
2. The reweight function w produces nonnegative weights. In other words, if u, v V

then w(uv)
0.
2.7. Johnsons algorithm
85
Algorithm 2.10: Johnsons algorithm for sparse graphs.

Input: A sparse weighted digraph G = (V, E), where the vertex set is
V = {1, 2, . . . , n}.
Output: If G has negative-weight cycles, then return False. Otherwise, return an
n n matrix D of shortest-path weights and a list P such that P [v] is a
parent list resulting from running Dijkstras algorithm on G with start
vertex v.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
s vertex not in V
V 0 V {s}
E 0 E {sv | v V }
G0 digraph (V 0 , E 0 ) with weight w(sv) = 0 for all v V
if BellmanFord(G0 , w, s) = False then
return False
d distance list returned by BellmanFord(G0 , w, s)
for each edge uv E 0 do
w(uv)
w(uv) + d[u] d[v]

for each u V do
P ) distance and parent lists returned by Dijkstra(G, w,
(,
u)
P [u] P
for each v V do
+ d[v] d[u]
D[u, v] [v]
return (D, P )
Both of these properties are proved in Lemma 2.10.

Lemma 2.10. Reweighting preserves shortest paths. Let G = (V, E) be a weighted
digraph having weight function w : E R and let h : V R be a mapping of vertices
to real numbers. Let w be another weight function for G such that
w(uv)
= w(uv) + h(u) h(v)

for all uv E. Suppose p : v0 , v1 , . . . , vk is any path in G. Then we have the following
results.
1. The path p is a shortest v0 -vk path with weight function w if and only if it is a
shortest v0 -vk path with weight function w.
2. The graph G has a negative cycle using weight function w if and only if G has a
negative cycle using w.
3. If G has no negative cycles, then w(uv)
0 for all uv E.
Proof. Write and for the shortest path weights derived from w and w,
respectively.
0 , vk ).
To prove part 1, we need to show that w(p) = (v0 , vk ) if and only if w(p)
= (v
86
First, note that any v0 -vk path p satisfies w(p)
= w(p) + h(v0 ) h(vk ) because

w(p)
k
X
i=1
k
X
i=1
k
X
i=1
k
X
i=1
w(v
i1 vi )

w(vi1 vi ) + h(vi1 ) h(vi )
w(vi1 vi ) +
k
X
i=1

h(vi1 ) h(vi )
w(vi1 vi ) + h(v0 ) h(vk )
= w(p) + h(v0 ) h(vk ).

Any v0 -vk path shorter than p and using weight function w is also shorter using w.
Therefore, w(p) = (v0 , vk ) if and only if w(p)
= (v0 , vk ).
To prove part 2, consider any cycle c : v0 , v1 , . . . , vk where v0 = vk . Using the proof
of part 1, we have
w(c)
= w(c) + h(v0 ) h(vk )
= w(c)
thus showing that c is a negative cycle using w if and only if it is a negative cycle using
w.
To prove part 3, we construct a new graph G0 = (V 0 , E 0 ) as follows. Consider a vertex

s
/ V and let V 0 = V {s} and E 0 = E {sv | v V }. Extend the weight function w
to include w(sv) = 0 for all v V . By construction, s has no incoming edges and any
path in G0 that contains s has s as the source vertex. Thus G0 has no negative cycles if
and only if G has no negative cycles. Define the function h : V R by v 7 (s, v)
with domain V 0 . By the triangle inequality (see Lemma 2.5),
(s, u) + w(uv) (s, v)
h(u) + w(uv) h(v)
thereby showing that w(uv)
= w(uv) + h(u) h(v) 0.
2.8
Problems
I believe that a scientist looking at nonscientific problems is just as dumb as the next guy.
Richard Feynman
2.1. The Euclidean algorithm is one of the oldest known algorithms. Given two positive
integers a and b with a b, let a mod b be the remainder obtained upon dividing
a by b. The Euclidean algorithm determines the greatest common divisor gcd(a, b)
of a and b. The procedure is summarized in Algorithm 2.11. Refer to Chabert [45]
for a history of algorithms from ancient to modern times.
(a) Implement Algorithm 2.11 in Sage and use your implementation to compute
the greatest common divisors of various pairs of integers. Use the built-in
Sage command gcd to verify your answer.
2.8. Problems
87
Algorithm 2.11: The Euclidean algorithm.

Input: Two integers a > 0 and b 0 with a b.
Output: The greatest common divisor of a and b.
1
2
3
4
5
6
7
xa
yb
while y 6= 0 do
r x mod y
xy
yr
return x
(b) Modify Algorithm 2.11 to compute the greatest common divisor of any pair
of integers.
2.2. Given a polynomial p(x) = an xn + an1 xn1 + + a1 x + a0 of degree n, we can use
Horners method [101] to efficiently evaluate p at a specific value x = x0 . Horners
method evaluates p(x) by expressing the polynomial as
p(x) =
n
X
i=0
ai xi = ( (an x + an1 )x + )x + a0
to obtain Algorithm 2.12.

(a) Compare the runtime of polynomial evaluation using equation (2.2) and Horners
method.
(b) Let v be a bit vector read using big-endian order. Write a Sage function that
uses Horners method to compute the integer representation of v.
(c) Modify Algorithm 2.12 to evaluate the integer representation of a bit vector
v read using little-endian order. Hence, write a Sage function to convert v to
its integer representation.
Algorithm 2.12: Polynomial evaluation using Horners method.
P
Input: A polynomial p(x) = ni=0 ai xi , where an 6= 0 and x0 R.
Output: An evaluation of p at x = x0 .
1
2
3
4
b an
for i n 1, n 2, . . . , 0 do
b bx0 + ai
return b
2.3. Let G = (V, E) be an undirected graph, let s V , and D is the list of distances
resulting from running Algorithm 2.1 with G and s as input. Show that G is
connected if and only if D[v] is defined for each v V .
2.4. Show that the worst-case time complexity of depth-first search Algorithm 2.2 is
O(|V | + |E|).
88
2.5. Let D be the list of distances returned by Algorithm 2.2, let s be a starting vertex,
and let v be a vertex such that D[v] 6= . Show that D[v] is the length of any
shortest path from s to v.
2.6. Consider the graph in Figure 2.10 as undirected. Run this undirected version
through Dijkstras algorithm with starting vertex v1 .
1
v3
v4
2
3
1
1
v5
3
3
v2
v1
Figure 2.14: Searching a directed house graph using Dijkstras algorithm.

2.7. Consider the graph in Figure 2.14. Choose any vertex as a starting vertex and run
Dijkstras algorithm over it. Now consider the undirected version of that digraph
and repeat the exercise.
2.8. For each vertex v of the graph in Figure 2.14, run breadth-first search over that
graph with v as the starting vertex. Repeat the exercise for depth-first search.
Compare the graphs resulting from the above exercises.
2.9. A list data structure can be used to manage vertices and edges. If L is a nonempty
list of vertices of a graph, we may want to know whether the graph contains a
particular vertex. We could search the list L, returning True if L contains the vertex
in question and False otherwise. Linear search is a simple searching algorithm.
Given an object E for which we want to search, we consider each element e of L in
turn and compare E to e. If at any point during our search we found a match, we
halt the algorithm and output an affirmative answer. Otherwise, we have scanned
through all elements of L and each of those elements do not match E. In this
case, linear search reports that E is not in L. Our discussion is summarized in
Algorithm 2.13.
(a) Implement Algorithm 2.13 in Sage and test your implementation using the
graphs presented in the figures of this chapter.
(b) What is the maximum number of comparisons during the running of Algorithm 2.13? What is the average number of comparisons?
(c) Why must the input list L be nonempty?
2.10. Binary search is a much faster searching algorithm than linear search. The binary
search algorithm assumes that its input list is ordered in some manner. For simplicity, we assume that the input list L consists of positive integers. The main idea
of binary search is to partition L into two halves: the left half and the right half.
Our task now is to determine whether the object E of interest is in the left half or
2.8. Problems
89
Algorithm 2.13: Linear search for lists.

Input: A nonempty list L of vertices or edges. An object E for which we want to
search in L.
Output: True if E is in L; False otherwise.
1
2
3
4
for each e L do
if E = e then
return True
return False
Algorithm 2.14: Binary search for lists of positive integers.

Input: A nonempty list L of positive integers. Elements of L are sorted in
nondecreasing order. An integer i for which we want to search in L.
Output: True if i is in L; False otherwise.
1
2
3
4
5
6
7
8
9
10
11
low 0
high |L| 1
while low high do
mid b low +2 high c
if i = L[mid] then
return True
if i < L[mid] then
high mid 1
else
low mid + 1
return False
90

the right half, and apply binary search recursively to the half in which E is located.
Algorithm 2.14 provides pseudocode of our discussion of binary search.
(a) Implement Algorithm 2.14 in Sage and test your implementation using the
graphs presented in the figures of this chapter.
(b) What is the worst case runtime of Algorithm 2.14? How does this compare
to the worst case runtime of linear search?
(c) Why must the input list L be sorted in nondecreasing order? Would Algorithm 2.14 work if L is sorted in nonincreasing order? If not, modify Algorithm 2.14 so that it works with an input list that is sorted in nonincreasing
order.
(d) Line 4 of Algorithm 2.14 uses the floor function to compute the index of the
middle value. Would binary search still work if we use the ceiling function
instead of the floor function?
(e) An improvement on the time complexity of binary search is to not blindly use
the middle value of the interval of interest, but to guess more precisely where
the target falls within this interval. Interpolation search uses this heuristic
to improve on the runtime of binary search. Provide an algorithm for interpolation search, analyze its worst-case runtime, and compare its theoretical
runtime efficiency with that of binary search (see pages 419420 in Knuth [120]
and pages 201202 in Sedgewick [165]).
2.11. Let G be a simple undirected graph having distance matrix D = [d(vi , vj )], where
d(vi , vj ) R denotes the shortest distance from vi V (G) to vj V (G). If
vi = vj , we set d(vi , vj ) = 0. For each pair of distinct vertices (vi , vj ), we have
d(vi , vj ) = d(vj , vi ). The i-j entry of D is also written as di,j and denotes the entry
in row i and column j.
(a) The total distance td(u) of a fixed vertex u V (G) is the sum of distances
from u to each vertex in G:
X
td(u) =
d(u, v).
vV (G)
If G is connected, i is the row index of vertex u in the distance matrix D, and

j is the column index of u in D, show that the total distance of u is
X
X
td(u) =
di,k =
dk,j .
(2.10)
k
(b) Let the vertices of G be labeled V = {v1 , v2 , . . . , vn }, where n = |V (G)| is

the order of G. The total distance td(G) of G is obtained by summing all the
d(vi , vj ) for i < j. If G is connected, show that the total distance of G is equal
to the sum of all entries in the upper (or lower) triangular of D:
!
X
X
1 XX
d(u, v) .
(2.11)
td(G) =
di,j =
di,j =
2
i<j
i>j
uV vV
Hence show that the total distance of G is equal to its Wiener number:
td(G) = W (G).
2.8. Problems
91
(c) Would equations (2.10) and (2.11) hold if G is not connected or directed?
2.12. The following result is from Yeh and Gutman [200]. Let G1 and G2 be graphs with
orders ni = |V (Gi )| and sizes mi = |E(Gi )|, respectively.
(a) If each of G1 and G2 is connected, show that the Wiener number of the
Cartesian product G1 G2 is
W (G1 G2 ) = n22 W (G1 ) + n21 W (G2 ).
(b) If G1 and G2 are arbitrary graphs, show that the Wiener number of the join
G1 + G2 is
W (G1 + G2 ) = n21 n1 + n22 n2 + n1 n2 m1 m2 .
2.13. The following results originally appeared in Entringer et al. [67] and independently
rediscovered many times since.
(a) If Pn is the path graph on n 0 vertices, show that the Wiener number of
Pn is W (Pn ) = 61 n(n2 1).
(b) If Cn is the cycle graph on n 0 vertices, show that the Wiener number of
Cn is
(1
n(n2 1), if n is odd,
8
W (Cn ) =
1 3
n,
if n is even.
8
(c) If Kn is the complete graph on n vertices, show that its Wiener number is
W (Kn ) = 21 n(n 1).
(d) Show that the Wiener number of the complete bipartite graph Km,n is
W (Km,n ) = mn + m(m 1) + n(n 1).
2.14. Consider the world map of major capital cities in Figure 2.15.
(a) Run breadth- and depth-first searches over the graph in Figure 2.15 and compare your results.
(b) Convert the graph in Figure 2.15 to a digraph as follows. Let 0 1 be a
fixed threshold probability and let V = {v1 , . . . , vn } be the vertex set of the
graph. For each edge vi vj , let 0 p 1 be its orientation probability and
define the directedness dir(vi , vj ) by
dir(vi , vj ) =
(
vi vj , if p ,
vj vi , otherwise.
That is, dir(vi , vj ) takes the endpoints of an undirected edge vi vj and returns
a directed version of this edge. The result is either the directed edge vi vj
or the directed edge vj vi . Use the above procedure to convert the graph of
Figure 2.15 to a digraph, and run breadth- and depth-first searches over the
resulting digraph.
92

(c) Table 2.6 lists distances in kilometers between the major capital cities shown
in Figure 2.15. Let those distances be the weights of the edges shown in Figure 2.15. Repeatedly run Dijkstras algorithm over this undirected, weighted
graph with each city as the start vertex. Use the procedure from the previous
exercise to obtain a directed version of the graph in Figure 2.15 and repeat
the current exercise with the resulting weighted digraph.
(d) Repeat the previous exercise, but use the Bellman-Ford algorithm instead of
Dijkstras algorithm. Compare the results you obtain using these two different
algorithms.
(e) Consider a weighted digraph version of the graph in Figure 2.15. Run the
Floyd-Roy-Warshall and Johnsons algorithms over the weighted digraph.
Compare the results output by these two algorithms to the results of the
previous exercise.
Lima
Washington DC
Ottawa
Pretoria
Berlin
New Delhi
Moscow
Figure 2.15: Major capital cities of the world.
Buenos Aires
Brasilia
Madrid
London
Bangkok
Beijing
Sydney
Tokyo
2.8. Problems
93
3154
Brasilia
Buenos Aires
Washington DC
Tokyo
Sydney
Pretoria
Ottawa
7540
1619
2103
6764
7906
3154
Lima
5915
5379
1261
929
London
8033
7288
1261
1866
Madrid
1619
5807
Moscow
7288
5796
3784
New Delhi
2908
734
5379
Ottawa
8033
7906
Pretoria
Table 2.6: Distances in kilometers between major world capital cities.
5796
Moscow
3784
1866
Madrid
New Delhi
929
London
Lima
2314
Berlin
2314
5807
Beijing
3282
Buenos Aires
2908
3282
Bangkok
Brasilia
Berlin
Beijing
Bangkok
Sydney
7540
2103
Tokyo
734
5915
6764
Washington DC
94
2.8. Problems
95
2.15. Various efficient search techniques exist that cater for special situations. Some of
these are covered in chapter 6 in Knuth [120] and chapters 1418 in Sedgewick [165].
Investigate an algorithm for and time complexity of trie search. Hashing techniques
can result in searches that run in O(1) time. Furthermore, hashing has important
applications outside of the searching problem, a case in point being cryptology.
Investigate how hashing can be used to speed up searches. For further information
on hashing and its application to cryptology, see Menezes et al. [142], Stinson [173],
or Trappe and Washington [179].
2.16. In addition to searching, there is the related problem of sorting a list according to
an ordering relation. If the given list L = [e1 , e2 , . . . , en ] consists of real numbers,
we want to order elements in nondecreasing order. Bubble sort is a basic sorting
algorithm that can be used to sort a list of real numbers, indeed any collection of
objects that can be ordered according to an ordering relation. During each pass
through the list L from left to right, we consider ei and its right neighbor ei+1 . If
ei ei+1 , then we move on to consider ei+1 and its right neighbor ei+2 . If ei > ei+1 ,
then we swap these two values around in the list and then move on to consider ei+1
and its right neighbor ei+2 . Each successive pass pushes to the right end an element
that is the next largest in comparison to the previous largest element pushed to
the right end. Hence the name bubble sort for the algorithm. Algorithm 2.15
summarizes our discussion.
Algorithm 2.15: Bubble sort.
Input: A list L of n > 1 elements that can be ordered using the less than or
equal to relation .
Output: The same list as L, but sorted in nondecreasing order.
1
2
3
4
5
for i n, n 1, . . . , 2 do
for j 2, 3, . . . , i do
if L[j 1] > L[j] then
swap the values of L[j 1] and L[j]
return L
(a) Analyze the worst-case runtime of Algorithm 2.15.

(b) Modify Algorithm 2.15 so that it sorts elements in nonincreasing order.
(c) Line 4 of Algorithm 2.15 is where elements are actually sorted. Swapping
the values of two elements is such a common task that sometimes we want
to perform the swap as efficiently as possible, i.e. using as few operations
as possible. A common way to swap the values of two elements a and b
is to create a temporary placeholder t and realize the swap as presented in
Algorithm 2.16. Some programming languages allow for swapping the values
of two elements without creating a temporary placeholder for an intermediary
value. Investigate how to realize this swapping method using a programming
language of your choice.
2.17. Selection sort is another simple sorting algorithm that works as follows. Let L =
[e1 , e2 , . . . , en ] be a list of elements that can be ordered according to the relation
, e.g. the ei can all be real numbers or integers. On the first scan of L
96
Algorithm 2.16: Swapping values using a temporary placeholder.

Input: Two objects a and b.
Output: The values of a and b swapped with each other.
1
2
3
ta
ab
bt
from left to right, among the elements L[2], . . . , L[n] we find the smallest element
and exchange it with L[1]. On the second scan, we find the smallest element
among L[3], . . . , L[n] and exchange that smallest element with L[2]. In general,
during the i-th scan we find the smallest element among L[i + 1], . . . , L[n] and
exchange that with L[i]. At the end of the i-th scan, the element L[i] is in its final
position and would not be processed again. When the index reaches i = n, the list
would have been sorted in nondecreasing order. The procedure is summarized in
Algorithm 2.17.
(a) Analyze the worst-case runtime of Algorithm 2.17 and compare your result to
the worst-case runtime of the bubble sort Algorithm 2.15.
(b) Modify Algorithm 2.17 to sort elements in nonincreasing order.
(c) Line 6 of Algorithm 2.17 assumes that among L[i+1], L[i+2], . . . , L[n] there is
a smallest element L[k] such that L[i] > L[k], hence we perform the swap. It is
possible that L[i] < L[k], obviating the need to carry out the value swapping.
Modify Algorithm 2.17 to take account of our discussion.
Algorithm 2.17: Selection sort.

Input: A list L of n > 1 elements that can be ordered using the relation .
Output: The same list as L, but sorted in nondecreasing order.
1
2
3
4
5
6
7
for i 1, 2, . . . , n 1 do
min i
for j i + 1, i + 2, . . . , n do
if L[j] < L[min] then
min j
swap the values of L[min] and L[i]
return L
2.18. In addition to bubble and selection sort, other algorithms exist whose runtime is
more efficient than these two basic sorting algorithms. Chapter 5 in Knuth [120] describes various efficient sorting techniques. See also chapters 813 in Sedgewick [165].
(a) Investigate and provide pseudocode for insertion sort and compare its runtime
efficiency with that of selection sort. Compare the similarities and differences
between insertion and selection sort.
(b) Shellsort is a variation on insertion sort that can speed up the runtime of
insertion sort. Describe and provide pseudocode for shellsort. Compare the
2.8. Problems
97
time complexity of shellsort with that of insertion sort. In what ways is

shellsort different from or similar to insertion sort?
(c) The quicksort algorithm due to C. A. R. Hoare [97] was published in 1962.
Describe and provide pseudocode for quicksort and compare its runtime complexity with the other sorting algorithms covered in this chapter.
2.19. Algorithm 2.3 uses breadth-first search to determine the connectivity of an undirected graph. Modify this algorithm to use depth-first search. How can Algorithm 2.3 be used or modified to test the connectivity of a digraph?
2.20. The following problem is known as the river crossing problem. A man, a goat,
a wolf, and a basket of cabbage are all on one side of a river. They have a boat
that could be used to cross to the other side of the river. The boat can only hold
at most two passengers, one of whom must be able to row the boat. One of the
two passengers must be the man and the other passenger can be either the goat,
the wolf, or the basket of cabbage. When crossing the river, if the man leaves the
wolf with the goat, the wolf would prey on the goat. If he leaves the goat with the
basket of cabbage, the goat would eat the cabbage. The objective is to cross the
river in such a way that the wolf has no chance of preying on the goat, nor that
the goat eat the cabbage.
(a) Let M , G, W , and C denote the man, the goat, the wolf, and the basket of
cabbage, respectively. Initially all four are on the left side of the river and none
of them are on the right side. Denote this by the ordered pair (M GW C, w),
which is called the initial state of the problem. When they have all crossed to
the right side of the river, the final state of the problem is (w, M GW C). The
underscore w means that neither M , G, W , nor C are on the corresponding
side of the river. List a finite sequence of moves to get from (M GW C, w) to
(w, M GW C). Draw your result as a digraph.
(b) In the digraph obtained from the previous exercise, let each edge of be of
unit weight. Find a shortest path from (M GW C, w) to (w, M GW C).
(c) Rowing from one side of the river to the other side is called a crossing. What
is the minimum number of crossings needed to get from (M GW C, w) to
(w, M GW C)?
2.21. Symbolic computation systems such as Magma, Maple, Mathematica, Maxima,
and Sage are able to read in a symbolic expression such as
(a + b)^2 - (a - b)^2
and determine whether or not the brackets match. A bracket is any of the following
characters:
( ) { } [ ]
A string S of characters is said to be balanced if any left bracket in S has a corresponding right bracket that is also in S. Furthermore, if there are k occurrences
of one type of left bracket, then there must be k occurrences of the corresponding
right bracket. The balanced bracket problem is concerned with determining whether
or not the brackets in S are balanced. Algorithm 2.18 contains a procedure to determine if the brackets in S are balanced, and if so return a list of positive integers
to indicate how the brackets match.
98

(a) Implement Algorithm 2.18 in Sage and test your implementation on various
strings containing brackets. Test your implementation on nonempty strings
without any brackets.
(b) Modify Algorithm 2.18 so that it returns True if the brackets of an input
string are balanced, and returns False otherwise.
(c) What is the worst-case runtime of Algorithm 2.18?
Algorithm 2.18: A brackets parser.

Input: A nonempty string S of characters.
Output: A list L of positive integers indicating how the brackets match. If the
brackets are not balanced, return the empty string .
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
L []
T empty stack
c1
n |S|
for i 0, 1, . . . , n do
if S[i + 1] is a left bracket then
append(L, c)
push (S[i + 1], c) onto T
cc+1
if S[i + 1] is a right bracket then
if T is empty then
return
(left, d) pop(T )
if left matches S[i + 1] then
append(L, d)
else
return
if T is empty then
return L
return
2.22. An arithmetic expression written in the form a + b is said to be in infix notation

because the operator is in between the operands. The same expression can also be
written in reverse Polish notation (or postfix notation) as
ab+
with the operator following its two operands. Given an arithmetic expression A =
e0 e1 en written in reverse Polish notation, we can use the stack data structure
to evaluate the expression. Let P = [e0 , e1 , . . . , en ] be the stack representation of
A, where traversing P from left to right we are moving from the top of the stack
to the bottom of the stack. We call P the Polish stack and the stack E containing
intermediate results the evaluation stack. While P is not empty, pop the Polish
stack and assign the extracted result to x. If x is an operator, we pop the evaluation
stack twice: the result of the first pop is assigned to b and the result of the second
2.8. Problems
99
pop is assigned to a. Compute the infix expression a x b and push the result onto
E. However, if x is an operand, we push x onto E. Iterate the above process until
P is empty, at which point the top of E contains the evaluation of A. Refer to
Algorithm 2.19 for pseudocode of the above discussion.
(a) Prove the correctness of Algorithm 2.19.
(b) What is the worst-case runtime of Algorithm 2.19?
(c) Modify Algorithm 2.19 to support the exponentiation operator.
Algorithm 2.19: Evaluate arithmetic expressions in reverse Polish notation.
Input: A Polish stack P containing an arithmetic expression in reverse Polish
notation.
Output: An evaluation of the arithmetic expression represented by P .
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
E empty stack
v NULL
while P is not empty do
x pop(P )
if x is an operator then
b pop(E)
a pop(E)
if x is addition operator then
v a+b
else if x is subtraction operator then
v ab
else if x is multiplication operator then
v ab
else if x is division operator then
v a/b
else
exit algorithm with error
push(E, v)
else
push(E, x)
v pop(E)
return v
2.23. Figure 2.5 provides a knights tour for the knight piece with initial position as
in Figure 2.5(a). By rotating the chessboard in Figure 2.5(b) by 90n degrees for
positive integer values of n, we obtain another knights tour that, when represented
as a graph, is isomorphic to the graph in Figure 2.5(c).
(a) At the beginning of the 18th century, de Montmort and de Moivre provided
the following strategy [11, p.176] to solve the knights tour problem on an
8 8 chessboard. Divide the board into an inner 4 4 square and an outer
shell of two squares deep, as shown in Figure 2.16(a). Place a knight on a
square in the outer shell and move the knight piece around that shell, always
100

in the same direction, so as to visit each square in the outer shell. After that,
move into the inner square and solve the knights tour problem for the 4 4
case. Apply this strategy to solve the knights tour problem with the initial
position as in Figure 2.16(b).
(b) Use the Montmort-Moivre strategy to obtain a knights tour, starting at the
position of the black-filled node in the outer shell in Figure 2.5(b).
(c) A re-entrant or closed knights tour is a knights tour that starts and ends
at the same square. Find re-entrant knights tours with initial positions as in
Figure 2.17.
(d) Devise a backtracking algorithm to solve the knights tour problem on an nn
chessboard for n > 3.
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0m
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
(a) A 4 4 inner square.
(b) Initial position in the outer shell.
Figure 2.16: De Montmort and de Moivres solution strategy for the 8 8 knights tour
problem.
0Z0Z0Z
Z0Z0Z0
0Z0Z0Z
Z0Z0Z0
0Z0Z0Z
m0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0m0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
0Z0Z0Z0Z
Z0Z0Z0Z0
(a) A 6 6 chessboard.
(b) An 8 8 chessboard.
Figure 2.17: Initial positions of re-entrant knights tours.

2.24. The n-queens problem is concerned with the placement of n queens on an n n
chessboard such that no two queens can attack each other. Two queens can attack
2.8. Problems
101
0L0Z
Z0ZQ
QZ0Z
Z0L0
0ZQZ0Z0Z
Z0Z0Z0ZQ
0Z0L0Z0Z
Z0Z0Z0L0
QZ0Z0Z0Z
Z0Z0ZQZ0
0L0Z0Z0Z
Z0Z0L0Z0
(a) n = 4
(b) n = 8
Figure 2.18: Solutions of the n-queens problem for n = 4, 8.

each other if they are in the same row, column, diagonal, or antidiagonal of the
chessboard. The trivial case n = 1 is easily solved by placing the one queen in the
only given position. There are no solutions for the cases n = 2, 3. Solutions for the
cases n = 4, 8 are shown in Figure 2.18. Devise a backtracking algorithm to solve
the n-queens problem for the case where n > 3. See Bell and Stevens [20] for a
survey of the n-queens problem and its solutions.
2.25. Hampton Court Palace in England is well-known for its maze of hedges. Figure 2.19
shows a maze and its graph representation; the figure is adapted from page 434 in
Sedgewick [165]. To obtain the graph representation, we use a vertex to represent
an intersection in the maze. An edge joining two vertices represents a path from
one intersection to another.
(a) Suppose the entrance to the maze is represented by the lower-left black-filled
vertex in Figure 2.19(b) and the exit is the upper-right black-filled vertex.
Solve the maze by providing a path from the entrance to the exit.
(b) Repeat the previous exercise for each pair of distinct vertices, letting one
vertex of the pair be the entrance and the other vertex the exit.
(c) What is the diameter of the graph in Figure 2.19(b)?
(d) Investigate algorithms for generating and solving mazes.
2.26. For each of the algorithms below: (i) justify whether or not it can be applied
to multigraphs or multidigraphs; (ii) if not, modify the algorithm so that it is
applicable to multigraphs or multidigraphs.
(a) Breadth-first search Algorithm 2.1.
(b) Depth-first search Algorithm 2.2.
(c) Graph connectivity test Algorithm 2.3.
(d) General shortest path Algorithm 2.4.
(e) Dijkstras Algorithm 2.5.
102
(a)
(b)
Figure 2.19: A maze and its graph representation.

(f) The Bellman-Ford Algorithms 2.6 and 2.7.
(g) The Floyd-Roy-Warshall Algorithm 2.8.
(h) The transitive closure Algorithm 2.9.
(i) Johnsons Algorithm 2.10.
(a) 2 2
(b) 3 3
(c) 4 4
Figure 2.20: Grid graphs for n = 2, 3, 4.

2.27. Let n be a positive integer. An n n grid graph is a graph on the Euclidean plane,
where each vertex is an ordered pair from Z Z. In particular, the vertices are
ordered pairs (i, j) Z Z such that
0 i, j < n.
(2.12)
Each vertex (i, j) is adjacent to any of the following vertices provided that expression (2.12) is satisfied: the vertex (i 1, j) immediately to its left, the vertex
(i + 1, j) immediately to its right, the vertex (i, j + 1) immediately above it, or
the vertex (i, j 1) immediately below it. Figure 2.20 illustrates some examples
of grid graphs. The 1 1 grid graph is the trivial graph K1 .
(a) Fix a positive integer n > 1. Describe and provide pseudocode of an algorithm
to generate all nonisomorphic n n grid graphs. What is the worst-case
runtime of your algorithm?
(b) How many n n grid graphs are there? How many of those graphs are
nonisomorphic to each other?
2.8. Problems
103
(c) Describe and provide pseudocode of an algorithm to generate a random n n

grid graph. Analyze the worst-case runtime of your algorithm.
(d) Extend the grid graph by allowing edges to be diagonals. That is, a vertex
(i, j) can also be adjacent to any of the following vertices so long as expression (2.12) holds: (i 1, j 1), (i 1, j + 1), (i + 1, j + 1), (i + 1, j 1).
With this extension, repeat the previous exercises.
2.28. Let G = (V, E) be a digraph with integer weight function w : E Z\{0},
where either w(e) > 0 or w(e) < 0 for each e E. Yamada and Kinoshita [198]
provide a divide-and-conquer algorithm to enumerate all the negative cycles in
G. Investigate the divide and conquer technique for algorithm design. Describe
and provide pseudocode of the Yamada-Kinoshita algorithm. Analyze its runtime
complexity and prove the correctness of the algorithm.
Chapter 3
Trees and Forests
In section 1.2.1, we briefly touched upon trees and provided examples of how trees could
be used to model hierarchical structures. This chapter provides an in-depth study of
trees, their properties, and various applications. After defining trees and related concepts in section 3.1, we then present various basic properties of trees in section 3.2.
Each connected graph G has an underlying subgraph called a spanning tree that contains all the vertices of G. Spanning trees are discussed in section 3.3 together with
various common algorithms for finding spanning trees. We then discuss binary trees in
section 3.4, followed by an application of binary trees to coding theory in section 3.5.
Whereas breadth- and depth-first searches are general methods for traversing a graph,
trees require specialized techniques in order to visit their vertices, a topic that is taken
up in section 3.6.
3.1
Definitions and examples

I think that I shall never see
A poem lovely as a tree.
Joyce Kilmer, Trees and Other Poems, 1914, Trees
Recall that a path in a graph G = (V, E) whose start and end vertices are the same is
called a cycle. We say G is acyclic, or a forest, if it has no cycles. In a forest, a vertex
of degree one is called an endpoint or a leaf . Any vertex that is not a leaf is called an
104
3.1. Definitions and examples
105
internal vertex. A connected forest is a tree. In other words, a tree is a graph without
cycles and each edge is a bridge. A forest can also be considered as a collection of trees.
A rooted tree T is a tree with a specified root vertex v0 , i.e. exactly one vertex has
been specially designated as the root of T . However, if G is a rooted tree with root
vertex v0 having degree one, then by convention we do not call v0 an endpoint or a leaf.
The depth depth(v) of a vertex v in T is its distance from the root. The height height(T )
of T is the length of a longest path starting from the root vertex, i.e. the height is the
maximum depth among all vertices of T . It follows by definition that depth(v) = 0 if and
only if v is the root of T , height(T ) = 0 if and only if T is the trivial graph, depth(v) 0
for all v V (T ), and height(T ) diam(T ).
The Unix, in particular Linux, filesystem hierarchy can be viewed as a tree (see
Figure 3.1). As shown in Figure 3.1, the root vertex is designated with the forward
slash, which is also referred to as the root directory. Other examples of trees include the
organism classification tree in Figure 3.2, the family tree in Figure 3.3, and the expression
tree in Figure 3.4.
A directed tree is a digraph which would be a tree if the directions on the edges
were ignored. A rooted tree can be regarded as a directed tree since we can imagine an
edge uv for u, v V being directed from u to v if and only if v is further away from v0
than u is. If uv is an edge in a rooted tree, then we call v a child vertex with parent u.
Directed trees are pervasive in theoretical computer science, as they are useful structures
for describing algorithms and relationships between objects in certain datasets.
/
bin
etc
home
lib
anne
sam
...
acyclic
diff
proc
opt
bin
dot
tmp
include
gc
neato
...
usr
local
share
src
...
...
Figure 3.1: The Linux filesystem hierarchy.

An ordered tree is a rooted tree for which an ordering is specified for the children of
each vertex. An n-ary tree is a rooted tree for which each vertex that is not a leaf has
at most n children. The case n = 2 are called binary trees. An n-ary tree is said to
be complete if each of its internal vertices has exactly n children and all leaves have the
same depth. A spanning tree of a connected, undirected graph G is a subgraph that is
a tree and containing all vertices of G.
Example 3.1. Consider the 4 4 grid graph with 16 vertices and 24 edges. Two
examples of a spanning tree are given in Figure 3.5 by using a darker line shading for its
edges.
Example 3.2. For n = 1, . . . , 6, how many distinct (nonisomorphic) trees are there of
order n? Construct all such trees for each n.
106
Chapter 3. Trees and Forests
organism
plant
animal
tree
flower
invertebrate
evergreen
deciduous
vetebrate
bird
finch
mammal
sparrow
rosella
dolphin
human
whale
Figure 3.2: Classification tree of organisms.
Nikolaus senior
Jacob
Nicolaus
Johann
Nicolaus I
Nicolaus II
Daniel
Johann II
Johann III
Daniel II
Jakob II
Figure 3.3: Bernoulli family tree of mathematicians.
Figure 3.4: Expression tree for the perfect square a2 + 2ab + b2 .
107
(a)
(b)
Figure 3.5: Two spanning trees for the 4 4 grid graph.

Solution. For n = 1, there is only one tree of order 1, i.e. K1 . The same is true for n = 2
and n = 3, where the required trees are P2 and P3 , respectively (see Figure 3.6). We
have two trees of order n = 4 (see Figure 3.7), three of order n = 5 (see Figure 3.8), and
six of order n = 6 (see Figure 3.9).
(a) n = 1
(b) n = 2
(c) n = 3
Figure 3.6: All distinct trees of order n = 1, 2, 3.
(a)
(b)
Figure 3.7: All distinct trees of order n = 4.

Example 3.3. Let T = (V, E) be a tree with vertex set
V = {a, b, c, d, e, f, v, w, x, y, z}
edge set
E = {va, vw, wx, wy, xb, xc, yd, yz, ze, zf }
and root vertex v. Verify that T is a binary tree. Suppose that x is the root of the branch
we want to remove from T . Find all children of x and cut off the branch rooted at x from
T . Is the resulting graph also a binary tree?
108
(a)
(b)
(c)
(a)
(b)
(c)
(d)
(f)
(e)
109
Solution. We construct the tree T in Sage as follows:

sage :
...
...
...
sage :
...
a c b
sage :
...
wy wx
T = DiGraph ({
" v " :[ " a " ," w " ] , " w " :[ " x " ," y " ] ,
" x " :[ " c " ," b " ] , " y " :[ " z " ," d " ] ,
" z " :[ " f " ," e " ]})
for v in T . vertex_iterator ():
print ( v ) ,
e d f w v y x z
for e in T . edge_iterator ():
print ( " % s % s " % ( e [0] , e [1])) ,
va vw yd yz xc xb ze zf
Each vertex in a binary tree has at most 2 children. Use this definition to test whether
or not a graph is a binary tree.
sage : T . is_tree ()
True
sage : def is_bintree1 ( G ):
...
for v in G . vertex_iterator ():
...
if len ( G . neighbors_out ( v )) > 2:
...
return False
...
return True
sage : is_bintree1 ( T )
True
Heres another way to test for binary trees. Let T be an undirected rooted tree. Each
vertex in a binary tree has a maximum degree of 3. If the root vertex is the only vertex
with degree 2, then T is a binary tree. (Problem 3.5 asks you to prove this result.) We
can use this test because the root vertex v of T is the only vertex with two children.
sage : def is_bintree2 ( G ):
...
if G . is_tree () and max ( G . degree ()) == 3 and G . degree (). count (2) == 1:
...
return True
...
return False
sage : is_bintree2 ( T . to_undirected ())
True
As x is the root vertex of the branch we want to cut off from T , we could use breadthor depth-first search to determine all the children of x. We then delete x and its children
from T .
sage :
sage :
sage :
[ x ,
sage :
sage :
...
a e d
sage :
...
wy va
sage :
sage :
[ x ,
sage :
sage :
...
a e d
sage :
...
wy va
T2 = copy ( T )
# using breadth - first search
V = list ( T . breadth_first_search ( " x " )); V
c , b ]
T . delete_vertices ( V )
for v in T . vertex_iterator ():
print ( v ) ,
f w v y z
for e in T . edge_iterator ():
print ( " % s % s " % ( e [0] , e [1])) ,
vw yd yz ze zf
# using depth - first search
V = list ( T2 . depth_first_search ( " x " )); V
b , c ]
T2 . delete_vertices ( V )
for v in T2 . vertex_iterator ():
print ( v ) ,
f w v y z
for e in T2 . edge_iterator ():
print ( " % s % s " % ( e [0] , e [1])) ,
vw yd yz ze zf
The resulting graph T is a binary tree because each vertex has at most two children.
sage : T
Digraph on 8 vertices
sage : is_bintree1 ( T )
True
Notice that the test defined in the function is_bintree2 can no longer be used to test
whether or not T is a binary tree, because T now has two vertices, i.e. v and w, each of
110
which has degree 2.

Consider again the organism classification tree in Figure 3.2. We can view the vertex
organism as the root of the tree and having two children. The first branch of organism is the subtree rooted at plant and its second branch is the subtree rooted
at animal. We form the complete tree by joining an edge between organism and
plant, and an edge between organism and animal. The subtree rooted at plant
can be constructed in the same manner. The first branch of this subtree is the subtree
rooted at tree and the second branch is the subtree rooted at flower. To construct
the subtree rooted at plant, we join an edge between plant and tree, and an
edge between plant and flower. The other subtrees of the tree in Figure 3.2 can be
constructed using the above recursive procedure.
In general, the recursive construction in Theorem 3.4 provides an alternative way
to define trees. We say construction because it provides an algorithm to construct a
tree, as opposed to the nonconstructive definition presented earlier in this section, where
we defined the conditions under which a graph qualifies as a tree without presenting a
procedure to construct a tree. Furthermore, we say recursive since a larger tree can be
viewed as being constructed from smaller trees, i.e. join up existing trees to obtain a
new tree. The recursive construction of trees as presented in Theorem 3.4 is illustrated
in Figure 3.10.
Theorem 3.4. Recursive construction of trees. An isolated vertex is a tree. That
single vertex is the root of the tree. Given a collection T1 , T2 , . . . , Tn of n > 0 trees,
construct a new tree as follows:
1. Let T be a tree having exactly the one vertex v, which is the root of T .
2. Let vi be the root of the tree Ti .
3. For i = 1, 2, . . . , n, add the edge vvi to T and add Ti to T . That is, each vi is now
a child of v.
The result is the tree T rooted at v with vertex set
V (T ) = {v}
and edge set
E(T ) =
[
i
[
i
V (Ti )

{vvi } E(Ti ) .
The following game is a variant of the Shannon switching game, due to Edmonds and
Lehman. We follow the description in Oxleys survey [156]. Recall that a minimal edge
cut of a graph is also called a bond of the graph. The following two-person game is played
on a connected graph G = (V, E). Two players Alice and Bob alternately tag elements
of E. Alices goal is to tag the edges of a spanning tree, while Bobs goal is to tag the
edges of a bond. If we think of this game in terms of a communication network, then
Bobs goal is to separate the network into pieces that are no longer connected to each
other, while Alice is aiming to reinforce edges of the network to prevent their destruction.
Each move for Bob consists of destroying one edge, while each move for Alice involves
securing an edge against destruction. The next result characterizes winning strategies
on G. The full proof can be found in Oxley [156]. See Rasmussen [160] for optimization
algorithms for solving similar games.
3.2. Properties of trees
111
v
...
T1
T2
Tn
Figure 3.10: Recursive construction of a tree.

Theorem 3.5. The following statements are equivalent for a connected graph G =
(V, E).
1. Bob plays first and Alice can win against all possible strategies of Bob.
2. The graph G has 2 edge-disjoint spanning trees.
3. For all partitions P of the vertex set V , the number of edges of G that join vertices
in different classes of the partition is at least 2(|P | 1).
3.2
Properties of trees
All theory, dear friend, is grey, but the golden tree of actual life springs ever green.
Johann Wolfgang von Goethe, Faust, part 1, 1808
By Theorem 1.25, each edge of a tree is a bridge. Removing any edge of a tree partitions
the tree into two components, each of which is a subtree of the original tree. The following
results provide further basic characterizations of trees.
Theorem 3.6. Any tree T = (V, E) has size |E| = |V | 1.
Proof. This follows by induction on the number of vertices. By definition, a tree has
no cycles. We need to show that any tree T = (V, E) has size |E| = |V | 1. For the
base case |V | = 1, there are no edges. Assume for induction that the result holds for
all integers less than or equal to k 2. Let T = (V, E) be a tree having k + 1 vertices.
Remove an edge from T , but not the vertices it is incident to. This disconnects T into
two components T1 = (V1 , E1 ) and T2 = (V2 , E2 ), where |E| = |E1 | + |E2 | + 1 and
|V | = |V1 | + |V2 | (and possibly one of the Ei is empty). Each Ti is a tree satisfying the
conditions of the induction hypothesis. Therefore,
|E| = |E1 | + |E2 | + 1
= |V1 | 1 + |V2 | 1 + 1
= |V | 1.
as required.
112
Corollary 3.7. If T = (V, E) is a graph of order |V | = n, then the following are

equivalent:
1. T is a tree.
2. T contains no cycles and has n 1 edges.
3. T is connected and has n 1 edges.
4. Every edge of T is a cut set.
Proof. (1) = (2): This holds by definition of trees and Theorem 3.6.
(2) = (3): If T = (V, E) has k connected components then it is a disjoint union
of trees Ti = (Vi , Ei ), i = 1, 2, . . . , k, for some k. By part (2), each of these satisfy
|Ei | = |Vi | 1
so
|E| =
=
k
X
i=1
k
X
i=1
|Ei |
|Vi | k
= |V | k.
This contradicts part (2) unless k = 1. Therefore, T is connected.
(3) = (4): If removing an edge e E leaves T = (V, E) connected then T 0 =
(V, E 0 ) is a tree, where E 0 = Ee. However, this means that |E 0 | = |E|1 = |V |11 =
|V | 2, which contradicts part (3). Therefore e is a cut set.
(4) = (1): From part (2) we know that T has no cycles and from part (3) we
know that T is connected. Conclude by the definition of trees that T is a tree.
Theorem 3.8. Let T = (V, E) be a tree and let u, v V be distinct vertices. Then T
has exactly one u-v path.
Proof. Suppose for contradiction that
P : v0 = u, v1 , v2 , . . . , vk = v
and
Q : w0 = u, w1 , w2 , . . . , w` = v
are two distinct u-v paths. Then P and Q has a common vertex x, which is possibly
x = u. For some i 0 and some j 0 we have vi = x = wj , but vi+1 6= wj+1 . Let
y be the first vertex after x such that y belongs to both P and Q. (It is possible that
y = v.) We now have two distinct x-y paths that have only x and y in common. Taken
together, these two x-y paths result in a cycle, contradicting our hypothesis that T is a
tree. Therefore T has only one u-v path.
Theorem 3.9. If T = (V, E) is a graph then the following are equivalent:
3.2. Properties of trees
113
1. T is a tree.
2. For any new edge e, the join T + e has exactly one cycle.
Proof. (1) = (2): Let e = uv be a new edge connecting u, v V . Suppose that
P : v0 = w, v1 , v2 , . . . , vk = w
and
P 0 : v00 = w, v10 , v20 , . . . , v`0 = w
are two cycles in T + e. If either P or P 0 does not contain e, say P does not contain e,
then P is a cycle in T . Let u = v0 and let v = v1 . The edge (v0 = w, v1 ) is a u-v path
and the sequence v = v1 , v2 , . . . , vk = w = u taken in reverse order is another u-v path.
This contradicts Theorem 3.8.
We may now suppose that P and P 0 both contain e. Then P contains a subpath
P0 = P e (which is not closed) that is the same as P except it lacks the edge from u
to v. Likewise, P 0 contains a subpath P00 = P 0 e (which is not closed) that is the same
as P 0 except it lacks the edge from u to v. By Theorem 3.8, these u-v paths P0 and P00
must be the same. This forces P and P 0 to be the same, which proves part (2).
(2) = (1): Part (2) implies that T is acyclic. (Otherwise, it is trivial to make
two cycles by adding an extra edge.) We must show T is connected. Suppose T is
disconnected. Let u be a vertex in one component, T1 say, of T and v a vertex in another
component, T2 say, of T . Adding the edge e = uv does not create a cycle (if it did then
T1 and T2 would not be disjoint), which contradicts part (2).
Taking together the results in this section, we have the following characterizations of
trees.
Theorem 3.10. Basic characterizations of trees. If T = (V, E) is a graph with n
vertices, then the following statements are equivalent:
1. T is a tree.
2. T contains no cycles and has n 1 edges.
3. T is connected and has n 1 edges.
4. Every edge of T is a cut set.
5. For any pair of distinct vertices u, v V , there is exactly one u-v path.
6. For any new edge e, the join T + e has exactly one cycle.
Let G = (V1 , E1 ) be a graph and T = (V2 , E2 ) a subgraph of G that is a tree. As in
part (6) of Theorem 3.10, we see that adding just one edge in E1 E2 to T will create
a unique cycle in G. Such a cycle is called a fundamental cycle of G. The set of such
fundamental cycles of G depends on T .
The following result essentially says that if a tree has at least one edge, then the tree
has at least two vertices each of which has degree one. In other words, each tree of order
2 has at least two pendants.
Theorem 3.11. Every nontrivial tree has at least two leaves.
114
Proof. Let T be a nontrivial tree of order m and size n. Consider the degree sequence
d1 , d2 , . . . , dm of T where d1 d2 dm . As T is nontrivial and connected, then
m 2 and di 1 for i = 1, 2, . . . , m. If T has less than two leaves, then d1 1 and
di 2 for 2 i m, hence
m
X
i=1
di 1 + 2(m 1) = 2m 1.
(3.1)
But by Theorems 1.7 and 3.6, we have

m
X
i=1
di = 2n = 2(m 1) = 2m 2
which contradicts inequality (3.1). Conclude that T has at least two leaves.
Theorem 3.12. If T is a tree of order m and G is a graph with minimum degree
(G) m 1, then T is isomorphic to a subgraph of G.
Proof. Use an inductive argument on the number of vertices. The result holds for m = 1
because K1 is a subgraph of every nontrivial graph. The result also holds for m = 2
since K2 is a subgraph of any graph with at least one edge.
Let m 3, let T1 be a tree of order m 1, and let H be a graph with (H) m 2.
Assume for induction that T1 is isomorphic to a subgraph of H. We need to show that
if T is a tree of order m and G is a graph with (G) m 1, then T is isomorphic to a
subgraph of G. Towards that end, consider a leaf v of T and let u be a vertex of T such
that u is adjacent to v. Then T v is a tree of order m 1 and (G) m 1 > m 2.
Apply the inductive hypothesis to see that T v is isomorphic to a subgraph T 0 of G.
Let u0 be the vertex of T 0 that corresponds to the vertex u of T under an isomorphism.
Since deg(u0 ) m 1 and T 0 has m 2 vertices distinct from u0 , it follows that u0 is
adjacent to some w V (G) such that w
/ V (T 0 ). Therefore T is isomorphic to the
graph obtained by adding the edge u0 w to T 0 .
Example 3.13. Consider a positive integer n. The Euler phi function (n) counts the
number of integers a, with 1 a n, such that gcd(a, n) = 1. The Euler phi sequence
of n is obtained by repeatedly iterating (n) with initial iteration value n. Continue
on iterating and stop when the output of (k ) is 1, for some positive integer k . The
number of terms generated by the iteration, including the initial iteration value n and
the final value of 1, is the length of (n).
(a) Let s0 = n, s1 , s2 , . . . , sk = 1 be the Euler phi sequence of n and produce a digraph G
of this sequence as follows. The vertex set of G is V = {s0 = n, s1 , s2 , . . . , sk = 1}
and the edge set of G is E = {si si+1 | 0 i < k}. Produce the digraphs of the Euler
phi sequences of 15, 22, 33, 35, 69, and 72. Construct the union of all such digraphs
and describe the resulting graph structure.
(b) For each n = 1, 2, . . . , 1000, compute the length of (n) and plot the pairs (n, (n))
on one set of axes.
Solution. The Euler phi sequence of 15 is
15,
(15) = 8,
(8) = 4,
(4) = 2,
(2) = 1.
3.3. Minimum spanning trees
115
The Euler phi sequences of 22, 33, 35, 69, and 72 can be similarly computed to obtain
their respective digraph representations. The union of all such digraphs is a directed tree
rooted at 1, as shown in Figure 3.11(a). Figure 3.11(b) shows a scatterplot of n versus
the length of (n).
12
4
15
10
20
33
24
44
35
22
72
length of (n)
10
8
6
4
2
0
200
400
800
1,000
69
(a)
600
(b)
Figure 3.11: Union of digraphs of Euler phi sequences and scatterplot.
3.3
Minimum spanning trees
Suppose we want to design an electronic circuit connecting several components. If these

components represent the vertices of a graph and a wire connecting two components
represents an edge of the graph, then for economical reasons we will want to connect the
components together using the least amount of wire. The problem essentially amounts
to finding a minimum spanning tree in the graph containing these vertices.
But what is a spanning tree? We can characterize a spanning tree in several ways,
each leading to an algorithm for constructing a spanning tree. Let G be a connected
graph and let T be a subgraph of G. If T is a tree that contains all the vertices of
G, then T is called a spanning tree of G. We can think of T as a tree that is also an
edge-deletion subgraph of G. That is, we start with a connected graph G and delete an
edge from G such that the resulting edge-deletion subgraph T1 is still connected. If T1 is
a tree, then we have obtained a spanning tree of G. Otherwise, we delete an edge from
T1 to obtain an edge-deletion subgraph T2 that is still connected. If T2 is a tree, then
we are done. Otherwise, we repeat the above procedure until we obtain an edge-deletion
subgraph Tk of G such that Tk is connected, Tk is a tree, and it contains all vertices
of G. Each edge removal does not decrease the number of vertices and must also leave
116
the resulting edge-deletion subgraph connected. Thus eventually the above procedure
results in a spanning tree of G. Our discussion is summarized in Algorithm 3.1.
Algorithm 3.1: Randomized spanning tree construction.
Input: A connected graph G.
Output: A spanning tree of G.
1
2
3
4
5
6
T G
while T is not a tree do
e random edge of T
if T e is connected then
T T e
return T
Another characterization of a spanning tree T of a connected graph G is that T is a

maximal set of edges of G that contains no cycle. Kruskals algorithm (see section 3.3.1)
exploits this condition to construct a minimum spanning tree (MST). A minimum spanning tree is a spanning tree of a weighted graph having lowest total weight among all
possible spanning trees of the graph. A third characterization of a spanning tree is that
it is a minimal set of edges that connect all vertices, a characterization that results in
yet another algorithm called Prims algorithm (see section 3.3.2) for constructing minimum spanning trees. The task of determining a minimum spanning tree in a connected
weighted graph is called the minimum spanning tree problem. As early as 1926, Otakar
Bor
uvka stated [31, 32] this problem and offered a solution now known as Bor
uvkas
algorithm (see section 3.3.3). See Graham and Hell [85] for a history of the minimum
spanning tree problem.
3.3.1
Kruskals algorithm
In 1956, Joseph B. Kruskal published [123] a procedure for constructing a minimum spanning tree of a connected weighted graph G = (V, E). Now known as Kruskals
algorithm,

with a suitable implementation the procedure runs in O |E| log |E| time. Variants
of Kruskals algorithm include the algorithm by Prim [159] and that by Loberman and
Weinberger [135].
Kruskals algorithm belongs to the class of greedy algorithms. As will be explained
below, when constructing a minimum spanning tree Kruskals algorithm considers only
the edge having minimum weight among all available edges. Given a weighted nontrivial
graph G = (V, E) that is connected, let w : E R be the weight function of G. The
first stage is creating a skeleton of the tree T that is initially set to be a graph without
edges, i.e. T = (V, ). The next stage involves sorting the edges of G by weights in
nondecreasing order. In other words, we label the edges of G as follows:
E = {e1 , e2 , . . . , en }
where n = |E| and w(e1 ) w(e2 ) w(en ). Now consider each edge ei for
i = 1, 2, . . . , n. We add ei to the edge set of T provided that ei does not result in T
having a cycle. The only way adding ei = ui vi to T would create a cycle is if both ui and
vi were endpoints of edges (not necessarily distinct) in the same connected component
of T . As long as the acyclic condition holds with the addition of a new edge to T , we
117
add that new edge. Following the acyclic test, we also test that the (updated) graph
T is a tree of G. As G is a graph of order |V |, apply Theorem 3.10 to see that if T
has size |V | 1, then it is a spanning tree of G. Algorithm 3.2 provides pseudocode of
our discussion of Kruskals algorithm. When the algorithm halts, it returns a minimum
spanning tree of G. The correctness of Algorithm 3.2 is proven in Theorem 3.14.
Algorithm 3.2: Kruskals algorithm.
Input: A connected weighted graph G = (V, E) with weight function w.
Output: A minimum spanning tree of G.
1
2
3
4
5
6
7
8
m |V |
T
sort E = {e1 , e2 , . . . , en } by weights so that w(e1 ) w(w2 ) w(en )
for i 1, 2, . . . , n do
if ei
/ E(T ) and T {ei } is acyclic then
T T {ei }
if |T | = m 1 then
return T
Theorem 3.14. Correctness of Algorithm 3.2. If G is a nontrivial connected

weighted graph, then Algorithm 3.2 outputs a minimum spanning tree of G.
Proof. Let G be a nontrivial connected graph of order m and having weight function w.
Let T be a subgraph of G produced by Kruskals algorithm 3.2. By construction, T is a
spanning tree of G with
E(T ) = {e1 , e2 , . . . , em1 }
where w(e1 ) w(e2 ) w(em1 ) so that the total weight of T is
w(T ) =
m1
X
w(ei ).
i=1
Suppose for contradiction that T is not a minimum spanning tree of G. Among all the
minimum spanning trees of G, let H be a minimum spanning tree of G such that H has
the most number of edges in common with T . As T and H are distinct subgraphs of G,
then T has at least an edge not belonging to H. Let ei E(T ) be the first edge not in
H. Construct the graph G0 = H + ei obtained by adding the edge ei to H. Note that
G0 has exactly one cycle C. Since T is acyclic, there exists an edge e0 E(C) such that
e0 is not in T . Construct the graph T0 = G0 e0 obtained by deleting the edge e0 from
G0 . Then T0 is a spanning tree of G with
w(T0 ) = w(H) + w(ei ) w(e0 )
and w(H) w(T0 ) and hence w(e0 ) w(ei ). By Kruskals algorithm 3.2, ei is an edge of
minimum weight such that {e1 , e2 , . . . , ei1 } {ei } is acyclic. Furthermore, the subgraph
{e1 , e2 , . . . , ei1 , e0 } of H is acyclic. Thus we have w(ei ) = w(e0 ) and w(T0 ) = w(H) and
so T is a minimum spanning tree of G. By construction, T0 has more edges in common
with T than H has with T , in contradiction of our hypothesis.
118
def kruskal ( G ):
"""
Implements Kruskal s algorithm to compute a MST of a graph .
INPUT :
G - a connected edge - weighted graph or digraph
whose vertices are assumed to be 0 , 1 , .... , n -1.
OUTPUT :
T - a minimum weight spanning tree .
If G is not explicitly edge - weighted then the algorithm
assumes all edge weights are 1. The tree T returned is
a weighted graph , even if G is not .
EXAMPLES :
sage : A = matrix ([[0 ,1 ,2 ,3] ,[0 ,0 ,2 ,1] ,[0 ,0 ,0 ,3] ,[0 ,0 ,0 ,0]])
sage : G = DiGraph (A , format = " adjacency_matrix " , weighted = True )
sage : TE = kruskal ( G ); TE . edges ()
[(0 , 1 , 1) , (0 , 2 , 2) , (1 , 3 , 1)]
sage : G . edges ()
[(0 , 1 , 1) , (0 , 2 , 2) , (0 , 3 , 3) , (1 , 2 , 2) , (1 , 3 , 1) , (2 , 3 , 3)]
sage : G = graphs . PetersenGraph ()
sage : TE = kruskal ( G ); TE . edges ()
[(0 , 1 , 1) , (0 , 4 , 1) , (0 , 5 , 1) , (1 , 2 , 1) , (1 , 6 , 1) , (2 , 3 , 1) ,
(2 , 7 , 1) , (3 , 8 , 1) , (4 , 9 , 1)]
TODO :
Add verbose option to make steps more transparent .
( Useful for teachers and students .)
"""
T_vertices = G . vertices () # a list of the form range ( n )
T_edges = []
E = G . edges () # a list of triples
# start ugly hack
Er = [ list ( x ) for x in E ]
E0 = []
for x in Er :
x . reverse ()
E0 . append ( x )
E0 . sort ()
E = []
for x in E0 :
x . reverse ()
E . append ( tuple ( x ))
# end ugly hack to get E is sorted by weight
for x in E : # find edges of T
TV = flatten ( T_edges )
u = x [0]
v = x [1]
if not ( u in TV and v in TV ):
T_edges . append ([ u , v ])
# find adj mat of T
if G . weighted ():
AG = G . w e i g h t e d _ a dj a c e n c y _ m a t r i x ()
else :
AG = G . adjacency_matrix ()
GV = G . vertices ()
n = len ( GV )
AT = []
for i in GV :
rw = [0]* n
for j in GV :
if [i , j ] in T_edges :
rw [ j ] = AG [ i ][ j ]
AT . append ( rw )
AT = matrix ( AT )
return Graph ( AT , format = " adjacency_matrix " , weighted = True )
Here is an example. We start with the grid graph. This is implemented in Sage such
that the vertices are given by the coordinates of the grid the graph lies on, as opposed
to 0, 1, . . . , n 1. Since the above implementation of Kruskals algorithm assumes that
the vertices are V = {0, 1, . . . , n 1}, we first redefine the graph suitable for running
Kruskals algorithm on it.
sage : G = graphs . GridGraph ([4 ,4])
119
sage : A = G . adjacency_matrix ()
sage : G = Graph (A , format = " adjacency_matrix " , weighted = True )
sage : T = kruskal ( G ); T . edges ()
[(0 , 1 , 1) , (0 , 4 , 1) , (1 , 2 , 1) , (1 , 5 , 1) , (2 , 3 , 1) , (2 , 6 , 1) , (3 ,7 , 1) ,
(4 , 8 , 1) , (5 , 9 , 1) , (6 , 10 , 1) , (7 , 11 , 1) , (8 , 12 , 1) , (9 , 13 , 1) ,
(10 , 14 , 1) , (11 , 15 , 1)]
An illustration of this graph is given in Figure 3.12.
Figure 3.12: Kruskals algorithm for the 4 4 grid graph.
3.3.2
Prims algorithm
Like Kruskals algorithm, Prims algorithm uses a greedy approach to computing a minimum spanning tree of a connected weighted graph G = (V, E), where n = |V | and
m = |E|. The algorithm was developed in 1930 by Czech mathematician V. Jarnk [105]
and later independently by R. C. Prim [159] and E. W. Dijkstra [58]. However, Prim was
the first to present an implementation that runs in time O(n2 ). Using 2-heaps, the runtime can be reduced [115] to O(m log n). With a Fibonacci heap implementation [79, 80],
the runtime can be reduced even further to O(m + n log n).
Pseudocode of Prims algorithm is given in Algorithm 3.3. For each v V , cost[v]
denotes the minimum weight among all edges connecting v to a vertex in the tree T ,
and parent[v] denotes the parent of v in T . During the algorithms execution, vertices v
that are not in T are organized in the minimum-priority queue Q, prioritized according
to cost[v]. Lines 1 to 3 set each cost[v] to a number that is larger than any weight in
the graph G, usually written . The parent of each vertex is set to NULL because we
have not yet started constructing the MST T . In lines 4 to 6, we choose an arbitrary
vertex r from V and mark that vertex as the root of T . The minimum-priority queue
is set to be all vertices from V . We set cost[r] to zero, making r the only vertex so far
with a cost that is < . During the first execution of the while loop from lines 7 to 12,
r is the first vertex to be extracted from Q and processed. Line 8 extracts a vertex u
from Q based on the key cost, thus moving u to the vertex set of T . Line 9 considers all
vertices adjacent to u. In an undirected graph, these are the neighbors of u; in a digraph,
we replace adj(u) with the out-neighbors oadj(u). The while loop updates the cost and
parent fields of each vertex v adjacent to u that is not in T . If parent[v] 6= NULL, then
cost[v] < and cost[v] is the weight of an edge connecting v to some vertex already in T .
Lines 13 to 14 construct the edge set of the minimum spanning tree and return this edge
set. The proof of correctness of Algorithm 3.3 is similar to the proof of Theorem 3.14.
Figure 3.13 shows the minimum spanning tree rooted at vertex 1 as a result of running
120
Prims algorithm over a digraph; Figure 3.14 shows the corresponding tree rooted at
vertex 5 of an undirected graph.
Algorithm 3.3: Prims algorithm.
Input: A weighted connected graph G = (V, E) with weight function w.
Output: A minimum spanning tree T of G.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
for each v V do
cost[v]
parent[v] NULL
r arbitrary vertex of V
cost[r] 0
QV
while Q 6= do
u extractMin(Q)
for each v adj(u) do
if v Q and w(u, v) < cost[v] then
parent[v] u
cost[v] w(u, v)

T (v, parent[v]) | v V {r}
return T
def prim ( G ):
"""
Implements Prim s algorithm to compute a MST of a graph .
INPUT :
G - a connected graph .
OUTPUT :
REFERENCES :
http :// en . wikipedia . org / wiki / Prim s_algorithm
"""
T_vertices = [0] # assumes G . vertices = range ( n )
T_edges = []
V = G . vertices ()
# start ugly hack to sort E
E0 = []
for x in Er :
x . reverse ()
E0 . append ( x )
E0 . sort ()
E = []
for x in E0 :
x . reverse ()
for x in E :
u = x [0]
v = x [1]
if u in T_vertices and not ( v in T_vertices ):
T_edges . append ([ u , v ])
T_vertices . append ( v )
# found T_vertices , T_edges
# find adj mat of T
if G . weighted ():
AG = G . w e i g h t e d _ a dj a c e n c y _ m a t r i x ()
else :
AG = G . adjacency_matrix ()
GV = G . vertices ()
n = len ( GV )
121
AT = []
for i in GV :
rw = [0]* n
for j in GV :
if [i , j ] in T_edges :
rw [ j ] = AG [ i ][ j ]
AT . append ( rw )
AT = matrix ( AT )
return Graph ( AT , format = " adjacency_matrix " , weighted = True )
sage : A = matrix ([[0 ,1 ,2 ,3] , [3 ,0 ,2 ,1] , [2 ,1 ,0 ,3] , [1 ,1 ,1 ,0]])
sage : E = G . edges (); E
[(0 , 1 , 1) , (0 , 2 , 2) , (0 , 3 , 3) , (1 , 0 , 3) , (1 , 2 , 2) , (1 , 3 , 1) , (2 , 0 , 2) ,
(2 , 1 , 1) , (2 , 3 , 3) , (3 , 0 , 1) , (3 , 1 , 1) , (3 , 2 , 1)]
sage : prim ( G )
Multi - graph on 4 vertices
sage : prim ( G ). edges ()
[(0 , 1 , 1) , (0 , 2 , 2) , (1 , 3 , 1)]
2
3
2
3
3
3
(b) 1st iteration of while loop.
2
3
1
2
2
3
1
3
(c) 2nd iteration of while loop.
(d) Final MST.
Figure 3.13: Running Prims algorithm over a digraph.

sage : A = matrix ([[0 ,7 ,0 ,5 ,0 ,0 ,0] , [0 ,0 ,8 ,9 ,7 ,0 ,0] , [0 ,0 ,0 ,0 ,5 ,0 ,0] , \
... [0 ,0 ,0 ,0 ,15 ,6 ,0] , [0 ,0 ,0 ,0 ,0 ,8 ,9] , [0 ,0 ,0 ,0 ,0 ,0 ,11] , [0 ,0 ,0 ,0 ,0 ,0 ,0]])
122

[(0 , 1 , 7) , (0 , 3 , 5) , (1 , 2 , 8) , (1 , 3 , 9) , (1 , 4 , 7) , (2 , 4 , 5) ,
(3 , 4 , 15) , (3 , 5 , 6) , (4 , 5 , 8) , (4 , 6 , 9) , (5 , 6 , 11)]
sage : prim ( G ). edges ()
[(0 , 1 , 7) , (0 , 3 , 5) , (1 , 2 , 8) , (1 , 4 , 7) , (3 , 5 , 6) , (4 , 6 , 9)]
3.3.3
Bor
uvkas algorithm
Bor
uvkas algorithm [31, 32] is a procedure for finding a minimum spanning tree in a
weighted connected graph G = (V, E) for which all edge weights are distinct. It was first
published in 1926 by Otakar Bor
uvka but subsequently rediscovered by many others,
including Choquet [50] and Florek et al. [74]. If G has order n = |V | and size m = |E|,
it can be shown that Bor
uvkas algorithm runs in time O(m log n).
Algorithm 3.4: Bor
uvkas algorithm.
Input: A weighted connected graph G = (V, E) with weight function w. All the
edge weights of G are distinct.
Output: A minimum spanning tree T of G.
1
2
3
4
5
6
7
n |V |
T Kn
while |E(T )| < n 1 do
for each component T 0 of T do
e0 edge of minimum weight that leaves T 0
E(T ) E(T ) e0
return T
Algorithm 3.4 provides pseudocode of Bor

uvkas algorithm. Given a weighted connected graph G = (V, E) all of whose edge weights are distinct, the initialization steps
in lines 1 and 2 construct a spanning forest T of G, i.e. the subgraph of G containing
all of the latters vertices and no edges. The initial forest has n components, each being
the trivial graph K1 . The while loop from lines 3 to 6 constructs a spanning tree of
G via a recursive procedure similar to Theorem 3.4. For each component T 0 of T , we
consider all the out-going edges of T 0 and choose an edge e0 that has minimum weight
among all such edges. This edge is then added to the edge set of T . In this way, two
distinct components, each of which is a tree, are joined together by a bridge. At the
end of the while loop, our final graph is a minimum spanning tree of G. Note that the
forest-merging steps in the for loop from lines 4 to 6 are amenable to parallelization,
hence the alternative name to Bor
uvkas algorithm: the parallel forest-merging method.
Example 3.15. Figure 3.15 illustrates the gradual construction of a minimum spanning
tree for the undirected graph given in Figure 3.15(a). In this case, we require two
iterations of the while loop in Bor
uvkas algorithm in order to obtain the final minimum
spanning tree in Figure 3.15(d).
def which_index (x , L ):
"""
L is a list of sublists ( or tuple of sets or list
of tuples , etc ).
Returns the index of the first sublist which x belongs
to , or None if x is not in flatten ( L ).
123
11
11
9
5
8
6
8
6
4
5
15
7
4
5
15
2
9
5
9
5
1
7
1
7
(b) 1st iteration of while loop.
11
11
9
5
8
6
8
6
4
5
15
7
4
5
15
2
9
5
9
5
1
7
1
7
(c) 2nd iteration of while loop.
(d) 3rd iteration of while loop.
11
5
8
6
15
7
9
5
1
7
(e) 4th iteration of while loop.
7
0
(f) Final MST.
Figure 3.14: Running Prims algorithm over an undirected graph.
124
8
7
10
4
9.5
2
5
6
9
11
0
(b) 0th iteration of while loop.
6
8
10
4
10
(c) 1st iteration of while loop.
(d) 2nd iteration of while loop.
Figure 3.15: Recursive construction of MST via Bor

uvkas algorithm.
125
The 0 - th element in
Lx = [ L . index ( S ) for S in L if x in S ]
almost works , but if the list is empty then Lx [0]
throws an exception .
EXAMPLES :
sage : L = [[1 ,2 ,3] ,[4 ,5] ,[6 ,7 ,8]]
sage : which_index (3 , L )
0
1
2
sage : which_index (9 , L ) == None
True
"""
for S in L :
if x in S :
return L . index ( S )
return None
def boruvka ( G ):
"""
Implements Boruvka s algorithm to compute a MST of a graph .
INPUT :
G - a connected edge - weighted graph with distinct weights .
OUTPUT :
REFERENCES :
http :// en . wikipedia . org / wiki / Boruvka s_algorithm
"""
T_vertices = [] # assumes G . vertices = range ( n )
T_edges = []
T = Graph ()
V = G . vertices ()
# start ugly hack to sort E
E0 = []
for x in Er :
x . reverse ()
E0 . append ( x )
E0 . sort ()
E = []
for x in E0 :
x . reverse ()
for e in E :
# create about | V |/2 edges of T " cheaply "
TV = T . vertices ()
if not ( e [0] in TV ) or not ( e [1] in TV ):
T . add_edge ( e )
for e in E :
# connect the " cheapest " components to get T
C = T . c o n n e c t e d _ c o m p o n e n t s _ s u b g r a p h s ()
VC = [ S . vertices () for S in C ]
if not ( e in T . edges ()) and ( which_index ( e [0] , VC ) != which_index ( e [1] , VC )):
if T . is_connected ():
break
T . add_edge ( e )
return T
Some examples using Sage:

sage : A = matrix ([[0 ,1 ,2 ,3] , [4 ,0 ,5 ,6] , [7 ,8 ,0 ,9] , [10 ,11 ,12 ,0]])
sage : boruvka ( G )
sage : boruvka ( G ). edges ()
[(0 , 1 , 1) , (0 , 2 , 2) , (0 , 3 , 3)]
sage : A = matrix ([[0 ,2 ,0 ,5 ,0 ,0 ,0] , [0 ,0 ,8 ,9 ,7 ,0 ,0] , [0 ,0 ,0 ,0 ,1 ,0 ,0] ,\
...
[0 ,0 ,0 ,0 ,15 ,6 ,0] , [0 ,0 ,0 ,0 ,0 ,3 ,4] , [0 ,0 ,0 ,0 ,0 ,0 ,11] , [0 ,0 ,0 ,0 ,0 ,0 ,0]])
126

[(0 , 1 , 2) , (0 , 3 , 5) , (1 , 2 , 8) , (1 , 3 , 9) , (1 , 4 , 7) ,
(2 , 4 , 1) , (3 , 4 , 15) , (3 , 5 , 6) , (4 , 5 , 3) , (4 ,6 , 4) , (5 , 6 , 11)]
sage : boruvka ( G )
[(0 , 1 , 2) , (0 , 3 , 5) , (2 , 4 , 1) , (3 , 5 , 6) , (4 , 5 , 3) , (4 , 6 , 4)]
sage : A = matrix ([[0 ,1 ,2 ,5] , [0 ,0 ,3 ,6] , [0 ,0 ,0 ,4] , [0 ,0 ,0 ,0]])
[(0 , 1 , 1) , (0 , 2 , 2) , (2 , 3 , 4)]
sage : A = matrix ([[0 ,1 ,5 ,0 ,4] , [0 ,0 ,0 ,0 ,3] , [0 ,0 ,0 ,2 ,0] , [0 ,0 ,0 ,0 ,0] , [0 ,0 ,0 ,0 ,0]])
[(0 , 1 , 1) , (0 , 2 , 5) , (1 , 4 , 3) , (2 , 3 , 2)]
3.4
Binary trees
A binary tree is a rooted tree with at most two children per parent. Each child is
designated as either a left-child or a right-child . Thus binary trees are also 2-ary trees.
Some examples of binary trees are illustrated in Figure 3.16. Given a vertex v in a
binary tree T of height h, the left subtree of v is comprised of the subtree that spans
the left-child of v and all of this childs descendants. The notion of a right-subtree of a
binary tree is similarly defined. Each of the left and right subtrees of v is itself a binary
tree with height h 1. If v is the root vertex, then each of its left and right subtrees
has height h 1, and at least one of these subtrees has height equal to h 1.
(a)
(b)
(c)
(d)
Figure 3.16: Examples of binary trees.

Theorem 3.16. If T is a complete binary tree of height h, then T has 2h+1 1 vertices.
Proof. Argue by induction on h. The assertion of the theorem is trivially true in the
base case h = 0. Let k 0 and assume for induction that any complete binary tree of
height k has order 2k+1 1. Suppose T is a complete binary tree of height k + 1 and
denote the left and right subtrees of T by T1 and T2 , respectively. Each Ti (for i = 1, 2)
is a complete binary tree of height k and by our induction hypothesis Ti has 2k+1 1
vertices. Thus T has order
1 + (2k+1 1) + (2k+1 1) = 2k+2 1
as required.
3.4. Binary trees
127
Theorem 3.16 provides a useful upper bound on the order of a binary tree of a given
height. This upper bound is stated in the following corollary.
Corollary 3.17. A binary tree of height h has at most 2h+1 1 vertices.
We now count the number of possible binary trees on n vertices. Let bn be the number
of binary trees of order n. For n = 0, we set b0 = 1. The trivial graph is the only binary
tree with one vertex, hence b1 = 1. Suppose n > 1 and let T be a binary tree on n
vertices. Then the left subtree of T has order 0 i n 1 and the right subtree has
n 1 i vertices. As there are bi possible left subtrees and bn1i possible right subtrees,
T has a total of bi bn1i different combinations of left and right subtrees. Summing from
i = 0 to i = n 1 and we have
bn =
n1
X
bi bn1i .
(3.2)
i=0
Expression (3.2) is known as the Catalan recursion and the number bn is the n-th Catalan
number, which we know from problem 1.15 can be expressed in the closed form

2n
1
.
(3.3)
bn =
n+1 n
Figures 3.17 to 3.19 enumerate all the different binary trees on 2, 3, and 4 vertices,
respectively.
(a)
(b)
Figure 3.17: The b2 = 2 binary trees on 2 vertices.
(a)
(b)
(c)
(d)
(e)

The first few values of (3.3) are
b0 = 1,
b1 = 1,
b2 = 2,
b3 = 5,
b4 = 14
which are rather small and of manageable size if we want to explicitly enumerate all
different binary trees with the above orders. However, from n = 4 onwards the value
of bn increases very fast. Instead of enumerating all the bn different binary trees of a
specified order n, a related problem is generating a random binary tree of order n. That
is, we consider the set B as a sample space of bn different binary trees on n vertices,
and choose a random element from B. Such a random element can be generated using
Algorithm 3.5. The list parent holds all vertices with less than two children, each vertex
can be considered as a candidate parent to which we can add a child. An element of
parent is a two-tuple (v, k) where the vertex v currently has k children.
128
(a)
(b)
(f)
(c)
(g)
(k)
(d)
(h)
(l)
(e)
(i)
(m)
(j)
(n)
Algorithm 3.5: Random binary tree.

Input: Positive integer n.
Output: A random binary tree on n vertices.
1
2
3
4
5
6
7
8
9
10
11
12
13
if n = 1 then
return K1
v0
T null graph
add v to T
parent [(v, 0)]
for i 1, 2, . . . , n 1 do
(v, k) remove random element from parent
if k < 1 then
add (v, k + 1) to parent
add edge (v, i) to T
add (i, 0) to parent
return T
3.4. Binary trees
3.4.1
129
Binary codes
What is a code?
A code is a rule for converting data in one format, or well-defined tangible representation,
into sequences of symbols in another format. The finite set of symbols used is called the
alphabet. We shall identify a code as a finite set of symbols which are the image of the
alphabet under this conversion rule. The elements of this set are referred to as codewords.
For example, using the ASCII code, the letters in the English alphabet get converted
into numbers in the set {0, 1, . . . , 255}. If these numbers are written in binary, then
each codeword of a letter has length 8, i.e. eight bits. In this way, we can reformat or
encode a string into a sequence of binary symbols, i.e. 0s and 1s. Encoding is the
conversion process one way. Decoding is the reverse process, converting these sequences
of code-symbols back into information in the original format.
Codes are used for:
Economy. Sometimes this is called entropy encoding since there is an entropy
function which describes how much information a channel (with a given error rate)
can carry and such codes are designed to maximize entropy as best as possible. In
this case, in addition to simply being given an alphabet A, one might be given a
weighted alphabet, i.e. an alphabet for which each symbol a A is associated with
a nonnegative number wa 0 (in practice, this number represents the probability
that the symbol a occurs in a typical word).
Reliability. Such codes are called error-correcting codes, since such codes are designed to communicate information over a noisy channel in such a way that the
errors in transmission are likely to be correctable.
Security. Such codes are called cryptosystems. In this case, the inverse of the
coding function c : A B is designed to be computationally infeasible. In other
words, the coding function c is designed to be a trapdoor function.
Other codes are merely simpler ways to communicate information (e.g. flag semaphores,
color codes, genetic codes, braille codes, musical scores, chess notation, football diagrams,
and so on) and have little or no mathematical structure. We shall not study them.
Basic definitions
If every word in the code has the same length, the code is called a block code. If a
code is not a block code, then it is called a variable-length code. A prefix-free code is a
code (typically one of variable-length) with the property that there is no valid codeword
in the code that is a prefix or start of any other codeword.1 This is the prefix-free
condition.
One example of a prefix-free code is the ASCII code. Another example is
00, 01, 100.
On the other hand, a non-example is the code
00, 01, 010, 100
1
In other words, a codeword s = s1 sm is a prefix of a codeword t = t1 tn if and only if m n

and s1 = t1 , . . . , sm = tm . Codes that are prefix-free are easier to decode than codes that are not
prefix-free.
130
since the second codeword is a prefix of the third one. Another non-example is Morse
code recalled in Table 3.1, where we use 0 for (dit) and 1 for (dah). For
example, consider the Morse code for aand the Morse code for w. These codewords
violate the prefix-free condition.
A
B
C
D
E
F
G
H
I
J
K
L
M
01
1000
1010
100
0
0010
110
0000
00
0111
101
0100
11
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
10
111
0110
1101
010
000
1
001
0001
011
1001
1011
1100
Table 3.1: Morse code
Gray codes
We begin with some history.2 Frank Gray (18871969) wrote about the so-called Gray
codes in a 1951 paper published in the Bell System Technical Journal and then in 1953
patented a device (used for television sets) based on his paper. However, the idea of
a binary Gray code appeared earlier. In fact, it appeared in an earlier patent (one by
Stibitz in 1943). It was also used in the French engineer E. Baudots telegraph machine
of 1878 and in a French booklet by L. Gros on the solution published in 1872 to the
Chinese ring puzzle.
The term Gray code is ambiguous. It is actually a large family of sequences of
n-tuples. Let Zm = {0, 1, . . . , m 1}. More precisely, an m-ary Gray code of length
n (called a binary Gray code when m = 2) is a sequence of all possible (i.e. N = mn )
n-tuples
g1 , g2 , . . . , gN
where
each gi Znm ,
gi and gi+1 differ by 1 in exactly one coordinate.
In other words, an m-ary Gray code of length n is a particular way to order the set of
all mn n-tuples whose coordinates are taken from Zm . From the transmission/communication perspective, this sequence has two advantages:
It is easy and fast to produce the sequence, since successive entries differ in only
one coordinate.
2
This history comes from an unpublished section 7.2.1.1 (Generating all n-tuples) in volume 4 of
Donald Knuths The Art of Computer Programming.
3.4. Binary trees
131
An error is relatively easy to detect, since we can compare an n-tuple with the
previous one. If they differ in more than one coordinate, we conclude that an error
was made.
Example 3.18. Here is a 3-ary Gray code of length 2:

[0, 0], [1, 0], [2, 0], [2, 1], [1, 1], [0, 1], [0, 2], [1, 2], [2, 2]
and the sequence
[0, 0, 0], [1, 0, 0], [1, 1, 0], [0, 1, 0], [0, 1, 1], [1, 1, 1], [1, 0, 1], [0, 0, 1]
is a binary Gray code of length 3.
Gray codes have applications to engineering, recreational mathematics (solving the
Tower of Hanoi puzzle, The Brain puzzle, the Chinese ring puzzle, etc.), and to mathematics (e.g. aspects of combinatorics, computational group theory, and the computational aspects of linear codes).
Binary Gray codes
Consider the so-called n-hypercube graph Qn , whose first few instances are illustrated
in Figure 1.27. This can be envisioned as the graph whose vertices are the vertices of a
cube in n-space
{(x1 , . . . , xn ) | 0 xi 1}
and whose edges are those line segments in Rn connecting two neighboring vertices, i.e.
two vertices that differ in exactly one coordinate. A binary Gray code of length n can
be regarded as a path on the hypercube graph Qn that visits each vertex of the cube
exactly once. In other words, a binary Gray code of length n may be identified with a
Hamiltonian path on the graph Qn . For example, Figure 3.20 illustrates a Hamiltonian
path on Q3 .
Figure 3.20: Viewing 3 as a Hamiltonian path on Q3 .

How do we efficiently compute a Gray code? Perhaps the simplest way to state the
idea of quickly constructing the reflected binary Gray code n of length n is as follows:
0 = [ ],

n = [0, n1 ], [1, rev
n1 ]
132
where rev
m means the Gray code in reverse order. For instance, we have
0 = [ ],

1 = [0], [1] ,

2 = [0, 0], [0, 1], [1, 1], [1, 0]
and so on. This is a nice procedure for creating the entire list at once, which gets very
long very fast. An implementation of the reflected Gray code using Python is given
below.
def graycode ( length , modulus ):
"""
Returns the n - tuple reflected Gray code mod m .
EXAMPLES :
sage : graycode (2 ,4)
[[0 ,
[1 ,
[2 ,
[3 ,
[3 ,
[2 ,
[1 ,
[0 ,
[0 ,
[1 ,
[2 ,
[3 ,
[3 ,
[2 ,
[1 ,
[0 ,
0] ,
0] ,
0] ,
0] ,
1] ,
1] ,
1] ,
1] ,
2] ,
2] ,
2] ,
2] ,
3] ,
3] ,
3] ,
3]]
"""
n , m = length , modulus
F = range ( m )
if n == 1:
return [[ i ] for i in F ]
L = graycode (n -1 , m )
M = []
for j in F :
M = M +[ ll +[ j ] for ll in L ]
k = len ( M )
Mr = [0]* m
for i in range (m -1):
i1 = i * int ( k / m )
# this requires Python 3.0 or Sage
i2 = ( i +1)* int ( k / m )
Mr [ i ] = M [ i1 : i2 ]
Mr [m -1] = M [( m -1)* int ( k / m ):]
for i in range ( m ):
if is_odd ( i ):
Mr [ i ]. reverse ()
M0 = []
for i in range ( m ):
M0 = M0 + Mr [ i ]
return M0
Consider the reflected binary code of length 8, i.e. 8 . This has 28 = 256 codewords.
Sage can easily create the list plot of the coordinates (x, y), where x is an integer j Z256
that indexes the codewords in 8 and the corresponding y is the j-th codeword in 8
converted to decimal. This will give us some idea of how the Gray code looks in some
sense. The plot is given in Figure 3.21.
What if we only want to compute the i-th Gray codeword in the Gray code of length
n? Can it be computed quickly without computing the entire list? At least in the case of
the reflected binary Gray code, there is a very simple way to do this. The k-th element in
3.5. Huffman codes
133
200
100
0
0
50
100
150
200
250
Figure 3.21: Scatterplot of 8 .

the above-described reflected binary Gray code of length n is obtained by simply adding
the binary representation of k to the binary representation of the integer part of k/2.
An example using Sage is given below.
def int2binary (m , n ):
returns GF (2) vector of length n obtained

from the binary repr of m , padded by 0 s
( on the left ) to length n .
EXAMPLES :
sage : for j in range (8):
....:
print int2binary (j ,3)+ int2binary ( int ( j /2) ,3)
....:
(0 , 0 , 0)
(0 , 0 , 1)
(0 , 1 , 1)
(0 , 1 , 0)
(1 , 1 , 0)
(1 , 1 , 1)
(1 , 0 , 1)
(1 , 0 , 0)
s = bin ( m )
k = len ( s )
F = GF (2)
b = [ F (0)]* n
for i in range (2 , k ):
b [n - k + i ] = F ( int ( s [ i ]))
return vector ( b )
def graycodeword (m , n ):
returns the k - th codeword in the reflected binary Gray code

of length n .
EXAMPLES :
sage : graycodeword (3 ,3)
(0 , 1 , 0)
return map ( int , int2binary (m , n )+ int2binary ( int ( m /2) , n ))
3.5
Huffman codes
An alphabet A is a finite set whose elements are referred to as symbols. A word (or string
or message) over A is a finite sequence of symbols in A and the length of the word is
134
the number of symbols it contains. A word is usually written by concatenating symbols

together, e.g. a1 a2 ak (ai A) is a word of length k.
A commonly occurring alphabet in practice is the binary alphabet B = {0, 1}. A
word over the binary alphabet is a finite sequence of 0s and 1s. If A is an alphabet, let
A denote the set of all words in A. The length of a word is denoted by vertical bars.
That is, if w = a1 ak is a word over A, then define |w| : A Z by
|w| = |a1 ak | = k.
Let A and B be two alphabets. A code for A using B is an injection c : A B . By
abuse of notation, we often denote the code simply by the set
C = c(A) = {c(a) | a A}.
The elements of C are called codewords. If B is the binary alphabet, then C is called a
binary code.
3.5.1
Tree representation
Any binary code can be represented by a tree, as Example 3.19 shows.

Example 3.19. Let B` be the binary code of length `. Represent codewords of B`
using trees.
Solution. Here is how to represent the code B` consisting of all binary strings of length
`. Start with the root node being the empty string. The two children of this node,
v0 and v1 , correspond to the two strings of length 1. Label v0 with a 0 and v1 with
a 1. The two children of v0 , i.e. v00 and v01 , correspond to the strings of length 2
which start with a 0. Similarly, the two children of v1 , i.e. v10 and v11 , correspond to
the strings of length 2 that each starts with a 1. Continue creating child nodes until we
reach length `, at which point we stop. There are a total of 2`+1 1 nodes in this tree
and 2` of them are leaves (vertices of a tree with degree 1, i.e. childless nodes). Note
that the parent of any node is a prefix to that node. Label each node vs with the string
s, where s is a binary sequence of length `. See Figure 3.22 for an example when
` = 2.
00
01
10
11
Figure 3.22: Tree representation of the binary code B2 .

In general, if C is a code contained in B` , then to create the tree for C, start with
the tree for B` . First, remove all nodes associated to a binary string for which it and
3.5. Huffman codes
135
all of its descendants are not in C. Next, remove all labels which do not correspond to
codewords in C. The resulting labeled graph is the tree associated to the binary code C.
For visualizing the construction of Huffman codes later, it is important to see that
we can reverse this construction to start from such a binary tree and recover a binary
code from it. The codewords are determined by the following rules:
The root node gets the empty codeword.
Each left-ward branch gets a 0 appended to the end of its parent. Each right-ward
branch gets a 1 appended to the end.
3.5.2
Uniquely decodable codes
If c : A B is a code, then we can extend c to A by concatenation:

c(a1 a2 ak ) = c(a1 )c(a2 ) c(ak ).
If the extension c : A T is also an injection, then c is called uniquely decodable.
The property of unique decodability or decipherability informally means that any given
sequence of symbols has at most one interpretation as a sequence of codewords.
Example 3.20. Is the Morse code in Table 3.1 uniquely decodable? Why or why not?
Solution. Note that these Morse codewords all have lengths less than or equal to 4.
Other commonly occurring symbols used (the digits 0 through 9, punctuation symbols,
and some others) are also encodable in Morse code, but they use longer codewords.
Let A denote the English alphabet, B = {0, 1} the binary alphabet, and c : A B
the Morse code. Since c(ET ) = 01 = c(A), it is clear that the Morse code is not uniquely
decodable.
In fact, prefix-free implies uniquely decodable.
Theorem 3.21. If a code c : A B is prefix-free, then it is uniquely decodable.
Proof. We use induction on the length of a message. We want to show that if x1 xk
and y1 y` are messages with c(x1 ) c(xk ) = c(y1 ) c(y` ), then x1 xk = y1 y` .
This in turn implies k = ` and xi = yi for all i.
The case of length 1 follows from the fact that c : A B is injective (by the
definition of code).
Suppose that the statement of the theorem holds for all codes of length < m. We
must show that the length m case is true. Suppose c(x1 ) c(xk ) = c(y1 ) c(y` ), where
m = max(k, `). These strings are equal, so the substring c(x1 ) of the left-hand side
and the substring c(y1 ) of the right-hand side are either equal or one is contained in the
other. If, say, c(x1 ) is properly contained in c(y1 ), then c is not prefix-free. Likewise if
c(y1 ) is properly contained in c(x1 ). Therefore, c(x1 ) = c(y1 ), which implies x1 = y1 .
Now remove this codeword from both sides, so c(x2 ) c(xk ) = c(y2 ) c(y` ). By the
induction hypothesis, x2 xk = y2 y` . These facts together imply k = ` and xi = yi
for all i.
136
P
Consider now a weighted alphabet (A, p), where p : A [0, 1] satisfies aA p(a) =
1, and a code c : A B . In other words, p is a probability distribution on A. Think
of p(a) as the probability that the symbol a arises in a typical message. The average
word length L(c) is3
X
L(c) =
p(a) |c(a)|
aA
where | | is the length of a codeword. Given a weighted alphabet (A, p) as above, a

code c : A B is called optimal if there is no such code with a smaller average word
length. Optimal codes satisfy the following amazing property. For a proof, which is very
easy and highly recommended for anyone who is curious to see more, refer to section 3.6
of Biggs [24].
Lemma 3.22. Suppose c : A B is a binary optimal prefix-free code and let ` =
maxaA |c(a)| denote the maximum length of a codeword. The following statements
hold.
1. If |c(a0 )| > |c(a)|, then p(a0 ) p(a).
2. The subset of codewords of length `, i.e.
C` = {c c(A) | ` = |c(a)|}
contains two codewords of the form b0 and b1 for some b B .
3.5.3
Huffman coding
The Huffman code construction is based on the second property in Lemma 3.22. Using
this property, in 1952 David Huffman [103] presented an optimal prefix-free binary code,
which has since been named Huffman code.
Here is the recursive/inductive construction of a Huffman code. We shall regard the
binary Huffman code as a tree, as described above. Suppose that the weighted alphabet
(A, p) has n symbols. We assume inductively that there is an optimal prefix-free binary
code for any weighted alphabet (A0 , p0 ) having < n symbols.
Huffmans rule 1 Let a, a0 A be symbols with the smallest weights. Construct a new
weighted alphabet with a, a0 replaced by the single symbol a = aa0 and having
weight p(a ) = p(a) + p(a0 ). All other symbols and weights remain unchanged.
Huffmans rule 2 For the code (A0 , p0 ) above, if a is encoded as the binary string s,
then the encoded binary string for a is s0 and the encoded binary string for a0 is
s1.
The above two rules tell us how to inductively build the tree representation for the
Huffman code of (A, p) up from its leaves (associated to the low weight symbols).
Find two different symbols of lowest weight, a and a0 . If two such symbols do not
exist, stop. Replace the weighted alphabet with the new weighted alphabet as in
Huffmans rule 1.
3
In probability terminology, this is the expected value E(X) of the random variable X, which assigns
to a randomly selected symbol in A the length of the associated codeword in c.
3.5. Huffman codes
137
Add two nodes (labeled with a and a0 , respectively) to the tree, with parent a (see
Huffmans rule 1).
If there are no remaining symbols in A, label the parent a with the empty set and
stop. Otherwise, go to the first step.
These ideas are captured in Algorithm 3.6, which outlines steps to construct a binary
tree corresponding to the Huffman code of an alphabet. Line 2 initializes a minimumpriority queue Q with the symbols in the alphabet A. Line 3 creates an empty binary
tree that will be used to represent the Huffman code corresponding to A. The for loop
from lines 4 to 10 repeatedly extracts from Q two elements a and b of minimum weights.
We then create a new vertex z for the tree T and also let a and b be vertices of T . The
weight W [z] of z is the sum of the weights of a and b. We let z be the parent of a and b,
and insert the new edges za and zb into T . The newly created vertex z is now inserted
into Q with priority W [z]. After n 1 rounds of the for loop, the priority queue has only
one element in it, namely the root r of the binary tree T . We extract r from Q (line 11)
and return it together with T (line 12).
Algorithm 3.6: Binary tree representation of Huffman codes.
Input: An alphabet A of n symbols. A weight list W of size n such that W [i] is
the weight of ai A.
Output: A binary tree T representing the Huffman code of A and the root r of T .
1
2
3
4
5
6
7
8
9
10
11
12
n |A|
QA
/* minimum priority queue */
T empty tree
for i 1, 2, . . . , n 1 do
a extractMin(Q)
b extractMin(Q)
z node with left child a and right child b
add the edges za and zb to T
W [z] W [a] + W [b]
insert z into priority queue Q
r extractMin(Q)
return (T, r)
The runtime analysis of Algorithm 3.6 depends on the implementation of the priority
queue Q. Suppose Q is a simple unsorted list. The initialization on line 2 requires O(n)
time. The for loop from line 4 to 10 is executed exactly n 1 times. Searching Q to
determine the element of minimum weight requires time at most O(n). Determining two
elements of minimum weights requires time O(2n). The for loop requires time O(2n2 ),
which is also the time requirement for the algorithm. An efficient implementation of
the priority queue Q, e.g. as a binary minimum heap, can lower the running time of
Algorithm 3.6 down to O(n log2 (n)).
Algorithm 3.6 represents the Huffman code of an alphabet as a binary tree T rooted
at r. For an illustration of the process of constructing a Huffman tree, see Figure 3.23.
To determine the actual encoding of each symbol in the alphabet, we feed T and r to
Algorithm 3.7 to obtain the encoding of each symbol. Starting from the root r whose
designated label is the empty string , the algorithm traverses the vertices of T in a
138
13
13
19
19
4
2
19
13
19
(d)
19
13
8
4
19
5
2
1
(e)
15
7
10
5
2
10
5
15
13
2
1
23
5
4
2
(f)
19
10
2
1
13
5
2
(c)
8
13
19
8
(g)
(h)
57
23
10
5
34
13
5
2
(b)
2
1
(a)
13
15
7
23
19
13
5
2
4
2
15
7
19
8
2
1
(i)
10
8
4
34
4
2
2
1
(j)
Figure 3.23: Constructing a Huffman tree.
7
3
3.6. Tree traversals
139
breadth-first search fashion. If v is an internal vertex with label e, the label of its leftchild is the concatenation e0 and for the right-child of v we assign the label e1. If v
happens to be a leaf vertex, we take its label to be its Huffman encoding. Any Huffman
encoding assigned to a symbol of an alphabet is not unique. Either of the two children of
an internal vertex can be designated as the left- (respectively, right-) child. The runtime
of Algorithm 3.7 is O(|V |), where V is the vertex set of T .
Algorithm 3.7: Huffman encoding of an alphabet.
Input: A binary tree T representing the Huffman code of an alphabet A. The
root r of T .
Output: A list H representing a Huffman code of A, where H[ai ] corresponds to
a Huffman encoding of ai A.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
H []
/* list of Huffman encodings */
Q [r]
/* queue of vertices */
root dequeue(Q)
if root is a leaf then
H[root] label of root
else
a left child of root
b right child of root
enqueue(Q, a)
enqueue(Q, b)
label of a label of root + 0
label of b label of root + 1
return H
Example 3.23. Consider the alphabet A = {a, b, c, d, e, f } with corresponding weights

w(a) = 19, w(b) = 2, w(c) = 40, w(d) = 25, w(e) = 31, and w(f ) = 3. Construct a
binary tree representation of the Huffman code of A and determine the encoding of each
symbol of A.
Solution. Use Algorithm 3.6 to construct a binary tree representation of the weighted
alphabet A. The resulting binary tree T is shown in Figure 3.24(a), where ai : wi is an
abbreviation for vertex ai has weight wi . The binary tree is rooted at k. To encode
each alphabetic symbol, input T and k into Algorithm 3.7 to get the encodings shown
in Figure 3.24(b).
3.6
Tree traversals
In computer science, tree traversal refers to the process of examining each vertex in a tree
data structure. Starting at the root of an ordered tree T , we can traverse the vertices of
T in one of various ways.
A level-order traversal of an ordered tree T examines the vertices in increasing order
of depth, with vertices of equal depth being examined according to their prescribed
order. One way to think about level-order traversal is to consider vertices of T having
140

k : 120
j : 71
i : 49
h : 24
g:5
b:2
d : 25
e : 31
c : 40
00
a : 19
000
f :3
0000
(a)
01
10
11
001
0001
(b)
Figure 3.24: Binary tree representation of an alphabet and its Huffman encodings.
the same depth as being ordered from left to right in decreasing order of importance.
If [v1 , v2 , . . . , vn ] lists the vertices from left to right at depth k, a decreasing order of
importance can be realized by assigning each vertex a numeric label using a labelling
function L : V (T ) R such that L(v1 ) < L(v2 ) < < L(vn ). In this way, a vertex
with a lower numeric label is examined prior to a vertex with a higher numeric label. A
level-order traversal of T , whose vertices of equal depth are prioritized according to L,
is an examination of the vertices of T from top to bottom, left to right. As an example,
the level-order traversal of the tree in Figure 3.25 is
42, 4, 15, 2, 3, 5, 7, 10, 11, 12, 13, 14.
Our discussion is formalized in Algorithm 3.8, whose general structure mimics that of
breadth-first search. For this reason, level-order traversal is also known as breadth-first
traversal. Each vertex is enqueued and dequeued exactly once. The while loop is executed
n times, hence we have a runtime of O(n). Another name for level-order traversal is topdown traversal because we first visit the root node and then work our way down the
tree, increasing the depth as we move downward.
Pre-order traversal is a traversal of an ordered tree using a general strategy similar
to depth-first search. For this reason, pre-order traversal is also referred to as depth-first
traversal. Parents are visited prior to their respective children and siblings are visited
according to their prescribed order. The pseudocode for pre-order traversal is presented
in Algorithm 3.9. Note the close resemblance to Algorithm 3.8; the only significant
change is to use a stack instead of a queue. Each vertex is pushed and popped exactly
once, so the while loop is executed n times, resulting in a runtime of O(n). Using
Algorithm 3.9, a pre-order traversal of the tree in Figure 3.25 is
42, 4, 2, 3, 10, 11, 14, 5, 12, 13, 15, 7.
Whereas pre-order traversal lists a vertex v the first time we visit it, post-order
traversal lists v the last time we visit it. In other words, children are visited prior to their
respective parents, with siblings being visited in their prescribed order. The prefix pre
in pre-order traversal means before, i.e. visit parents before visiting children. On the
141
42
15
10
11
12
13
14
Figure 3.25: Traversing a tree.

Algorithm 3.8: Level-order traversal.
Input: An ordered tree T on n > 0 vertices.
Output: A list of the vertices of T in level-order.
1
2
3
4
5
6
7
8
9
10
11
L []
Q empty queue
r root of T
enqueue(Q, r)
v dequeue(Q)
append(L, v)
[u1 , u2 , . . . , uk ] ordering of children of v
for i 1, 2, . . . , k do
enqueue(Q, ui )
return L
Algorithm 3.9: Pre-order traversal.

Output: A list of the vertices of T in pre-order.
1
2
3
4
5
6
7
8
9
10
11
L []
S empty stack
r root of T
push(S, r)
v pop(S)
append(L, v)
[u1 , u2 , . . . , uk ] ordering of children of v
for i k, k 1, . . . , 1 do
push(S, ui )
return L
142
other hand, the prefix post in post-order traversal means after, i.e. visit parents
after having visited their children. The pseudocode for post-order traversal is presented
in Algorithm 3.10, whose general structure bears close resemblance to Algorithm 3.9.
The while loop of the former is executed n times because each vertex is pushed and
popped exactly once, resulting in a runtime of O(n). The post-order traversal of the tree
in Figure 3.25 is
2, 10, 14, 11, 3, 12, 13, 5, 4, 7, 15, 42.
Algorithm 3.10: Post-order traversal.
Output: A list of the vertices of T in post-order.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
L []
S empty stack
r root of T
push(S, r)
if top(S) is unmarked then
mark top(S)
[u1 , u2 , . . . , uk ] ordering of children of top(S)
for i k, k 1, . . . , 1 do
push(S, ui )
else
v pop(S)
append(L, v)
return L
Instead of traversing a tree T from top to bottom as is the case with level-order
traversal, we can reverse the direction of our traversal by traversing a tree from bottom
to top. Called bottom-up traversal , we first visit all the leaves of T and consider the
subtree T1 obtained by vertex deletion of those leaves. We then recursively perform
bottom-up traversal of T1 by visiting all of its leaves and obtain the subtree T2 resulting
from vertex deletion of those leaves of T1 . Apply bottom-up traversal to T2 and its vertex
deletion subtrees until we have visited all vertices, including the root vertex. The result
is a procedure for bottom-up traversal as presented in Algorithm 3.11. In lines 3 to 5,
we initialize the list C to contain the number of children of vertex i. This takes O(m)
time, where m = |E(T )|. Lines 6 to 14 extract all the leaves of T and add them to the
queue Q. From lines 15 to 23, we repeatedly apply bottom-up traversal to subtrees of
T . As each vertex is enqueued and dequeued exactly once, the two loops together run
in time O(n) and therefore Algorithm 3.11 has a runtime of O(n + m). As an example,
a bottom-up traversal of the tree in Figure 3.25 is
2, 7, 10, 12, 13, 14, 15, 5, 11, 3, 4, 42.
Yet another common tree traversal technique is called in-order traversal . However, inorder traversal is only applicable to binary trees, whereas the other traversal techniques
we considered above can be applied to any tree with at least one vertex. Given a binary
tree T having at least one vertex, in-order traversal first visits the root of T and consider

Algorithm 3.11: Bottom-up traversal.
Output: A list of the vertices of T in bottom-up order.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Q empty queue
r root of T
C [0, 0, . . . , 0]
/* n copies of 0 */
for each edge (u, v) E(T ) do
C[u] C[u] + 1
R empty queue
enqueue(R, r)
while length(R) > 0 do
v dequeue(R)
for each w children(v) do
if C[w] = 0 then
enqueue(Q, w)
else
enqueue(R, w)
L []
v dequeue(Q)
append(L, v)
if v 6= r then
C[parent(v)] C[parent(v)] 1
if C[parent(v)] = 0 then
u parent(v)
enqueue(Q, u)
return L
Algorithm 3.12: In-order traversal.

Input: A binary tree T on n > 0 vertices.
Output: A list of the vertices of T in in-order.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
L []
S empty stack
v root of T
while True do
if v 6= NULL then
push(S, v)
v left-child of v
else
if length(S) = 0 then
exit the loop
v pop(S)
append(L, v)
v right-child of v
return L
143
144
its left- and right-children. We then recursively apply in-order traversal to the left and
right subtrees of the root vertex. Notice the symmetry in our description of in-order
traversal: start at the root, then traverse the left and right subtrees in in-order. For this
reason, in-order traversal is sometimes referred to as symmetric traversal. Our discussion
is summarized in Algorithm 3.12. In the latter algorithm, if a vertex does not have a
left-child, then the operation of finding its left-child returns NULL. The same holds when
the vertex does not have a right-child. Since each vertex is pushed and popped exactly
once, it follows that in-order traversal runs in time O(n). Using Algorithm 3.12, an
in-order traversal of the tree in Figure 3.24(b) is
0000, 000, 0001, 00, 001, 0, 01, , 10, 1, 11.
3.7
Problems
When solving problems, dig at the roots instead of just hacking at the leaves.
Anthony J. DAngelo, The College Blue Book
3.1. Construct all nonisomorphic trees of order 7.

3.2. Let G be a weighted connected graph and let T be a subgraph of G. Then T is a
maximum spanning tree of G provided that the following conditions are satisfied:
(a) T is a spanning tree of G.
(b) The total weight of T is maximum among all spanning trees of G.
Modify Kruskals, Prims, and Bor
uvkas algorithms to return a maximum spanning
tree of G.
3.3. Describe and present pseudocode of an algorithm to construct all spanning trees
of a connected graph. What is the worst-case runtime of your algorithm? How
many of the constructed spanning trees are nonisomorphic to each other? Repeat
the exercise for minimum and maximum spanning trees.
3.4. Consider an undirected, connected simple graph G = (V, E) of order n and size
m and having an integer weight function w : E Z given by w(e) > 0 for
all e E. Suppose that G has N minimum spanning trees. Yamada et al. [197]
provide an O(N m ln n) algorithm to construct all the N minimum spanning trees of
G. Describe and provide pseudocode of the Yamada-Kataoka-Watanabe algorithm.
Provide runtime analysis and prove the correctness of this algorithm.
3.5. The solution of Example 3.3 relied on the following result: Let T = (V, E) be a tree
rooted at v0 and suppose v0 has exactly two children. If maxvV deg(v) = 3 and
v0 is the only vertex with degree 2, then T is a binary tree. Prove this statement.
Give examples of graphs that are binary trees but do not satisfy the conditions
of the result. Under which conditions would the above test return an incorrect
answer?
3.6. What is the worst-case runtime of Algorithm 3.1?
3.7. Figure 3.5 shows two nonisomorphic spanning trees of the 4 4 grid graph.
3.7. Problems
145
(a) For each n = 1, 2, . . . , 7, construct all nonisomorphic spanning trees of the

n n grid graph.
(b) Explain and provide pseudocode of an algorithm for constructing all spanning
trees of the n n grid graph, where n > 0.
(c) In general, if n is a positive integer, how many nonisomorphic spanning trees

are there in the n n grid graph?
(d) Describe and provide pseudocode of an algorithm to generate a random spanning tree of the n n grid graph. What is the worst-case runtime of your
algorithm?
3.8. Theorem 3.4 shows how to recursively construct a new tree from a given collection
of trees, hence it can be considered as a recursive definition of trees. To prove theorems based upon recursive definitions, we use a proof technique called structural
induction. Let S(C) be a statement about the collection of structures C, each of
which is defined by a recursive definition. In the base case, prove S(C) for the
basis structure(s) C. For the inductive case, let X be a structure formed using
the recursive definition from the structures Y1 , Y2 , . . . , Yk . Assume for induction
that the statements S(Y1 ), S(Y2 ), . . . , S(Yk ) hold and use the inductive hypotheses
S(Yi ) to prove S(X). Hence conclude that S(X) is true for all X. Apply structural
induction to show that any graph constructed using Theorem 3.4 is indeed a tree.
3.9. In Kruskals Algorithm 3.2, line 5 requires that the addition of a new edge to T
does not result in T having a cycle. A tree by definition has no cycles. Suppose
line 5 is changed to:
if ei
/ E(T ) and T {ei } is a tree then
With this change, explain why Algorithm 3.2 would return a minimum spanning
tree or why the algorithm would fail to do so.
3.10. This problem is concerned with improving the runtime of Kruskals Algorithm 3.2.
Explain how to use a priority queue to obviate the need for sorting the edges by
weight. Investigate the union-find data structure. Explain how to use union-find
to ensure that the addition of each edge results in an acyclic graph.
3.11. Figure 3.26 shows a weighted version of the Chvatal graph, which has 12 vertices and 24 edges. Use this graph as input to Kruskals, Prims, and Bor
uvkas
algorithms and compare the resulting minimum spanning trees.
3.12. Algorithm 3.1 presents a randomized procedure to construct a spanning tree of a
given connected graph via repeated edge deletion.
(a) Describe and present pseudocode of a randomized algorithm to grow a spanning tree via edge addition.
(b) Would Algorithm 3.1 still work if the input graph G has self-loops or multiple
edges? Explain why or why not. If not, modify Algorithm 3.1 to handle the
case where G has self-loops and multiple edges.
(c) Repeat the previous exercise for Kruskals, Prims, and Bor
uvkas algorithms.
146
11.4
40.7
17.1
14.4
5.6
35.4
5
4
14.5
15
9
11.8
8.5
3.7
48
11
10
0.2
9.1
27.1
6.9
17
43.2
10.2
22.1
22
42.7
36.6
44.2
Figure 3.26: Weighted Chvatal graph.
Algorithm 3.13: Random spanning tree of Kn .

Input: A positive integer n representing the order of Kn , with vertex set
V = {0, 1, . . . , n 1}.
Output: A random spanning tree of Kn .
1
2
3
4
5
6
7
8
if n = 1 then
return K1
P random permutation of V
T null tree
for i 1, 2, . . . , n 1 do
j random element from {0, 1, . . . , i 1}
add edge (P [j], P [i]) to T
return T
3.7. Problems
147
3.13. Algorithm 3.13 constructs a random spanning tree of the complete graph Kn on
n > 0 vertices. Its runtime is dependent on efficient algorithms for obtaining a
random permutation of a set of objects, and choosing a random element from a
given set.
(a) Describe and analyze the runtime of a procedure to construct a random permutation of a set of nonnegative integers.
(b) Describe an algorithm for randomly choosing an element of a set of nonnegative integers. Analyze the runtime of this algorithm.
(c) Taking into consideration the previous two algorithms, what is the runtime of
Algorithm 3.13?
3.14. We want to generate a random undirected, connected simple graph on n vertices
and having m edges. Start by generating a random spanning tree T of Kn . Then
add random edges to T until the requirements are satisfied.
(a) Present pseudocode to realize the above procedure. What is the worst-case
runtime of your algorithm?
(b) Modify your algorithm to handle the case where m < n 1. Why must
m n 1?
(c) Modify your algorithm to handle the case where each edge has a weight within
the closed interval [, ].
3.15. Enumerate all the different binary trees on 5 vertices.

3.16. Algorithm 3.5 generates a random binary tree on n > 0 vertices. Modify this
algorithm so that it generates a random k-ary tree of order n > 0, where k 3.
3.17. Show by giving an example that the Morse code is not prefix-free.
3.18. Consider the alphabet A = {a, b, c} with corresponding probabilities (or weights)
p(a) = 0.5, p(b) = 0.3, and p(c) = 0.2. Generate two different Huffman codes for
A and illustrate the tree representations of those codes.
3.19. Find the Huffman code for the letters of the English alphabet weighted by the
frequency of common American usage.4
3.20. Let G = (V1 , E2 ) be a graph and T = (V2 , E2 ) a spanning tree of G. Show that
there is a one-to-one correspondence between fundamental cycles in G and edges
not in T .
3.21. Let G = (V, E) be the 3 3 grid graph and T1 = (V1 , E1 ), T2 = (V2 , E2 ) be
spanning trees of G in Example 3.1. Find a fundamental cycle in G for T1 that is
not a fundamental cycle in G for T2 .
3.22. Usually there exist many spanning trees of a graph. Classify those graphs for
which there is only one spanning tree. In other words, find necessary and sufficient
conditions for a graph G such that if T is a spanning tree of G then T is unique.
4
You can find this on the Internet or in the literature. Part of this exercise is finding this frequency
distribution yourself.
148
3.23. Convert the function graycodeword into a pure Python function.

3.24. Example 3.13 verifies that for any positive integer n > 1, repeated iteration of
the Euler phi function (n) eventually produces 1. Show that this is the case or
provide an explanation why it is in general false.
3.25. The Collatz conjecture [125] asserts that for any integer n > 0, repeated iteration
of the function
( 3n+1
, if n is odd,
2
T (n) =
n
,
if n is even
2
eventually produces the value 1. For example, repeated iteration of T (n) starting
from n = 22 results in the sequence
22, 11, 17, 26, 13, 20, 10, 5, 8, 4, 2, 1.
(3.4)
One way to think about the Collatz conjecture is to consider the digraph G
produced by considering (ai , T (ai )) as a directed edge of G. Then the Collatz
conjecture can be rephrased to say that there is some integer k > 0 such that
(ak , T (ak )) = (2, 1) is a directed edge of G. The graph obtained in this manner is called the Collatz graph of T (n). Given a collection of positive integers
1 , 2 , . . . , k , let Gi be the Collatz graph of the function T (i ) with initial iteration value i . Then the union of the Gi is the directed tree
[
Gi
rooted at 1, called the Collatz tree of (1 , 2 , . . . , k ). Figure 3.27 shows such a

tree for the collection of initial iteration values 1024, 336, 340, 320, 106, 104, and
96. See Lagarias [126, 127] for a comprehensive survey of the Collatz conjecture.
(a) The Collatz sequence of a positive integer n > 1 is the integer sequence produced by repeated iteration of T (n) with initial iteration value n. For example,
the Collatz sequence of n = 22 is the sequence (3.4). Write a Sage function
to produce the Collatz sequence of an integer n > 1.
(b) The Collatz length of n > 1 is the number of terms in the Collatz sequence of
n, inclusive of the starting iteration value and the final integer 1. For instance,
the Collatz length of 22 is 12, that of 106 is 11, and that of 51 is 18. Write
a Sage function to compute the Collatz length of a positive integer n > 1. If
n > 1 is a vertex in a Collatz tree, verify that the Collatz length of n is the
distance d(n, 1).
(c) Describe the Collatz graph produced by the function T (n) with initial iteration
value n = 1.
(d) Fix a positive integer n > 1 and let Li be the Collatz length of the integer
1 i n. Plot the pairs (i, Li ) on one set of axes.
3.26. The following result was first published in Wiener [195]. Let T = (V, E) be a tree
of order n > 0. For each edge e E, let n1 (e) and n2 (e) = n n1 (e) be the orders
3.7. Problems
149
16
32
10
20
21
64
42
128
12
13
40
80
84
85
256
24
26
168
170
512
48
52
53
160
336
340
1024
96
104
106
320
Figure 3.27: The union of Collatz graphs is a tree.
150

of the two components of the edge-deletion subgraph T e. Show that the Wiener
number of T is
X
W (T ) =
n1 (e) n2 (e).
eE
3.27. The following result [145] was independently discovered in the late 1980s by Merris
and McKay, and is known as the Merris-McKay theorem. Let T be a tree of order
n and let L be its Laplacian matrix having eigenvalues 1 , 2 , . . . , n . Show that
the Wiener number of T is
n1
X
1
.
W (T ) = n
i
i=1
3.28. For each of the algorithms below: (i) justify whether or not it can be applied
to multigraphs or multidigraphs; (ii) if not, modify the algorithm so that it is
applicable to multigraphs or multidigraphs.
(a) Randomized spanning tree construction Algorithm 3.1.
(b) Kruskals Algorithm 3.2.
(c) Prims Algorithm 3.3.
(d) Bor
uvkas Algorithm 3.4.
3.29. Section 3.6 provides iterative algorithms for the following tree traversal techniques:
(a) Level-order traversal: Algorithm 3.8.
(b) Pre-order traversal: Algorithm 3.9.
(c) Post-order traversal: Algorithm 3.10.
(d) Bottom-up traversal: Algorithm 3.11.
(e) In-order traversal: Algorithm 3.12.
Rewrite each of the above as recursive algorithms.
3.30. In cryptography, the Merkle signature scheme [143] was introduced in 1987 as an
alternative to traditional digital signature schemes such as the Digital Signature
Algorithm or RSA. Buchmann et al. [39] and Szydlo [174] provide efficient algorithms for speeding up the Merkle signature scheme. Investigate this scheme and
how it uses binary trees to generate digital signatures.
3.31. Consider the finite alphabet A = {a1 , a2 , . . . , ar }. If C is a subset of A , then we say
that C is an r-ary code and call r the radix of the code. McMillans theorem [141],
first published in 1956, relates codeword lengths to unique decipherability. In
particular, let C = {c1 , c2 , . . . , cn } be an r-ary code where each ci has length ì . If
C is uniquely decipherable, McMillans theorem states that the codeword lengths
ì must satisfy Krafts inequality
n
X
1
1.
ì
r
i=1
Prove McMillans theorem.
3.7. Problems
151
3.32. A code C = {c1 , c2 , . . . , cn } is said to be instantaneous if each codeword ci can be

interpreted as soon as it is received. For example, given the the code {01, 010} and
the string 01010, upon receiving the first 0 we are unable to decide whether that
element belong to 01 or 010. However, the code {1, 01} is instantaneous because
given the string 1101 and the first 1, we can interpret the latter as the codeword
1. Prove that a code is instantaneous if and only if it is prefix-free.
3.33. Krafts inequality and the accompanying Krafts theorem were first published [122]
in 1949 in the Masters thesis of Leon Gordon Kraft. Krafts theorem relates the
inequality to instantaneous codes. Let C = {c1 , c2 , . . . , cn } be an r-ary code where
each codeword ci has length ì . Krafts theorem states that C is an instantaneous
code if and only if the codeword lengths satisfy
n
X
1
1.
ì
r
i=1
Prove Krafts theorem.

3.34. Let T be a nontrivial tree and P
let ni count the number of vertices of T that have
degree i. Show that T has 2 +
i=3 (i 2)ni leaves.
3.35. If a forest F has k trees totalling n vertices altogether, how many edges does F
contain?
3.36. The Lucas number Ln , named after Edouard

Lucas, has the following recursive
definition:
2,
if n = 0,
Ln = 1,
if n = 1,
Ln1 + Ln2 , if n > 1.
(a) If = (1 + 5)/2 is the golden ratio, show that

Ln = n + ()n .
(b) Let (Wn ) be the number of spanning trees of the wheel graph. Benjamin
and Yerger [23] provide a combinatorial proof that (Wn ) = L2n 2. Present
the Benjamin-Yerger combinatorial proof.
Chapter 4
Tree Data Structures
In Chapters 2 and 3, we discussed various algorithms that rely on priority queues as

one of their fundamental data structures. Such algorithms include Dijkstras algorithm,
Prims algorithm, and the algorithm for constructing Huffman trees. The runtime of
any algorithm that uses priority queues crucially depends on an efficient implementation
of the priority queue data structure. This chapter discusses the general priority queue
data structure and various efficient implementations based on trees. Section 4.1 provides
some theoretical underpinning of priority queues and considers a simple implementation
of priority queues as sorted lists. Section 4.2 discusses how to use binary trees to realize
an efficient implementation of priority queues called a binary heap. Although very useful
in practice, binary heaps do not lend themselves to being merged in an efficient manner,
a setback rectified in section 4.3 by a priority queue implementation called binomial
heaps. As a further application of binary trees, section 4.4 discusses binary search trees
as a general data structure for managing data in a sorted order.
152
4.1. Priority queues
4.1
153
Priority queues
A priority queue is essentially a queue data structure with various accompanying rules
regarding how to access and manage elements of the queue. Recall from section 2.2.1
that an ordinary queue Q has the following basic accompanying functions for accessing
and managing its elements:
dequeue(Q) Remove the front of Q.
enqueue(Q, e) Append the element e to the end of Q.
If Q is now a priority queue, each element is associated with a key or priority p X

from a totally ordered set X. A binary relation denoted by an infix operator, say ,
is defined on all elements of X such that the following properties hold for all a, b, c X:
Totality: We have a b or b a.
Antisymmetry: If a b and b a, then a = b.
Transitivity: If a b and b c, then a c.
If the above three properties hold for the relation , then we say that is a total
order on X and that X is a totally ordered set. In all, if the key of each element of
Q belongs to the same totally ordered set X, we use the total order defined on X to
compare the keys of the queue elements. For example, the set Z of integers is totally
ordered by the less than or equal to relation. If the key of each e Q is an element
of Z, we use the latter relation to compare the keys of elements of Q. In the case of an
ordinary queue, the key of each queue element is its position index.
To extract from a priority queue Q an element of lowest priority, we need to define
the notion of smallest priority or key. Let pi be the priority or key assigned to element
ei of Q. Then pmin is the lowest key if pmin p for any element key p. The element with
corresponding key pmin is the minimum priority element. Based upon the notion of key
comparison, we define two operations on a priority queue:
insert(Q, e, p) Insert into Q the element e with key p.
extractMin(Q) Extract from Q an element having the smallest priority.
An immediate application of priority queues is sorting a finite sequence of items.

Suppose L is a finite list of n > 0 items on which a total order is defined. Let Q be
an empty priority queue. In the first phase of the priority queue sorting algorithm,
we extract each element e L from L and insert e into Q with key e itself. In other
words, each element e is its own key. This first phase of the sorting algorithm requires
n element extractions from L and n element insertions into Q. The second phase of
the algorithm involves extracting elements from Q via the extractMin operation. Queue
elements are extracted via extractMin and inserted back into L in the order in which
they are extracted from Q. Algorithm 4.1 presents pseudocode of our discussion. The
runtime of Algorithm 4.1 depends on how the priority queue Q is implemented.
154
Chapter 4. Tree Data Structures
Algorithm 4.1: Sorting a sequence via priority queue.

Input: A finite list L of n > 0 elements on which a total order is defined.
Output: The same list L sorted by the total order relation defined on its
elements.
1
2
3
4
5
6
7
Q []
for i 1, 2, . . . , n do
e dequeue(L)
insert(Q, e, e)
for i 1, 2, . . . , n do
e extractMin(Q)
enqueue(L, e)
4.1.1
Sequence implementation
A simple way to implement a priority queue is to maintain a sorted sequence. Let

e0 , e1 , . . . , en be a sequence of n + 1 elements with corresponding keys 0 , 1 , . . . , n and
suppose that the i all belong to the same totally ordered set X having total order .
Using the total order, we assume that the i are sorted as
0 1 n
and ei ej if and only if i j . Then we consider the queue Q = [e0 , e1 , . . . , en ] as a
priority queue in which the head is always the minimum element and the tail is always
the maximum element. Extracting the minimum element is simply a dequeue operation
that can be accomplished in constant time O(1). However, inserting a new element into
Q takes linear time.
Let e be an element with corresponding key X. Inserting e into Q requires that
we maintain elements of Q sorted according to the total order . If Q is empty, we
simply enqueue e into Q. Suppose now that Q is a nonempty priority queue. If 0 ,
then e becomes the new head of Q. If n , then e becomes the new tail of Q. Inserting
a new head or tail into Q each requires constant time O(1). However, if 1 n1
then we need to traverse Q starting from e1 , searching for a position at which to insert e.
Let ei be the queue element at position i within Q. If i then we insert e into Q at
position i, thus moving ei to position i + 1. Otherwise we next consider ei+1 and repeat
the above comparison process. By hypothesis, 1 n1 and therefore inserting e
into Q takes a worst-case runtime of O(n).
4.2
Binary heaps
A sequence implementation of priority queues has the advantage of being simple to

understand. Inserting an element into a sequence-based priority queue requires linear
time, which can quickly become infeasible for queues containing hundreds of thousands
or even millions of elements. Can we do any better? Rather than using a sorted sequence,
we can use a binary tree to realize an implementation of priority queues that is much more
efficient than a sequence-based implementation. In particular, we use a data structure
called a binary heap, which allows for element insertion in logarithmic time.
In [196], Williams introduced the heapsort algorithm and described how to implement
a priority queue using a binary heap. A basic idea is to consider queue elements as
4.2. Binary heaps
155
internal vertices in a binary tree T , with external vertices or leaves being place-holders.
The tree T satisfies two further properties:
1. A relational property specifying the relative ordering and placement of queue elements.
2. A structural property that specifies the structure of T .
The relational property of T can be expressed as follows:
Definition 4.1. Heap-order property. Let T be a binary tree and let v be a vertex of
T other than the root. If p is the parent of v and these vertices have corresponding keys
p and v , respectively, then p v .
The heap-order property is defined in terms of the total order used to compare the
keys of the internal vertices. Taking the total order to be the ordinary less than or
equal to relation, it follows from the heap-order property that the root of T is always
the vertex with a minimum key. Similarly, if the total order is the usual greater than
or equal to relation, then the root of T is always the vertex with a maximum key. In
general, if is a total order defined on the keys of T and u and v are vertices of T , we
say that u is less than or equal to v if and only if u v. Furthermore, u is said to be
a minimum vertex of T if and only if u v for all vertices of T . From our discussion
above, the root is always a minimum vertex of T and is said to be at the top of the
heap, from which we derive the name heap for this data structure.
Another consequence of the heap-order property becomes apparent when we trace
out a path from the root of T to any internal vertex. Let r be the root of T and let v be
any internal vertex of T . If r, v0 , v1 , . . . , vn , v is an r-v path with corresponding keys
r , v0 , v1 , . . . , vn , v
then we have
r v0 v1 vn v .
In other words, the keys encountered on the path from r to v are arranged in nondecreasing order.
The structural property of T is used to enforce that T be of as small a height as
possible. Before stating the structural property, we first define the level of a binary tree.
Recall that the depth of a vertex in T is its distance from the root. Level i of a binary
tree T refers to all vertices of T that have the same depth i. We are now ready to state
the heap-structure property.
Definition 4.2. Heap-structure property. Let T be a binary tree with height h.
Then T satisfies the heap-structure property if T is nearly a complete binary tree. That
is, level 0 i h 1 has 2i vertices, whereas level h has 2h vertices. The vertices at
level h are filled from left to right.
If a binary tree T satisfies both the heap-order and heap-structure properties, then
T is referred to as a binary heap. By insisting that T satisfy the heap-order property,
we are able to determine the minimum vertex of T in constant time O(1). Requiring
that T also satisfy the heap-structure property allows us to determine the last vertex
of T . The last vertex of T is identified as the right-most internal vertex of T having
the greatest depth. Figure 4.1 illustrates various examples of binary heaps. The heapstructure property together with Theorem 3.16 result in the following corollary on the
height of a binary heap.
156
10
(a)
0
17
13
19
24
10
23
(b)
1
13
10
17
(c)
Figure 4.1: Examples of binary heaps with integer keys.
4.2. Binary heaps
157
Corollary 4.3. A binary heap T with n internal vertices has height

h = lg(n + 1) .
Proof. Level h 1 has at least one internal vertex. Apply Theorem 3.16 to see that T
has at least
2h2+1 1 + 1 = 2h1
internal vertices. On the other hand, level h 1 has at most 2h1 internal vertices.
Another application of Theorem 3.16 shows that T has at most
2h1+1 1 = 2h 1
internal vertices. Thus n is bounded by
2h1 n 2h 1.
Taking logarithms of each side in the latter bound results in
lg(n + 1) h lg n + 1
and the corollary follows.
0
0
10
17
13
19
24
23
10
(a)
(b)
10
13
17
(c)
Figure 4.2: Sequence representations of various binary heaps.
4.2.1
Sequence representation
Any binary heap can be represented as a binary tree. Each vertex in the tree must know
about its parent and its two children. However, a more common approach is to represent
a binary heap as a sequence such as a list, array, or vector. Let T be a binary heap
consisting of n internal vertices and let L be a list of n elements. The root vertex is
represented as the list element L[0]. For each index i, the children of L[i] are L[2i + 1]
and L[2i + 2] and the parent of L[i] is

i1
.
L
2
158
With a sequence representation of a binary heap, each vertex needs not know about
its parent and children. Such information can be obtained via simple arithmetic on
sequence indices. For example, the binary heaps in Figure 4.1 can be represented as the
corresponding lists in Figure 4.2. Note that it is not necessary to store the leaves of T
in the sequence representation.
4.2.2
Insertion and sift-up
We now consider the problem of inserting a vertex v into a binary heap T . If T is empty,
inserting a vertex simply involves the creation of a new internal vertex. We let that
new internal vertex be v and let its two children be leaves. The resulting binary heap
augmented with v has exactly one internal vertex and satisfies both the heap-order and
heap-structure properties, as shown in Figure 4.3. In other words, any binary heap with
one internal vertex trivially satisfies the heap-order property.
v
(a)
(b)
Figure 4.3: Inserting a vertex into an empty binary heap.

Let T now be a nonempty binary heap, i.e. T has at least one internal vertex, and
suppose we want to insert into T an internal vertex v. We must identify the correct leaf
of T at which to insert v. If the n internal vertices of T are r = v0 , v1 , . . . , vn1 , then by
the sequence representation of T we can identify the last internal vertex vn1 in constant
time. The correct leaf at which to insert v is the sequence element immediately following
vn1 , i.e. the element at position n in the sequence representation of T . We replace with
v the leaf at position n in the sequence so that v now becomes the last vertex of T .
The binary heap T augmented with the new last vertex v satisfies the heap-structure
property, but may violate the heap-order property. To ensure that T satisfies the heaporder property, we perform an operation on T called sift-up that involves possibly moving
v up through various levels of T . Let v be the key of v and let p(v) be the key of
vs parent. If the relation p(v) v holds, then T satisfies the heap-order property.
Otherwise we swap v with its parent, effectively moving v up one level to be at the
position previously occupied by its parent. The parent of v is moved down one level
and now occupies the position where v was previously. With v in its new position, we
perform the same key comparison process with vs new parent. The key comparison and
swapping continue until the heap-order property holds for T . In the worst case, v would
become the new root of T after undergoing a number of swaps that is proportional to the
height of T . Therefore, inserting a new internal vertex into T can be achieved in time
O(lg n). Figure 4.4 illustrates the insertion of a new internal vertex into a nonempty
binary heap and the resulting sift-up operation to maintain the heap-order property.
Algorithm 4.2 presents pseudocode of our discussion for inserting a new internal vertex
into a nonempty binary heap. The pseudocode is adapted from Howard [102], which
provides a C implementation of binary heaps.
4.2. Binary heaps
159
6
17
4
13
19
8
24
2
10
23
6
17
4
13
19
8
24
(a)
17
3
4
13
19
8
24
23
2
10
6
17
4
13
19
0
24
(c)
3
4
13
19
0
24
23
2
10
6
17
4
13
19
3
24
(e)
0
4
13
19
3
24
(g)
17
23
10
(f)
1
17
23
10
(d)
1
(b)
1
23
10
23
2
10
6
17
4
13
19
3
24
(h)
Figure 4.4: Insert and sift-up in a binary heap.
23
10
8
160
Algorithm 4.2: Inserting a new internal vertex into a binary heap.

Input: A nonempty binary heap T , in sequence representation, having n internal
vertices. An element v that is to be inserted as a new internal vertex of T .
Output: The binary heap T augmented with the new internal vertex v.
1
2
3
4
5
6
7
8
9
10
in
while i > 0 do
p b(i 1)/2c
if T [p] v then
exit the loop
else
T [i] T [p]
ip
T [i] v
return T
4.2.3
Deletion and sift-down
The process for deleting the minimum vertex of a binary heap bears some resemblance
to that of inserting a new internal vertex into the heap. Having removed the minimum
vertex, we must then ensure that the resulting binary heap satisfies the heap-order
property. Let T be a binary heap. By the heap-order property, the root of T has a
key that is minimum among all keys of internal vertices in T . If the root r of T is the
only internal vertex of T , i.e. T is the trivial binary heap, we simply remove r and T now
becomes the empty binary heap or the trivial tree, for which the heap-order property
vacuously holds. Figure 4.5 illustrates the case of removing the root of a binary heap
having one internal vertex.
r
(a)
(b)
Figure 4.5: Deleting the root of a trivial binary heap.

We now turn to the case where T has n > 1 internal vertices. Let r be the root
of T and let v be the last internal vertex of T . Deleting r would disconnect T . So we
instead replace the key and information at r with the key and other relevant information
pertaining to v. The root r now has the key of the last internal vertex, and v becomes
a leaf.
At this point, T satisfies the heap-structure property but may violate the heap-order
property. To restore the heap-order property, we perform an operation on T called siftdown that may possibly move r down through various levels of T . Let c(r) be the child of
r with key that is minimum among all the children of r, and let r and c(r) be the keys of
r and c(r), respectively. If r c(r) , then the heap-order property is satisfied. Otherwise
we swap r with c(r), moving r down one level to the position previously occupied by
c(r). Furthermore, c(r) is moved up one level to the position previously occupied by r.
With r in its new position, we perform the same key comparison process with a child of
4.2. Binary heaps
161
r that has minimum key among all of rs children. The key comparison and swapping
continue until the heap-order property holds for T . In the worst case, r would percolate
all the way down to the level that is immediately above the last level after undergoing a
number of swaps that is proportional to the height of T . Therefore, deleting the minimum
vertex of T can be achieved in time O(lg n). Figure 4.6 illustrates the deletion of the
minimum vertex of a binary heap with at least two internal vertices and the resulting
sift-down process that percolates vertices down through various levels of the heap in order
to maintain the heap-order property. Algorithm 4.3 summarizes our discussion of the
process for extracting the minimum vertex of T while also ensuring that T satisfies the
heap-order property. The pseudocode is adapted from the C implementation of binary
heaps in Howard [102]. With some minor changes, Algorithm 4.3 can be used to change
the key of the root vertex and maintain the heap-order property for the resulting binary
tree.
Algorithm 4.3: Extract the minimum vertex of a binary heap.
Input: A binary heap T , given in sequence representation, having n > 1 internal
vertices.
Output: Extract the minimum vertex of T . With one vertex removed, T must
satisfy the heap-order property.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
root T [0]
nn1
v T [n]
i0
j0
while True do
left 2i + 1
right 2i + 2
if left < n and T [left] v then
if right < n and T [right] T [left] then
j right
else
j left
else if right < n and T [right] v then
j right
else
T [i] v
exit the loop
T [i] T [j]
ij
return root
4.2.4
Constructing a binary heap
Given a collection of n vertices v0 , v1 , . . . , vn1 with corresponding keys 0 , 1 , . . . , n1 ,

we want to construct a binary heap containing exactly those vertices. A basic approach
is to start with a trivial tree and build up a binary heap via successive insertions. As each
162
23
6
17
4
13
19
8
24
2
10
23
6
17
4
13
19
8
24
(a)
(b)
23
6
17
4
13
19
23
10
24
6
17
4
13
19
(d)
2
23
17
3
4
13
19
4
10
24
6
17
23
13
19
(f)
2
17
23
13
19
8
24
(g)
10
24
(e)
10
24
(c)
10
4
10
6
17
19
13
23
8
24
(h)
Figure 4.6: Delete and sift-down in a binary heap.
10
4.2. Binary heaps
163
insertion requires O(lg n) time, the method of binary heap construction via successive
insertion of each of the n vertices requires O(n lg n) time. It turns out we could do a
bit better and achieve the same result in linear time.
Algorithm 4.4: Heapify a binary tree.
Input: A binary tree T , given in sequence representation, having n > 1 internal
vertices.
Output: The binary tree T heapified so that it satisfies the heap-order property.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
for i bn/2c 1, . . . , 0 do
v T [i]
j0
while True do
left 2i + 1
right 2i + 2
if left < n and T [left] v then
if right < n and T [right] T [left] then
j right
else
j left
else if right < n and T [right] v then
j right
else
T [i] v
exit the while loop
T [i] T [j]
ij
return T
A better approach starts by letting v0 , v1 , . . . , vn1 be the internal vertices of a binary

tree T . The tree T need not satisfy the heap-order property, but it must satisfy the heapstructure property. Suppose T is given in sequence representation so that we have the
correspondence vi = T [i] and the last internal vertex of T has index n 1. The parent
of T [n 1] has index

n1
.
j=
2
Any vertex of T with sequence index beyond n 1 is a leaf. In other words, if an internal
vertex has index > j, then the children of that vertex are leaves and have indices n.
Thus any internal vertex with index bn/2c has leaves for its children. Conclude that
internal vertices with indices
jnk jnk
jnk
,
+ 1,
+ 2, . . . , n 1.
(4.1)
2
2
2
have only leaves for their children.

Our next task is to ensure that the heap-order property holds for T . If v is an
internal vertex with index in (4.1), then the subtree rooted at v is trivially a binary
heap. Consider the indices from bn/2c 1 all the way down to 0 and let i be such an
index, i.e. let 0 i bn/2c 1. We heapify the subtree of T rooted at T [i], effectively
164
performing a sift-down on this subtree. Once we have heapified all subtrees rooted at
T [i] for 0 i bn/2c 1, the resulting tree T is a binary heap. Our discussion is
summarized in Algorithm 4.4.
Earlier in this section, we claimed that Algorithm 4.4 can be used to construct a
binary heap in worst-case linear time. To prove this, let T be a binary tree satisfying the
heap-structure property and having n internal vertices. By Corollary 4.3, T has height
h = dlg(n + 1)e. We perform a sift-down for at most 2i vertices of depth i, where each
sift-down for a subtree rooted at a vertex of depth i takes O(h i) time. Then the total
time for Algorithm 4.4 is
!
!
X
X 2i
O
2i (h i) = O 2h
2hi
0i<h
0i<h
!
X k
= O 2h
2k
k>0

= O 2h+1
= O(n)
where we used the closed form
4.3
k>0
k/2k = 2 for a geometric series and Theorem 3.16.
Binomial heaps
We are given two binary heaps T1 and T2 and we want to merge them into a single heap.
We could start by choosing to insert each element of T2 into T1 , successively extracting
the minimum element from T2 and insert that minimum element into T1 . If T1 and T2
have m and n elements, respectively, we would perform n extractions from T2 totalling
!
X
O
lg k
0<kn
time and inserting all of the extracted elements from T2 into T1 requires a total runtime
of
!
X
O
lg k .
(4.2)
nk<n+m
We approximate the addition of the two sums by

Z
n+m
k=n+m

k ln k k
+ C
lg k dk =
ln 2
k=0
for some constant C. The above method of successive extraction and insertion therefore
has a total runtime of

(n + m) ln(n + m) n m
O
ln 2
for merging two binary heaps.
Alternatively, we could slightly improve the latter runtime for merging T1 and T2 by
successively extracting the last internal vertex of T2 . The whole process of extracting
4.3. Binomial heaps
165
all elements from T2 in this way takes O(n) time and inserting each of the extracted
elements into T1 still requires the runtime in expression (4.2). We approximate the sum
in (4.2) by
k=n+m
Z k=n+m

k ln k k
lg k dk =
+ C
ln 2
k=n
k=n
for some constant C. Therefore the improved extraction and insertion method requires

(n + m) ln(n + m) n ln n m
O
n
ln 2
time in order to merge T1 and T2 .

Can we improve on the latter runtime for merging two binary heaps? It turns out we
can by using a type of mergeable heap called binomial heap that supports merging two
heaps in logarithmic time.
4.3.1
Binomial trees
A binomial heap can be considered as a collection of binomial trees. The binomial tree
of order k is denoted Bk and defined recursively as follows:
1. The binomial tree of order 0 is the trivial tree.
2. The binomial tree of order k > 0 is a rooted tree, where from left to right the
children of the root of Bk are roots of Bk1 , Bk2 , . . . , B0 .
Various examples of binomial trees are shown in Figure 4.7. The binomial tree Bk can
also be defined as follows. Let T1 and T2 be two copies of Bk1 with root vertices r1
and r2 , respectively. Then Bk is obtained by letting, say, r1 be the left-most child of r2 .
Lemma 4.4 lists various basic properties of binomial trees. Property (3) of Lemma 4.4
uses the binomial coefficient, from whence Bk derives its name.
Lemma 4.4. Basic properties of binomial trees. Let Bk be a binomial tree of
order k 0. Then the following properties hold:
1. The order of Bk is 2k .
2. The height of Bk is k.
3. For 0 i k, we have
k
i
vertices at depth i.
4. The root of Bk is the only vertex with maximum degree (Bk ) = k. If the children
of the root are numbered k 1, k 2, . . . , 0 from left to right, then child i is the
root of the subtree Bi .
Proof. We use induction on k. The base case for each of the above properties is B0 ,
which trivially holds.
(1) By our inductive hypothesis, Bk1 has order 2k1 . Since Bk is comprised of two
copies of Bk1 , conclude that Bk has order
2k1 + 2k1 = 2k .
166
(a) B0
(b) B1
(c) B2
(d) B3
(e) B4
(f) B5
Figure 4.7: Binomial trees Bk for k = 0, 1, 2, 3, 4, 5.
4.3. Binomial heaps
167
(2) The binomial tree Bk is comprised of two copies of Bk1 , the root of one copy
being the left-most child of the root of the other copy. Then the height of Bk is one
greater than the height of Bk1 . By our inductive hypothesis, Bk1 has height k 1 and
therefore Bk has height (k 1) + 1 = k.
(3) Denote by D(k, i) the number of vertices of depth i in Bk . As Bk is comprised
of two copies of Bk1 , a vertex at depth i in Bk1 appears once in Bk at depth i and a
second time at depth i + 1. By our inductive hypothesis,
D(k, i) = D(k 1, i) + D(k 1, i 1)

k1
k1
=
+
i
i1

k
=
i
where we used Pascals formula which states that

n+1
n
n
=
+
r
r1
r
for any positive integers n and r with r n.
(4) This property follows from the definition of Bk .
Corollary 4.5. If a binomial tree has order n 0, then the degree of any vertex i is
bounded by deg(i) lg n.
Proof. Apply properties (1) and (4) of Lemma 4.4.
4.3.2
Binomial heaps
In 1978, Jean Vuillemin [186] introduced binomial heaps as a data structure for implementing priority queues. Mark R. Brown [37, 38] subsequently extended Vuillemins
work, providing detailed analysis of binomial heaps and introducing an efficient implementation.
A binomial heap H can be considered as a collection of binomial trees. Each vertex
in H has a corresponding key and all vertex keys of H belong to a totally ordered set
having total order . The heap also satisfies the following binomial heap properties:
Heap-order property. Let Bk be a binomial tree in H. If v is a vertex of Bk
other than the root and p is the parent of v and having corresponding keys v and
p , respectively, then p v .
Root-degree property. For any integer k 0, H contains at most one binomial
tree whose root has degree k.
If H is comprised of the binomial trees Bk0 , Bk1 , . . . , Bkn for nonnegative integers ki ,
we can consider H as a forest made up of the trees Bki . We can also represent H as a tree
in the following way. List the binomial trees of H as Bk0 , Bk1 , . . . , Bkn in nondecreasing
order of root degrees, i.e. the root of Bki has order less than or equal to the root of Bkj
if and only if ki kj . The root of H is the root of Bk0 and the root of each Bki has
for its child the root of Bki+1 . Both the forest and tree representations are illustrated in
Figure 4.8 for the binomial heap comprised of the binomial trees B0 , B1 , B3 .
168
(a) Binomial heap as a forest.
(b) Binomial heap as a tree.
Figure 4.8: Forest and tree representations of a binomial heap.

The heap-order property for binomial heaps is analogous to the heap-order property
for binary heaps. In the case of binomial heaps, the heap-order property implies that
the root of a binomial tree has a key that is minimum among all vertices in that tree.
However, the similarity more or less ends there. In a tree representation of a binomial
heap, the root of the heap may not necessarily have the minimum key among all vertices
of the heap.
The root-degree property can be used to derive an upper bound on the number of
binomial trees in a binomial heap. If H is a binomial heap with n vertices, then H has
at most 1 + blg nc binomial trees. To prove this result, note that (see Theorem 2.1 and
Corollary 2.1.1 in [162, pp.4042]) n can be uniquely written in binary representation as
the polynomial
n = ak 2k + ak1 2k1 + + a1 21 + a0 20 .
Pblg nc i
ai 2 . Apply
The binary representation of n requires 1 + blg nc bits, hence n = i=0
property (1) of Lemma 4.4 to see that the binomial tree Bi is in H if and only if the i-th
bit is bi = 1. Conclude that H has at most 1 + blg nc binomial trees.
4.3.3
Construction and management
Let H be a binomial heap comprised of the binomial trees Bk0 , Bk1 , . . . , Bkn where the
root of Bki has order less than or equal to the root of Bkj if and only if ki kj .
Denote by rki the root of the binomial tree Bki . If v is a vertex of H, denote by
child[v] the left-most child of v and by sibling[v] we mean the sibling immediately to
the right of v. Furthermore, let parent[v] be the parent of v and let degree[v] denote
the degree of v. If v has no children, we set child[v] = NULL. If v is one of the roots
rki , we set parent[v] = NULL. And if v is the right-most child of its parent, then we set
sibling[v] = NULL.
The roots rk0 , rk1 , . . . , rkn can be organized as a linked list, called a root list, with
two functions for accessing the next root and the previous root. The root immediately
following rki is denoted next[rki ] = sibling[v] = rki+1 and the root immediately before rki
is written prev[rki ] = rki1 . For rk0 and rkn , we set next[rkn ] = sibling[v] = NULL and
prev[rk0 ] = NULL. We also define the function head[H] that simply returns rk0 whenever
H has at least one element, and head[H] = NULL otherwise.
4.3. Binomial heaps
169
Minimum vertex
To find the minimum vertex, we find the minimum among rk0 , rk1 , . . . , rkm because by
definition the root rki is the minimum vertex of the binomial tree Bki . If H has n vertices,
we need to check at most 1 + blg nc vertices to find the minimum vertex of H. Therefore
determining the minimum vertex of H takes O(lg n) time. Algorithm 4.5 summarizes
our discussion.
Algorithm 4.5: Determine the minimum vertex of a binomial heap.
Input: A binomial heap H of order n > 0.
Output: The minimum vertex of H.
1
2
3
4
5
6
7
8
9
u NULL
v head[H]
min
while v 6= NULL do
if v < min then
min v
uv
v sibling[v]
return u
Merging heaps
Recall that Bk is constructed by linking the root of one copy of Bk1 with the root of
another copy of Bk1 . When merging two binomial heaps whose roots have the same
degree, we need to repeatedly link the respective roots. The root linking procedure runs
in constant time O(1) and is rather straightforward, as presented in Algorithm 4.6.
Algorithm 4.6: Linking the roots of binomial heaps.
Input: Two copies of Bk1 , one rooted at u and the other at v.
Output: The respective roots of two copies of Bk1 linked, with one root
becoming the parent of the other.
1
2
3
4
parent[u] v
sibling[u] child[v]
child[v] u
degree[v] degree[v] + 1
Besides linking the roots of two copies of Bk1 , we also need to merge the root lists
of two binomial heaps H1 and H2 . The resulting merged list is sorted in nondecreasing
order of degree. Let L1 be the root list of H1 and let L2 be the root list of H2 . First
we create an empty list L. As the lists Li are already sorted in nondecreasing order of
vertex degree, we use merge sort to merge the Li into a single sorted list. The whole
procedure for merging the Li takes linear time O(n), where n = |L1 | + |L2 | 1. Refer to
Algorithm 4.7 for pseudocode of the procedure just described.
Having clarified the root linking and root lists merging procedures, we are now ready
to describe a procedure for merging two nonempty binomial heaps H1 and H2 into a
170
Algorithm 4.7: Merging two root lists.

Input: Two root lists L1 and L2 , each containing the roots of binomial trees in
the binomial heaps H1 and H2 , respectively. Each root list Li is sorted in
increasing order of vertex degree.
Output: A single list L that merges the root lists Li and sorted in nondecreasing
order of degree.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
i1
j1
L []
n |L1 | + |L2 | 1
append(L1 , )
append(L2 , )
for k 0, 1, . . . , n do
if deg(L1 [i]) deg(L2 [j]) then
append(L, L1 [i])
ii+1
else
append(L, L2 [j])
j j+1
return L
single binomial heap H. Initially there are at most two copies of B0 , one from each of
the Hi . If two copies of B0 are present, we let the root of one be the parent of the other
as per Algorithm 4.6, producing B1 as a result. From thereon, we generally have at most
three copies of Bk for some integer k > 0: one from H1 , one from H2 , and the third from
a previous merge of two copies of Bk1 . In the presence of two or more copies of Bk , we
merge two copies as per Algorithm 4.6 to produce Bk+1 . If Hi has ni vertices, then Hi
has at most 1 + blg ni c binomial trees, from which it is clear that merging H1 and H2
requires
max(1 + blg n1 c, 1 + blg n2 c)
steps. Letting N = max(n1 , n2 ), we see that merging H1 and H2 takes logarithmic time
O(lg N ). The operation of merging two binomial heaps is presented in pseudocode as
Algorithm 4.8, which is adapted from Cormen et al. [54, p.463] and the C implementation
of binomial queues in [102]. A word of warning is order here. Algorithm 4.8 is destructive
in the sense that it modifies the input heaps Hi in-place without making copies of those
heaps.
Vertex insertion
Let v be a vertex with corresponding key v and let H1 be a binomial heap of n vertices.
The single vertex v can be considered as a binomial heap H2 comprised of exactly the
binomial tree B0 . Then inserting v into H1 is equivalent to merging the heaps Hi and
can be accomplished in O(lg n) time. Refer to Algorithm 4.9 for pseudocode of this
straightforward procedure.
4.3. Binomial heaps
Algorithm 4.8: Merging two binomial heaps.

Input: Two binomial heaps H1 and H2 .
Output: A binomial heap H that results from merging the Hi .
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
H empty binomial heap

head[H] merge sort the root lists of H1 and H2
if head[H] = NULL then
return H
prevv NULL
v head[H]
nextv sibling[v]
while nextv 6= NULL do
if degree[v] 6= degree[nextv] or (sibling[nextv] 6= NULL and
degree[sibling[nextv]] = degree[v]) then
prevv v
v nextv
else if v nextv then
sibling[v] sibling[nextv]
link the roots nextv and v as per Algorithm 4.6
else
if prevv = NULL then
head[H] nextv
else
sibling[prevv] nextv
link the roots v and nextv as per Algorithm 4.6
v nextv
nextv sibling[v]
return H
Algorithm 4.9: Insert a vertex into a binomial heap.

Input: A binomial heap H and a vertex v.
Output: The heap H with v inserted into it.
1
2
3
4
5
6
7
H1 empty binomial heap

head[H1 ] v
parent[v] NULL
child[v] NULL
sibling[v] NULL
degree[v] 0
H merge H and H1 as per Algorithm 4.8
171
172
Delete minimum vertex

Extracting the minimum vertex from a binomial heap H consists of several phases.
Let H be comprised of the binomial trees Bk0 , Bk1 , . . . , Bkm with corresponding roots
rk0 , rk1 , . . . , rkm and let n be the number of vertices in H. In the first phase, from among
the rki we identify the root v with minimum key and remove v from H, an operation
that runs in O(lg n) time because we need to process at most 1 + blg nc roots. With the
binomial tree Bk rooted at v thus severed from H, we now have a forest consisting of the
heap without Bk (denote this heap by H1 ) and the binomial tree Bk . By construction,
v is the root of Bk and the children of v from left to right can be considered as roots
of binomial trees as well, say B`s , B`s1 , . . . , B`0 where `s > `s1 > > `0 . Now
sever the root v from its children. The B`j together can be viewed as a binomial heap
H2 with, from left to right, binomial trees B`0 , B`1 , . . . , B`s . Finally the binomial heap
resulting from removing v can be obtained by merging H1 and H2 in O(lg n) time as per
Algorithm 4.8. In total we can extract the minimum vertex of H in O(lg n) time. Our
discussion is summarized in Algorithm 4.10 and an illustration of the extraction process
is presented in Figure 4.9.
Algorithm 4.10: Extract the minimum vertex from a binomial heap.
Input: A binomial heap H.
Output: The minimum vertex of H removed.
1
2
3
4
5
6
v extract minimum vertex from root list of H

H2 empty binomial heap
L list of vs children reversed
head[H2 ] L[0]
H merge H and H2 as per Algorithm 4.8
return v
4.4
Binary search trees
A binary search tree (BST) is a rooted binary tree T = (V, E) having vertex weight
function : V R. The weight of each vertex v is referred to as its key, denoted v .
Each vertex v of T satisfies the following properties:
Left subtree property. The left subtree of v contains only vertices whose keys
are at most v . That is, if u is a vertex in the left subtree of v, then u v .
Right subtree property. The right subtree of v contains only vertices whose
keys are at least v . In other words, any vertex u in the right subtree of v satisfies
v u .
Recursion property. Both the left and right subtrees of v must also be binary
search trees.
The above are collectively called the binary search tree property. See Figure 4.10 for
an example of a binary search tree. Based on the binary search tree property, we can
use in-order traversal (see Algorithm 3.12) to obtain a listing of the vertices of a binary
search tree sorted in nondecreasing order of keys.
4.4. Binary search trees
70
173
60
65
67
66
40
68
41
69
45
43
48
44
49
47
11
12
15
10
(a)
70
60
65
67
66
40
68
41
69
45
43
48
44
49
47
11
12
15
10
(b)
70
65
67
60
66
40
68
69
41
45
43
48
44
15
49
12
47
11
10
(c)
5
70
65
67
15
60
66
69
68
12
40
41
45
43
48
49
44
11
10
47
(d)
Figure 4.9: Extracting the minimum vertex from a binomial heap.
174

10
15
13
20
11
Figure 4.10: A binary search tree.
4.4.1
Searching
Given a BST T and a key k, we want to locate a vertex (if one exists) in T whose key is k.
The search procedure for a BST is reminiscent of the binary search algorithm discussed
in problem 2.10. We begin by examining the root v0 of T . If v0 = k, the search is
successful. However, if v0 6= k then we have two cases to consider. In the first case, if
k < v0 then we search the left subtree of v0 . The second case occurs when k > v0 , in
which case we search the right subtree of v0 . Repeat the process until a vertex v in T
is found for which k = v or the indicated subtree is empty. Whenever the target key
is different from the key of the vertex we are currently considering, we move down one
level of T . Thus if h is the height of T , it follows that searching T takes a worst-case
runtime of O(h). The above procedure is presented in pseudocode as Algorithm 4.11.
Note that if a vertex v does not have a left subtree, the operation of locating the root
of vs left subtree should return NULL. A similar comment applies when v does not have
a right subtree. Furthermore, from the structure of Algorithm 4.11, if the input BST is
empty then NULL is returned. See Figure 4.11 for an illustration of locating vertices with
given keys in a BST.
Algorithm 4.11: Locate a key in a binary search tree.
Input: A binary search tree T and a target key k.
Output: A vertex in T with key k. If no such vertex exists, return NULL.
1
2
3
4
5
6
7
v root[T ]
while v 6= NULL and k 6= v do
if k < v then
v leftchild[v]
else
v rightchild[v]
return v
From the binary search tree property, deduce that a vertex of a BST T with minimum
key can be found by starting from the root of T and repeatedly traversing left subtrees.
When we have reached the left-most vertex v of T , querying for the left subtree of v
should return NULL. At this point, we conclude that v is a vertex with minimum key.
Each query for the left subtree moves us one level down T , resulting in a worst-case
runtime of O(h) with h being the height of T . See Algorithm 4.12 for pseudocode of the
procedure.
The procedure for finding a vertex with maximum key is analogous to that for finding
175
10
10
15
13
11
20
19
23
15
22
26
(a) Vertex with key 6: search fail.
13
11
20
19
23
22
26
(b) Vertex with key 22: search success.
Figure 4.11: Finding vertices with given keys in a BST.
10
10
15
13
11
20
19
23
15
22
26
13
11
20
19
23
(a) Minimum vertex.
22
26
(b) Maximum vertex.
Figure 4.12: Locating minimum and maximum vertices in a BST.
10
10
15
13
11
20
19
(a) Successor of 9.
15
23
22
26
13
11
20
19
(b) Predecessor of 11.
Figure 4.13: Searching for successor and predecessor.
23
22
26
176
one with minimum key. Starting from the root of T , we repeatedly traverse right subtrees
until we encounter the right-most vertex, which by the binary search tree property has
maximum key. This procedure has the same worst-case runtime of O(h). Figure 4.12
illustrates the process of locating the minimum and maximum vertices of a BST.
Algorithm 4.12: Finding a vertex with minimum key in a BST.
Input: A nonempty binary search tree T .
Output: A vertex of T with minimum key.
1
2
3
4
v root of T
while leftchild[v] 6= NULL do
v leftchild[v]
return v
Corresponding to the notions of left- and right-children, we can also define successors
and predecessors as follows. Suppose v is not a maximum vertex of a nonempty BST
T . The successor of v is a vertex in T distinct from v with the smallest key greater
than or equal to v . Similarly, for a vertex v that is not a minimum vertex of T , the
predecessor of v is a vertex in T distinct from v with the greatest key less than or equal
to v . The notions of successors and predecessors are concerned with relative key order,
not a vertexs position within the hierarchical structure of a BST. For instance, from
Figure 4.10 we see that the successor of the vertex u with key 8 is the vertex v with key
10, i.e. the root, even though v is an ancestor of u. The predecessor of the vertex a with
key 4 is the vertex b with key 3, i.e. the minimum vertex, even though b is a descendant
of a.
We now describe a method to systematically locate the successor of a given vertex.
Let T be a nonempty BST and v V (T ) not a maximum vertex of T . If v has a right
subtree, then we find a minimum vertex of vs right subtree. In case v does not have
a right subtree, we backtrack up one level to vs parent u = parent(v). If v is the root
of the right subtree of u, we backtrack up one level again to us parent, making the
assignments v u and u parent(u). Otherwise we return vs parent. Repeat the
above backtracking procedure until the required successor is found. Our discussion is
summarized in Algorithm 4.13. Each time we backtrack to a vertexs parent, we move
up one level, hence the worst-case runtime of Algorithm 4.13 is O(h) with h being the
height of T . The procedure for finding predecessors is similar. Refer to Figure 4.13 for
an illustration of locating successors and predecessors.
4.4.2
Insertion
Inserting a vertex v into a BST T is rather straightforward. If T is empty, we let v be the

root of T . Otherwise T has at least one vertex. In that case, we need to locate a vertex
in T that can act as a parent and adopt v as a child. To find a candidate parent, let
u be the root of T . If v < u then we assign the root of the left subtree of u to u itself.
Otherwise we assign the root of the right subtree of u to u. We then carry on the above
key comparison process until the operation of locating the root of a left or right subtree
returns NULL. At this point, a candidate parent for v is the last non-NULL value of u. If
v < u then we let v be us left-child. Otherwise v is the right-child of u. After each key
comparison, we move down at most one level so that in the worst-case inserting a vertex
177
Algorithm 4.13: Finding successors in a binary search tree.

Input: A nonempty binary search tree T and a vertex v that is not a maximum
of T .
Output: The successor of v.
1
2
3
4
5
6
7
if rightchild[v] 6= NULL then

return minimum vertex of vs right subtree as per Algorithm 4.12
u parent(v)
while u 6= NULL and v = rightchild[u] do
vu
u parent(u)
return u
into T takes O(h) time, where h is the height of T . Algorithm 4.14 presents pseudocode
of our discussion and Figure 4.14 illustrates how to insert a vertex into a BST.
Algorithm 4.14: Inserting a vertex into a binary search tree.
Input: A binary search tree T and a vertex x to be inserted into T .
Output: The same BST T but augmeneted with x.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
u NULL
v root of T
while v 6= NULL do
uv
if x < v then
v leftchild[v]
else
v rightchild[v]
parent[x] u
if u = NULL then
root[T ] x
else
if x < u then
leftchild[u] x
else
rightchild[u] x
4.4.3
Deletion
Whereas insertion into a BST is straightforward, removing a vertex requires much more
work. Let T be a nonempty binary search tree and suppose we want to remove v V (T )
from T . Having located the position that v occupies within T , we need to consider three
separate cases: (1) v is a leaf; (2) v has one child; (3) v has two children.
1. If v is a leaf, we simply remove v from T and the procedure is complete. The
resulting tree without v satisfies the binary search tree property.
178
10
10
15
13
11
15
20
19
23
22
26
(a)
13
11
20
19
12
23
22
26
(b)
Figure 4.14: Inserting into a binary search tree.
Algorithm 4.15: Deleting a vertex from a binary search tree.

Input: A nonempty binary search tree T and a vertex x V (T ) to be removed
from T .
Output: The same BST T but without x.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
u NULL
v NULL
if leftchild[x] 6= NULL or rightchild[x] 6= NULL then
vx
else
v successor of x
if leftchild[v] 6= NULL then
u leftchild[v]
else
u rightchild[v]
if u 6= NULL then
parent[u] parent[v]
if parent[v] = NULL then
root[T ] u
else
if v = leftchild[parent[v]] then
leftchild[parent[v]] u
else
rightchild[parent[v]] u
if v 6= x then
x v
copy vs auxilary data into x
4.5. AVL trees
179
2. Suppose v has the single child u. Removing v would disconnect T , a situation that
can be prevented by splicing out u and letting u occupy the position previously
held by v. The resulting tree with v removed as described satisfies the binary
search tree property.
3. Finally suppose v has two children and let s and p be the successor and predecessor
of v, respectively. It can be shown that s has no left-child and p has no right-child.
We can choose to either splice out s or p. Say we choose to splice out s. Then we
remove v and let s hold the position previously occupied by v. The resulting tree
with v thus removed satisfies the binary search tree property.
The above procedure is summarized in Algorithm 4.15, which is adapted from [54, p.262].
Figure 4.15 illustrates the various cases to be considered when removing a vertex from
a BST. Note that in Algorithm 4.15, the process of finding the successor dominates the
runtime of the entire algorithm. Other operations in the algorithm take at most constant
time. Therefore deleting a vertex from a binary search tree can be accomplished in worstcase O(h) time, where h is the height of the BST under consideration.
4.5
AVL trees
To motivate the need for AVL trees, note the lack of a structural property for binary
search trees similar to the structural property for binary heaps. Unlike binary heaps,
a BST is not required to have as small a height as possible. As a consequence, any
given nonempty collection C = {v0 , v1 , . . . , vk } of weighted vertices can be represented by
various BSTs with different heights; see Figure 4.16. Some BST representations of C have
heights smaller than other BST representations of C. Those BST representations with
smaller heights can result in reduced time for basic operations such as search, insertion,
and deletion and out-perform BST representations having larger heights. To achieve
logarithmic or near-logarithmic time complexity for basic operations, it is desirable to
maintain a BST with as small a height as possible.
Adelson-Velski and Landis [1] introduced in 1962 a criterion for constructing and
maintaining binary search trees having logarithmic heights. Recall that the height of a
tree is the maximum depth of the tree. Then the Adelson-Velski-Landis criterion can
be expressed as follows.
Definition 4.6. Height-balance property. Let T be a binary tree and suppose v is
an internal vertex of T . Let h` be the height of the left subtree of v and let hr be the
height of vs right subtree. Then v is said to be height-balanced if |h` hr | 1. For each
internal vertex u of T , if u is height-balanced then the whole tree T is height-balanced.
Binary trees having the height-balance property are called AVL trees. The structure
of such trees is such that given any internal vertex v of an AVL tree, the heights of the
left and right subtrees of v differ by at most 1. Complete binary trees are trivial examples
of AVL trees, as are nearly complete binary trees. A less trivial example of AVL trees
are what is known as Fibonacci trees, so named because the construction of Fibonacci
trees bears some resemblance to how Fibonacci numbers are produced. Fibonacci trees
can be constructed recursively in the following manner. The Fibonacci tree F0 of height
0 is the trivial tree. The Fibonacci tree F1 of height 1 is a binary tree whose left and
right subtrees are both F0 . For n > 1, the Fibonacci tree Fn of height n is a binary
180
10
10
15
13
20
11
19
23
15
22
26
13
13
26
(b) Leaf deleted.
15
23
10
19
22
10
11
(a) Target vertex 9 is a leaf.
20
20
12
19
23
11
15
22
26
12
20
11
19
23
22
(c) Target vertex 13 has one child.
26
(d) Vertex deleted.
10
15
10
13
20
12
18
11
17
23
19
22
16
26
16
(e) Target vertex 15 has two children.
13
20
12
11
18
17
23
19
(f) Vertex deleted.
Figure 4.15: Deleting a vertex from a binary search tree.
22
26
4.5. AVL trees
181
20
15
13
13
10
10
10
15
13
7
5
15
13
20
10
20
20
(a)
15
(b)
(c)
(d)
Figure 4.16: Different structural representations of a BST.

tree whose left and right subtrees are Fn2 and Fn1 , respectively. Refer to Figure 4.17
for examples of Fibonacci trees; Figure 4.18 shows F6 together with subtree heights for
vertex labels.
(a) F0
(b) F1
(c) F2
(d) F3
(e) F4
(f) F5
Figure 4.17: Fibonacci trees of heights n = 0, 1, 2, 3, 4, 5.
Theorem 4.7. Logarithmic height. The height h of an AVL tree with n internal
vertices is bounded by
lg(n + 1) h < 2 lg n + 1.
Proof. Any binary tree of height h has at most 2i leaves. From the proof of Corollary 4.3,
we see that n is bounded by 2h1 n 2h 1 and in particular n + 1 2h . Take the
logarithm of both sides to get h lg(n + 1).
182

6
Figure 4.18: Fibonacci tree F6 with subtree heights for vertex labels.
Now instead of deriving an upper bound for h, we find the minimum order of an AVL
tree and from there derive the required upper bound for h. Let T be an AVL tree of
minimum order. One subtree of T has height h1. The other subtree has height h1 or
h 2. Our objective is to construct T to have as small a number of vertices as possible.
Without loss of generality, let the left and right subtrees of T have heights h 2 and
h 1, respectively. The Fibonacci tree Fh of height h fits the above requirements for T .
If N (h) denote the number of internal vertices of Fh , then N (h) = 1+N (h1)+N (h2)
is strictly increasing so
N (h) > N (h 2) + N (h 2) = 2 N (h 2).
(4.3)
Repeated application of (4.3) shows that

N (h) > 2i N (h 2i)
(4.4)
for any integer i such that h 2i 1. Choose i so that h 2i = 1 or h 2i = 2, say the

former. Substitute i = (h 1)/2 into (4.4) yields N (h) > 2(h1)/2 . That is, n > 2(h1)/2
and taking logarithm of both sides yields h < 2 lg n + 1.
An immediate consequence of Theorem 4.7 is that any binary search tree implemented
as an AVL tree should have at most logarithmic height. Contrast this with a general BST
of order N1 , whose height can be as low as logarithmic in N1 or as high as linear in N1 .
Translating to search time, we see that searching a general BST using Algorithm 4.11
is in the worst case O(N1 ), which is no better than searching a sorted list. However,
if N2 is the order of an AVL tree endowed with the binary search tree property, then
searching the AVL tree using Algorithm 4.11 has worst-case O(lg N2 ) runtime. While the
worst-case runtime of searching a general BST can vary between O(lg N1 ) and O(N1 ),
that for an AVL tree with the binary search tree property is at most O(lg N2 ).
4.5.1
Insertion
The algorithm for insertion into a BST can be modified and extended to support insertion
into an AVL tree. Let T be an AVL tree having the binary search tree property, and v
4.5. AVL trees
183
a vertex to be inserted into T . In the trivial case, T is the null tree so inserting v into T
is equivalent to letting T be the trivial tree rooted at v. Consider now the case where T
has at least one vertex. Apply Algorithm 4.14 to insert v into T and call the resulting
augmented tree Tv . But our problem is not yet over; Tv may violate the height-balance
property. To complete the insertion procedure, we require a technique to restore, if
necessary, the height-balance property to Tv .
To see why the augmented tree Tv may not necessarily be height-balanced, let u be
the parent of v in Tv , where previously u was a vertex T (and possibly a leaf). In the
original AVL tree T , let Pu : r = u0 , u1 , . . . , uk = u be the path from the root r of T
to u with corresponding subtree heights H(ui ) = hi for i = 0, 1, . . . , k. An effect of the
insertion is to extend the path Pu to the longer path Pv : r = u0 , u1 , . . . , uk = u, v and
possibly increase subtree heights by one. One of two cases can occur with respect to Tv .
1. Height-balanced: Tv is height-balanced so no need to do anything further. A simple
way to detect this is to consider the subtree S rooted at u, the parent of v. If S
has two children, then no height adjustment need to take place for vertices in Pu ,
hence Tv is an AVL tree (see Figure 4.19). Otherwise we perform any necessary
height adjustment for vertices in Pu , starting from uk = u and working our way
up to the root r = u0 . After adjusting the height of ui , we test to see whether
ui (with its new height) is height-balanced. If each of the ui with their new heights
are height-balanced, then Tv is height-balanced.
2. Height-unbalanced: During the height adjustment phase, it may happen that some
uj with its new height is not height-balanced. Among all such height-unbalanced
vertices, let u` be the first height-unbalanced vertex detected during the process of
height adjustment starting from uk = u and going up towards r = u0 . We need to
rebalance the subtree rooted at u` . Then we continue on adjusting heights of the
remaining vertices in Pu , also performing height-rebalancing where necessary.
Case 1 is relatively straightforward, but it is case 2 that involves much intricate work.
4
4
3
2
0
1
0
1
0
4
3
2
0
2
0
1
0
(a) Insert a vertex.
1
0
2
0
2
0
1
0
(b) Vertex inserted.
1
0
2
0
1
0
(c) Vertex inserted.
Figure 4.19: Augmented tree is balanced after insertion; vertex labels are heights.
We now turn to the case where inserting a vertex v into a nonempty AVL tree T
results in an augmented tree Tv that is not height-balanced. A general idea for rebalancing (and hence restoring the height-balance property to) Tv is to determine where in
Tv the height-balance property is first violated (the search phase), and then to locally
rebalance subtrees at and around the point of violation (the repair phase). A description
of the search phase follows. Let
Pv : r = u0 , u1 , . . . , uk = u, v
184
be the path from the root r of Tv (and hence of T ) to v. Traversing upward from v to r,
let z be the first height-unbalanced vertex. Among the children of z, let y be the child of
higher height and hence an ancestor of v. Similarly, among the children of y let x be the
child of higher height. In case a tie occurs, let x be the child of y that is also an ancestor
of v. As each vertex is an ancestor of itself, it is possible that x = v. Furthermore, x is
a grandchild of z because x is a child of y, which in turn is a child of z. The vertex z
is not height-balanced due to inserting v into the subtree rooted at y, hence the height
of y is 2 greater than its sibling (see Figure 4.20, where height-unbalanced vertices are
colored red). We have determined the location at which the height-balance property is
first violated.
5
4
1
0
3 z
2
1
0
2
0
0
(a) Insert a vertex.
2 y
1 x
0 v
4 z
1
0
0
2
1
0
1
0
(b) Vertex inserted.
3 y
1
0
2 x
0
1
0 v
(c) Vertex inserted.
Figure 4.20: Augmented tree is unbalanced after insertion; vertex labels are heights.
We now turn to the repair phase. The central question is: How are we to restore the height-balance property to the subtree rooted at z? By trinode restructuring is meant the process whereby the height-balance property is restored; the prefix
tri refers to the three vertices x, y, z that are central to this process. A common
name for the trinode restructuring is rotation in view of the geometric interpretation
of the process. Figure 4.21 distinguishes four rotation possibilities, two of which are
symmetrical to the other two. The single left rotation in Figure 4.21(a) occurs when
height(x) = height(root(T0 )) + 1 and detailed in Algorithm 4.16. The single right rotation in Figure 4.21(b) occurs when height(x) = height(root(T3 )) + 1; see Algorithm 4.17
for pseudocode. Figure 4.21(c) illustrates the case of a right-left double rotation and
occurs when height(root(T3 )) = height(root(T0 )); see Algorithm 4.18 for pseudocode to
handle the rotation. The fourth case is illustrated in Figure 4.21(d) and occurs when
height(root(T0 )) = height(root(T3 )); refer to Algorithm 4.19 for pseudocode to handle
this left-right double rotation. Each of the four algorithms mentioned above run in constant time O(1) and preserves the in-order traversal ordering of all vertices in Tv . In all,
the insertion procedure is summarized in Algorithm 4.20. If h is the height T , locating and inserting the vertex v takes worst-case O(h) time, which is also the worst-case
runtime for the search-and-repair phase. Thus letting n be the number of vertices in T ,
insertion takes worst-case O(lg n) time.
4.5.2
Deletion
The process of removing a vertex from an AVL tree is similar to the insertion procedure. However, instead of using the insertion algorithm for BST, we use the deletion
4.5. AVL trees
185
z
y
y
z
T0
T1
T2
T3
T0
T1
T2
T3
(a) Left rotation of y over z.
z
y
T3
T2
T0
T1
T0
T1
T2
T3
(b) Right rotation of y over z.
z
y
T0
T3
T1
T0
T2
T1
T2
T3
(c) Double rotation: right rotation of x over y, then left rotation over z.
z
y
x
x
T3
T0
T1
T2
T0
T1
T2
T3
(d) Double rotation: left rotation of x over y, then right rotation over z.
Figure 4.21: Rotations in the trinode restructuring process.
186
Algorithm 4.16: Single left rotation in the trinode restructure process.

Input: Three vertices x, y, z of an augmented AVL tree Tv , where z is the first
height-unbalanced vertex in the path from v up to the root of Tv . The left
subtree of z is denoted T0 and the left subtree of y is T1 . The left and
right subtrees of x are T2 and T3 , respectively.
Output: A single left rotation to height-balance the subtree rooted at z.
1
2
3
4
5
6
7
8
9
rightchild[parent[z]] y
parent[y] parent[z]
parent[z] y
leftchild[y] z
parent[root[T1 ]] z
rightchild[z] root[T1 ]
height[z] 1 + max(height[root[T0 ]], height[root[T1 ]])
height[x] 1 + max(height[root[T2 ]], height[root[T3 ]])
height[y] 1 + max(height[x], height[z])
Algorithm 4.17: Single right rotation in the trinode restructure process.

subtree of z is T3 and the right subtree of y is T2 . The left and right
subtrees of x are T0 and T1 , respectively.
Output: A single right rotation to height-balance the subtree rooted at z.
1
2
3
4
5
6
7
8
9
leftchild[parent[z]] y
parent[y] parent[z]
parent[z] y
rightchild[y] z
parent[root[T2 ]] z
leftchild[z] root[T2 ]
height[x] 1 + max(height[root[T0 ]], height[root[T1 ]])
height[y] 1 + max(height[x], height[z])
4.5. AVL trees
187
Algorithm 4.18: Double rotation: right rotation followed by left rotation.

subtree of z is T0 and the right subtree of y is T3 . The roots of the left
and right subtrees of x are denoted T1 and T2 , respectively.
Output: A right-left double rotation to height-balance the subtree rooted at z.
1
2
3
4
5
6
7
8
9
10
11
12
13
rightchild[parent[z]] x
parent[x] parent[z]
parent[z] x
leftchild[x] z
rightchild[x] y
rightchild[z] root[T1 ]
parent[root[T1 ]] z
parent[y] x
leftchild[y] root[T2 ]
parent[root[T2 ]] y
height[y] 1 + max(height[root[T2 ]], height[root[T3 ]])
height[x] 1 + max(height[y], height[z])
Algorithm 4.19: Double rotation: left rotation followed by right rotation.

subtree of y is T0 and the right subtree of z is T3 . The roots of the left
and right subtrees of x are denoted T1 and T2 , respectively.
Output: A left-right double rotation to height-balance the subtree rooted at z.
1
2
3
4
5
6
7
8
9
10
11
12
13
leftchild[parent[z]] x
parent[x] parent[z]
parent[z] x
rightchild[x] z
leftchild[z] root[T2 ]
parent[T2 ] z
leftchild[x] y
parent[y] x
rightchild[y] root[T1 ]
parent[root[T1 ]] y
height[y] 1 + max(height[root[T0 ]], height[root[T1 ]])
height[x] 1 + max(height[y], height[z])
188
Algorithm 4.20: Insert a vertex into an AVL tree.

Input: An AVL tree T and a vertex v.
Output: The AVL tree T with v inserted into it.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
insert v into T as per Algorithm 4.14

height[v] 0
uv
/* begin height adjustment */
x NULL
y NULL
z NULL
while parent[u] 6= NULL do
u parent[u]
if leftchild[u] 6= NULL and rightchild[u] 6= NULL then
h` height[leftchild[u]]
hr height[rightchild[u]]
height[u] 1 + max(h` , hr )
if |h` hr | > 1 then
if height[rightchild[rightchild[u]]] = height[leftchild[u]] + 1 then
zu
y rightchild[z]
x rightchild[y]
trinode restructuring as per Algorithm 4.16
continue with next iteration of loop
if height[leftchild[leftchild[u]]] = height[rightchild[u]] + 1 then
zu
y leftchild[z]
x leftchild[y]
if height[rightchild[rightchild[u]]] = height[leftchild[u]] then
zu
y rightchild[z]
x leftchild[y]
if height[leftchild[leftchild[u]]] = height[rightchild[u]] then
zu
y leftchild[z]
x rightchild[y]
if leftchild[u] 6= NULL then
height[u] 1 + height[leftchild[u]]
if rightchild[u] 6= NULL then
height[u] 1 + height[rightchild[u]]
4.6. Problems
189
Algorithm 4.15 for BST to remove the target vertex from an AVL tree. The resulting tree may violate the height-balance property, which can be restored using trinode
restructuring.
Let T be an AVL tree having vertex v and suppose we want to remove v from T . In
the trivial case, T is the trivial tree whose sole vertex is v. Deleting v is simply removing
it from T so that T becomes the null tree. On the other hand, suppose T has at least
n > 1 vertices. Apply Algorithm 4.15 to remove v from T and call the resulting tree with
v removed Tv . It is possible that Tv does not satisfy the height-balance property. To
restore the height-balance property to Tv , let u be the parent of v in T prior to deleting
v from T . Having deleted v from T , let P : r = u0 , u1 , . . . , uk = u be the path from the
root r of Tv to u. Adjust the height of u and, traversing from u up to r, perform height
adjustment to each vertex in P and where necessary carry out trinode restructuring. The
resulting algorithm is very similar to Algorithm 4.20; see Algorithm 4.21 for pseudocode.
The deletion procedure via Algorithm 4.15 requires worst-case runtime O(lg n), where
n is the number of vertices in T , and the height-adjustment process runs in worst-case
O(lg n) time as well. Thus Algorithm 4.21 has worst-case runtime of O(lg n).
4.6
Problems
No problem is so formidable that you cant walk away from it.
Charles M. Schulz
4.1. Let Q be a priority queue of n > 1 elements, given in sequence representation.

From section 4.1.1, we know that inserting an element into Q takes O(n) time and
deleting an element from Q takes O(1) time.
(a) Suppose Q is an empty priority queue and let e0 , e1 , . . . , en be n + 1 elements
we want to insert into Q. What is the total runtime required to insert all the
ei into Q while also ensuring that the resulting queue is a priority queue?
(b) Let Q = [e0 , e1 , . . . , en ] be a priority queue of n + 1 elements. What is the
total time required to remove all the elements of Q?
4.2. Prove the correctness of Algorithms 4.2 and 4.3.
4.3. Describe a variant of Algorithm 4.3 for modifying the key of the root of a binary
heap, without extracting any vertex from the heap.
4.4. Section 4.2.2 describes how to insert an element into a binary heap T . The general
strategy is to choose the first leaf following the last internal vertex of T , replace
that leaf with the new element so that it becomes an internal vertex, and perform a
sift-up operation from there. If instead we choose any leaf of T and replace that leaf
with the new element, explain why we cannot do any better than Algorithm 4.2.
4.5. Section 4.2.3 shows how to extract the minimum vertex from a binary heap T .
Instead of replacing the root with the last internal vertex of T , we could replace
the root with any other vertex of T that is not a leaf and then proceed to maintain
the heap-structure and heap-order properties. Explain why the latter strategy is
not better than Algorithm 4.3.
190
Algorithm 4.21: Delete a vertex from an AVL tree.

Input: An AVL tree T and a vertex v V (T ).
Output: The AVL tree T with v removed from it.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
u parent[v]
delete v from T as per Algorithm 4.15
adjust the height of u
/* begin height adjustment */
x NULL
y NULL
z NULL
while parent[u] 6= NULL do
u parent[u]
if leftchild[u] 6= NULL and rightchild[u] 6= NULL then
h` height[leftchild[u]]
hr height[rightchild[u]]
height[u] 1 + max(h` , hr )
if |h` hr | > 1 then
if height[rightchild[rightchild[u]]] = height[leftchild[u]] + 1 then
zu
y rightchild[z]
x rightchild[y]
if height[leftchild[leftchild[u]]] = height[rightchild[u]] + 1 then
zu
y leftchild[z]
x leftchild[y]
if height[rightchild[rightchild[u]]] = height[leftchild[u]] then
zu
y rightchild[z]
x leftchild[y]
if height[leftchild[leftchild[u]]] = height[rightchild[u]] then
zu
y leftchild[z]
x rightchild[y]
if leftchild[u] 6= NULL then
height[u] 1 + height[leftchild[u]]
if rightchild[u] 6= NULL then
height[u] 1 + height[rightchild[u]]
4.6. Problems
191
4.6. Let S be a sequence of n > 1 real numbers. How can we use algorithms described
in section 4.2 to sort S?
4.7. The binary heaps discussed in section 4.2 are properly called minimum binary
heaps because the root of the heap is always the minimum vertex. A corresponding notion is that of maximum binary heaps, where the root is always the maximum
element. Describe algorithms analogous to those in section 4.2 for managing maximum binary heaps.
4.8. What is the total time required to extract all elements from a binary heap?

4.9. Numbers of the form nr are called binomial coefficients. They also count the
number of r-combinations from a set of n objects. Algorithm 4.22 presents pseudocode to generate all the r-combinations of a set of n distinct objects. What is the
worst-case runtime of Algorithm 4.22? Prove the correctness of Algorithm 4.22.
4.10. In contrast to enumerating all the r-combinations of a set of n objects, we may
only want to generate a random r-combination. Describe and present pseudocode
of a procedure to generate a random r-combination of {1, 2, . . . , n}.
4.11. A problem related to the r-combinations of the set S = {1, 2, . . . , n} is that of
generating the permutations of S. Algorithm 4.23 presents pseudocode to generate
all the permutations of S in increasing lexicographic order. Find the worst-case
runtime of this algorithm and prove its correctness.
4.12. Provide a description and pseudocode of an algorithm to generate a random permutation of {1, 2, . . . , n}.
4.13. Takaoka [175] presents a general method for combinatorial generation that runs in
O(1) time. How can Takaokas method be applied to generating combinations and
permutations?
4.14. The proof of Lemma 4.4 relies on Pascals formula, which states that for any
positive integers n and r such that r n, the following identity holds:

n+1
n
n
=
+
.
r
r1
r
Prove Pascals formula.
4.15. Let m, n, r be nonnegative integers such that r n. Prove the Vandermonde
convolution

X

r
m+n
m
n
=
.
r
k
rk
k=0
The latter equation, also known as Vandermondes identity, was already known
as early as 1303 in China by Chu Shi-Chieh. Alexandre-Theophile Vandermonde
independently discovered it and his result was published in 1772.
4.16. If m and n are nonnegative integers, prove that

X

n
m+n+1
m+k
.
=
n
k
k=0
192
Algorithm 4.22: Generating all the r-combinations of {1, 2, . . . , n}.

Input: Two nonnegative integers n and r.
Output: A list L containing all the r-combinations of the set {1, 2, . . . , n} in
increasing lexicographic order.
1
2
3
4
5
6
7
8
9
10
11
12
13
L []
ci i for i = 1, 2, . . . , r
append(L, c1 c2 cr )
for i 2, 3, . . . , nr do
mr
max n
while cm = max do
mm1
max max 1
cm cm + 1
cj cj1 + 1 for j = m + 1, m + 2, . . . , r
append(L, c1 c2 cr )
return L
Algorithm 4.23: Generating all the permutations of {1, 2, . . . , n}.

Input: A positive integer n.
Output: A list L containing all the permutations of {1, 2, . . . , n} in increasing
lexicographic order.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
L []
ci i for i = 1, 2, . . . , n
append(L, c1 c2 cn )
for i 2, 3, . . . , n! do
mn1
while cm > cm+1 do
mm1
kn
while cm > ck do
k k1
swap the values of cm and ck
pm+1
qn
while p < q do
swap the values of cp and cq
pp+1
q q1
append(L, c1 c2 cn )
return L
4.6. Problems
193
4.17. Let n be a positive integer. How many distinct binomial heaps having n vertices
are there?
4.18. The algorithms described in section 4.3 are formally for minimum binomial heaps
because the vertex at the top of the heap is always the minimum vertex. Describe
analogous algorithms for maximum binomial heaps.
4.19. If H is a binomial heap, what is the total time required to extract all elements
from H?
4.20. Frederickson [78] describes an O(k) time algorithm for finding the k-th smallest
element in a binary heap. Provide a description and pseudocode of Fredericksons
algorithm and prove its correctness.
4.21. Fibonacci heaps [79] allow for amortized O(1) time with respect to finding the
minimum element, inserting an element, and merging two Fibonacci heaps. Deleting the minimum element takes amortized time O(lg n), where n is the number
of vertices in the heap. Describe and provide pseudocode of the above Fibonacci
heap operations and prove the correctness of the procedures.
4.22. Takaoka [176] introduces another type of heap called a 2-3 heap. Deleting the
minimum element takes amortized O(lg n) time with n being the number of vertices
in the 2-3 heap. Inserting an element into the heap takes amortized O(1) time.
Describe and provide pseudocode of the above 2-3 heap operations. Under which
conditions would 2-3 heaps be more efficient than Fibonacci heaps?
4.23. In 2000, Chazelle [47] introduced the soft heap, which can perform common heap
operations in amortized O(1) time. He then applied [46] the soft heap to realize a
very efficient implementation of an algorithm for finding minimum spanning trees.
In 2009, Kaplan and Zwick [114] provided a simple implementation and analysis of
Chazelles soft heap. Describe soft heaps and provide pseudocode of common heap
operations. Prove the correctness of the algorithms and provide runtime analyses.
Describe how to use soft heap to realize an efficient implementation of an algorithm
to produce minimum spanning trees.
4.24. Explain any differences between the binary heap-order property, the binomial heaporder property, and the binary search tree property. Can in-order traversal be used
to list the vertices of a binary heap in sorted order? Explain why or why not.
4.25. Present pseudocode of an algorithm to find a vertex with maximum key in a binary
search tree.
4.26. Compare and contrast algorithms for locating minimum and maximum elements
in a list with their counterparts for a binary search tree.
4.27. Let T be a nonempty BST and suppose v V (T ) is not a minimum vertex of T .
If h is the height of T , describe and present pseudocode of an algorithm to find the
predecessor of v in worst-case time O(h).
4.28. Let L = [v0 , v1 , . . . , vn ] be the in-order listing of a BST T . Present an algorithm
to find the successor of v V (T ) in constant time O(1). How can we find the
predecessor of v in constant time as well?
194
4.29. Modify Algorithm 4.15 to extract a minimum vertex of a binary search tree. Now
do the same to extract a maximum vertex. How can Algorithm 4.15 be modified
to extract a vertex from a binary search tree?
4.30. Let v be a vertex of a BST and suppose v has two children. If s and p are the
successor and predecessor of v, respectively, show that s has no left-child and p has
no right-child.
4.31. Let L = [e0 , e1 , . . . , en ] be a list of n + 1 elements from a totally ordered set X with
total order . How can binary search trees be used to sort L?
4.32. Describe and present pseudocode of a recursive algorithm for each of the following
operations on a BST.
(a) Find a vertex with a given key.
(b) Locate a minimum vertex.
(c) Locate a maximum vertex.
(d) Insert a vertex.
4.33. Are the algorithms presented in section 4.4 able to handle a BST having duplicate
keys? If not, modify the relevant algorithm(s) to account for the case where two
vertices in a BST have the same key.
4.34. The notion of vertex level for binary trees can be extended to general rooted trees
as follows. Let T be a rooted tree with n > 0 vertices and height h. Then level
0 i h of T consists of all those vertices in T that have the same depth i. If
each vertex at level i has i + m children for some fixed integer m > 0, what is the
number of vertices at each level of T ?
4.35. Compare the search, insertion, and deletion times of AVL trees and random binary
search trees. Provide empirical results of your comparative study.
4.36. Describe and present pseudocode of an algorithm to construct a Fibonacci tree of
height n for some integer n 0. Analyze the worst-case runtime of your algorithm.
4.37. The upper bound in Theorem 4.7 can be improved as follows. From the proof of
the theorem, we have the recurrence relation N (h) > N (h 1) + N (h 2).
(a) If h 2, show that there exists some c > 0 such that N (h) ch .
(b) Assume for induction that
N (h) > N (h 1) + N (h 2) ch1 + ch2
for some h > 2. If c > 0, show that c2 c 1 = 0 is a solution to the
recurrence relation ch1 + ch2 and that
N (h) >
!h
1+ 5
.
2
4.6. Problems
195
(c) Use the previous two parts to show that

h<
1
lg n
lg
where = (1 + 5)/2 is the golden ratio and n counts the number of internal
vertices of an AVL tree of height h.
4.38. The Fibonacci sequence Fn is defined as follows. We have initial values F0 = 0
and F1 = 1. For n > 1, the n-th term in the sequence can be obtained via the
recurrence relation Fn = Fn1 + Fn2 . Show that
n (1/)n
Fn =
5
(4.5)
where is the golden ratio. The closed form solution (4.5) to the Fibonacci sequence is known as Binets formula, named after Jacques Philippe Marie Binet,
even through Abraham de Moivre knew about this formula long before Binet did.
Chapter 5
Distance and Connectivity
5.1
Paths and distance
5.1.1
Distance and metrics
Consider an edge-weighted simple graph G = (V, E, i, h) without negative weight cycles.

Here E V (2) , i : E V (2) is an incidence function as in (1.2), which we regard
as the identity function, and h : E V is an orientation function as in (1.3). Let
W : E R be the weight function. (If G is not provided with a weight function on
the edges, we assume that each edge has unit weight.) If v1 , v2 V are two vertices
and P = (e1 , e2 , . . . , em ) is a v1 -v2 path (so v1 is incident to e1 and v2 is incident to em ),
define the weight of P to be the sum of the weights of the edges in P :
W (P ) =
m
X
W (ei ).
i=1
The distance function d : V V R {} on G is defined by

d(v1 , v2 ) =
if v1 and v2 lie in distinct connected components of G, and by
d(v1 , v2 ) = min W (P )
P
196
(5.1)
5.1. Paths and distance
197
otherwise, where the minimum is taken over all paths P from v1 to v2 . By hypothesis, G
has no negative weight cycles so the minimum in (5.1) exists. It follows by definition of
the distance function that d(u, v) = if and only if there is no path between u and v.
How we interpret the distance function d depends on the meaning of the weight
function W . In practical applications, vertices can represent physical locations such as
cities, sea ports, or landmarks. An edge weight could be interpreted as the physical
distance in kilometers between two cities, the monetary cost of shipping goods from one
sea port to another, or the time required to travel from one landmark to another. Then
d(u, v) could mean the shortest route in kilometers between two cities, the lowest cost
incurred in transporting goods from one sea port to another, or the least time required
to travel from one landmark to another.
The distance function d is not in general a metric, i.e. the triangle inequality does
not in general hold for d. However, when the distance function is a metric then G is
called a metric graph. The theory of metric graphs, due to their close connection with
tropical curves, is an active area of research. For more information on metric graphs, see
Baker and Faber [10].
5.1.2
Radius and diameter
A new hospital is to be built in a large city. Construction has not yet started and a
number of urban planners are discussing the future location of the new hospital. What
is a possible location for the new hospital and how are we to determine this location?
This is an example of a class of problems known as facility location problems. Suppose
our objective in selecting a location for the hospital is to minimize the maximum response
time between the new hospital and the site of an emergency. To help with our decision
making, we could use the notion of the center of a graph.
The center of a graph G = (V, E) is defined in terms of the eccentricity of the graph
under consideration. The eccentricity : V R is defined as follows. For any vertex
v, the eccentricity (v) is the greatest distance between v and any other vertex in G. In
symbols, the eccentricity is expressible as
(v) = max d(u, v).
uV
For example, in a tree T with root r the eccentricity of r is the height of T . In the graph
of Figure 5.1, the eccentricity of 2 is 5 and the shortest paths that yield (2) are
P1 : 2, 3, 4, 14, 15, 16
P2 : 2, 3, 4, 14, 15, 17.
The eccentricity of a vertex v can be thought of as an upper bound on the distance from
v to any other vertex in G. Furthermore, we have at least one vertex in G whose distance
from v is (v).
v 1
(v) 6
2
5
3
4
4
4
5
5
6
6
7
7
8
7
9
5
10
6
11
7
12
7
13
6
14
5
15 16
6 7
17
7
Table 5.1: Eccentricity distribution for the graph in Figure 5.1.

To motivate the notion of the radius of a graph, consider the distribution of eccentricity among vertices of the graph G in Figure 5.1. The required eccentricity distribution
198
Chapter 5. Distance and Connectivity
16
11
12
15
10
13
14
17
Figure 5.1: Determine the eccentricity, center, radius, and diameter.
(v)
10
12
14
16
Figure 5.2: Eccentricity distribution of the graph in Figure 5.1. The horizontal axis
represents the vertex name, while the vertical axis is the corresponding eccentricity.
5.1. Paths and distance
199
is shown in Table 5.1. Among the eccentricities in the latter table, the minimum eccentricity is (3) = (4) = 4. An intuitive interpretation is that both of the vertices 3 and
4 have the shortest distance to any other vertices in G. We can invoke an analogy with
plane geometry as follows. If a circle has radius r, then the distance from the center
of the circle to any point within the circle is at most r. The minimum eccentricity in
graph theory plays a role similar to the radius of a circle. If an object is strategically
positionede.g. a vertex with minimum eccentricity or the center of a circlethen its
greatest distance to any other object is guaranteed to be minimum. With the above
analogy in mind, we define the radius of a graph G = (V, E), written rad(G), to be the
minimum eccentricity among the eccentricity distribution of G. In symbols,
rad(G) = min (v).
vV
The center of G, written C(G), is the set of vertices with minimum eccentricity. Thus
the graph in Figure 5.1 has radius 4 and center {3, 4}. As should be clear from the latter
example, the radius is a number whereas the center is a set. Refer to the beginning of
the section where we mentioned the problem of selecting a location for a new hospital.
We could use a graph to represent the geography of the city wherein the hospital is to
be situated and select a location that is in the center of the graph.
Consider now the maximum eccentricity of a graph. In (2.5) we defined the diameter
of a graph G = (V, E) by
diam(G) = max d(u, v).
u,vV
u6=v
The diameter of G can also be defined as the maximum eccentricity of any vertex in G:
diam(G) = max (v).
vV
In case G is disconnected, define its diameter to be diam(G) = . To compute diam(G),

use the Floyd-Roy-Warshall algorithm (see section 2.6) to compute the shortest distance
between each pair of vertices. The maximum of these distances is the diameter. The set
of vertices of G with maximum eccentricity is called the periphery of G, written per(G).
The graph in Figure 5.1 has diameter 7 and periphery {7, 8, 11, 12, 16, 17}.
Theorem 5.1. Eccentricities of adjacent vertices. Let G = (V, E) be an undirected, connected graph having nonnegative edge weights. If uv E and W is a weight
function for G, then |(u) (v)| W (uv).
Proof. By definition, we have d(u, x) (u) and d(v, x) (v) for all x V . Let w V
such that d(u, w) = (u). Apply the triangle inequality to obtain
d(u, w) d(u, v) + d(v, w)
(u) W (uv) + d(v, w)
W (uv) + (v)
from which we have (u) (v) W (uv). Repeating the above argument with the role
of u and v interchanged yields (v) (u) W (uv). Both (u) (v) W (uv) and
(v) (u) W (uv) together yields the inequality |(u) (v)| W (uv) as required.
200
5.1.3
Center of trees
Given a tree T of order 3, we want to derive a bound on the number of vertices that
comprise the center of T . A graph in general can have one, two, or more number of
vertices for its center. Indeed, for any integer n > 0 we can construct a graph whose
center has cardinality n. The cases for n = 1, 2, 3 are illustrated in Figure 5.3. But can
we do the same for trees? That is, given any positive integer n does there exist a tree
whose center has n vertices? It turns out that the center of a tree cannot have more
than two vertices, a result first discovered [111] by Camille Jordan in 1869.
(a) |C(G)| = 1
(b) |C(G)| = 2
(c) |C(G)| = 3
Figure 5.3: Constructing graphs with arbitrarily large centers.

Theorem 5.2. Jordan [111]. If a tree T has order 3, then the center of T is either
a single vertex or two adjacent vertices.
Proof. As all eccentric vertices of T are leaves (see problem 5.7), removing all the leaves
of T decreases the eccentricities of the remaining vertices by one. The tree comprised of
the surviving vertices has the same center as T . Continue pruning leaves as described
above and note that the tree comprised of the surviving vertices has the same center as
the previous tree. After a finite number of leaf pruning stages, we eventually end up
with a tree made up of either one vertex or two adjacent vertices. The vertex set of this
final tree is the center of T .
5.1.4
Distance matrix
In sections 1.3.4 and 2.3, the distance matrix D of a graph G was defined to be D = [dij ],
where dij = d(vi , vj ) and the vertices of G are indexed by V = {v0 , v1 , . . . , vk }. The
matrix D is square where we set dij = 0 for entries along the main diagonal. If there is
no path from vi to vj , then we set dij = . If G is undirected, then D is symmetric and
is equal to its transpose, i.e. DT = D. To compute the distance matrix D, apply the
Floyd-Roy-Warshall algorithm to determine the distances between all pairs of vertices.
Refer to Figure 5.4 for examples of distance matrices of directed and undirected graphs.
In the remainder of this section, graph refers to an undirected graph unless otherwise
specified.
Instead of one distance matrix, we can define several distance matrices on G. Consider
an edge-weighted graph G = (V, E) without negative weight cycles and let
d : V V R {}
be a distance function of G. Let = diam(G) be the diameter of G and index the
vertices of G in some arbitrary but fixed manner, say V = {v0 , v1 , . . . , vn }. The sequence
5.2. Vertex and edge connectivity
201
3
5
(a)
1
0
1
2
2
1
0
1
1
0
1
2
2
3
2
1
0
1
3
2
2
0
1
1
0
3
5
1
0
(b)
0
1
1
2
3
2
1
0
2
1
1
2
3
2
0
1
2
3
1
0
Figure 5.4: Distance matrices of directed and undirected graphs.

of distance matrices of G are a sequence of (n 1) (n 1) matrices A1 , A2 , . . . , A
where
(
1, if d(vi , vj ) = k,
(Ak )ij =
0, otherwise.
In particular, A1 is the usual adjacency matrix A. To compute the sequence of distance
matrices of G, use the Floyd-Roy-Warshall algorithm to compute the distance between
each pair of vertices and assign the resulting distance to the corresponding matrix Ai .
The distance matrix arises in several applications, including communication network
design [86] and network flow algorithms [58]. Thanks to Graham and Pollak [86], the
following unusual fact is known. If T is any tree then
det D(T ) = (1)n1 (n 1)2n2
where n denotes the order of T . In particular, the determinant of the distance matrix of
a tree is independent of the structure of the tree. This fact is proven in the paper [86],
but see also [65].
5.2
Vertex and edge connectivity
If G = (V, E) is a graph and U V is a vertex set with the property that G U

has more connected components than G, then we call U a vertex-cut. The term cutvertex or cut-point is used when the vertex-cut consists of exactly one vertex. For an
intuitive appreciation of vertex-cut, suppose G = (V, E) is a connected graph. Then
U V is a vertex-cut if the vertex deletion subgraph G U is disconnected. For
example, the cut-vertex of the graph in Figure 5.5 is the vertex 0. By v (G) we mean
the vertex connectivity of a connected graph G, defined as the minimum number of
vertices whose removal would either disconnect G or reduce G to the trivial graph. The
202
vertex connectivity v (G) is also written as (G). The vertex connectivity of the graph in
Figure 5.5 is v (G) = 1 because we only need to remove vertex 0 in order to disconnect
the graph. The vertex connectivity of a connected graph G is thus the vertex-cut of
minimum cardinality. And G is said to be k-connected if v (G) k. From the latter
definition, it immediately follows that if G has at least 3 vertices and is k-connected then
any vertex-cut of G has at least cardinality k. For instance, the graph in Figure 5.5 is
1-connected. In other words, G is k-connected if the graph remains connected even after
removing any k 1 or fewer vertices from G.
0
Figure 5.5: A claw graph with 4 vertices.
Figure 5.6: The Petersen graph on 10 vertices.

Example 5.3. Here is a Sage example concerning (G) using the Petersen graph depicted in Figure 5.6. A linear programming Sage package, such as GLPK, must be
installed for the commands below to work.
sage :
sage :
10
sage :
3.0
sage :
sage :
9
sage :
2.0
G = graphs . PetersenGraph ()
len ( G . vertices ())
G . vertex_connectivity ()
G . delete_vertex (0)
G . vertex_connectivity ()
The notions of edge-cut and cut-edge are similarly defined. Let G = (V, E) be a
graph and D E an edge set such that the edge deletion subgraph G D has more
components than G. Then D is called an edge-cut. An edge-cut D is said to be minimal
203
if no proper subset of D is an edge-cut. The term cut-edge or bridge is reserved for

the case where the set D is a singleton. Think of a cut-edge as an edge whose removal
from a connected graph would result in that graph being disconnected. Going back
to the case of the graph in Figure 5.5, each edge of the graph is a cut-edge. A graph
having no cut-edge is called bridgeless. An open question as of 2010 involving bridges
is the cycle double cover conjecture, due to Paul Seymour and G. Szekeres, which states
that every bridgeless graph admits a set of cycles that contains each edge exactly twice.
The edge connectivity of a connected graph G, written e (G) and sometimes denoted
by (G), is the minimum number of edges whose removal would disconnect G. In other
words, e (G) is the minimum cardinality among all edge-cuts of G. Furthermore, G is
said to be k-edge-connected if e (G) k. A connected graph that is k-edge-connected
is guaranteed to be connected after removing k 1 edges from it. When we have
removed k or more edges, then the graph would become disconnected. By convention, a
1-edge-connected graph is simply a connected graph. The graph in Figure 5.5 has edge
connectivity e (G) = 1 and is 1-edge-connected.
Example 5.4. Here is a Sage example concerning (G) using the Petersen graph shown
in Figure 5.6. You must install an optional linear programming Sage package such as
GLPK for the commands below to work.
sage :
sage :
10
sage :
15
sage :
3.0
sage :
sage :
14
sage :
2.0
G = graphs . PetersenGraph ()
E = G . edges (); len ( E )
G . edge_connectivity ()
G . delete_edge ( E [0])
len ( G . edges ())
G . edge_connectivity ()
Vertex and edge connectivity are intimately related to the reliability and survivability
of computer networks. If a computer network G (which is a connected graph) is kconnected, then it would remain connected despite the failure of at most k 1 network
nodes. Similarly, G is k-edge-connected if the network remains connected after the failure
of at most k 1 network links. In practical terms, a network with redundant nodes
and/or links can afford to endure the failure of a number of nodes and/or links and
still be connected, whereas a network with very few redundant nodes and/or links (e.g.
something close to a spanning tree) is more prone to be disconnected. A k-connected or
k-edge-connected network is more robust (i.e. can withstand) against node and/or link
failures than is a j-connected or j-edge-connected network, where j < k.
Proposition 5.5. If (G) is the minimum degree of an undirected connected graph G =
(V, E), then the edge connectivity of G satisfies (G) (G).
Proof. Choose a vertex v V whose degree is deg(v) = (G). Deleting the (G) edges
incident on v suffices to disconnect G as v is now an isolated vertex. It is possible that
G has an edge-cut whose cardinality is smaller than (G). Hence the result follows.
Let G = (V, E) be a graph and suppose X1 and X2 comprise a partition of V . A
partition-cut of G, denoted hX1 , X2 i, is the set of all edges of G with one endpoint in
X1 and the other endpoint in X2 . If G is a bipartite graph with bipartition X1 and X2 ,
then hX1 , X2 i is a partition-cut of G. It follows that a partition-cut is also an edge-cut.
204
Proposition 5.6. An undirected connected graph G is k-edge-connected if and only if

any partition-cut of G has at least k edges.
Proof. Assume that G is k-edge-connected. Then each edge-cut has at least k edges. As
a partition-cut is an edge-cut, then any partition-cut of G has at least k edges.
On the other hand, suppose each partition-cut has at least k edges. If D is a minimal
edge-cut of G and X1 and X2 are the vertex sets of the two components of G D, then
D = hX1 , X2 i. To see this, note that D hX1 , X2 i. If hX1 , X2 i D 6= then choose
some e hX1 , X2 i such that e
/ D. The endpoints of e belong to the same component
of G D, in contradiction of the definition of X1 and X2 . Thus any minimal edge-cut is
a partition-cut and conclude that any edge-cut has at least k edges.
Proposition 5.7. If G = (V, E) is an undirected connected graph with vertex connectivity
(G) and edge connectivity (G), then we have (G) (G).
Proof. Let S be an edge-cut of G with cardinality k = |S| = (G). Removing k suitably
chosen vertices of G suffice to delete the edges of S and hence disconnect G. It is also
possible to have a smaller vertex-cut elsewhere in G. Hence the inequality follows.
Taking together Propositions 5.5 and 5.7, we have Whitneys inequality.
Theorem 5.8. Whitneys inequality [194]. Let G be an undirected connected graph
with vertex connectivity (G), edge connectivity (G), and minimum degree (G). Then
we have the following inequality:
(G) (G) (G).
Proposition 5.9. Let G be an undirected connected graph that is k-connected for some
k 3. If e is an edge of G, then the edge-deletion subgraph G e is (k 1)-connected.
Proof. Let V = {v1 , v2 , . . . , vk2 } be a set of k 2 vertices in G e. It suffice to show
the existence of a u-v walk in (G e) V for any distinct vertices u and v in (G e) V .
We need to consider two cases: (i) at least one of the endpoints of e is in V ; and (ii)
neither endpoints of e is in V .
(i) Assume that V has at least one endpoint of e. As G V is 2-connected, any
distinct pair of vertices u and v in G V is connected by a u-v path that excludes e.
Hence the u-v path is also in (G e) V .
(ii) Assume that neither endpoints of e is in V . If u and v are distinct vertices in
(G e) V , then either: (1) both u and v are endpoints of e; or (2) at least one of u
and v is an endpoint of e.
(1) Suppose u and v are both endpoints of e. As G is k-connected, then G has at
least k + 1 vertices so that the vertex set of G {v1 , v2 , . . . , vk2 , u, v} is nonempty.
Let w be a vertex of G {v1 , v2 , . . . , vk2 , u, v}. Then there is a u-w path in G
{v1 , v2 , . . . , vk2 , v} and a w-v path in G {v1 , v2 , . . . , vk2 , u}. Neither the u-w nor
the w-v paths contain e. The concatenation of these two paths is a u-v walk in
(G e) V .
(2) Now suppose at least one of u and v, say u, is an endpoint of e. Let w be the other
endpoint of e. As G is k-connected, then G {v1 , v2 , . . . , vk2 , w} is connected and
we can find a u-v path P in G {v1 , v2 , . . . , vk2 , w}. Furthermore P is a u-v path
in G {v1 , v2 , . . . , vk2 } that neither contain w nor e. Hence P is a u-v path in
(G e) V .
205
Conclude that G e is (k 1)-connected.

Repeated application of Proposition 5.9 results in the following corollary.
Corollary 5.10. Let G be an undirected connected graph that is k-connected for some
k 3. If E is any set of m edges of G, for m k 1, then the edge-deletion subgraph
G E is (k m)-connected.
What does it mean for a communications network to be fault-tolerant? In 1932,
Hassler Whitney provided [194] a characterization of 2-connected graphs whereby he
showed that a graph G is 2-connected if and only if each pair of distinct vertices in G
has two different paths connecting those two vertices. A key to understanding Whitneys
characterization of 2-connected graphs is the notion of internal vertex of a path. Given a
path P in a graph, a vertex along that path is said to be an internal vertex if it is neither
the initial nor the final vertex of P . In other words, a path P has an internal vertex if
and only if P has at least two edges. Building upon the notion of internal vertices, we
now discuss what it means for two paths to be internally disjoint. Let u and v be distinct
vertices in a graph G and suppose P1 and P2 are two paths from u to v. Then P1 and P2
are said to be internally disjoint if they do not share any common internal vertex. Two
u-v paths are internally disjoint in the sense that both u and v are the only vertices to
be found in common between those paths. The notion of internally disjoint paths can be
easily extended to a collection of u-v paths. Whitneys characterization essentially says
that a graph is 2-connected if and only if any two u-v paths are internally disjoint.
Consider the notion of internally disjoint paths within the context of communications
network. As a first requirement for fault-tolerant communications network, we want the
network to remain connected despite the failure of any network node. By Whitneys
characterization, this is possible if the original communications network is 2-connected.
That is, we say that a communications network is fault-tolerant provided that any pair
of distinct nodes is connected by two internally disjoint paths. The failure of any node
should at least guarantee that any two distinct nodes are still connected.
Theorem 5.11. Whitneys characterization of 2-connected graphs [194]. Let
G be an undirected connected graph having at least 3 vertices. Then G is 2-connected if
and only if any two distinct vertices in G are connected by two internally disjoint paths.
Proof. (=) For the case of necessity, argue by contraposition. That is, suppose G is not
2-connected. Let v be a cut-vertex of G, from which it follows that Gv is disconnected.
We can find two vertices w and x such that there is no w-x path in G v. Therefore v
is an internal vertex of any w-x path in G.
(=) For the case of sufficiency, let G be 2-connected and let u and v be any two
distinct vertices in G. Argue by induction on d(u, v) that G has at least two internally
disjoint u-v paths. For the base case, suppose u and v are connected by an edge e so that
d(u, v) = 1. Adapt the proof of Proposition 5.9 to see that G e is connected. Hence we
can find a u-v path P in G e such that P and e are two internally disjoint u-v paths
in G.
Assume for induction that G has two internally disjoint u-v paths where d(u, v) < k
for some k 2. Let w and x be two distinct vertices in G such that d(w, x) = k and
hence there is a w-x path in G of length k, i.e. we have a w-x path
W : w = w1 , w2 , . . . , wk1 , wk = x.
206
Note that d(w, wk1 ) < k and apply the induction hypothesis to see that we have two
internally disjoint w-wk1 paths in G; call these paths P and Q. As G is 2-connected,
we have a w-x path R in G wk1 and hence R is also a w-x path in G. Let z be the
vertex on R that immediately precedes x and assume without loss of generality that z
is on P . We claim that G has two internally disjoint w-x paths. One of these paths is
the concatenation of the subpath of P from w to z with the subpath of R from z to x.
If x is not on Q, then construct a second w-x path, internally disjoint from the first one,
as follows: concatenate the path Q with the edge wk1 w. In case x is on Q, take the
subpath of Q from w to x as the required second path.
From Theorem 5.11, an undirected connected graph G is 2-connected if and only if any
two distinct vertices of G are connected by two internally disjoint paths. In particular,
let u and v be any two distinct vertices of G and let P and Q be two internally disjoint
u-v paths as guaranteed by Theorem 5.11. Starting from u, travel along the path P
to arrive at v. Then start from v and travel along the path Q to arrive at u. The
concatenation of the internally disjoint paths P and Q is hence a cycle passing through
u and v. We have proved the following corollary to Theorem 5.11.
Corollary 5.12. Let G be an undirected connected graph having at least 3 vertices. Then
G is 2-connected if and only if any two distinct vertices of G lie on a common cycle.
The following theorem provides further characterizations of 2-connected graphs, in
addition to Whitneys characterization.
Theorem 5.13. Characterizations of 2-connected graphs. Let G = (V, E) be an
undirected connected graph having at least 3 vertices. Then the following are equivalent.
1. G is 2-connected.
2. If u, v V are distinct vertices of G, then u and v lie on a common cycle.
3. If v V and e E, then v and e lie on a common cycle.
4. If e1 , e2 E are distinct edges of G, then e1 and e2 lie on a common cycle.
5. If u, v V are distinct vertices and e E, then they lie on a common path.
6. If u, v, w V are distinct vertices, then they lie on a common path.
7. If u, v, w V are distinct vertices, then there is a path containing any two of these
vertices but excluding the third.
5.3
Mengers theorem
Mengers theorem has a number of different versions: an undirected, vertex-connectivity

version; a directed, vertex-connectivity version; an undirected, edge-connectivity version;
and a directed, edge-connectivity version. In this section, we will prove the undirected,
vertex-connectivity version. But first, lets consider a few technical results that will be
of use for the purpose of this section.
Let u and v be distinct vertices in a connected graph G = (V, E) and let S V .
Then S is said to be u-v separating if u and v lie in different components of the vertex
5.3. Mengers theorem
207
deletion subgraph G S. The vertices u and v are positioned such that after removing
vertices in S from G and the corresponding edges, u and v are no longer connected nor
strongly connected to each other. It is clear by definition that u, v
/ S. We also say
that S separates u and v, or S is a vertex separating set. Similarly an edge set T E is
u-v separating (or separates u and v) if u and v lie in different components of the edge
deletion subgraph G T . But unlike the case of vertex separating sets, it is possible for
u and v to be endpoints of edges in T because the removal of edges does not result in
deleting the corresponding endpoints. The set T is also called an edge separating set. In
other words, S is a vertex cut and T is an edge cut. When it is clear from context, we
simply refer to a separating set. See Figure 5.7 for illustrations of separating sets.
(a) Original graph.
(b) Vertex separated.
(c) Original graph.
(d) Edge separated.
Figure 5.7: Vertex and edge separating sets. Blue-colored vertices are those we want
to separate. The red-colored vertices form a vertex separating set or vertex cut; the
red-colored edges constitute an edge separating set or edge cut.
Proposition 5.14. Consider two distinct, non-adjacent vertices u, v in a connected

graph G. If Puv is a collection of internally disjoint u-v paths in G and Suv is a uv separating set of vertices in G, then
|Puv | |Suv |.
(5.2)
Proof. Each u-v path in Puv must include at least one vertex from Suv because Suv is
a vertex cut of G. Any two distinct paths in Puv cannot contain the same vertex from
Suv . Thus the number of internally disjoint u-v paths is at most |Suv |.
The bound (5.2) holds for any u-v separating set Suv of vertices in G. In particular,
we can choose Suv to be of minimum cardinality among all u-v separating sets of vertices
in G. Thus we have the following corollary. Mengers Theorem 5.18 provides a much
stronger statement of Corollary 5.15, saying in effect that the two quantities max(|Puv |)
and min(|Suv |) are equal.
Corollary 5.15. Consider any two distinct, non-adjacent vertices u, v in a connected
graph G. Let max(|Puv |) be the maximum number of internally disjoint u-v paths in G
and denote by min(|Suv |) the minimum cardinality of a u-v separating set of vertices in
G. Then we have max(|Puv |) min(|Suv |).
208
Corollary 5.16. Consider any two distinct, non-adjacent vertices u, v in a connected

graph G. Let Puv be a collection of internally disjoint u-v paths in G and let Suv be a u-v
separating set of vertices in G. If |Puv | = |Suv |, then Puv has maximum cardinality among
all collections of internally disjoint u-v paths in G and Suv has minimum cardinality
among all u-v separating sets of vertices in G.
Proof. Argue by contradiction. Let Quv be another collection of internally disjoint u-v
paths in G such that |Quv | |Puv |. Then |Puv | |Quv | |Suv | by Proposition 5.14.
We cannot have |Quv | > |Puv |, which would be contradictory to our hypothesis that
Puv = |Suv |. Thus |Quv | = |Puv |. Let Tuv be another u-v separating set of vertices in
G such that |Tuv | |Suv |. Then we have |Puv | |Tuv | |Suv | by Proposition 5.14.
We cannot have |Tuv | < |Suv | because we would then end up with |Puv | |Tuv | and
Puv = |Suv |, a contradiction. Therefore |Tuv | = |Suv |.
Lemma 5.17. Consider two distinct, non-adjacent vertices u, v in a connected graph G
and let k be the minimum number of vertices required to separate u and v. If G has a
u-v path of length 2, then G has k internally disjoint u-v paths.
Proof. Argue by induction on k. For the base case, assume k = 1. Hence G has a cut
vertex x such that u and v are disconnected in G x. Any u-v path must contain x. In
particular, there can be only one internally disjoint u-v path.
Assume for induction that k 2. Let P : u, x, v be a path in G having length 2 and
suppose S is a smallest u-v separating set for G x. Then S {x} is a u-v separating
set for G. By the minimality of k, we have |S| k 1. By the induction hypothesis,
we have at least k 1 internally disjoint u-v paths in G x. As P is internally disjoint
from any of the latter paths, conclude that G has k internally disjoint u-v paths.
Theorem 5.18. Mengers theorem. Let G be an undirected connected graph and let
u and v be distinct, non-adjacent vertices of G. Then the maximum number of internally
disjoint u-v paths in G equals the minimum number of vertices needed to separate u and
v.
Proof. Suppose that the maximum number of independent u-v paths in G is attained by
u-v paths P1 , . . . , Pk . To obtain a separating set W V , we must at least remove one
point in each path Pi . This implies the minimum number of vertices needed to separate
u and v is at least k. Therefore, we have an upper bound:
#{indep. u v paths} #{min. number of vertices needed to separate u and v}.
We show that equality holds. Let n denote the number of edges of G. The proof is by
induction on n. By hypothesis, n 2. If n = 2 the statement holds by inspection, since
in that case G is a line graph with 3 vertices V = {u, v, w} and 2 edges, E = {uw.wv}.
In that situation, there is only 1 u-v path (namely, uwv) and only one vertex separating
u and v (namely, w).
Suppose now n > 3 and assume the statement holds for each graph with < n edges.
Let
k = #{independent u v paths}
and let
` = #{min. number of vertices needed to separate u and v},
5.4. Whitneys Theorem
209
so that k `. Let e E and let G/e be the contraction graph having edges E {e}
and vertices the same as those of G, except that the endpoints of e have been identified.
Suppose that k < ` and G does not have ` independent u-v paths. The contraction
graph G/e does not have ` independent u-v paths either (where now, if e contains u or
v then we must appropriately redefine u or v, if needed). However, by the induction
hypothesis G/e does have the property that the maximum number of internally disjoint
u-v paths equals the minimum number of vertices needed to separate u and v. Therefore,
#{independent u v paths in G/e}
< #{min. number of vertices needed to separate u and v in G}.
By induction,
#{independent u v paths in G/e}
= #{min. number of vertices needed to separate u and v in G/e}.
Now, we claim we can pick e such that e does contain u or v and in such a way that
#{minimum number of vertices needed to separate u and v in G}
#{minimum number of vertices needed to separate u and v in G/e}.
Proof: Indeed, since n > 3 any separating set realizing the minimum number of vertices
needed to separate u and v in G cannot contain both a vertex in G adjacent to u and a
vertex in G adjacent to v. Therefore, we may pick e accordingly. (Q.E.D. claim)
The result follows from the claim and the above inequalities.
The following statement is the undirected, edge-connectivity version of Mengers theorem.
Theorem 5.19. Mengers theorem (edge-connectivity form). Let G be an undirected graph, and let s and t be vertices in G. Then, the maximum number of edgedisjoint (s, t)-paths in G equals the minimum number of edges from E(G) whose deletion
separates s and t.
This is proven the same way as the previous version but using the generalized mincut/max-flow theorem (see Remark 9.6 above).
Theorem 5.20. Diracs theorem. Let G = (V, E) be an undirected k-connected graph
with |V | k + 1 vertices for k 3. If S V is any set of k vertices, then G has a cycle
containing the vertices of S.
Proof.
5.4
Whitneys Theorem
Theorem 5.21. Whitneys theorem (vertex version). Suppose G = (V, E) is a

graph with |V | k + 1. The following are equivalent:
G is k-vertex-connected,
Any pair of distinct vertices v, w V are connected by at least k independent
paths.
210
Solution. ...
Theorem 5.22. Whitneys theorem (edge version). Suppose G = (V, E) is a

graph with |V | k + 1. The following are equivalent:
the graph G is k-edge-connected,
any pair of vertices are connected by at least k edge-disjoint paths.
Solution. ...
Theorem 5.23. Whitneys Theorem. Let G = (V, E) be a connected graph such that
|V | 3. Then G is 2-connected if and only if any pair u, v V has two internally
disjoint paths between them.
5.5
Centrality of a vertex
Louis, I think this is the beginning of a beautiful friendship.
Rick from the 1942 film Casablanca
degree centrality
betweenness centrality
closeness centrality
eigenvector centrality
Algorithm 5.1: Friendship graph.

Input: A positive integer n.
Output: The friendship graph Fn .
1
2
3
4
5
6
7
8
9
10
11
if n = 1 then
return C3
G null graph
N 2n + 1
for i 0, 1, . . . , N 3 do
if i is odd then
add edges (i, i + 1) and (i, N 1) to G
else
add edge (i, N 1) to G
add edges (N 2, 0) and (N 2, N 1) to G
return E
5.6. Network reliability
5.6
211
Network reliability
Whitney synthesis
Tuttes synthesis of 3-connected graphs
Harary graphs
constructing an optimal k-connected n-vertex graph
5.7
Problems
When you dont share your problems, you resent hearing the problems of other people.
Chuck Palahniuk, Invisible Monsters, 1999
5.1. Let G = (V, E) be an undirected, unweighted simple graph. Show that V and the
distance function on G form a metric space if and only if G is connected.
5.2. Let u and v be two distinct vertices in the same connected component of G. If P
is a u-v path such that d(u, v) = (u), we say that P is an eccentricity path for u.
(a) If r is the root of a tree, show that the end-vertex of an eccentricity path for
r is a leaf.
(b) If v is a vertex of a tree distinct from the root r, show that any eccentricity
path for v must contain r or provide an example to the contrary.
(c) A vertex w is said to be an eccentric vertex of v if d(v, w) = (v). Intuitively,
an eccentric vertex of v can be considered as being as far away from v as
possible. If w is an eccentric vertex of v and vice versa, then v and w are said
to be mutually eccentric. See Buckley and Lau [41] for detailed discussions of
mutual eccentricity. If w is an eccentric vertex of v, explain why v is also an
eccentric vertex of w or show that this does not in general hold.
5.3. If u and v are vertices of a connected graph G such that d(u, v) = diam(G), show
that u and v are mutually eccentric.
5.4. If uv is an edge of a tree T and w is a vertex of T distinct from u and v, show that
|d(u, w) d(w, v)| = W (uv) with W (uv) being the weight of uv.
5.5. If u and v are vertices of a tree T such that d(u, v) = diam(T ), show that u and v
are leaves.
5.6. Let v1 , v2 , . . . , vk be the leaves of a tree T . Show that per(T ) = {v1 , v2 , . . . , vk }.
5.7. Show that all the eccentric vertices of a tree are leaves.
5.8. If G is a connected graph, show that rad(G) diam(G) 2 rad(G).
5.9. Let T be a tree of order 3. If the center of T has one vertex, show that diam(T ) =
2 rad(T ). If the center of T has two vertices, show that diam(T ) = 2 rad(T ) 1.
212
5.10. Let G = (V, E) be a simple undirected, connected graph. Define the distance of a
vertex v V by
X
d(v) =
d(v, x)
xV
and define the distance of the graph G itself by

d(G) =
1X
d(v).
2 vV
For any vertex v V , show that d(G) d(v) + d(G v) with G v being a vertex
deletion subgraph of G. This result appeared in Entringer et al. [67, p.284].
5.11. Determine the sequence of distance matrices for the graphs in Figure 5.4.
5.12. If G = (V, E) is an undirected connected graph and v V , prove the following
vertex connectivity inequality:
(G) 1 (G v) (G).
5.13. If G = (V, E) is an undirected connected graph and e E, prove the following
edge connectivity inequality:
(G) 1 (G e) (G).
code
0
3
6
9
12
15
18
21
24
27
30
33
36
39
42
45
48
51
name
Alicante Bouschet
Cabernet Franc
Chardonnay
Donzillinho
Flora
Gr
uner Veltliner
Meslier-Saint-Francois
Muscat Hamburg
Ortega
Perle
Petit Manseng
Reichensteiner
Roter Veltliner
Ruby Cabernet
Semillon
Taminga
Traminer
Trousseau
code
1
4
7
10
13
16
19
22
25
28
31
34
37
40
43
46
49
52
name
Aramon
Cabernet Sauvignon
Chenin Blanc
Ehrenfelser
Gamay
Kemer
M
uller-Thurgau
Muscat of Alexandria
Osteiner
Perle de Csaba
Petite Bouschet
Riesling
Rotgipfler
Sauvignon Blanc
Siegerrebe
Teinturier du Cher
Trincadeiro
Verdelho
code
2
5
8
11
14
17
20
23
26
29
32
35
38
41
44
47
50
53
name
Bequignol
Carignan
Colombard
Fer Servadou
Gelber Ortlieber
Merlot
Muscat Blanc
Optima
Peagudo
Perlriesling
Pinot Noir
Rotberger
Royalty
Schonburger
Sylvaner
Tinta Madeira
Trollinger
Wittberger
Table 5.2: Numeric code and actual name of common grape cultivars.
5.14. Figure 5.8 depicts how common grape cultivars are related to one another; the
graph is adapted from Myles et al. [147]. The numeric code of each vertex can
be interpreted according to Table 5.2. Compute various distance and connectivity
measures for the graph in Figure 5.8.
5.15. Prove the characterizations of 2-connected graphs as stated in Theorem 5.13.
5.7. Problems
213
17
39
38
42
49
36
40
11
26
18
51
12
37
47
30
24
48
33
45
41
14
20
43
15
52
13
19
27
32
44
23
10
6
46
25
29
34
31
53
16
35
1
50
21
22
Figure 5.8: Network of common grape cultivars.
28
214
5.16. Let G = (V, E) be an undirected connected graph of order n and suppose that
deg(v) (n + k 2)/2 for all v V and some fixed positive integer k. Show that
G is k-connected.
5.17. A vertex (or edge) separating set S of a connected graph G is minimum if S has
the smallest cardinality among all vertex (respectively edge) separating sets in G.
Similarly S is said to be maximum if it has the greatest cardinality among all
vertex (respectively edge) separating sets in G. For the graph in Figure 5.7(a),
determine the following:
(a) A minimum vertex separating set.
(b) A minimum edge separating set.
(c) A maximum vertex separating set.
(d) A maximum edge separating set.
(e) The number of minimum vertex separating sets.
(f) The number of minimum edge separating sets.
Chapter 6
Optimal Graph Traversals
6.1
Eulerian graphs
multigraphs and simple graphs

Eulerian tours
Eulerian trails
6.2
Hamiltonian graphs

Hamiltonian paths (or cycles)
Hamiltonian graphs
Theorem 6.1. Ore 1960. Let G be a simple graph with n 3 vertices. If deg(u) +
deg(v) n for each pair of non-adjacent vertices u, v V (G), then G is Hamiltonian.
Corollary 6.2. Dirac 1952. Let G be a simple graph with n 3 vertices. If deg(v)
n/2 for all v V (G), then G is Hamiltonian.
6.3
The Chinese Postman Problem
See section 6.2 of Gross and Yellen [88].

de Bruijn sequences
215
216
Chapter 6. Optimal Graph Traversals

de Bruijn digraphs
constructing a (2, n)-de Bruijn sequence
postman tours and optimal postman tours
constructing an optimal postman tour
6.4
The Traveling Salesman Problem

See section 6.4 of Gross and Yellen [88], and section 35.2 of Cormen et al. [54].
Gray codes and n-dimensional hypercubes
the Traveling Salesman Problem (TSP)
nearest neighbor heuristic for TSP
some other heuristics for solving TSP
Chapter 7
Planar Graphs
A planar graph is a graph that can be drawn on a sheet of paper without any overlapping
between its edges.
It is a property of many natural graphs drawn on the earths surface, like for
instance the graph of roads, or the graph of internet fibers. It is also a necessary property
of graphs we want to build, like VLSI layouts.
Of course, the property of being planar does not prevent one from finding a drawing
with many overlapping between edges, as this property only asserts that there exists a
drawing (or embedding) of the graph avoiding it. Planarity can be characterized in many
different ways, one of the most satiating being Kuratowskis theorem.
See chapter 9 of Gross and Yellen [88].
7.1
Planarity and Eulers Formula
planarity, non-planarity, planar and plane graphs

crossing numbers
Theorem 7.1. The complete bipartite graph K3,n is non-planar for n 3.

Theorem 7.2. Eulers Formula. Let G be a connected plane graph having n vertices,
e edges and f faces. Then n e + f = 2.
7.2
Kuratowskis Theorem
Kuratowski graphs
The objective of this section is to prove the following theorem.

Theorem 7.3. [124] Kuratowskis Theorem. A graph is planar if and only if it
contains no subgraph homeomorphic to a subdivision of K5 or K3,3 .
Graph Minors : The reader may find interesting to notice that the previous result, first proved in 1930 as purely topological (there is no mention of graphs in Kuratowskis original paper), can be seen as a very special case of the Graph Minor Theorem
(Thm1.29).
217
218
Chapter 7. Planar Graphs
(a) Errera graph.
(b) Planar representation.
Figure 7.1: The Errera graph is planar.
7.3. Planarity algorithms
219
It can easily be seen that if a graph G is planar, any of its subgraph is also planar.
Besides, planarity is still preserved under edge contraction. These two facts mean together that any minor of a planar graph is still planar graph, which makes of planarity
a minor-closed property. If we let P denote the poset of all non-planar graph, ordered
with the minor partial order, we can now consider the set Pmin of its minimal elements
which, by the Graph Minor Theorem, is a finite set.
Actually, Kuratowskis theorem asserts that Pmin = {K5 , K3,3 }.
7.3
Planarity algorithms
planarity testing for 2-connected graphs

planarity testing algorithm of Hopcroft and Tarjan [99]
planarity testing algorithm of Boyer and Myrvold [33]
Chapter 8
Graph Coloring

See Jensen and Toft [106] for a survey of graph coloring problems.
See Dyer and Frieze [63] for an algorithm on randomly colouring random graphs.
8.1
Vertex coloring
Vertex coloring is a widespread center of interest in graph theory, which has many variants. Formally speaking, a coloring of the vertex set of a graph G is any function
f : V (G) 7 {1, . . . , k} giving to each vertex a color among a set of cardinal k. Things
get much more difficult when we add to it the constraint under which a coloring becomes
a proper coloring : a coloring with k colors of a graph G is said to be proper if there are
no edges between any two vertices colored with the same color. This can be rephrased
in many different ways :
i {1, . . . , k}, G[f 1 (i)] is a stable set
u, v G, u 6= v, f (u) = f (v) uv 6 E(G)
A proper coloring of G with k colors is a partition of V (G) into k independent sets
220
8.2. Edge coloring
221
Chromatic numbers : quite clearly, it is always possible to find a proper coloring

of a graph G using one color per vertex. For this reason, the Coloring Problem is an
optimisation problem which amounts to finding the least number k of colors such that
G can be properly colored with k colors is k-colorable. This integer, written (G), is
called the chromatic number of G.
Greedy coloring, and an easy upper bound : the simple fact that Graph Coloring is a NP-complete problem must not prevent one from trying to color it greedily.
One such method would be to iteratively pick, in a graph G, an uncolored vertex v, and
to color it with the smallest color available which is not yet used by one of its neighbors
(in order to keep it proper). Such a coloring will obviously stay proper until the whole
vertex set is colored, and never use more than (G) + 1 different colors (where (G)
is the maximal degree of G), as in the procedure no vertex will ever exclude more than
(G) colors.
Such an algorithm can be written in Sage in a few lines :
sage :
sage :
sage :
sage :
...
...
g = graphs . RandomGNP (100 ,5/100)

C = Set ( xrange (100))
color = {}
for u in g :
interdits = Set ([ color [ v ] for v in g . neighbors ( u ) if color . has_key ( v )])
color [ u ] = min (C - interdits )
Brooks Theorem
heuristics for vertex coloring
8.2
Edge coloring
Edge coloring is the direct application of vertex coloring to the line graph of a graph G,
written L(G), which is the graph whose vertices are the edges of G, two vertices being
adjacent if and only if their corresponding edges share an endpoint. We write (L(G)) =
0 (G) the chromatic index of G. In this special case, however, the optimization problem
defined above, though still NP-Complete, is much better understood through Vizings
theorem.
Theorem 8.1 (Vizing). The edges of a graph G can be properly colored using at least
(G) colors and at most (G) + 1
Notice that the lower bound can be easily proved : if a vertex v has a degree d(v),
then at least d(v) colors are required to color G as all the edges incident to v must
receive different colors. Besides, the upper bound of (G) + 1 can not be deduced from
the greedy algorithm given in the previous section, as the maximal degree of L(G) is not
equal to (G) but to max d(u) + d(v) 2, which can reach 2(G) 2 in regular graphs.
uv
algorithm for edge coloring by maximum matching

algorithm for sequential edge coloring
8.3
Applications of graph coloring
assignment problems
222
Chapter 8. Graph Coloring

scheduling problems
matching problems
map coloring and the Four Color Problem
Chapter 9
Network Flows
See Jungnickel [112], and chapter 12 of Gross and Yellen [88].
9.1
Flows and cuts
single source-single sink networks

feasible networks
maximum flow and minimum cut
9.2
Ford-Fulkerson theorem
The Ford-Fulkerson Theorem, or Max-flow/Min-cut Theorem, was proven by P. Elias,

A. Feinstein, and C.E. Shannon in 1956, and, independently, by L.R. Ford, Jr. and D.R.
Fulkerson in the same year. So it should be called the Elias-Feinstein-Ford-FulkersonShannon Theorem, to be precise about the authorship.
To explain the meaning of this theorem, we need to introduce some notation and
terminology.
Consider an edge-weighted simple digraph G = (V, E, i, h) without negative weight
cycles. Here E V (2) , i is an incidence function as in (??), which we regard as the
identity function, and h is an orientation function as in (??). Let G be a network,
with two distinguished vertices, the source and the sink. Let s and t denote the
source and the sink of G, respectively. The capacity (or edge capacity) ) is a mapping
c : E R, denoted by cuv or c(u, v), for (u, v) E and h(e) = u. If (u, v) E
and h(e) = v then we set, by convention, c(v, u) = c(u, v). Thinking of a graph as
a network of pipes (representing the edges) transporting water with various junctions
(representing vertices), the capacity function represents the maximum amount of flow
that can pass through an edge.
A flow is a mapping f : E R, denoted by fuv or f (u, v), subject to the following
two constraints:
f (u, v) c(u, v), for each (u, v) V (the capacity constraint),
uV, (u,v)E
f (u, v) =
uV, (v,u)E
f (v, u) , for each v V (conservation of flows).

223
224
Chapter 9. Network Flows
An edge (u, v) E is f -saturated if f (u, v) = c(u, v). An edge (u, v) E is f -zero

if f (u, v) = 0. A path with available capacity is called an augmenting path. More
precisely, a directed path form s to t is f -augmenting, or f -unsaturated, if no forward
edge is f -saturated and no backward edge is f -zero.
The value of the flow is defined by
X
X
|f | =
f (s, v)
f (v, s),
vV
vV
where s is the source. It represents the amount of flow passing from the source to the
sink. The maximum flow problem is to maximize |f |, that is, to route as much flow as
possible from s to t.
Example 9.1. Consider the digraph having
0
1
1
1 0 1
1 1
0
0 1 0
0
0 1
0 1 0
depicted in Figure 9.1.
adjacency matrix
0
0 0
1
0 1
0
1 0
,
0
0 1
0
0 1
1 1 0
Figure 9.1: A digraph with 6 vertices.

Suppose that each edge has capacity 1. A maximum flow f is obtained by taking a
flow value of 1 along each edge of the path
p1 : (0, 1), (1, 5),
and a flow value of 1 along each edge of the path
p2 : (0, 2), (2, 4), (4, 5).
The maximum value of the flow in this case is |f | = 2.
This graph can be created in Sage using the commands
sage : B = matrix ([[0 ,1 ,1 ,0 ,0 ,0] ,[0 ,0 ,0 ,1 ,0 ,1] ,[0 ,1 ,0 ,0 ,1 ,0] ,[0 ,0 ,0 ,0 ,0 ,1] ,[0 ,0 ,0 ,0 ,0 ,1] ,[0 ,0 ,
sage : H = DiGraph (B , format = " adjacency_matrix " , weighted = True )
Type H.show(edgewlabels=True) if you want to see the graph with the capacities labeling the edges.
9.2. Ford-Fulkerson theorem
225
Given a capacitated digraph with capacity c and flow f , we define the residual digraph
Gf = (V, E) to be the digraph with capacity cf (u, v) = c(u, v) f (u, v) and no flow. In
other words, Gf is the same graph but it has a different capacity cf and flow 0. This is
also called a residual network.
Define an s t cut in our capacitated digraph G to be a partition C = (S, T ) of V
such that s S and t T . Recall the cut-set of C is the set
{(u, v) E | u S, v T }.
Lemma 9.2. Let G = (V, E) be a capacitated digraph with capacity c : E R, and
let s and t denote the source and the sink of G, respectively. If C is an s t cut and if
the edges in the cut-set of C are removed, then |f | = 0.
Exercise 9.3. Prove Lemma 9.2.
The capacity of an s t cut C = (S, T ) is defined by
X
c(S, T ) =
c(u, v).
(s,t)(S,T )
The minimum cut problem is to minimize the amount of capacity of an s t cut.

The following theorem is due to P. Elias, A. Feinstein, L.R. Ford, Jr., D.R. Fulkerson,
C.E. Shannon.
Theorem 9.4. (max-flow min-cut theorem) The maximum value of an s-t flow is equal
to the minimum capacity of an s-t cut.
The intuitive explanation of this result is as follows.
Suppose that G = (V, E) is a graph where each edge has capacity 1. Let s V be the
source and t V be the sink. The maximum flow from s to t is the maximum number
of independent paths from s to t. Denote this maximum flow by m. Each s-t cut must
intersect each s-t path at least once. In fact, if S is a minimal s-t cut then for each edge
e in S there is an s-t path containing e. Therefore, |S| e.
On the other hand, since each edge has unit capacity, the maximum flow value cant
exceed the number of edges separating s from t, so m |S|.
Remark 9.5. Although the notion of an independent path is important for the networktheoretic proof of Mengers theorem (which we view as a corollary to the Ford-Fulkerson
theorem on network flows on networks having capacity 1 on all edges), its significance
is less important for networks having arbitrary capacities. One must use caution in
generalizing the above intuitive argument to establish a rigorous proof of the general
version of the MFMC theorem.
Remark 9.6. This theorem can be generalized as follows. In addition to edge capacity,
suppose there is capacity at each vertex, that is, a mapping c : V R, denoted by
v 7 c(v), such that the flow f has to satisfy not only the capacity constraint and the
conservation of flows, but also the vertex capacity constraint
X
f (w, v) c(v),
wV
for each v V {s, t}. Define an s t cut to be the set of vertices and edges such
that for any path from s to t, the path contains a member of the cut. In this case, the
226
capacity of the cut is the sum the capacity of each edge and vertex in it. In this new
definition, the generalized max-flow min-cut theorem states that the maximum value of
an s t flow is equal to the minimum capacity of an s t cut..
The idea behind the Ford-Fulkerson algorithm is very simple: As long as there is a
path from the source to the sink, with available capacity on all edges in the path, we
send as much flow as we can alone along each of these paths. This is done inductively,
one path at a time.
Algorithm 9.1: Ford-Fulkerson algorithm.
Input: Graph G = (V, E) with flow capacity c, source s, and sink t.
Output: A flow f from s to t which is a maximum for all edges in E.
1
2
3
4
5
6
f (u, v) 0 for each edge uv E

while there is an s-t path p in Gf such that cf (e) > 0 for each edge e E do
find cf (p) = min{cf (u, v) | (u, v) p}
for each edge uv do
f (u, v) = f (u, v) + cf (p)
f (v, u) = f (v, u) cf (p)
To prove the max-flow/min-cut theorem we will use the following lemma.
Lemma 9.7. Let G = (V, E) be a directed graph with edge capacity c : E Z, a

source s V , and a sink t V . A flow f : E Z is a maximum flow if and only if
there is no f -augmenting path in the graph.
In other words, a flow f in a capacitated network is a maximum flow if and only if
there is no f -augmenting path in the network.
Solution. One direction is easy. Suppose that the flow is a maximum. If there is an
f -augmenting path then the current flow can be increased using that path, so the flow
would not be a maximum. This contradiction proves the only if direction.
Now, suppose there is no f -augmenting path in the network. Let S be the set of
vertices v such that there is an f -unsaturated path from the source s to v. We know
s S and (by hypothesis) t
/ S. Thus there is a cut of the form (S, T ) in the network.
Let e = (v, w) be any edge in this cut, v S and w T . Since there is no f -unsaturated
path from s to w, e is f -saturated. Likewise, any edge in the cut (T, S) is f -zero.
Therefore, the current flow value is equal to the capacity of the cut (S, T ). Therefore,
the current flow is a maximum.
We can now prove the max-flow/min-cut theorem.
Solution. Let f be a maximum flow. If
S = {v V | there exists an f saturated path from s to v},
then by the previous lemma, S 6= V . Since T = V S is non-empty, there is a cut
C = (S, T ). Each edge of this cut C in the capacitated network G is f -saturated.
9.2. Ford-Fulkerson theorem
227
Here is some Python code1 which implements this. The class FlowNetwork is basically
a Sage Graph class with edge weights and an extra data structure representing the flow
on the graph.
class Edge :
def __init__ ( self ,U ,V , w ):
self . source = U
self . to = V
self . capacity = w
def __repr__ ( self ):
return str ( self . source ) + " ->" + str ( self . to ) + " : " + str ( self . capacity )
class FlowNetwork ( object ):
"""
This is a graph structure with edge capacities .
EXAMPLES :
g = FlowNetwork ()
map ( g . add_vertex , [ s ,o ,p ,q ,r ,t ])
g . add_edge ( s ,o ,3)
g . add_edge ( s ,p ,3)
g . add_edge ( o ,p ,2)
g . add_edge ( o ,q ,3)
g . add_edge ( p ,r ,2)
g . add_edge ( r ,t ,3)
g . add_edge ( q ,r ,4)
g . add_edge ( q ,t ,2)
print g . max_flow ( s ,t )
"""
def __init__ ( self ):
self . adj , self . flow , = {} ,{}
def add_vertex ( self , vertex ):
self . adj [ vertex ] = []
def get_edges ( self , v ):
return self . adj [ v ]
def add_edge ( self , u ,v , w =0):
assert ( u != v )
edge = Edge (u ,v , w )
redge = Edge (v ,u ,0)
edge . redge = redge
redge . redge = edge
self . adj [ u ]. append ( edge )
self . adj [ v ]. append ( redge )
self . flow [ edge ] = self . flow [ redge ] = 0
def find_path ( self , source , sink , path ):
if source == sink :
return path
for edge in self . get_edges ( source ):
residual = edge . capacity - self . flow [ edge ]
if residual > 0 and not ( edge , residual ) in path :
result = self . find_path ( edge . to , sink , path + [ ( edge , residual ) ])
if result != None :
return result
def max_flow ( self , source , sink ):
path = self . find_path ( source , sink , [])
while path != None :
flow = min ( res for edge , res in path )
for edge , res in path :
self . flow [ edge ] += flow
self . flow [ edge . redge ] -= flow
path = self . find_path ( source , sink , [])
return sum ( self . flow [ edge ] for edge in self . get_edges ( source ))
Please see http://en.wikipedia.org/wiki/Ford-Fulkerson_algorithm.
228
9.3
Edmonds and Karps algorithm
The objective of this section is to prove Edmond and Karps algorithm for the maximum
flow-minimum cut problem with polynomial complexity.
9.4
Goldberg and Tarjans algorithm
The objective of this section is to prove Goldberg and Tarjans algorithm for finding
maximal flows with polynomial complexity.
Chapter 10
Random Graphs
A random graph can be thought of as being a member from a collection of graphs having
some common properties. Recall that Algorithm 3.5 allows for generating a random
binary tree having at least one vertex. Fix a positive integer n and let T be a collection
of all binary trees on n vertices. It can be infeasible to generate all members of T , so for
most purposes we are only interested in randomly generating a member of T . A binary
tree of order n generated in this manner is said to be a random graph.
This chapter is a digression into the world of random graphs and various models for
generating different types of random graphs. Unlike other chapters in this book, our
approach is rather informal and not as rigorous as in other chapters. We will discuss
some common models of random graphs and a number of their properties without being bogged down in details of proofs. Along the way, we will demonstrate that random
graphs can be used to model diverse real-world networks such as social, biological, technological, and information networks. Bollobas [25] and Kolchin [121] provide standard
references on the theory of random graphs with rigorous proofs. For comprehensive
surveys of random graphs and networks that do not go into too much technical details, see Barabasi [12], Easley and Kleinberg [64], and Watts [190, 191]. On the other
hand, surveys that cover diverse applications of random graphs and networks and are
geared toward the technical aspects of the subject include Albert and Barabasi [5], Barrat et al. [16], Ben-Naim et al. [22], Bollobas et al. [26], Bornholdt and Schuster [30], Caldarelli and Vespignani [42], Cohen and Havlin [53], Csermely [55], Dehmer and EmmertStreib [57], Dorogovtsev and Mendes [60, 61], Ganguly et al. [82], Gross and Sayama [89],
Newman et al. [148], and Newman [152, 153].
10.1
Network statistics
Numerous real-world networks are large, having from thousands up to millions of vertices
and edges. Network statistics provide a way to describe properties of networks without
concerning ourselves with individual vertices and edges. A network statistic should
describe essential properties of the network under consideration, provide a means to
differentiate between different classes of networks, and be useful in network algorithms
and applications [35]. In this section, we discuss various common network statistics that
can be used to describe graphs underlying large networks.
229
230
Chapter 10. Random Graphs
10.1.1
Degree distribution
The degree distribution of a graph G = (V, E) quantifies the fraction of vertices in G

having a specific degree k. If v is any vertex of G, we denote this fraction by
p = Pr[deg(v) = k].
(10.1)
As indicated by the notation, we can think of (10.1) as the probability that a vertex v V
chosen uniformly at random has degree k. The degree distribution of G is consequently a
histogram of the degrees of vertices in G. Figure 10.1 illustrates the degree distribution
of the Zachary [201] karate club network. The degree distributions of many real-world
networks have the same general curve as depicted in Figure 10.1(b), i.e. a peak at low
degrees followed by a tail at higher degrees. See for example the degree distribution of
the neural network in Figure 10.2, that of a power grid network in Figure 10.3, and the
degree distribution of a scientific coauthorship network in Figure 10.4.
0.3
0.25
0.2
0.15
0.1
5 102
2
(a) Zachary karate club network.
10
12
14
16
(b) Linear scaling.
100.6
100.8
101
101.2
101.4
100
100.2
100.4
100.6
100.8
101
101.2
(c) Log-log scaling.
Figure 10.1: The friendship network within a 34-person karate club. This is more commonly known as the Zachary [201] karate club network. The network is an undirected,
connected, unweighted graph having 34 vertices and 78 edges. The horizontal axis represents degree; the vertical axis represents the probability that a vertex from the network
has the corresponding degree.
10.1. Network statistics
231
102
6
101.5
4
102
2
20
40
60
80
100
120
100
(a) Linear scaling.
101
102
(b) Log-log scaling.
Figure 10.2: Degree distribution of the neural network of the Caenorhabditis elegans.
The network is a directed, not strongly connected, weighted graph with 297 vertices
and 2,359 edges. The horizontal axis represents degree; the vertical axis represents the
probability that a vertex from the network has the corresponding degree. The degree
distribution is derived from dataset by Watts and Strogatz [192] and White et al. [193].
0.3
101
0.2
102
0.1
103
10
(a) Linear scaling.
15
100
100.2
100.4
100.6
100.8
101
101.2
Figure 10.3: Degree distribution of the Western States Power Grid of the United States.
The network is an undirected, connected, unweighted graph with 4,941 vertices and 6,594
edges. The horizontal axis represents degree; the vertical axis represents the probability
that a vertex from the network has the corresponding degree. The degree distribution is
derived from dataset by Watts and Strogatz [192].
232

101
0.12
0.1
102
8 102
6 102
103
4 102
104
2 102
0
50
100
150
200
250
(a) Linear scaling.
100
101
102
Figure 10.4: Degree distribution of the network of coauthorships between scientists posting preprints on the condensed matter eprint archive at http://arxiv.org/archive/
cond-mat. The network is a weighted, disconnected, undirected graph having 40,421
vertices and 175,693 edges. The horizontal axis represents degree; the vertical axis
represents the probability that a vertex from the coauthorship network has the corresponding degree. The degree distribution is derived from the 2005 update of the dataset
by Newman [150].
10.1.2
Distance statistics
In chapter 5 we discussed various distance metrics such as radius, diameter, and eccentricity. To that distance statistics collection we add the average or characteristic distance
d, defined as the arithmetic mean of all distances in a graph. Let G = (V, E) be a simple
graph with n = |V | and m = |E|, where G can be either directed or undirected. Then
G has size at most n(n 1) because for any distinct vertex pair u, v V we count the
edge from u to v and the edge from v to u. The characteristic distance of G is defined
by
X
1
d(G) =
d(u, v)
n(n 1) u6=vV
where the distance function
d(u, v) = 0,
k,
d is given by
if there is no path from u to v,
if u = v,
where k is the length of a shortest u-v path.
If G is strongly connected (respectively, connected for the undirected case) then our
distance function is of the form d : V V Z+ {0}, where the codomain is the
set of nonnegative integers. The case where G is not strongly connected (respectively,
disconnected for the undirected version) requires special care. One way is to compute
the characteristic distance for each component and then find the average of all such
characteristic distances. Call the resulting characteristic distance dc , where c means
component. Another way is to assign a large number as the distance of non-existing
shortest paths. If there is no u-v path, we let d(u, v) = n because n = |V | is larger than
the length of any shortest path between connected vertices. The resulting characteristic
distance is denoted db , where b means big number. Furthermore denote by d the number
10.2. Binomial random graph model
233
of pairs (u, v) such that v is not reachable from u. For example, the Zachary [201] karate
club network has d = 2.4082 and d = 0; the C. elegans neural network [192, 193]
has db = 71.544533, dc = 3.991884, and d = 20, 268; the Western States Power Grid
network [192] has d = 18.989185 and d = 0; and the condensed matter coauthorship
network [150] has db = 7541.74656, dc = 5.499329, and d = 152, 328, 281.
We can also define the concept of distance distribution similar to how the degree
distribution was defined in section 10.1.1. If ` is a positive integer with u and v being
connected vertices in a graph G = (V, E), denote by
p = Pr[d(u, v) = `]
(10.2)
the fraction of ordered pairs of connected vertices in V V having distance ` between

them. As is evident from the above notation, we can think of (10.2) as the probability
that a uniformly chosen connected pair (u, v) of vertices in G has distance `. The distance
distribution of G is hence a histogram of the distances between pairs of vertices in G.
Figure 10.5 illustrates distance distributions of various real-world networks.
Algorithm 10.1: Generate a random graph in G(n, p).
Input: Positive integer n and a probability 0 < p < 1.
Output: A random graph from G(n, p).
1
2
3
4
5
6
7
8
G Kn
V {0, 1, . . . , n 1}
E {2-combinations of V }
for each e E do
r draw uniformly at random from interval (0, 1)
if r < p then
add edge e to G
return G
10.2
Binomial random graph model
Fix a positive integer n, a probability p, and a vertex set V = {0, 1, . . . , n1}. The binomial (or Bernoulli ) random graph model, denoted G(n, p) and introduced by Gilbert [84],
is formally a probability space over the set of undirected simple graphs on n vertices. If
G is any element of the probability space G(n, p) and ij is any edge for distinct i, j V ,
then ij occurs as an edge of G independently with probability p. In symbols, for any
distinct pair i, j V we have
Pr[ij E(G)] = p
where all such events are mutually independent. Equivalently the model G(n, p) considers
the collection
of all undirected simple graphs on n vertices, each such graph having at

n
most 2 edges, m actual edges, and an associated probability
n
pm (1 p)( 2 )m .
(10.3)
Notice the latters resemblance to the binomial distribution. By G G(n, p) we mean

that G is a random graph of the space G(n, p) and having probability distribution G(n, p).
234
0.3
0.4
0.2
0.3
0.2
0.1
0.1
(a) Zachary karate club network [201].
10
12
14
(b) C. elegans neural network [192, 193].
102
0.3
5
4
0.2
3
2
0.1
1
0
10
20
30
(c) Power grid network [192].
40
(d) Condensed
work [150].
10
matter
12
14
16
coauthorship
18
net-
Figure 10.5: Distance distributions for various real-world networks. The horizontal axis
represents distance and the vertical axis represents the probability that a uniformly
chosen pair of distinct vertices from the network has the corresponding distance between
them.
235
To generate a random graph in G(n, p), start with G being a graph on n vertices but
no edges. That is, initially
G is Kn , the complement of the complete graph on n vertices.
Consider each of the n2 possible edges in some order and add it independently to G
with probability p. See Algorithm 10.1 for pseudocode of the procedure. The runtime
of Algorithm 10.1 depends on an efficient algorithm for generating all 2-combinations of
a set of n objects. We could adapt Algorithm 4.22 to our needs or search for a more
efficient algorithm; see problem 10.3 for discussion of an algorithm to generate a graph
in G(n, p) in quadratic time. Figure 10.6 illustrates some random graphs from G(25, p)
with p = i/6 for i = 0, 1, . . . , 5. See Figure 10.7 for results for graphs in G(2 104 , p).
The expected number of edges of any G G(n, p) is

n
pn(n 1)
= E[|E|] = p
=
2
2
and the expected total degree is

n
= E[# deg] = 2p
= pn(n 1).
2
Then the expected degree of each edge is p(n 1). From problem 1.7 we know that the
number of undirected simple graphs on n vertices is given by
2n(n1)/2
where (10.3) is the probability of any of these graphs being the output of the above
procedure. Let (n, m) be the number of graphs from G(n, p) that are connected and
have size m, and by Pr[G ] is meant the probability that G G(n, p) is connected. Apply
expression (10.3) to see that
Pr[G ] =
(n2 )
X
i=n1
n
(n, i) pi (1 p)( 2 )i
where n 1 is the least number of edges of any undirected connected graph on n vertices,
i.e. the size of any spanning tree of a connected graph in G(n, p). Similarly define
Pr[ij ] to be the probability that two distinct vertices i, j of G G(n, p) are connected.
Gilbert [84] showed that as n , the probabilities Pr[G ] and Pr[ij ] approach
Pr[G ] 1 n(1 p)n1
and
Pr[ij ] 1 2(1 p)n1 .
Example 10.1. Consider a digraph D = (V, E) without self-loops or multiple edges.
Then D is said to be oriented if for any distinct pair u, v V at most one of uv, vu is
an edge of D. Provide specific examples of oriented graphs.
Solution. If u, v V is any pair of distinct vertices of an oriented graph D = (V, E), we
have various possibilities:
1. uv
/ E and vu
/ E.
236
(a) p = 0; = 0, |E| = 0; = 0, # deg = 0
(b) p = 1/6; = 50, |E| = 44; = 100,

# deg = 88
(c) p = 1/3; = 100, |E| = 108; = 200,

# deg = 212
(d) p = 1/2; = 150, |E| = 156; = 300,

# deg = 312
(e) p = 2/3; = 200, |E| = 185; = 400,

# deg = 370
(f) p = 5/6; = 250, |E| = 255; = 500,

# deg = 510
Figure 10.6: Binomial random graphs G(25, p) for various values of p.
237
108
0.2
0.4
0.6
0.8
Figure 10.7: Comparison of expected and experimental values of the number of edges
and total degree of random simple undirected graphs in G(n, p). The horizontal axis
represents probability points; the vertical axis represents the size and total degree (expected or experimental). Fix n = 20, 000 and consider r = 50 probability points chosen
as follows. Let pmin = 0.000001, pmax = 0.999999, and F = (pmax /pmin )1/(r1) . For
i = 1, 2, . . . , r = 50 the i-th probability point pi is defined by pi = pmin F i1 . Each
experiment consists in generating M = 500 random graphs from G(n, pi ). For each
Gi G(n, pi ), where i = 1, 2, . . . , 500, compute its actual size i and actual total degree
i . Then take the mean
of the i and the mean of the i .
Algorithm 10.2: Random oriented graph via G(n, p).

Input: Positive integer n and probability 0 < p < 1.
Output: A random oriented graph on n vertices.
1
2
3
4
5
6
7
8
9
10
11
G random graph in G(n, p) as per Algorithm 10.3

E edge set of G
G directed version of G
cutoff draw uniformly at random from interval (0, 1)
if r < cutoff then
remove uv from G
else
remove vu from G
return G
238
2. uv E and vu
/ E.
3. uv
/ E and vu E.
Let n > 0 be the number of vertices in D and let 0 < p < 1. Generate a random
oriented graph as follows. First we generate a binomial random graph G G(n, p) where
G is simple and undirected. Then we consider the digraph version of G and proceed to
randomly prune either uv or vu from G, for each distinct pair of vertices u, v. Refer to
Algorithm 10.2 for pseudocode of our discussion. A Sage implementation follows:
sage :
sage :
sage :
sage :
sage :
...
...
...
...
...
G = graphs . RandomGNP (20 , 0.1)

E = G . edges ( labels = False )
G = G . to_directed ()
cutoff = 0.5
for u , v in E :
r = random ()
if r < cutoff :
G . delete_edge (u , v )
else :
G . delete_edge (v , u )
which produced the random oriented graph in Figure 10.8.
Figure 10.8: A random oriented graph generated using a graph in G(20, 0.1) and cutoff
probability 0.5.
Efficient generation of sparse G G(n, p)

The techniques discussed so far (Algorithms 10.1 and 10.9) for generating a random
graph from G(n, p) can be unsuitable when the number of vertices n is in the hundreds
of thousands or millions. In many applications of G(n, p) we are only interested in sparse
random graphs. A linear time algorithm to generate a random sparse graph from G(n, p)
is presented in Batagelj and Brandes [18].
The Batagelj-Brandes algorithm for generating a random sparse graph G G(n, p)
uses what is known as a geometric method to skip over certain edges. Fix a probability
239
0 < p < 1 that an edge will be in the resulting random sparse graph G. If e is an edge
of G, we can consider the events leading up to the choice of e as
e1 , e2 , . . . , ek
where in the i-th trial the event ei is a failure, for 1 i < k, but the event ek is the
first success after k 1 successive failures. In probabilistic terms, we perform a series
of independent trials each having success probability p and stop when the first success
occurs. Letting X be the number of trials required until the first success occurs, then X
is a geometric random variable with parameter p and probability mass function
Pr[X = k] = p(1 p)k1
for integers k 1, where
X
k=1
(10.4)
p(1 p)k1 = 1.
In other words, waiting times are geometrically distributed.

Suppose we want to generate a random number from a geometric distribution, i.e.
we want to simulate X such that
Pr[X = k] = p(1 p)k1 ,
Note that
`
X
k=1
k = 1, 2, 3, . . .
Pr[X = k] = 1 Pr[X > ` 1] = 1 (1 p)`1 .
In other words, we can simulate a geometric random variable by generating r uniformly

at random from the interval (0, 1) and set X to that value of k for which
1 (1 p)k1 < r < 1 (1 p)k
or equivalently for which
(1 p)k < 1 r < (1 p)k1
where 1 r and r are both uniformly distributed. Thus we can define X by
X = min{k | (1 p)k < 1 r}

ln(1
r)
= min k k >
ln(1 p)

ln(1 r)
=1+
.
ln(1 p)
That is, we can choose k to be

ln(1 r)
k =1+
ln(1 p)
which is used as a basis of Algorithm 10.3. In the latter algorithm, note that the vertex
set is V = {0, 1, . . . , n 1} and candidate edges are generated in lexicographic order.
The Batagelj-Brandes Algorithm 10.3 has worst-case runtime O(n + m), where n and m
are the order and size, respectively, of the resulting graph.
240
Algorithm 10.3: Linear generation of a random sparse graph in G(n, p).

Output: A random sparse graph from G(n, p).
1
2
3
4
5
6
7
8
9
10
11
12
G Kn
u1
v 1
while u < n do
v v + 1 + bln(1 r)/ ln(1 p)c
while v u and u < n do
v vu
uu+1
if u < n then
add edge uv to G
return G
Degree distribution
Consider a random graph G G(n, p) and let v be a vertex of G. With probability p, the
vertex v is incident with each of the remaining n 1 vertices in G. Then the probability
that v has degree k is given by the binomial distribution

n1 k
Pr[deg(v) = k] =
p (1 p)n1k
(10.5)
k
and the expected degree of v is E[deg(v)] = p(n 1). Setting z = p(n 1), we can
express (10.5) as

k
n1
z
n1
z
Pr[deg(v) = k] =
1
k
n1z
n1
and thus
zk
exp(z)
k!
as n . In the limit of large n, the probability that vertex v has degree k approaches
the Poisson distribution. That is, as n gets larger and larger any random graph in G(n, p)
has a Poisson degree distribution.
Pr[deg(v) = k]
10.3
Erd
os-R
enyi model
Let N be a fixed nonnegative integer. The Erdos-Renyi [69, 70] (or uniform) random
graph model, denoted G(n, N ), is a probability space over the set of undirected simple
graphs on n vertices and exactly N edges. Hence G(n, N ) can be considered as a collection
n
of ( 2 ) undirected simple graphs on exactly N edges, each such graph being selected with
N
equal probability. A note of caution is in order here. Numerous papers on random graphs
refer to G(n, p) as the Erdos-Renyi random graph model, where in fact this binomial
random graph model should be called the Gilbert model in honor of E. N. Gilbert who
10.3. Erdos-Renyi model
241
introduced [84] it in 1959. Whenever a paper makes a reference to the Erdos-Renyi

model, one should question whether the paper is referring to G(n, p) or G(n, N ).
To generate a graph in G(n, N ), start
with G being a graph on n vertices but no
n
edges. Then choose N of the possible 2 edges independently and uniformly at random
and let the chosen edges be the edge set of G. Each graph G G(n, N ) is associated
with a probability

n
2
of being the graph resulting from the above procedure. Furthermore each of the
edges has a probability

n
1
2
n
2
of being chosen. Algorithm 10.4 presents a straightforward translation of the above

procedure into pseudocode.
Algorithm 10.4: Generation of random graph in G(n, N ).
Input: Positive integer n and integer N with 0 N

Output: A random graph from G(n, N ).
1
2
3
4
5
6
7
8
GK
nn
E e0 , e1 , . . . , e(n)1
2
n
2
for i 0, 1, . . . , N 1 do

r draw uniformly at random from 0, 1, . . . , n2 1
while er is an edge of G do

r draw uniformly at random from 0, 1, . . . , n2 1
add edge er to G
return G
The runtime of Algorithm 10.4 is probabilistic and can be analyzed via the geometric
distribution. If i is the number of edges chosen so far, then the probability of choosing
a new edge in the next step is

n
i
2
.
n
2
We repeatedly choose an edge uniformly at random from the collection of all possible
edges, until we come across the first edge that is not already in the graph. The number
of trials required until the first new edge is chosen can be modeled using the geometric
distribution with probability mass function (10.4). Given a geometric random variable
X, we have the expectation
E[X] =
1
n p(1 p)n1 = .
p
n=1
Therefore the expected number of trials until a new edge be chosen is

n
2

n
i
2
242
from which the expected total runtime is

Z N
N
n
n
X
2
2
dx
n
n
i
x
0
2
i=1 2

n
n
2
=
ln n
.
2
N
2

The denominator in the latter fraction becomes zero when n2 = N , which can be
prevented by adding one to the denominator. Then we have the expected total runtime
!

N
n
n
X
n
2
ln n 2
n
2
i
N +1
2
i=1 2

which is O(N ) when N n2 /2, and O(N ln N ) when N = n2 . In other words,
Algorithm
runtime when the number N of required edges satisfies
10.4 has expected linear

N n2 /2. But for N > n2 /2, we obtain expected
linear runtime by generating the

n
complete graph Kn and randomly delete 2 N edges from the latter graph. Our
discussion is summarized in Algorithm 10.5.
Algorithm 10.5: Generation of random graph in G(n, N ) in expected linear time.

Input: Positive integer n and integer N with 0 N n2 .

n
1 if N
/2 then
2
2
return result of Algorithm 10.4
3 G Kn

n
4 for i 1, 2, . . . ,
N do
2
5
e draw uniformly at random from E(G)
6
remove edge e from G
7 return G
10.4
Small-world networks
Many real-world networks exhibit the small-world effect: that most pairs of distinct
vertices in the network are connected by relatively short path lengths. The small-world
effect was empirically demonstrated [144] in a famous 1960s experiment by Stanley Milgram, who distributed a number of letters to a random selection of people. Recipients
were instructed to deliver the letters to the addressees on the condition that letters must
be passed to people whom the recipients knew on a first-name basis. Milgram found that
on average six steps were required for a letter to reach its target recipient, a number now
immortalized in the phrase six degrees of separation [91]. Figure 10.9 plots results of
an experimental study of the small-world problem as reported in [180]. The small-world
effect has been studied and verified for many real-world networks including
social: collaboration network of actors in feature films [7, 192], scientific publication
authorship [44, 90, 149, 150];
10.4. Small-world networks
243
information: citation network [161], Rogets Thesaurus [118], word co-occurrence [59,
73];
technological: internet [48, 72], power grid [192], train routes [167], software [151,
183];
biological: metabolic network [108], protein interactions [107], food web [104, 138],
neural network [192, 193].
frequency
15
10
10
number of intermediaries
Figure 10.9: Frequency distribution of the number of intermediaries required for letters
to reach their intended addressees. The distribution has a mean of 5.3, interpreted as the
average number of intermediaries required for a letter to reach its intended destination.
The plot is derived from data reported in Travers and Milgram [180].
Watts and Strogatz [189, 190, 192] proposed a network model that produces graphs
exhibiting the small-world effect. Let n and k be positive integers such that n k
ln n 1 (in particular, 0 < k < n/2), k being even, and consider a probability 0 < p < 1.
Starting from an undirected k-circulant graph G = (V, E) on n vertices, the WattsStrogatz model proceeds to rewire each edge with probability p. The rewiring procedure
works as follows. Let V be uniformly distributed. For each v V , let e E be an
edge having v as an endpoint. Choose another u V different from v. With probability
p, delete the edge e and add the edge vu. The rewiring must produce a simple graph
with the same order and size as G. As p 1, the graph G goes from k-circulant
to exhibiting properties of G(n, p). Small-world networks are intermediate between kcirculant and binomial random graphs (see Figure 10.10). The Watts-Strogatz model is
said to provide a procedure for interpolating between the latter two types of graphs.
The last paragraph contains an algorithm for rewiring edges of a graph. While the
algorithm is simple, in practice it potentially skips over a number of vertices to be
considered for rewiring. If G = (V, E) is a k-circulant graph on n vertices and p is the
rewiring probability, the candidate vertices to be rewired follow a geometric distribution
with parameter p. This geometric trick, essentially the same speed-up technique used by
the Batagelj-Brandes Algorithm 10.3, can be used to speed up the rewiring algorithm.
To elaborate, suppose G has vertex set V = {0, 1, . . . , n 1}. If r is chosen uniformly at
random from the interval (0, 1), the index of the vertex to be rewired can be obtained
244
(a) p = 0, k-circulant
(b) p = 0.3, small-world
(c) p = 1, random
Figure 10.10: With increasing randomness, k-circulant graphs evolve to exhibit properties of random graphs in G(n, p). Small-world networks are intermediate between
k-circulant graphs and random graphs in G(n, p).
from

ln(1 r)
1+
.
ln(1 p)
The above geometric method is incorporated into Algorithm 10.6 to generate a WattsStrogatz network in worst-case runtime O(nk +m), where n and k are as per the input of
the algorithm and m is the size of the k-circulant graph on n vertices. Note that lines 7
to 12 are where we avoid self-loops and multiple edges.
Algorithm 10.6: Watts-Strogatz network model.
Input: Positive integer n denoting the number of vertices. Positive even integer k
for the degree of each vertex, where n k ln n 1. In particular, k
should satisfy 0 < k < n/2. Rewiring probability 0 < p 1.
Output: A Watts-Strogatz network on n vertices.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
M nk
/* sum of all vertex degrees = twice number of edges */
v 1 + bln(1 r)/ ln(1 p)c
E contiguous edge list of k-circulant graph on n vertices
while v M do
u draw uniformly at random from [0, 1, . . . , n 1]
if v 1 is even then
while E[v] = u or (u, E[v]) E do
else
while E[v 2] = u or (E[v 2], u) E do
E[v 1] u
v v + 1 + bln(1 r)/ ln(1 p)c
G Kn
add edges in E to G
return G
10.4. Small-world networks
245
Characteristic path length

Watts and Strogatz [192] analyzed the structure of networks generated by Algorithm 10.6
via two quantities: the characteristic path length ` and the clustering coefficient C. The
characteristic path length quantifies the average distance between any distinct pair of
vertices in a Watts-Strogatz network. The quantity `(G) is thus said to be a global
property of G. Watts and Strogatz characterized as small-world those networks that
exhibit high clustering coefficients and low characteristic path lengths.
Let G = (V, E) be a Watts-Strogatz network as generated by Algorithm 10.6, where
the vertex set is V = {0, 1, . . . , n 1}. For each pair of vertices i, j V , let dij be the
distance from i to j. If there is no path from i to j or i = j, set dij = 0. Thus
0, if there is no path from i to j,
dij = 0, if i = j,
k, where k is the length of a shortest path from i to j.

Since G is undirected, we have dij = dji . Consequently when computing the distance
between each distinct pair of vertices, we should avoid double counting by computing dij
for i < j. Then the characteristic path length of G is defined by
1X
1
dij
`(G) =
n(n 1)/2 2 i6=j
(10.6)
X
1
=
dij
n(n 1) i6=j
which is averaged over all possible pairs of distinct vertices, i.e. the number of edges in
the complete graph Kn .
It is inefficient to compute the characteristic path length via equation (10.6) because
we would effectively sum n(n 1) distance values. As G is undirected, note that
X
X
1X
dij =
dij =
dij .
2 i6=j
i<j
i>j
The latter equation holds for the following reason. Let D = [dij ] be a matrix of distances
for G, where i is the row index, j is the column index, and dij is the distance from i to j.
The required sum of distances can be obtained by summing all entries above (or below)
the main diagonal of D. Therefore the characteristic path length can be expressed as
X
2
`(G) =
dij
n(n 1) i<j
=
X
2
dij
n(n 1) i>j
which requires summing n(n1)

distance values.
2
Let G = (V, E) be a Watts-Strogatz network with n = |V |. Set k 0 = k/2, where k
is as per Algorithm 10.6. As the rewiring probability p 0, the average path length
tends to
n
n
` 0 =
.
4k
2k
246
In the special case p = 0, we have

n(n + k 2)
.
2k(n 1)
`=
However as p 1, we have `
ln n
.
ln k
Clustering coefficient
The clustering coefficient of a simple graph G quantifies the cliquishness of vertices
in G = (V, E). This quantity is thus said to be a local property of G. Watts and
Strogatz [192] defined the clustering coefficient as follows. Suppose n = |V | > 0 and let ni
count the number of neighbors of vertex i V , a quantity that is equivalent to the degree
of i, i.e. deg(i) = ni . The complete graph Kni on the ni neighbors of i has ni (ni 1)/2
edges. The neighbor graph Ni of i is a subgraph of G, consisting of all vertices (6= i) that
are adjacent to i and preserving the adjacency relation among those vertices as found in
the supergraph G. For example, given the graph in Figure 10.11(a) the neighbor graph
of vertex 10 is shown in Figure 10.11(b). The local clustering coefficient Ci of i is the
ratio
Ni
Ci =
ni (ni 1)/2
where Ni counts the number of edges in Ni . In case i has degree deg(i) < 2, we set the
local clustering coefficient of i to be zero. Then the clustering coefficient of G is defined
by
1X
Ni
1X
Ci =
.
C(G) =
n iV
n iV ni (ni 1)/2
3
3
1
10
9
7
(a) Graph on 11 vertices.
6
7
(b) N10
Figure 10.11: The neighbor graph of a vertex.

Consider the case where we have a k-circulant graph G = (V, E) on n vertices and a
rewiring probability p = 0. That is, we do not rewire any edge of G. Each vertex of G has
degree k. Let k 0 = k/2. Then the k neighbors of each vertex in G has 3k 0 (k 0 1)/2 edges
between them, i.e. each neighbor graph Ni has size 3k 0 (k 0 1)/2. Then the clustering
coefficient of G is
3(k 0 1)
.
2(2k 0 1)
When the rewiring probability is p > 0, Barrat and Weigt [17] showed that the clustering
coefficient of any graph G0 in the Watts-Strogatz network model (see Algorithm 10.6)
10.5. Scale-free networks
247
can be approximated by
C(G0 )
3(k 0 1)
(1 p)3 .
2(2k 0 1)
Degree distribution
For a Watts-Strogatz network without rewiring, each vertex has the same degree k. It
easily follows that for each vertex v, we have the degree distribution
(
1, if i = k,
Pr[deg(v) = i] =
0, otherwise.
A rewiring probability p > 0 introduces disorder in the network and broadens the
degree distribution, while the expected degree is k. A k-circulant graph on n vertices
has nk/2 edges. With the rewiring probability p > 0, a total of pnk/2 edges would
be rewired. However note that only one endpoint of an edge is rewired, thus after the
rewiring process the degree of any vertex v is deg(v) k/2. Therefore with k > 2, a
Watts-Strogatz network has no isolated vertices.
For p > 0, Barrat and Weigt [17] showed that the degree of a vertex v can be written
as deg(v) = k/2 + ni with ni 0, where ni can be divided into two parts and as
follows. First k/2 edges are left intact after the rewiring process, the probability of
this occurring is 1 p for each edge. Second = ni edges have been rewired towards
i, each with probability 1/n. The probability distribution of is

k/2
P1 () =
(1 p) pk/2
and the probability distribution of is

pnk/2

1
pnk/2
1
1
P2 () =
n
n
where
P2 ()
(pk/2)
exp(pk/2)
!
for large n. Combine the above two factors to obtain the degree distribution
Pr[deg(v) = ] =
min{k/2, k/2}
X
i=0

k/2
(pk/2)k/2i
(1 p)i pk/2i
exp(pk/2)
i
( k/2 i)!
for k/2.
10.5
Scale-free networks
The networks covered so farGilbert G(n, p) model, Erdos-Renyi G(n, N ) model, WattsStrogatz small-world modelare static. Once a network is generated from any of these
models, the corresponding model does not specify any means for the network to evolve
over time. Barabasi and Albert [13] proposed a network model based on two ingredients:
248
1. Growth: at each time step, a new vertex is added to the network and connected
to a pre-determined number of existing vertices.
2. Preferential attachment: the newly added vertex is connected to an existing vertex
in proportion to the latters existing degree.
Preferential attachment also goes by the colloquial name of the rich-get-richer effect
due to the work of Herbert Simon [172]. In sociology, preferential attachment is known
as the Matthew effect due to the following verse from the Book of Matthew, chapter 25
verse 29, in the Bible: For to every one that hath shall be given but from him that
hath not, that also which he seemeth to have shall be taken away. Barabasi and Albert
observed that many real-world networks exhibit statistical properties of their proposed
model. One particularly significant property is that of power-law scaling, hence the
Barabasi-Albert model is also called a model of scale-free networks. Note that it is only
the degree distributions of scale-free networks that are scale-free. In their empirical study
of the World Wide Web (WWW) and other real-world networks, Barabasi and Albert
noted that the probability that a web page increases in popularity is directly proportional
to the pages current popularity. Thinking of a web page as a vertex and the degree of a
page as the number of other pages that the current page links to, the degree distribution
of the WWW follows a power law function. Power-law scaling has been confirmed for
many real-world networks:
actor collaboration network [13]
citation [56, 161, 166] and coauthorship networks [150]
human sexual contacts network [110, 134]
the Internet [48, 72, 184] and the WWW [6, 15, 36]
metabolic networks [107, 108]
telephone call graphs [3, 4]
Figure 10.12 illustrates the degree distributions of various real-world networks, plotted
on log-log scales. Corresponding distributions for various simulated Barabasi-Albert
networks are illustrated in Figure 10.13.
But how do we generate a scale-free graph as per the description in Barabasi and
Albert [13]? The original description of the Barabasi-Albert model as contained in [13]
is rather ambiguous with respect to certain details. First, the whole process is supposed
to begin with a small number of vertices. But as the degree of each of these vertices
is zero, it is unclear how the network is to grow via preferential attachment from the
initial pool of vertices. Second, Barabasi and Albert neglected to clearly specify how to
select the neighbors for the newly added vertex. The above ambiguities are resolved in
Bollobas et al. [28], wherein is given a precise statement of a random graph process that
realizes the Barabasi-Albert model. Fix a sequence of vertices v1 , v2 , . . . and consider
the case where each newly added vertex is to be connected to m = 1 vertex already in
a graph. Inductively define a random graph process (Gt1 )t0 as follows, where Gt1 is a
digraph on {vi | 1 i t}. Start with the null graph G01 or the graph G11 with one
vertex and one self-loop. Denote by degG (v) the total (in and out) degree of vertex v in
249
101
101
102
102
3
10
103
104
104
105
105
106
100
101
102
100
(a) US patent citation network.
101
102
103
(b) Google web graph.
101
102
102
103
103
104
104
105
105
106
100
101
102
103
(c) LiveJournal frienship network.
104
100
101
102
103
(d) Actor collaboration network.
Figure 10.12: Degree distributions of various real-world networks on log-log scales. The
horizontal axis represents degree and the vertical axis is the corresponding probability of
a vertex having that degree. The US patent citation network [132] is a directed graph on
3, 774, 768 vertices and 16, 518, 948 edges. It covers all citations made by patents granted
between 1975 and 1999. The Google web graph [133] is a digraph having 875, 713 vertices
and 5, 105, 039 edges. This dataset was released in 2002 by Google as part of the Google
Programming Contest. The LiveJournal friendship network [9, 133] is a directed graph on
4, 847, 571 vertices and 68, 993, 773 edges. The actor collaboration network [13], based on
the Internet Movie Database (IMDb) at http://www.imdb.com, is an undirected graph
on 383, 640 vertices and 16, 557, 920 edges. Two actors are connected to each other if
they have starred in the same movie. In all of the above degree distributions, self-loops
are not taken into account and, where a graph is directed, we only consider the in-degree
distribution.
250
101
101
102
102
103
103
104
104
105
105 0
10
101
102
103
106 0
10
104
101
(a) n = 105 vertices
103
104
105
(b) n = 106 vertices
101
101
102
102
103
103
104
104
105
105
106
106
107 0
10
102
107
10
10
10
10
(c) n = 107 vertices
10
10
100
101
102
103
104
105
106
(d) n = 2 107 vertices
Figure 10.13: Degree distributions of simulated graphs in the classic Barabasi-Albert

model. The horizontal axis represents degree; the vertical axis is the corresponding
probability of a vertex having a particular degree. Each generated graph is directed and
has minimum out-degree m = 5. The above degree distributions are only for in-degrees
and do not take into account self-loops.
251
the graph G. For t > 1 construct Gt1 from Gt1

by adding the vertex vt and a directed
1
edge from vt to vi , where i is randomly chosen with probability
Pr[i = s] =
(
degG1t1 (vs )/(2t 1), if 1 s t 1,
1/(2t 1),
if s = t.
The latter process generates a forest. For m > 1 the graph evolves as per the case m = 1;
i.e. we add m edges from vt one at a time. This process can result in self-loops and
n
for the collection of all graphs on n vertices and minimal
multiple edges. We write Gm
n
is denoted
degree m in the Barabasi-Albert model, where a random graph from Gm
n
n
Gm Gm .
Now consider the problem of translating the above procedure into pseudocode. Fix a
positive integer n > 1 for the number of vertices in the scale-free graph to be generated
via preferential attachment. Let m 1 be the number of vertices that each newly added
vertex is to be connected to; this is equivalent to the minimum degree that any new vertex
will end up possessing. At any time step, let M be the contiguous edge list of all edges
created thus far in the above random graph process. It is clear that the frequency (or
number of occurrences) of a vertex is equivalent to the vertexs degree. We can thus use
M as a pool to sample in constant time from the degree-skewed distribution. Batagelj and
Brandes [18] used the latter observation to construct an algorithm for generating scalefree networks via preferential attachment; pseudocode is presented in Algorithm 10.7.
Note that the algorithm has linear runtime O(n + m), where n is the order and m the
size of the graph generated by the algorithm.
Algorithm 10.7: Scale-free network via preferential attachment.
Input: Positive integer n > 1 and minimum degree d 1.
Output: Scale-free network on n vertices.
1
2
3
4
5
6
7
8
9
/* vertex set is V = {0, 1, . . . , n 1} */

G Kn
M list of length 2nd
for v = 0, 1, . . . , n 1 do
for i = 0, 1, . . . , d 1 do
M [2(vd + i)] v
r draw uniformly at random from {0, 1, . . . , 2(vd + i)}
M [2(vd + i) + 1] M [r]
add edge (M [2i], M [2i + 1]) to G for i = 0, 1, . . . , nd 1
return G
On the evidence of computer simulation and various real-world networks, it was

suggested [13, 14] that Pr[deg(v) = k] k with = 2.90.1. Letting n be the number
of vertices, Bollobas et al. [28] obtained Pr[deg(v) = k] asymptotically for all k n1/15
and showed as a consequence that = 3. In the process of doing so, Bollobas et al.
proved various results concerning the expected degree. Denote by #nm (k) the number of
vertices of Gnm with in-degree k (and consequently with total degree m + k). For the case
m = 1, we have the expectation
E[degGt1 (vt )] = 1 +
1
2t 1
252
and for s < t we have

E[degGt1 (vs )] =
2t
(vs )].
E[degGt1
1
2t 1
Taking the above two equations together, for 1 s n we have

E[degGn1 (vs )] =
n
Y
i=s
4ns+1 n!2 (2s 2)!

2i
=
.
2i 1
(2n)!(s 1)!2
Furthermore for 0 k n1/15 we have

E[#nm (k)]
2m(m + 1)n
(k + m)(k + m + 1)(k + m + 2)
uniformly in k.
As regards the diameter, with n as per Algorithm 10.7, computer simulation by
Barabasi, Albert, and Jeong [6, 15] and heuristic arguments by Newman et al. [154]
suggest that a graph generated by the Barabasi-Albert model has diameter approximately
ln n. As noted by Bollobas and Riordan [27], the approximation diam(Gnm ) ln n holds
for the case m = 1, but for m 2 they showed that as n then diam(Gnm )
ln / ln ln n.
10.6
Problems
Where should I start? Start from the statement of the problem. What can I do? Visualize
the problem as a whole as clearly and as vividly as you can.
G. Polya, from page 33 of [158]
10.1. Algorithm 10.8 presents a procedure to construct a random graph that is simple
and undirected; the procedure is adapted from pages 47 of Lau [129]. Analyze the
time complexity of Algorithm 10.8. Compare and contrast your results with that
for Algorithm 10.5.
10.2. Modify Algorithm 10.8 to generate the following random graphs.
(a) Simple weighted, undirected graph.
(b) Simple digraph.
(c) Simple weighted digraph.
10.3. Algorithm 10.1 can be considered as a template for generating random graphs in
G(n, p). The procedure does not specify how to generate all the 2-combinations of
a set of n > 1 objects. Here we discuss how to construct all such 2-combinations
and derive a quadratic time algorithm for generating random graphs in G(n, p).
(a) Consider a vertex set V = {0, 1, . . . , n 1} with at least two elements and let
E be the set of all 2-combinations of V , where each 2-combination is written
ij. Show that ij E if and only if i < j.
10.6. Problems
Algorithm 10.8: Random simple undirected graph.

Input: Positive integers n and m specifying the order and size, respectively, of
the output graph.
Output: A random simple undirected graph with n vertices and m edges. If m
exceeds the size of Kn , then Kn is returned.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
if n = 1 then
return K1
max n(n 1)/2
if m > max then
return Kn
G null graph
A n n adjacency matrix with entries aij
aij False for 0 i, j < n
i0
while i < m do
u draw uniformly at random from {0, 1, . . . , n 1}
v draw uniformly at random from {0, 1, . . . , n 1}
if u = v then
if u > v then
swap values of u and v
if auv = False then
add edge uv to G
auv True
ii+1
return G
Algorithm 10.9: Quadratic generation of a random graph in G(n, p).

Output: A random graph from G(n, p).
1
2
3
4
5
6
7
8
G Kn
V {0, 1, . . . , n 1}
for i 0, 1, . . . , n 2 do
for j i + 1, i + 2, . . . , n 1 do
if r < p then
add edge ij to G
return G
253
254
Algorithm 10.10: Briggs algorithm for random graph in G(n, N ).

Input: Positive integers n and N such that 1 N n2 .

n
1 max
2
2 if n = 1 or N = max then
3
return Kn
4 G Kn
5 u 0
6 v 1
7 t 0
/* number of candidates processed so far */
8 k 0
/* number of edges selected so far */
9 while True do
10
r draw uniformly at random from {0, 1, . . . , max t}
11
if r < N k then
12
add edge uv to G
13
k k+1
14
if k = N then
15
return G
16
tt+1
17
v v+1
18
if v = n then
19
uu+1
20
v u+1
10.6. Problems
255
(b) From the previous exercise, we know that if 0 i < n 1 then there are
n (i + 1) pairs jk where either i = j or i = k. Show that
n2
X
n2 n
(n i 1) =
2
i=0
and conclude that Algorithm 10.9 has worst-case runtime O((n2 n)/2).
10.4. Modify the Batagelj-Brandes Algorithm 10.3 to generate the following types of
graphs.
(a) Directed simple graphs.
(b) Directed acyclic graphs.
(c) Bipartite graphs.
10.5. Repeat the previous problem for Algorithm 10.5.
10.6. In 2006, Keith M. Briggs provided [34] an algorithm that generates a random
graph in G(n, N ), inspired by Knuths Algorithm S (Selection sampling technique)
as found on page 142 of Knuth [119]. Pseudocode of Briggs procedure is presented
in Algorithm 10.10. Provide runtime analysis of Algorithm 10.10 and compare your
results with those presented in section 10.3. Under which conditions would Briggs
algorithm be more efficient than Algorithm 10.5?
10.7. Briggs Algorithm 10.10 follows the general template of an algorithm that samples
without replacement n items from a pool of N candidates. Here 0 < n N and
the size N of the candidate pool is known in advance. However there are situations
where the value of N is not known beforehand, and we wish to sample without
replacement n items from the candidate pool. What we know is that the candidate
pool has enough members to allow us to select n items. Vitters algorithm R [185],
called reservoir sampling, is suitable for the situation and runs in O(n(1+ln(N/n)))
expected time. Describe and provide pseudocode of Vitters algorithm, prove its
correctness, and provide runtime analysis.
10.8. Repeat Example 10.1 but using each of Algorithms 10.1 and 10.5.
10.9. Diego Garlaschelli introduced [83] in 2009 a weighted version of the G(n, p) model,
called the weighted random graph model. Denote by GW (n, p) the weighted random
graph model. Provide a description and pseudocode of a procedure to generate a
graph in GW (n, p) and analyze the runtime complexity of the algorithm. Describe
various statistical physics properties of GW (n, p).
10.10. Latora and Marchiori [128] extended the Watts-Strogatz model to take into account weighted edges. A crucial idea in the Latora-Marchiori model is the concept
of network efficiency. Describe the Latora-Marchiori model and provide pseudocode
of an algorithm to construct Latora-Marchiori networks. Explain the concepts
of local and global efficiencies and how these relate to clustering coefficient and
characteristic path length. Compare and contrast the Watts-Strogatz and LatoraMarchiori models.
256
10.11. The following model for growing graphs is known as the CHKNS model [43],1
named for its original proponents. Start with the trivial graph G at time step
t = 1. For each subsequent time step t > 1, add a new vertex to G. Furthermore
choose two vertices uniformly at random and with probability join them by an
undirected edge. The newly added edge does not necessarily have the newly added
vertex as an endpoint. Denote by dk (t) the expected number of vertices with degree
k at time t. Assuming that no self-loops are allowed, show that
d0 (t + 1) = d0 (t) + 1 2
d0 (t)
t
and
dk1 (t)
dk (t)
2
.
t
t
As t , show that the probability that a vertex be chosen twice decreases as
t2 . If v is a vertex chosen uniformly at random, show that
dk (t + 1) = dk (t) + 2
Pr[deg(v) = k] =
(2)k
(1 + 2)k+1
and conclude that the CHKNS model has an exponential degree distribution. The
size of a component counts the number of vertices in the component itself. Let
Nk (t) be the expected number of components of size k at time t. Show that
N1 (t + 1) = N1 (t) + 1 2
N1 (t)
t
and for k > 1 show that

k1
X
iNi (t) (k i)Nki (t)
Nk (t + 1) = Nk (t) +
t
t
i=1
kNk (t)
.
t
10.12. Algorithm 10.7 can easily be modified to generate other types of scale-free networks. Based upon the latter algorithm, Batagelj and Brandes [18] presented
a procedure for generating bipartite scale-free networks; see Algorithm 10.11 for
pseudocode. Analyze the runtime efficiency of Algorithm 10.11. Fix positive integer values for n and d, say n = 10, 000 and d = 4. Use Algorithm 10.11 to generate
a bipartite graph with your chosen values for n and d. Plot the degree distribution
of the resulting graph using a log-log scale and confirm that the generated graph
is scale-free.
10.13. Find the degree and distance distributions, average path lengths, and clustering
coefficients of the following network datasets:
(a) actor collaboration [13]
(b) coauthorship of condensed matter preprints [150]
(c) Google web graph [133]
(d) LiveJournal friendship [9, 133]
1
Or the chickens model, depending on how you pronounce CHKNS.
10.6. Problems
257
Algorithm 10.11: Bipartite scale-free network via preferential attachment.

Input: Positive integer n > 1 and minimum degree d 1.
Output: Bipartite scale-free multigraph. Each partition has n vertices and each
vertex has minimum degree d.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
G K2n
/* vertex set is {0, 1, . . . , 2n 1} */
M1 list of length 2nd
M2 list of length 2nd
for v = 0, 1, . . . , n 1 do
for i = 0, 1, . . . , d 1 do
M1 [2(vd + i)] v
M2 [2(vd + i)] n + v
if r is even then
M1 [2(vd + i) + 1] M2 [r]
else
M1 [2(vd + i) + 1] M1 [r]
if r is even then
M2 [2(vd + i) + 1] M1 [r]
else
M2 [2(vd + i) + 1] M2 [r]
add edges (M1 [2i], M1 [2i + 1]) and (M2 [2i], M2 [2i + 1]) to G for i = 0, 1, . . . , nd 1
return G
258

(e) neural network of the C. elegans [192, 193]
(f) US patent citation [132]
(g) Western States Power Grid of the US [192]
(h) Zachary karate club [201]
Chapter 11
Graph Problems and Their LP
Formulations
This document is meant as an explanation of several graph theoretical functions defined
in Sages Graph Library (http://www.sagemath.org/), which use Linear Programming
to solve optimization of existence problems.
11.1
Maximum average degree
The average degree of a graph G is defined as ad(G) = 2|E(G)|

. The maximum average
|V (G)|
degree of G is meant to represent its densest part, and is formally defined as :
mad(G) = max ad(H)
HG
Even though such a formulation does not show it, this quantity can be computed in
polynomial time through Linear Programming. Indeed, we can think of this as a simple
flow problem defined on a bipartite graph. Let D be a directed graph whose vertex set
we first define as the disjoint union of E(G) and V (G). We add in D an edge between
(e, v) E(G) V (G) if and only if v is one of es endpoints. Each edge will then have a
flow of 2 (through the addition in D of a source and the necessary edges) to distribute
among its two endpoints. We then write in our linear program the constraint that each
vertex can absorb a flow of at most z (add to D the necessary sink and the edges with
capacity z).
Clearly, if H G is the densest subgraph in G, its |E(H)| edges will send a flow
. An
of 2|E(H)| to their |V (H)| vertices, such a flow being feasible only if z 2|E(H)|
|V (H)|
elementary application of the max-flow/min-cut theorem, or of Halls bipartite matching
theorem shows that such a value for z is also sufficient. This LP can thus let us compute
the Maximum Average Degree of the graph.
Sage method : Graph.maximum_average_degree()
LP Formulation :
Minimize : z
Such that :
259
260
Chapter 11. Graph Problems and Their LP Formulations

a vertex can absorb at most z
v V (G),
eE(G)
ev
xe,v z
each edge sends a flow of 2

e = uv E(G), xe,u + xe,u = 2
xe,v real positive variable
Here is the corresponding Sage code:

sage : g = graphs . PetersenGraph ()
sage : p = M i x e d I n t e g e rL i n e a r P r o g r a m ( maximization = False )
sage : x = p . new_variable ( dim = 2 )
sage : p . set_objective ( p [ z ])
sage : for v in g :
...
p . add_constraint ( sum ([ x [ u ][ v ] for u in g . neighbors ( v ) ]) <= p [ z ] )
sage : for u , v in g . edges ( labels = False ):
...
p . add_constraint ( x [ u ][ v ] + x [ v ][ u ] == 2 )
sage : p . solve ()
3.0
REMARK : In many if not all the other LP formulations, this Linear Program
is used as a constraint. In those problems, we are always at some point looking for a
subgraph H of G such that H does not contain any cycle. The edges of G are in this
case variables, whose value can be equal to 0 or 1 depending on whether they belong
to such a graph H. Based on the observation that the Maximum Average Degree of a
tree on n vertices is exactly its average degree (= 2 2/n < 1), and that any cycles
in a graph ensures its average degree is larger than 2, we can then set the constraint
2
. This is a handy way to write in LP the constraint that the set of
that z 2 |V (G)|
edges belonging to H is acyclic. For this to work, though, we need to ensure that the
variables corresponding to our edges are binary variables.
11.2
Traveling Salesman Problem
Given a graph G whose edges are weighted by a function w : E(G) R, a solution to

the T SP is a Hamiltonian (spanning) cycle whose weight (the sum of the weight of its
edges) is minimal. It is easy to define both the objective and the constraint that each
vertex must have exactly two neighbors, but this could produce solutions such that the
set of edges define the disjoint union of several cycles. One way to formulate this linear
program is hence to add the constraint that, given an arbitrary vertex v, the set S of
edges in the solution must contain no cycle in G v, which amounts to checking that
the set of edges in S no adjacent to v is of maximal average degree strictly less than 2,
using the remark from section ??.
We will then, in this case, define variables representing the edges included in the
solution, along with variables representing the weight that each of these edges will send
to their endpoints.
LP Formulation :
11.2. Traveling Salesman Problem
261
Minimize
w(e)be
eE(G)
Such that :
Each vertex is of degree 2

v V (G),
be = 2
eE(G)
ev
No cycle disjoint from a special vertex v

* Each edge sends a flow of 2 if it is taken
e = uv E(G v ), xe,u + xe,v = 2be

* Vertices receive strictly less than 2
v V (G v ),
eE(G)
ev
xe,v 2
2
|V (G)|
Variables
xe,v real positive variable (flow sent by the edge)

be binary (is the edge in the solution ?)
Sage method : Graph.traveling_salesman_problem()
Here is the corresponding Sage corresponding to a simpler case looking for an
Hamiltonian cycle in a graph:
sage : g = graphs . GridGraph ([4 ,4])
sage : p = M i x e d I n t e g e rL i n e a r P r o g r a m ( maximization = False )
sage : f = p . new_variable ()
sage : r = p . new_variable ()
sage : eps = 1/(2* Integer ( g . order ()))
sage : x = g . vertex_iterator (). next ()
sage : # reorders the edge as they can appear in the two different ways
sage : R = lambda x , y : (x , y ) if x < y else (y , x )
sage : # All the vertices have degree 2
sage : for v in g :
...
p . add_constraint ( sum ([ f [ R (u , v )] for u in g . neighbors ( v )]) == 2)
sage : # r is greater than f
sage : for u , v in g . edges ( labels = None ):
...
p . add_constraint ( r [( u , v )] + r [( v , u )] - f [ R (u , v )] >= 0)
sage : # no cycle which does not contain x
sage : for v in g :
...
if v != x :
...
p . add_constraint ( sum ([ r [( u , v )] for u in g . neighbors ( v )]) <= 1 - eps )
sage : p . set_objective ( None )
sage : p . set_binary ( f )
sage : p . solve ()
0.0
# optional - GLPK , CBC , CPLEX
262
sage : # We can now build the solution

sage : # found as a graph
sage : f =
sage : tsp
sage : for
...
...
p . get_values ( f )
= Graph ()
e in g . edges ( labels = False ):
if f [ R ( e [0] , e [1])] == 1:
tsp . add_edge ( e )
#
#
#
#
#
sage : tsp . is_regular ( k =2) and tsp . is_connected ()

True
sage : tsp . order () == g . order ()
True
11.3
optional
optional
optional
optional
optional
GLPK , CBC , CPLEX

GLPK , CBC , CPLEX
GLPK , CBC , CPLEX
GLPK , CBC , CPLEX
GLPK , CBC , CPLEX

Edge-disjoint spanning trees
This problem is polynomial by a result from Edmonds. Obviously, nothing ensures the
following formulation is a polynomial algorithm as it contains many integer variables,
but it is still a short practical way to solve it.
This problem amounts to finding, given a graph G and an integer k, edge-disjoint
spanning trees T1 , . . . , Tk which are subgraphs of G. In this case, we will chose to define
a spanning tree as an acyclic set of |V (G)| 1 edges.
Sage method : Graph.edge_disjoint_spanning_trees()
LP Formulation :
Maximize : nothing
Such that :
An edge belongs to at most one set

e E(G),
Each set contains |V (G)| 1 edges
i [1, . . . , k],
i[1,...,k]
eE(G)
be,k 1
be,k = |V (G)| 1
No cycles
* In each set, each edge sends a flow of 2 if it is taken
i [1, . . . , k], e = uv E(G), xe,k,u + xe,k,u = 2be,k

i [1, . . . , k], v V (G),
eE(G)
ev
xe,k,v 2
2
|V (G)|
Variables
be,k binary (is edge e in set k ?)

xe,k,u positive real (flow sent by edge e to vertex u in set k)
11.4. Steiner tree
263

sage : g = graphs . RandomGNP (40 ,.6)
sage : p = M i x e d I n t e g e rL i n e a r P r o g r a m ()
sage : colors = range (2)
sage : # Sort an edge
sage : S = lambda (x , y ) : (x , y ) if x < y else (y , x )
sage : edges = p . new_variable ( dim = 2)
sage : r_edges = p . new_variable ( dim = 2)
sage : # An edge belongs to at most one tree
sage : for e in g . edges ( labels = False ):
...
p . add_constraint ( sum ([ edges [ j ][ S ( e )] for j in colors ]) , max = 1)
sage : for j in colors :
...
# each color class has g . order () -1 edges
...
p . add_constraint (
...
sum ([ edges [ j ][ S ( e )] for e in g . edges ( labels = None )])
...
>= g . order () -1)
...
# Each vertex is in the tree
...
for v in g . vertices ():
...
...
sum ([ edges [ j ][ S ( e )] for e in g . edges_incident (v , labels = None )])
...
>= 1)
...
# r_edges is larger than edges
...
for u , v in g . edges ( labels = None ):
...
...
r_edges [ j ][( u , v )] + r_edges [ j ][( v , u )]
...
== edges [ j ][ S (( u , v ))] )
sage : # no cycles
sage : epsilon = (3* Integer ( g . order ()))**( -1)
sage : for j in colors :
...
for v in g :
...
...
sum ([ r_edges [ j ][( u , v )] for u in g . neighbors ( v )])
...
<= 1 - epsilon )
sage : p . set_binary ( edges )
sage : p . solve ()
0.0

sage : # found as a list of trees
sage : edges = p . get_values ( edges )
sage : trees = [ Graph () for c in colors ]

sage : for e in g . edges ( labels = False ):

...
for c in colors :
...
if round ( edges [ c ][ S ( e )]) == 1:
...
trees [ c ]. add_edge ( e )
#
#
#
#
sage : all ([ trees [ j ]. is_tree () for j in colors ])

True
11.4
optional
optional
optional
optional
GLPK , CBC , CPLEX

GLPK , CBC , CPLEX
GLPK , CBC , CPLEX
GLPK , CBC , CPLEX
Steiner tree
See Trietsch [181] for a relationship between Steiner trees and Eulers problem of polygon
division. Finding a spanning tree in a Graph G can be done in linear time, whereas
computing a Steiner Tree is NP-hard. The goal is in this case, given a graph, a weight
function w : E(G) R and a set S of vertices, to find the tree of minimum cost
connecting them all together. Equivalently, we will be looking for an acyclic subgraph
Hof G containing |V (H)| vertices and |E(H)| = |V (H)| 1 edges, which contains each
vertex from S
264
LP Formulation :
Minimize :
w(e)be
eE(G)
Such that :
Each vertex from S is in the tree

v S,
eE(G)
ev
be 1
c is equal to 1 when a vertex v is in the tree

v V (G), e E(G), e v, be cv
The tree contains |V (H)| vertices and |E(H)| = |V (H)| 1 edges
X
X
cv
be = 1
vG
eE(G)
No Cycles
e = uv E(G), xe,u + xe,u = 2be,k

v V (G),
eE(G)
ev
xe,v 2
2
|V (G)|
Variables :
be binary (is e in the tree ?)

cv binary (does the tree contain v ?)
xe,v real positive variable (flow sent by the edge)
Sage method : Graph.steiner_tree()
sage : vertices = [(0 ,2) ,(5 ,3)]
sage : from sage . numerical . mip import M i x e d I n t e ge r L i n e a r P r o g r a m
sage : p = M i x e d I n t e g er L i n e a r P r o g r a m ( maximization = False )
sage : # Reorder an edge
sage : R = lambda (x , y ) : (x , y ) if x < y else (y , x )
sage :
sage :
sage :
sage :
# edges used in the Steiner Tree

edges = p . new_variable ()
# relaxed edges to test for acyclicity
r_edges = p . new_variable ()
11.5. Linear arboricity
265
sage : # Whether a vertex is in the Steiner Tree

sage : vertex = p . new_variable ()
sage : # Which vertices are in the tree ?
sage : for v in g :
...
for e in g . edges_incident (v , labels = False ):
...
p . add_constraint ( vertex [ v ] - edges [ R ( e )] , min = 0)
sage : # We must have the given vertices in our tree
sage : for v in vertices :
...
...
sum ([ edges [ R ( e )] for e in g . edges_incident (v , labels = False )]
...
== 1)
sage : # The number of edges is equal to the number of vertices in our tree minus 1
sage : p . add_constraint (
...
sum ([ vertex [ v ] for v in g ])
...
- sum ([ edges [ R ( e )] for e in g . edges ( labels = None )])
...
== 1)
sage : # There are no cycles in our graph
sage : for u , v in g . edges ( labels = False ):
...
...
r_edges [( u , v )]+ r_edges [( v , u )] - edges [ R (( u , v ))]
...
<= 0 )
sage : eps = 1/(5* Integer ( g . order ()))
sage : for v in g :
...
p . add_constraint ( sum ([ r_edges [( u , v )] for u in g . neighbors ( v )]) , max = 1 - eps )
sage : p . set_objective ( sum ([ edges [ R ( e )] for e in g . edges ( labels = False )]))
sage : p . set_binary ( edges )
sage : p . solve ()
6.0
sage : # found as a tree
sage :
sage :
sage :
...
...
sage :
True
sage :
True
11.5
edges = p . get_values ( edges )

st = Graph ()
st . add_edges (
[ e for e in g . edges ( labels = False )
if edges [ R ( e )] == 1])
st . is_tree ()

all ([ v in st for v in vertices ])

Linear arboricity
The linear arboricity of a graph G is the least number k such that the edges of G can
be partitioned into k classes, each of them being a forest of paths (the disjoints union
of paths trees of maximal degree 2). The corresponding LP is very similar to the one
giving edge-disjoint spanning trees
LP Formulation :
Maximize : nothing
Such that :
An edge belongs to exactly one set

e E(G),
i[1,...,k]
be,k = 1
266

Each class has maximal degree 2
v V (G), i [1, . . . , k],
eE(G)
ev
be,k 2
No cycles
* In each set, each edge sends a flow of 2 if it is taken
i [1, . . . , k], e = uv E(G), xe,k,u + xe,k,v = 2be,k

i [1, . . . , k], v V (G),
eE(G)
ev
xe,k,v 2
2
|V (G)|
Variables
be,k binary (is edge e in set k ?)

xe,k,u positive real (flow sent by edge e to vertex u in set k)
Sage method : sage.graphs.graph_coloring.linear_arboricity()
Here is the corresponding Sage code :
sage : k = 2
sage : # c is a boolean value such that c [ i ][( u , v )] = 1
sage : # if and only if (u , v ) is colored with i
sage : c = p . new_variable ( dim =2)
sage : # relaxed value
sage : r = p . new_variable ( dim =2)
sage : E = lambda x , y : (x , y ) if x < y else (y , x )
sage : MAD = 1 -1/( Integer ( g . order ())*2)
sage : # Partition of the edges
...
p . add_constraint ( sum ([ c [ i ][ E (u , v )] for i in range ( k )]) , max =1 , min =1)
sage : for i in range ( k ):
...
# r greater than c
...
...
p . add_constraint ( r [ i ][( u , v )] + r [ i ][( v , u )] - c [ i ][ E (u , v )] , max =0 , min =0)
...
# Maximum degree 2
...
for u in g . vertices ():
...
p . add_constraint ( sum ([ c [ i ][ E (u , v )] for v in g . neighbors ( u )]) , max = 2)
...
# no cycles
...
p . add_constraint ( sum ([ r [ i ][( u , v )] for v in g . neighbors ( u )]) , max = MAD )
sage : p . set_binary ( c )
sage : c = p . get_values ( c )
sage :
sage :
sage :
sage :
gg = g . copy ()
gg . delete_edges ( g . edges ())
answer = [ gg . copy () for i in range ( k )]
add = lambda (u , v ) , i : answer [ i ]. add_edge (( u , v ))
sage : for i in range ( k ):

...
...
if c [ i ][ E (u , v )] == 1:
...
add (( u , v ) , i )
11.6. H-minor
11.6
267
H-minor
For more information on minor theory, please see

http://en.wikipedia.org/wiki/Minor_%28graph_theory%29
It is a wonderful subject, and I do not want to begin talking about it when I know I
couldnt freely fill pages with remarks :-)
For our purposes, we will just say that finding a minor H in a graph G, consists in :
1. Associating to each vertex h H a set Sh of representants in H, different vertices
h having disjoints representative sets
2. Ensuring that each of these sets is connected (can be contracted)
3. If there is an edge between h1 and h2 in H, there must be an edge between the
corresponding representative sets
Here is how we will address these constraints :
1. Easy
2. For any h, we can find a spanning tree in Sh (an acyclic set of |Sh | 1 edges)
3. This one is very costly.
To each directed edge g1 g2 (I consider g1 g2 and g2 g1 as different) and every edge
h1 h2 is associated a binary variable which can be equal to one only if g1 represents
h1 and g2 represents g2 . We then sum all these variables to be sure there is at least
one edge from one set to the other.
268
LP Formulation :
Maximize : nothing
Such that :
A vertex g V (G) can represent at most one vertex h V (H)

X
g V (G),
rsh,g 1
hV (H)
An edge e can only belong to the tree of h if both its endpoints represent h
e = g1 g2 E(G), te,h rsh,g1 and te,h rsh,g2
In each representative set, the number of vertices is one more than the number
of edges in the corresponding tree
X
X
h,
rsh,g
te,h = 1
gV (G)
eE(G)
No cycles in the union of the spanning trees

e = uv E(G), xe,u + xe,v = 2
te,h
hV (H)
v V (G),
eE(G)
ev
xe,k,v 2
2
|V (G)|
arc(g1 ,g2 ),(h1 ,h2 ) can only be equal to 1 if g1 g2 is leaving the representative set
of h1 to enter the one of h2 . (note that this constraints has to be written both
for g1 , g2 , and then for g2 , g1 )
g1 , g2 V (G), g1 6= g2 , h1 h2 E(H)
arc(g1 ,g2 ),(h1 ,h2 ) rsh1 ,g1 and arc(g1 ,g2 ),(h1 ,h2 ) rsh2 ,g2
We have the necessary edges between the representative sets
h1 h2 E(H)
g1 ,g2 V (G),g1 6=g2
arc(g1 ,g2 ),(h1 ,h2 ) 1
Variables
rsh,g binary (does g represent h ? rs = representative set)

te,h binary (does e belong to the spanning tree of the set representing h ?)
xe,v real positive (flow sent from edge e to vertex v)
11.6. H-minor
269
arc(g1 ,g2 ),(h1 ,h2 ) binary (is edge g1 g2 leaving the representative set of h1 to enter
the one of h2 ?)
sage : g = graphs . PetersenGraph ()
sage : H = graphs . CompleteGraph (4)
sage : # sorts an edge
sage : S = lambda (x , y ) : (x , y ) if x < y else (y , x )
sage :
sage :
sage :
sage :
# rs = Representative set of a vertex

# for h in H , v in G is such that rs [ h ][ v ] == 1 if and only if v
# is a representant of h in g
rs = p . new_variable ( dim =2)
sage : for v in g :
...
p . add_constraint ( sum ([ rs [ h ][ v ] for h in H ]) , max = 1)
sage : # We ensure that the set of representatives of a
sage : # vertex h contains a tree , and thus is connected
sage : # edges represents the edges of the tree
sage : edges = p . new_variable ( dim = 2)
sage : # there can be a edge for h between two vertices
sage : # only if those vertices represent h
...
for h in H :
...
p . add_constraint ( edges [ h ][ S (( u , v ))] - rs [ h ][ u ] , max = 0 )
...
p . add_constraint ( edges [ h ][ S (( u , v ))] - rs [ h ][ v ] , max = 0 )
sage : # The number of edges of the tree in h is exactly the cardinal
sage : # of its representative set minus 1
sage : for h in H :
...
...
sum ([ edges [ h ][ S ( e )] for e in g . edges ( labels = None )])
...
- sum ([ rs [ h ][ v ] for v in g ])
...
==1 )
sage : # a tree has no cycle
sage : epsilon = 1/(5* Integer ( g . order ()))
sage : r_edges = p . new_variable ( dim =2)
sage : for h in H :
...
...
...
r_edges [ h ][( u , v )] + r_edges [ h ][( v , u )] >= edges [ h ][ S (( u , v ))])
...
for v in g :
...
...
sum ([ r_edges [ h ][( u , v )] for u in g . neighbors ( v )]) <= 1 - epsilon )
sage : # Once the representative sets are described , we must ensure
sage : # there are arcs corresponding to those of H between them
sage : h_edges = p . new_variable ( dim =2)
sage : for h1 , h2 in H . edges ( labels = None ):
...
for v1 , v2 in g . edges ( labels = None ):
...
p . add_constraint ( h_edges [( h1 , h2 )][ S (( v1 , v2 ))]
...
...
...
sage :
sage :
sage :
sage :
0.0
p . set_binary ( rs )
p . set_binary ( edges )
p . set_objective ( None )
p . solve ()
sage : # We can now build the solution found as a

sage : # dictionary associating to each vertex of H
rs [ h2 ][ v2 ] ,
rs [ h1 ][ v1 ] ,
rs [ h1 ][ v2 ] ,
rs [ h2 ][ v1 ] ,
max
max
max
max
=
=
=
=
0)
0)
0)
0)
270
sage : # the corresponding set of vertices in G

sage : rs = p . get_values ( rs )
sage : from sage . sets . set import Set
sage : rs_dict = {}
sage : for h in H :
...
rs_dict [ h ] = [ v for v in g if rs [ h ][ v ]==1]
Appendix A
Asymptotic Growth
Name
theta
Standard notation
f (n) = (g(n))
big oh
f (n) = O(g(n))
omega
f (n) = (g(n))
little oh
f (n) = o(g(n))
little omega
f (n) = (g(n))
f (n) = (g(n))
tilde
Intuitive notation Meaning

f (n) (g(n))
f (n) c g(n)
f (n) O(g(n))
f (n) c g(n)
f (n) o(g(n))
f (n) g(n)
f (n) (g(n))
f (n) (g(n))
f (n) (g(n))
f (n) c g(n)
f (n) g(n)
f (n) log(1) g(n)
Table A.1: Meaning of asymptotic notations.
Class
lim f (n)/g(n) =
Equivalent definition
f (n) = (g(n))
a constant
f (n) = O(g(n)) and f (n) = (g(n))
f (n) = o(g(n))
zero
f (n) = (g(n))
f (n) = O(g(n)) but f (n) 6= (g(n))
f (n) 6= O(g(n)) but f (n) = (g(n))
Table A.2: Asymptotic behavior in the limit of large n.
271
Appendix B
GNU Free Documentation License
Version 1.3, 3 November 2008
Copyright 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc.
http://www.fsf.org
Everyone is permitted to copy and distribute verbatim copies of this license document,
but changing it is not allowed.
Preamble
The purpose of this License is to make a manual, textbook, or other functional
and useful document free in the sense of freedom: to assure everyone the effective
freedom to copy and redistribute it, with or without modifying it, either commercially
or noncommercially. Secondarily, this License preserves for the author and publisher a
way to get credit for their work, while not being considered responsible for modifications
made by others.
This License is a kind of copyleft, which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General
Public License, which is a copyleft license designed for free software.
We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals
providing the same freedoms that the software does. But this License is not limited to
software manuals; it can be used for any textual work, regardless of subject matter or
whether it is published as a printed book. We recommend this License principally for
works whose purpose is instruction or reference.
1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that contains a
notice placed by the copyright holder saying it can be distributed under the terms of this
License. Such a notice grants a world-wide, royalty-free license, unlimited in duration,
to use that work under the conditions stated herein. The Document, below, refers
to any such manual or work. Any member of the public is a licensee, and is addressed
as you. You accept the license if you copy, modify or distribute the work in a way
requiring permission under copyright law.
272
273
A Modified Version of the Document means any work containing the Document
or a portion of it, either copied verbatim, or with modifications and/or translated into
another language.
A Secondary Section is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the
Document to the Documents overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part
a textbook of mathematics, a Secondary Section may not explain any mathematics.) The
relationship could be a matter of historical connection with the subject or with related
matters, or of legal, commercial, philosophical, ethical or political position regarding
them.
The Invariant Sections are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is
released under this License. If a section does not fit the above definition of Secondary
then it is not allowed to be designated as Invariant. The Document may contain zero
Invariant Sections. If the Document does not identify any Invariant Sections then there
are none.
The Cover Texts are certain short passages of text that are listed, as Front-Cover
Texts or Back-Cover Texts, in the notice that says that the Document is released under
this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may
be at most 25 words.
A Transparent copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable
for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing
editor, and that is suitable for input to text formatters or for automatic translation to
a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to
thwart or discourage subsequent modification by readers is not Transparent. An image
format is not Transparent if used for any substantial amount of text. A copy that is not
Transparent is called Opaque.
Examples of suitable formats for Transparent copies include plain ASCII without
markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly
available DTD, and standard-conforming simple HTML, PostScript or PDF designed
for human modification. Examples of transparent image formats include PNG, XCF
and JPG. Opaque formats include proprietary formats that can be read and edited only
by proprietary word processors, SGML or XML for which the DTD and/or processing
tools are not generally available, and the machine-generated HTML, PostScript or PDF
produced by some word processors for output purposes only.
The Title Page means, for a printed book, the title page itself, plus such following
pages as are needed to hold, legibly, the material this License requires to appear in the
title page. For works in formats which do not have any title page as such, Title Page
means the text near the most prominent appearance of the works title, preceding the
beginning of the body of the text.
The publisher means any person or entity that distributes copies of the Document
to the public.
A section Entitled XYZ means a named subunit of the Document whose title
either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ
274
Appendix B. GNU Free Documentation License
in another language. (Here XYZ stands for a specific section name mentioned below,
such as Acknowledgements, Dedications, Endorsements, or History.)
To Preserve the Title of such a section when you modify the Document means that
it remains a section Entitled XYZ according to this definition.
The Document may include Warranty Disclaimers next to the notice which states
that this License applies to the Document. These Warranty Disclaimers are considered
to be included by reference in this License, but only as regards disclaiming warranties:
any other implication that these Warranty Disclaimers may have is void and has no effect
on the meaning of this License.
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either commercially
or noncommercially, provided that this License, the copyright notices, and the license
notice saying this License applies to the Document are reproduced in all copies, and
that you add no other conditions whatsoever to those of this License. You may not use
technical measures to obstruct or control the reading or further copying of the copies
you make or distribute. However, you may accept compensation in exchange for copies.
If you distribute a large enough number of copies you must also follow the conditions in
section 3.
You may also lend copies, under the same conditions stated above, and you may
publicly display copies.
3. COPYING IN QUANTITY
If you publish printed copies (or copies in media that commonly have printed covers)
of the Document, numbering more than 100, and the Documents license notice requires
Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all
these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the
back cover. Both covers must also clearly and legibly identify you as the publisher of
these copies. The front cover must present the full title with all words of the title equally
prominent and visible. You may add other material on the covers in addition. Copying
with changes limited to the covers, as long as they preserve the title of the Document
and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put
the first ones listed (as many as fit reasonably) on the actual cover, and continue the
rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100,
you must either include a machine-readable Transparent copy along with each Opaque
copy, or state in or with each Opaque copy a computer-network location from which
the general network-using public has access to download using public-standard network
protocols a complete Transparent copy of the Document, free of added material. If
you use the latter option, you must take reasonably prudent steps, when you begin
distribution of Opaque copies in quantity, to ensure that this Transparent copy will
remain thus accessible at the stated location until at least one year after the last time
you distribute an Opaque copy (directly or through your agents or retailers) of that
edition to the public.
275
It is requested, but not required, that you contact the authors of the Document well
before redistributing any large number of copies, to give them a chance to provide you
with an updated version of the Document.
4. MODIFICATIONS
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under
precisely this License, with the Modified Version filling the role of the Document, thus
licensing distribution and modification of the Modified Version to whoever possesses a
copy of it. In addition, you must do these things in the Modified Version:
A. Use in the Title Page (and on the covers, if any) a title distinct from that of the
Document, and from those of previous versions (which should, if there were any,
be listed in the History section of the Document). You may use the same title as
a previous version if the original publisher of that version gives permission.
B. List on the Title Page, as authors, one or more persons or entities responsible for
authorship of the modifications in the Modified Version, together with at least five
of the principal authors of the Document (all of its principal authors, if it has fewer
than five), unless they release you from this requirement.
C. State on the Title page the name of the publisher of the Modified Version, as the
publisher.
D. Preserve all the copyright notices of the Document.
E. Add an appropriate copyright notice for your modifications adjacent to the other
copyright notices.
F. Include, immediately after the copyright notices, a license notice giving the public
permission to use the Modified Version under the terms of this License, in the form
shown in the Addendum below.
G. Preserve in that license notice the full lists of Invariant Sections and required Cover
Texts given in the Documents license notice.
H. Include an unaltered copy of this License.
I. Preserve the section Entitled History, Preserve its Title, and add to it an item
stating at least the title, year, new authors, and publisher of the Modified Version as
given on the Title Page. If there is no section Entitled History in the Document,
create one stating the title, year, authors, and publisher of the Document as given
on its Title Page, then add an item describing the Modified Version as stated in
the previous sentence.
J. Preserve the network location, if any, given in the Document for public access to
a Transparent copy of the Document, and likewise the network locations given in
the Document for previous versions it was based on. These may be placed in the
History section. You may omit a network location for a work that was published
at least four years before the Document itself, or if the original publisher of the
version it refers to gives permission.
276
K. For any section Entitled Acknowledgements or Dedications, Preserve the Title

of the section, and preserve in the section all the substance and tone of each of the
contributor acknowledgements and/or dedications given therein.
L. Preserve all the Invariant Sections of the Document, unaltered in their text and
in their titles. Section numbers or the equivalent are not considered part of the
section titles.
M. Delete any section Entitled Endorsements. Such a section may not be included
in the Modified Version.
N. Do not retitle any existing section to be Entitled Endorsements or to conflict in
title with any Invariant Section.
O. Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or appendices that qualify
as Secondary Sections and contain no material copied from the Document, you may at
your option designate some or all of these sections as invariant. To do this, add their
titles to the list of Invariant Sections in the Modified Versions license notice. These
titles must be distinct from any other section titles.
You may add a section Entitled Endorsements, provided it contains nothing but
endorsements of your Modified Version by various partiesfor example, statements of
peer review or that the text has been approved by an organization as the authoritative
definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up
to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified
Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be
added by (or through arrangements made by) any one entity. If the Document already
includes a cover text for the same cover, previously added by you or by arrangement
made by the same entity you are acting on behalf of, you may not add another; but you
may replace the old one, on explicit permission from the previous publisher that added
the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any
Modified Version.
5. COMBINING DOCUMENTS
You may combine the Document with other documents released under this License,
under the terms defined in section 4 above for modified versions, provided that you
include in the combination all of the Invariant Sections of all of the original documents,
unmodified, and list them all as Invariant Sections of your combined work in its license
notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical
Invariant Sections may be replaced with a single copy. If there are multiple Invariant
Sections with the same name but different contents, make the title of each such section
unique by adding at the end of it, in parentheses, the name of the original author or
publisher of that section if known, or else a unique number. Make the same adjustment
277
to the section titles in the list of Invariant Sections in the license notice of the combined
work.
In the combination, you must combine any sections Entitled History in the various
original documents, forming one section Entitled History; likewise combine any sections Entitled Acknowledgements, and any sections Entitled Dedications. You must
delete all sections Entitled Endorsements.
6. COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other documents released
under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the
rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted
document, and follow this License in all other respects regarding verbatim copying of
that document.
7. AGGREGATION WITH INDEPENDENT

WORKS
A compilation of the Document or its derivatives with other separate and independent
documents or works, in or on a volume of a storage or distribution medium, is called an
aggregate if the copyright resulting from the compilation is not used to limit the legal
rights of the compilations users beyond what the individual works permit. When the
Document is included in an aggregate, this License does not apply to the other works in
the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Documents
Cover Texts may be placed on covers that bracket the Document within the aggregate,
or the electronic equivalent of covers if the Document is in electronic form. Otherwise
they must appear on printed covers that bracket the whole aggregate.
8. TRANSLATION
Translation is considered a kind of modification, so you may distribute translations
of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include
translations of some or all Invariant Sections in addition to the original versions of these
Invariant Sections. You may include a translation of this License, and all the license
notices in the Document, and any Warranty Disclaimers, provided that you also include
the original English version of this License and the original versions of those notices and
disclaimers. In case of a disagreement between the translation and the original version
of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled Acknowledgements, Dedications, or
History, the requirement (section 4) to Preserve its Title (section 1) will typically
require changing the actual title.
278
9. TERMINATION
You may not copy, modify, sublicense, or distribute the Document except as expressly
provided under this License. Any attempt otherwise to copy, modify, sublicense, or
distribute it is void, and will automatically terminate your rights under this License.
However, if you cease all violation of this License, then your license from a particular
copyright holder is reinstated (a) provisionally, unless and until the copyright holder
explicitly and finally terminates your license, and (b) permanently, if the copyright holder
fails to notify you of the violation by some reasonable means prior to 60 days after the
cessation.
Moreover, your license from a particular copyright holder is reinstated permanently
if the copyright holder notifies you of the violation by some reasonable means, this is the
first time you have received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after your receipt of the
notice.
Termination of your rights under this section does not terminate the licenses of parties
who have received copies or rights from you under this License. If your rights have been
terminated and not permanently reinstated, receipt of a copy of some or all of the same
material does not give you any rights to use it.
10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free
Documentation License from time to time. Such new versions will be similar in spirit to
the present version, but may differ in detail to address new problems or concerns. See
http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License or any later version
applies to it, you have the option of following the terms and conditions either of that
specified version or of any later version that has been published (not as a draft) by the
Free Software Foundation. If the Document does not specify a version number of this
License, you may choose any version ever published (not as a draft) by the Free Software
Foundation. If the Document specifies that a proxy can decide which future versions
of this License can be used, that proxys public statement of acceptance of a version
permanently authorizes you to choose that version for the Document.
11. RELICENSING
Massive Multiauthor Collaboration Site (or MMC Site) means any World Wide
Web server that publishes copyrightable works and also provides prominent facilities for
anybody to edit those works. A public wiki that anybody can edit is an example of
such a server. A Massive Multiauthor Collaboration (or MMC) contained in the
site means any set of copyrightable works thus published on the MMC site.
CC-BY-SA means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal
place of business in San Francisco, California, as well as future copyleft versions of that
license published by that same organization.
279
Incorporate means to publish or republish a Document, in whole or in part, as part
of another Document.
An MMC is eligible for relicensing if it is licensed under this License, and if all
works that were first published under this License somewhere other than this MMC, and
subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or
invariant sections, and (2) were thus incorporated prior to November 1, 2008.
The operator of an MMC Site may republish an MMC contained in the site under
CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is
eligible for relicensing.
ADDENDUM: How to use this License for your

documents
To use this License in a document you have written, include a copy of the License
in the document and put the following copyright and license notices just after the title
page:
Copyright YEAR YOUR NAME. Permission is granted to copy, distribute
and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software
Foundation; with no Invariant Sections, no Front-Cover Texts, and no BackCover Texts. A copy of the license is included in the section entitled GNU
Free Documentation License.
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the
with . . . Texts. line with this:
with the Invariant Sections being LIST THEIR TITLES, with the FrontCover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of
the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the
GNU General Public License, to permit their use in free software.
Bibliography
[1] G. M. Adelson-Velski and E. M. Landis. An algorithm for the organization of information. Soviet Mathematics Doklady, 3:12591263, 1962.
[2] A. V. Aho, J. E. Hopcroft, and J. D. Ullman. The Design and Analysis of Computer
Algorithms. Addison-Wesley Publishing Company, 1974.
[3] W. Aiello, F. Chung, and L. Lu. A random graph model for massive graphs. In Proceedings of the 32nd Annual ACM Symposium on Theory of Computing, pages 171180.
Association for Computing Machinery, 2000.
[4] W. Aiello, F. Chung, and L. Lu. Handbook of Massive Data Sets, volume 4 of Massive Computing, chapter Random evolution of massive graphs, pages 97122. Kluwer
Academic Publishers, 2002.
[5] R. Albert and A.-L. Barab
asi. Statistical mechanics of complex networks. Reviews of
Modern Physics, 74(1):4797, 2002.
[6] R. Albert, H. Jeong, and A.-L. Barabasi. Diameter of the World-Wide Web. Nature,
401(6749):130131, 1999.
[7] L. A. N. Amaral, A. Scala, M. Barthelemy, and H. E. Stanley. Classes of small-world
networks. Proceedings of the National Academy of Sciences USA, 97(21):1114911152,
2000.
[8] V. Arlazarov, E. Dinic, M. Kronrod, and I. Faradzev. On economical construction of
the transitive closure of a directed graph. Soviet Mathematics Doklady, 11(5):12091210,
1970.
[9] L. Backstrom, D. Huttenlocher, J. Kleinberg, and X. Lan. Group formation in large
social networks: Membership, growth, and evolution. In T. Eliassi-Rad, L. H. Ungar,
M. Craven, and D. Gunopulos, editors, Proceedings of the Twelfth ACM SIGKDD International Conference on Knowledge Discovery and Data Mining, pages 4454, Philadelphia, PA, USA, 2006. Association for Computing Machinery.
[10] M. Baker and X. Faber. Quantum Graphs and Their Applications, volume 415 of Contemporary Mathematics, chapter Metrized Graphs, Laplacian Operators, and Electrical
Networks, pages 1533. American Mathematical Society, 2006.
[11] W. W. R. Ball and H. S. M. Coxeter. Mathematical Recreations and Essays. Dover
Publications, 13th edition, 1987.
[12] A.-L. Barab
asi. Linked: The New Science of Networks. Basic Books, 2002.
[13] A.-L. Barab
asi and R. Albert. Emergence of scaling in random networks. Science,
286(5439):509512, 1999.
[14] A.-L. Barab
asi, R. Albert, and H. Jeong. Mean-field theory for scale-free random networks. Physica A, 272(1-2):173187, 1999.
[15] A.-L. Barab
asi, R. Albert, and H. Jeong. Scale-free characteristics of random networks:
The topology of the world wide web. Physica A, 281(1-4):6977, 2000.
[16] A. Barrat, M. Barthelemy, and A. Vespignani. Dynamical Processes on Complex Networks. Cambridge University Press, 2008.
[17] A. Barrat and M. Weigt. On the properties of small-world network models. The European
Physical Journal B, 13(3):547560, 2000.
280
Bibliography
281
[18] V. Batagelj and U. Brandes. Efficient generation of large random networks. Physical
Review E, 71(3):036113, 2005.
[19] R. A. Beezer. A First Course in Linear Algebra. Robert A. Beezer, University of Puget
Sound, USA, 2009. http://linear.ups.edu.
[20] J. Bell and B. Stevens. A survey of known results and research areas for n-queens.
Discrete Mathematics, 309(1):131, 2009.
[21] R. Bellman. Dynamic Programming. Princeton University Press, 1957.
[22] E. Ben-Naim, H. Frauenfelder, and Z. Toroczkai, editors. Complex Networks. Springer,
2004.
[23] A. T. Benjamin and C. R. Yerger. Combinatorial interpretations of spanning tree identities. Bulletin of the Institute for Combinatorics and its Applications, 47(May):3742,
2006.
[24] N. L. Biggs. Codes: An Introduction to Information, Communication, and Cryptography.
Springer, 2009.
[25] B. Bollob
as. Random Graphs. Cambridge University Press, 2nd edition, 2001.
[26] B. Bollob
as, R. Kozma, and D. Miklos, editors. Handbook of Large-Scale Random Networks. J
anos Bolyai Mathematical Society and Springer, 2008.
[27] B. Bollob
as and O. Riordan. The diameter of a scale-free random graph. Combinatorica,
24(1):534, 2004.
[28] B. Bollob
as, O. Riordan, J. Spencer, and G. E. Tusnady. The degree sequence of a
scale-free random graph process. Random Structures & Algorithms, 18(3):279290, 2001.
[29] S. P. Borgatti. Centrality and network flow. Social Networks, 27(1):5571, 2005.
[30] S. Bornholdt and H. G. Schuster, editors. Handbook of Graphs and Networks: From the
Genome to the Internet. Wiley-VCH, 2003.
[31] O. Bor
uvka. O jistem problemu minimalnm (about a certain minimal problem). Pr
ace
mor. prrodoved. spol. v Brne III, 3:3758, 1926.
[32] O. Bor
uvka. Prspevek k resen otazky ekonomicke stavby elektrovodnch st (contribution to the solution of a problem of economical construction of electrical networks).
Elektronicky Obzor, 15:153154, 1926.
[33] J. M. Boyer and W. J. Myrvold. On the cutting edge: Simplified O(n) planarity by edge
addition. Journal of Graph Algorithms and Applications, 8(2):241273, 2004.
[34] K. M. Briggs. The verywnauty graph library (version 1.1), accessed 28th January 2011.
http://keithbriggs.info/very_nauty.html.
[35] M. Brinkmeier and T. Schank. Network Analysis: Methodological Foundations, volume
3418 of Lecture Notes in Computer Science, chapter Network Statistics, pages 293317.
Springer, 2005.
[36] A. Broder, R. Kumar, F. Maghoul, P. Raghavan, S. Rajagopalan, R. Stata, A. Tomkins,
and J. Wiener. Graph structure in the web. Computer Networks, 33(1-6):309320, 2000.
[37] M. R. Brown. The Analysis of a Practical and Nearly Optimal Priority Queue. PhD thesis, Computer Science Department, Stanford University, 1977. Technical Report STANCS-77-600.
[38] M. R. Brown. Implementation and analysis of binomial queue algorithms. SIAM Journal
on Computing, 7(3):298319, 1978.
[39] J. Buchmann, E. Dahmen, and M. Schneider. Merkle tree traversal revisited. In J. Buchmann and J. Ding, editors, Post-Quantum Cryptography, Second International Workshop, PQCrypto 2008, volume 5299 of Lecture Notes in Computer Science, pages 6378.
Springer, 2008.
[40] F. Buckley and F. Harary. Distance in Graphs. Perseus Books, 1990.
[41] F. Buckley and W. Y. Lau. Mutually eccentric vertices in graphs. Ars Combinatoria,
67(April), 2003.
282
Bibliography
[42] G. Caldarelli and A. Vespignani, editors. Large Scale Structure and Dynamics of Complex Networks: From Information Technology to Finance and Natural Science. World
Scientific, 2007.
[43] D. S. Callaway, J. E. Hopcroft, J. M. Kleinberg, M. E. J. Newman, and S. H. Strogatz.
Are randomly grown graphs really random? Physical Review E, 64(4):041902, 2001.
[44] R. D. Castro and J. W. Grossman. Famous trails to Paul Erdos. Mathematical Intelligencer, 21(3):5153, 1999.
[45] J.-L. Chabert, editor. A History of Algorithms: From the Pebble to the Microchip.
Springer, 1999.
[46] B. Chazelle. A minimum spanning tree algorithm with inverse-Ackermann type complexity. Journal of the ACM, 47(6):10281047, 2000.
[47] B. Chazelle. The soft heap: An approximate priority queue with optimal error rate.
Journal of the ACM, 47(6):10121027, 2000.
[48] Q. Chen, H. Chang, R. Govindan, S. Jamin, S. Shenker, and W. Willinger. The origin
of power-laws in internet topologies revisited. In Proceedings of the 21st Annual Joint
Conference of the IEEE Computer and Communications Societies, pages 608617. IEEE
Computer Society, 2002.
[49] A. G. Chetwynd and A. J. W. Hilton. Star multigraphs with three vertices of maximum
degree. Math. Proc. Camb. Phil. Soc., 100:303317, 1986.
[50] G. Choquet. Etude

de certains reseaux de routes. Comptes Rendus Hebdomadaires des
Seances de lAcademie des Sciences, 206:310313, 1938.
[51] D. Cohen. On holy wars and a plea for peace, 01st April 1980. http://www.ietf.org/
rfc/ien/ien137.txt.
[52] D. Cohen. On holy wars and a plea for peace. IEEE Computer Magazine, 14(10):4854,
1981.
[53] R. Cohen and S. Havlin. Complex Networks: Structure, Robustness and Function. Cambridge University Press, 2010.
[54] T. H. Cormen, C. E. Leiserson, R. L. Rivest, and C. Stein. Introduction to Algorithms.
MIT Press and McGraw-Hill, 2nd edition, 2001.
[55] P. Csermely. Weak Links: The Universal Key to the Stability of Networks and Complex
Systems. Springer, 2009.
[56] D. J. de Solla Price. Networks of scientific papers. Science, 149(3683):510515, 1965.
[57] M. Dehmer and F. Emmert-Streib, editors. Analysis of Complex Networks: From Biology
to Linguistics. Wiley-VCH, 2009.
[58] E. W. Dijkstra. A note on two problems in connexion with graphs. Numerische Mathematik, 1(1):269271, 1959.
[59] S. N. Dorogovtsev and J. F. F. Mendes. Language as an evolving word web. Proceedings
of the Royal Society B: Biological Sciences, 268(1485):26032606, 2001.
[60] S. N. Dorogovtsev and J. F. F. Mendes. Evolution of networks. Advances in Physics,
51(4):10791187, 2002.
[61] S. N. Dorogovtsev and J. F. F. Mendes. Evolution of Networks: From Biological Nets to
the Internet and WWW. Clarendon Press, 2002.
[62] H. Dorrie. 100 Great Problems of Elementary Mathematics: Their History and Solution.
Translated by David Antin. Dover Publications, 1965.
[63] M. Dyer and A. Frieze. Randomly coloring random graphs. Random Structures &
Algorithms, 36(3):251272, 2010.
[64] D. Easley and J. Kleinberg. Networks, Crowds, and Markets: Reasoning about a Highly
Connected World. Cambridge University Press, 2010.
[65] M. Edelberg, M. R. Garey, and R. L. Graham. On the distance matrix of a tree. Discrete
Mathematics, 14(1):2339, 1976.
[66] N. D. Elkies and R. P. Stanley. The mathematical knight. The Mathematical Intelligencer,
25(1):2234, 2003.
Bibliography
283
[67] R. C. Entringer, D. E. Jackson, and D. A. Snyder. Distance in graphs. Czechoslovak

Mathematical Journal, 26(2):283296, 1976.
[68] P. Erd
os and T. Gallai. Graphs with prescribed degrees of vertices (in Hungarian).
Matematikai Lopak, 11:264274, 1960.
[69] P. Erd
os and A. Renyi. On random graphs. Publicationes Mathematicae, 6:290297,
1959.
[70] P. Erd
os and A. Renyi. On the evolution of random graphs. Magyar Tudomanyos
Akademia Matematikai Kutat
o Intezetenek K
ozlemenyei, 5:1761, 1960.
[71] P. L. Erd
os, I. Mikl
os, and Z. Toroczkai. A simple Havel-Hakimi type algorithm to realize
graphical degree sequences of directed graphs. Electronic Journal of Combinatorics,
17(1):R66, 2010.
[72] M. Faloutsos, P. Faloutsos, and C. Faloutsos. On power-law relationships of the Internet
topology. Computer Communications Review, 29(4):251262, 1999.
[73] R. Ferrer i Cancho and R. V. Sole. The small world of human language. Proceedings of
the Royal Society B: Biological Sciences, 268(1482):22612265, 2001.
[74] K. Florek, J. Lukaszewicz, J. Perkal, H. Steinhaus, and S. Zubrzycki. Sur la liaison et la
division des points dun ensemble fini. Colloquium Mathematicum, 2:282285, 1951.
[75] R. W. Floyd. Algorithm 97: Shortest path. Communications of the ACM, 5(6):345,
1962.
[76] L. R. Ford Jr. Network flow theory. Technical Report P-923, The Rand Corporation,
USA, 1956.
[77] L. R. Foulds. Graph Theory Applications. Springer, 1992.
[78] G. N. Frederickson. An optimal algorithm for selection in a min-heap. Information and
Computation, 104(2):197214, 1993.
[79] M. L. Fredman and R. E. Tarjan. Fibonacci heaps and their uses in improved network optimization algorithms. In 25th Annual Symposium on Foundations of Computer Science.
IEEE, 1984.
[80] M. L. Fredman and R. E. Tarjan. Fibonacci heaps and their uses in improved network
optimization algorithms. Journal of the ACM, 34(3):596615, 1987.
[81] G. Gallo and S. Pallottino. Netflow at Pisa, volume 26 of Mathematical Programming
Studies, chapter Shortest path methods: A unifying approach, pages 3864. Springer,
1986.
[82] N. Ganguly, A. Deutsch, and A. Mukherjee, editors. Dynamics On and Of Complex Networks: Applications to Biology, Computer Science, and the Social Sciences. Birkhauser,
2009.
[83] D. Garlaschelli. The weighted random graph model. New Journal of Physics,
11(7):073005, 2009.
[84] E. N. Gilbert. Random graphs. Annals of Mathematical Statistics, 30(4):11411144,
1959.
[85] R. L. Graham and P. Hell. On the history of the minimum spanning tree problem. Annals
of the History of Computing, 7(1):4357, 1985.
[86] R. L. Graham and H. O. Pollak. On the addressing problem for loop switching. Bell
System Technical Journal, 50:24952519, 1971.
[87] I. Gribkovskaia, . Halskau Sr., and G. Laporte. The bridges of Konigsberga historical
perspective. Networks, 49(3):199203, 2007.
[88] J. Gross and J. Yellen. Graph Theory and Its Applications. CRC Press, 1999.
[89] T. Gross and H. Sayama, editors. Adaptive Networks: Theory, Models and Applications.
Springer, 2009.
[90] J. W. Grossman and P. D. F. Ion. On a portion of the well-known collaboration graph.
Congressus Numerantium, 108:129131, 1995.
[91] J. Guare. Six Degrees of Separation: A Play. Vintage, 1990.
284
Bibliography
[92] I. Gutman, Y.-N. Yeh, S.-L. Lee, and Y.-L. Luo. Some recent results in the theory of
the Wiener number. Indian Journal of Chemistry, 32A(8):651661, 1993.
[93] S. L. Hakimi. On realizability of a set of integers as degrees of the vertices of a linear
graph I. SIAM Journal of Applied Mathematics, 10(3):496506, 1962.
[94] S. L. Hakimi. On realizability of a set of integers as degrees of the vertices of a linear
graph II: Uniqueness. SIAM Journal of Applied Mathematics, 11(1):135147, 1963.
[95] V. Havel. Pozn
amka o existenci konecn
ych graf
u (in Czech, a remark on the existence
of finite graphs). Casopis

pro Pestov
an Matematiky, 80(4):477480, 1955.
[96] K. Heinrich and P. Hor
ak. Eulers theorem. American Mathematical Monthly,
101(3):260261, 1994.
[97] C. A. R. Hoare. Quicksort. Computer Journal, 5(1):1015, 1962.
[98] J. E. Hopcroft and R. E. Tarjan. Algorithm 447: Efficient algorithms for graph manipulation. Communications of the ACM, 16(6):372378, 1973.
[99] J. E. Hopcroft and R. E. Tarjan. Efficient planarity testing. Journal of the ACM,
21(4):549568, 1974.
[100] B. Hopkins and R. Wilson. The truth about Konigsberg. The College Mathematics
Journal, 35(3):198207, 2004.
[101] W. G. Horner. A new method of solving numerical equations of all orders, by continuous
approximation. Philosophical Transactions of the Royal Society of London, 109:308335,
1819.
[102] S. Howard. C algorithms (version 1.2.0), accessed 20th December 2010. http:
//c-algorithms.sourceforge.net.
[103] D. A. Huffman. A method for the construction of minimum-redundancy codes. In
Proceedings of the I.R.E, volume 40, pages 10981102, 1952.
[104] M. Huxham, S. Beaney, and D. Raffaelli. Do parasites reduce the chances of triangulation
in a real food web? Oikos, 76(2):284300, 1996.
[105] V. Jarnk. O jistem problemu minimalnm (Z dopisu panu O. Bor
uvkovi) (Czech). Pr
ace
Moravske Prrodovedecke Spolecnosti Brno, 6:5763, 1930.
[106] T. R. Jensen and B. Toft. Graph Coloring Problems. John Wiley & Sons, 1995.
[107] H. Jeong, S. Mason, A.-L. Barabasi, and Z. N. Oltvai. Lethality and centrality in protein
networks. Nature, 411(6833):4142, 2001.
[108] H. Jeong, B. Tombor, R. Albert, Z. N. Oltvai, and A.-L. Barabasi. The large-scale
organization of metabolic networks. Nature, 407(6804):651654, 2000.
[109] D. B. Johnson. Efficient algorithms for shortest paths in sparse networks. Journal of the
ACM, 24(1):113, 1977.
[110] J. H. Jones and M. S. Handcock. An assessment of preferential attachment as a mechanism for human sexual network formation. Proceedings of the Royal Society B: Biological
Sciences, 270(1520):11231128, 2003.
[111] C. Jordan. Sur les assemblages de lignes. Journal f
ur die reine und angewandte Mathematik, 70(January):185190, 1869.
[112] D. Jungnickel. Graphs, Networks and Algorithms. Springer, 3rd edition, 2008.
[113] D. Kalman. Marriages made in the heavens: A practical application of existence. Mathematics Magazine, 72(2):94103, 1999.
[114] H. Kaplan and U. Zwick. A simpler implementation and analysis of Chazelles soft heaps.
In C. Mathieu, editor, SODA 2009: Proceedings of the Twentieth Annual ACM-SIAM
Symposium on Discrete Algorithms, pages 477485. SIAM, 2009.
[115] A. Kershenbaum and R. Van Slyke. Computing minimum spanning trees efficiently. In
Proceedings of the ACM Annual Conference 25, pages 518527. Association for Computing Machinery, 1972.
[116] S. C. Kleene. Automata Studies, chapter Representation of Events in Nerve Nets and
Finite Automata, pages 341. Princeton University Press, 1956.
Bibliography
285
[117] J. Kleinberg. The small-world phenomenon: An algorithmic perspective. In STOC 00:

Proceedings of the Thirty-Second Annual ACM Symposium on Theory of Computing,
pages 163170. Association for Computing Machinery, 2000.
[118] D. E. Knuth. The Stanford GraphBase: A Platform for Combinatorial Computing.
Addison-Wesley, 1993.
[119] D. E. Knuth. Seminumerical Algorithms, volume 2 of The Art of Computer Programming.
Addison-Wesley, 3rd edition, 1998.
[120] D. E. Knuth. Sorting and Searching, volume 3 of The Art of Computer Programming.
Addison-Wesley, 2nd edition, 1998.
[121] V. F. Kolchin. Random Graphs. Cambridge University Press, 1999.
[122] L. G. Kraft. A device for quantizing, grouping, and coding amplitude-modulated pulses.
Masters thesis, Department of Electrical Engineering, Massachusetts Institute of Technology, USA, 1949.
[123] J. B. Kruskal. On the shortest spanning subtree of a graph and the traveling salesman
problem. Proceedings of the American Mathematical Society, 7(1):4850, 1956.
[124] K. Kuratowski. Sur le problème des courbes gauches en topologie. Fundamenta Mathematicae, 15:271283, 1930.
[125] J. C. Lagarias. The 3x + 1 problem and its generalizations. The American Mathematical
Monthly, 92(1):323, 1985.
[126] J. C. Lagarias. The 3x+1 problem: An annotated bibliography (19631999), 03rd August
2009. arXiv:math/0309224, http://arxiv.org/abs/math.NT/0309224.
[127] J. C. Lagarias. The 3x+1 problem: An annotated bibliography, II (2000-2009), 27th August 2009. arXiv:math/0608208, http://arxiv.org/abs/math.NT/0608208.
[128] V. Latora and M. Marchiori. Economic small-world behavior in weighted networks. The
European Physical Journal B, 32(2):249263, 2003.
[129] H. T. Lau. A Java Library of Graph Algorithms and Optimization. Chapman & Hall/CRC, 2007.
[130] C. Y. Lee. An algorithm for path connections and its applications. IRE Transactions on
Electronic Computers, EC-10(3):346365, 1961.
[131] D. H. Lehmer. Mathematical methods in large-scale computing units. In Proceedings of
the Second Symposium on Large-Scale Digital Calculating Machinery, 1949.
[132] J. Leskovec, J. M. Kleinberg, and C. Faloutsos. Graphs over time: Densification laws,
shrinking diameters and possible explanations. In R. Grossman, R. J. Bayardo, and K. P.
Bennett, editors, Proceedings of the Eleventh ACM SIGKDD International Conference
on Knowledge Discovery and Data Mining, pages 177187. Association for Computing
Machinery, 2005.
[133] J. Leskovec, K. J. Lang, A. Dasgupta, and M. W. Mahoney. Statistical properties of community structure in large social and information networks. In J. Huai, R. Chen, H.-W.
Hon, Y. Liu, W.-Y. Ma, A. Tomkins, and X. Zhang, editors, Proceedings of the 17th International Conference on World Wide Web, pages 695704. Association for Computing
Machinery, 2008.
[134] F. Liljeros, C. R. Edling, L. A. N. Amaral, H. E. Stanley, and Y.
Aberg. The web of
human sexual contacts. Nature, 411(6840):907908, 2001.
[135] H. Loberman and A. Weinberger. Formal procedures for connecting terminals with a
minimum total wire length. Journal of the ACM, 4(4):428437, 1957.
[136] M. Loebbing and I. Wegener. The number of knights tours equals 33,439,123,484,294
counting with binary decision diagrams. The Electronic Journal of Combinatorics,
3(1):R5, 1996.
[137] M. E. Lucas. Recreations Mathematiques. 4 volumes, Gauthier-Villars, Paris, 188294.
[138] N. D. Martinez. Artifacts or attributes? Effects of resolution on the Little Rock Lake
food web. Ecological Monographs, 61(4):367392, 1991.
286
Bibliography
[139] B. McKay. Description of graph6 and sparse6 encodings, accessed 05th April 2010.
http://cs.anu.edu.au/~bdm/data/formats.txt.
[140] B. D. McKay. Knights tours of an 8 8 chessboard. Technical Report TR-CS-97-03,
Department of Computer Science, Australian National University, Australia, February
1997.
[141] B. McMillan. Two inequalities implied by unique decipherability. IRE Transactions on
Information Theory, 2(4):115116, 1956.
[142] A. J. Menezes, P. C. van Oorschot, and S. A. Vanstone. Handbook of Applied Cryptography. CRC Press, 1996.
[143] R. C. Merkle. A digital signature based on a conventional encryption function. In
C. Pomerance, editor, Advances in Cryptology CRYPTO 87, A Conference on the
Theory and Applications of Cryptographic Techniques, volume 293 of Lecture Notes in
Computer Science, pages 369378. Springer, 1987.
[144] S. Milgram. The small world problem. Psychology Today, 1(1):6067, 1967.
[145] B. Mohar, D. Babic, and N. Trinajstic. A novel definition of the Wiener index for trees.
Journal of Chemical Information and Computer Sciences, 33(1):153154, 1993.
[146] E. F. Moore. The shortest path through a maze. In Proceedings of the International
Symposium on the Theory of Switching, pages 285292, 1959.
[147] S. Myles, A. R. Boyko, C. L. Owens, P. J. Brown, F. Grassi, M. K. Aradhya, B. Prins,
A. Reynolds, J.-M. Chia, D. Ware, C. D. Bustamante, and E. S. Buckler. Genetic
structure and domestication history of the grape. Proceedings of the National Academy
of Sciences USA, 2010.
[148] M. Newman, A.-L. Barab
asi, and D. J. Watts. The Structure and Dynamics of Networks.
Princeton University Press, 2006.
[149] M. E. J. Newman. Scientific collaboration networks: I. Network construction and fundamental results. Physical Review E, 64(1):016131, 2001.
[150] M. E. J. Newman. The structure of scientific collaboration networks. Proceedings of the
National Academy of Sciences USA, 98(2):404409, 2001.
[151] M. E. J. Newman. Mixing patterns in networks. Physical Review E, 67(2):026126, 2003.
[152] M. E. J. Newman. The structure and function of complex networks. SIAM Review,
45(2):167256, 2003.
[153] M. E. J. Newman. Networks: An Introduction. Oxford University Press, 2010.
[154] M. E. J. Newman, S. H. Strogatz, and D. J. Watts. Random graphs with arbitrary degree
distribution and their applications. Physical Review E, 64(2):026118, 2001.
[155] E. Nuutila. Efficient Transitive Closure Computation in Large Digraphs, volume 74 of
Mathematics and Computing in Engineering Series. Finnish Academy of Technology,
1995. http://www.cs.hut.fi/~enu/thesis.html.
[156] J. Oxley. What is a matroid? Cubo Matem
atica Educacional, 5(3):179218, 2003.
[157] J. Petersen. Sur le theorème de tait. LIntermediaire des Mathematiciens, 5:225227,
1898.
[158] G. Polya. How To Solve It: A New Aspect of Mathematical Method. Princeton University
Press, 2nd edition, 1957.
[159] R. C. Prim. Shortest connection networks and some generalizations. Bell System Technical Journal, 36:13891401, 1957.
[160] R. Rasmussen. Algorithmic Approaches for Playing and Solving Shannon Games. PhD
thesis, Faculty of Information Technology, Queensland University of Technology, Australia, 2007. http://eprints.qut.edu.au/18616/.
[161] S. Redner. How popular is your paper? An empirical study of the citation distribution.
The European Physical Journal B, 4(2):131134, 1998.
[162] K. H. Rosen. Elementary Number Theory and Its Applications. Addison Wesley Longman, 4th edition, 2000.
Bibliography
287
[163] B. Roy. Transitivite et connexite. Comptes Rendus des Seances de lAcademie des
Sciences, 249:216218, 1959.
[164] V. Runde. A Taste of Topology. Springer, 2005.
[165] R. Sedgewick. Algorithms in C. Addison-Wesley Publishing Company, 1990.
[166] P. O. Seglen. The skewness of science. Journal of the American Society for Information
Science, 43(9):628638, 1992.
[167] P. Sen, S. Dasgupta, A. Chatterjee, P. A. Sreeram, G. Mukherjee, and S. S. Manna.
Small-world properties of the Indian railway network. Physical Review E, 67(3):036106,
2003.
[168] A. Shimbel. Structure in communications nets. In Proceedings of the Symposium on
Information Networks, pages 199203, 1955.
[169] S. Shirali and H. L. Vasudeva. Metric Spaces. Springer, 2006.
[170] V. Shoup. A Computational Introduction to Number Theory and Algebra. Cambridge
University Press, 2nd edition, 2008. http://www.shoup.net/ntb.
[171] G. Sierksma and H. Hoogeveen. Seven criteria for integer sequences being graphic.
Journal of Graph Theory, 15(2):223231, 1991.
[172] H. A. Simon. On a class of skew distribution functions. Biometrika, 42(3-4):425440,
1955.
[173] D. R. Stinson. Cryptography: Theory and Practice. Chapman & Hall/CRC, 2nd edition,
2002.
[174] M. Szydlo. Merkle tree traversal in log space and time. In C. Cachin and J. Camenisch,
editors, Advances in Cryptology - EUROCRYPT 2004, International Conference on the
Theory and Applications of Cryptographic Techniques, volume 3027 of Lecture Notes in
Computer Science, pages 541554. Springer, 2004.
[175] T. Takaoka. O(1) time algorithms for combinatorial generation by tree traversal. The
Computer Journal, 42(5):400408, 1999.
[176] T. Takaoka. Theory of 2-3 heaps. In T. Asano, H. Imai, D. T. Lee, S.-I. Nakano,
and T. Tokuyama, editors, COCOON 99: Proceedings of the 5th Annual International
Conference on Computing and Combinatorics, volume 1627 of Lecture Notes in Computer
Science. Springer, 1999.
[177] R. E. Tarjan. Depth-first search and linear graph algorithms. SIAM Journal on Computing, 1(2):146160, 1972.
[178] G. Tarry. Le problème des labyrinthes. Nouvelles Annales de Mathematique, 14(3):187
190, 1895.
[179] W. Trappe and L. C. Washington. Introduction to Cryptography with Coding Theory.
Pearson Education, 2nd edition, 2006.
[180] J. Travers and S. Milgram. An experimental study of the small world problem. Sociometry, 32(4):425443, 1969.
[181] D. Trietsch. Eulers problem of polygon division and full steiner topologiesa duality.
Technical Report 625, Center for Mathematical Studies in Economics and Management
Science, Northwestern University, USA, October 1984. http://econpapers.repec.org/
paper/nwucmsems/625.htm.
[182] A. Tripathi and S. Vijay. A note on a theorem of Erdos & Gallai. Discrete Mathematics,
265(1-3):417420, 2003.
[183] S. Valverde, R. F. Cancho, and R. V. Sole. Scale-free networks from optimal design.
Europhysics Letters, 60(4):512517, 2002.
[184] A. Vazquez, R. Pastor-Satorras, and A. Vespignani. Large-scale topological and dynamical properties of the Internet. Physical Review E, 65(6):066130, 2002.
[185] J. S. Vitter. Random sampling with a reservoir. ACM Transactions on Mathematical
Software, 11(1):3757, 1985.
[186] J. Vuillemin. A data structure for manipulating priority queues. Communications of the
ACM, 21(4):309315, 1978.
288
Bibliography
[187] H. Walther. Ten Applications of Graph Theory. Kluwer Academic Publishers, 1984.
[188] S. Warshall. A theorem on boolean matrices. Journal of the ACM, 9(1):1112, 1962.
[189] D. J. Watts. Networks, dynamics, and the small-world phenomenon. The American
Journal of Sociology, 105(2):493527, 1999.
[190] D. J. Watts. Small Worlds. Princeton University Press, 1999.
[191] D. J. Watts. Six Degrees: The Science of a Connected Age. W. W. Norton & Company,
2004.
[192] D. J. Watts and S. H. Strogatz. Collective dynamics of small-world networks. Nature,
393(6684):440442, 1998.
[193] J. G. White, E. Southgate, J. N. Thompson, and S. Brenner. The structure of the nervous
system of the nematode Caenorhabditis elegans. Philosophical Transactions of the Royal
Society B: Biological Sciences, 314(1165):1340, 1986.
[194] H. Whitney. Congruent graphs and the connectivity of graphs. American Journal of
Mathematics, 54(1):150168, 1932.
[195] H. Wiener. Structural determination of paraffin boiling points. Journal of the American
Chemical Society, 69(1):1720, 1947.
[196] J. W. J. Williams. Algorithm 232: Heapsort. Communications of the ACM, 7(6):347348,
1964.
[197] T. Yamada, S. Kataoka, and K. Watanabe. Listing all the minimum spanning trees in an
undirected graph. International Journal of Computer Mathematics, 87(14):31753185,
2010.
[198] T. Yamada and H. Kinoshita. Finding all the negative cycles in a directed graph. Discrete
Applied Mathematics, 118(3):279291, 2002.
[199] V. Yegnanarayanan. Graph theory to pure mathematics: Some illustrative examples.
Resonance, 10(1):5059, 2005.
[200] Y.-N. Yeh and I. Gutman. On the sum of all distances in composite graphs. Discrete
Mathematics, 135(1-3):359365, 1994.
[201] W. W. Zachary. An information flow model for conflict and fission in small groups.
Journal of Anthropological Research, 33(4):452473, 1977.
Index
Cn , 16
En , 48
Gc , 33
Kn , 15
Km,n , 16
Ln , 34
Pn , 16, 34
Qn , 34
Wn , 28
, 28
(G), 9
adj, 4
L, 21, 41
Ni , 246
=, 22
deg, 5, 9
deg+ , 6
deg , 6
(G), 9
depth(v), 105
diam(G), 199
dir, 91
, 197
height(T ), 105
iadj, 5
id, 5
(G), 202
e (G), 203
v (G), 201
(G), 203
lg, 157
oadj, 5
od, 5
, 13
G, 33
per(G), 199
rad(G), 199
, 34
td, 90
, 134, 137
(n), 114
f -augmenting, 224
f -saturated, 224
f -unsaturated, 224
f -zero, 224
k-connected, 202
k-edge-connected, 203
n-queens problem, 100
n-space, 131
graph6, 53, 55, 57, 58
sparse6, 55, 57
Lukaszewicz, J., 122
acyclic, 104, 116, 117, 145
Adelson-Velski, G. M., 179
adjacency matrix, 18
reduced, 19
algorithm
greedy, 75, 76, 116, 119
optimization, 110
random, 50, 103, 145147, 234, 235, 239,
241, 242, 244, 251, 253, 254, 257
recursive, 150
alphabet, 39, 40, 129, 133
binary, 134, 135
English, 129, 147
weighted, 129, 136
Altito, Noelie, 84
arcs, 3
Argentina, 93, 94
ASCII, 55, 57, 129
augmenting path, 224
Australia, 93, 94
Australian National University, 55
automata theory, 38, 84
AVL tree, 179, 195
height-balance property, 179
backtrack, 63
algorithm, 101
Baker, Matthew, 197
balanced bracket problem, 97, 98
289
290
Bangkok, 93, 94
Barabasi-Albert model, 248
Batagelj, Vladimir, 237, 256
Batagelj-Brandes algorithm, 237, 239
Baudot, E., 130
Beijing, 93, 94
Bell, Jordan, 101
Bellman, Richard E., 76
Bellman-Ford algorithm, 72, 7679, 84, 85,
92
Benjamin, Arthur T., 151
Berlin, 93, 94
Bernoulli family, 106
BFS, 5963, 65, 69
big-endian, 57, 58
Biggs, Norman, 136
binary heap, 152, 154, 179
heap-structure property, 179
maximum, 191
minimum, 191
order property, 155, 193
sift-down, 160
sift-up, 158
structure property, 155
binary search, 88, 90, 174
binary search tree, 152, 172, 174, 179, 181,
182
left subtree property, 172
property, 172, 182, 193
recursion property, 172
right subtree property, 172
binary tree, 107, 109, 126128, 147, 152
complete, 126, 179
nearly complete, 155, 179
random, 128, 147
Binet
formula, 195
Jacques Philippe Marie, 195
binomial
coefficient, 165, 191
distribution, 234
random graph, 236
tree, 165
binomial heap, 152, 164, 165, 167, 193
maximum, 193
minimum, 193
order property, 167, 168, 193
properties, 167
Index
root-degree property, 167, 168
biology, 196
bipartite graph, 16, 17, 50, 256, 257
complete, 16, 17
bit, 57, 129, 134
least significant, 57
most significant, 57
parity, 57
bit vector, 55, 57, 58
length, 57
bond, 31, 110
Bor
uvka
algorithm, 116, 122, 124, 144, 145, 150
Otakar, 116, 122
bowtie graph, 12
braille, 129
branch cut, 107, 109
Brandes, Ulrik, 237, 256
Brasilia, 93, 94
Brazil, 93, 94
breadth-first search, 5963, 68, 69, 71, 72,
88, 91, 97, 109, 139, 140
tree, 59, 62
bridge, 31, 105, 111, 122, 203
bridgeless, 203
Briggs
algorithm, 255
Keith M., 255
BST, 172
bubble sort, 95, 96
Buenos Aires, 93, 94
butterfly graph, 12
Caenorhabditis elegans, 231
Canada, 93, 94
canonical label, 23, 24
Cantor-Schroder-Bernstein theorem, 50
capacity, 223
cut, 225
card, 65
cardinality, 9
Carroll, Lewis, 2
Cartesian product, 34, 35
Catalan
number, 48, 127
recursion, 127
Chazelle, Bernard, 193
check matrix, 19
Index
chemistry, 81, 196
chess, 63, 100, 129
chessboard, 63
knight, 63
knight piece, 63
knights tour, 6365, 100
queen, 100, 101
child
left, 126, 139, 144
right, 126, 139, 144
China, 93, 94
Chinese ring puzzle, 130, 131
CHKNS model, 255
Choquet, G., 122
Chu Shi-Chieh, 191
Chvatal graph, 145, 146
circuit, 12
board, 59
electronic, 115
classification tree, 105, 106, 110
claw graph, 202
closed form, 127
code, 129, 134
r-ary, 150
binary, 129, 134, 135
block, 129
economy, 129
error-correcting, 19, 129
linear, 131
optimal, 136
prefix, 129
prefix-free, 129, 135, 147
radix, 150
reliability, 129
security, 129
tree representation, 134
uniquely decodable, 135
variable-length, 129
codeword, 129, 134
length, 136
coding function, 129
Cohen, Danny, 57
Collatz
conjecture, 148
graph, 148, 149
length, 148
sequence, 148
tree, 148, 149
291
color code, 129
coloring
edge, 37
vertex, 37, 38
combinatorial generation, 191
combinatorial graphs, 2
combinatorics, 131
communications network, 205
complement, 33
complete graph, 15, 146, 147, 234, 239, 241,
244, 245, 253, 254
component, 13, 28, 111
connected, 116
computer science, 38, 139
condensed matter, 232
connected graph, 13, 110
connectivity, 97
cost, 70
Coward, Noel, 10
cryptosystem, 129
cut
set, 31, 112
cut-edge, 202, 203
cut-point, 201
cut-vertex, 201, 202
cycle, 12, 71, 72, 86, 104, 105, 111, 113
fundamental, 113, 147
negative, 71, 72, 77, 79, 8486, 103
cycle double cover conjecture, 203
cycle graph, 16, 50
DAngelo, Anthony J., 144
Dorrie, Heinrich, 48
data structure, 52, 152
de Moivre, Abraham, 195
de Montmort, Pierre Remond, 99
decode, 129
degree, 5, 9
matrix, 21
maximum, 9, 109
minimum, 9, 114
sequence, 24, 114
weighted, 7
degree distribution, 230232, 239, 249, 250
depth-first search, 59, 63, 6569, 72, 88, 91,
97, 109, 140
tree, 65, 68
de Moivre, Abraham, 99
292
DFA, 39, 40
DFS, 63, 6569
diameter, 62, 63
Digital Signature Algorithm, 150
digraph, 5, 105
weighted, 70
Dijkstra
algorithm, 14, 7277, 84, 85, 92, 152
E. W., 72, 119
Diracs theorem, 209
directedness, 91
disconnected graph, 13
disconnecting set, 31
distance, 52, 62, 6971, 73, 75, 77, 79, 105
characteristic, 232
function, 70, 71, 196, 197, 211
matrix, 21, 71
minimum, 73
total, 90
distance distribution, 233
distribution
binomial, 239
geometric, 238, 240
Poisson, 240
uniform, 239
divide and conquer, 103
Dryden, John, 58
dynamic programming, 79
eccentricity, 197, 198
mutual, 211
path, 211
vertex, 211
edge, 3
capacity, 223
contraction, 32
cut, 31, 110, 207
deletion, 31
deletion subgraph, 31
directed, 4
endpoint, 116
head, 6
incident, 3
multigraph, 6
multiple, 3
tagging game, 110
tail, 6
weight, 5, 6
Index
edge-cut, 202
Edmonds, Jack, 110
eigenvalue, 150
element
random, 127
Elkies, Noam D., 65
encode, 129
endianness, 57
England, 93, 94, 101
entropy
encoding, 129
function, 129
Erdos, Paul, 24, 25
error rate, 129
Euclidean algorithm, 87
Euler
Leonhard, 1, 9, 47, 48, 114
phi function, 114, 148
phi sequence, 114, 115
polygon division problem, 47, 48
subgraph, 12
Eulerian trail, 1
Faber, Xander, 197
family tree, 14, 105, 106
fault-tolerant, 205
Fermats little theorem, 50
Fibonacci
number, 179
sequence, 195
tree, 179, 181183, 194
FIFO, 60, 65
filesystem, 105
hierarchy, 105
finite automaton, 38, 39, 50
deterministic, 39, 40
nondeterministic, 40, 41
first in, first out, 60
flag semaphore, 129
Florek, K., 122
Florentine families, 37
flow, 223
value, 224
flow chart, 52
Floyd, Robert, 79
Floyd-Roy-Warshall algorithm, 77, 7981,
83, 84, 92, 200, 201
football, 129
Index
forbidden minor, 36
Ford, Lester Randolph, Jr., 76
forest, 104, 105
Foulds, L. R., 37
Franklin graph, 22
Frederickson, Greg N., 193
FreeBSD, 52
frequency distribution, 243
friendship graph, 210
FRW, 77, 79
function plot, 2
Gallai, Tibor, 24, 25
Garlaschelli, Diego, 255
genetic code, 129
Germany, 93, 94
Gilbert, E. N., 240
girth, 12
Goldbach, Christian, 47
Goldberg, R., 77
golden ratio, 151, 195
Graham, Ronald L., 116, 201
graph, 3
applications, 36
connected, 13, 69, 70
dense, 54, 79
directed, 5
disconnected, 13
intersection, 28
join, 28
nonisomorphic, 48
simple, 7
sparse, 17, 54, 79, 84, 85
traversal, 58, 59
trivial, 114, 122
undirected, 3
union, 27, 28
unweighted, 3
weighted, 5, 69, 70, 116, 119
graph isomorphism, 22, 24
graph minor, 36
graphical sequence, 24, 26
Gray code, 130, 131
m-ary, 130
binary, 130, 131
reflected, 131133
Gray, Frank, 130
Gribkovskaia, Irina, 1
293
grid, 35
graph, 102, 103, 105, 107, 118, 119, 145,
147
Gros, L., 130
group theory
computational, 131
Gullivers Travels, 57
Hakimi, S. L., 25
Halskau Sr., yvind, 1
Hamming distance, 34
Hampton Court Palace, 101
handshaking lemma, 9
Havel, Vaclav, 25
Havel-Hakimi
test, 26
theorem, 25
heap
2-heap, 119
k-ary, 76
binary, 76
binary minimum, 137
Fibonacci, 76, 84, 119
heapsort, 154
Heinrich, Katherine, 50
Hell, Pavol, 116
hierarchical structure, 14, 104, 105
Hoare, C. A. R., 97
Hopcroft, John E., 63
Hopkins, Brian, 1
Horak, Peter, 50
Horner
method, 87
W. G., 87
house graph, 3
Huffman
David, 136
tree, 152
Huffman code, 135138, 140, 147
binary, 136
encoding, 139
tree construction, 136
tree representation, 137, 138, 140
Humpty Dumpty, 2
hypercube graph, 34, 35, 131
in-neighbor, 5
incidence
function, 6
294
matrix, 20
incidence matrix
oriented, 21
unoriented, 20
indegree, 5
unweighted, 6, 7
India, 93, 94
induction, 111, 114, 126, 135, 136, 145
structural, 145
infix notation, 98
information channel, 129
insertion sort, 96
Internet, 248
topology, 249
interpolation search, 90
invariant, 23, 26
isomorphism, 114
Japan, 93, 94
Jarnk, V., 119
Johnson
algorithm, 72, 84, 85, 92
Donald B., 84
join, 113
Jordan, Camille, 200
Konigsberg, 1
graph, 2, 5
seven bridges puzzle, 1, 9
Kaliningrad, 1
Kaplan, Haim, 193
Kataoka, Seiji, 144
Kinoshita, Harunobu, 103
Kleene
algorithm, 84
Stephen, 84
Klein, Felix, 2
Kneser graph, 5355
Knuth
Algorithm S, 255
Donald E., 49, 90, 95, 96, 130, 255
Kraft
inequality, 150, 151
Leon Gordon, 151
theorem, 151
Kruskal
algorithm, 116119, 144, 145, 150
Joseph B., 116
Index
ladder graph, 34
Lagarias, Jeffrey C., 148
Landis, E. M., 179
language, 41
regular, 41
Laplacian matrix, 21, 150
Laporte, Gilbert, 1
last in, first out, 65
Latora, V., 255
Latora-Marchiori model, 255
lattice, 35
Lee, C. Y., 59
Lehman, A., 110
Lehmer, D. H., 49
level
binary tree, 155
tree, 194
LIFO, 65
Lima, 93, 94
linear search, 88
Linux, 105
list, 53, 59, 60, 62, 65, 76, 137
adjacency, 53, 54, 62
contiguous edge, 55, 244
edge, 55
element, 53
empty, 53
length, 53
little-endian, 57
Loberman, H., 116
Loebbing, Martin, 65
London, 93, 94
Lucas
M. Edouard,
63, 151
number, 151
Madrid, 93, 94
Marchiori, M., 255
marriage ties, 37
matrix, 17
adjacency, 18, 53, 54, 58
bi-adjacency, 19
distance, 201
main diagonal, 58
transpose, 47
upper triangle, 58
Matthew effect, 248
max-flow min-cut theorem, 225
Index
generalized, 226
maximum flow problem, 224
maze, 59, 63, 101
McKay, Brendan D., 55, 65
McMillan
Brockway, 150
theorem, 150
Menezes, Alfred J., 95
Mengers theorem, 206208
merge sort, 169
Merkle, Ralph C., 150
Merris-McKay theorem, 150
mesh, 35, 36
message, 133
metabolic network, 248
metric, 71, 197
function, 70
metric graph, 197
metric space, 71
finite, 71
Milgram, Stanley, 242
minimum cut problem, 225
minimum spanning tree problem, 116
molecular graph, 36, 37, 81
Montmort-Moivre strategy, 100
Moore, Edward F., 59, 76
Morse code, 130, 135, 147
Moscow, 93, 94
MST, 116
multi-undirected graph, 5
multidigraph, 5, 39
multigraph, 5
adjacency, 7
in-neighbor, 7
out-neighbor, 7
Munroe, Randall, 52, 63, 72, 76, 104, 152,
215, 216
musical score, 129
neighbor graph, 246
network, 38, 223
biological, 231, 242
citation, 249
collaboration, 249
communication, 110
flow, 38
information, 242
social, 232, 242, 249
295
technological, 231, 242
Zachary karate club, 230
New Delhi, 93, 94
NFA, 40, 41
node, 3
noisy channel, 129
null graph, 4, 248
Nuutila, Esko, 84
operations research, 38
order, 3
organism, 106, 110
orientation, 6, 21
probability, 91
oriented graph, 235
random, 235, 238
Ottawa, 93, 94
out-neighbor, 5, 60, 68, 72, 73
outdegree, 5
unweighted, 6, 7
overfull graph, 47
Oxley, James, 110
parallel forest-merging, 122
parallelization, 122
partition, 50
Pascal
formula, 167, 191
path, 11, 12, 104, 105
closed, 12
distance, 70
even, 12
geodesic, 13
graph, 34
Hamiltonian, 131
internally disjoint, 205
length, 70, 71, 105
odd, 12
shortest, 52, 7073, 75, 77, 79, 84
tree, 112, 113
weighted, 84
path graph, 16
pendant, 9, 113
perfect square, 106
Perkal, J., 122
permutation
equivalent, 23
random, 147
Peru, 93, 94
296
Index
regular graph, 9, 50
Petersen
graph, 37, 38, 68, 69, 202, 203
k-circulant, 50, 51, 242, 244
Julius, 68
r-regular, 9, 51
planar graph, 37, 48
relative complement, 33
plane, 102
remainder, 57
Pollak, O., 201
Renaissance, 37
postfix notation, 98
reservoir sampling, 255
power grid, 231
residual digraph, 225
preferential attachment, 247, 248, 251
residual network, 225
prefix-free condition, 129
reverse Polish notation, 98
Pregel River, 1
rich-get-richer effect, 248
Pretoria, 93, 94
river crossing problem, 97
Prim
Robertson, Neil, 36
algorithm, 116, 119121, 123, 144, 145, Robertson-Seymour theorem, 36
150, 152
Rogets Thesaurus, 242
R. C., 116, 119
root directory, 105
priority queue, 152, 153
root list, 168
probability, 136
Roy, Bernard, 79
expectation, 136
RSA, 150
sample space, 127
Runde, Volker, 71
space, 234
Russia, 1, 93, 94
pseudorandom number, 49, 238
Python, 17
saturated edge, 224
scale-free network, 251, 256, 257
queue, 59, 62, 65, 69, 73, 140
scatterplot, 2, 115, 133
dequeue, 60, 62, 140, 142
Schulz, Charles M., 189
end, 60
scientific collaboration, 232
enqueue, 60, 62, 140, 142
Sedgewick, Robert, 90, 95, 96, 101
front, 60
selection sort, 95, 96
length, 60
self-complementary graph, 33
minimum-priority, 84, 119, 137
self-loop, 4
priority, 137
separating set, 31, 207
rear, 60
set, 53
start, 60
n-set, 2
quicksort, 97
totally ordered, 153
Seymour
random graph, 229
Paul, 36, 203
Bernoulli, 234
Shannon
binomial, 234, 242
Claude E., 7, 110
Erdos-Renyi, 240
multigraphs, 7, 8
uniform, 240
switching game, 110, 111
weighted, 255
shellsort,
96
random variable
Shimbel, A., 76
geometric, 238
Shirali, Satish, 71
Rasmussen, Rune, 110
shortest path, 13
recurrence relation, 194, 195
recursion, 79, 110, 111, 122, 124, 136, 142, Simon, Herbert, 248
simple graph, 7, 147, 242
144, 145
random, 234, 239, 241, 242, 253, 254
regular expression, 41
Index
single-source shortest path, 72, 76
six degrees of separation, 242
size, 3
component, 256
tree, 111113
small-world, 51, 63, 244
algorithm, 244
characteristic path length, 244
clustering coefficient, 244, 246
effect, 241
experimental results, 243
network, 244
social network, 196
social network analysis, 37
South Africa, 93, 94
Spain, 93, 94
spanning forest, 122
spanning subgraph, 14
spanning tree, 37, 105, 107, 110, 115117,
145, 147, 151
maximum, 144
minimum, 115117, 119124, 145
randomized construction, 145, 146, 150
sparse graph, 237
stack, 65, 68, 69, 140
length, 65
pop, 65, 68, 140, 142, 144
push, 65, 68, 140, 142, 144
Stanley, Richard P., 65
star graph, 17
state, 39, 40
accepting, 39, 40
diagram, 39, 40
final, 39, 40, 97
initial, 39, 40, 97
Steinhaus, H., 122
Stevens, Brett, 101
Stinson, Douglas R., 95
string, 39, 129, 133
accepted, 41
empty, 137
Strogatz, Steven H., 242
subgraph, 10, 14
edge-deletion, 115, 116, 150
subtree, 110, 142
left, 126, 144
right, 126, 144
supergraph, 14
297
Swift, Jonathan, 57
Sydney, 93, 94
symbol, 133
symbolic computation, 97
symmetric difference, 28, 29
Szekeres, G., 203
Takaoka, Tadao, 191, 193
Tanner graph, 19, 20
Tarjan, Robert Endre, 63
Tarry, Gaston, 63
telegraph, 130
Thailand, 93, 94
The Brain puzzle, 131
Thoreau, Henry David, 7
threshold
probability, 91
Through the Looking Glass, 2
Tokyo, 93, 94
topology, 71
total order, 153
Tower of Hanoi puzzle, 131
trail, 11, 12
closed, 12
transition
function, 39, 40
table, 39
transitive closure, 83, 84
trapdoor function, 129
Trappe, Wade, 95
traveling salesman problem, 37, 52
traversal
bottom-up, 142, 143, 150
in-order, 142144, 150, 172
level-order, 139142, 150
post-order, 140, 142, 150
pre-order, 140, 141, 150
treasure map, 1
tree, 14, 59, 104, 105, 113
2-ary, 126
n-ary, 105
binary, 105, 135, 137, 142
complete, 105, 110
depth, 105
directed, 105
expression, 105, 106
height, 105
nonisomorphic, 105, 107, 108
298
ordered, 105, 139
recursive definition, 110, 111, 145
rooted, 14, 59, 68, 105, 109, 126
subtree, 111
traversal, 139, 141
triangle inequality, 70, 71, 86, 197
Tripathi, Amitabha, 24
trivial graph, 15, 105, 255
tuple, 2
union
digraph, 114, 115
union-find, 145
Unix, 105
unweighted degree, 7
USA, 93, 94, 231, 249
value of flow, 224
van Oorschot, Paul C., 95
Vandermonde
Alexandre-Theophile, 191
convolution, 191
Vanstone, Scott A., 95
Vasudeva, Harkrishan L., 71
vending machine, 3840
vertex, 3
adjacent, 3
child, 105, 109
cut, 31, 207
degree, 9
deletion, 30, 142
deletion subgraph, 30, 201
endpoint, 104, 105
head, 4
internal, 105, 205
isolated, 9, 53, 110
leaf, 104, 105, 134, 142
multigraph, 6
parent, 105
root, 14, 105, 107, 109, 134
set, 3
source, 73, 86
tail, 4
union, 28
vertex connectivity, 201
vertex-cut, 201
Vijay, Sujith, 24
Vitter
algorithm, 255
Index
Jeffrey Scott, 255
Vuillemin, Jean, 167
Wagner
conjecture, 36
Klaus, 36
walk, 11, 12
closed, 12
length, 11
trivial, 11
Walther, Hansjoachim, 37
Warshall, Stephen, 79, 84
Washington DC, 93, 94
Washington, Lawrence C., 95
Watanabe, Kohtaro, 144
Watts, Duncan J., 242
Watts-Strogatz model, 242, 244, 255
Wegener, Ingo, 65
weight, 69, 71, 79, 116
correcting, 71
function, 71, 85, 116
graph, 5
minimum, 75, 116, 119, 122
multigraph, 6
negative, 71, 72, 76, 77
nonnegative, 7073, 75, 84
path, 196
positive, 71
reweight, 84, 85
setting, 71
unit, 70, 71
Weinberger, A., 116
wheel graph, 28, 37, 151
Whitney
Hassler, 205
inequality, 204
theorem, 209
Wiener
Harold, 81, 148
number, 81, 150
Williams, J. W. J., 154
Wilson, Robin, 1
wine, 212, 213
word, 39, 133
World Wide Web, 248
Yamada, Takeo, 103, 144
Yegnanarayanan, V., 50
Yerger, Carl R., 151
Index
Zachary, Wayne W., 230
zero padding, 57
Zubrzycki, S., 122
Zwick, Uri, 193
299

Intro To Graph Theory

Uploaded by

Intro To Graph Theory

Uploaded by

Algorithmic Graph Theory

David Joyner, Minh Van Nguyen, Nathann Cohen

Copyright 2010 David Joyner <wdjoyner@gmail.com>

1 Introduction to Graph Theory

11 Graph Problems and Their LP

6 Optimal Graph Traversals

Spiked Math, http://spikedmath.com/120.html

Chapter 1. Introduction to Graph Theory

Figure 1.1: The seven bridges of Konigsberg puzzle.

Graphs and digraphs

The word graph is commonly understood to mean a visual representation of a dataset,

(a) Plots of functions.

Figure 1.2: Visual representations of datasets as plots.

1.1. Graphs and digraphs

Figure 1.3: A house graph.

Chapter 1. Introduction to Graph Theory

G . neighbors ( " a " )

1.1. Graphs and digraphs

Figure 1.4: A figure with a self-loop.

Chapter 1. Introduction to Graph Theory

Definition 1.5. For a weighted multigraph G, we are given:

Such a multigraph is denoted G = (V, E, i). An orientation on G is a function

Figure 1.5: An example of a weighted multigraph.

The unweighted outdegree of a vertex v V counts the edges going out of v:

1.1. Graphs and digraphs

Chapter 1. Introduction to Graph Theory

(a) Simple graph.

Figure 1.6: A simple graph, its digraph version, and a multidigraph.

Figure 1.7: The family of Shannon multigraphs Sh(n) for n = 2, . . . , 7.

1.1. Graphs and digraphs

So for the graph G in Figure 1.6, we have (G) = (G) = 2.

Proof. Each edge e = v1 v2 E is incident with two vertices, so e is counted twice

Chapter 1. Introduction to Graph Theory

which can be re-arranged as

deg(v) are both even, their difference is also even.

Subgraphs and other graph types

Walks, trails, and paths

1.2. Subgraphs and other graph types

Figure 1.8: Walking along a graph.

Chapter 1. Introduction to Graph Theory

Figure 1.9: Butterfly graph with 5 vertices.

1.2. Subgraphs and other graph types

Theorem 1.13. Every u-v walk in a graph contains a u-v path.

Chapter 1. Introduction to Graph Theory

Figure 1.10: A family tree.

Subgraphs, complete and bipartite graphs

Figure 1.11: A graph and one of its subgraphs.

1.2. Subgraphs and other graph types

We now consider several standard classes of graphs. The complete graph Kn on n

Figure 1.12: Complete graphs Kn for 1 n 5.

Chapter 1. Introduction to Graph Theory

Figure 1.13: Cycle graphs Cn for 3 n 6.

1.3. Representing graphs as matrices

Figure 1.14: Bipartite, complete bipartite, and star graphs.

Representing graphs as matrices

An m n matrix A can be represented as

a11 a12 a1n

Chapter 1. Introduction to Graph Theory

Figure 1.15: What are the adjacency matrices of these graphs?

1.3. Representing graphs as matrices

The corresponding graph is similar to that in Figure 1.16.

Chapter 1. Introduction to Graph Theory

Figure 1.16: A Tanner graph.

1.3. Representing graphs as matrices

matrix B = [bij ] defined by

An orientation of an undirected graph G is an assignment of direction to each edge of G.

The degree matrix of a graph G = (V, E) is an n n diagonal matrix D whose i-th

Chapter 1. Introduction to Graph Theory

Figure 1.17: Two representations of the Franklin graph.

Figure 1.18: Isomorphic and nonisomorphic graphs.

1.4. Isomorphic graphs

Two n n matrices A1 and A2 are permutation equivalent if there is a permutation

Chapter 1. Introduction to Graph Theory

Algorithm 1.1: Computing graph isomorphism using canonical labels.

The path Pn , for n 3, has the degree sequence

Let S be a non-increasing sequence of non-negative integers. Then S is said to be