Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Number crunching :
Diwali/Deepavali Challenge
| Author |
Message |
|---|
 RogerVolunteer developer
Volunteer tester
Send message
Joined: 27 Nov 11
Posts: 1138
ID: 120786
Credit: 268,668,824
RAC: 0
                    
|
|
Welcome to the Diwali/Deepavali Challenge
The sixth Challenge of the 2017 Challenge series is a 5 day challenge to celebrate Diwali/Deepavali. The challenge is being offered on the The Riesel Problem (LLR) application.
Diwali or Deepavali is the Hindu festival of lights celebrated every year in autumn in the northern hemisphere. One of the most popular festivals of Hinduism, it spiritually signifies the victory of light over darkness, good over evil, knowledge over ignorance, and hope over despair. Its celebration includes millions of lights shining on housetops, outside doors and windows, around temples and other buildings in the communities and countries where it is observed. The festival preparations and rituals typically extend over a five-day period, but the main festival night of Diwali coincides with the darkest, new moon night of the Hindu Lunisolar month Kartika in Bikram Sambat calendar. In the Gregorian calendar, Diwali night falls between mid-October and mid-November.
Before Diwali night, people clean, renovate, and decorate their homes and offices. On Diwali night, people dress up in new clothes or their best outfit, light up diyas (lamps and candles) inside and outside their home, participate in family puja (prayers) typically to Lakshmi – the goddess of fertility and prosperity. After puja, fireworks follow, then a family feast including mithai (sweets), and an exchange of gifts between family members and close friends. Deepavali also marks a major shopping period in nations where it is celebrated.
On the same night that Hindus celebrate Diwali, Jains celebrate a festival also called Diwali to mark the attainment of moksha by Mahavira, Sikhs celebrate Bandi Chhor Divas to mark the release of Guru Hargobind from a Mughal Empire prison, and Newar Buddhists, unlike the majority of Buddhists, celebrate Diwali by worshipping Lakshmi.
To participate in the Challenge, please select only the The Riesel Problem (LLR) project in your PrimeGrid preferences section. The challenge will begin 18th October 2017 00:00 UTC and end 23rd October 2017 00:00 UTC. Note the non-standard start time.
Any prime we find in this challenge would be the first TRP k we will have eliminated in over 3 years!
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 will take ~16 hours on fast/newer computers and 48+ 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. :)
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 TRP 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 is also now available, and can speed up tasks, giving you a greater chance of being the Prime finder.
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 tasks issued AFTER 18 October 2017 00:00 UTC and received BEFORE 23rd October 2017 00:00 UTC will be considered for credit. We will be using the same scoring method as we currently use for BOINC credits. A quorum of 2 is NOT needed to award Challenge score - i.e. no double checker. Therefore, each returned result will earn a Challenge score. Please note that if the result is eventually declared invalid, the score will be removed.
At the Conclusion of the Challenge
We kindly ask users "moving on" to ABORT their tasks instead of DETACHING, RESETTING, or PAUSING.
ABORTING tasks allows them to be recycled immediately; thus a much faster "clean up" to the end of an LLR Challenge. DETACHING, RESETTING, and PAUSING tasks causes them to remain in limbo until they EXPIRE. Therefore, we must wait until tasks expire to send them out to be completed.
Please consider either completing what's in the queue or ABORTING them. Thank you. :)
About the Riesel Problem
Hans Ivar Riesel (May 28, 1929 in Stockholm - December 21, 2014) was a Swedish mathematician. In 1956, he showed that there are an infinite number of positive odd integer k's such that k*2^n-1 is composite (not prime) for every integer n>=1. These numbers are now called Riesel numbers. He further showed that k=509203 was such one.
It is conjectured that 509203 is the smallest Riesel number. The Riesel problem consists of determining that 509203 is the smallest Riesel number. To show that it is the smallest, a prime of the form k*2^n-1 must be found for each of the positive integer k's less than 509203. As of October 8th, 2017, there remain 50 k's for which no primes have been found. They are as follows:
2293, 9221, 23669, 31859, 38473, 46663, 67117, 74699, 81041, 93839, 97139, 107347, 121889, 129007, 143047, 146561, 161669, 192971, 206039, 206231, 215443, 226153, 234343, 245561, 250027, 273809, 315929, 319511, 324011, 325123, 327671, 336839, 342847, 344759, 362609, 363343, 364903, 365159, 368411, 371893, 384539, 386801, 397027, 409753, 444637, 470173, 474491, 477583, 485557, 494743
For a more detailed history and status of the Riesel problem, please visit Wilfrid Keller's The Riesel Problem: Definition and Status.
Last Primes found at PrimeGrid
402539*2^7173024-1 by Walter Darimont on 2 October 2014. Official Announcement.
502573*2^7181987-1 by Denis Iakovlev on 4 October 2014. Official Announcement.
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:
(Edouard Lucas: 1842-1891, Derrick H. Lehmer: 1905-1991, Hans Riesel: 1929-2014).
____________
| |
|
Michael Goetz Volunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
                            
