Welcome to the Year of the Pig Challenge

2019 is a Year of the Pig. In Chinese astrology, each year is related to a Chinese zodiac animal according to the 12-year cycle. The cycle of twelve corresponds to the twelve-year cycle of Jupiter. There are five types of Pigs, named after the Chinese elements. In order, they are: Metal, Water, Wood, Fire, and Earth. 2019 is an Earth Pig Year, starting on 5th February 2019 and ending on 24th January 2020. Earth Pigs are Communicative, popular among their friends, with a strong sense of time keeping. Famous Earth Pigs include Henry Ford and Arnold Schwarzenegger.

The second Challenge of the 2019 Challenge series is a 5 day challenge to celebrate the Year of the Pig. The challenge is being offered on the Generalized Cullen/Woodall Prime Search (LLR) application.

To participate in the Challenge, please select only the Generalized Cullen/Woodall Prime Search LLR (GCW) project in your PrimeGrid preferences section. The challenge will begin 5th March 2019 18:00 UTC and end at 10th March 2019 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 ~2 days on fast/newer computers and 10+ 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 GCW 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>llrGCW</name> <fraction_done_exact/> </app> <app_version> <app_name>llrGCW</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 GCW 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 GCW 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 5th March 2019 18:00 UTC and received BEFORE 10th March 2019 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 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é
  

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

Your app_config.xml file refers to an unknown application 'llrGCW'. Known applications: 'genefer17low', 'genefer16', 'gcw_sieve', 'genefer15', 'pps_sr2sieve', 'llrSOB', 'llrESP', 'llr321', 'llrPPSE', 'llrSR5', 'llrPPS', 'llrCUL', 'llrWOO', 'ap26', 'genefer'
3/2/2019 12:48:13 PM

This is the notice I receive trying to test this project. Appreciate any help you can give me.

This is common to see when you set a config for a project you have not run yet. You need to run GCW in order for the BOINC client to know what you are referring to... The error should be resolved once you start your first GCW LLR task.

Hmm I wasn't getting any tasks, so your saying dl tasks without the app_config in the projects folder then insert the app_config? I'll try that next chance I get.

Hi.

I want to try the best multithreading settings for this challenge. What I need to run in command line?

Hi.

I want to try the best multithreading settings for this challenge. What I need to run in command line?

All the info is in the first post in this thread.

Gary

and here we go ...
good luck to all
may a lucky one find a GCW-prime!
____________
Sysadm@Nbg
my current lucky number: 113856050^65536 + 1
PSA-PRPNet-Stats-URL: http://u-g-f.de/PRPNet/

i wish this would run better on a amd thread ripper....

and here we go ...
good luck to all
may a lucky one find a GCW-prime!

How Big is this Prime?

The first day is done!

Challenge: Year of the Pig
App: 30 (GCW-LLR)
(As of 2019-03-06 19:46:40 UTC)

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

Of those tasks that have been sent out:

