Welcome to Martin Gardner's Birthday Challenge

The seventh challenge of the 2021 Series will be a 7-day challenge in celebration of the 107th (prime number!) birthday of beloved American science communicator, Martin Gardner. The challenge will be offered on the GCW-LLR application, beginning 21 October 00:00 UTC and ending 28 October 00:00 UTC.

October 21 is the anniversary of Martin Gardner's birth. Gardner (1914-2010) is a legend in recreational (and professional) mathematics circles. Although he had little mathematical training, his 1956-1981 Scientific American column "Mathematical Games" has had a huge impact on the way people view math. In a Science Talk podcast shortly after Gardner's death, Douglas Hofstadter, author of the popular math book "Gödel, Escher, Bach", said that for himself and many others, "Scientific American was just the wrapping for Martin Gardner's column." (link)

"No branch of number theory is more saturated with mystery and elegance than the study of prime numbers: those exasperating, unruly integers that refuse to be divided evenly by any integers except themselves and 1." -Martin Gardner, Patterns and Primes

To participate in the Challenge, please select only the Generalized Cullen/Woodall Prime Search LLR (GCW) project in your PrimeGrid preferences section.

Note on LLR2 tasks: LLR2 has eliminated the need for a full doublecheck task on each workunit, but has replaced it with a short verification task. Expect to receive a few tasks about 1% of normal length.

Application builds are available for Linux 32 and 64 bit, Windows 32 and 64 bit and MacIntel. Intel and recent AMD CPUs with FMA3 capabilities (Haswell or better for Intel, Zen-2 or better for AMD) will have a very large advantage, and Intel CPUs with dual AVX-512 (certain recent Intel Skylake-X and Xeon CPUs) will be the fastest.

Note that LLR is running the latest AVX-512 version of LLR which takes full advantage of the features of these newer CPUs. It's faster than the previous LLR app and draws more power and produces more heat, especially if they're highly overclocked. If you have certain recent Intel Skylake-X and Xeon CPUs, especially if it's overclocked or has overclocked memory, and haven't run the new AVX-512 LLR before, we strongly suggest running it before the challenge while you are monitoring the temperatures.

This app uses a lot of memory. It requires about 1.5 GB of swap space / virtual memory, and 750 MB of physical memory.
If you are using Digital Ocean or TheScience.cloud 3-core/1GB droplets, you can only run one task at a time.

Multi-threading is supported and IS recommended. (GCW tasks on one CPU core will take 6-7 days on fast/newer computers and 2 weeks+ on slower/older computers.)

Those looking to maximize their computer's performance during this challenge, or when running LLR in general, may find this information useful.

• Your mileage may vary. Before the challenge starts, take some time and experiment and see what works best on your computer.
  
• If you have a CPU with hyperthreading or SMT, either turn off this feature in the BIOS, or set BOINC to use 50% of the processors.
  
  
  • If you're using a GPU for other tasks, it may be beneficial to leave hyperthreading on in the BIOS and instead tell BOINC to use 50% of the CPU's. This will allow one of the hyperthreads to service the GPU.

  
  

• The new multi-threading system is now live. Click here to set the maximum number of threads. This will allow you to select multi-threading from the project preferences web page. No more app_config.xml. It works like this:
  
  
  • In the preferences selection, there are selections for "max jobs" and "max cpus", similar to the settings in app_config.
    
  • Unlike app_config, these two settings apply to ALL apps. You can't chose 1 thread for SGS and 4 for SoB. When you change apps, you need to change your multithreading settings if you want to run a different number of threads.
    
  • There will be individual settings for each venue (location).
    
  • This will eliminate the problem of BOINC downloading 1 task for every core.
    
  • The hyperthreading control isn't possible at this time.
    
  • The "max cpus" control will only apply to LLR apps. The "max jobs" control applies to all apps.

  
  

• If you want to continue to use app_config.xml for LLR tasks, you need to change it if you want it to work. Please see this message for more information.
  
• Some people have observed that when using multithreaded LLR, hyperthreading is actually beneficial. We encourage you to experiment and see what works best for you.

Time zone converter:

The World Clock - Time Zone Converter

NOTE: The countdown clock on the front page uses the host computer time. Therefore, if your computer time is off, so will the countdown clock. For precise timing, use the UTC Time in the data section at the very top, above the countdown clock.

Scoring Information