|
|
If you want to use multi-threading, this is what app_config.xml looks like TRP:
<app>
<name>llrTRP</name>
<max_concurrent>1</max_concurrent>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrTRP</app_name>
<cmdline>-t 4</cmdline>
<avg_ncpus>4</avg_ncpus>
</app_version>
That's for using all four cores on a 4 core CPU. Adjust as needed for your specific hardware and preferences.
____________
My lucky number is 75898524288+1 | |
|
|
|
If you want to use multi-threading, this is what app_config.xml looks like TRP:
<app>
<name>llrTRP</name>
<max_concurrent>1</max_concurrent>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrTRP</app_name>
<cmdline>-t 4</cmdline>
<avg_ncpus>4</avg_ncpus>
</app_version>
That's for using all four cores on a 4 core CPU. Adjust as needed for your specific hardware and preferences.
Nice, thank you very much for Posting this.
I see that <max_ncpus>4</max_ncpus> is not used anymore?
____________
Crunching@EVGA The Number One Team in the BOINC Community. Folding@EVGA The Number One Team in the Folding@Home Community. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
Nice, thank you very much for Posting this.
I see that <max_ncpus>4</max_ncpus> is not used anymore?
It never was used, despite a lot of people including it in their examples.
At least not in app_config.xml.
It is used in app_info.xml, but is not used in app_config.xml. In app_config.xml it's ignored, and doesn't hurt anything. People reasonably assumed that if both were used in app_info.xml (which came first), then both should also be used in app_config.xml. But that's not true: app_config.xml only uses the <avg_ncpus> tag.
____________
My lucky number is 75898524288+1 | |
|
Ken_g6Volunteer developer
Send message
Joined: 4 Jul 06
Posts: 938
ID: 3110
Credit: 258,343,096
RAC: 82,001
                
|
|
I haven't found a need for the <app> section either. <app_version> alone seems sufficient.
____________
| |
|
|
|
|
Another fun challenge, thanks. Just started a few months ago and am trying to find a project I can really get into. 321 was cool, but I'm seeing mega primes being found with the PPS LLR, PSP, SR5, and GFN applications. The plan was to run all the projects to Gold, then figure out which my computers and I liked. Will run all my Haswells during this competition leaving a spare core idle to keep my temps down. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
Reminder: This challenge starts at 00:00, not 18:00. That means it starts about 7 hours from now rather than 25 hours from now. Don't be late!
____________
My lucky number is 75898524288+1 | |
|
|
|
|
How do I configure multi CPU? I can't find any app_config.xml. Using latest Boinc and only have one instance of TRP LLR 8.0 running and not using much CPU.
I have it as the only selected option in my Prime Grid prefs. | |
|
RafaelVolunteer tester
Send message
Joined: 22 Oct 14
Posts: 909
ID: 370496
Credit: 528,656,660
RAC: 383,837
                
