Welcome to the World Water Day Challenge

The second challenge of the 2022 Series will be a 5-day challenge in celebration of World Water Day, the annual United Nations Observance, started in 1993, that celebrates water and raises awareness of the 2 billion people currently living without access to safe water. The challenge will be offered on the 321-LLR application, beginning 21 March 03:21 UTC and ending 26 March 03:21 UTC.

To participate in the Challenge, please select only the 321 Prime Search LLR (321) project in your PrimeGrid preferences section.

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

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

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

Multi-threading is supported and IS recommended. (321 tasks on one CPU core will take 2-3 days on fast/newer computers and 1 week+ on slower/older computers.)

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

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

  
  

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

  
  

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

Time zone converter:

The World Clock - Time Zone Converter

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

Scoring Information

Scores will be kept for individuals and teams. Only tasks issued AFTER 21st March 2022 03:21 UTC and received BEFORE 26th March 2022 03:21 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, 16408818

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, 16819291, 17748034

What is LLR?

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

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

What is LLR2?

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

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

Is there going to be a wet dress rehearsal?

My meager computers won’t make much of a difference, but I have joined team Ukraine for the balance of the challenge. My toes are getting cold and I shall take a vacation from Antarctica to go someplace warmer as Autumn comes to the south and Spring to the north.

(Any replies to this should be worded very, very carefully. The “no politics” rules still apply.)
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

I messed up my start to this challenge. I miscalculated the cache requirements for my two larger computers and ended up aborting their tasks after 25 minutes. Oops!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

I'll be making a much lower contribution, myself. My PG electricity budget is shared with my gas budget, so I'm down to my main CPU only (not even GPU) for daily crunching. I'll fire up my two X99 systems for this challenge because they have a good performance/watt ratio.

I love PG, but going to work is a wee bit more important.
____________
Eating more cheese on Thursdays.

Day 1 is just about over, here are the stats!

Challenge: World Water Day
App: 7 (321-LLR)
Fast DC tasks are NOT included.
(As of 2022-03-22 01:01:15 UTC)

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

Of those tasks that have been sent out:

1119 (6%) were aborted. [1119 (6%) / 0 (0%) / 0 (0%)]
55 (0%) came back with some kind of an error. [55 (0%) / 0 (0%) / 0 (0%)]
3871 (21%) have returned a successful result. [3871 (21%) / 0 (0%) / 0 (0%)]
13115 (72%) are still in progress. [13115 (72%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

1373 (35%) are pending validation. [1373 (35%) / 0 (0%) / 0 (0%)]
2498 (65%) have been successfully validated. [2498 (65%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]

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

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

This is a World Water Day challenge thread, not World War Three thread. While we are all saddened by what is happening in the world, there is the whole internet where you can discuss worldwide events. Let's keep our math bubble free of politics, no matter what your views are.

I have hidden the posts that violated our rules regarding no political threads. All of the hidden posts were either political, off topic, or quoted a post that was one of those issues.

The choice of any user to be a part of or change a team is a personal one, and unless their is some other rule violation (e.g., an obscene team name, etc.), any PG participant should feel free to be a part of any team that allows them to be a member, change their team affiliation any time they like, or choose not to be a member of a team.

One day left in the challenge!

Challenge: World Water Day
App: 7 (321-LLR)
Fast DC tasks are NOT included.
(As of 2022-03-25 01:40:20 UTC)

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

Of those tasks that have been sent out:

4080 (8%) were aborted. [4080 (8%) / 0 (0%) / 0 (0%)]
259 (0%) came back with some kind of an error. [259 (0%) / 0 (0%) / 0 (0%)]
29926 (57%) have returned a successful result. [29926 (57%) / 0 (0%) / 0 (0%)]
18331 (35%) are still in progress. [18331 (35%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

3892 (13%) are pending validation. [3892 (13%) / 0 (0%) / 0 (0%)]
26034 (87%) have been successfully validated. [2634 (87%) / 0 (0%) / 0 (0%)]
4 (0%) were invalid. [4 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]

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

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

Incredible showing for this challenge! Here are the final stats. Cleanup is in progress now!

Challenge: World Water Day
App: 7 (321-LLR)
Fast DC tasks are NOT included.
(As of 2022-03-27 19:41:31 UTC)

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

Of those tasks that have been sent out:

7707 (12%) were aborted. [7707 (12%) / 0 (0%) / 0 (0%)]
324 (1%) came back with some kind of an error. [324 (1%) / 0 (0%) / 0 (0%)]
39523 (62%) have returned a successful result. [39523 (62%) / 0 (0%) / 0 (0%)]
6218 (10%) are still in progress. [6218 (10%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

842 (2%) are pending validation. [842 (2%) / 0 (0%) / 0 (0%)]
38681 (98%) have been successfully validated. [38681 (98%) / 0 (0%) / 0 (0%)]
9 (0%) were invalid. [9 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]

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

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

Cleanup Status:

Mar 28: 279 tasks outstanding; 77 affecting individual (46) scoring positions; 48 affecting team (7) scoring positions.
Mar 29: 209 tasks outstanding; 49 affecting individual (36) scoring positions; 33 affecting team (5) scoring positions.
Mar 30: 148 tasks outstanding; 28 affecting individual (24) scoring positions; 18 affecting team (2) scoring positions.
Mar 31: 37 tasks outstanding; 6 affecting individual (6) scoring positions; 0 affecting team (0) scoring positions.
Apr 1: 20 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Apr 2: 13 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Apr 3: 8 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Apr 4: 1 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
____________

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

The results are final!

During the 5 day challenge, we completed almost 40,000 tasks. For the first time at least since I've been challenge coordinator, WE FOUND A MEGA PRIME DURING A CHALLENGE! Shoutout to boss for their find: 3*2^18924988-1. The challenge boosted the project's average output to 20 times typical.

136 teams and 563 individuals participated in the Challenge.

Top Three Individuals:
1. Icecold
2. tng
3. MiHost

Top Three Teams:
1. Ukraine
2. TeAm AnandTech
3. SETI.Germany

Phenomenal work everyone! See you at the GEEK PRIDE DAY Challenge in T-minus 49 days!
____________

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

For the first time at least since I've been challenge coordinator, WE FOUND A MEGA PRIME DURING A CHALLENGE!