Scores will be kept for individuals and teams. Only tasks issued AFTER 21st October 2021 00:00 UTC and received BEFORE 28th October 2021 00:00 UTC will be considered for credit. We will be using the same scoring method as we currently use for BOINC credits. A quorum of 2 is NOT needed to award Challenge score - i.e. no double checker. Therefore, each returned result will earn a Challenge score. Please note that if the result is eventually declared invalid, the score will be removed.

At the Conclusion of the Challenge

We kindly ask users "moving on" to ABORT their tasks instead of DETACHING, RESETTING, or PAUSING.

ABORTING tasks allows them to be recycled immediately; thus a much faster "clean up" to the end of an LLR Challenge. DETACHING, RESETTING, and PAUSING tasks causes them to remain in limbo until they EXPIRE. Therefore, we must wait until tasks expire to send them out to be completed.

Please consider either completing what's in the queue or ABORTING them. Thank you. :)

About the Generalized Cullen/Woodall Prime Search

A Cullen number (first studied by Reverend James Cullen in 1905) is a number of the form n * 2^n + 1. A Woodall number (first studied by Allan Cunningham and H.J. Woodall in 1917) is a number of the form n * 2^n - 1.

Generalized Cullen and Woodall numbers are of the form n * b^n + 1 and n * b^n - 1, respectively, where n + 2 > b.

A couple of years ago PrimeGrid moved its search for Generalized Cullen and Generalized Woodall primes from PRPNet to BOINC. A double-check of all ranges searched by PRPNet has been completed by PrimeGrid, and is continuing on with new work running multiple bases (b values) concurrently and incrementing through n values.

PrimeGrid is sieving to a much larger n than has been previously done. The largest candidates will be in excess of 15,000,000 digits, and will be the same size as the largest candidates in the Seventeen or Bust project.

Once PrimeGrid finds a Generalized Cullen or Woodall on a base, it stops looking for Generalized Cullen or Woodall primes on that base, depending on the type found. For all the current bases, PrimeGrid will initially be searching only for Generalized Cullen Primes. For detail about the bases PrimeGrid will be searching (and has searched), you can go here: http://www.primegrid.com/forum_thread.php?id=3008&nowrap=true#30718.

In addition to having found the largest known Cullen prime http://primes.utm.edu/primes/page.php?id=89536 and largest known Woodall prime http://primes.utm.edu/primes/page.php?id=124539, PrimeGrid has found the largest known Generalized Cullen prime, http://primes.utm.edu/primes/page.php?id=124515 and the 4th largest known Generalized Woodall prime http://primes.utm.edu/primes/page.php?id=98862.

For more information on Generalized Cullen and Woodall Numbers, you can go here: http://primes.utm.edu/top20/page.php?id=42 and here: http://primes.utm.edu/top20/page.php?id=45.

What is LLR?

The Lucas-Lehmer-Riesel (LLR) test is a primality test for numbers of the form N = k*2^n − 1, with 2^n > k. Also, LLR is a program developed by Jean Penne that can run the LLR-tests. It includes the Proth test to perform +1 tests and PRP to test non base 2 numbers. See also:

• Lucas-Lehmer-Riesel test (WIKI)
  
• Download LLR by Jean Penné
  

What is LLR2?

LLR2 is an improvement to the LLR application developed by our very own Pavel Atnashev and stream. It utilizes Gerbicz checks to enable the Fast DoubleCheck feature, which will nearly double the speed of PrimeGrid's progress on the projects it's applied to. For more information, see this forum post.
____________

Time flies like an arrow. Fruit flies like a banana.

What is the current FFT range for tasks?
____________
Eating more cheese on Thursdays.

What is the current FFT range for tasks?

Thanks to you both. Trying to get a picture of where to set multithreading since I haven't GCW'd in awhile. Can be a challenge (heh) with the multiple bases and +/-1. The two tasks I completed came in 1792k and 2304k. It's so easy to just set MT to all the cores when core counts are low. But it looks like my mid-core CPUs will use them all with some cache to spare and my high(er)-core will do better with two tasks at a time.

For anyone who wants to know, 2304k would need about 18MB of cache to fit inside the CPU. Just a wee bit awkward for Ryzens.
____________
Eating more cheese on Thursdays.

Those look like proof tasks--the credit is way too low to be a full LLR task.

