Welcome to the Lennart Vogel Honorary Challenge

The fifth Challenge of the 2019 Challenge series is a special 7 day challenge to honour Lennart Vogel and his enormous contributions to Primegrid. The challenge is being offered on the Extended Sierpinski Problem (ESP) (LLR) application.

Lennart Vogel of Sweden is one of the giants in the Prime Hunting Universe. Lennart SM5YMT started at Primegrid in May 2007 and is well known for his Bugs Bunny profile picture. Many a time I would see the Bugs Bunny and look forward to what was written. Lennart has found 22 K's, the first base 13 GW, won yellow jersey in the 2009 and 2010 Tour de Primes for most primes found, polka dot in 2009 and green jersey for highest prime score in 2010. He was member of the PrimeSearchTeam, keen Admin loading up new search ranges and guiding light on new projects through the Project Staging Area, advancing project goals with his own unique style. Lennart's profile writings:

Your personal background.
I am a computer technian. Doing work on lots off computersystem.
Live in Sweden out on the country.
Hobies Boat on our lake, Hamradio, My call SM5YMT.
Btw i am 53 years old...

Your opinions about PrimeGrid
I like math so this is a projekt for me.
PrimGrid is running well, Many choices.
Any suggestions? Yes! Wy not software for Mac ?
Lennart

Please share your remembrances of Lennart in this thread as the challenge progresses.

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 August 2019 00:00 UTC and end at 10th August 2019 00:00 UTC.

Application builds are available for Linux 32 and 64 bit, Windows 32 and 64 bit and MacIntel. Intel CPUs with FMA3 capabilities (Sandy Bridge, Ivy Bridge, Haswell, Broadwell, Skylake, Kaby Lake, Coffee Lake) 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.

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 1 day on fast/newer computers and 4 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 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. 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.

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/> </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 a 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 August 2019 00:00 UTC and received BEFORE 10th August 2019 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 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).
____________

Note that PPS 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. [/b]

Roger wrote:

dannyridel wrote:

...
Note that PPS 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.
...

PPS?
I thought that this was an ESP project?

I guess it should be ESP instead of PPS (probably a side effect of "copy-and-paste" from the last challenge)

Did anyone ever figure out what happened to him?

Did anyone ever figure out what happened to him?

.......and the SGS prime rainfall has started, as people count down to the challenge on SGS :)
____________
My lucky numbers 1059094^1048576+1 and 224584605939537911+81292139*23#*n for n=0..26

Sorry, we've been trying to protect Lennart's privacy. There's probably no point in doing that anymore.

Around the beginning of 2015, Lennart Vogel suffered a stroke. He was not able to speak or communicate. The prognosis at the time was not good and he was not expected to recover.

We have had no additional information since then.

Of course, our thoughts and prayers go out to Lennart and his family.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Sorry, we've been trying to protect Lennart's privacy. There's probably no point in doing that anymore.

Around the beginning of 2015, Lennart Vogel suffered a stroke. He was not able to speak or communicate. The prognosis at the time was not good and he was not expected to recover.

We have had no additional information since then.

Of course, our thoughts and prayers go out to Lennart and his family.

I am expecting we'll break n=13M during this challenge. Last prime was at n=11,452,891.

At the present rate it looks like we may actually break n=13M before the challenge starts!

n=13M for k=238411 is 3,913,396 digits, and we are 3,910,390 right now. Given that we've been doing a few thousand digits per day for the past week or so it will be a close call whether n=13M is passed moments before, or moments after, the challenge begins.

Either way, a great milestone for the search! Best of luck in the challenge everyone! :)

Regards,
Kellen

The current highest n sent out is now 13003377.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

After 1 day...


Challenge: Lennart Vogel Honorary
App: 20 (ESP-LLR)
(As of 2019-08-04 01:39:44 UTC)

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

Of those tasks that have been sent out:

