This section provides practice in the use of list structure and data
abstraction to manipulate sets and trees. The application is to
methods for representing data as sequences of ones and zeros (bits).
For example, the
ASCII standard code used to represent text in
computers encodes each
character as a sequence of seven bits. Using
seven bits allows us to distinguish $2^7$, or
128, possible different characters. In general, if we want to distinguish
$n$ different symbols, we will need to use
$\log_2 n$ bits per symbol. If all our messages
are made up of the eight symbols A, B, C, D, E, F, G, and H, we can choose
a code with three bits per character, for example
Codes such as ASCII and the A-through-H code above are known as
fixed-length codes, because they represent each symbol in the
message with the same number of bits. It is sometimes advantageous to use
variable-length codes, in which different symbols may be
represented by different numbers of bits. For example,
Morse code does not use the same number of dots and dashes for each letter
of the alphabet. In particular, E, the most frequent letter, is represented
by a single dot. In general, if our messages are such that some symbols
appear very frequently and some very rarely, we can encode data more
efficiently (i.e., using fewer bits per message) if we assign shorter
codes to the frequent symbols. Consider the following alternative code for
the letters A through H:
A
0
C
1010
E
1100
G
1110
B
100
D
1011
F
1101
H
1111
With this code, the same message as above is encoded as the string
100010100101101100011010100100000111001111
This string contains 42 bits, so it saves more than 20% in space in
comparison with the fixed-length code shown above.
One of the difficulties of using a variable-length code is knowing
when you have reached the end of a symbol in reading a sequence of
zeros and ones. Morse code solves this problem by using a special
separator code (in this case, a pause) after the sequence of
dots and dashes for each letter. Another solution is to design the
code in such a way that no complete code for any symbol is the
beginning (or prefix) of the code for another symbol. Such a
code is called a
prefix code. In the example above, A is encoded by 0 and B is
encoded by 100, so no other symbol can have a code that begins with 0 or
with 100.
In general, we can attain significant savings if we use
variable-length prefix codes that take advantage of the relative
frequencies of the symbols in the messages to be encoded. One
particular scheme for doing this is called the Huffman encoding
method, after its discoverer,
David Huffman. A Huffman code can be represented as a
binary tree whose leaves are the symbols that are encoded. At each
non-leaf node of the tree there is a set containing all the symbols in the
leaves that lie below the node. In addition, each symbol at a leaf is
assigned a weight (which is its relative frequency), and each non-leaf
node contains a weight that is the sum of all the weights of the leaves
lying below it. The weights are not used in the encoding or the decoding
process. We will see below how they are used to help construct the tree.
Figure 2.24 shows the Huffman tree for the
A-through-H code given above. The weights at the leaves indicate that the
tree was designed for messages in which A appears with relative frequency
8, B with relative frequency 3, and the other letters each with relative
frequency 1.
Given a Huffman tree, we can find the encoding of any symbol by
starting at the root and moving down until we reach the leaf that
holds the symbol. Each time we move down a left branch we add a 0 to
the code, and each time we move down a right branch we add a 1. (We
decide which branch to follow by testing to see which branch either is
the leaf node for the symbol or contains the symbol in its set.) For
example, starting from the root of the tree in
figure 2.24, we arrive at the leaf for D by
following a right branch, then a left branch, then a right branch, then a
right branch; hence, the code for D is 1011.
To decode a bit sequence using a Huffman tree, we begin at the root
and use the successive zeros and ones of the bit sequence to determine
whether to move down the left or the right branch. Each time we come
to a leaf, we have generated a new symbol in the message, at which
point we start over from the root of the tree to find the next symbol.
For example, suppose we are given the tree above and the sequence
10001010. Starting at the root, we move down the right branch (since
the first bit of the string is 1), then down the left branch (since
the second bit is 0), then down the left branch (since the third bit
is also 0). This brings us to the leaf for B, so the first
symbol of the decoded message is B. Now we start again at the root,
and we make a left move because the next bit in the string is 0.
This brings us to the leaf for A. Then we start again at the root
with the rest of the string 1010, so we move right, left, right, left and
reach C. Thus, the entire message is BAC.
Generating Huffman trees
Given an alphabet of symbols and their relative frequencies,
how do we construct the best code? (In other words, which
tree will encode messages with the fewest bits?) Huffman gave an algorithm
for doing this and showed that the resulting code is indeed the best
variable-length code for messages where the relative frequency of the
symbols matches the frequencies with which the code was constructed.
We will not prove this optimality of Huffman codes here, but we will
show how Huffman trees are constructed.[1]
The algorithm for generating a Huffman tree is very simple. The idea
is to arrange the tree so that the symbols with the lowest frequency
appear farthest away from the root. Begin with the set of leaf nodes,
containing symbols and their frequencies, as determined by the initial data
from which the code is to be constructed. Now find two leaves with
the lowest weights and merge them to produce a node that has these
two nodes as its left and right branches. The weight of the new node
is the sum of the two weights. Remove the two leaves from the
original set and replace them by this new node. Now continue this
process. At each step, merge two nodes with the smallest weights,
removing them from the set and replacing them with a node that has
these two as its left and right branches. The process stops when
there is only one node left, which is the root of the entire tree.
Here is how the Huffman tree of figure 2.24 was
generated:
$\{$(A 8) (B 3) ($\{$C D$\}$ 2) ($\{$E F G H$\}$ 4)$\}$
Merge
$\{$(A 8) ($\{$B C D$\}$ 5) ($\{$E F G H$\}$ 4)$\}$
Merge
$\{$(A 8) ($\{$B C D E F G H$\}$ 9)$\}$
Final merge
$\{$($\{$A B C D E F G H$\}$ 17)$\}$
The algorithm does not always specify a unique tree, because there may
not be unique smallest-weight nodes at each step. Also, the choice of
the order in which the two nodes are merged (i.e., which will be the
right branch and which will be the left branch) is arbitrary.
Representing Huffman trees
In the exercises below we will work with a system that uses
Huffman trees to encode and decode messages and generates Huffman
trees according to the algorithm outlined above. We will begin by
discussing how trees are represented.
Leaves of the tree are represented by a list consisting of the
symbol leaf,string "leaf",
the symbol at the leaf, and the weight:
function make_leaf(symbol, weight) {
return list("leaf", symbol, weight);
}
function is_leaf(object) {
return head(object) === "leaf";
}
function symbol_leaf(x) { return head(tail(x)); }
function weight_leaf(x) { return head(tail(tail(x))); }
A general tree will be a list of
a string "code_tree",
a left branch, a right branch, a set
of symbols, and a weight. The set of symbols will be simply a list of
the symbols, rather than some more sophisticated set representation.
When we make a tree by merging two nodes, we obtain the weight of the
tree as the sum of the weights of the nodes, and the set of symbols as
the union of the sets of symbols for the nodes. Since our symbol sets are
represented as lists, we can form the union by using the
appendprocedurefunction
we defined in section 2.2.1:
Original
JavaScript
(define (make-code-tree left right)
(list left
right
(append (symbols left) (symbols right))
(+ (weight left) (weight right))))
function left_branch(tree) { return head(tail(tree)); }
function right_branch(tree) { return head(tail(tail(tree))); }
function symbols(tree) {
return is_leaf(tree)
? list(symbol_leaf(tree))
: head(tail(tail(tail(tree))));
}
function weight(tree) {
return is_leaf(tree)
? weight_leaf(tree)
: head(tail(tail(tail(tail(tree)))));
}
The
proceduresfunctionssymbols and
weight must do something slightly different
depending on whether they are called with a leaf or a general tree.
These are simple examples of
generic
proceduresfunctions(procedures(functions
that can handle more than one kind of data), which we will have much more
to say about in sections 2.4
and 2.5.
The decoding
procedurefunction
The following
procedurefunction
implements the decoding algorithm. It takes as arguments a list of zeros
and ones, together with a Huffman tree.
function decode(bits, tree) {
function decode_1(bits, current_branch) {
if (is_null(bits)) {
return null;
} else {
const next_branch = choose_branch(head(bits),
current_branch);
return is_leaf(next_branch)
? pair(symbol_leaf(next_branch),
decode_1(tail(bits), tree))
: decode_1(tail(bits), next_branch);
}
}
return decode_1(bits, tree);
}
function choose_branch(bit, branch) {
return bit === 0
? left_branch(branch)
: bit === 1
? right_branch(branch)
: error(bit, "bad bit -- choose_branch");
}
The
procedurefunctiondecode-1decode_1
takes two arguments: the list of remaining bits and the current position in
the tree. It keeps moving down the tree, choosing a left or
a right branch according to whether the next bit in the list is a zero or a
one. (This is done with the
procedurefunctionchoose-branch.)choose_branch.)
When it reaches a leaf, it returns the symbol at that leaf as the next
symbol in the message by
consing
it onto the result of decoding the rest of the message,
starting at the root of the tree.
adjoining
it to the result of decoding the rest of the message,
starting at the root of the tree.
Note the error check in the final clause of
choose-branch,choose_branch,
which complains if the
procedurefunction
finds something other than a zero or a one in the input data.
Sets of weighted elements
In our representation of trees, each non-leaf node contains a set of
symbols, which we have represented as a simple list. However, the
tree-generating algorithm discussed above requires that we also work
with sets of leaves and trees, successively merging the two smallest
items. Since we will be required to repeatedly find the smallest item
in a set, it is convenient to use an ordered representation for this
kind of set.
We will represent a set of leaves and trees as a list of elements,
arranged in increasing order of weight.
The following
adjoin-setadjoin_setprocedurefunction
for constructing sets is similar to the one
described in exercise 2.65; however, items
are compared by their weights, and the element being added to the set is
never already in it.
Original
JavaScript
(define (adjoin-set x set)
(cond ((null? set) (list x))
((< (weight x) (weight (car set))) (cons x set))
(else (cons (car set)
(adjoin-set x (cdr set))))))
The following
procedurefunction
takes a list of symbol-frequency pairs such as
((A 4) (B 2) (C 1) (D 1))
list(list("A", 4), list("B", 2), list("C", 1), list("D", 1))
and constructs an initial ordered set of leaves, ready to be merged
according to the Huffman algorithm:
Encode-symbol is a procedure,
which you must write, that returns the list of bits that encodes a given
symbol according to a given tree.
The function encode_symbol,
which you must write, returns the list of bits that encodes a given symbol
according to
a given tree.
You should design
encode-symbolencode_symbol
so that it signals an error if the symbol is not in the tree at all.
Test your
procedurefunction
by encoding the result you obtained in
exercise 2.71 with the sample tree and
seeing whether it is the same as the original sample message.
Exercise 2.73
The following
procedurefunction
takes as its argument a list of symbol-frequency pairs (where no symbol
appears in more than one pair) and generates a Huffman encoding tree
according to the Huffman algorithm.
function generate_huffman_tree(pairs) {
return successive_merge(make_leaf_set(pairs));
}
Original
JavaScript
Make-leaf-set is the procedure
given above that transforms the
list of pairs into an ordered set of leaves.
Successive-merge
is the procedure
you must write, using make-code-tree to
successively merge the smallest-weight elements of the set until there
is only one element left, which is the desired Huffman tree.
The function make_leaf_set
that transforms the list of pairs into an ordered set of leaves is
given above. Write the function
successive_merge using
make_code_tree to successively
merge the smallest-weight elements of the set until there is only one
element left, which is the desired Huffman tree.
(This
procedurefunction
is slightly tricky, but not really complicated. If you find yourself
designing a complex
procedure,function,
then you are almost certainly doing something wrong. You can take
significant advantage of the fact that we are using an ordered set
representation.)
Exercise 2.74
The following eight-symbol alphabet with associated relative
frequencies was designed to efficiently encode the lyrics of 1950s
rock songs. (Note that the symbols of an
alphabet need not be individual letters.)
Original
JavaScript
A
2
NA
16
BOOM
1
SHA
3
GET
2
YIP
9
JOB
2
WAH
1
Use
generate-huffman-treegenerate_huffman_tree
(exercise 2.73) to generate a
corresponding Huffman tree, and use encode
(exercise 2.72) to encode the following
message:
Get a job
Sha na na na na na na na na
Get a job
Sha na na na na na na na na
Wah yip yip yip yip yip yip yip yip yip
Sha boom
How many bits are required for the encoding? What is the smallest number
of bits that would be needed to encode this song if we used a fixed-length
code for the eight-symbol alphabet?
const lyrics_frequencies =
list(list("A", 2),
list("NA", 16),
list("BOOM", 1),
list("SHA", 3),
list("GET", 2),
list("YIP", 9),
list("JOB", 2),
list("WAH", 2));
const lyrics_tree = generate_huffman_tree(lyrics_frequencies);
const lyrics = list(
'GET', 'A', 'JOB',
'SHA', 'NA', 'NA', 'NA', 'NA', 'NA', 'NA', 'NA', 'NA',
'GET', 'A', 'JOB', 'SHA', 'NA', 'NA', 'NA', 'NA', 'NA',
'NA', 'NA', 'NA', 'WAH', 'YIP', 'YIP', 'YIP', 'YIP',
'YIP', 'YIP', 'YIP', 'YIP', 'YIP', 'SHA', 'BOOM'
);
length(encode(lyrics, lyrics_tree));
// 84
We have an alphabet of $n = 8$ symbols, and a
message of $m = 36$ symbols. Then the minimum
number of bits to encode a specific symbol using a fixed-length code is
$\lceil \log_2{n} \rceil = 3$. Thus the minimum
number of bits to encode all the lyrics is
$m \lceil\log_2{n}\rceil = 36 \times 3 = 108$.
Exercise 2.75
Suppose we have a Huffman tree for an alphabet of
$n$ symbols, and that the relative frequencies
of the symbols are 1, 2, 4, …,
$2^{n-1}$. Sketch the tree for
$n$=5; for $n$=10.
In such a tree (for general $n$) how may bits
are required to encode the most frequent symbol? the least frequent symbol?
The tree will be unbalanced, similar to the tree given in
figure . Encoding the most
frequent symbol requires one bit, whereas
$n - 1$ bits are required to encode the
least frequent symbol.
Exercise 2.76
Consider the encoding
procedurefunction
that you designed in exercise 2.72. What
is the
order of growth in the number of steps needed to encode a symbol?
Be sure to include the number of steps needed to search the symbol list at
each node encountered. To answer this question in general is difficult.
Consider the special case where the relative frequencies of the
$n$ symbols are as described in
exercise 2.75, and give the order of
growth (as a function of $n$) of the number of
steps needed to encode the most frequent and least frequent symbols in the
alphabet.
Consider the special case in
exercise 2.72. At each step down the path
of length $n$, we need to do a linear search in
a list of length $n, n-1, \ldots, 1$. In the
worst case, there are
$O(n \times n / 2) = O(n^2)$ number of steps.
$O(n^2)$.
[1]
See
Hamming 1980
for a discussion of the mathematical properties of Huffman codes.