Year of the Dog

2018 is a Year of the Dog. In Chinese astrology, each year is related to a Chinese zodiac animal according to the 12-year cycle. 2018 is an Earth Dog Year, starting on 16th February 2018 and ending on 4th February 2019. Earth Dog's are Communicative, serious, and responsible in work. Famous Earth Dog's include Madonna and Michael Jackson.

The second Challenge of the 2018 Challenge series is a 7 day challenge to celebrate the Year of the Dog. The challenge is being offered on the 321 Prime Search (LLR) application.

To participate in the Challenge, please select only the 321 Prime Search LLR (321) project in your PrimeGrid preferences section. The challenge will begin 16th March 2018 18:00 UTC and end 23rd March 2018 18: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 ~48 hours on fast/newer computers and 6+ 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 321 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>llr321</name> <fraction_done_exact/> <max_concurrent>1</max_concurrent> </app> <app_version> <app_name>llr321</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 321 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 321 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 16th March 2018 18:00 UTC and received BEFORE 23rd March 2018 18: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 321 Search

321 Search began in February 2003 from a post by Paul Underwood seeking help from interested parties in a prime search attempt of the form 3*2^n-1. The initial goal was to build upon the completed work at Proth Search and extend the list of known primes to an exponent of 1 million (n=1M). That was quickly achieved so they advanced their goal to finding a mega prime for which they sieved up to n=5M.

As seen on PrimeGrid's front page, that goal was achieved on 23 Mar 2008, 7:57:28 UTC, when Dylan Bennett of Canada returned a positive result for n=4235414 (3*2^4235414-1). official announcement | decimal representation

PrimeGrid added the +1 form and continues the search up to n=25M.