722 (7%) were aborted. [722 (7%) / 0 (0%) / 0 (0%)]
28 (0%) came back with some kind of an error. [28 (0%) / 0 (0%) / 0 (0%)]
2196 (22%) have returned a successful result. [2193 (22%) / 0 (0%) / 3 (0%)]
7125 (71%) are still in progress. [7123 (71%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

1595 (73%) are pending validation. [1592 (72%) / 0 (0%) / 3 (0%)]
587 (27%) have been successfully validated. [587 (27%) / 0 (0%) / 0 (0%)]
3 (0%) were invalid. [3 (0%) / 0 (0%) / 0 (0%)]
11 (1%) are inconclusive. [11 (1%) / 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=13171484. The leading edge was at n=13016388 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.19% as much as it had prior to the challenge!

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

After 2 days...


Challenge: Lennart Vogel Honorary
App: 20 (ESP-LLR)
(As of 2019-08-05 00:05:58 UTC)

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

Of those tasks that have been sent out:

1146 (8%) were aborted. [1146 (8%) / 0 (0%) / 0 (0%)]
90 (1%) came back with some kind of an error. [90 (1%) / 0 (0%) / 0 (0%)]
5517 (38%) have returned a successful result. [5510 (38%) / 0 (0%) / 7 (0%)]
7650 (53%) are still in progress. [7648 (53%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

3044 (55%) are pending validation. [3040 (55%) / 0 (0%) / 4 (0%)]
2432 (44%) have been successfully validated. [2429 (44%) / 0 (0%) / 3 (0%)]
10 (0%) were invalid. [10 (0%) / 0 (0%) / 0 (0%)]
31 (1%) are inconclusive. [31 (1%) / 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=13234998. The leading edge was at n=13016388 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.68% as much as it had prior to the challenge!

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

After 3 days...


Challenge: Lennart Vogel Honorary
App: 20 (ESP-LLR)
(As of 2019-08-06 00:23:42 UTC)

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

Of those tasks that have been sent out:

2737 (14%) were aborted. [2737 (14%) / 0 (0%) / 0 (0%)]
310 (2%) came back with some kind of an error. [310 (2%) / 0 (0%) / 0 (0%)]
9420 (50%) have returned a successful result. [9409 (50%) / 0 (0%) / 11 (0%)]
6534 (34%) are still in progress. [6532 (34%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

3953 (42%) are pending validation. [3947 (42%) / 0 (0%) / 6 (0%)]
5344 (57%) have been successfully validated. [5339 (57%) / 0 (0%) / 5 (0%)]
44 (0%) were invalid. [44 (0%) / 0 (0%) / 0 (0%)]
79 (1%) are inconclusive. [79 (1%) / 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=13296498. The leading edge was at n=13016388 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.15% as much as it had prior to the challenge!

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

After 4 days...


Challenge: Lennart Vogel Honorary
App: 20 (ESP-LLR)
(As of 2019-08-06 23:56:08 UTC)

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

Of those tasks that have been sent out:

3077 (13%) were aborted. [3077 (13%) / 0 (0%) / 0 (0%)]
357 (2%) came back with some kind of an error. [357 (2%) / 0 (0%) / 0 (0%)]
13321 (56%) have returned a successful result. [13306 (56%) / 0 (0%) / 15 (0%)]
7007 (29%) are still in progress. [7005 (29%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

3914 (29%) are pending validation. [3908 (29%) / 0 (0%) / 6 (0%)]
9217 (69%) have been successfully validated. [9208 (69%) / 0 (0%) / 9 (0%)]
88 (1%) were invalid. [88 (1%) / 0 (0%) / 0 (0%)]
102 (1%) are inconclusive. [102 (1%) / 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=13353744. The leading edge was at n=13016388 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.59% as much as it had prior to the challenge!

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

5 days complete, 2 to go...


Challenge: Lennart Vogel Honorary
App: 20 (ESP-LLR)
(As of 2019-08-08 00:15:19 UTC)

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

Of those tasks that have been sent out:

3337 (12%) were aborted. [3337 (12%) / 0 (0%) / 0 (0%)]
367 (1%) came back with some kind of an error. [367 (1%) / 0 (0%) / 0 (0%)]
17260 (61%) have returned a successful result. [17241 (60%) / 0 (0%) / 19 (0%)]
7561 (27%) are still in progress. [7559 (26%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

4278 (25%) are pending validation. [4273 (25%) / 0 (0%) / 5 (0%)]
12742 (74%) have been successfully validated. [12728 (74%) / 0 (0%) / 14 (0%)]
127 (1%) were invalid. [127 (1%) / 0 (0%) / 0 (0%)]
113 (1%) are inconclusive. [113 (1%) / 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=13430594. The leading edge was at n=13016388 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.18% as much as it had prior to the challenge!

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

6 days done, 1 to do!


Challenge: Lennart Vogel Honorary
App: 20 (ESP-LLR)
(As of 2019-08-09 00:04:45 UTC)

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

Of those tasks that have been sent out:

3667 (11%) were aborted. [3667 (11%) / 0 (0%) / 0 (0%)]
383 (1%) came back with some kind of an error. [383 (1%) / 0 (0%) / 0 (0%)]
21255 (65%) have returned a successful result. [21232 (65%) / 0 (0%) / 23 (0%)]
7513 (23%) are still in progress. [7511 (23%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

4557 (21%) are pending validation. [4551 (21%) / 0 (0%) / 6 (0%)]
16437 (77%) have been successfully validated. [16420 (77%) / 0 (0%) / 17 (0%)]
160 (1%) were invalid. [160 (1%) / 0 (0%) / 0 (0%)]
101 (0%) are inconclusive. [101 (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=13499606. The leading edge was at n=13016388 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.71% as much as it had prior to the challenge!

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

8 hours to go!


Challenge: Lennart Vogel Honorary
App: 20 (ESP-LLR)
(As of 2019-08-09 16:17:20 UTC)

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

Of those tasks that have been sent out:

6315 (17%) were aborted. [6315 (17%) / 0 (0%) / 0 (0%)]
427 (1%) came back with some kind of an error. [427 (1%) / 0 (0%) / 0 (0%)]
23955 (64%) have returned a successful result. [23929 (64%) / 0 (0%) / 26 (0%)]
6819 (18%) are still in progress. [6817 (18%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

4527 (19%) are pending validation. [4520 (19%) / 0 (0%) / 7 (0%)]
19136 (80%) have been successfully validated. [19117 (80%) / 0 (0%) / 19 (0%)]
178 (1%) were invalid. [178 (1%) / 0 (0%) / 0 (0%)]
114 (0%) are inconclusive. [114 (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=13538082. The leading edge was at n=13016388 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 4.01% as much as it had prior to the challenge!

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

With eight hours remaining in the challenge, it's time to remind everyone...

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 ViM (Virtual Machine), please ABORT all remaining tasks first.

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

And we're done!

Final statistics:


Challenge: Lennart Vogel Honorary
App: 20 (ESP-LLR)
(As of 2019-08-10 00:05:33 UTC)

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

Of those tasks that have been sent out:

6695 (17%) were aborted. [6694 (17%) / 0 (0%) / 1 (0%)]
428 (1%) came back with some kind of an error. [428 (1%) / 0 (0%) / 0 (0%)]
25500 (66%) have returned a successful result. [25473 (66%) / 0 (0%) / 27 (0%)]
5780 (15%) are still in progress. [5780 (15%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

4237 (17%) are pending validation. [4231 (17%) / 0 (0%) / 6 (0%)]
20958 (82%) have been successfully validated. [20937 (82%) / 0 (0%) / 21 (0%)]
195 (1%) were invalid. [195 (1%) / 0 (0%) / 0 (0%)]
110 (0%) are inconclusive. [110 (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=13540746. The leading edge was at n=13016388 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 4.03% as much as it had prior to the challenge!


We didn't find a prime, but we did do over 14 times what we normally do. Incredible job everyone!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

The cleanup begins. I expect it to last between 3 and 6 weeks.

Status:
Aug 10 (start): Lennart Vogel Honorary: 4346 tasks outstanding; 4062 affecting individual (257) scoring positions; 2544 affecting team (57) scoring positions.
Aug 10: Lennart Vogel Honorary: 3755 tasks outstanding; 3501 affecting individual (252) scoring positions; 1165 affecting team (51) scoring positions.
Aug 11: Lennart Vogel Honorary: 3037 tasks outstanding; 2839 affecting individual (245) scoring positions; 887 affecting team (47) scoring positions.
Aug 12: Lennart Vogel Honorary: 2590 tasks outstanding; 2112 affecting individual (228) scoring positions; 751 affecting team (44) scoring positions.
Aug 13: Lennart Vogel Honorary: 2139 tasks outstanding; 1723 affecting individual (213) scoring positions; 622 affecting team (41) scoring positions.
Aug 14: Lennart Vogel Honorary: 1878 tasks outstanding; 1506 affecting individual (204) scoring positions; 535 affecting team (36) scoring positions.
Aug 15: Lennart Vogel Honorary: 1490 tasks outstanding; 1106 affecting individual (183) scoring positions; 294 affecting team (32) scoring positions.
Aug 16: Lennart Vogel Honorary: 1217 tasks outstanding; 883 affecting individual (169) scoring positions; 163 affecting team (25) scoring positions.
Aug 17: Lennart Vogel Honorary: 982 tasks outstanding; 660 affecting individual (150) scoring positions; 115 affecting team (18) scoring positions.
Aug 18: Lennart Vogel Honorary: 773 tasks outstanding; 487 affecting individual (132) scoring positions; 60 affecting team (15) scoring positions.
Aug 19: Lennart Vogel Honorary: 629 tasks outstanding; 361 affecting individual (115) scoring positions; 23 affecting team (11) scoring positions.
Aug 20: Lennart Vogel Honorary: 500 tasks outstanding; 258 affecting individual (99) scoring positions; 23 affecting team (11) scoring positions.
Aug 21: Lennart Vogel Honorary: 381 tasks outstanding; 167 affecting individual (78) scoring positions; 9 affecting team (7) scoring positions.
Aug 22: Lennart Vogel Honorary: 336 tasks outstanding; 146 affecting individual (72) scoring positions; 8 affecting team (6) scoring positions.
Aug 23: Lennart Vogel Honorary: 281 tasks outstanding; 116 affecting individual (63) scoring positions; 6 affecting team (5) scoring positions.
Aug 24: Lennart Vogel Honorary: 234 tasks outstanding; 96 affecting individual (54) scoring positions; 4 affecting team (4) scoring positions.
Aug 25: Lennart Vogel Honorary: 195 tasks outstanding; 78 affecting individual (48) scoring positions; 3 affecting team (3) scoring positions.
Aug 26: Lennart Vogel Honorary: 157 tasks outstanding; 60 affecting individual (41) scoring positions; 3 affecting team (3) scoring positions.
Aug 27: Lennart Vogel Honorary: 129 tasks outstanding; 44 affecting individual (31) scoring positions; 3 affecting team (3) scoring positions.
Aug 28: Lennart Vogel Honorary: 105 tasks outstanding; 34 affecting individual (27) scoring positions; 3 affecting team (3) scoring positions.
Aug 29: Lennart Vogel Honorary: 87 tasks outstanding; 22 affecting individual (18) scoring positions; 2 affecting team (2) scoring positions.
Aug 30: Lennart Vogel Honorary: 75 tasks outstanding; 16 affecting individual (14) scoring positions; 1 affecting team (1) scoring positions.
Aug 31: Lennart Vogel Honorary: 63 tasks outstanding; 12 affecting individual (10) scoring positions; 1 affecting team (1) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

I expect it to last between 3 and 6 weeks.

Status:
Aug 10 (start): Lennart Vogel Honorary: 4346 tasks outstanding; 4062 affecting individual (257) scoring positions; 2544 affecting team (57) scoring positions.
Aug 31: Lennart Vogel Honorary: 63 tasks outstanding; 12 affecting individual (10) scoring positions; 1 affecting team (1) scoring positions.[/quote]
Sep 1: Lennart Vogel Honorary: 54 tasks outstanding; 11 affecting individual (9) scoring positions; 1 affecting team (1) scoring positions.
Sep 2: Lennart Vogel Honorary: 42 tasks outstanding; 4 affecting individual (4) scoring positions; 1 affecting team (1) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

The results are final!

Top 3 individuals:

1: zunewantan
2: vaughan
3: DeleteNull

Top 3 teams:

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

Nice to see such a good turn out.
Congratulations to the winners, and well done to everyone who participated.
Let's raise a glass to Lennart.


____________