Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Number crunching :
World Space Week Challenge
Author |
Message |
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 336 ID: 764476 Credit: 46,281,510 RAC: 0
                 
|
Welcome to the World Space Week Challenge
The sixth challenge of the 2022 Series will be a 7-day challenge in celebration of the annual United Nations education event, World Space Week. The challenge will be offered on the TRP-LLR application, beginning 04 October 12:00 UTC and ending 11 October 12:00 UTC.
From https://www.worldspaceweek.org:
World Space Week is an international celebration of science and technology, and their contribution to the betterment of the human condition. The United Nations General Assembly declared in 1999 that World Space Week will be held each year from October 4-10. These dates commemorate two events:
October 4, 1957: Launch of the first human-made Earth satellite, Sputnik 1, thus opening the way for space exploration
October 10, 1967: The signing of the Treaty on Principles Governing the Activites of States in the Exploration and Peaceful Uses of Outer Space, including the Moon and Other Celestial Bodies.
------------------------------------------------------------------------------------------------------
To participate in the Challenge, please select only the The Riesel Problem (LLR) 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. (TRP-LLR tasks on one CPU core take about 28 hours on average.)
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 ${c.start} and received BEFORE ${c.end} 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 a 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 April 24, 2021, there remain 44 k's for which no primes have been found. They are as follows:
23669, 31859, 38473, 46663, 67117, 74699, 81041, 93839, 97139, 107347, 121889, 129007, 143047, 161669, 206231, 215443, 226153, 234343, 245561, 250027, 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.
To participate in effort, please select The Riesel Problem (LLR) project in your PrimeGrid preferences section.
Additional Information
The Riesel problem is to k*2^n-1 as the Sierpinski problem is to k*2^n+1. There is no equivalent to the 'prime' Sierpinski problem since k=509203, the conjectured smallest Riesel number, is prime.
Primes found at PrimeGrid
191249*2^3417696-1 by Jonathan Pritchard on 21 Nov 2010. Official Announcement
428639*2^3506452-1 by Brett Melvold on 14 Jan 2011. Official Announcement
65531*2^3629342-1 by Adrian Schori on 5 Apr 2011. Official Announcement
123547*2^3804809-1 by Jakub Łuszczek on 8 May 2011. Official Announcement
415267*2^3771929-1 by Alexey Tarasov on 8 May 2011. Official Announcement
141941*2^4299438-1 by Scott Brown on 26 May 2011. Official Announcement
353159*2^4331116-1 by Jaakko Reinman on 31 May 2011. Official Announcement
162941*2^993718-1 by Dmitry Domanov on 02 February 2012. Official Announcement
252191*2^5497878-1 by Jan Haller on 23 June 2012. Official Announcement.
398023*2^6418059-1 by Vladimir Volynsky on 5 October 2013. Official Announcement.
304207*2^6643565-1 by Randy Ready on 10 October 2013. Official Announcement.
40597*2^6808509-1 by Frank Meador on 25 December 2013. Official Announcement.
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.
273809*2^8932416-1 by Wolfgang Schwieger on 13 December 2017. Official Announcement.
146561*2^11280802-1 by Pavel Atnashev on 17 November 2020. Official Announcement.
9221*2^11392194-1 by Barry Schnur on 7 Feb 2021. Official Announcement
Primes found outside PrimeGrid
2293*2^12918431-1 by Ryan Propper on February 13 2021.
192971*2^14773498-1 by Ryan Propper on March 7 2021.
206039*2^13104952-1 by Ryan Propper on April 26 2021.
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:
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.
| |
|
|
The race is on!
____________
Greetings, Jens
1461*2^3373383+1 | |
|
Dave  Send message
Joined: 13 Feb 12 Posts: 3148 ID: 130544 Credit: 2,213,476,432 RAC: 266,006
                      
|
Good luck all. | |
|
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 336 ID: 764476 Credit: 46,281,510 RAC: 0
                 
