Skip to main content

Lua implementation of Aho-Corasick string matching

The Aho-Corasick string matching algorithm is a fast way of matching a large number of strings against  a source document. It consists of two stages: building of a special suffix tree and then matching against the tree. The algorithm is linear in the size of the source document (and number of matches) and matches all strings in the dictionary simultaneously and outputs them.

It is particularly helpful when a large dictionary of strings needs to be matched against a document. For example, it can be used to match a dictionary of known virus signatures against a suspicious executable. And it's possible to build the suffix tree ahead of time when the dictionary is fixed.

I needed a Lua implementation of the algorithm for a project and have created one (with a test suite) and released it here. There are two functions: build (which takes an array of strings, the dictionary, and returns the tree in the form of a Lua table) and match (which finds matches in a string given a tree). Since the tree is just a Lua table is can be serialized and loaded into programs as needed.

Lua 5.2.0  Copyright (C) 1994-2011 Lua.org, PUC-Rio
> AC = require 'aho-corasick'
> t = AC.build({"The", "han", "and", "pork", "port", "pot", "ha", "e"})
> m = AC.match("The pot had a handle")
> print(table.concat(m, ","))
The,e,pot,ha,ha,han,and,e

The Wikipedia article has a good explanation of the algorithm itself, but to ease (my own) understanding of the algorithm in action I built a small Processing program that animates the process of matching. (The video is much easier to watch if seen on YouTube).



There's a small test suite included with the implementation. To run it do lua test.lua.

Comments

Popular posts from this blog

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it: Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name. There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly. What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message: Our system is unable to process last names that contain non-letters, please replace them with spaces. Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your

How to write a successful blog post

First, a quick clarification of 'successful'. In this instance, I mean a blog post that receives a large number of page views. For my, little blog the most successful post ever got almost 57,000 page views. Not a lot by some other standards, but I was pretty happy about it. Looking at the top 10 blog posts (by page views) on my site, I've tried to distill some wisdom about what made them successful. Your blog posting mileage may vary. 1. Avoid using the passive voice The Microsoft Word grammar checker has probably been telling you this for years, but the passive voice excludes the people involved in your blog post. And that includes you, the author, and the reader. By using personal pronouns like I, you and we, you will include the reader in your blog post. When I first started this blog I avoid using "I" because I thought I was being narcissistic. But we all like to read about other people, people help anchor a story in reality. Without people your bl

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator: From flickr Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press? Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me". Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of