# A Neighborhood of Infinity

## Tuesday, September 29, 2009

### test, ignore

\int_{0}^{1}\frac{x^{4}\left(1-x\right)^{4}}{1+x^{2}}dx=\frac{22}{7}-\pi

You know, I think I won't delete this. It's a celebration of my having embedded some TeX using the advice at Bot Cyborg.

## Saturday, September 26, 2009

### Finite Differences of Real-Valued Functions

Conor McBride's discovery that you can differentiate container types to get useful constructions like zippers has to be one of the most amazing things I've seen in computer science. But seeing the success of differentiation suggests the idea of taking a step back and looking at finite differences.

Forget about types for the moment and consider functions on a field R. Given a function f:R→R we can define Δf:R×R→R by

Δf(x,y) = (f(x)-f(y))/(x-y)

Δ is the finite difference operator. But does it make any kind of sense for types? At first it seems not because we can't define subtraction and division of types. Can we massage this definition into a form that uses only addition and multiplication?

First consider Δc where c is a constant function. Then Δc(x,y)=0.

Now consider the identity function i(x)=x. Then Δi(x,y)=1.

Δ is linear in the sense that if f and g are functions, Δ(f+g) = Δf+Δg.

Now consider the product of two functions, f and g.

Δ(fg)(x,y) = (f(x)g(x)-f(y)g(y))/(x-y)

= (f(x)g(x)-f(x)g(y)+f(x)g(y)-f(y)g(y))/(x-y)

= f(x)Δg(x,y)+g(y)Δf(x,y)

So now we have a Leibniz-like rule. We can compute finite differences of polynomials without using subtraction or division! What's more, we can use these formulae to difference algebraic functions defined implicitly by polynomials. For example consider f(x)=1/(1-x). We can rewrite this implicitly, using only addition and multiplication, as

f(x) = 1+x f(x)

Differencing both sides we get

Δf(x,y) = x Δf(x,y)+f(y)

That tells us that Δf(x,y) = f(x)f(y).

### Finite Differences of Types

We're now ready to apply our operator to types. Instead of functions on the reals we work with functors on the set of types. A good first example container is the functor F(X)=XN for an integer N. This is basically just an array of N elements of type X. We could apply the Leibniz rule repeatedly, but we expect to get the same result as if we'd worked over the reals. So setting f(x)=xN we get

Δf(x,y) = (xN-yN)/(x-y) = xN-1+xN-2y+xN-3y2+...+yN-1

So we know that on types, ΔF(X,Y) = XN-1+XN-2Y+...+YN-1.

There's a straightforward interpretation we can give this. Differentiating a type makes a hole in it. Finite differencing makes a hole in it, but everything to the left of the hole is of one type and everything on the right is another. For example, for F(X)=X3, ΔF(X,Y)=X2+XY+Y2 can be drawn as:

If you've been reading the right papers then at this point it should all become familiar. Finite differencing is none other than dissection, as described by Conor in his Jokers and Clowns paper. I don't know if he was aware that he was talking about finite differences - the paper itself talks about this being a type of derivative. It's sort of implicit when he writes the isomorphism:

right :: p j + (Δp c j , c) → (j , Δp c j ) + p c

With a little rearrangement this becomes the definition of finite difference.

Now that we've recognised dissection as finite difference we can reason informally about dissection using high school algebra. For example, we already know that lists, defined by L(X) = 1+X L(X) can be informally thought of as L(X)=1/(1-X). So using the example I gave above we see that ΔL(X,Y)=1/((1-X)(1-Y)) = L(X)L(Y). So the dissection of a list is a pair of lists, one for the left elements, and one for the right elements. Just what we'd expect.

Another example. Consider the trees defined by T(X)=X+T(X)2. Informally we can interpret this as T(X)=(1+√(1-4X))/2. A little algebraic manipulation, using (√x-√y)(√x+√y) = x-y shows that