|
Challenge: World Space Week
App: 15 (TRP-LLR)
Fast DC tasks are NOT included.
(As of 2022-10-07 00:19:54 UTC)
35602 tasks have been sent out. [CPU/GPU/anonymous_platform: 35602 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
2136 (6%) were aborted. [2136 (6%) / 0 (0%) / 0 (0%)]
78 (0%) came back with some kind of an error. [78 (0%) / 0 (0%) / 0 (0%)]
19246 (54%) have returned a successful result. [19246 (54%) / 0 (0%) / 0 (0%)]
14142 (40%) are still in progress. [14142 (40%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
2904 (15%) are pending validation. [2904 (15%) / 0 (0%) / 0 (0%)]
16342 (85%) have been successfully validated. [16342 (85%) / 0 (0%) / 0 (0%)]
1 (0%) were invalid. [1 (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=13417280. The leading edge was at n=13122603 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.25% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 336 ID: 764476 Credit: 46,281,510 RAC: 0
                 
|
Challenge: World Space Week
App: 15 (TRP-LLR)
Fast DC tasks are NOT included.
(As of 2022-10-07 20:28:13 UTC)
44470 tasks have been sent out. [CPU/GPU/anonymous_platform: 44470 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
2452 (6%) were aborted. [2452 (6%) / 0 (0%) / 0 (0%)]
78 (0%) came back with some kind of an error. [78 (0%) / 0 (0%) / 0 (0%)]
27369 (62%) have returned a successful result. [27369 (62%) / 0 (0%) / 0 (0%)]
14571 (33%) are still in progress. [14571 (33%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
3011 (11%) are pending validation. [3011 (11%) / 0 (0%) / 0 (0%)]
24358 (89%) have been successfully validated. [24358 (89%) / 0 (0%) / 0 (0%)]
2 (0%) were invalid. [2 (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=13493520. The leading edge was at n=13122603 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.83% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
|
Just a question please regarding TRP results.
How does this user have no main tasks validated? Only proof tasks?
http://www.primegrid.com/hosts_user.php?userid=1194437
That would seem like a better use of my CPU time. What am I missing?
I see other crunchers with similar results to me but I've not seen only proof tasks being done before.
____________
Слава Україні! | |
|
|
Just a question please regarding TRP results.
How does this user have no main tasks validated? Only proof tasks?
http://www.primegrid.com/hosts_user.php?userid=1194437
That would seem like a better use of my CPU time. What am I missing?
I see other crunchers with similar results to me but I've not seen only proof tasks being done before.
TRP task list for the first computer in user's computer list:
http://www.primegrid.com/results.php?hostid=1009814&offset=0&show_names=0&state=0&appid=15
TRP task list for the second computer in user's computer list:
http://www.primegrid.com/results.php?hostid=1143132&offset=0&show_names=0&state=0&appid=15
I see many main tasks validated.
What seemed interesting to me is that I saw no proof task was crunched in those two computers.
____________
"Accidit in puncto, quod non contingit in anno."
Something that does not occur in a year may, perchance, happen in a moment. | |
|
|
Just a question please regarding TRP results.
How does this user have no main tasks validated? Only proof tasks?
http://www.primegrid.com/hosts_user.php?userid=1194437
That would seem like a better use of my CPU time. What am I missing?
I see other crunchers with similar results to me but I've not seen only proof tasks being done before.
TRP task list for the first computer in user's computer list:
http://www.primegrid.com/results.php?hostid=1009814&offset=0&show_names=0&state=0&appid=15
TRP task list for the second computer in user's computer list:
http://www.primegrid.com/results.php?hostid=1143132&offset=0&show_names=0&state=0&appid=15
I see many main tasks validated.
What seemed interesting to me is that I saw no proof task was crunched in those two computers.
If you look at the download time, you will see a lot of tasks downloaded at once, when proof tasks weren't probably available (yet). Just a guess though.
____________
676754^262144+1 is prime | |
|
|
Just a question please regarding TRP results.
How does this user have no main tasks validated? Only proof tasks?
http://www.primegrid.com/hosts_user.php?userid=1194437
That would seem like a better use of my CPU time. What am I missing?
I see other crunchers with similar results to me but I've not seen only proof tasks being done before.
They manually and selectively abort one type of tasks.
For the first computer there, if you look at:
https://www.primegrid.com/results.php?hostid=1143132&show_names=1&state=4&appid=15 (valid TRP)
https://www.primegrid.com/results.php?hostid=1143132&show_names=1&state=5&appid=15 (aborted TRP)
you see comparable numbers of tasks.
You can download a big number of tasks after the challenge has started, select all those that are main tasks, and abort them.
(I am not sure if the example is so good, after all, but it is possible to selectively abort. But why would you? Is the credit awarded to Main tasks and Proof tasks not fair?)
/JeppeSN | |
|
|
But why would you? Is the credit awarded to Main tasks and Proof tasks not fair?
No, because the only credit sought is a primary number.
The other is only a benchmark to see the work done to get there. | |
|
|
But why would you? Is the credit awarded to Main tasks and Proof tasks not fair?
No, because the only credit sought is a primary number.
The other is only a benchmark to see the work done to get there.
It is true that only a Main task can make you "finder" of a prime number (and give you prime "score" as a finder). But in terms of the BOINC credit and the challenge points, both types of tasks are good. /JeppeSN | |
|
|
Just a question please regarding TRP results.
How does this user have no main tasks validated? Only proof tasks?
http://www.primegrid.com/hosts_user.php?userid=1194437
That would seem like a better use of my CPU time. What am I missing?
I see other crunchers with similar results to me but I've not seen only proof tasks being done before.
He Aborted them from what I see.
And needs to be banned IMO. | |
|
|
I don't think anyone should be banned.
There are also crunchers who would like to do only proof tasks.
____________
Greetings, Jens
1461*2^3373383+1 | |
|
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 336 ID: 764476 Credit: 46,281,510 RAC: 0
                 
|
Challenge: World Space Week
App: 15 (TRP-LLR)
Fast DC tasks are NOT included.
(As of 2022-10-10 07:14:10 UTC)
76962 tasks have been sent out. [CPU/GPU/anonymous_platform: 76962 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
6081 (8%) were aborted. [6081 (8%) / 0 (0%) / 0 (0%)]
352 (0%) came back with some kind of an error. [352 (0%) / 0 (0%) / 0 (0%)]
51875 (67%) have returned a successful result. [51875 (67%) / 0 (0%) / 0 (0%)]
18654 (24%) are still in progress. [18654 (24%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
3292 (6%) are pending validation. [3292 (6%) / 0 (0%) / 0 (0%)]
48583 (94%) have been successfully validated. [48583 (94%) / 0 (0%) / 0 (0%)]
2 (0%) were invalid. [2 (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=13732540. The leading edge was at n=13122603 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 4.65% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
mikey Send message
Joined: 17 Mar 09 Posts: 1591 ID: 37043 Credit: 717,037,960 RAC: 550,555
                     
|
I don't think anyone should be banned.
There are also crunchers who would like to do only proof tasks.
+1 | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 13892 ID: 53948 Credit: 384,256,683 RAC: 129,235
                              
|
I don't think anyone should be banned.
There are also crunchers who would like to do only proof tasks.
You need to try much harder than that if you want to get banned. There are some things that could get you banned, but this doesn’t even come close. We didn’t even ban the people we caught cheating many years ago. (We did something worse to them: we took away their credit.)
____________
My lucky number is 75898524288+1 | |
|
|
I don't think anyone should be banned.
There are also crunchers who would like to do only proof tasks.
Then we all should only have to run proof tasks to find that Prime.
I would like to only run proof tasks but I am not going to cheat the Challenge Series.
Maybe they could change it to where you also must run the Checker Task on any Prime that they have Found.
But if you abort them all then you would never check it for your own Prime.
But the way of the world is to cheat your way to the end.
This is Great "(We did something worse to them: we took away their credit.)" | |
|
|
Probably i see mutual misunderstanding of some terms.
Main task (long) performs the primality test (LLR).
Proof task (short) makes the check of main task authenticity via GEC-VDF algorithm, i.e. it try to prove, that the user REALLY did calculation of main task from beginning to the end and didn't fake result.
Only main task gives the "ownership of prime" (if the prime was found)
There are a lot of users with powerful computers who would like to get long main tasks only. There is no "criminal" or "cheating" to abort short proof tasks.
On the other hand there are a lot of users with ancient slow computers who would like to get short proof tasks only. And again, there is no "criminal" or "cheating" to abort long main tasks, especially if you see that the long task cannot fit the deadline.
All tasks aborted will immediately reassigned to other users and not abandoned. | |
|
|
Probably i see mutual misunderstanding of some terms.
Main task (long) performs the primality test (LLR).
Proof task (short) makes the check of main task authenticity via GEC-VDF algorithm, i.e. it try to prove, that the user REALLY did calculation of main task from beginning to the end and didn't fake result.
Only main task gives the "ownership of prime" (if the prime was found)
There are a lot of users with powerful computers who would like to get long main tasks only. There is no "criminal" or "cheating" to abort short proof tasks.
On the other hand there are a lot of users with ancient slow computers who would like to get short proof tasks only. And again, there is no "criminal" or "cheating" to abort long main tasks, especially if you see that the long task cannot fit the deadline.
All tasks aborted will immediately reassigned to other users and not abandoned.
I see, I show Completed and validated (1st) [Proof task] | |
|
|
It's a little annoying because I read the opposite and I must always correct on reading!
État Temps de fonctionnement (sec)
Terminé et validé [Main task] 156.07
Terminé et validé (1st) [Proof task] 21,680.42
____________
| |
|
|
I see, I show Completed and validated (1st) [Proof task]
[Proof task] is the link to the proof task from the main task.
[Main task] is the link to the main task from the proof one.
| |
|
|
I see, I show Completed and validated (1st) [Proof task]
[Proof task] is the link to the proof task from the main task.
[Main task] is the link to the main task from the proof one.
Yes I know Main Tasks if a Prime is Found it is the winner and the Proof Task is the Double Checker, Thank you | |
|
|
Yes I know Main Tasks if a Prime is Found it is the winner and the Proof Task is the Double Checker, Thank you
However, no double checker is recorded officially for LLR2 primes. This only happens for "race" subprojects (non-LLR2) where both users do the same amount of work (and one is unlucky to finish 2nd). /JeppeSN | |
|
Dave  Send message
Joined: 13 Feb 12 Posts: 3148 ID: 130544 Credit: 2,213,476,432 RAC: 266,006
                      
|
Aannyywayy.........
Excellent challenge all! Enjoyed that with a few close calls & mini battles in the mix. | |
|
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 336 ID: 764476 Credit: 46,281,510 RAC: 0
                 
|
And we're done! Here are the stats:
Challenge: World Space Week
App: 15 (TRP-LLR)
Fast DC tasks are NOT included.
(As of 2022-10-11 20:26:57 UTC)
91632 tasks have been sent out. [CPU/GPU/anonymous_platform: 91632 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
14774 (16%) were aborted. [14774 (16%) / 0 (0%) / 0 (0%)]
691 (1%) came back with some kind of an error. [691 (1%) / 0 (0%) / 0 (0%)]
63458 (69%) have returned a successful result. [63458 (69%) / 0 (0%) / 0 (0%)]
10529 (11%) are still in progress. [10529 (11%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
2746 (4%) are pending validation. [2746 (4%) / 0 (0%) / 0 (0%)]
60712 (96%) have been successfully validated. [60712 (96%) / 0 (0%) / 0 (0%)]
2 (0%) were invalid. [2 (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=13783970. The leading edge was at n=13122603 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.04% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 336 ID: 764476 Credit: 46,281,510 RAC: 0
                 
|
Cleanup Status:
Oct 12: 1689 tasks outstanding; 769 affecting individual (164) scoring positions; 292 affecting team (30) scoring positions.
Oct 13: 933 tasks outstanding; 328 affecting individual (112) scoring positions; 128 affecting team (19) scoring positions.
Oct 18: 76 tasks outstanding; 9 affecting individual (8) scoring positions; 0 affecting team (0) scoring positions.
Oct 19: 70 tasks outstanding; 9 affecting individual (8) scoring positions; 0 affecting team (0) scoring positions.
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 336 ID: 764476 Credit: 46,281,510 RAC: 0
                 
|
The results are final!
During the 7 day challenge, we completed 125104 tasks (including doublechecks).
130 teams and 566 individuals participated in the challenge.
Top Three Individuals:
1. [TA]Skillz with 11,452 tasks completed
2. tng with 6,643 tasks completed
3. vaughan with 5,478 tasks completed
Top Three Teams:
1. TeAm AnandTech with 27,298 tasks completed
2. Antarctic Crunchers with 17,242 tasks completed
3. Czech National Team with 10,923 tasks completed
Great work everyone, see you in the next challenge: the Prime Meridian Challenge starts in 6 days as of posting!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
mikey Send message
Joined: 17 Mar 09 Posts: 1591 ID: 37043 Credit: 717,037,960 RAC: 550,555
                     
|
I don't think anyone should be banned.
There are also crunchers who would like to do only proof tasks.
Then we all should only have to run proof tasks to find that Prime.
I would like to only run proof tasks but I am not going to cheat the Challenge Series.
Maybe they could change it to where you also must run the Checker Task on any Prime that they have Found.
But if you abort them all then you would never check it for your own Prime.
But the way of the world is to cheat your way to the end.
This is Great "(We did something worse to them: we took away their credit.)"
I don't think they send out the Proof Task to the same person who does the Main Task for data integrity reasons, ie someone doing their own checking could lead to massive cheating | |
|
mikey Send message
Joined: 17 Mar 09 Posts: 1591 ID: 37043 Credit: 717,037,960 RAC: 550,555
                     
|
Probably i see mutual misunderstanding of some terms.
Main task (long) performs the primality test (LLR).
Proof task (short) makes the check of main task authenticity via GEC-VDF algorithm, i.e. it try to prove, that the user REALLY did calculation of main task from beginning to the end and didn't fake result.
Only main task gives the "ownership of prime" (if the prime was found)
There are a lot of users with powerful computers who would like to get long main tasks only. There is no "criminal" or "cheating" to abort short proof tasks.
On the other hand there are a lot of users with ancient slow computers who would like to get short proof tasks only. And again, there is no "criminal" or "cheating" to abort long main tasks, especially if you see that the long task cannot fit the deadline.
All tasks aborted will immediately reassigned to other users and not abandoned.
Maybe the Staff could start bouncing around the idea of letting users choose which kind of task they get, Proof or Main, to optimize their pc's capabilities instead of having people abort the unwanted tasks. Of course this could lead to a pc not getting any tasks if ie not enough people are doing the Main tasks so no Proof tasks are available, but that's a User problem not a Project problem. | |
|
mikey Send message
Joined: 17 Mar 09 Posts: 1591 ID: 37043 Credit: 717,037,960 RAC: 550,555
                     
|
The results are final!
During the 7 day challenge, we completed 125104 tasks (including doublechecks).
130 teams and 566 individuals participated in the challenge.
Top Three Individuals:
1. [TA]Skillz with 11,452 tasks completed
2. tng with 6,643 tasks completed
3. vaughan with 5,478 tasks completed
Top Three Teams:
1. TeAm AnandTech with 27,298 tasks completed
2. Antarctic Crunchers with 17,242 tasks completed
3. Czech National Team with 10,923 tasks completed
Great work everyone, see you in the next challenge: the Prime Meridian Challenge starts in 6 days as of posting!
Michael you do a very good job of managing all these challenges and posting all the relevant data Thank You!!!! | |
|
Dave  Send message
Joined: 13 Feb 12 Posts: 3148 ID: 130544 Credit: 2,213,476,432 RAC: 266,006
                      
|
Maybe the Staff could start bouncing around the idea of letting users choose which kind of task they get, Proof or Main .
No.
| |
|
Dave  Send message
Joined: 13 Feb 12 Posts: 3148 ID: 130544 Credit: 2,213,476,432 RAC: 266,006
                      
|
Michael you do a very good job of managing all these challenges and posting all the relevant data Thank You!!!!
I agree with this. | |
|
|
I don't think they send out the Proof Task to the same person who does the Main Task for data integrity reasons, ie someone doing their own checking could lead to massive cheating
For LLR2, main tasks reside in a different work unit than their associated proof tasks. A proof task can be sent to the same user that did the corresponding main task. It can even be the same computer. The scheme means it should be safe (the user does not know the secret "key" the server has).
For traditional crunching (non-LLR2) both/all tasks in the test of one candidate number are of the same kind, and if a two were sent to the same person, he could just make up a residue and send it in for both tasks, thereby cheating.
/JeppeSN | |
|
mikey Send message
Joined: 17 Mar 09 Posts: 1591 ID: 37043 Credit: 717,037,960 RAC: 550,555
                     
|
I don't think they send out the Proof Task to the same person who does the Main Task for data integrity reasons, ie someone doing their own checking could lead to massive cheating
For LLR2, main tasks reside in a different work unit than their associated proof tasks. A proof task can be sent to the same user that did the corresponding main task. It can even be the same computer. The scheme means it should be safe (the user does not know the secret "key" the server has).
For traditional crunching (non-LLR2) both/all tasks in the test of one candidate number are of the same kind, and if a two were sent to the same person, he could just make up a residue and send it in for both tasks, thereby cheating.
/JeppeSN
That's cool thank you! | |
|
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 336 ID: 764476 Credit: 46,281,510 RAC: 0
                 
|
Michael you do a very good job of managing all these challenges and posting all the relevant data Thank You!!!!
<3
love your profile picture btw lol
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
Post to thread
Message boards :
Number crunching :
World Space Week Challenge |