# Google Billboard Problems

A mysterious billboard appeared on 101-southbound which I passed each day to work. The billboard said:

{ the first 10-digit prime in consecutive digits of

e}.com

I passed by the billboard numerous times before I realized it wasn't an advertisement for a company, it wasn't touting some servers new ability, it was actually a question. A problem to be solved. As I've shown before I'm always up for a good problem, I got right on it.

## Problem #1

My first intrepretation of the problem was to find the first 10-digit prime, the first being 1,000,000,007 and the next being 1,000,000,009 and seeing if they are in *e*. So I've already created a few primes scripts before but not up to 10-digits, so I modified it a touch and started that cranking out some big primes.

Now as I started to think about it more I realized that this intrepretation doesn't make sense, since it is wholly dependent on the length of *e* that you are using to check. It's possible you can extend *e* long enough to have any 10-digit prime show up.

Well, I had left my big prime number generator cranking and it turned out 105 million prime numbers, up to 2.1 billion. This file of consecutive primes ended up being 1 gig! This took about 4-hours on an Opteron 64-bit 2ghz box. Thankfully I wouldn't need it.

So on to the second, and real interpretation, of the question, take 10-digit chunks of *e*, starting at the beginning and check if those are prime. This turns out to be a much easier problem.

Now, the largest number it could be is 9,999,999,999, so the largest prime we need to check is the square root of that, which is roughly 100,000. Now the list of primes up to 100,000 is quick and easy to generate. [again previous scripts]

So grabbing the first ~2,500 digits of *e*, from this site [nasa.gov], I was guessing 2,500 would be enough. I could always go back for more. Moving them onto one line for ease of use I ended up with this file [e.0]

I wrote this script [util_chunkify.py] to chunkify it into 10-digit pieces that are possibly primes, stripping out digits that end with an even number or 5. This left me with the following file [e.10digit.chunks]

So I then wrote a script which reads in the primes from this file [primes.sm] and puts them in an array. This is what is used to check if our 10-digit e-chunks are prime, using this script [checke.py]

Here are the first ten, the first one of course is the correct answer:

- ** 7427466391 **
- 7413596629
- 6059563073
- 3490763233
- 2988075319
- 1573834187
- 7021540891
- 5408914993
- 6480016847
- 9920695517

So going to: http://www.7427466391.com/ brings up a second problem.

## Problem #2

Here's the second problem:

```
f(1) = 7182818284
f(2) = 8182845904
f(3) = 8747135266
f(4) = 7427466391
f(5) = ???
```

**First Idea**

The first thought was to solve it using a 3rd degree polynomial which will give us an equation which will fit the four points and we can plug in the 5th value, **5**, and get the answer. After struggling with Excel, which could graph and forecast the polynomial and even give us an equation it would not give us the forecasted value. dumb. Abandoning Excel, since it's equation wasn't even all that accurate.

Using: `a * x^3 + b * x^2 + c * x + d = y`

Gives us the following 4-equations and 4-unknowns:

1a + 1b + 1c + d = 7182818284 8a + 4b + 2c + d = 8182845904 27a + 9b + 3c + d = 8747135266 64a + 16b + 4c + d = 7427466391

This solves to:

a = -241369996.5 b = 1230350850 c = -1001434954.5 d = 7195272385

Plugging into the above for f(5) = **2775619365**

Testing this does not work, but since this section was labeled, First Idea, you should of seen that it would've been wrong.

**Second Idea**

After giving up the the polynomial fit and looking at the numbers a little more the first number looked very much like the beginning of *e*. It turns out to be the first segment of *e* and the other numbers also are all segments of *e*. They looked like this:

2718281828459045235360287471352662497757247093699959574966967627724076630353547594571382178525166427427466391 7182818284 8182845904 8747135266 7427466391

The first number mapped to the 2 spot of e, the 2nd number to the 6th spot, the 3rd number to the 24th spot and the 4th number to the 100th spot. This gave me the new functions:

k

```
f(1) = 2
f(2) = 6
f(3) = 24
f(4) = 100
```

Numerous attempts were made to try to figure out a patern here, which turns out to be very close to a factorial series, `f(x) = (x+1)!`

but not quite, the 100 would need to be 120. After awhile looking at this it was abandoned and back to the original numbers.

```
f(1) = 7182818284
f(2) = 8182845904
f(3) = 8747135266
f(4) = 7427466391
f(5) = ???
```

Trying out various things on them, the following turned up which seemed a little too coincendental to be a coincendence:

```
7+1+8+2+8+1+8+2+8+4 = 49
8+1+8+2+8+4+5+9+0+4 = 49
8+7+4+7+1+3+5+2+6+6 = 49
7+4+2+7+4+6+6+3+9+1 = 49
```

So a quick script [sum_checke.py] to check if these are the first 4 values of 10-digit chunks of *e* that sum to 49, which they turned out to be. The script turned up:

- 7182818284
- 8182845904
- 8747135266
- 7427466391
**5966290435**- 2952605956
- 0753907774
- 0777449920
- 3069697720
- 1252389784

The 5th one being the correct answer.

Following the directions, it turned out to be a recruitment tool for Google Labs, looking for the best and brightest. It was pretty fun and good idea for them. Unfortunately, their search engine is too good and anyone can look up answers to them, so I'm not sure how valid of a test it is. I did send them the link to my resume, encoded of course.

## Calculating *e*

I felt like it was cheating downloading some one else's calculated digits of *e*. So using the formula:

e = 1/0! + 1/1! + 1/2! + 1/3! + 1/4! + ... 1/N!

I wrote the following script, calc_e.py to calculate the digits of *e*, the script uses the GMP libraries for precision.

## Related Links

Initial Introduction: Google Blog

Dr. Math's About

*e*GMP: GNU Multiple Precision Arithmetic Library : the fastest bignum library on the planet!