Welcome to the Mathematics Awareness Month Challenge

The third Challenge of the 2018 Challenge series is a 5 day challenge to celebrate Mathematics and Statistics Awareness Month. The challenge is being offered on the Extended Sierpinski Problem (LLR) application.

Each April 55,000 mathematicians and scientists celebrate Mathematics and Statistics Awareness Month to increase public understanding and appreciation for mathematics and statistics. Starting in 2017 the month's theme is to celebrate mathematics and statistics and the diverse researchers and students in these fields who are contributing so much to furthering discoveries, solving problems, and finding beauty in our world.

College, University and high school departments, institutional public information offices, math clubs, student groups, related associations and interest groups are urged to organize and host activities in April for Mathematics and Statistics Awareness Month. Past activities have included workshops, competitions, exhibits, festivals, lectures, symposia, department open houses, math art exhibits, and math poetry readings. Some years, elected officials have issued proclamations, frequently in connection with special meetings and events arranged to observe the month.

To participate in the Challenge, please select only the Extended Sierpinski Problem LLR (ESP) project in your PrimeGrid preferences section. The challenge will begin 3rd April 2018 12:00 UTC and end 8th April 2018 12:00 UTC.

Application builds are available for Linux 32 and 64 bit, Windows 32 and 64 bit and MacIntel. Intel CPUs with AVX capabilities (Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Kaby Lake, Coffee Lake) will have a very large advantage, and Intel CPUs with FMA3 (Haswell, Broadwell, Skylake, Kaby Lake, Coffee Lake) will be the fastest.

ATTENTION: The primality program LLR is CPU intensive; so, it is vital to have a stable system with good cooling. It does not tolerate "even the slightest of errors." Please see this post for more details on how you can "stress test" your computer. Tasks on one CPU core will take ~12 hours on fast/newer computers and 2+ days on slower/older computers. If your computer is highly overclocked, please consider "stress testing" it. Sieving is an excellent alternative for computers that are not able to LLR. :)

Highly overclocked Haswell, Broadwell, Skylake, Kaby Lake or Coffee Lake (i.e., Intel Core i7, i5, and i3 -4xxx or better) computers running the application will see fastest times. Note that ESP is running the latest FMA3 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. If you have a Haswell, Broadwell, Skylake, Kaby Lake or Coffee Lake CPU, especially if it's overclocked or has overclocked memory, and haven't run the new FMA3 LLR before, we strongly suggest running it before the challenge while you are monitoring the temperatures.

Please, please, please make sure your machines are up to the task.

Multi-threading optimisation instructions

Those looking to maximise 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 an Intel CPU with hyperthreading, either turn off the hyperthreading 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.

  
  

• Use LLR's multithreaded mode. It requires a little bit of setup, but it's worth the effort. Follow these steps:
  
  
  
  • Create a app_config.xml file in the directory C:\ProgramData\BOINC\projects\www.primegrid.com\ (or wherever your BOINC data directory is located). For a quad core CPU, the file should contain the following contents. Change the two occurrences of "4" to the number of actual cores your computer has.
    
    
    <app_config> <app> <name>llrESP</name> <fraction_done_exact/> <max_concurrent>1</max_concurrent> </app> <app_version> <app_name>llrESP</app_name> <cmdline>-t 4</cmdline> <avg_ncpus>4</avg_ncpus> </app_version> </app_config>
    
    
  • After creating the file, click on "Options/Read config files". You should then restart BOINC or reboot.
    
  • The first time BOINC downloads an ESP task, it may act a little strange and download 4 tasks instead of 1. The run times on this first set of tasks may look a bit strange too. This is normal. This will also occur anytime BOINC downloads more than one task at a time. This can be avoided by setting "Use at most [ 1 ] % of the CPUs" before you download ESP tasks. After one task was downloaded, increase the percentage.
    
  • 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 3rd April 2018 12:00 UTC and received BEFORE 8th April 2018 12: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 Extended Sierpinski Project

Wacław Franciszek Sierpiński (14 March 1882 - 21 October 1969), a Polish mathematician, was known for outstanding contributions to set theory, number theory, theory of functions and topology. It is in number theory where we find the Sierpinski problem.

Basically, the Sierpinski problem is "What is the smallest Sierpinski number" and the prime Sierpinski problem is "What is the smallest 'prime' Sierpinski number?"

First we look at Proth numbers (named after the French mathematician François Proth). A Proth number is a number of the form k*2^n+1 where k is odd, n is a positive integer, and 2^n>k.

