=========== this definition by Mark & Ceal Wutka, link below ============
A Directed Acyclic Word Graph, or DAWG, is a data structure that permits extremely fast word searches. The entry point into the graph represents the starting letter in the search. Each node represents a letter, and you can travel from the node to two other nodes, depending on whether you the letter matches the one you are searching for.
It's a Directed graph because you can only move in a specific direction between two nodes. In other words, you can move from A to B, but you can't move from B to A. It's Acyclic because there are no cycles. You cannot have a path from A to B to C and then back to A. The link back to A would create a cycle, and probably an endless loop in your search program.
The description is a little confusing without an example, so imagine we have a DAWG containing the words CAT, CAN, DO, and DOG. The graph woud look like this:
C --Child--> A --Child--> N (EOW)
| T (EOW)
D--Child--> O (EOW) --Child --> G (EOW)
Now, imagine that we want to see if CAT is in the DAWG. We start at the entry point (the C) in this case. Since C is also the letter we are looking for, we go to the child node of C. Now we are looking for the next letter in CAT, which is A. Again, the node we are on (A) has the letter we are looking for, so we again pick the child node which is now N. Since we are looking for T and the current node is not T, we take the Next node instead of the child. The Next node of N is T. T has the letter we want. Now, since we have processed all the letters in the word we are searching for, we need to make sure that the current node has an End-of-word flag (EOW) which it does, so CAT is stored in the graph.
One of the tricks with making a DAWG is trimming it down so that words with common endings all end at the same node. For example, suppose we want to store DOG and LOG in a DAWG. The ideal would be something like this:
D --Child--> O --Child--> G(EOW)
In other words, the OG in DOG and LOG is defined by the same pair of nodes.
=========== Creating a DAWG ============
[...] The idea is to first create a tree, where a leaf would represent the end of a word and there can be multiple leaves that are identical. For example, DOG and LOG would be stored like this:
D --Child--> O --Child--> G (EOW)
L --Child-> O --Child--> G (EOW)
Now, suppose you want to add DOGMA to the tree. You'd proceed as if you were doing a search. Once you get to G, you find it has no children, so you add a child M, and then add a child A to the M, making the graph look like:
D --Child--> O --Child--> G (EOW) --Child--> M --Child--> A (EOW)
L --Child-> O --Child--> G (EOW)
As you can see, by adding nodes to the tree this way, you share common beginnings, but the endings are still separated. To shrink the size of the DAWG, you need to find common endings and combine them. To do this, you start at the leaf nodes (the nodes that have no children). If two leaf nodes are identical, you combine them, moving all the references from one node to the other. For two nodes to be identical, they not only must have the same letter, but if they have Next nodes, the Next nodes must also be identical (if they have child nodes, the child nodes must also be identical).
Take the following tree of CITIES, CITY, PITIES and PITY:
C --Child--> I --Child--> T --Child--> I --Child--> E --Child--> S (EOW)
| Y (EOW)
P --Child--> I --Child--> T --Child--> I --Child--> E --Child--> S (EOW)
Continue reading this explanation at:
- 1. word_dawg (pre-set/fixed list read in from "tessdata/word-dawg")
(this one is read in raw/directly for speed, user can't change this right now)
- 2. document_words (document-words that have already been recognized)
(built during execution; FIX: is/isn't cleared per-document/baseapi call)
- 3. pending_words (words tess is working on, at the moment, before they are added to document_word)
- 4. user_words (user-adjustable list read in from "tessdata/user-words")
(add here custom words that tesseract tends to corrupt)
Let's say that tesseract thinks it found a word with four letters, "thls". Before this word is output, tesseract will:
- look-up "thls" in DAWG #1 (see above)
- (when does it check user-words?)
- By looking through the sorted list for each of the classes, tesseract will note that the third character had a second-best choice to be an 'i' so it changes that letter and
- look-up "this" in DAWG #1 and this time it DOES match.
- (fmg has seen tess KEEP ON permuting even after a match in both #1 and #4 so is not sure what the ending conditions are - maybe someone who knows better can explain) which can only mean that:
- until the certainty of the word isn't moved beyond some threshold, permuting of other letters continues...
=========== DAWG-related ToDo's ============
- Need to add info here on:
- how to view/list words ALREADY IN "tessdata/word-dawg"
- how to CREATE A NEW "tessdata/word-dawg"
- which constants need to be tweaked when adding words to "tessdata/word-dawg"
- which constants need to be tweaked when adding words to "tessdata/user-words" (because a poster on the forums said that after about 5000 words are added guano happens)
- why/what for is rand() used in add_word_to_dawg()
- what to do when the dreaded "DAWG Table is too full" error occurs AFTER Ray Smith's patch is already applied...
Generated on Wed Feb 28 19:49:30 2007 for Tesseract by 1.5.1
COPIED VERBATIM FROM http://tesseract-ocr.repairfaq.org/