Welcome to the Solar Eclipse Challenge

As seen from the Earth, a solar eclipse is a type of eclipse that occurs when the Moon passes between the Sun and Earth, and the Moon fully or partially blocks ("occults") the Sun. This can happen only at new moon, when the Sun and the Moon are in conjunction as seen from Earth in an alignment referred to as syzygy. In a total eclipse, the disk of the Sun is fully obscured by the Moon. In partial and annular eclipses only part of the Sun is obscured.

An eclipse is a natural phenomenon. Nevertheless, in some ancient and modern cultures, solar eclipses have been attributed to supernatural causes or regarded as bad omens. A total solar eclipse can be frightening to people who are unaware of its astronomical explanation, as the Sun seems to disappear during the day and the sky darkens in a matter of minutes.

To celebrate this phenomenon, we are hosting a 5 day challenge on the SR5 subproject.

This project is an extension of the original Sierpinski/Riesel problems (SoB/TRP). It is attempting to solve the Sierpinski/Riesel problems for base 5 by determining the smallest Sierpinski/Riesel numbers. Therefore, primes of the form k*5^n+/-1 are being sought for even k's.

A distributed effort is currently ongoing in support of the project. More information can be found in the mersenneforum.org Sierpinski/Riesel Base 5 thread.

To participate in the Challenge, please select only the SR5 (LLR) project in your PrimeGrid preferences section. The challenge will begin March 15th 2015, 07:41 UTC and end March 20th 2015, 07:41 UTC. Application builds are available for Linux , Windows and MacIntel 32 bit and 64 bit. Intel CPU's with AVX and FMA capabilities will be significantly faster than the ones without, as this instruction set allows for more computing power.

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. WU's will take about 2.5 hours on fast/newer computers and 5+ hours 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. :)

Restricted airflow is one of the primary reasons for overheating. Take the time to monitor the fans and review the dust buildup. Please, please, please make sure your machines are up to the task.

NOTE: Should you be lucky enough to find a prime, extra processing is required and the run-time may be as much as 10 times longer than normal.

DON'T ABORT TASKS THAT SEEM TO BE TAKING AN UNUSUALLY LONG TIME TO RUN!

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 to the left of the countdown clock.

Scoring Information

Scores will be kept for individuals and teams. Only work units issued AFTER March 15th 2015, 07:41 UTC and received BEFORE March 20th 2015, 07:41 UTC will be considered for credit.

Therefore, each completed WU will earn a unique score based on its n value. The higher the n, the higher the score. This is different than BOINC cobblestones! 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 would prefer users "moving on" to finish those tasks they have downloaded, if not then please ABORT the WU's 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 an LLR 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.

Please consider either completing what's in the queue or ABORTING them. Thank you. :)


Best of Luck!!!

Sierpinski Base 5 - The smallest even Sierpinski base 5 number is suggested to be k=159986. To prove this, it is sufficient to show that k*5^n+1 is prime for each even k < 159986. This has currently been achieved for all even k, with the exception of the following 37 values (as of 2 March 2015):

k = 6436, 7528, 10918, 26798, 29914, 31712, 36412, 41738, 44348, 44738, 45748, 51208, 58642, 60394, 62698, 64258, 67612, 67748, 71492, 74632, 76724, 77072, 81556, 83936, 84284, 90056, 92158, 92906, 93484, 105464, 118568, 126134, 138514, 139196, 144052, 152588, 154222

Riesel Base 5 - The smallest even Riesel base 5 number is suggested to be k=346802. To prove this, it is sufficient to show that k*5^n-1 is prime for each even k < 346802. This has currently been achieved for all even k, with the exception of the following 79 values (as of 2 March 2015):


k = 3622, 4906, 23906, 26222, 35248, 35816, 52922, 53546, 63838, 64598, 66916, 68132, 71146, 76354, 81134, 88444, 92936, 100186, 102818, 102952, 109238, 109838, 109862, 127174, 131848, 134266, 136804, 143632, 145462, 145484, 146264, 146756, 147844, 151042, 152428, 154844, 159388, 164852, 170386, 170908, 171362, 177742, 180062, 182398, 187916, 189766, 190334, 194368, 195872, 201778, 204394, 206894, 207494, 213988, 231674, 238694, 239062, 239342, 246238, 248546, 259072, 265702, 267298, 271162, 273662, 285598, 285728, 296024, 298442, 301562, 304004, 306398, 313126, 318278, 322498, 325922, 327926, 335414, 338866