1476 (17%) were aborted. [1476 (17%) / 0 (0%) / 0 (0%)]
144 (2%) came back with some kind of an error. [144 (2%) / 0 (0%) / 0 (0%)]
2187 (25%) have returned a successful result. [2187 (25%) / 0 (0%) / 0 (0%)]
5037 (57%) are still in progress. [5037 (57%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

1462 (67%) are pending validation. [1462 (67%) / 0 (0%) / 0 (0%)]
718 (33%) have been successfully validated. [718 (33%) / 0 (0%) / 0 (0%)]
2 (0%) were invalid. [2 (0%) / 0 (0%) / 0 (0%)]
5 (0%) are inconclusive. [5 (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=5146028. The leading edge was at n=5089561 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.11% as much as it had prior to the challenge!


8800 tasks sent out, and 2100 completed in the first day, compared to about 230 tasks completed on a normal day.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

After (a bit more than) two days:


Challenge: Year of the Pig
App: 30 (GCW-LLR)
(As of 2019-03-08 00:05:41 UTC)

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

Of those tasks that have been sent out:

2055 (15%) were aborted. [2055 (15%) / 0 (0%) / 0 (0%)]
336 (2%) came back with some kind of an error. [336 (2%) / 0 (0%) / 0 (0%)]
5898 (42%) have returned a successful result. [5898 (42%) / 0 (0%) / 0 (0%)]
5682 (41%) are still in progress. [5682 (41%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

2676 (45%) are pending validation. [2676 (45%) / 0 (0%) / 0 (0%)]
3187 (54%) have been successfully validated. [3187 (54%) / 0 (0%) / 0 (0%)]
17 (0%) were invalid. [17 (0%) / 0 (0%) / 0 (0%)]
18 (0%) are inconclusive. [18 (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=5181812. The leading edge was at n=5089561 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.81% as much as it had prior to the challenge!


We're doing in excess of 10 times the normal amount of GCW tasks each day!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

After three days:


Challenge: Year of the Pig
App: 30 (GCW-LLR)
(As of 2019-03-08 19:48:12 UTC)

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

Of those tasks that have been sent out:

2337 (14%) were aborted. [2337 (14%) / 0 (0%) / 0 (0%)]
475 (3%) came back with some kind of an error. [475 (3%) / 0 (0%) / 0 (0%)]
8734 (51%) have returned a successful result. [8734 (51%) / 0 (0%) / 0 (0%)]
5668 (33%) are still in progress. [5668 (33%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

3158 (36%) are pending validation. [3158 (36%) / 0 (0%) / 0 (0%)]
5502 (63%) have been successfully validated. [5502 (63%) / 0 (0%) / 0 (0%)]
31 (0%) were invalid. [31 (0%) / 0 (0%) / 0 (0%)]
43 (0%) are inconclusive. [43 (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=5203868. The leading edge was at n=5089561 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.25% as much as it had prior to the challenge!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

With a bit less than one day to go...


Challenge: Year of the Pig
App: 30 (GCW-LLR)
(As of 2019-03-09 22:32:42 UTC)

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

Of those tasks that have been sent out:

2750 (12%) were aborted. [2750 (12%) / 0 (0%) / 0 (0%)]
707 (3%) came back with some kind of an error. [707 (3%) / 0 (0%) / 0 (0%)]
12824 (58%) have returned a successful result. [12824 (58%) / 0 (0%) / 0 (0%)]
5745 (26%) are still in progress. [5745 (26%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

3499 (27%) are pending validation. [3499 (27%) / 0 (0%) / 0 (0%)]
9224 (72%) have been successfully validated. [9224 (72%) / 0 (0%) / 0 (0%)]
52 (0%) were invalid. [52 (0%) / 0 (0%) / 0 (0%)]
49 (0%) are inconclusive. [49 (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=5237712. The leading edge was at n=5089561 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.91% as much as it had prior to the challenge!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

I am afraid to ask but is this the Norm?
2337 (14%) were aborted. [2337 (14%) / 0 (0%) / 0 (0%)]
2055 (15%) were aborted. [2055 (15%) / 0 (0%) / 0 (0%)]

I am afraid to ask but is this the Norm?
2337 (14%) were aborted. [2337 (14%) / 0 (0%) / 0 (0%)]
2055 (15%) were aborted. [2055 (15%) / 0 (0%) / 0 (0%)]

This is definitely true - I've aborted 20+ WUs since moving to multithreading, compared to approx zero over the previous few years. BOINC client behaviour leads to unexpected trends sometimes.
____________

I'm pretty sure most of the aborts are related to multi-tasking. This chart shows the abort percentage by sub project. Projects where you don't use multitasking have very low abort ratios.

In particular, SGS and PPSE and GFN have low percentages, so the aborts aren't related to prime searching.

The challenge just ended, so it's time to remind everyone...

(Actually, it's a bit late, but it's still important.)

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. Thank you!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Final statistics:


Challenge: Year of the Pig
App: 30 (GCW-LLR)
(As of 2019-03-10 18:26:08 UTC)

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

Of those tasks that have been sent out:

3733 (14%) were aborted. [3733 (14%) / 0 (0%) / 0 (0%)]
865 (3%) came back with some kind of an error. [865 (3%) / 0 (0%) / 0 (0%)]
16121 (61%) have returned a successful result. [16121 (61%) / 0 (0%) / 0 (0%)]
5524 (21%) are still in progress. [5524 (21%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

3421 (21%) are pending validation. [3421 (21%) / 0 (0%) / 0 (0%)]
12563 (78%) have been successfully validated. [12563 (78%) / 0 (0%) / 0 (0%)]
71 (0%) were invalid. [71 (0%) / 0 (0%) / 0 (0%)]
66 (0%) are inconclusive. [66 (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=5263641. The leading edge was at n=5089561 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.42% as much as it had prior to the challenge!


We did over 3000 tasks per day, which is more than ten times normal. Fantastic job everyone!


We have a bit of a break until the next challenge, a one week TRP challenge at the end of May. We'll be restarting the 321-sieve soon, so you'all will have time to work on that new (or old) 321-sieve badge before worrying about another challenge.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

The cleanup starts now. I expect the cleanup to take about a month.


Year of the Pig Challenge Cleanup:
Mar 10: Year of the Pig: 3464 tasks outstanding; 3307 affecting individual (252) scoring positions; 1646 affecting team (56) scoring positions.
Mar 11: Year of the Pig: 2787 tasks outstanding; 2668 affecting individual (245) scoring positions; 1319 affecting team (53) scoring positions.
Mar 12: Year of the Pig: 2294 tasks outstanding; 2125 affecting individual (231) scoring positions; 744 affecting team (47) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Waiting for a wingman... Wow, talk about diminishing returns! This host is using 72 threads per llrGCW task, so over 1,000,000 CPU seconds @ 3 GHz on a high-end CPU and not getting good throughput. Also running running 69 tasks in parallel, which doesn't help. At least there's enough RAM.

This is not the only host configured this way. Someone needs to make a YT video on multithreading LLR tasks efficiently (for max both throughput or min runtime) and link it to the main PG page. The PG forums contain valuable info but the signal-to-noise ratio is really low.

Year of the Pig Challenge Cleanup:
Mar 10: Year of the Pig: 3464 tasks outstanding; 3307 affecting individual (252) scoring positions; 1646 affecting team (56) scoring positions.
Mar 11: Year of the Pig: 2787 tasks outstanding; 2668 affecting individual (245) scoring positions; 1319 affecting team (53) scoring positions.
Mar 12: Year of the Pig: 2294 tasks outstanding; 2125 affecting individual (231) scoring positions; 744 affecting team (47) scoring positions.
Mar 13: Year of the Pig: 2000 tasks outstanding; 1825 affecting individual (221) scoring positions; 649 affecting team (46) scoring positions.
Mar 14: Year of the Pig: 1777 tasks outstanding; 1558 affecting individual (212) scoring positions; 539 affecting team (40) scoring positions.
Mar 15: Year of the Pig: 1592 tasks outstanding; 1404 affecting individual (207) scoring positions; 495 affecting team (38) scoring positions.
Mar 16: Year of the Pig: 1468 tasks outstanding; 1294 affecting individual (196) scoring positions; 461 affecting team (37) scoring positions.
Mar 17: Year of the Pig: 1367 tasks outstanding; 1201 affecting individual (191) scoring positions; 427 affecting team (36) scoring position
Mar 18: Year of the Pig: 1223 tasks outstanding; 1034 affecting individual (184) scoring positions; 387 affecting team (34) scoring positions.
Mar 19: Year of the Pig: 1143 tasks outstanding; 970 affecting individual (180) scoring positions; 335 affecting team (32) scoring positions.
Mar 20: Year of the Pig: 1055 tasks outstanding; 904 affecting individual (177) scoring positions; 311 affecting team (32) scoring positions.
Mar 21: Year of the Pig: 970 tasks outstanding; 843 affecting individual (173) scoring positions; 296 affecting team (32) scoring positions.
Mar 22: Year of the Pig: 909 tasks outstanding; 743 affecting individual (168) scoring positions; 278 affecting team (31) scoring positions.
Mar 23: Year of the Pig: 822 tasks outstanding; 643 affecting individual (161) scoring positions; 257 affecting team (31) scoring positions.
Mar 24: Year of the Pig: 760 tasks outstanding; 580 affecting individual (151) scoring positions; 225 affecting team (26) scoring positions.
Mar 25: Year of the Pig: 677 tasks outstanding; 487 affecting individual (145) scoring positions; 197 affecting team (24) scoring positions.
Mar 26: Year of the Pig: 590 tasks outstanding; 428 affecting individual (132) scoring positions; 175 affecting team (22) scoring positions.
Mar 27: Year of the Pig: 503 tasks outstanding; 355 affecting individual (122) scoring positions; 94 affecting team (17) scoring positions.
Mar 28: Year of the Pig: 418 tasks outstanding; 280 affecting individual (110) scoring positions; 74 affecting team (14) scoring positions.
Mar 29: Year of the Pig: 350 tasks outstanding; 216 affecting individual (97) scoring positions; 61 affecting team (13) scoring positions.
Mar 30: Year of the Pig: 288 tasks outstanding; 182 affecting individual (87) scoring positions; 46 affecting team (12) scoring positions.
Mar 31: Year of the Pig: 244 tasks outstanding; 130 affecting individual (69) scoring positions; 36 affecting team (7) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Year of the Pig Challenge Cleanup:
Mar 10: Year of the Pig: 3464 tasks outstanding; 3307 affecting individual (252) scoring positions; 1646 affecting team (56) scoring positions.
Apr 1: Year of the Pig: 201 tasks outstanding; 112 affecting individual (63) scoring positions; 21 affecting team (6) scoring positions.
Apr 2: Year of the Pig: 168 tasks outstanding; 87 affecting individual (54) scoring positions; 16 affecting team (5) scoring positions.
Apr 3: Year of the Pig: 138 tasks outstanding; 65 affecting individual (45) scoring positions; 13 affecting team (4) scoring positions.
Apr 4: Year of the Pig: 116 tasks outstanding; 53 affecting individual (40) scoring positions; 11 affecting team (3) scoring positions.
Apr 5: Year of the Pig: 102 tasks outstanding; 49 affecting individual (37) scoring positions; 11 affecting team (3) scoring positions.
Apr 6: Year of the Pig: 80 tasks outstanding; 41 affecting individual (33) scoring positions; 10 affecting team (3) scoring positions.
Apr 7: Year of the Pig: 67 tasks outstanding; 30 affecting individual (28) scoring positions; 8 affecting team (3) scoring positions.
Apr 8: Year of the Pig: 62 tasks outstanding; 27 affecting individual (25) scoring positions; 7 affecting team (3) scoring positions.
Apr 9: Year of the Pig: 58 tasks outstanding; 25 affecting individual (24) scoring positions; 5 affecting team (2) scoring positions.
Apr 10: Year of the Pig: 53 tasks outstanding; 25 affecting individual (24) scoring positions; 5 affecting team (2) scoring positions.
Apr 11: Year of the Pig: 48 tasks outstanding; 22 affecting individual (22) scoring positions; 4 affecting team (2) scoring positions.
Apr 12: Year of the Pig: 45 tasks outstanding; 21 affecting individual (21) scoring positions; 4 affecting team (2) scoring positions.
Apr 13: Year of the Pig: 42 tasks outstanding; 18 affecting individual (18) scoring positions; 4 affecting team (2) scoring positions.
Apr 14: Year of the Pig: 29 tasks outstanding; 8 affecting individual (8) scoring positions; 0 affecting team (0) scoring positions.
Apr 15: Year of the Pig: 25 tasks outstanding; 5 affecting individual (5) scoring positions; 0 affecting team (0) scoring positions.
Apr 16: Year of the Pig: 21 tasks outstanding; 5 affecting individual (5) scoring positions; 0 affecting team (0) scoring positions.
Apr 17: Year of the Pig: 18 tasks outstanding; 4 affecting individual (4) scoring positions; 0 affecting team (0) scoring positions.
Apr 18: Year of the Pig: 15 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Apr 19: Year of the Pig: 8 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Apr 20: Year of the Pig: 4 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Apr 21: Year of the Pig: 3 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Apr 22: Year of the Pig: 3 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Apr 23: Year of the Pig: 1 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
Apr 24: Year of the Pig: 0 tasks outstanding; 0 affecting individual (0) scoring positions; 0 affecting team (0) scoring positions.

The cleanup is completed!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

... The cleanup is completed!

Are the results final already?
I mean, can I update the Challenge Series results ?

The results are final!

Top 3 individuals:

1: zunewantan
2: Scott Brown
3: DeleteNull

Top 3 teams:

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

Congratulations to the winners, and well done to everyone who participated.
See you at the Hans Ivar Riesel's 90th Birthday Challenge!
____________