Conway's Game of Life

Conway's Game of Life is a well-known cellular automaton in which each generation of a population 'evolves' from the previous one according to a set of predefined rules.

Here is John Scholes' famous one-line APL function takes a boolean matrix as argument and returns a boolean matrix with the new generation.

The Glider
One interesting pattern that occurs in Life is a Glider:

To see how the Glider evolves over the generations, we need to give it some space to move around. The Game of Life takes place on an infinite two-dimensional grid, but that might be a bit large for our computer! Let's start the Glider off in the bottom right-hand corner of a 10 x 10 grid:

After one generation the pattern becomes:

The Glider has slightly changed shape and also moved up and to the left.

Visualising it
To make the pattern easier to see, we can print a  symbol where there's a cell and a   otherwise, for example:

Here's how the Glider evolves over the first ten generations:

How the APL code works
If you're completely new to APL, this explanation is probably not the place to start, rather check out our introductions. However, you should be able to get some idea of what's happening even if the details are not yet clear. Just bear in mind that APL evaluates expressions from right to left unless you use parentheses.

To compute a new generation in the Game of Life we first need to find out how many neighbours each live cell has. To keep things simple let's consider the following 5-by-5 grid:

Rotation
If we rotate each row of the grid one place left by using APL's Rotate function, each element is replaced by its right-hand neighbour. In other words, the new grid will have a 1 for all cells whose right-hand neighbour was 1:

Similarly we can rotate right to find the left-hand neighbour by using. By using APL's Outer Product operator  together with the Rotate function we can get a set of three grids containing the left-hand neighbour, the original grid, and the right-hand neighbour:

Extending to two dimensions
Now we can use a similar trick but rotate up and down by using APL's First Axis Rotate function. Used with an Outer Product this gives us a series of 9 grids:

The grid in the centre is our original grid, and the others give the neighbours above, below, left, right and diagonally.

Summing it up
Now we can find out how many neighbours each cell in the original grid has by summing the corresponding elements in each of the 9 grids. For a live cell this will give us 1 more than the number of neighbours - e.g. a 4 in the result means a cell has three neighbours. For a dead cell the result is just the number of neighbours:

For a cell to exist in the next generation, one of two rules must be met:


 * Any live cell with two neighbours lives, unchanged, to the next generation
 * Any cell, live or dead, with exactly three neighbours is live in the next generation

This means that all cells which might be live in the next generation will have a sum of 3 (from the first rule) or 3 or 4 (from the second rule).

So we're interested in cells with a sum of 3 or 4, which we can find as follows:

The next step is best understood by first considering the two scores 4 and 3 separately

(a) A score of 4 corresponds either to a live cell with three neighbours or a dead cell with four neighbours. Only in the former case do we get a cell in the next generation - i.e. we get a cell if the score is 4 and the cell is currently live. Here we're using APL's And function,

(b) A score of three corresponds either to a live cell with two neighbours or a dead cell with three neighbours. In either case we get a cell in the next generation:

We can write this slightly redundantly by and-ing with 1 (meaning "and the cell is alive or dead") for reasons which will become apparent shortly:

So the next step is to say that a cell is live if either test (a) or test (b) is met. We need to use APL's Or function,. We could write this rather long-windedly as:

Refactoring
But we can take advantage of APL's Inner Product operator to do the and operations of each test and then or the result - the  in the following:

The final expression ends with a bit of housekeeping using  to turn the result back into a simple array (it's currently nested).