History
Robert Smith originally presented the idea of a Sierpinski/Riesel base 5 search on 17 September 2004, in the primeform yahoo group. Using {3,7,13,31,601} as the covering set, he proposed that k=346802 is the smallest Riesel base 5 number. Shortly afterwards, Guido Smetrijns proposed that k=159986 is the smallest Sierpinski base 5 number.

After doing most of the initial work himself, Robert posted in the mersenneforum.org on 28 September 2004, and thus, the distributed effort began. Other principle players in the development, management, and growth of the project are Lars Dausch, Geoff Reynolds, Anand S Nair, and Thomas Masser.

Primes found by PrimeGrid

109208*5^1816285+1 found by Scott Brown on 18 October 2014 | Official Announcement
325918*5^1803339-1 found by Jörg Meili on 21 September 2014 | Official Announcement
133778*5^1785689+1 found by Guo Hua Miao on 17 August 2014 | Official Announcement
24032*5^1768249+1 found by Hiroyuki Okazaki on 23 July 2014 | Official Announcement
138172*5^1714207-1 found by Walter Darimont on 27 June 2014 | Official Announcement
22478*5^1675150-1 found by Guo Hua Miao on 19 June 2014 | Official Announcement
326834*5^1634978-1 found by Scott Brown on 25 April 2014 | Official Announcement
207394*5^1612573-1 found by Honza Cholt on 9 April 2014 | Official Announcement
104944*5^1610735-1 found by Brian Smith on 9 April 2014 | Official Announcement
330286*5^1584399-1 found by Scott Brown on 21 March 2014 | Official Announcement
22934*5^1536762-1 found by Keishi Toda on 6 February 2014 | Official Announcement
178658*5^1525224-1 found by Keishi Toda on 31 January 2014 | Official Announcement
59912*5^1500861+1 found by Raymond Ottusch on 17 January 2014 | Official Announcement
37292*5^1487989+1 found by Stephen R Cilliers on 29 December 2013 | Official Announcement
173198*5^1457792-1 found by Motohiro Ohno on 4 December 2013 | Official Announcement
245114*5^1424104-1 found by David Yost on 1 November 2013
175124*5^1422646-1 found by David Yost on 31 October 2013
256612*5^1335485-1 found by Wolfgang Schwieger on 4 August 2013
268514*5^1292240-1 found by Raymond Schouten on 16 July 2013
243944*5^1258576-1 found by Tod Slakans on 5 July 2013
97366*5^1259955-1 found by Jörg Meili on 4 July 2013
84466*5^1215373-1 found by Raymond Schouten on 29 June 2013
150344*5^1205508-1 found by Randy Ready on 28 June 2013
1396*5^1146713-1 found by Randy Ready on 23 June 2013
17152*5^1131205-1 found by Bob Benson on 22 June 2013
92182*5^1135262+1 found by Randy Ready on 21 June 2013
329584*5^1122935-1 found by Stephen R Cilliers on 21 June 2013
305716*5^1093095-1 found by Randy Ready on 18 June 2013
130484*5^1080012-1 found by Randy Ready on 17 June 2013
97768*5^987383-1 found by Ulrich Hartel on 17 June 2013
55154*5^1063213+1 found by Senji Yamashita on 16 June 2013
243686*5^1036954-1 found by Katsumi Hirai on 16 June 2013
70082*5^936972-1 found by Scott Brown on 30 May 2013
102976*5^929801-1 found by David Yost on 9 May 2013
110488*5^917100+1 found by Ronny Willig on 25 March 2013
162434*5^856004-1 found by Predrag Kurtovic on 10 January 2013
174344*5^855138-1 found by Ronny Willig on 9 January 2013
57406*5^844253-1 found by David Yost on 7 November 2012
48764*5^831946-1 found by David Yost on 12 October 2012
162668*5^785748-1 found by Lennart Vogel on 3 July 2012
289184*5^770116-1 found by David Yost on 7 June 2012
11812*5^769343-1 found by Göran Schmidt on 2 June 2012
316594*5^766005-1 found by Michael Becker on 30 May 2012
340168*5^753789-1 found by Kimmo Myllyvirta on 18 May 2012
338948*5^743996-1 found by Ricky L Hubbard on 7 May 2012
18656*5^735326-1 found by Lennart Vogel on 3 May 2012
5374*5^723697-1 found by Kelvin Lewis on 13 April 2012
72532*5^708453-1 found by Göran Schmidt on 7 February 2012
2488*5^679769-1 found by Sascha Beat Dinkel on 24 November 2011
331882*5^674961-1 found by Ronny Willig on 11 November 2011
27994*5^645221-1 found by Philipp Bliedung on 18 July 2011
262172*5^643342-1 found by Kimmo Myllyvirta on 13 July 2011
49568*5^640900-1 found by Sascha Beat Dinkel on 1 July 2011
270748*5^614625-1 found by Puzzle Peter on 14 February 2011
266206*5^608649-1 found by Puzzle Peter on 10 February 2011
210092*5^618136-1 found by Puzzle Peter on 31 January 2011
301016*5^586858-1 found by Puzzle Peter on 24 January 2011