|
How do I configure multi CPU? I can't find any app_config.xml. Using latest Boinc and only have one instance of TRP LLR 8.0 running and not using much CPU.
I have it as the only selected option in my Prime Grid prefs.
You have to create that file. On a default BOINC installation, open notepad and save as app_config.xml onto C:\ProgramData\BOINC\projects\www.primegrid.com
There, you have to manually put the tags. I'll give mine as an example, it's what I use on my i5. It's set to use 3 cores so that I have 1 free for my GPU, but you can change the -t 3 and avg_ncpus parameters to accomodate your needs.
<app_config>
<app>
<name>llrTRP</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrTRP</app_name>
<cmdline>-t 3</cmdline>
<avg_ncpus>3</avg_ncpus>
</app_version>
</app_config> | |
|
|
|
open notepad
I couldn't get notepad to save it as an xml file. I downloaded notepad++ for free and used that and it worked.
You need to refresh the settings after you have updated the xml file. You can find out how to do that elsewhere on the forums so I won't repeat it here. | |
|
|
|
|
Thank you got it running. My last questions are - If I have 4 core but 8 for hyperthreading do I sill use 4 or 8 in the .xml file? Also no GPU support?
How do I configure multi CPU? I can't find any app_config.xml. Using latest Boinc and only have one instance of TRP LLR 8.0 running and not using much CPU.
I have it as the only selected option in my Prime Grid prefs.
You have to create that file. On a default BOINC installation, open notepad and save as app_config.xml onto C:\ProgramData\BOINC\projects\www.primegrid.com
There, you have to manually put the tags. I'll give mine as an example, it's what I use on my i5. It's set to use 3 cores so that I have 1 free for my GPU, but you can change the -t 3 and avg_ncpus parameters to accomodate your needs.
<app_config>
<app>
<name>llrTRP</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrTRP</app_name>
<cmdline>-t 3</cmdline>
<avg_ncpus>3</avg_ncpus>
</app_version>
</app_config>
| |
|
|
|
I couldn't get notepad to save it as an xml file. I downloaded notepad++ for free and used that and it worked.
You can use Windows Notepad to save as *.xml in the Save As dialog box by clicking on 'Save as type' drop down menu to save as 'All Files' and then type in filename 'app_config.xml'. Or you can save as the default *.txt file and rename it, as it is a simple ASCII text file. | |
|
|
|
Thank you got it running. My last questions are - If I have 4 core but 8 for hyperthreading do I sill use 4 or 8 in the .xml file? Also no GPU support?
On a quad core CPU, disable hyperthreading in BIOS generally works best. You can also go into BOINC manager Options > Computing preferences to specify 'Use at most 50% of the CPUs' to use 4 of available 8 threads when hyperthreading is enabled on a quad core CPU. I prefer the first method.
No GPU app for TRP (LLR) - CPU, only. | |
|
RafaelVolunteer tester
Send message
Joined: 22 Oct 14
Posts: 909
ID: 370496
Credit: 528,656,660
RAC: 383,837
|
Thank you got it running. My last questions are - If I have 4 core but 8 for hyperthreading do I sill use 4 or 8 in the .xml file?
If you can disable HT, that's preferred option. If you can, go into Boinc settings and make it so that you only use 50% of the CPUs. Regardless, I suggest using t4, unless you want to leave a core free for something (say, a GPU)
Also no GPU support?
No, LLR doesn't support GPUs. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
Stats after day 1:
Challenge: Diwali/Deepavali
App: 15 (TRP-LLR)
(As of 2017-10-19 00:00:10 UTC)
23008 tasks have been sent out. [CPU/GPU/anonymous_platform: 22966 (100%) / 0 (0%) / 42 (0%)]
Of those tasks that have been sent out:
1340 (6%) came back with some kind of an error. [1340 (6%) / 0 (0%) / 0 (0%)]
5079 (22%) have returned a successful result. [5044 (22%) / 0 (0%) / 35 (0%)]
16589 (72%) are still in progress. [16582 (72%) / 0 (0%) / 7 (0%)]
Of the tasks that have been returned successfully:
3601 (71%) are pending validation. [3576 (70%) / 0 (0%) / 25 (0%)]
1467 (29%) have been successfully validated. [1457 (29%) / 0 (0%) / 10 (0%)]
2 (0%) were invalid. [2 (0%) / 0 (0%) / 0 (0%)]
9 (0%) are inconclusive. [9 (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=8696159. The leading edge was at n=8611827 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.98% as much as it had prior to the challenge!
On a normal day, we do about 1000 TRP tasks, so depending on which number you use we're doing somewhere between 5x and 20x the normal daily processing.
Last time we found a TRP prime, we found 2 primes in 3 days. Can we find one during this challenge?
____________
My lucky number is 75898524288+1 | |
|
|
|
|
We are past the astronomical new moon of the Diwali which (wrt. the center of the Earth) occurred at 19:12 universal time (that is 00:42 Indian Standard Time). /JeppeSN | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
After 2 days:
Challenge: Diwali/Deepavali
App: 15 (TRP-LLR)
(As of 2017-10-20 01:39:41 UTC)
32979 tasks have been sent out. [CPU/GPU/anonymous_platform: 32898 (100%) / 0 (0%) / 81 (0%)]
Of those tasks that have been sent out:
2362 (7%) came back with some kind of an error. [2362 (7%) / 0 (0%) / 0 (0%)]
13396 (41%) have returned a successful result. [13323 (40%) / 0 (0%) / 73 (0%)]
17221 (52%) are still in progress. [17213 (52%) / 0 (0%) / 8 (0%)]
Of the tasks that have been returned successfully:
6685 (50%) are pending validation. [6643 (50%) / 0 (0%) / 42 (0%)]
6660 (50%) have been successfully validated. [6629 (49%) / 0 (0%) / 31 (0%)]
13 (0%) were invalid. [13 (0%) / 0 (0%) / 0 (0%)]
38 (0%) are inconclusive. [38 (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=8730467. The leading edge was at n=8611827 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.38% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
|
|
|
Hi.
In the beginning I had some tasks which ran quite long, and now the tasks finish after significantly less time.
Is there a reason for this on the project side?
Thanks.
____________
Greetings, Jens
147433824^131072+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
Hi.
In the beginning I had some tasks which ran quite long, and now the tasks finish after significantly less time.
Is there a reason for this on the project side?
Thanks.
I don't have a definite explanation for the difference. It's not something one would expect to see.
The only thing that comes to mind is that perhaps the computer is significantly overheating and the CPU is slowing down to lower the temperature and protect the CPU?
Another possibility is that the earlier tasks ran while hyperthreading was turned off (or only 4 threads were active), and later tasks were run with hyperthreading turned on and all 8 threads running LLR.
Both scenarios would effectively cause the CPU to slow down. It looks as if the CPU is indeed running slower on the later tasks, but I can't tell from here what the cause might be.
____________
My lucky number is 75898524288+1 | |
|
RogerVolunteer developer
Volunteer tester
Send message
Joined: 27 Nov 11
Posts: 1138
ID: 120786
Credit: 268,668,824
RAC: 0
|
Hi.
In the beginning I had some tasks which ran quite long, and now the tasks finish after significantly less time.
Is there a reason for this on the project side?
Thanks.
Different k on TRP range from 2,293 to 494,743.
You will see different run time lengths depending on the k.
I don't think the user can determine which k was run. You used to be able to determine this.
Note that some k's, if they are found, would also knock off outstanding k's on higher bases:
k=2,293 testing is the same as base 4 k=4,586 and base 16 k=18,344.
k=9,221 testing is the same as base 4 for the same k-value.
k=23,669 and 31,859 testing are the same as bases 4 and 16 for the same k-value.
Extra kudos for finding those. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
Hi.
In the beginning I had some tasks which ran quite long, and now the tasks finish after significantly less time.
Is there a reason for this on the project side?
Thanks.
Different k on TRP range from 2,293 to 494,743.
You will see different run time lengths depending on the k.
I don't think the user can determine which k was run. You used to be able to determine this.
are the same as bases 4 and 16 for the same k-value.
Extra kudos for finding those.
The timing differences he's seeing are much too large to be the result of different FFT sizes. Also, the timing differences don't correspond to similar differences in credit, which you would expect if the tasks were of different lengths. His run times, and cpu times, vary from about 40K seconds to about 130K seconds, while credit only varies by about 20% at most.
The cpu-times seem to vary over a range consistent with both running with and without hyperthreading. My best guess is that the longer times occurred when all 8 threads were busy running LLR, and the faster times happened when only 4 were running LLR.
____________
My lucky number is 75898524288+1 | |
|
|
|
Note that some k's, if they are found, would also knock off outstanding k's on higher bases:
k=2,293 testing is the same as base 4 k=4,586 and base 16 k=18,344.
k=9,221 testing is the same as base 4 for the same k-value.
k=23,669 and 31,859 testing are the same as bases 4 and 16 for the same k-value.
Extra kudos for finding those.
True. But for a related reason, maybe one should not even consider bases b that are perfect squares (or more generally perfect powers, b = c^m). If a number can be written as k*b^n ± 1, then it seems natural to choose the base b such that it is not a perfect power, by "moving out" the exponent if needed, (c^m)^n = c^(mn).
If we still allow perfect-power bases, a find like 402539*2^7173024 - 1 can be written in many ways, since 7173024 is divisible by 2^5 and by 3. For example:
402539*2^7173024 - 1
= 402539*4^3586512 - 1
= 402539*8^2391008 - 1
= 402539*16^1793256 - 1
= 402539*64^1195504 - 1
and so on.
I guess for some k values (unlike those you mentioned) in TRP, you cannot know in advance if a prime k*2^n - 1 can also be written with a perfect-power base, but we can still be "lucky".
/JeppeSN | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
After 3 days:
Challenge: Diwali/Deepavali
App: 15 (TRP-LLR)
(As of 2017-10-21 03:10:40 UTC)
42208 tasks have been sent out. [CPU/GPU/anonymous_platform: 42089 (100%) / 0 (0%) / 119 (0%)]
Of those tasks that have been sent out:
4221 (10%) came back with some kind of an error. [4221 (10%) / 0 (0%) / 0 (0%)]
22675 (54%) have returned a successful result. [22564 (53%) / 0 (0%) / 111 (0%)]
15312 (36%) are still in progress. [15304 (36%) / 0 (0%) / 8 (0%)]
Of the tasks that have been returned successfully:
8121 (36%) are pending validation. [8076 (36%) / 0 (0%) / 45 (0%)]
14456 (64%) have been successfully validated. [14390 (63%) / 0 (0%) / 66 (0%)]
42 (0%) were invalid. [42 (0%) / 0 (0%) / 0 (0%)]
56 (0%) are inconclusive. [56 (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=8758644. The leading edge was at n=8611827 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!
____________
My lucky number is 75898524288+1 | |
|
|
|
Hi.
In the beginning I had some tasks which ran quite long, and now the tasks finish after significantly less time.
Is there a reason for this on the project side?
Thanks.
Different k on TRP range from 2,293 to 494,743.
You will see different run time lengths depending on the k.
I don't think the user can determine which k was run. You used to be able to determine this.
are the same as bases 4 and 16 for the same k-value.
Extra kudos for finding those.
The timing differences he's seeing are much too large to be the result of different FFT sizes. Also, the timing differences don't correspond to similar differences in credit, which you would expect if the tasks were of different lengths. His run times, and cpu times, vary from about 40K seconds to about 130K seconds, while credit only varies by about 20% at most.
The cpu-times seem to vary over a range consistent with both running with and without hyperthreading. My best guess is that the longer times occurred when all 8 threads were busy running LLR, and the faster times happened when only 4 were running LLR.
Thanks for thinking about this.
I've been running the i7 with hyperthreading turned on all the time. In the beginning I only had one four-core task running with two WCG tasks beside it, and since those have finished I've been running two four-core tasks simultaneously. I'm talking about the i7 here. Still running AP27 or PPS-Sieve beside the cpu-tasks.
On the Octopus (octacore Opteron processor) I'm having quite different run-times as well. Two quad-core task running there as well.
On my Mac Mini Server and my snow mini I'm encountering run-times which seem to be just opposites of each other machine: While one has the first task short and the second longer, it's vice versa on the other machine. The snow mini has no tasks beside running Boinc atm, while the server is serving files.
The three Linux boxes are just running PrimeGrid while having Firefox in RAM.
The i7 is running a Boinc update script to try to get work from a certain project every sixty minutes. Haven't gotten any until now...
____________
Greetings, Jens
147433824^131072+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
4 days done!
Challenge: Diwali/Deepavali
App: 15 (TRP-LLR)
(As of 2017-10-22 05:05:04 UTC)
51718 tasks have been sent out. [CPU/GPU/anonymous_platform: 51561 (100%) / 0 (0%) / 157 (0%)]
Of those tasks that have been sent out:
5201 (10%) came back with some kind of an error. [5201 (10%) / 0 (0%) / 0 (0%)]
32294 (62%) have returned a successful result. [32144 (62%) / 0 (0%) / 150 (0%)]
14223 (28%) are still in progress. [14216 (27%) / 0 (0%) / 7 (0%)]
Of the tasks that have been returned successfully:
8649 (27%) are pending validation. [8600 (27%) / 0 (0%) / 49 (0%)]
23484 (73%) have been successfully validated. [23383 (72%) / 0 (0%) / 101 (0%)]
78 (0%) were invalid. [78 (0%) / 0 (0%) / 0 (0%)]
83 (0%) are inconclusive. [83 (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=8791896. The leading edge was at n=8611827 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.09% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
With one day remaining in the challenge, it's time for our public service announcement about helping at the end of the challenge...
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 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
And we're done! Final statistics:
Challenge: Diwali/Deepavali
App: 15 (TRP-LLR)
(As of 2017-10-23 01:14:13 UTC)
57471 tasks have been sent out. [CPU/GPU/anonymous_platform: 57198 (100%) / 0 (0%) / 273 (0%)]
Of those tasks that have been sent out:
7635 (13%) came back with some kind of an error. [7635 (13%) / 0 (0%) / 0 (0%)]
40180 (70%) have returned a successful result. [40002 (70%) / 0 (0%) / 178 (0%)]
8809 (15%) are still in progress. [8716 (15%) / 0 (0%) / 93 (0%)]
Of the tasks that have been returned successfully:
7342 (18%) are pending validation. [7307 (18%) / 0 (0%) / 35 (0%)]
32640 (81%) have been successfully validated. [32497 (81%) / 0 (0%) / 143 (0%)]
128 (0%) were invalid. [128 (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=8804328. The leading edge was at n=8611827 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.24% as much as it had prior to the challenge!
Alas, we failed to find a prime during the challenge. We've checked 200 thousand candidates since the last prime was found, and we checked another 20 thousand during this challenge.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
Now the cleanup begins. I expect the cleanup to between 18 and 36 days.
Cleanup Status:
22-Oct: Diwali/Deepavali: 7413 tasks outstanding; 6342 affecting individual (291) scoring positions; 4311 affecting team (65) scoring positions.
23-Oct: Diwali/Deepavali: 5801 tasks outstanding; 4823 affecting individual (286) scoring positions; 3240 affecting team (58) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
compositeVolunteer tester
Send message
Joined: 16 Feb 10
Posts: 1140
ID: 55391
Credit: 1,016,995,917
RAC: 1,679,199
         
|
|
Is this workunit counted as challenge cleanup or just regular work? Both initial tasks for it were issued during the challenge, and they were both aborted after the challenge ended. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
Is this workunit counted as challenge cleanup or just regular work? Both initial tasks for it were issued during the challenge, and they were both aborted after the challenge ended.
That doesn't count as part of the cleanup.
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
Cleanup Status:
22-Oct: Diwali/Deepavali: 7413 tasks outstanding; 6342 affecting individual (291) scoring positions; 4311 affecting team (65) scoring positions.
23-Oct: Diwali/Deepavali: 5801 tasks outstanding; 4823 affecting individual (286) scoring positions; 3240 affecting team (58) scoring positions.
24-Oct: Diwali/Deepavali: 3510 tasks outstanding; 2763 affecting individual (263) scoring positions; 1840 affecting team (45) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
compositeVolunteer tester
Send message
Joined: 16 Feb 10
Posts: 1140
ID: 55391
Credit: 1,016,995,917
RAC: 1,679,199
|
Is this workunit counted as challenge cleanup or just regular work? Both initial tasks for it were issued during the challenge, and they were both aborted after the challenge ended.
That doesn't count as part of the cleanup.
Then it would be nice if the server has a "challenge cleanup" option that I could select, which would send longer tasks only if they are cleanup tasks and something short like PPSE LLR when none are available, until such time as cleanup is done (and maybe this option would work only for reliable hosts). That task was handed to me because there was no cleanup work available at the time. Not a big loss, TRP LLR turnaround for me is about 5300 to 7000 seconds. It would be much longer without multithreading. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
Is this workunit counted as challenge cleanup or just regular work? Both initial tasks for it were issued during the challenge, and they were both aborted after the challenge ended.
That doesn't count as part of the cleanup.
Then it would be nice if the server has a "challenge cleanup" option that I could select, which would send longer tasks only if they are cleanup tasks and something short like PPSE LLR when none are available, until such time as cleanup is done (and maybe this option would work only for reliable hosts). That task was handed to me because there was no cleanup work available at the time. Not a big loss, TRP LLR turnaround for me is about 5300 to 7000 seconds. It would be much longer without multithreading.
Getting the cleanup tasks sent out to hosts is rarely a problem, so such an option would add complexity but not add any value. If you wish to run PPSE, please run PPSE. There's plenty of people who want to run TRP (or any other project.)
____________
My lucky number is 75898524288+1 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
Cleanup Status:
22-Oct: Diwali/Deepavali: 7413 tasks outstanding; 6342 affecting individual (291) scoring positions; 4311 affecting team (65) scoring positions.
23-Oct: Diwali/Deepavali: 5801 tasks outstanding; 4823 affecting individual (286) scoring positions; 3240 affecting team (58) scoring positions.
24-Oct: Diwali/Deepavali: 3510 tasks outstanding; 2763 affecting individual (263) scoring positions; 1840 affecting team (45) scoring positions.
25-Oct: Diwali/Deepavali: 2551 tasks outstanding; 1668 affecting individual (240) scoring positions; 1158 affecting team (40) scoring positions.
26-Oct: Diwali/Deepavali: 1559 tasks outstanding; 941 affecting individual (193) scoring positions; 475 affecting team (31) scoring positions.
27-Oct: Diwali/Deepavali: 1153 tasks outstanding; 640 affecting individual (163) scoring positions; 152 affecting team (20) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
Maybe i missed this, I'm new here but why is the year 2017 not selectable in the 'current overall standings' ? | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
Maybe i missed this, I'm new here but why is the year 2017 not selectable in the 'current overall standings' ?
The person who was in charge of that is no longer available, and that list was done on his private resources. We haven't replaced it yet, so 2016 is the latest year with cumulative totals.
____________
My lucky number is 75898524288+1 | |
|
RogerVolunteer developer
Volunteer tester
Send message
Joined: 27 Nov 11
Posts: 1138
ID: 120786
Credit: 268,668,824
RAC: 0
|
Maybe i missed this, I'm new here but why is the year 2017 not selectable in the 'current overall standings' ?
The person who was in charge of that is no longer available, and that list was done on his private resources. We haven't replaced it yet, so 2016 is the latest year with cumulative totals.
I had a go at producing the individual cumulative totals for 2017. Let me know if works and any issues:
https://docs.google.com/spreadsheets/d/1jygHG0CFLPYhPJ6kqX_ZanzK-_8bRuyZR9ePEyricRs | |
|
|
|
|
First of all thanks for taking charge. In the points columns, instead of the actual credit can you show the challenge position points earned and total of those show the overall position?
The reason I ask is that if someone gets third in one short challenge but first in a long challenge their overall position could go up and might not if you have it based on the actual credit.
Again, thanks Rick | |
|
|
|
|
My thanks as well.
There is a freeze pane option in Excel which allows for one or more rows/columns to be frozen while one scrolls across the spreadsheet. For example, if we freeze row 1 with all of the headings, one can scroll down the spreadsheet as far as they like and without losing the row headings so as to be able to read the meaning of each cell.
If this can be implemented, it would be very nice. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
Cleanup Status:
22-Oct: Diwali/Deepavali: 7413 tasks outstanding; 6342 affecting individual (291) scoring positions; 4311 affecting team (65) scoring positions.
23-Oct: Diwali/Deepavali: 5801 tasks outstanding; 4823 affecting individual (286) scoring positions; 3240 affecting team (58) scoring positions.
24-Oct: Diwali/Deepavali: 3510 tasks outstanding; 2763 affecting individual (263) scoring positions; 1840 affecting team (45) scoring positions.
25-Oct: Diwali/Deepavali: 2551 tasks outstanding; 1668 affecting individual (240) scoring positions; 1158 affecting team (40) scoring positions.
26-Oct: Diwali/Deepavali: 1559 tasks outstanding; 941 affecting individual (193) scoring positions; 475 affecting team (31) scoring positions.
27-Oct: Diwali/Deepavali: 1153 tasks outstanding; 640 affecting individual (163) scoring positions; 152 affecting team (20) scoring positions.
28-Oct: Diwali/Deepavali: 824 tasks outstanding; 427 affecting individual (130) scoring positions; 110 affecting team (15) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
RogerVolunteer developer
Volunteer tester
Send message
Joined: 27 Nov 11
Posts: 1138
ID: 120786
Credit: 268,668,824
RAC: 0
|
First of all thanks for taking charge. In the points columns, instead of the actual credit can you show the challenge position points earned and total of those show the overall position?
The reason I ask is that if someone gets third in one short challenge but first in a long challenge their overall position could go up and might not if you have it based on the actual credit.
Again, thanks Rick
Yes, of course.
Is a spread sheet, so is easy enough to do.
Will have to wait till the morning though. Is 10:40pm here.
Cheers,
Roger | |
|
RogerVolunteer developer
Volunteer tester
Send message
Joined: 27 Nov 11
Posts: 1138
ID: 120786
Credit: 268,668,824
RAC: 0
|
|
Try this one:
https://docs.google.com/spreadsheets/d/1lyWS-I9lo02TlKAmvpPA5aQR8AscRPAOBLZlEk_nXmc
First row frozen so can scroll down while still being able to see the headings.
Position Rank is by Challenge Points. If zero Points then Position Rank is sorted by Challenge Score. | |
|
|
|
|
Nice work!
____________
 | |
|
|
|
Try this one:
https://docs.google.com/spreadsheets/d/1lyWS-I9lo02TlKAmvpPA5aQR8AscRPAOBLZlEk_nXmc
First row frozen so can scroll down while still being able to see the headings.
Position Rank is by Challenge Points. If zero Points then Position Rank is sorted by Challenge Score.
Well done ! | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
Cleanup Status:
22-Oct: Diwali/Deepavali: 7413 tasks outstanding; 6342 affecting individual (291) scoring positions; 4311 affecting team (65) scoring positions.
23-Oct: Diwali/Deepavali: 5801 tasks outstanding; 4823 affecting individual (286) scoring positions; 3240 affecting team (58) scoring positions.
24-Oct: Diwali/Deepavali: 3510 tasks outstanding; 2763 affecting individual (263) scoring positions; 1840 affecting team (45) scoring positions.
25-Oct: Diwali/Deepavali: 2551 tasks outstanding; 1668 affecting individual (240) scoring positions; 1158 affecting team (40) scoring positions.
26-Oct: Diwali/Deepavali: 1559 tasks outstanding; 941 affecting individual (193) scoring positions; 475 affecting team (31) scoring positions.
27-Oct: Diwali/Deepavali: 1153 tasks outstanding; 640 affecting individual (163) scoring positions; 152 affecting team (20) scoring positions.
28-Oct: Diwali/Deepavali: 824 tasks outstanding; 427 affecting individual (130) scoring positions; 110 affecting team (15) scoring positions.
29-Oct: Diwali/Deepavali: 554 tasks outstanding; 253 affecting individual (104) scoring positions; 66 affecting team (11) scoring positions.
30-Oct: Diwali/Deepavali: 332 tasks outstanding; 143 affecting individual (76) scoring positions; 38 affecting team (9) scoring positions.
31-Oct: Diwali/Deepavali: 176 tasks outstanding; 69 affecting individual (49) scoring positions; 15 affecting team (3) scoring positions.
1-Nov: Diwali/Deepavali: 122 tasks outstanding; 45 affecting individual (35) scoring positions; 11 affecting team (3) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
|
|
Try this one:
https://docs.google.com/spreadsheets/d/1lyWS-I9lo02TlKAmvpPA5aQR8AscRPAOBLZlEk_nXmc
First row frozen so can scroll down while still being able to see the headings.
Position Rank is by Challenge Points. If zero Points then Position Rank is sorted by Challenge Score.
Great job, thank you!!
____________
Proud member of Team Aggie the Pew
"Wir müssen wissen. Wir werden wissen."
"We must know, we shall know."
- David Hilbert, 1930 | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
Cleanup Status:
22-Oct: Diwali/Deepavali: 7413 tasks outstanding; 6342 affecting individual (291) scoring positions; 4311 affecting team (65) scoring positions.
23-Oct: Diwali/Deepavali: 5801 tasks outstanding; 4823 affecting individual (286) scoring positions; 3240 affecting team (58) scoring positions.
24-Oct: Diwali/Deepavali: 3510 tasks outstanding; 2763 affecting individual (263) scoring positions; 1840 affecting team (45) scoring positions.
25-Oct: Diwali/Deepavali: 2551 tasks outstanding; 1668 affecting individual (240) scoring positions; 1158 affecting team (40) scoring positions.
26-Oct: Diwali/Deepavali: 1559 tasks outstanding; 941 affecting individual (193) scoring positions; 475 affecting team (31) scoring positions.
27-Oct: Diwali/Deepavali: 1153 tasks outstanding; 640 affecting individual (163) scoring positions; 152 affecting team (20) scoring positions.
28-Oct: Diwali/Deepavali: 824 tasks outstanding; 427 affecting individual (130) scoring positions; 110 affecting team (15) scoring positions.
29-Oct: Diwali/Deepavali: 554 tasks outstanding; 253 affecting individual (104) scoring positions; 66 affecting team (11) scoring positions.
30-Oct: Diwali/Deepavali: 332 tasks outstanding; 143 affecting individual (76) scoring positions; 38 affecting team (9) scoring positions.
31-Oct: Diwali/Deepavali: 176 tasks outstanding; 69 affecting individual (49) scoring positions; 15 affecting team (3) scoring positions.
1-Nov: Diwali/Deepavali: 122 tasks outstanding; 45 affecting individual (35) scoring positions; 11 affecting team (3) scoring positions.
2-Nov: Diwali/Deepavali: 82 tasks outstanding; 31 affecting individual (25) scoring positions; 8 affecting team (3) scoring positions.
3-Nov: Diwali/Deepavali: 71 tasks outstanding; 29 affecting individual (23) scoring positions; 8 affecting team (3) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
RogerVolunteer developer
Volunteer tester
Send message
Joined: 27 Nov 11
Posts: 1138
ID: 120786
Credit: 268,668,824
RAC: 0
|
|
Now with Teams tab:
https://docs.google.com/spreadsheets/d/1woEJoCZxjVNbxMF6i_IbuN2Mrj5cyR3NG0Igf4d1waM | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,800,865
RAC: 149,809
|
|
Cleanup Status:
22-Oct: Diwali/Deepavali: 7413 tasks outstanding; 6342 affecting individual (291) scoring positions; 4311 affecting team (65) scoring positions.
23-Oct: Diwali/Deepavali: 5801 tasks outstanding; 4823 affecting individual (286) scoring positions; 3240 affecting team (58) scoring positions.
24-Oct: Diwali/Deepavali: 3510 tasks outstanding; 2763 affecting individual (263) scoring positions; 1840 affecting team (45) scoring positions.
25-Oct: Diwali/Deepavali: 2551 tasks outstanding; 1668 affecting individual (240) scoring positions; 1158 affecting team (40) scoring positions.
26-Oct: Diwali/Deepavali: 1559 tasks outstanding; 941 affecting individual (193) scoring positions; 475 affecting team (31) scoring positions.
27-Oct: Diwali/Deepavali: 1153 tasks outstanding; 640 affecting individual (163) scoring positions; 152 affecting team (20) scoring positions.
28-Oct: Diwali/Deepavali: 824 tasks outstanding; 427 affecting individual (130) scoring positions; 110 affecting team (15) scoring positions.
29-Oct: Diwali/Deepavali: 554 tasks outstanding; 253 affecting individual (104) scoring positions; 66 affecting team (11) scoring positions.
30-Oct: Diwali/Deepavali: 332 tasks outstanding; 143 affecting individual (76) scoring positions; 38 affecting team (9) scoring positions.
31-Oct: Diwali/Deepavali: 176 tasks outstanding; 69 affecting individual (49) scoring positions; 15 affecting team (3) scoring positions.
1-Nov: Diwali/Deepavali: 122 tasks outstanding; 45 affecting individual (35) scoring positions; 11 affecting team (3) scoring positions.
2-Nov: Diwali/Deepavali: 82 tasks outstanding; 31 affecting individual (25) scoring positions; 8 affecting team (3) scoring positions.
3-Nov: Diwali/Deepavali: 71 tasks outstanding; 29 affecting individual (23) scoring positions; 8 affecting team (3) scoring positions.
4-Nov: Diwali/Deepavali: 48 tasks outstanding; 20 affecting individual (17) scoring positions; 6 affecting team (3) scoring positions.
5-Nov: Diwali/Deepavali: 33 tasks outstanding; 16 affecting individual (15) scoring positions; 5 affecting team (3) scoring positions.
6-Nov: Diwali/Deepavali: 27 tasks outstanding; 12 affecting individual (12) scoring positions; 4 affecting team (2) scoring positions.
7-Nov: Diwali/Deepavali: 17 tasks outstanding; 7 affecting individual (7) scoring positions; 3 affecting team (1) scoring positions.
8-Nov: Diwali/Deepavali: 12 tasks outstanding; 5 affecting individual (5) scoring positions; 0 affecting team (0) scoring positions.
9-Nov: Diwali/Deepavali: 8 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
RogerVolunteer developer
Volunteer tester
Send message
Joined: 27 Nov 11
Posts: 1138
ID: 120786
Credit: 268,668,824
RAC: 0
|
|
The results are final!
Top 3 individuals:
1: zunewantan
2: Scott Brown
3: DeleteNull
Top 3 teams:
1: Aggie The Pew
2: SETI.Germany
3: Czech National Team
Congratulations to the winners, and well done to everyone who participated.
See you at the up-coming Generalized Fermat Prime Search challenge!
____________
| |
|
Message boards :
Number crunching :
Diwali/Deepavali Challenge |
