Google treasure hunt: last puzzle
Few days back google announced about last leg of google treasure hunt journey. This time they provided unix epoch time 1212448500, time when puzzle was supposed to get released.
You can use http://www.epochconverter.com/ to convert it to human readable format. This side also provides list of available methods to get epoch time, convert it to human readable format and vice-versa.
PHP date(output format, epoch); Output format example: ‘r’ = RFC 2822 date
Python import time first, then time.gmtime(epoch)
MySQL from_unixtime(epoch, optional output format)
So the puzzle was supposed to release at
Mon, 02 Jun 2008 23:15:00 GMT, for India: Tuesday, June 03, 2008 4:45:00 AM (middle of the night).
Forth Puzzle is available here. Its a bit tricky, but i wrote a c program to calculate the number using brute force method…and it worked.(Share how you did it or is there some shortcut which works without any programming). Problem is to find a prime number which in turn can be expressed as sum of of n consecutive prime numbers. Your answer should satisfy 4 such list of prime numbers of given length.
So its over for now and soon they are going to contest winners and rewards. Hope i could have been one
. But I have submitted this puzzle after long delay.(Was sleeping when it was released)
- Puzzle 1 (Robot in a maze) : Find it here
- Puzzle 2 (getting lines from specific files in zip archive) : Find it here
- Puzzle 3 (Network routing table) : Find it here
Comments
4 Responses to “Google treasure hunt: last puzzle”
Leave a Reply
Add to del.icio.us Network
Google Reader Shared Items
Twitter Feed
Flickr Photos
This one was pretty fun. I couldn’t find a good mathematical approach (Problems related to sums of primes seem to be hard. See the Goldbach conjecture), so I wrote a Haskell program that used a tower of lazy immutable Arrays, each built by referencing an arrays of shorter consecutive prime sums. I then marched linearly through the array for the longest consecutive sum, until I found a prime and then used a binary search to check if that number was found in each of the other arrays. Since each of the arrays can be defined in terms of each other, this solution represents a sort of dynamic programming solution, and since Haskell is lazy the binary search doesn’t have to compute the entire array that we’re performing binary search on. It still took about 9 seconds to find the answer on my laptop though. I’m interested to see more elegant solutions.
good Luck !
[…] « Google treasure hunt: last puzzle […]
when brute works, nothing can be better