Primes found by SR5 since collaboration

109988*5^544269+1 found by ltd on 23 April 2011
68492*5^542553+1 found by ltd on 24 April 2011

Primes found by others

114986*5^1052966-1 found by Sergey Batalov on 3 June 2013
119878*5^1019645-1 found by Sergey Batalov on 3 June 2013
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)

I think the starting time is in the middle of the night here. Better set the alarm clock.

I think the starting time is in the middle of the night here. Better set the alarm clock.

Hungary is CET I believe, so that'll be 08:41 local. Nearly got mixed up with adding or subtracting hours then...

forget about the clicking-or-whatever-addon-software
use the builtin boinc-cmdline-tool "boinccmd" with
- windows: taskplaner
- unix/linux: atd (or crond)
see here: http://boinc.berkeley.edu/wiki/Boinccmd_tool

____________
Sysadm@Nbg
my current lucky number: 3019277580135*2^1290000-1
PSA-PRPNet-Stats-URL: http://u-g-f.de/PRPNet/

I wonder if I downloaded ahead of time the wu's, I know I am supposed to have an empty que. But, perhaps only those wu's will not get credit that started prior to the official start time and all other already downloaded would receive credit as they start and complete within the competition?

It looks like the counter on the frontpage is wrong.

It takes more than 100 hours usually, and TEN TIMES when a prime is found... I should not do this not to interfere other programs.

Nayuta Ito wrote:

It takes more than 100 hours usually, and TEN TIMES when a prime is found... I should not do this not to interfere other programs.

These take exactly 3 hours on my i7-3770 (not overclocked). I don't know where your 100 hour number came from.

It takes more than 100 hours usually, and TEN TIMES when a prime is found... I should not do this not to interfere other programs.

By my time, it is just over three days until the challenge starts. I'm pretty new, so I haven't witnessed any prior challenge. I'm planning to run SR5 24/7 on both my computers throughout the challenge, then finish up the two paused SoB tasks on one computer and continue running the challenge subproject to help with cleanup on the other computer. I don't have hundreds of computers (I'm looking at you, Scott Brown), so to me the challenge is just an opportunity to focus on a subproject that I don't normally run. About how long is the estimated timeframe for an SR5 challenge cleanup to reach ~90%? I have been reading the posts from the Year of the Sheep challenge, but since I joined after that started, and SR5 is much shorter (and less prone to absurdly long validation syndrome), I would like to know for future reference the length of the cleanup.

Thank you.

Well, there's 90% and there's 90%....

In last years SR5 challenge thread you can see it took about 6 weeks for the number of units that influence scoring positions to reach zero. (Of which the last two weeks were waiting for one particular person to finish their wu.)
And 90% done was reached in about 2 weeks.
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)

Hello!
Good morning!

Seems like the statistics for the current challenge is missing! We are only a couple of hour into the challenge, so nobody have turned in some results yet?

Good luck every body and dig dip for some new primes!

With regards,

Hans Sveen
Oslo, Norway

We are off and running, 3 computers, crunching 16 wu's at a time. "Poor" little AMD is really struggling. Others are doing each in about 4 hours.
And yes, it sure was the middle of the night here too. Not even the midnight sun I saw so often in your country Sveen.