A Sierpinski number is an odd k such that the Proth number k*2^n+1 is not prime for all n. For example, 3 is not a Sierpinski number because n=2 produces a prime number (3*2^2+1=13). In 1962, John Selfridge proved that 78,557 is a Sierpinski number...meaning he showed that for all n, 78557*2^n+1 was not prime.

Most number theorists believe that 78,557 is the smallest Sierpinski number, but it hasn't yet been proven. In order to prove it, it has to be shown that every single k less than 78,557 is not a Sierpinski number, and to do that, some n must be found that makes k*2^n+1 prime.

The smallest proven 'prime' Sierpinski number is 271,129. In order to prove it, it has to be shown that every single 'prime' k less than 271,129 is not a Sierpinski number, and to do that, some n must be found that makes k*2^n+1 prime.

Should both of these problems be solved, k = 78557 will be established as the smallest Sierpinski number, and k = 271129 will be established as the smallest prime Sierpinski number. However, this would not prove that k = 271129 is the second provable Sierpinski number. Since the prime Sierpinski problem is testing all prime k's for 78557 < k < 271129, all that's needed is to test the composite k's for 78557 < k < 271129. Thus, the Extended Sierpinski Problem is established.

The following k's remain for each project:

• Waclaw Franciszek Sierpinski (WIKI)
  
• Sierpinski number / The Sierpinski problem (WIKI)
  
• The Sierpinski problem (Prothsearch)
  

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é
  

(Edouard Lucas: 1842-1891, Derrick H. Lehmer: 1905-1991, Hans Riesel: 1929-2014).
____________

app_config.xml applies also to Linux. Depending on your distribution, it should be in

You wrote name of this mathematician a bit incorrectly - special Polish characters are changed to their closest Latin equivalents. His name should be written as "Wacław Franciszek Sierpiński" (I bolded two changed letters).

WooHoo, my first Challenge

Now the questions...

Do you have app_config instructions for linux?
Are they needed for Linux?

Trying to clear my 'old' tasks now to be ready for April 3

PS. nice that you have a 12:00:00 UTC start, is that for everybody living on that side of the planet??? (just joking)

OK, so after a bit of playing, using PPSE as my guinea pig tasks I can see the following...

System is an i7 8700K with a GTX 1070Ti - no overclocking

System is set to only take PPSE tasks except for the GPU - it will take any task

1) Run all cores and multithread - runs 12 PPSE tasks each taking approx 24 minutes
2) Run all cores Boinc set to 50% CPU - runs 6 PPSE tasks each taking approx 11 minutes
3) Run with Boinc set to 50% and app_config - runs 1 task taking approx 3 minutes 40 secs

So, for the challenge, do I want to do as many tasks as possible - option 2 or do I want to complete a task in the quickest time possible - option 3?

I'm also making the assumption that what I see for PPSE tasks will be similar for the challenge tasks

Thoughts?

Thanx

Dad

I am interested in participating and tried to put the xml in the directory you gave but couldn't find it. Is it possible to just create a projects folder and stick it in there?

ESP's been slowly rising, from 634 tasks completed per day till 994 currently.
Expecting a big leap as the Challenge begins:

8 minutes till Challenge start. Let's hope for a prime!

8 minutes till Challenge start. Let's hope for a prime!

.....and we're off :)
____________
My lucky numbers 1059094^1048576+1 and 224584605939537911+81292139*23#*n for n=0..26

8 minutes till Challenge start. Let's hope for a prime!

In any project. Haha
We found a Woodall prime in the 321 challenge. Will we see an SR5 prime in the ESP challenge? Maybe a PSP prime?

8 minutes till Challenge start. Let's hope for a prime!

In any project. Haha
We found a Woodall prime in the 321 challenge. Will we see an SR5 prime in the ESP challenge? Maybe a PSP prime?

Ummmmmmmmmmmmm...

Looks like we've eliminated one K from the Extended Sierpinski Problem during the first couple of hours of the challenge.

It's so bonkers that it happened right at the start too. Someone keeping to ESP while everyone was busy with 321 could have maybe gotten it.

It's so bonkers that it happened right at the start too. Someone keeping to ESP while everyone was busy with 321 could have maybe gotten it.

It's so bonkers that it happened right at the start too. Someone keeping to ESP while everyone was busy with 321 could have maybe gotten it.

It was returned within 4 hours of the start. It was sent out in the first 10 minutes of the challenge, and the prime finder and the wingman got the task within seconds of each other.

That being said, if it weren't for the challenge, that task wouldn't have been sent out for another week or two. Even with large tasks like these, thousands of tasks get sent out in the first few minutes of a challenge.