Hi! I already returned a task around 3:30 UTC (llrGCW_385473577_1) and it's checked, but I don't appear in the list:

https://www.primegrid.com/challenge/2021_7/top_users.html

(now updated at 5:00 UTC). Is there anything wrong?

One day down! Here are the task stats:
Challenge: Martin Gardner's Birthday
App: 30 (GCW-LLR)
Fast DC tasks are NOT included.
(As of 2021-10-22 00:35:18 UTC)

14533 tasks have been sent out. [CPU/GPU/anonymous_platform: 14533 (100%) / 0 (0%) / 0 (0%)]

Of those tasks that have been sent out:

1836 (13%) were aborted. [1836 (13%) / 0 (0%) / 0 (0%)]
68 (0%) came back with some kind of an error. [68 (0%) / 0 (0%) / 0 (0%)]
951 (7%) have returned a successful result. [951 (7%) / 0 (0%) / 0 (0%)]
11678 (80%) are still in progress. [11678 (80%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

676 (71%) are pending validation. [676 (71%) / 0 (0%) / 0 (0%)]
275 (29%) have been successfully validated. [275 (29%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=6031560. The leading edge was at n=5844056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.21% as much as it had prior to the challenge!
____________

Time flies like an arrow. Fruit flies like a banana.

Day 2 stats:
Challenge: Martin Gardner's Birthday
App: 30 (GCW-LLR)
Fast DC tasks are NOT included.
(As of 2021-10-22 23:04:59 UTC)

22264 tasks have been sent out. [CPU/GPU/anonymous_platform: 22264 (100%) / 0 (0%) / 0 (0%)]

Of those tasks that have been sent out:

2456 (11%) were aborted. [2456 (11%) / 0 (0%) / 0 (0%)]
87 (0%) came back with some kind of an error. [87 (0%) / 0 (0%) / 0 (0%)]
2715 (12%) have returned a successful result. [2715 (12%) / 0 (0%) / 0 (0%)]
17006 (76%) are still in progress. [17006 (76%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

2015 (74%) are pending validation. [2015 (74%) / 0 (0%) / 0 (0%)]
700 (26%) have been successfully validated. [700 (26%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=6147116. The leading edge was at n=5844056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.19% as much as it had prior to the challenge!
____________

Time flies like an arrow. Fruit flies like a banana.

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=6147116. The leading edge was at n=5844056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.19% as much as it had prior to the challenge!

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=6147116. The leading edge was at n=5844056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.19% as much as it had prior to the challenge!

How is n=6147116 being determined as the leading edge? I don't see numbers similar to that one anywhere on https://www.primegrid.com/stats_gcw_llr.php

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=6147116. The leading edge was at n=5844056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.19% as much as it had prior to the challenge!

How is n=6147116 being determined as the leading edge? I don't see numbers similar to that one anywhere on https://www.primegrid.com/stats_gcw_llr.php

That n=6147116 probably refers to the candidate 3073558 * 49^3073558 + 1, which is rewritten as 3073558 * 7^6147116 + 1 before being crunched. (We do the same thing for GCW b=121, and we did for b=25 until that search ended with tng's prime.) Doubling these exponents makes them the largest ones currently used in GCW.

It's a bit misleading to state GCW leading edges in terms of n, as GCW doesn't search in n order--it searches in size order. But all of the different leading edges (one for each b) are proportional to each other, so at least the percentages are meaningful.

Day 3:
Challenge: Martin Gardner's Birthday
App: 30 (GCW-LLR)
Fast DC tasks are NOT included.
(As of 2021-10-24 00:58:38 UTC)

27293 tasks have been sent out. [CPU/GPU/anonymous_platform: 27293 (100%) / 0 (0%) / 0 (0%)]

Of those tasks that have been sent out:

3034 (11%) were aborted. [3034 (11%) / 0 (0%) / 0 (0%)]
331 (1%) came back with some kind of an error. [331 (1%) / 0 (0%) / 0 (0%)]
5193 (19%) have returned a successful result. [5193 (19%) / 0 (0%) / 0 (0%)]
18735 (69%) are still in progress. [18735 (69%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

2058 (40%) are pending validation. [2058 (40%) / 0 (0%) / 0 (0%)]
3135 (60%) have been successfully validated. [3135 (60%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=6216372. The leading edge was at n=5844056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 6.37% as much as it had prior to the challenge!
____________

Time flies like an arrow. Fruit flies like a banana.

Day 4:

Challenge: Martin Gardner's Birthday
App: 30 (GCW-LLR)
Fast DC tasks are NOT included.
(As of 2021-10-24 23:31:16 UTC)

31202 tasks have been sent out. [CPU/GPU/anonymous_platform: 31202 (100%) / 0 (0%) / 0 (0%)]

Of those tasks that have been sent out:

3319 (11%) were aborted. [3319 (11%) / 0 (0%) / 0 (0%)]
348 (1%) came back with some kind of an error. [348 (1%) / 0 (0%) / 0 (0%)]
7258 (23%) have returned a successful result. [7258 (23%) / 0 (0%) / 0 (0%)]
20277 (65%) are still in progress. [20277 (65%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

2136 (29%) are pending validation. [2136 (29%) / 0 (0%) / 0 (0%)]
5122 (71%) have been successfully validated. [5122 (71%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=6276314. The leading edge was at n=5844056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 7.40% as much as it had prior to the challenge!
____________

Time flies like an arrow. Fruit flies like a banana.

Day 5 stats comin' at ya:

Challenge: Martin Gardner's Birthday
App: 30 (GCW-LLR)
Fast DC tasks are NOT included.
(As of 2021-10-26 00:20:03 UTC)

36210 tasks have been sent out. [CPU/GPU/anonymous_platform: 36210 (100%) / 0 (0%) / 0 (0%)]

Of those tasks that have been sent out:

4885 (13%) were aborted. [4885 (13%) / 0 (0%) / 0 (0%)]
378 (1%) came back with some kind of an error. [378 (1%) / 0 (0%) / 0 (0%)]
9638 (27%) have returned a successful result. [9638 (27%) / 0 (0%) / 0 (0%)]
21309 (59%) are still in progress. [21309 (59%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

2380 (25%) are pending validation. [2380 (25%) / 0 (0%) / 0 (0%)]
7258 (75%) have been successfully validated. [7258 (75%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=6329984. The leading edge was at n=5844056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 8.31% as much as it had prior to the challenge!
____________

Time flies like an arrow. Fruit flies like a banana.

How are the leading edge digits on the Subproject status page calculated? It says 4,796,754 is current leading edge digits which would correspond to n = 4306102 for base 13. It's very close to the minimal n in progress, also for the other bases. Is there something with the leading edge calculation?
____________
1281979 * 2^485014 + 1 is prime ... no further hits up to: n = 5,700,000

How are the leading edge digits on the Subproject status page calculated? It says 4,796,754 is current leading edge digits which would correspond to n = 4306102 for base 13. It's very close to the minimal n in progress, also for the other bases. Is there something with the leading edge calculation?

6 days down, one to go!

Challenge: Martin Gardner's Birthday
App: 30 (GCW-LLR)
Fast DC tasks are NOT included.
(As of 2021-10-26 23:50:23 UTC)

39462 tasks have been sent out. [CPU/GPU/anonymous_platform: 39462 (100%) / 0 (0%) / 0 (0%)]

Of those tasks that have been sent out:

9002 (23%) were aborted. [9002 (23%) / 0 (0%) / 0 (0%)]
401 (1%) came back with some kind of an error. [401 (1%) / 0 (0%) / 0 (0%)]
12356 (31%) have returned a successful result. [12356 (31%) / 0 (0%) / 0 (0%)]
17703 (45%) are still in progress. [17703 (45%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

3089 (25%) are pending validation. [3089 (25%) / 0 (0%) / 0 (0%)]
9267 (75%) have been successfully validated. [9267 (75%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=6347216. The leading edge was at n=5844056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 8.61% as much as it had prior to the challenge!
____________

Time flies like an arrow. Fruit flies like a banana.

A few hours left in the challenge! Some friendly reminders... :)

At the Conclusion of the Challenge

When the challenge completes, we would prefer users "moving on" to finish those tasks they have downloaded, if not then please ABORT the WU's (and then UPDATE the PrimeGrid project) instead of DETACHING, RESETTING, or PAUSING.

ABORTING WU's allows them to be recycled immediately; thus a much faster "clean up" to the end of a Challenge. DETACHING, RESETTING, and PAUSING WU's causes them to remain in limbo until they EXPIRE. Therefore, we must wait until WU's expire to send them out to be completed.

Likewise, if you're shutting down the computer for an extended period of time, or deleting the VM (Virtual Machine), please ABORT all remaining tasks first. Also, be aware that merely shutting off a cloud server doesn't stop the billing. You have to destroy/delete the server if you don't want to continue to be charged for it.

Thank you!
____________

Time flies like an arrow. Fruit flies like a banana.

Since an LLR2 challenge like this one contains two very different types of tasks, I wonder if it would relevant and technically possible to split the column Tasks on the challenge leaderboard top_users.html into two columns, Main tasks and Proof tasks? /JeppeSN

Challenge ending? Guess it's time to spin up the home furnace...
____________
Eating more cheese on Thursdays.

Here are the final stats for the end of the challenge - phenomenal work! Cleanup is starting now.

Challenge: Martin Gardner's Birthday
App: 30 (GCW-LLR)
Fast DC tasks are NOT included.
(As of 2021-10-28 19:50:16 UTC)

44585 tasks have been sent out. [CPU/GPU/anonymous_platform: 44585 (100%) / 0 (0%) / 0 (0%)]

Of those tasks that have been sent out:

16185 (36%) were aborted. [16185 (36%) / 0 (0%) / 0 (0%)]
435 (1%) came back with some kind of an error. [435 (1%) / 0 (0%) / 0 (0%)]
15638 (35%) have returned a successful result. [15638 (35%) / 0 (0%) / 0 (0%)]
8453 (19%) are still in progress. [8453 (19%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

2364 (15%) are pending validation. [2364 (15%) / 0 (0%) / 0 (0%)]
13274 (85%) have been successfully validated. [13274 (85%) / 0 (0%) / 0 (0%)]
1 (0%) were invalid. [1 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=6347216. The leading edge was at n=5844056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 8.61% as much as it had prior to the challenge!
____________

Time flies like an arrow. Fruit flies like a banana.

Looks like in the last day a lot of tasks were aborted and recycled from computers that had grabbed too much work. Alas, but still overall very good progress over the course of the whole challenge.
____________

Cleanup Status:

Oct 29: 2122 tasks outstanding; 1606 affecting individual (229) scoring positions; 869 affecting team (50) scoring positions.
Oct 30: 1878 tasks outstanding; 1407 affecting individual (219) scoring positions; 748 affecting team (48) scoring positions.
Oct 31: 1433 tasks outstanding; 1054 affecting individual (198) scoring positions; 558 affecting team (40) scoring positions.
Nov 1: 866 tasks outstanding; 470 affecting individual (141) scoring positions; 219 affecting team (26) scoring positions.
Nov 2: 735 tasks outstanding; 363 affecting individual (122) scoring positions; 189 affecting team (23) scoring positions.
Nov 3: 548 tasks outstanding; 243 affecting individual (92) scoring positions; 121 affecting team (18) scoring positions.
Nov 4: 288 tasks outstanding; 135 affecting individual (60) scoring positions; 13 affecting team (9) scoring positions.
Nov 5: 166 tasks outstanding; 73 affecting individual (39) scoring positions; 7 affecting team (7) scoring positions.
Nov 6: 89 tasks outstanding; 27 affecting individual (23) scoring positions; 5 affecting team (5) scoring positions.
Nov 7: 45 tasks outstanding; 13 affecting individual (12) scoring positions; 0 affecting team (0) scoring positions.
Nov 8: 9 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Nov 9: 5 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Nov 10: 5 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Nov 11: 5 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Nov 12: 5 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Nov 13: 5 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Nov 14: 3 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Nov 15: 3 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
____________

Time flies like an arrow. Fruit flies like a banana.

Cleanup Status:
Nov 23: 1 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
____________

Time flies like an arrow. Fruit flies like a banana.

The results are final!

During these 7 days, we completed more than 14,000 tasks. No new primes were found during the challenge, but it brought a lot of needed attention to the GCW subproject, pushing the leading edge by about 9%. The challenge boosted the project's average output to 20 times typical.

105 teams and 443 individuals participated in the Challenge.

Top Three Individuals:
1. vaughan
2. tng
3. xii5ku


Top Three Teams:
1. TeAm AnandTech
2. Czech National Team
3. SETI.Germany

Thank you again to everyone. We really appreciate your participation and hope you had fun!
____________

Time flies like an arrow. Fruit flies like a banana.