Yeah, yeah, I know you expect from me matrix jokes. What if I told you I have no jokes on that ? So, just take the blue pill and go into serious stuff like ...

### Cutting to the chase

I personally find matrix multiplication as the guy who sells stolen phones at the corner of the street. I mean, you get stuff at lower price but it can break in two days and you can get busted by the cops. Or not. I really need to find better metaphors...

Matrix multiplication is a well known method. People wrote on it before quite good articles, but I think you might get stuff simpler just by looking over some problems. For the ones who are familiar with the topic, you can skip to the last two problems. ### Getting high fast

Now I need to find better subtitles... However, first of all to know logarithmic matrix multiplication, you have to know logarithmic multiplication.

Basically we have to compute *x*^{n} considering the multiplication operation take *O*(1) time. Take it straight forward we get *x*^{n} = *x* * *x* * .. * *x* , so *O*(*N*). Let's try to reduce it step by step. Let's take *x*^{n} = *x*^{2} * *x*^{2} * .... And we multiply by *x* if n is odd. This should work fine and the constant is reduced at half. Right... Similarly we can go to *x*^{n} = *x*^{sqrt(n)} * *x*^{sqrt(n)} * ... and this goes to *O*(*sqrtN*). This reasoning stops here.

To get it faster you have to simply observe that *x*^{n} = *x*^{n / 2} * *x*^{n / 2} for n even and *x*^{n} = *x*^{n / 2} * *x*^{n / 2} * *x* for n odd. The two terms are the same and the third is constant, so we really need to compute *x*^{n / 2} once. And *x*^{n / 4} once. And so on. Therefore the *O*(*logN*) complexity.

Now, notice that we did not specified that x is an integer or a number. The same rules hold for other mathematical associative structures such as matrices.

### Don't get stuck with struct

If you sayin' Y U NO REMEMBER MATRIX, then let me refresh your maths knowledge. You don't really need to know much about matrices to use put recurrences in a matrix multiplication form. Multiplying squared matrices is straight forward. Given two matrices their product is

Each element in each row in *M* is multiplied by its correspondent in the columns of *N*. If you find it simpler to remember, just imagine horizontal rows splitting matrix *M* and vertical row splitting matrix *N* and then match each row with each column.

Let's make a structure in which we keep a matrix. If new to matrices you should get an idea how matrix multiplication works from the code below.

```
struct matrix {
// N is the size of the matrix
int m[N][N];
matrix()
{
memset(m,0,sizeof(m));
}
matrix operator * (matrix b)
{
matrix c = matrix();
for (int i = 0; i < N; ++i)
for (int j = 0; j < N; ++j)
for (int k = 0; k < N; ++k)
c.m[i][j] = (c.m[i][j] + 1LL * m[i][k] * b.m[k][j]) % M;
return c;
}
...
};
```

Notice that we define the multiplication operation. We specifically did this so we can use a matrix exactly as a number in the logarithmic multiplication algorithm. So the code will be the same for an int and a matrix. Pretty cool if I do say so. And I do.

```
matrix modPow(matrix m,int n)
{
if ( n == 0 )
return unit; // the unit matrix - that is 1 for principal diagonal , otherwise 0
matrix half = modPow(m,n/2);
matrix out = half * half;
if ( n % 2 )
out = out * m;
return out;
}
```

Note that we could have defined an operator for power multiplication or used a template that we could have applied for a general type, but I find the implementation above more clear due to the clarity of the recurrence.

*N*-th Fibonacci term

For starters, let's define:

*F*_{n} = *F*_{n} - 1 + *F*_{n} - 2 with *F*_{1} = 1, *F*_{2} = 1

We need to put this in the form of a matrix recurrence. Well, each term is dependent of other consecutive two. This is a good clue we need just a 2 row matrix. So, from *F*_{n - 2} and *F*_{n - 1} we need to compute *F*_{n}. To keep the recurrences squared we will compute from the pair (*F*_{n - 2}, *F*_{n - 1}) the pair (*F*_{n - 1}, *F*_{n}).

*F*_{n} = *F*_{n - 1} * 1 + *F*_{n - 2} * 1 *F*_{n - 1} = *F*_{n - 1} * 1 + *F*_{n - 2} * 0

Or, as matrices:

Going one step backwards we got:

Finally:

Getting at power n takes logarithmic time , so that is just... fast.

### Bits and pieces