Primes known for 3*2^n+1 occur at the following n (PrimeGrid's finds in bold & linked):
1, 2, 5, 6, 8, 12, 18, 30, 36, 41, 66, 189, 201, 209, 276, 353, 408, 438, 534, 2208, 2816, 3168, 3189, 3912, 20909, 34350, 42294, 42665, 44685, 48150, 54792, 55182, 59973, 80190, 157169, 213321, 303093, 362765, 382449, 709968, 801978, 916773, 1832496, 2145353, 2291610, 2478785, 5082306, 7033641, 10829346

Primes known for 3*2^n-1 occur at the following n (PrimeGrid's finds in bold & linked):
1, 2, 3, 4, 6, 7, 11, 18, 34, 38, 43, 55, 64, 76, 94, 103, 143, 206, 216, 306, 324, 391, 458, 470, 827, 1274, 3276, 4204, 5134, 7559, 12676, 14898, 18123, 18819, 25690, 26459, 41628, 51387, 71783, 80330, 85687, 88171, 97063, 123630, 155930, 164987, 234760, 414840, 584995, 702038, 727699, 992700, 1201046, 1232255, 2312734, 3136255, 4235414, 6090515, 11484018, 11731850, 11895718


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).
____________

Is there a score list in this challenge?

I edited my app_config.xml and got the following message

PrimeGrid: Notice from BOINC
Your app_config.xml file refers to an unknown application 'llr321'. Known applications: 'llrMEGA', 'genefer15', 'llrTPS', 'llrPPS', 'genefer16', 'genefer17mega', 'genefer17low', 'genefer18', 'gcw_sieve', 'genefer20', 'pps_sr2sieve', 'llrPPSE', 'llrSOB', 'llrESP', 'llrPSP'
08/03/2018 17:31:31

Any ideas what I'm doing wrong?

<app_config>
<app>
<name>llr321</name>
<fraction_done_exact/>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>llr321</app_name>
<cmdline>-t 2</cmdline>
<avg_ncpus>2</avg_ncpus>
</app_version>
<app>
<name>llrSOB</name>
<fraction_done_exact/>
<max_concurrent>1</max_concurrent>
</app>
<app_version>
<app_name>llrSOB</app_name>
<cmdline>-t 2</cmdline>
<avg_ncpus>2</avg_ncpus>
</app_version>
</app_config>

Thanks Rob.
____________
My lucky numbers 1059094^1048576+1 and 224584605939537911+81292139*23#*n for n=0..26

I edited my app_config.xml and got the following message

PrimeGrid: Notice from BOINC
Your app_config.xml file refers to an unknown application 'llr321'. Known applications: 'llrMEGA', 'genefer15', 'llrTPS', 'llrPPS', 'genefer16', 'genefer17mega', 'genefer17low', 'genefer18', 'gcw_sieve', 'genefer20', 'pps_sr2sieve', 'llrPPSE', 'llrSOB', 'llrESP', 'llrPSP'
08/03/2018 17:31:31

Any ideas what I'm doing wrong?

I edited my app_config.xml and got the following message

PrimeGrid: Notice from BOINC
Your app_config.xml file refers to an unknown application 'llr321'. Known applications: 'llrMEGA', 'genefer15', 'llrTPS', 'llrPPS', 'genefer16', 'genefer17mega', 'genefer17low', 'genefer18', 'gcw_sieve', 'genefer20', 'pps_sr2sieve', 'llrPPSE', 'llrSOB', 'llrESP', 'llrPSP'
08/03/2018 17:31:31

Any ideas what I'm doing wrong?

You're probably not expecting this answer: You're doing nothing wrong.

BOINC behaves that way until you run one of those tasks. You can safely ignore that message.

The challenge starts in approximately 20 minutes!

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

The first result has been returned (it was run on 12 SkyLake cores on an i9-7920X.)
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Yes, 321 is a CPU only sub-project and you can run GPU tasks in parallel.

Question:
1st post says "To participate in the Challenge, please select only the 321 Prime Search LLR (321) project in your PrimeGrid preferences section." but I see people running GFNs issued after the start.

... but why leave the GPU idle when it can be doing something useful?

For my computer, the AP27 search seems to be the GPU project that has the minimum impact on the CPU task being processed simultaneously.
Next is PPS-Sieve.

Here, running GFN-15 at the same time, increases the CPU task crunch time noticeably.
In decreasing "impact time" order, I noted GFN-16, 17-Low, 17-Mega, and so on.

Day 1 is over!

Challenge: Year of the Dog
App: 7 (321-LLR)
(As of 2018-03-17 18:59:58 UTC)

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

Of those tasks that have been sent out:

1437 (10%) came back with some kind of an error. [1435 (10%) / 0 (0%) / 2 (0%)]
4415 (31%) have returned a successful result. [4362 (31%) / 0 (0%) / 53 (0%)]
8425 (59%) are still in progress. [8418 (59%) / 0 (0%) / 7 (0%)]

Of the tasks that have been returned successfully:

2795 (63%) are pending validation. [2762 (63%) / 0 (0%) / 33 (1%)]
1594 (36%) have been successfully validated. [1574 (36%) / 0 (0%) / 20 (0%)]
3 (0%) were invalid. [3 (0%) / 0 (0%) / 0 (0%)]
23 (1%) are inconclusive. [23 (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=13924048. The leading edge was at n=13851056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.53% as much as it had prior to the challenge!


Well over 4000 321 tasks were sent out and completed in the first day. Normal for 321 is about 300 per day. Were close to 15 times normal for this challenge. That's pretty spectacular.

Can we find a 321 prime?

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

After 2 days:


Challenge: Year of the Dog
App: 7 (321-LLR)
(As of 2018-03-18 18:54:18 UTC)

22710 tasks have been sent out. [CPU/GPU/anonymous_platform: 22591 (99%) / 0 (0%) / 119 (1%)]

Of those tasks that have been sent out:

2248 (10%) came back with some kind of an error. [2246 (10%) / 0 (0%) / 2 (0%)]
11187 (49%) have returned a successful result. [11077 (49%) / 0 (0%) / 110 (0%)]
9275 (41%) are still in progress. [9268 (41%) / 0 (0%) / 7 (0%)]

Of the tasks that have been returned successfully:

4603 (41%) are pending validation. [4558 (41%) / 0 (0%) / 45 (0%)]
6529 (58%) have been successfully validated. [6464 (58%) / 0 (0%) / 65 (1%)]
19 (0%) were invalid. [19 (0%) / 0 (0%) / 0 (0%)]
36 (0%) are inconclusive. [36 (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=13966470. The leading edge was at n=13851056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.83% as much as it had prior to the challenge!

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

Since 321 is only available as CPU apps, that leaves your GPU free to do something else. It won't count for the challenge, but why leave the GPU idle when it can be doing something useful?

Because electricity costs. :D

A bit shy of 4 days in...


Challenge: Year of the Dog
App: 7 (321-LLR)
(As of 2018-03-20 14:22:26 UTC)

37946 tasks have been sent out. [CPU/GPU/anonymous_platform: 37719 (99%) / 0 (0%) / 227 (1%)]

Of those tasks that have been sent out:

3714 (10%) came back with some kind of an error. [3712 (10%) / 0 (0%) / 2 (0%)]
24635 (65%) have returned a successful result. [24421 (64%) / 0 (0%) / 214 (1%)]
9597 (25%) are still in progress. [9586 (25%) / 0 (0%) / 11 (0%)]

Of the tasks that have been returned successfully:

5943 (24%) are pending validation. [5890 (24%) / 0 (0%) / 53 (0%)]
18554 (75%) have been successfully validated. [18393 (75%) / 0 (0%) / 161 (1%)]
74 (0%) were invalid. [74 (0%) / 0 (0%) / 0 (0%)]
64 (0%) are inconclusive. [64 (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=14043528. The leading edge was at n=13851056 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!


Since the normal number of 321 tasks completed each day is about 300, this challenge is running in excess of 20 times the normal rate. I generally consider 5x a successful challenge, and 10x to be a great challenge. 20x is unprecedented in recent memory.

In the team competition, the battle for 1st and 2nd place has been very tight right from the beginning. Aggie the Pew has been maintaining a small lead over the Czech National Team. In the individual competition, [AF>Amis des Lapins] dthonon has a substantial and probably insurmountable lock on first place.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Hi there.

* The first time BOINC downloads an 321 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 321 tasks. After one task was downloaded, increase the percentage.

Yesterday I threw in another dual-core machine and actually cared about the setting to only use one core. After the work-unit was downloaded the machine started running it on both cores. I suppose this is not the expected behaviour, is it?

If you have multithreading specified in app_config, the app would run according to it. <cmdline>-t 2</cmdline>? Running on two cores then.

As I said, the "use % of CPUs" setting doesn't have anything to do with it, it only controls how BOINC makes scheduling decisions: "I'm running enough units right now" or "I need to download/run more units as I have free resources", etc. I guess, theoretically, if you have <avg_ncpus>2</avg_ncpus> in app_config, 2 cores in your system and you've set "use % of CPUs" to 50% or lower, then, maybe it shouldn't have run the unit seing that it means allocating more resources than the setting specifies, but I don't think there is code that has a check like that, it would run the unit because it has to run something, it cannot run half of a unit.

After 5 of 7 days:


Challenge: Year of the Dog
App: 7 (321-LLR)
(As of 2018-03-21 18:31:14 UTC)

47523 tasks have been sent out. [CPU/GPU/anonymous_platform: 47205 (99%) / 0 (0%) / 318 (1%)]

Of those tasks that have been sent out:

5666 (12%) came back with some kind of an error. [5664 (12%) / 0 (0%) / 2 (0%)]
33306 (70%) have returned a successful result. [33030 (70%) / 0 (0%) / 276 (1%)]
8551 (18%) are still in progress. [8511 (18%) / 0 (0%) / 40 (0%)]

Of the tasks that have been returned successfully:

5789 (17%) are pending validation. [5736 (17%) / 0 (0%) / 53 (0%)]
27341 (82%) have been successfully validated. [27118 (81%) / 0 (0%) / 223 (1%)]
106 (0%) were invalid. [106 (0%) / 0 (0%) / 0 (0%)]
70 (0%) are inconclusive. [70 (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=14086716. The leading edge was at n=13851056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.70% as much as it had prior to the challenge!


No primes yet, but there's still 48 hours to go. Will you be the lucky one?
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

The latest work-units on my i5 have been significantly bigger than the previous ones. Rounded 140k secs vs. 80k secs. with the same settings on my side. Is this just coincidence, or might this be a proper development?

Our challenges have always been rather fickle when it come to finding primes.

During this year's 321 challenge, we haven't found a 321 prime -- yet. That's despite processing about twenty times as many numbers as normal. If we do find one in the remaining day or so, it will be about 4.2 million digits in length.

Here's the fickle part: during the challenge we DID find a 3.3 million digit GFN-19, which is the second GFN-19 this year after not having found any for over 5 years. And that was after having found the first four in less than 12 months.

And so, of course, now we've also found a 5.1 million digit Woodall prime during the 321 challenge. The last time a Woodall was discovered was over 10 years ago in 2007.

So very fickle!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Given the randomness maybe I should go to another big prime project after the challenge...

Given the randomness maybe I should go to another big prime project after the challenge...

where are the badges for Year of the Dog ?

There's less than 1 day to go!


Challenge: Year of the Dog
App: 7 (321-LLR)
(As of 2018-03-22 19:03:30 UTC)

54633 tasks have been sent out. [CPU/GPU/anonymous_platform: 54262 (99%) / 0 (0%) / 371 (1%)]

Of those tasks that have been sent out:

6257 (11%) came back with some kind of an error. [6255 (11%) / 0 (0%) / 2 (0%)]
40616 (74%) have returned a successful result. [40285 (74%) / 0 (0%) / 331 (1%)]
7760 (14%) are still in progress. [7722 (14%) / 0 (0%) / 38 (0%)]

Of the tasks that have been returned successfully:

5406 (13%) are pending validation. [5360 (13%) / 0 (0%) / 46 (0%)]
34959 (86%) have been successfully validated. [34674 (85%) / 0 (0%) / 285 (1%)]
165 (0%) were invalid. [165 (0%) / 0 (0%) / 0 (0%)]
86 (0%) are inconclusive. [86 (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=14122412. The leading edge was at n=13851056 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.96% as much as it had prior to the challenge!


Is there a 321 prime lurking in the next 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 are done! Final statistics:


Challenge: Year of the Dog
App: 7 (321-LLR)
(As of 2018-03-23 18:05:50 UTC)

60640 tasks have been sent out. [CPU/GPU/anonymous_platform: 60217 (99%) / 0 (0%) / 423 (1%)]

Of those tasks that have been sent out:

7728 (13%) came back with some kind of an error. [7725 (13%) / 0 (0%) / 3 (0%)]
47262 (78%) have returned a successful result. [46873 (77%) / 0 (0%) / 389 (1%)]
5622 (9%) are still in progress. [5591 (9%) / 0 (0%) / 31 (0%)]

Of the tasks that have been returned successfully:

4193 (9%) are pending validation. [4160 (9%) / 0 (0%) / 33 (0%)]
42784 (91%) have been successfully validated. [42428 (90%) / 0 (0%) / 356 (1%)]
204 (0%) were invalid. [204 (0%) / 0 (0%) / 0 (0%)]
81 (0%) are inconclusive. [81 (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=14148473. The leading edge was at n=13851056 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!


Alas, no 321 primes this time. Maybe next challenge...
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Cleanup begins:

Mar 23: Year of the Dog: 4150 tasks outstanding; 3228 affecting individual (259) scoring positions; 1104 affecting team (36) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

a little off topic
why the badges of the Tour de prime do not appear in my signature on boinc?

Cleanup:

Mar 23: Year of the Dog: 4150 tasks outstanding; 3228 affecting individual (259) scoring positions; 1104 affecting team (36) scoring positions.
Mar 24: Year of the Dog: 2691 tasks outstanding; 1884 affecting individual (232) scoring positions; 676 affecting team (27) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

a little off topic
why the badges of the Tour de prime do not appear in my signature on boinc?

Cleanup:

Mar 23: Year of the Dog: 4150 tasks outstanding; 3228 affecting individual (259) scoring positions; 1104 affecting team (36) scoring positions.
Mar 24: Year of the Dog: 2691 tasks outstanding; 1884 affecting individual (232) scoring positions; 676 affecting team (27) scoring positions.
Mar 25: Year of the Dog: 1838 tasks outstanding; 1174 affecting individual (202) scoring positions; 421 affecting team (20) scoring positions.
Mar 26: Year of the Dog: 1332 tasks outstanding; 768 affecting individual (166) scoring positions; 306 affecting team (17) scoring positions.
Mar 27: Year of the Dog: 1055 tasks outstanding; 556 affecting individual (139) scoring positions; 48 affecting team (13) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

I believe this is the same Sebastien who runs WUProp, and if so, it's possible he may have abandoned both websites. I hope that's not true.....

Sebastien who runs WUProp is active http://wuprop.boinc-af.org/forum_thread.php?id=351&postid=6065#6065

I will not support the project anymore.

Cleanup:

Mar 23: Year of the Dog: 4150 tasks outstanding; 3228 affecting individual (259) scoring positions; 1104 affecting team (36) scoring positions.
Mar 24: Year of the Dog: 2691 tasks outstanding; 1884 affecting individual (232) scoring positions; 676 affecting team (27) scoring positions.
Mar 25: Year of the Dog: 1838 tasks outstanding; 1174 affecting individual (202) scoring positions; 421 affecting team (20) scoring positions.
Mar 26: Year of the Dog: 1332 tasks outstanding; 768 affecting individual (166) scoring positions; 306 affecting team (17) scoring positions.
Mar 27: Year of the Dog: 1055 tasks outstanding; 556 affecting individual (139) scoring positions; 48 affecting team (13) scoring positions.
Mar 28: Year of the Dog: 795 tasks outstanding; 327 affecting individual (113) scoring positions; 33 affecting team (10) scoring positions.
Mar 29: Year of the Dog: 585 tasks outstanding; 207 affecting individual (91) scoring positions; 20 affecting team (7) scoring positions.
Mar 30: Year of the Dog: 468 tasks outstanding; 166 affecting individual (83) scoring positions; 17 affecting team (7) scoring positions.
Mar 31: Year of the Dog: 252 tasks outstanding; 69 affecting individual (44) scoring positions; 8 affecting team (4) scoring positions.
Apr 1: Year of the Dog: 192 tasks outstanding; 52 affecting individual (37) scoring positions; 8 affecting team (4) scoring positions.
Apr 2: Year of the Dog: 133 tasks outstanding; 38 affecting individual (29) scoring positions; 7 affecting team (4) scoring positions.
Apr 3: Year of the Dog: 109 tasks outstanding; 34 affecting individual (27) scoring positions; 3 affecting team (3) scoring positions.
Apr 4: Year of the Dog: 76 tasks outstanding; 28 affecting individual (22) scoring positions; 3 affecting team (3) scoring positions.
Apr 5: Year of the Dog: 59 tasks outstanding; 24 affecting individual (20) scoring positions; 2 affecting team (2) scoring positions.
Apr 6: Year of the Dog: 41 tasks outstanding; 12 affecting individual (12) scoring positions; 2 affecting team (2) scoring positions.
Apr 7: Year of the Dog: 33 tasks outstanding; 9 affecting individual (9) scoring positions; 2 affecting team (2) scoring positions.
Apr 8: Year of the Dog: 30 tasks outstanding; 7 affecting individual (7) scoring positions; 2 affecting team (2) scoring positions.
Apr 9: Year of the Dog: 21 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

The results are final!

Top 3 individuals:

1: [AF>Amis des Lapins] dthonon
2: Scott Brown
3: zunewantan

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!
____________