On my quad-core i3, these SR5-LLR tasks run between 27-40 hours minimum (none of these a prime so far). What I don't understand is why there is so much variance in processing time in tasks downloaded seconds apart with no other projects running. ???

Thank you for the advice. I set both the buffers to 10 days, and that happens to be exactly enough to download two SR5 workunits, so I get exactly the situation I was hoping for, with a "virtually zero" buffer.

I do think it will download new tasks even if my SoB tasks are paused, as it's just fulfilling the buffer, and my SoB tasks are paused individually, not project or BOINC wide.

We are off and running, 3 computers, crunching 16 wu's at a time. "Poor" little AMD is really struggling. Others are doing each in about 4 hours.
And yes, it sure was the middle of the night here too. Not even the midnight sun I saw so often in your country Sveen.

And I'm here, crunching on a dual core desktop that takes 12 hours each and a quad core laptop that takes ~22 hours each due to its underclock, thinking of upgrading my desktop to your "poor little AMD." *sigh*

On a happier note, here's to someone finding a prime!

it's taking me 6-7 hours on my i7-3820

I do think it will download new tasks even if my SoB tasks are paused, as it's just fulfilling the buffer, and my SoB tasks are paused individually, not project or BOINC wide.

Sorry, but that's a "feature" of BOINC.

It will not download any more PrimeGrid tasks while those SoB tasks are paused. 100% certain about that, unfortunately.

forget about the clicking-or-whatever-addon-software
use the builtin boinc-cmdline-tool "boinccmd" with
- windows: taskplaner
- unix/linux: atd (or crond)
see here: http://boinc.berkeley.edu/wiki/Boinccmd_tool

Hyperthreading, as a general rule, should always be off (or at least using only half the available 'cores') for any LLR tasks. However, sieves benefit from it, so it does require a little micromanagement when you want to switch sub-projects. However, the benefits of shorter time far outweigh having to change a setting in BOINC.