As you can see, this technique can be used to calculate the n-th term of a linear recurrence. In the following example we need to find out how many arrays of length n with maximum k consecutive 0 bits are there. ( *n* ≤ 10^{9}, *k* ≤ 40 )

Let's suppose n is small enough so we can use dynamic programming to solve the problem. Denote *D*_{n, k} = number of arrays of length n which end in k number of 0s

As you can guess one can make two moves: add a 0 and add a 1. Therefore, from state (*n*, *k*) we can go to states (*n* + 1, *k* + 1) and (*n* + 1, 0). So and *D*_{n, k} = *D*_{n - 1, k - 1}. As we did before, let's write down all recurrences we are interested in.

*D*_{n, 1} = *D*_{n - 1, 0}

*D*_{n, 2} = *D*_{n - 1, 1}

...

*D*_{n, k} = *D*_{n - 1, k - 1}

The matrix recurrence will come straight away:

As you can see, now the complexity of the solution is reduces from *O*(*N* * *K*) to *O*(*logN* * *K*^{3}), the *K*^{3} being the complexity of multiplying 2 K-size matrices.

### How big can it get ?

Now seriously, I really need better subtitles. Problem Chimney from TopCoder can be solved similarly with the problems above.

Usually, when we got a big *N*, this is a hint in favor of logarithmic multiplication. So we have to find a recurrence. More specifically, we have to find a good way to represent a state.

You can also note that we are not really interested how many layers have been completed, but what are the last moves made. So we can have the next forms of completed blocks in the last layers:

```
+-----+--+ +-----+--+ +-----+--+ +-----+--+
|xxxxx| | | | | |xxxxx| | | |xx|
+--+--| | +--+--| | +--+--| | +--+--|xx|
| | | | |xx| | | | | | | |xx| |xx|
| +--+--+ |xx+--+--+ | +--+--+ |xx+--+--+
| | | |xx|xxxxx| | |xxxxx| |xx|xxxxx|
+--+-----+ +--+-----+ +--+-----+ +--+-----+
1 2 3 4
+-----+--+ +-----+--+ +-----+--+ +-----+--+
| | | | |xx| | |xx| | |xx|
+--+--| | +--+--|xx| +--+--|xx| +--+--|oo|
+--+--| | +--+--|xx| +--+--|xx| +--+--|oo|
|xx| | | |xx| |oo| |xx| |oo| |xx| |oo|
|xx+--+--+ |xx+--+oo+ |xx+--+oo+ |xx+--+oo+
|=====xxx| |xx|xxxoo| |===== oo| |===@@@@@|
+--+-----+ +--+-----+ +--+-----+ +--+-----+
5 6 7 8
```

`xx`

represent brick on the n-th layer. `==`

and `oo`

are bricks on the n+1-th layer. `@@`

are bricks on the n+2-th layer. The special thing is we do not care what is the orientation of the chimney as all its bricks are similar, so for one brick on n-th layer ( pic 1 ) we treat all 4 possible displays the same. Another important thing to notice is that after we place two bricks one next to the other we can complete another brick in the layer above. ( pics 5,6 and 7 ). Finally, we can just add another brick to the n+2-th layer. ( pic 8 ) For simplicity, we should also consider the free layer ( a layer that contains no bricks ).

Therefore, this problem can be solved by matrix multiplication, building a 9 per 9 matrix and logarithmic multiplying it. You can see my implementation here.

### Summing up

What we looked at today can be a good tool, no doubt. But as a personal advice, use it only when is necessary outside contests. Some problems are intended to be solved in a different way and people can skip useful stuff by overusing the method described above.

I also recommend this blog post, which is really good.

### PS

Thank you for reading and please state your opinion on my tutorial. ( or, more specifically, on my writing style and how useful you find the material presented ) Any suggestions for next tutorial are welcome.

You can find my previous article here.

Hope you enjoyed!

Added to favourites. You're great at explaining!

Auto comment: topic has been updated by DanAlex (previous revision, new revision, compare).One quick note: If you change your matrix multiplication code in this way (I mean changing second and third for) It will be much faster because of CPU cache.

I think we can optimize furthur by using

`const matrix &b`

since it wont clone to a new matrix.And sorry but can you explain more why that trick run faster in that case ?

Can someone explain why Dn,k = Dn-1,k. Why isn't it simply equal to Dn-1,k-1 ?

You are right. PocolaOctavian also noticed. Sorry for long delay in response, I'll modify it.

I want some problems to pratice. Can you give some???