The Aho – Korasik algorithm — a substring search algorithm developed by Alfred Aho and Margaret Korasik in 1975  , implements a search for multiple substrings from a dictionary in a given string .
It is widely used in system software, for example, it is used in the grep search utility  .
- 1 principle of operation
- 2 Computational complexity
- 3 notes
- 4 References
Principle of Operation
The algorithm builds a finite state machine , to which it then passes a search string. The machine receives all the characters of the string in turn and moves along the corresponding edges. If the machine has reached its final state, the corresponding dictionary line is present in the search line.
Several search strings can be combined into a search tree, the so-called boron (prefix tree). Bor is a state machine that recognizes one line from - but provided that the beginning of the line is known.
The first task in the algorithm is to teach the automaton to "recover" if the substring does not match. At the same time, transferring the automaton to its initial state with any unsuitable letter is not suitable, since this can lead to the omission of the substring (for example, when searching for the
aab aabab comes
aab aabab , after reading the fifth character, resetting the automaton to the initial state will lead to the omission of the substring - it was true go to state
a , and then process the fifth character again). In order for the automaton to regenerate itself, suffix links loaded with the empty symbol ⌀ are added to it (so that the deterministic automaton becomes non-deterministic). For example, if the string
aaba , then the boron suffixes
a suggested. A suffix link is a link to a node corresponding to the longest suffix that does not lead the boron to a dead end (in this case,
For the root node, the suffix link is a loop. For the rest, the rule is this: if the last recognized character is , then the parent suffix is crawled if there is an arc loaded with the symbol from there , the suffix link goes to the node where this arc leads. Otherwise, the algorithm goes through the suffix link again and again until it either goes through the root link loop or finds an arc loaded with a symbol .
* ··· ⌀ ···> * ··· ⌀ ···> * ··· ⌀ ···> * | | c c ↓ ↓ [*] ·············· ⌀ ···············> * new suffix link
This automaton is non-deterministic. The transformation of a nondeterministic finite state machine into a deterministic one in the general case leads to a significant increase in the number of vertices. But this automaton can be turned into deterministic without creating new vertices: if for the vertex nowhere to go by symbol , go through the suffix link again and again - until either we get to the root, or where will we go by the symbol .
It is convenient to do all determinations recursively. For example, for a suffix link:
Alg Suff Link (v) if v. cache Suff Link ≠ Ø // for the root, the root is initially root. cache Suff Link = root return v. cache Suff link u: = v. parent c: = v. character to repeat u: = Suff Link (u) to (u = root) or (there exists a path u —c → w) if there exists a transition u —c → w then v. cache Suff Link: = w otherwise v. cache Suff Link: = root return v. cache Suff link
Determination increases the number of end vertices: if suffix links from the top lead to the final , itself also declared ultimate. For this, the so-called end links are created: the end link leads to the end vertex closest to the suffix links; traversing the end links gives all matching lines.
alg Output Result (v, i) type "Found" + v. needle + "in position" + (i - v. depth + 1)
alg Main Part Search state: = root cycle i = 1 .. | haystack | state: = Transition (state, haystack [i]); if condition. needle ≠ Ø Output Result (state, i) timeState: = state So far Final Link (time Comp) ≠ Ø timeSost: = EndReference (timeSost); Output Result (timeSost, i)
Suffix and end links in the machine can be calculated as needed already in the search phase. Side transitions - you can calculate on the spot without caching in any way , you can cache for all nodes, you can cache for the most important ones (all this does not affect the asymptotic estimation of the algorithm).
The computational complexity of the algorithm depends on the organization of the data. For example:
- If the machine’s navigation table is stored as an index array , memory consumption computational complexity where - the length of the text in which the search is performed, - the total length of all words in the dictionary, Is the size of the alphabet, Is the total length of all matches.
- If the machine’s transition table is stored as a red-black tree , the memory consumption is reduced to however computational complexity rises to .