This is true. However, if you run PPS_Sieve tasks at the same time while the CPU has Hyperthreading enabled(LLR or Sieve, doesn't matter) your GPU output will suffer substantially. Your GPU will constantly be trying to find a stable "virtual" core to run on. In my experience, just leave Hyperthreading off period. Lower CPU temps, better GPU output.

Challenge update:

Normally, I try to post these updates close to the 24 hour, 48 hour, etc. points, but the timing for this challenge (~3 AM my time) doesn't lend itself to that.

Challenge: Solar Eclipse
App: 19 (SR5-LLR)
(As of 2015-03-16 11:36:34 UTC)

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

Of those tasks that have been sent out:

996 (2%) came back with some kind of an error. [996 (2%) / 0 (0%) / 0 (0%)]
13673 (31%) have returned a successful result. [13671 (31%) / 0 (0%) / 2 (0%)]
28857 (66%) are still in progress. [28855 (66%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

8178 (60%) are pending validation. [8178 (60%) / 0 (0%) / 0 (0%)]
5450 (40%) have been successfully validated. [5448 (40%) / 0 (0%) / 2 (0%)]
4 (0%) were invalid. [4 (0%) / 0 (0%) / 0 (0%)]
41 (0%) are inconclusive. [41 (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=1941427. The leading edge was at n=1916233 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.31% as much as it had prior to the challenge!


____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

Approximately 50% through the challenge:

Challenge: Solar Eclipse
App: 19 (SR5-LLR)
(As of 2015-03-17 20:34:00 UTC)

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

Of those tasks that have been sent out:

2778 (4%) came back with some kind of an error. [2778 (4%) / 0 (0%) / 0 (0%)]
37820 (52%) have returned a successful result. [37815 (52%) / 0 (0%) / 5 (0%)]
32132 (44%) are still in progress. [32130 (44%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

15100 (40%) are pending validation. [15098 (40%) / 0 (0%) / 2 (0%)]
22558 (60%) have been successfully validated. [22555 (60%) / 0 (0%) / 3 (0%)]
55 (0%) were invalid. [55 (0%) / 0 (0%) / 0 (0%)]
107 (0%) are inconclusive. [107 (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=1957756. The leading edge was at n=1916233 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.17% as much as it had prior to the challenge!

____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

Now that the challenge is full on, what are the chances of a prime being found during the challenge?

I took a peek at 2014's SR5 challenge as well as the prime tracker in the SR5 subforum. It seems a prime was found during the challenge last year. This year, the numbers are larger, but the challenge is also five days instead of three, and we have more people (like myself). I assume no primes have been found yet, as there hasn't been any announcement about a prime in the pipeline.

I also note that a prime hasn't been found since last October, which is six months ago. Did something significant happen to the number size then, or did the number of people doing SR5 decrease, or is it just a long gap in between primes?

MeFigaYoma,

You're right about one thing, there's a pretty big gap between the last SR/5 prime found and where we are now. Looking at the history below:

109208·5^1816285+1 (SR5): official announcement | k=109208 eliminated
325918·5^1803339+1 (SR5): official announcement | k=325918 eliminated
133778·5^1785689+1 (SR5): official announcement | k=133778 eliminated
24032·5^1768249+1 (SR5): official announcement | k=24032 eliminated
138172·5^1714207-1 (SR5): official announcement | k=138172 eliminated
22478·5^1675150-1 (SR5): official announcement | k=22478 eliminated
326834·5^1634978-1 (SR5): official announcement | k=326834 eliminated
207394·5^1612573-1 (SR5): official announcement | k=207394 eliminated
104944·5^1610735-1 (SR5): official announcement | k=104944 eliminated
330286·5^1584399-1 (SR5): official announcement | k=330286 eliminated
22934·5^1536762-1 (SR5): official announcement | k=22934 eliminated
178658·5^1525224-1 (SR5): official announcement | k=178658 eliminated
59912·5^1500861+1 (SR5): official announcement | k=59912 eliminated
37292·51487989+1 (SR5): official announcement | k=37292 eliminated
173198·51457792-1 (SR5): official announcement | k=173198 eliminated


We are now (or should be) at N=2,000,000. It wouldn't surprise me to see two SR/5 primes discovered before the end of the tourney based upon prior history (looks like 2 K's fall approximately every 100,000 N)....

Neo
AtP!

Indeed, we've been in an SR5 dry spell. We're due!
____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

Indeed, but perhaps not as much of a dry spell as we might think. If we look at the two different forms of primes that are being searched separately (i.e., the +1 and -1 varieties), then our "dry spell" might not seem excessively large. The largest "n" gap in our quite small sample is with the +1 variety and equals just over 267k (on the -1 side of things, the largest gap is only just over 67k). Most ranges are now at about a leading edge of 1,960k (with the back edge at about 1,888k). This puts the leading edge at about 246k beyond the last -1 find and about 144k beyond the last +1 find. Big gaps to be sure, but perhaps to be expected at times.

Thank you, what I am trying to figure out is should I upgrade my PhenomII 1045T.
...
Knowing the new CPUs have AVX instructions that I believe help in primegrid.
...
Is it worth the money, or just keep what I have.

Mass storage speed (be it SSD or hard drive) is of practically no consequence here. There are plenty of good reasons for buying fast/huge storage, but PrimeGrid isn't one. PG is all about CPU, memory bandwidth, and GPU.

g

with less than a day to go:

Challenge: Solar Eclipse
App: 19 (SR5-LLR)
(As of 2015-03-19 13:53:17 UTC)

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

Of those tasks that have been sent out:

7168 (6%) came back with some kind of an error. [7128 (6%) / 0 (0%) / 40 (0%)]
72528 (65%) have returned a successful result. [72518 (65%) / 0 (0%) / 10 (0%)]
32204 (29%) are still in progress. [32202 (29%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

18978 (26%) are pending validation. [18974 (26%) / 0 (0%) / 4 (0%)]
53203 (73%) have been successfully validated. [53197 (73%) / 0 (0%) / 6 (0%)]
169 (0%) were invalid. [169 (0%) / 0 (0%) / 0 (0%)]
178 (0%) are inconclusive. [178 (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=1978553. The leading edge was at n=1916233 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.25% as much as it had prior to the challenge!

There's about 17 hours to go. Will you be the one to find a prime and eliminate another k from either the Riesel or Sierpinski base 5 problems?
____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

With a little under 1 day left on the clock, it's time for the usual end of challenge reminder :)

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 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.
____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

***BREAKING NEWS***

Stars eclipsed by large white rat.

Ends


Thanks to all who took part and especially those who made it possible.


____________
Oh Bondage? Up Yours.

http://www.youtube.com/watch?v=ogypBUCb7DA

***BREAKING NEWS***
Stars eclipsed by large white rat.

Is the clock off or is it me? Looks like still over 4 hours remaining in the Challenge?

Nice challenge (returned my final workunit just 44 seconds before the end) and nice solar eclipse afterwards (about 80% and no clouds). :)
____________

The challenge is over! I hope everyone enjoyed the challenge, and if you were fortunate enough to be in position to see the real eclipse, hopefully you had clear skies and a good view!

Final statistics:

Challenge: Solar Eclipse
App: 19 (SR5-LLR)
(As of 2015-03-20 18:12:20 UTC)

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

Of those tasks that have been sent out:

16531 (13%) came back with some kind of an error. [16491 (13%) / 0 (0%) / 40 (0%)]
88870 (70%) have returned a successful result. [88858 (70%) / 0 (0%) / 12 (0%)]
12724 (10%) are still in progress. [12724 (10%) / 0 (0%) / 0 (0%)]

Of the tasks that have been returned successfully:

13313 (15%) are pending validation. [13310 (15%) / 0 (0%) / 3 (0%)]
75158 (85%) have been successfully validated. [75149 (85%) / 0 (0%) / 9 (0%)]
253 (0%) were invalid. [253 (0%) / 0 (0%) / 0 (0%)]
146 (0%) are inconclusive. [146 (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=1984312. The leading edge was at n=1916233 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.55% as much as it had prior to the challenge!

____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

Cleanup status:

20-Mar: Solar Eclipse: 15149 tasks outstanding; 12843 affecting individual (297) scoring positions; 11948 affecting team (82) scoring positions.

Although the tasks are short, the task deadlines are long to allow for extra processing that occurs when your computer finds a prime. The length of the cleanup is related to the length of the deadline rather than the length of the tasks, so I expect this cleanup to take between 6 and 12 weeks.
____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

Nice challenge (returned my final workunit just 44 seconds before the end) and nice solar eclipse afterwards (about 80% and no clouds). :)

Cleanup status:

20-Mar: Solar Eclipse: 15149 tasks outstanding; 12843 affecting individual (297) scoring positions; 11948 affecting team (82) scoring positions.
21-Mar: Solar Eclipse: 9221 tasks outstanding; 7046 affecting individual (292) scoring positions; 4369 affecting team (64) scoring positions.
22-Mar: Solar Eclipse: 7688 tasks outstanding; 5866 affecting individual (289) scoring positions; 3515 affecting team (58) scoring positions.
23-Mar: Solar Eclipse: 6787 tasks outstanding; 5164 affecting individual (288) scoring positions; 3034 affecting team (55) scoring positions.
24-Mar: Solar Eclipse: 6165 tasks outstanding; 4621 affecting individual (284) scoring positions; 2762 affecting team (55) scoring positions.
25-Mar: Solar Eclipse: 5732 tasks outstanding; 4266 affecting individual (283) scoring positions; 2416 affecting team (51) scoring positions.
26-Mar: Solar Eclipse: 5339 tasks outstanding; 3957 affecting individual (282) scoring positions; 2233 affecting team (49) scoring positions.
27-Mar: Solar Eclipse: 5004 tasks outstanding; 3676 affecting individual (277) scoring positions; 2093 affecting team (47) scoring positions.
____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

There will be at least 3 SR5 work units that I downloaded but was unable to return before the end of the challenge, due to one of my computers deciding it was a nice day to die.

Nothing I have so far been able to do can get a spark out of it, seems to be a motherboard failure. I will need a few days to get parts and build a new machine.
I think the CPU (an AMD Phenom II X6 1100) is still OK, that way I just have to but an new AM3+ motherboard and I will be able to update to later chips as finance is available.

Also I am hoping that the Hard drives are still OK and all my (not backed up) data is OK as well, I was going to back it up over the last few weeks but kept forgetting, nice of fate to force my hand.

So I can't even abort those work units at this stage, if I can get things working again I may still be able to return the WUs before the deadline but I doubt it.

The (expensive) joys of computing, they say it is all fun and games, I say that depends on what you are playing.

Conan

Cleanup status:

20-Mar: Solar Eclipse: 15149 tasks outstanding; 12843 affecting individual (297) scoring positions; 11948 affecting team (82) scoring positions.
21-Mar: Solar Eclipse: 9221 tasks outstanding; 7046 affecting individual (292) scoring positions; 4369 affecting team (64) scoring positions.
22-Mar: Solar Eclipse: 7688 tasks outstanding; 5866 affecting individual (289) scoring positions; 3515 affecting team (58) scoring positions.
23-Mar: Solar Eclipse: 6787 tasks outstanding; 5164 affecting individual (288) scoring positions; 3034 affecting team (55) scoring positions.
24-Mar: Solar Eclipse: 6165 tasks outstanding; 4621 affecting individual (284) scoring positions; 2762 affecting team (55) scoring positions.
25-Mar: Solar Eclipse: 5732 tasks outstanding; 4266 affecting individual (283) scoring positions; 2416 affecting team (51) scoring positions.
26-Mar: Solar Eclipse: 5339 tasks outstanding; 3957 affecting individual (282) scoring positions; 2233 affecting team (49) scoring positions.
27-Mar: Solar Eclipse: 5004 tasks outstanding; 3676 affecting individual (277) scoring positions; 2093 affecting team (47) scoring positions.
28-Mar: Solar Eclipse: 4780 tasks outstanding; 3469 affecting individual (276) scoring positions; 1998 affecting team (47) scoring positions.


____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

Cleanup status:

20-Mar: Solar Eclipse: 15149 tasks outstanding; 12843 affecting individual (297) scoring positions; 11948 affecting team (82) scoring positions.
21-Mar: Solar Eclipse: 9221 tasks outstanding; 7046 affecting individual (292) scoring positions; 4369 affecting team (64) scoring positions.
22-Mar: Solar Eclipse: 7688 tasks outstanding; 5866 affecting individual (289) scoring positions; 3515 affecting team (58) scoring positions.
23-Mar: Solar Eclipse: 6787 tasks outstanding; 5164 affecting individual (288) scoring positions; 3034 affecting team (55) scoring positions.
24-Mar: Solar Eclipse: 6165 tasks outstanding; 4621 affecting individual (284) scoring positions; 2762 affecting team (55) scoring positions.
25-Mar: Solar Eclipse: 5732 tasks outstanding; 4266 affecting individual (283) scoring positions; 2416 affecting team (51) scoring positions.
26-Mar: Solar Eclipse: 5339 tasks outstanding; 3957 affecting individual (282) scoring positions; 2233 affecting team (49) scoring positions.
27-Mar: Solar Eclipse: 5004 tasks outstanding; 3676 affecting individual (277) scoring positions; 2093 affecting team (47) scoring positions.
28-Mar: Solar Eclipse: 4780 tasks outstanding; 3469 affecting individual (276) scoring positions; 1998 affecting team (47) scoring positions.
29-Mar: Solar Eclipse: 4532 tasks outstanding; 3286 affecting individual (273) scoring positions; 1909 affecting team (47) scoring positions.
30-Mar: Solar Eclipse: 4247 tasks outstanding; 3012 affecting individual (266) scoring positions; 1789 affecting team (47) scoring positions.
31-Mar: Solar Eclipse: 3624 tasks outstanding; 2485 affecting individual (253) scoring positions; 1133 affecting team (39) scoring positions.
____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

Cleanup status:

20-Mar: Solar Eclipse: 15149 tasks outstanding; 12843 affecting individual (297) scoring positions; 11948 affecting team (82) scoring positions.
1-Apr: Solar Eclipse: 2738 tasks outstanding; 1842 affecting individual (236) scoring positions; 730 affecting team (29) scoring positions.
2-Apr: Solar Eclipse: 1639 tasks outstanding; 958 affecting individual (186) scoring positions; 322 affecting team (18) scoring positions.
3-Apr: Solar Eclipse: 1427 tasks outstanding; 805 affecting individual (172) scoring positions; 268 affecting team (17) scoring positions.
4-Apr: Solar Eclipse: 995 tasks outstanding; 512 affecting individual (145) scoring positions; 129 affecting team (10) scoring positions.
5-Apr: Solar Eclipse: 615 tasks outstanding; 263 affecting individual (98) scoring positions; 9 affecting team (5) scoring positions.
6-Apr: Solar Eclipse: 486 tasks outstanding; 184 affecting individual (83) scoring positions; 7 affecting team (3) scoring positions.
7-Apr: Solar Eclipse: 405 tasks outstanding; 139 affecting individual (69) scoring positions; 4 affecting team (2) scoring positions.
8-Apr: Solar Eclipse: 378 tasks outstanding; 121 affecting individual (64) scoring positions; 4 affecting team (2) scoring positions.
9-Apr: Solar Eclipse: 287 tasks outstanding; 81 affecting individual (53) scoring positions; 3 affecting team (2) scoring positions.
10-Apr: Solar Eclipse: 262 tasks outstanding; 75 affecting individual (49) scoring positions; 3 affecting team (2) scoring positions.
11-Apr: Solar Eclipse: 235 tasks outstanding; 64 affecting individual (45) scoring positions; 3 affecting team (2) scoring positions.
12-Apr: Solar Eclipse: 225 tasks outstanding; 61 affecting individual (43) scoring positions; 3 affecting team (2) scoring positions.
13-Apr: Solar Eclipse: 202 tasks outstanding; 51 affecting individual (39) scoring positions; 3 affecting team (2) scoring positions.
14-Apr: Solar Eclipse: 179 tasks outstanding; 43 affecting individual (36) scoring positions; 3 affecting team (2) scoring positions.
15-Apr: Solar Eclipse: 149 tasks outstanding; 32 affecting individual (28) scoring positions; 1 affecting team (1) scoring positions.
16-Apr: Solar Eclipse: 133 tasks outstanding; 29 affecting individual (25) scoring positions; 1 affecting team (1) scoring positions.
17-Apr: Solar Eclipse: 102 tasks outstanding; 23 affecting individual (21) scoring positions; 1 affecting team (1) scoring positions.
18-Apr: Solar Eclipse: 56 tasks outstanding; 10 affecting individual (10) scoring positions; 1 affecting team (1) scoring positions.
19-Apr: Solar Eclipse: 43 tasks outstanding; 9 affecting individual (9) scoring positions; 1 affecting team (1) scoring positions.
20-Apr: Solar Eclipse: 32 tasks outstanding; 6 affecting individual (6) scoring positions; 0 affecting team (0) scoring positions.
21-Apr: Solar Eclipse: 29 tasks outstanding; 5 affecting individual (5) scoring positions; 0 affecting team (0) scoring positions.
22-Apr: Solar Eclipse: 19 tasks outstanding; 4 affecting individual (4) scoring positions; 0 affecting team (0) scoring positions.
23-Apr: Solar Eclipse: 13 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
24-Apr: Solar Eclipse: 12 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
25-Apr: Solar Eclipse: 11 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
26-Apr: Solar Eclipse: 10 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
27-Apr: Solar Eclipse: 10 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
28-Apr: Solar Eclipse: 6 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
29-Apr: Solar Eclipse: 6 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
30-Apr: Solar Eclipse: 3 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

Cleanup status:

20-Mar: Solar Eclipse: 15149 tasks outstanding; 12843 affecting individual (297) scoring positions; 11948 affecting team (82) scoring positions.
1-Apr: Solar Eclipse: 2738 tasks outstanding; 1842 affecting individual (236) scoring positions; 730 affecting team (29) scoring positions.
1-May: Solar Eclipse: 3 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
2-May: Solar Eclipse: 1 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

Congratulations to the winners!


The cleanup has completed, and we can now officially announce the winners.


Individual winners:

First place: zunewantan
Second place: Retnek
Third place: Scott Brown


Team winners:

First place: Aggie The Pew
Second place: SETI.Germany
Third place: Sicituradastra.


Congratulations to zunewantan and team Aggie The Pew, and thanks to everyone for participating!
____________
My lucky number is 75898^524288+1
Please do not PM me with support questions. They will usually go unanswered. Ask on the forums instead. Thank you!

Cleanup status:

20-Mar: Solar Eclipse: 15149 tasks outstanding; 12843 affecting individual (297) scoring positions; 11948 affecting team (82) scoring positions.

Although the tasks are short, the task deadlines are long to allow for extra processing that occurs when your computer finds a prime. The length of the cleanup is related to the length of the deadline rather than the length of the tasks, so I expect this cleanup to take between 6 and 12 weeks.

And the overall leaderboard has been updatet too :) This challenge is, for now, the only one on it :)
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)