193997*2^11452891+1

Congratulations tng*!

GDB is the double checker.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

193997*2^11452891+1

Congratulations tng*!

GDB is the double checker.

193997*2^11452891+1

Congratulations tng*!

GDB is the double checker.

How are the chances of reopening ESP SV looking like with one less k in the pipeline?

Very good job.

Eliminating K=193997 at the beginning of the challenge will push ESP even a bit more because we will process a bit more candidates for remaining K's.

Last K was eliminated in early 2015, it was first mega-ESP back then.
____________
My stats

193997*2^11452891+1

Congratulations tng*!

GDB is the double checker.

After 1 day:


Challenge: Mathematics Awareness Month
App: 20 (ESP-LLR)
(As of 2018-04-04 12:57:43 UTC)

10568 tasks have been sent out. [CPU/GPU/anonymous_platform: 10508 (99%) / 0 (0%) / 60 (1%)]

Of those tasks that have been sent out:

749 (7%) came back with some kind of an error. [749 (7%) / 0 (0%) / 0 (0%)]
2838 (27%) have returned a successful result. [2792 (26%) / 0 (0%) / 46 (0%)]
6981 (66%) are still in progress. [6967 (66%) / 0 (0%) / 14 (0%)]

Of the tasks that have been returned successfully:

1928 (68%) are pending validation. [1897 (67%) / 0 (0%) / 31 (1%)]
901 (32%) have been successfully validated. [886 (31%) / 0 (0%) / 15 (1%)]
3 (0%) were invalid. [3 (0%) / 0 (0%) / 0 (0%)]
6 (0%) are inconclusive. [6 (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=11572832. The leading edge was at n=11413664 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.39% as much as it had prior to the challenge!


Normally this is the part where I say some variation of "participation is great and maybe we'll find a prime". Participation IS great, of course, but we've already found an ESP prime and eliminated a K. So...

Participation is great! Can we find a SECOND prime???
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

It's a very simplistic calculation.

If the leading edge was at 2 million at the start of the challenge, and it's now at 3 million, then the increase is 50%.

It is not "work" that's being measured, only the increase in the value of the leading edge.

____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Have you stopped sending out new work with multiplier 193997 already? At what time did that happen?

I think the tasks related to 193997 that have already been sent out, will still finish normally? And if no second work unit has been sent yet, or if results are inconclusive, you will still keep sending out work with the relevant n and with k=193997 until the status of each task is certain?

/JeppeSN

It looks like this was a fairly low weight k. (2nd lowest left maybe?)

I can't remember whether if we had our choice we'd eliminate a low or high weight k. Can someone remind me which we prefer and why?

Thanks!

Since PrimeGrid began, we have found 11 primes larger than 3 million digits.

Three of them have been found in the last 15 days.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

It looks like this was a fairly low weight k. (2nd lowest left maybe?)

I can't remember whether if we had our choice we'd eliminate a low or high weight k. Can someone remind me which we prefer and why?

Thanks!

I hope this post is comprehensible enough. I've been meaning to gather all my thoughts on this into an educational math video of some sort, maybe one day I'll get to it. In this post omitted A LOT of what I want to talk about too. It's fun stuff.

But I'm still not sure I'm sold on which we'd rather eliminate. . .

Argument for eliminating High Weight:
It eliminates a ton of candidates, and allows us to get to a higher n faster.

Argument for eliminating a Low Weight:
Each check at a given prime value has roughly the same chance of being prime, and takes a similar time to check. We like the high weight because it gives us more chances to find a prime without the computation getting substantially more difficult. If it's going to take 10,000 tests to find a prime on each of them, the 10,000th test is going to be a lot harder on a low weight.

After 2 days:


Challenge: Mathematics Awareness Month
App: 20 (ESP-LLR)
(As of 2018-04-05 14:37:21 UTC)

15801 tasks have been sent out. [CPU/GPU/anonymous_platform: 15690 (99%) / 0 (0%) / 111 (1%)]

Of those tasks that have been sent out:

1338 (8%) came back with some kind of an error. [1338 (8%) / 0 (0%) / 0 (0%)]
7102 (45%) have returned a successful result. [7003 (44%) / 0 (0%) / 99 (1%)]
7361 (47%) are still in progress. [7349 (47%) / 0 (0%) / 12 (0%)]

Of the tasks that have been returned successfully:

3444 (48%) are pending validation. [3400 (48%) / 0 (0%) / 44 (1%)]
3628 (51%) have been successfully validated. [3574 (50%) / 0 (0%) / 54 (1%)]
10 (0%) were invalid. [10 (0%) / 0 (0%) / 0 (0%)]
20 (0%) are inconclusive. [19 (0%) / 0 (0%) / 1 (0%)]

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


Time for a second ESP prime yet? Sometimes they come in bunches...
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

After three days:


Challenge: Mathematics Awareness Month
App: 20 (ESP-LLR)
(As of 2018-04-06 11:52:57 UTC)

19843 tasks have been sent out. [CPU/GPU/anonymous_platform: 19689 (99%) / 0 (0%) / 154 (1%)]

Of those tasks that have been sent out:

1567 (8%) came back with some kind of an error. [1567 (8%) / 0 (0%) / 0 (0%)]
10914 (55%) have returned a successful result. [10772 (54%) / 0 (0%) / 142 (1%)]
7362 (37%) are still in progress. [7350 (37%) / 0 (0%) / 12 (0%)]

Of the tasks that have been returned successfully:

3981 (36%) are pending validation. [3920 (36%) / 0 (0%) / 61 (1%)]
6890 (63%) have been successfully validated. [6809 (62%) / 0 (0%) / 81 (1%)]
23 (0%) were invalid. [23 (0%) / 0 (0%) / 0 (0%)]
20 (0%) are inconclusive. [20 (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=11717413. The leading edge was at n=11413664 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.66% as much as it had prior to the challenge!


Two days left; can we eliminate a second k?
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Hello

Under 300 participants.
That's a small number.
The challenge wasn't even advertised in my team forum.
Maybe a large number of PrimeGriders have been reluctant to abort running-on long tasks.

With one day to go:


Challenge: Mathematics Awareness Month
App: 20 (ESP-LLR)
(As of 2018-04-07 13:19:30 UTC)

24098 tasks have been sent out. [CPU/GPU/anonymous_platform: 23894 (99%) / 0 (0%) / 204 (1%)]

Of those tasks that have been sent out:

2237 (9%) came back with some kind of an error. [2237 (9%) / 0 (0%) / 0 (0%)]
15388 (64%) have returned a successful result. [15194 (63%) / 0 (0%) / 194 (1%)]
6473 (27%) are still in progress. [6463 (27%) / 0 (0%) / 10 (0%)]

Of the tasks that have been returned successfully:

4211 (27%) are pending validation. [4157 (27%) / 0 (0%) / 54 (0%)]
11116 (72%) have been successfully validated. [10976 (71%) / 0 (0%) / 140 (1%)]
41 (0%) were invalid. [41 (0%) / 0 (0%) / 0 (0%)]
20 (0%) are inconclusive. [20 (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=11778590. The leading edge was at n=11413664 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.20% as much as it had prior to the challenge!


Four days are done and one remains. Over fifteen thousand tasks have been returned. To put that in perspective, normal is about 200 each day. So far we've done almost exactly 20 times normal. And, of course, we eliminated one of the remaining k's.

Is there another prime hiding in the last day's tasks?
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

The end is near! The end of the challenge, that is. So it's time to remind everyone...

At the Conclusion of the Challenge

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. Thank you!


____________
My lucky number is 75898⁵²⁴²⁸⁸+1

We're done!

Challenge: Mathematics Awareness Month
App: 20 (ESP-LLR)
(As of 2018-04-08 12:01:43 UTC)

27624 tasks have been sent out. [CPU/GPU/anonymous_platform: 27377 (99%) / 0 (0%) / 247 (1%)]

Of those tasks that have been sent out:

3971 (14%) came back with some kind of an error. [3971 (14%) / 0 (0%) / 0 (0%)]
19615 (71%) have returned a successful result. [19373 (70%) / 0 (0%) / 242 (1%)]
4033 (15%) are still in progress. [4028 (15%) / 0 (0%) / 5 (0%)]

Of the tasks that have been returned successfully:

3759 (19%) are pending validation. [3704 (19%) / 0 (0%) / 55 (0%)]
15760 (80%) have been successfully validated. [15573 (79%) / 0 (0%) / 187 (1%)]
58 (0%) were invalid. [58 (0%) / 0 (0%) / 0 (0%)]
38 (0%) are inconclusive. [38 (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=11820458. The leading edge was at n=11413664 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.56% as much as it had prior to the challenge!


ESP processing was about 20x normal, and we found the first ESP prime in over three years! How long will it take to find primes for the remaining 10 k's?

There's no BOINC challenge in May. The next scheduled BOINC challenge will be an SR5 challenge in mid-June. It is likely, however, that we'll be starting a double check of some old TRP that was only single checked under "Adaptive Replication."

Thanks everyone for participating!

(Information about the cleanup will be coming soon.)
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

I expect the cleanup to take 3 to 4 weeks.

Cleanup:

Apr: 8: Mathematics Awareness Month: 3789 tasks outstanding; 3608 affecting individual (271) scoring positions; 2612 affecting team (58) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

WooHoo,

Had a great time, however...

I can no longer run more than 2 CPU tasks at once???

I HAD modified my APP_CONFIG file and changed the BOINC preference to 8.33%, now that the challenge is over I have set BOINC back to 100% and tried deleting the APP_CONFIG and/or changing APP_CONFIG to
<app_config>
<app>
<name>llrESP</name>
<fraction_done_exact/>
<max_concurrent>6</max_concurrent>
</app>
<app_version>
<app_name>llrESP</app_name>
<cmdline>-t 6</cmdline>
<avg_ncpus>6</avg_ncpus>
</app_version>
</app_config>

but all I get is 2 tasks running of the 5 it has downloaded

It's like the APP_CONFIG has persisted

Any thoughts???

Thanx

Dad

<max_concurrent>6</max_concurrent>

<cmdline>-t 6</cmdline>
<avg_ncpus>6</avg_ncpus>

You're correct Michael, I have no Idea what these commands do.

I have an i7 8700k - 6 cores and multithreading turned ON

Before this challenge I could run 12 simultaneous WU's, now I can run 2 of the 5 downloaded

I thought deleting the app_config would fix it, obviously not

Dad

I expect the cleanup to take 3 to 4 weeks.

Cleanup:

Apr 8: Mathematics Awareness Month: 3789 tasks outstanding; 3608 affecting individual (271) scoring positions; 2612 affecting team (58) scoring positions.
Apr 9: Mathematics Awareness Month: 2162 tasks outstanding; 1586 affecting individual (238) scoring positions; 893 affecting team (40) scoring positions.
Apr 10: Mathematics Awareness Month: 1427 tasks outstanding; 998 affecting individual (210) scoring positions; 379 affecting team (34) scoring positions.
Apr 11: Mathematics Awareness Month: 1150 tasks outstanding; 745 affecting individual (193) scoring positions; 302 affecting team (30) scoring positions.
Apr 12: Mathematics Awareness Month: 884 tasks outstanding; 537 affecting individual (166) scoring positions; 77 affecting team (23) scoring positions.
Apr 13: Mathematics Awareness Month: 562 tasks outstanding; 288 affecting individual (119) scoring positions; 20 affecting team (10) scoring positions.
Apr 14: Mathematics Awareness Month: 417 tasks outstanding; 190 affecting individual (91) scoring positions; 14 affecting team (7) scoring positions.
Apr 15: Mathematics Awareness Month: 300 tasks outstanding; 132 affecting individual (66) scoring positions; 11 affecting team (5) scoring positions.
Apr 16: Mathematics Awareness Month: 207 tasks outstanding; 89 affecting individual (51) scoring positions; 5 affecting team (4) scoring positions.
Apr 17: Mathematics Awareness Month: 126 tasks outstanding; 38 affecting individual (32) scoring positions; 4 affecting team (3) scoring positions.
Apr 18: Mathematics Awareness Month: 94 tasks outstanding; 22 affecting individual (21) scoring positions; 2 affecting team (2) scoring positions.
Apr 19: Mathematics Awareness Month: 62 tasks outstanding; 14 affecting individual (14) scoring positions; 1 affecting team (1) scoring positions.
Apr 20: Mathematics Awareness Month: 42 tasks outstanding; 8 affecting individual (8) scoring positions; 1 affecting team (1) scoring positions.
Apr 21: Mathematics Awareness Month: 33 tasks outstanding; 6 affecting individual (6) scoring positions; 1 affecting team (1) scoring positions.
Apr 22: Mathematics Awareness Month: 25 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Apr 23: Mathematics Awareness Month: 23 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Apr 24: Mathematics Awareness Month: 20 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Apr 25: Mathematics Awareness Month: 17 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

The results are final!

Special congratulations to tng* for finding the prime 193997*2^11452891+1 and so elimiating one of the ESP k's!

Top 3 individuals:

1: zunewantan
2: xii5ku
3: Scott Brown

Top 3 teams:

1: Aggie The Pew
2: Czech National Team
3: SETI.Germany

Congratulations to the winners, and well done to everyone who participated.
See you at the World Cup Challenge!
____________

Top 3 individuals:

I think there is a little copy and paste error in this list. B-)