ΔT(X,Y) = 1/(1-(T(X)+T(Y))

In other words, a dissection of a tree is a list of trees, each of which is a tree of X or a tree of Y. This corresponds to the fact that if you dissect a tree at some element, and then follow the path from the root to the hole left behind, then all of the left branches (in blue) are trees of type X and all of the right branches (in red) are trees of type Y.

If you're geometrically inclined then you can think of types with holes in them as being a kind of tangent to the space of types. Along those lines, dissections become secants. I think this geometric analogy can be taken a lot further and that in fact a non-trivial piece of differential geometry can be made to work with types. But that's for another day.

Oh, I almost forgot. Derivatives are what you get when you compute finite differences for points really close to each other. So I hope you can see that Δf(x,x)=df/dx giving us holes in terms of dissections. Conor mentions this in his paper.

We should also be able to use this approach to compute finite differences in other algebraic structures that don't have subtraction or division.

I can leave you with some exercises:

1. What does finite differencing mean when applied to both ordinary and exponential generating functions?

2. Can you derive the "chain rule" for finite differences? This can be useful when you compute dissections of types defined by sets of mutually recursive definitions.

3. Why is right, defined above, a massaged version of the definition of finite difference? (Hint: define d=((f(x)-f(y))/(x-y). In this equation, eliminate the division by a suitable multiplication and eliminate the subtraction by a suitable addition. And remember that (,) is Haskell notation for the product of types.)

## Sunday, September 13, 2009

### More Parsing With Best First Search

> {-# LANGUAGE NoMonomorphismRestriction,GeneralizedNewtypeDeriving #-}

I have three goals in this post:

1. Refactoring the technique in my previous post so that building the search tree is entirely separate from searching the tree.
2. Making it work with real-valued weights, not just integers
3. Applying it to an ambiguous parsing problem, making use of a type class to define an abstract grammar.

> import Control.Arrow> import Control.Monad> import Control.Monad.Instances> import Control.Monad.State> import Data.Either> import Data.Function> import Random> import qualified Data.List as L> import qualified Data.Map as M

### Search Trees

The idea is that I want to search a tree of possibilities where each edge of the tree is marked with a weight. The goal will be to search for leaves that minimise the sum of the weights of the edges down to the leaf.

Here's an example tree:

The minimum weight leaf is at C. If we're working with probabilities then we'll use minus the log of the probability of a branch as the weight. That way multiplication of probabilities becomes additions of weights, and the likeliest leaf has the minimum weight path.

So here's the definition of a search tree. I've given both leaves and edges weights:

> data Search c a = Leaf   { lb::c, leaf::a}>                 | Choice { lb::c, choices::[Search c a] } deriving Show

(Compare with this.) lb is short for 'lower bound'. It provides a lower bound for the total weight of any option in this subtree (assuming non-negative weights). The tree in the diagram would look like:

> ex1 = Choice 0 [>   Choice (-log 0.1) [>       Leaf (-log 0.5) 'A',>       Leaf (-log 0.5) 'B'],>   Choice (-log 0.2) [>       Leaf (-log 0.6) 'C',>       Leaf (-log 0.4) 'D']]

This tree is a container in a straightforward way and so we can make it an instance of Functor:

> instance Functor (Search c) where>    fmap f (Leaf   c a ) = Leaf c   $f a> fmap f (Choice c as) = Choice c$ map (fmap f) as

But it's also a monad. >>= maps all of the elements of a tree to trees in their own right, and then grafts those trees into the parent tree:

> instance Num c => Monad (Search c) where>    return = Leaf 0>    a >>= f = join $fmap f a where> join (Leaf c a ) = Choice c [a]> join (Choice c as) = Choice c$ map join as

It's easy to make trees into a MonadPlus by simply grafting trees into a new root. MonadPlus is meant to be a monoid, but this operation, as written below, isn't precisely associative. But it's 'morally' associative in that two terms that are meant to be equal describe equivalent search trees. So I'm not going to lose any sleep over it:

> instance Num c => MonadPlus (Search c) where>    mzero = Choice 0 []>    a mplus b = Choice 0 [a,b]

For our searching we'll need a priority queue. I'll use a skew tree with code I lifted from somewhere I've forgotten:

> data Ord a => Tree a = Null | Fork a (Tree a) (Tree a) deriving Show> isEmpty :: Ord a => Tree a -> Bool> isEmpty Null = True> isEmpty (Fork x a b) = False> minElem :: Ord a => Tree a -> a> minElem (Fork x a b) = x> deleteMin :: Ord a => Tree a -> Tree a> deleteMin (Fork x a b) = merge a b> insert :: Ord a => a -> Tree a -> Tree a> insert x a = merge (Fork x Null Null) a> merge :: Ord a => Tree a -> Tree a -> Tree a> merge a Null = a> merge Null b = b> merge a b>  | minElem a <= minElem b = connect a b>  | otherwise = connect b a> connect (Fork x a b) c = Fork x b (merge a c)

At each stage in the search we'll pick the unexplored branch with the lowest total weight so far. So when we compare trees we'll compare on their lower bounds. So we need an ordering on the trees as follows:

> instance (Num c) => Eq (Search c a) where>    (==) = (==) on lb> instance (Num c,Ord c) => Ord (Search c a) where>    compare = compare on lb

The real cost of a choice isn't just the weight immediately visible in the tree but the cost of the journey you took to get there. We use the bumpUp function to put that extra cost into the part of the tree we're currently looking at:

> bumpUp delta (Leaf   c a)  = Leaf   (delta+c) a> bumpUp delta (Choice c as) = Choice (delta+c) as

The only tricky aspect to this code is that we need to be able to handle infinite trees. We can't have our code simply go off and return when it's found the next match because it might not be possible to do so in a finite time. Instead, the code needs to perform one operation at a time and report what it found at each point, even if that report is just stalling for time. We do this by returning a (possibly infinite) list containing elements that are either (1) the next item found or (2) a new update giving more information about the lower bound of the cost of any item that might be yet to come. This allows the caller to bail out of the search once the cost has passed a certain threshold.

(Returning a useless looking constructor to stall for time is a common design pattern in Haskell. It's an example of how programs that work with codata need to keep being productive and you get something similar with the -|Skip|- in Stream Fusion. First time I write the code I failed to do this and kept wondering why my infinite searches would just hang, despite my great efforts to make it as lazy as possible.)

> runSearch :: (Num c,Ord c) => Tree (Search c a) -> [Either c a]> runSearch Null = []> runSearch queue = let>    m = minElem queue>    queue' = deleteMin queue>    in case m of>        Leaf   c a  -> Left c : Right a : runSearch queue'>        Choice c as -> Left c           : (runSearch $foldl (flip insert) queue'$ map (bumpUp c) as)

A quick test of an infinite search: finding Pythagorean triples by brute force. We give each integer as cost one more than the previous one:

I guess this is actually Dijkstra's algorithm, but on a tree rather than a general graph.

> integers m = Choice 1 [Leaf 0 m,integers (m+1)]> test = do>    a <- integers 1>    b <- integers 1>    c <- integers 1>    guard $a*a+b*b==c*c> return (a,b,c)> test1 = runSearch (insert test Null) If you run test1 you'll notice how the output is noisy because of all those Left w terms. If you'e not worried about non-termination you could just throw out redundant output like so: > reduce [] = []> reduce (Left a : Left b : bs) = reduce (Left b : bs) Might as well convert weights to probabilities while we're at it: > reduce (Left a : bs) = Left (exp (-a)) : reduce bs> reduce (Right a : bs) = Right a : reduce bs This version should be a lot less chatty: > test2 = reduce test1 ### Grammar Now that searching works I can turn to an application - a more sophisticated example of what I briefly looked at previously), parsing with ambiguous grammars. So let me first build types to represent parsed sentences in a toy grammar: > data Noun = Noun String deriving (Show,Eq,Ord)> data Verb = Verb String deriving (Show,Eq,Ord)> data Adj = Adj String deriving (Show,Eq,Ord)> data Prep = Prep String deriving (Show,Eq,Ord) The following two are noun phrase and prepositional phrase: > data NP = NP [Adj] Noun deriving (Show,Eq,Ord)> data PP = PP Prep Noun deriving (Show,Eq,Ord) And entire sentences: > data Sentence = Sentence [NP] Verb [NP] [PP] deriving (Show,Eq,Ord) We want to be able to print parsed sentences so here's a quick 'unparse' type class to recover the underlying string: > class UnParse a where> unParse :: a -> String> instance UnParse Noun where> unParse (Noun a) = a> instance UnParse Verb where> unParse (Verb a) = a> instance UnParse Adj where> unParse (Adj a) = a> instance UnParse Prep where> unParse (Prep a) = a> instance UnParse NP where> unParse (NP a b) = concatMap unParse a ++ unParse b> instance UnParse PP where> unParse (PP a b) = unParse a ++ unParse b> instance UnParse Sentence where> unParse (Sentence a b c d) = concatMap unParse a ++ unParse b ++ concatMap unParse c ++ concatMap unParse d Now I'm going to approach the problem of parsing ambiguous sentences in two ways. One will be efficient, and one will be inefficient but represent the 'ground truth' against which we'll compare. (This reflects standard practice in graphics publications where authors compare their fancy new algorithm with an ultra-slow but reliable Monte Carlo ray-tracer.) I'm going to assume that sentences in my language are described by a "context free" probability distribution so that a noun phrase, say, has a fixed probability of being made up of each possible combination of constituents regardless of the context in which it appears. I need an English word for something that takes a grammar and does something with it but I'm at a loss to think of an example. I'll use 'transducer', even though I don't think that's right. So a transducer is built from either terminal nodes of one character, or it's one of a choice of transducers, each with a given probability: > class Transducer t where> char :: Char -> t Char> choose :: [(Float,t a)] -> t a And here's our toy grammar. It's nothing like an actual natural language because real grammars take a long time to get right. Note I'm just giving the first couple of type signatures to show that the grammar uses only the Monad and Transducer interfaces: > string :: (Monad t, Transducer t) => [Char] -> t [Char]> string "" = return ""> string (c:cs) = do {char c; string cs; return (c:cs)} So, for example, a noun has a 50% chance of being the string ab and a 50% chance of being the string ba: > noun :: (Monad t, Transducer t) => t Noun> noun = do> a <- choose [(0.5,string "ab"),(0.5,string "ba")]> return$ Noun a> verb :: (Monad t, Transducer t) => t Verb> verb = do>    a <- choose [(0.5,string "aa"),(0.5,string "b")]>    return $Verb a> adjective :: (Monad t, Transducer t) => t Adj> adjective = do> a <- choose [(0.5,string "ab"),(0.5,string "aa")]> return$ Adj a> parsePrep = do>    a <- choose [(0.5,string "a"),(0.5,string "b")]>    return $Prep a Some of our "parts of speech" allow sequences of terms. We need some kind of probabilistic model of how many such terms we can expect. I'm going to assume the probability falls off exponentially with the number of items: > many :: (Monad t, Transducer t) => Float -> t a -> t [a]> many p t = choose [> (p,return []),> (1-p,do> a <- t> as <- many p t> return$ a:as)]

I also have a convenience function for sequences of length at least 1:

> many1 p t = do>     a <- t>     as <- many p t>     return (a:as)

And now the rest of the grammar:

> parseNP = do>    a <- many 0.5 adjective>    b <- noun>    return $NP a b> parsePP = do> a <- parsePrep> b <- noun> return$ PP a b> sentence = do>    a <- many 0.5 parseNP>    b <- verb>    c <- many 0.5 parseNP>    d <- many 0.5 parsePP>    return $Sentence a b c d We're going to use this grammar with two instances of type Transducer. The first will use the rules of the grammar as production rules to generate random sentences. The second will parse strings using the grammar. So we get two uses from one 'transducer'. This is pretty powerful: we have described the grammar in an abstract way that doesn't asuume any particular use for it. > newtype Generator a = Generator { unGen :: State StdGen a } deriving Monad> newtype Parser a = Parser { runParse :: (String -> Search Float (a,String)) } Let's implement the generation first: > instance Transducer Generator where> char a = return a> choose p = do> r <- Generator (State random)> case (L.find ((>=r) . fst)$ zip (scanl1 (+) (map fst p)) (map snd p)) of>            Just opt -> snd opt

We can test it by generating a bunch of random sentences:

> gen = mkStdGen 12343210> generate n partOfSpeech = (unGen $sequence (replicate n partOfSpeech)) evalState gen> test3 = mapM_ print$ generate 10 sentence

We can now use generate-and-test to estimate what proportion of randomly generated sentences match a given sentence:

> generateAndTest n partOfSpeech chars = do>    a <- generate n sentence>    guard $unParse a == chars> return a> collectResults n partOfSpeech chars = M.fromListWith (+)$ map (flip (,) 1) $> generateAndTest n partOfSpeech chars> countResults n partOfSpeech chars = mapM_ print$ L.sortBy (flip compare on snd) $> M.toList$ collectResults n partOfSpeech chars> test4 = countResults 100000 (noun :: Parser Noun) "abab"

On the other hand we can build a parser, based on Hutton's, just like in my previous post except using this new tree search monad:

> instance Monad Parser where>   return a = Parser (\cs -> return (a,cs))>   p >>= f = Parser (\cs -> do>       (a,cs') <- runParse p cs>       runParse (f a) cs')> instance MonadPlus Parser where>   mzero = Parser (\cs -> mzero)>   p mplus q = Parser (\cs -> runParse p cs mplus runParse q cs)> instance Transducer Parser where>    char c = Parser $char' where> char' "" = mzero> char' (a:as) = if a==c then return (a,as) else mzero> choose p = foldl1 mplus$ map (\(p,x) -> prob p >> x) p where>       prob p = Parser (\cs -> Leaf (-log p) ((),cs))> goParse (Parser f) x = runSearch $insert (f x) Null> end = Parser (\cs -> if cs=="" then return ((),"") else mzero)> withEnd g = do> a <- g> end> return a> normalise results = let total = last (lefts results)> in map (\x -> case x of> Left a -> a / total> Right b -> b> ) results> findParse chars = mapM_ print$ reduce $runSearch$>   insert (runParse (withEnd sentence) chars) Null

### Results

And now we can try running both methods on the same string:

> main = do>    let string = "ababbbab">    findParse string>    print "-------------------">    countResults 1000000 (sentence :: Parser Sentence) string

You should see the parsings from countResults in roughly the same proportion as the relative probabilities given by findParse. Remember that the relative probability of a given parsing is the last Left p term before that parsing. Try playing with string, the number of Monte Carlo runs and the seed. Remember that there is going to be some variation in the randomised algorithm, especially with hard to parse strings, but raising the number of runs will eventually give reasonable numbers. Of course ultimately we don't care about the Monte Carlo method so it's allowed to be slow.

Anyway, none of this is a new algorithm. You can find similar things in papers such as Probabilistic tree transducers and A Generalization of Dijkstra's Algorithm. But what is cool is how easily Haskell allows us to decouple the tree building part from the searching part. (And of course the tree is never fully built, it's built and destroyed lazily as needed.) All of the published algorithms have the parsing and searching hopelessly interleaved so it's hard to see what exactly is going on. Here the search algorithm doesn't need to know anything about grammars, or even that it is searching for parsings.

Semiring Parsing is also easy to implement this way.

BTW If you think my "ab" language is a bit to contrived, check out the last picture here for an example of some natural language that is in a similar spirit :-)