# Lab 7: Autocomplete

You are not logged in.

Note that this link will take you to an external site (https://shimmer.mit.edu) to authenticate, and then you will be redirected back to this page.

## 1) Preparation§

This lab assumes you have Python 3.6 or later installed on your machine (3.9 recommended).

The following file contains code and other resources as a starting point for this lab: lab7.zip

Most of your changes should be made to lab.py, which you will submit at the end of this lab. Importantly, you should not add any imports to the file.

You can also see and participate in online discussion about this lab in the "Lab 7" Category in the forum.

This lab is worth a total of 4 points. Your score for the lab is based on:

• correctly answering the questions on thie page (0.5 points)
• passing the test cases from test.py under the time limit (1.5 points), and
• a brief "checkoff" conversation with a staff member to discuss your code (2 points).

Note that passing all of the tests on the server will require that your code runs reasonably efficiently.

Reminder: Collaboration Policy

Please also review the collaboration policy before continuing.

The questions below are all due at 5pm Eastern on Friday, 16 April. The checkoff is due at 10pm on Wednesday, 21 April.

## 2) Introduction§

Type "aren't you" into a search engine and you'll get a handful of search suggestions, ranging from "aren't you clever?" to "aren't you a little short for a stormtrooper?". If you've ever done a web search, you've probably seen an autocompletion — a handy list of words that pops up under your search, guessing at what you were about to type.

Search engines aren't the only place you'll find this mechanism. Cell phones use autocomplete/autocorrect to predict/correct words that are entered for, for example, text messages. Some IDEs (integrated development environments - used for coding / software development) use autocomplete to make the process of coding more efficient by offering suggestions for completing long function or variable names.

In this lab, we are going to implement our own version of an autocomplete/autocorrect engine using a tree structure called a trie, as described in this document.

The lab will ask you first to create a class to represent a generic trie data structure. You will then use the trie to write your own autocomplete and autocorrect, as well as a mechanism for searching.

Note

At several points throughout this lab, you will be asked to write some test cases of your own using doctests. We strongly encourage you to try writing those tests before implementing the associated behavior (by thinking through what the output should be on some small examples), so that you can use them to help with testing and debugging when you are ready to implement the associated functionality.

Of course, if you have trouble thinking about how to structure your test cases, what test cases might be useful, etc, please don't hesitate to ask for help!

### 2.1) The Trie Data Structure§

A trie1, also known as a prefix tree, is a type of search tree that stores an associative array (a mapping from keys to values). In a trie, the keys are always ordered sequences. The trie stores keys organized by their prefixes (their first characters), with longer prefixes given by successive levels of the trie. Each node optionally contains a value to be associated with that node's prefix.

As an example, consider a trie constructed as follows:

t = Trie()
t['bat'] = 7
t['bar'] = 3
t['bark'] = ':)'


This trie would look like the following (Fig. 1).

Placeholder for Diagram 24d837d3835052ca35fb0966da1a4c89
Fig. 1

Two important things to notice here:

1. There is no single object that represents the whole structure of this trie. Rather, each node in the diagram above is represented by a single Trie instance.

2. The keys associated with each node are not actually stored in the nodes themselves. Rather, they are associated with the edges connecting the nodes.

We'll start by implementing a class called Trie to represent tries in Python. This class will include facilities for adding, deleting, modifying, and iterating over key/value pairs. For example, consider the following example (noting that the argument we provide when first creating the Trie object is the type of its keys (see the description of __init__ below for more information)):

>>> t = Trie(str)
>>> t['bat'] = True
>>> t['bar'] = True
>>> t['bark'] = True
>>>
>>> t['bat']
True
>>> t['something']
Traceback (most recent call last):
...
KeyError
>>>
>>> t['bark'] = 20
>>> t['bark']
20
>>>
>>> for i in t:
print(i)

('bat', True)
('bar', True)
('bark', 20)
>>>
>>> del t['bar']
>>>
>>> for i in t:
print(i)

('bat', True)
('bark', 20)


Note that we are not limited to using only strings as keys. We'll want to set things up so that we can also use, for example, tuples as keys, as in the example below:

>>> t = Trie(tuple)
>>> t[2, ] = 'cat'
>>> t[1, 0, 0] = 'dog'
>>> t[1, 0, 1] = 'ferret'
>>> t[1, 0, 1, 80] = 'tomato'
>>>
>>> t[1, 0]
Traceback (most recent call last):
...
KeyError
>>> t[1, 0, 0]
'dog'
>>> for i in t:
print(i)

((2,), 'cat')
((1, 0, 0), 'dog')
((1, 0, 1), 'ferret')
((1, 0, 1, 80), 'tomato')


Note that, in terms of interface and functionality, the Trie class will have a lot in common with a Python dictionary. However, the representation we're using "under the hood" has some nice features that make it particularly well-suited for tasks (like autocompletion) that use prefix-based lookups.

We will only test your code using strings and tuples, but you may be interested to see if you can make it work with other types as well!

## 3) Trie class and basic methods§

In lab.py, you are responsible for implementing the Trie class, which should support the following methods.

__init__( self, key_type )

The __init__ method should take in a single argument representing the type of the keys to be used in this trie. This will be specified as a Python type object (like str or tuple), rather than with any particular object of that type.

An example of such a type would be str. Note that str, which represents the built-in string type, is a first-class object that we can make use of as we would any other object; and that, generally speaking, we can make "empty" instances of string by calling str with no arguments: str(). This generally works for other types as well.

Check Yourself:

Try playing around with various type objects in a Python REPL. What kinds of objects are created when you call int(), str(), tuple(), list(), or similar? What if you alias str to a different name, like foo = str? Does that allow using foo() instead of str()?

Try experimenting with some of these things, and feel free to ask if you're confused by the results!

Ultimately, the __init__ method should set up exactly three instance variables:

• value, the value associated with the sequence ending at this node. Initial value is None (we will assume that a value of None means that a given key has no value associated with it, not that the value None is associated with it).

• key_type, some way to keep track of the type of the keys (without explicitly storing the entire keys themselves). The exact choice of representation is up to you.

• children, a dictionary mapping a single-element sequence (in our case, either a length-1 string or a length-1 tuple, depending on the key_type) to another trie node, i.e., the next level of the trie hierarchy (tries are a recursive data structure). Initial value is an empty dictionary.

How many Trie instances comprise the example trie structure in the drawing above (Figure 1)?
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

The top node in Figure 1 is represented by a Trie instance, let's call it t. In that case, t.children represents a dictionary. What are the keys in this dictionary? Enter a list or tuple containing all of the keys:
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

What is the type of the values in the t.children dictionary?
 str list tuple dict Trie something else
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

__setitem__( self, key, value )

Add the given key to the trie, associating it with the given value. For the trie node that marks the end of the key, set that node's value attribute to be given value argument. This method doesn't return a value. This is a special method name used by Python to implement subscript assignment. For example, x[k] = v is translated by Python into x.__setitem__(k, v). If the type of the key is not consistent with the key type expected for the trie, a TypeError exception should be raised (see https://docs.python.org/3/reference/simple_stmts.html#raise).

Examples (using the trie structure from the picture above (Figure 1)):

• t = Trie(str) would create the root node of the example trie above.

• t['bat'] = 7 adds three nodes (representing the 'b', 'ba', and 'bat' prefixes) and associates the value 7 with the node corresponding to 'bat'.

• t['bark'] = ':)' adds two new nodes for prefixes 'bar' and 'bark' shown on the bottom right of the trie, setting the value of the last node to ':)'.

• t['bar'] = 3 doesn't add any nodes and only sets the value of the first node added above when inserting "bark" to 3.

• t[1] = True raises a TypeError (because the given key is not of the appropriate type) and does not make any change to the trie.

Continuing the example from above, how many new Trie instances will be created if we execute t['bank'] = 4?
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

If we then run t['ban'] = 7, how many new Trie instances will be created?
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

__getitem__( self, key )

Return the value associated with the given key. This is a special method name used by Python to implement subscripting (indexing). For example, x[k] is translated by Python into x.__getitem__(k). Your code should find the corresponding node for the given key, and return the associated value. You should raise a KeyError if the key cannot be found in the trie. If the type of the key is not consistent with the expected type of keys for this trie, raise a TypeError instead.

Examples (using the first example trie from above):

• t['bark'] should return ':)'.

• t['apple'] should raise a KeyError since the given key does not exist in the trie.

• t['ba'] should also raise a KeyError since, even though the key 'ba' is represented in the trie, it has no value associated with it.

• t[1] should raise a TypeError since the keys for this trie are expected to be strings, not integers.

Check Yourself:

Add some doctests to the docstring for __getitem__ to test that it is working as expected.

__delitem__( self, key )

Disassociate the given key from its value. This is a special method name used by Python to implement index deletion. For example, del x[k] is translated by Python into x.__delitem__(k). Trying to delete a key that has no associated value should raise a KeyError, and trying to delete a key of the wrong type should raise a TypeError.

Examples (using the example trie from above):

• del t["bar"] should disassociate "bar" from its value in the trie, so that subsequent lookups of t["bar"] produce a KeyError.

• del t["foo"] should raise a KeyError since "foo" does not exist as a key in the example trie.

For the purposes of this lab, you only need to do the bare minimum so that the key is no longer associated with a value (don't worry about extra memory usage after deleting the key). As an interesting optional feature (and a nice improvement to the structure), you could also try removing all unnecessary nodes from the trie structure.

Check Yourself:

Add some doctests to the docstring for __delitem__ to make sure it is working as expected.

__contains__( self, key )

Return True if key occurs and has a value other than None in the trie. __contains__ is the special method name used by Python to implement the in operator. For example,

k in x


is translated to

x.__contains__(k)


Hint: At first glance, the code for this method might look very similar to some of the other methods above. Make good use of helper functions to avoid repetitious code!

What should be the result of evaluating 'bar' in t, using the example trie from above?
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

What should be the result of evaluating 'barking' in t, using the example trie from above?
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

What should be the result of evaluating 'ba' in t, using the example trie from above?
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

Check Yourself:

Add some doctests to the docstring for __contains__ to make sure it is working as expected.

__iter__( self )

__iter__ should be a generator that yields (key, value) tuples for each key stored in the trie. The pairs can be produced in any order. __iter__ is the special method name used by Python when it needs to iterate over a data object, i.e., the method invoked by the iter() built-in function. For example, the following Python code will print all the keys in a trie:

for key, val in t:
print(key)


You should do this without first making a list or other structure that contains the items in the trie.

Hint: You'll want to return a recursive generator function that uses yield (and maybe yield from) to produce the required sequence of values one at a time. See https://docs.python.org/3/howto/functional.html#generators and/or https://docs.python.org/3/whatsnew/3.3.html#pep-380, and/or the week 5 and 8 lecture videos.

Examples (using the example trie from above):

• The example above prints bat, bar, and bark on three separate lines.

• list(t) returns [('bat', 7), ('bar', 3), ('bark', ':)')] (but not necessarily in that order). Note that the list function has an internal for loop that uses iter(t) to iterate over each element of the sequence t.

## 4) Autocomplete§

Now that we've implemented the skeleton of the trie structure itself, let's implement our auto-complete engine!

We'll start with implementing autocompletion for words, and then we'll move to implementing autocompletion for sentences. As a start for either of these, we'll need a way to build up a Trie instance from a text document. To this end, we'll implement the following two helper functions:

make_word_trie(text)

text is a string containing a body of text. Return a Trie instance mapping words in the text to the frequency with which they occur in the given piece of text.

Note that we have provided a method called tokenize_sentences which will try to intelligently split a piece of text into individual sentences. You should use this function rather than implementing your own. The function takes in a single string and returns a list of strings, one for each sentence, where punctuation has been stripped out and the sentence consists only of words. Words within those sentences are sequences of characters separated by spaces.

make_phrase_trie(text)

text is a string containing a body of text. Return a Trie instance mapping sentences (represented as tuples of words) to the frequency with which they occur in the given piece of text.

Check Yourself:

Add some doctests to the docstrings for make_word_trie and make_phrase_trie, including at least one example of your own devising for each function.

As a running example, we'll use the following trie (Fig. 2), which could have been created by calling make_word_trie("bat bat bark bar").

Placeholder for Diagram ed0229eac3b017728a9762c0e00bb502
Fig. 2

Once we have those trie representations, we are ready to go ahead and implement autocompletion! We'll implement autocompletion as a function described below:

autocomplete( trie, prefix, max_count=None )

trie is an instance of Trie, prefix is a string/tuple, max_count is an integer or None. Return a list of the max_count most-frequently-occurring keys that start with prefix. In the case of a tie, you may output any of the most-frequently-occurring keys. If there are fewer than max_count valid keys available starting with prefix, return only as many as there are. The returned list may be in any order. If max_count is not specified, your list should contain all keys that start with prefix.

Return [] if prefix is not in the trie. Raise a TypeError if the given prefix has the wrong type.

If t refers to the example trie structure in Figure 2, what should be the result of evaluating the following Python expression?

autocomplete(t, "ba", 1)

This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

With that same example trie, there are multiple possible correct ways that the following expression could be evaluated:
autocomplete(t, "ba", 2)


Enter any one such valid result in the box below:

This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

Using the same example trie, what should be the result of evaluating the following?

autocomplete(t, "be", 2)

This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

Your implementation should be agnostic to the type of its inputs (i.e., it should work on tries/prefixes that are either strings or tuples).

Importantly, the structure of the trie should allow us to implement autocomplete efficiently, without needing to consider all of the values in the entire trie.

Check Yourself:

Write a few small tests of your own (as doctests in autocomplete's doctsring) to test this behavior. You may include the above examples as test cases, but you should also include at least 1 non-trivial test case of your own devising.

## 5) Autocorrect§

You may have noticed that for some words, our autocomplete implementation generates very few or no suggestions. In cases such as these, we may want to guess that the user mistyped something in the original word. We ask you to implement a more sophisticated tool: autocorrect.

In this case, we will only concern ourselves with tries that are made up of words (i.e., we won't concern ourselves with tuples in this case).

autocorrect( trie, prefix, max_count=None )

trie is an instance of Trie whose keys are strings, prefix is a string, max_count is an integer or None; returns a list of up to max_count words. autocorrect should invoke autocomplete, but if fewer than max_count completions are made, suggest additional words by applying one valid edit to the prefix.

An edit for a word can be any one of the following:

• A single-character insertion (add any one character in the range "a" to "z" at any place in the word)
• A single-character deletion (remove any one character from the word)
• A single-character replacement (replace any one character in the word with a character in the range a-z)
• A two-character transpose (switch the positions of any two adjacent characters in the word)

A valid edit is an edit that results in a word in the trie without considering any suffix characters. In other words we don't try to autocomplete valid edits, we just check if edit in trie is True.

For example, editing "te" to "the" is valid, but editing "te" to "tze" is not, as "tze" isn't a word. Likewise, editing "phe" to "the" is valid, but "phe" to "pho" is not because "pho" is not a word in the corpus, although many words beginning with "pho" are.

In summary, given a prefix that produces C completions, where C < max_count, generate up to max_count - C additional words by considering all valid single edits of that prefix (i.e., corpus words that can be generated by 1 edit of the original prefix) and selecting the most-frequently-occurring edited words. Return a list of suggestions produced by including all C of the completions and up to max_count - C of the most-frequently-occuring valid edits of the prefix; the list may be in any order. Be careful not to repeat suggested words!

If max_count is None (or is unspecified), autocorrect should return all autocompletions as well as all valid edits.

Example (using the example trie from above):

• autocorrect(t, "bar", 3) returns ['bar', 'bark', 'bat'] since "bar" and "bark" are found by autocomplete and "bat" is valid edit involving a single-character replacement, i.e., "t" is replacing the "r" in "bar".
Check Yourself:

Write a few small tests of your own (as doctests in autocorrect's doctsring) to test this behavior. You may include the above examples as test cases, but you should also include at least 1 non-trivial test case of your own devising.

## 6) Selecting words from a word trie§

It's sometimes useful to select only the words from a trie that match a pattern. That's the purpose of the word_filter method.

word_filter( trie, pattern )

trie is a trie whose keys are strings, and pattern is a string. Return a list of (word, freq) tuples for those words whose characters match those of pattern. The characters in pattern are matched one-at-a-time with the characters in each word stored in the trie. If all the characters in a particular word are matched, the (word, freq) pair should be included in the list to be returned. The list can be in any order.

The characters in pattern are interpreted as follows:

• '*' matches a sequence of zero or more of the next unmatched characters in word.

• '?' matches the next unmatched character in word no matter what it is. There must be a next unmatched character for '?' to match.

• otherwise the character in the pattern must exactly match the next unmatched character in the word.

Note that the characters replaced by * and ? can be arbitrary characters, not just letters.

Pattern examples:

• "*a*t" matches all words that contain an "a" and end in "t." This would include words like "at", "art", "saint", and "what."
• "year*" would match "year," "years," and "yearn," among others (as well as longer words like "yearning").
• "year?" would match "years," and "yearn" (but not longer words).
• "*ing" matches all words ending in "ing."
• "???" would match all 3-letter words.
• "?ing" matches all 4-letter words ending in "ing."
• "?*ing" matches all words with 4 or more letters that end in "ing."

Filter examples (using the example trie from above):

• word_filter(t, "*") returns [('bat', 2), ('bar', 1), ('bark', 1)], i.e., listing all the words in the trie.

• word_filter(t, "???") returns [('bat', 2), ('bar', 1)], i.e., listing all the 3-letter words in the trie.

• word_filter(t, "*r*") returns [('bar', 1), ('bark', 1)], i.e., listing all the words containing an "r" in any position.

Hint: the matching operation can implemented as a recursive search function that attempts to match the next character in the pattern with some number of characters at the beginning of the word, then recursively matches the remaining characters in the pattern with remaining unmatched characters in the word. You should not use a "brute-force" method that involves generating and/or looping over all words in the trie.

Note

You cannot use any of the built-in Python pattern-matching functions, e.g., functions from the re module — you are expected to write your own pattern-matching code. Copying or referencing code from StackOverflow or other sources is also not appropriate.

Check Yourself:

Write a few small tests of your own (as doctests in word_filter's doctsring) to test this behavior. You may include the above examples as test cases, but you should also include at least 1 non-trivial test case of your own devising.

As in the previous labs, we provide you with a test.py script to help you verify the correctness of your code. In addition to the test cases for this week's lab, we'll have you test out your code by running it on several examples of real public-domain books (courtesy of Project Gutenberg).

Download the following text files (each of which contains a whole book) to the same directory as your lab.py (by right-clicking the link and then clicking "Save As" or similar):

You can load the text of any of these files using something like the following code:

with open("filename.txt", encoding="utf-8") as f:


After running this code, the variable text will be bound to a string containing the text contained in the filename.txt file.

We'll read the contents of these files into Python, use our make_word_trie and make_phrase_trie functions to create the relevant trie structures, and use our autocompletion/autocorrection based on those corpora. Use these tools to answer the following questions and be prepared to discuss how you used your Trie structure to answer these questions during the checkoff.

In Alice's Adventures in Wonderland, what are the six most common sentences (regardless of prefix)? Enter your answer as a Python list of tuples:
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

In Metamorphosis, what are the six most common words starting with gre? Enter your answer as a Python list of strings:
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

In Metamorphosis, what are all of the words matching the pattern c*h, along with their counts? Enter your answer as a Python list of tuples, of the same form as your output from word_filter:
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

In A Tale of Two Cities, what are all of the words matching the pattern r?c*t, along with their counts? Enter your answer as a Python list of tuples, of the same form as your output from word_filter:
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

What are the top 12 autocorrections for 'hear' in Alice in Wonderland? Enter your answer as a Python list of strings:
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

What are all autocorrections for 'hear' in Pride and Prejudice? Enter your answer as a Python list of strings:
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

How many distinct words are in Dracula?
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

How many total words are in Dracula?
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

How many distinct sentences are in Alice's Adventures in Wonderland?
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

How many total sentences are in Alice's Adventures in Wonderland?
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

## 8) Code Submission§

No file selected
This question is due on Friday April 16, 2021 at 05:00:00 PM Eastern time.

## 9) Checkoff§

Once you are finished with the code, please come to a office hours and add yourself to the queue asking for a checkoff. You must be ready to discuss your code and test cases in detail before asking for a checkoff.

You should be prepared to demonstrate your code (which should be well-commented, should avoid repetition, and should make good use of helper functions). In particular, be prepared to discuss:

• how you were able to keep track of the prefix associated with each node without explicitly storing the prefix itself
• the tradeoff between using iteration and recursion when implementing the __getitem__ method.
• how you created a generator when implementing the __iter__ method without first creating some other structure to store the items. Did you use yield from?
• how using your other methods would simplify the implementation of autocomplete
• how your code for creating edits works.
• how your recursive matching works (without enumerating all words) for the filter implementation.
• how you used your Trie structure to answer the questions at the bottom of the page.
• the new test cases you created to test the functionalities throughout the lab.