Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Number crunching :
Magellan 500th Anniversary Challenge
| Author |
Message |
|---|
 Michael Gutierrez Volunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
                 
|
|
Welcome to Magellan's 500th Anniversary Challenge!
The eighth challenge of the 2020 Series will be a 10-day challenge commemorating the (approximate) 500th Anniversary of the extraordinary expedition of Portuguese explorer Ferdinand Magellan. The challenge will be offered on the CUL-LLR and WOO-LLR subprojects, beginning 18 November 18:00 UTC and ending 28 November 18:00 UTC.
FIVE HUNDRED YEARS ago, Ferdinand Magellan (3 February 1480 – 27 April 1521) began a historic journey to circumnavigate the globe. Simple, right? Not really— the explorer and his voyage are a study in contradiction. Magellan was Portuguese, but sailed on behalf of Spain. He was a formidable captain, but his crew hated him. His expedition was the first to sail around the world, but he didn’t end up circling the globe himself. His name wasn’t even Magellan.
Nonetheless, it’s clear that Ferdinand Magellan’s 1519 expedition changed the world forever. His journey was “the greatest sea voyage ever undertaken, and the most significant,” says historian Laurence Bergreen, author of Over the Edge of the World: Magellan’s Terrifying Circumnavigation of the Globe. “That’s not hyperbole.”
Brutal, bellicose, and brave, Magellan turned a commercial voyage into a hair-raising showdown with a wide world few Europeans could imagine. At the beginning of his journey, his contemporaries suspected it was impossible to sail around the entire globe—and feared that everything from sea monsters to killer fogs awaited anyone foolhardy enough to try. “It sounded suicidal to do this,” says Bergreen.
For more, check out this fantastic biography: https://www.nationalgeographic.com/culture/2019/09/magellan-first-sail-around-world-think-again/
To participate in the Challenge, please select only the Cullen Prime Search LLR (CUL) and/or Woodall Prime Search LLR (WOO) projects 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.
ATTENTION: The primality program LLR is CPU intensive; so, it is vital to have a stable system with good cooling. It does not tolerate "even the slightest of errors." Please see this post for more details on how you can "stress test" your computer. Tasks on one CPU core will take about 3 days on fast/newer computers and 1 week+ 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. :)
TL;DR: Please, please, please make sure your machines are up to the task.
Multi-threading is supported and IS recommended.
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 18 November 2020 18:00 UTC and received BEFORE 28 November 2020 18:00 UTC will be considered for credit. We will be using the same scoring method as we currently use for BOINC credits. Please note that while regular credit is not awarded until a task is validated, challenge points are awarded immediately. However, if the task 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 Cullen Prime Search
A Cullen number in the form of n*2^n+1. Fr. James Cullen first studied these numbers in 1905 because they have interesting divisibility properties. It is conjectured that there are infinitely many n values that will yield Cullen primes, though it has been shown that almost all are composite.
Further reading:
Cullen Number on Wikipedia
Cullen prime Prime Pages' Glossary entry
Top Twenty Cullen Primes in Chris Caldwell's Database
The following n values yield prime Cullen numbers (OEIS A005849) (ones found at Primegrid highlighted):
1, 141, 4713, 5795, 6611, 18496, 32292, 32469, 59656, 90825, 262419, 361275, 481899, 1354828, 6328548, and 6679881.
About Woodall Prime Search
Woodall Numbers (sometimes called Cullen numbers 'of the second kind') are positive integers of the form Wn = n*2^n-1, where n is also a positive integer greater than zero. Woodall numbers that are prime are called Woodall primes (or Cullen primes of the second kind).
The Woodall numbers Wn are primes for the following n:
2, 3, 6, 30, 75, 81, 115, 123, 249, 362, 384, 462, 512, 751, 822, 5312, 7755, 9531, 12379, 15822, 18885, 22971, 23005, 98726, 143018, 151023, 667071, 1195203, 1268979, 1467763, 2013992, 2367906, 3752948, and 17016602 and composite for all other n less than 17337441.
It is conjectured that there are infinitely many such primes. Currently, PrimeGrid is testing for Woodall primes in the n=17M - n=18M level (M=mega, 10^6). The last 4 Woodall primes found by PrimeGrid are:
2013992*2^2013992−1 (Lasse Mejling Andersen): official announcement | Prime Pages Entry
2367906*2^2367906−1 (Stephen Kohlman): official announcement | Prime Pages Entry
3752948*2^3752948−1 (Matthew J. Thompson): official announcement | Prime Pages Entry
17016602*2^17016602−1 (Diego Bertolotti): official announcement | Prime Pages Entry
For more information on Woodall numbers, please visit the following sites:
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.
| |
|
|
|
|
Most of the following information can be found in the paper by Keller and also on Caldwell's pages (the Glossary and the Top Twenty):
In 1905, in the Educational Times, Question 15897, James Cullen considered numbers of the form n*2^n + 1, and noted that none of the candidates with 1 < n < 100 were prime, with the possible exception of n=53. Does anyone have a copy of that contribution by Cullen? Soon, Allan J. C. Cunningham resolved the case n=53 by exhibiting the divisor 5519, and he stated that all numbers n*2^n + 1 for 2 ≤ n ≤ 200 were composite with the possible exception of n=141.
About 50 years later, electronic computers were being developed, and Raphael M. Robinson did a complete search to n=1000 and found that the only prime in this range (other than the trivial one for n=1) was for n=141. This was the first nontrivial Cullen prime. No other primes were noted until Wilfrid Keller in 1984 searched to n=30000 and discovered no less than four new Cullen primes.
Today, 16 Cullen primes are known, and the latest two have been found by PrimeGrid, both in 2009. When will we find the next one?
/JeppeSN | |
|
|
|
Most of the following information can be found in the paper by Keller and also on Caldwell's pages (the Glossary and the Top Twenty):
In 1905, in the Educational Times, Question 15897, James Cullen considered numbers of the form n*2^n + 1, and noted that none of the candidates with 1 < n < 100 were prime, with the possible exception of n=53. Does anyone have a copy of that contribution by Cullen? Soon, Allan J. C. Cunningham resolved the case n=53 by exhibiting the divisor 5519, and he stated that all numbers n*2^n + 1 for 2 ≤ n ≤ 200 were composite with the possible exception of n=141.
About 50 years later, electronic computers were being developed, and Raphael M. Robinson did a complete search to n=1000 and found that the only prime in this range (other than the trivial one for n=1) was for n=141. This was the first nontrivial Cullen prime. No other primes were noted until Wilfrid Keller in 1984 searched to n=30000 and discovered no less than four new Cullen primes.
Today, 16 Cullen primes are known, and the latest two have been found by PrimeGrid, both in 2009. When will we find the next one?
/JeppeSN
Scan of the original journal - Page 534, it's about 2/3 down the first column. No solution is provided, of course. While searching for this I found a separate journal that existed to answer "select" questions from the ET. Here is a link to the 1906 journal containing a solution by Allan Cunningham. The question is on bottom of page 48 in the reader (44 in journal), solution starts next page.
As an OT aside, I wish I knew this existed when I was a math teacher. There are some interesting problems in here I would have loved to pose to my students. I have a collection of late 19th and early 20th century textbooks that I would steal problems from to pry my students away from their calculators (because if those long gone students could do it in class, mine should do it faster!).
____________
Eating more cheese on Thursdays. | |
|
|
|
|
Thank you very much! The first link, Cullen's problem, I got to work (but you should not use quotation marks in the url tag, it is https://archive.org/details/educationaltimes58educ/page/534/mode/2up). Here it is an inlined PNG image:
The second link, I could not get to work. Maybe you need to be logged in, or in a particular geographical area?
/JeppeSN | |
|
|
|
|
Whoops, my bad. Too many HTML habits and not enough BBCode use.
Second link direct:
https://babel.hathitrust.org/cgi/pt?id=chi.57065015&view=1up&seq=49
Catalog page might offer a way in if that doesn't work?
https://catalog.hathitrust.org/Record/008857619
c.1 ser.2 v.10 1906 is the edition with the solutions.
____________
Eating more cheese on Thursdays. | |
|
|
|
|
Do I need to select only CUL-LLR and/or WOO-LLR and unselect PPS-SV for the 10-day duration to make sure I only participate in the challenge? | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 390,667,578
RAC: 110,130
                            
|
Do I need to select only CUL-LLR and/or WOO-LLR and unselect PPS-SV for the 10-day duration to make sure I only participate in the challenge?
PPS-Sieve on the CPU should be unchecked. If you want to run PPS-Sieve on your GPU, that's fine, although it might impact CPU performance, depending on your computer.
____________
My lucky number is 75898524288+1 | |
|
|
|
Do I need to select only CUL-LLR and/or WOO-LLR and unselect PPS-SV for the 10-day duration to make sure I only participate in the challenge?
PPS-Sieve on the CPU should be unchecked. If you want to run PPS-Sieve on your GPU, that's fine, although it might impact CPU performance, depending on your computer.
Thank you! | |
|
|
|
|
Make sure not to download many tasks before the challenge starts. (Abort them if unstarted, and consider setting "Maintain enough work for an additional _ days" to zero/blank.) Be aware that only tasks that are downloaded after the start time of the challenge and are returned before the end time, count towards the challenge statistics.
Also, be aware that one task will take many hours, even if you enable multithreading. So do not have a "cache" of several CUL/WOO tasks before the start. And get rid of your "pool" of tasks of other types (e.g. PPS-something) during the challenge.
If you care, there are different ways to micro-optimize this, including changing your preferences just after the start time of the challenge (18 November 18:00 UTC).
/JeppeSN | |
|
|
|
|
Hello Supporter
I dont need the Checklist for Spys and others
Cheklist Name :
Tasks returned in the last 24 hours
Please delete this.
Thanks
have a nice Day
____________
| |
|
Dave
Send message
Joined: 13 Feb 12
Posts: 3168
ID: 130544
Credit: 2,224,464,176
RAC: 228,967
                       
|
|
Just ignore it. Others use it. | |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
One day down, 9 to go. Here are the stats so far, separated by subproject:
App: 4 (CUL-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-19 19:07:18 UTC)
5626 tasks have been sent out. [CPU/GPU/anonymous_platform: 5626 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
690 (12%) were aborted. [690 (12%) / 0 (0%) / 0 (0%)]
174 (3%) came back with some kind of an error. [174 (3%) / 0 (0%) / 0 (0%)]
942 (17%) have returned a successful result. [942 (17%) / 0 (0%) / 0 (0%)]
3820 (68%) are still in progress. [3820 (68%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
942 (100%) are pending validation. [942 (100%) / 0 (0%) / 0 (0%)]
0 (0%) have been successfully validated. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=19068689. The leading edge was at n=18840665 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.21% as much as it had prior to the challenge!
App: 3 (WOO-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-19 19:07:19 UTC)
4692 tasks have been sent out. [CPU/GPU/anonymous_platform: 4692 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
516 (11%) were aborted. [516 (11%) / 0 (0%) / 0 (0%)]
318 (7%) came back with some kind of an error. [318 (7%) / 0 (0%) / 0 (0%)]
485 (10%) have returned a successful result. [485 (10%) / 0 (0%) / 0 (0%)]
3373 (72%) are still in progress. [3373 (72%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
485 (100%) are pending validation. [485 (100%) / 0 (0%) / 0 (0%)]
0 (0%) have been successfully validated. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=19652199. The leading edge was at n=19356295 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.53% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
|
|
|
Have a Nice Day
Understand
| |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
Day 2 of 10:
Challenge: Magellan 500th Anniversary
App: 4 (CUL-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-20 18:57:47 UTC)
8934 tasks have been sent out. [CPU/GPU/anonymous_platform: 8934 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
1540 (17%) were aborted. [1540 (17%) / 0 (0%) / 0 (0%)]
242 (3%) came back with some kind of an error. [242 (3%) / 0 (0%) / 0 (0%)]
2749 (31%) have returned a successful result. [2749 (31%) / 0 (0%) / 0 (0%)]
4403 (49%) are still in progress. [4403 (49%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
1378 (50%) are pending validation. [1378 (50%) / 0 (0%) / 0 (0%)]
1371 (50%) have been successfully validated. [1371 (50%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=19185382. The leading edge was at n=18840665 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.83% as much as it had prior to the challenge!
Challenge: Magellan 500th Anniversary
App: 3 (WOO-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-20 18:57:48 UTC)
6662 tasks have been sent out. [CPU/GPU/anonymous_platform: 6662 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
1222 (18%) were aborted. [1222 (18%) / 0 (0%) / 0 (0%)]
406 (6%) came back with some kind of an error. [406 (6%) / 0 (0%) / 0 (0%)]
1447 (22%) have returned a successful result. [1447 (22%) / 0 (0%) / 0 (0%)]
3587 (54%) are still in progress. [3587 (54%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
1447 (100%) are pending validation. [1447 (100%) / 0 (0%) / 0 (0%)]
0 (0%) have been successfully validated. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=19737949. The leading edge was at n=19356295 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.97% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
|
|
|
Is it possible to see which n value (in n*2^n -1,Woodall) a given task is currently associated with?
Thanks! | |
|
Ken_g6Volunteer developer
Send message
Joined: 4 Jul 06
Posts: 936
ID: 3110
Credit: 257,827,723
RAC: 74,089
                    
|
|
LLR2 generally seems to list the candidate being tested in stderr.txt. After returning a result, stderr.txt is shown when you click on the task link. | |
|
|
|
Is it possible to see which n value (in n*2^n -1,Woodall) a given task is currently associated with?
Thanks!
If the task is unfinished, you must access the computer which is currently doing the task, and find a special text file in a special BOINC folder and know how to interpret the numbers in it.
If the task has finished and the result been returned, you can see it on the task page if you read the stderr carefully. Example with Cullen (until link rots because task gets purged): resultid=1150987977 - the candidate is 19086288*2^19086288+1.
/JeppeSN | |
|
|
|
LLR2 generally seems to list the candidate being tested in stderr.txt. After returning a result, stderr.txt is shown when you click on the task link.
While the task is running, stderr.txt in the corresponding slot folder holds the number being tested.
For example (CUL):
BOINC PrimeGrid wrapper 2.01 (Aug 11 2020 22:09:56)
running ../../projects/www.primegrid.com/llr2_1.0.0_win64_200814.exe -v
LLR2 Program - Version 1.0.0, using Gwnum Library Version 29.8
running ../../projects/www.primegrid.com/llr2_1.0.0_win64_200814.exe -oGerbicz=1 -oProofName=proof -oProofCount=128 -oProductName=prod -oPietrzak=1 -oCachePoints=0 -pSavePoints -q19163285*2^19163285+1 -d -t4 -oDiskWriteTime=1
Starting Proth prime test of 19163285*2^19163285+1
Using zero-padded FMA3 FFT length 2016K, Pass1=448, Pass2=4608, clm=2, 4 threads, a = 3, L2 = 529*283, M = 149707
It seems (at least under Windows) that the number being tested appears in the command line used to launch the cruncher program.
So, for Windows, an easy way to know such number is to invoke task manager, go to the details tab and take a look at the command line (-qXXXXXXX).
(Note that the command line column in the details tab in task manager might not be visible by default.
If so, just right click on any column header, pick "Choose columns" and check command line)
But it seems the OP is using Darwin OS (http://www.primegrid.com/show_host_detail.php?hostid=1037563).
I don't anything about such OS :(
____________
"Accidit in puncto, quod non contingit in anno."
Something that does not occur in a year may, perchance, happen in a moment. | |
|
|
|
|
What is a fast DC task?
____________
Thanks,
Jim
 | |
|
|
|
|
Jim, It is the validation task that is significantly shorter thanks to LLR2 (hence "fast" Double Check) than the old method of running each full WU twice, see https://www.primegrid.com/forum_thread.php?id=9303&nowrap=true#143209 | |
|
BurVolunteer tester
Send message
Joined: 25 Feb 20
Posts: 515
ID: 1241833
Credit: 413,783,846
RAC: 37,243
      
|
|
Why are so many aborted? I can see some people aborting DC tasks, but those aren't counted here.
____________
1281979 * 2^485014 + 1 is prime ... no further hits up to: n = 5,700,000 | |
|
|
|
|
Not the right Way, I know.
in Future - I send ready Tasks back.
OK
I had beleve - Backtasks go back in the right Server and next users can upload the Tasks.
but this is not the right way
I say
SORRY
in Future, I do the right
Tasks send back if they are ready
download
No bunkering Not to many Tasks, and so on
Tom | |
|
|
|
|
Hello,
How is fairness ensured with audit tasks?
For example we can read in the results:
Rank Name Team Score Tasks
a n1 X 55 444.69 77
b n2 Y 50 848.67 313
c n3 Z 44 645.20 6
thank you
____________
| |
|
|
|
|
Thanks.
Jim
____________
Thanks,
Jim
| |
|
|
|
Hello,
How is fairness ensured with audit tasks?
For example we can read in the results:
Rank Name Team Score Tasks
a n1 X 55 444.69 77
b n2 Y 50 848.67 313
c n3 Z 44 645.20 6
thank you
the score is proportional to the time taken. | |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
Day 3 task status update:
Challenge: Magellan 500th Anniversary
App: 4 (CUL-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-21 22:31:22 UTC)
12629 tasks have been sent out. [CPU/GPU/anonymous_platform: 12629 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
1967 (16%) were aborted. [1967 (16%) / 0 (0%) / 0 (0%)]
317 (3%) came back with some kind of an error. [317 (3%) / 0 (0%) / 0 (0%)]
4818 (38%) have returned a successful result. [4818 (38%) / 0 (0%) / 0 (0%)]
5527 (44%) are still in progress. [5527 (44%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
1516 (31%) are pending validation. [1516 (31%) / 0 (0%) / 0 (0%)]
3302 (69%) have been successfully validated. [3302 (69%) / 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=19339247. The leading edge was at n=18840665 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.65% as much as it had prior to the challenge!
Challenge: Magellan 500th Anniversary
App: 3 (WOO-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-21 22:31:23 UTC)
8464 tasks have been sent out. [CPU/GPU/anonymous_platform: 8464 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
1476 (17%) were aborted. [1476 (17%) / 0 (0%) / 0 (0%)]
463 (5%) came back with some kind of an error. [463 (5%) / 0 (0%) / 0 (0%)]
2771 (33%) have returned a successful result. [2771 (33%) / 0 (0%) / 0 (0%)]
3754 (44%) are still in progress. [3754 (44%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
736 (27%) are pending validation. [736 (27%) / 0 (0%) / 0 (0%)]
2035 (73%) have been successfully validated. [2035 (73%) / 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=19845651. The leading edge was at n=19356295 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.53% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
|
|
|
I was wondering what the split is between Cullen and Woodall tasks in this Magellan 500th Anniversary Challenge?
Is it 50:50 or are users favouring one over the other.
Is there a tactical advantage points wise to choose one?
____________
 | |
|
|
|
Why are so many aborted? I can see some people aborting DC tasks, but those aren't counted here.
Aborting all long runners, cause no avx support and those tasks
have estimated time left with 9.00 Cullen (LLR) (mt-4-cores) 196:43:18
and Time until end of Magellan 500th Anniversary challenge: 155:09:00
____________
 | |
|
BurVolunteer tester
Send message
Joined: 25 Feb 20
Posts: 515
ID: 1241833
Credit: 413,783,846
RAC: 37,243
|
Why are so many aborted? I can see some people aborting DC tasks, but those aren't counted here.
Aborting all long runners, cause no avx support and those tasks
have estimated time left with 9.00 Cullen (LLR) (mt-4-cores) 196:43:18
and Time until end of Magellan 500th Anniversary challenge: 155:09:00
Every day there are 15-16% aborted, it can't be a single user, I think.
I was wondering what the split is between Cullen and Woodall tasks in this Magellan 500th Anniversary Challenge?
Is it 50:50 or are users favouring one over the other. It's in the stats posted by Michael. Cullen is strongly favored, which I assume is due to it being behind in terms of n (19.2M vs. 19.8M). I only crunch CUL for that reason. On the other hand, maybe there is a more profane reason like it giving more points/time.
____________
1281979 * 2^485014 + 1 is prime ... no further hits up to: n = 5,700,000 | |
|
|
|
I was wondering what the split is between Cullen and Woodall tasks in this Magellan 500th Anniversary Challenge?
Is it 50:50 or are users favouring one over the other.
Answering only the first part. You can see some numbers in Michael Gutierrez's post above.
For example, "returned successfully" is 1516+3302+2 = 4820 for Cullen, and 736+2035+1 = 2772 for Woodall. As a ratio, 4820:2772 is approximately 63:37 (in percent). However, this is by number of tasks. But since Woodall are currently longer tasks than Cullen, the ratio in terms of computation time or credit would be more even than that.
/JeppeSN
Addition (in edit): I have speculated whether CUL is going to overtake WOO during this challenge (deep Discord link). I think it is the case; before the end of the challenge, leading edge CUL may be bigger than leading edge WOO. | |
|
|
|
|
I had crunch only with grca
a long Time
I am every Day per 24 h in work
7 Days per week
ever.
That was
without Problems | |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
Day 4 update, split by project @vaughan!
Challenge: Magellan 500th Anniversary
App: 4 (CUL-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-22 19:46:22 UTC)
15093 tasks have been sent out. [CPU/GPU/anonymous_platform: 15093 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
2357 (16%) were aborted. [2357 (16%) / 0 (0%) / 0 (0%)]
384 (3%) came back with some kind of an error. [384 (3%) / 0 (0%) / 0 (0%)]
6593 (44%) have returned a successful result. [6593 (44%) / 0 (0%) / 0 (0%)]
5759 (38%) are still in progress. [5759 (38%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
1351 (20%) are pending validation. [1351 (20%) / 0 (0%) / 0 (0%)]
5242 (80%) have been successfully validated. [5242 (80%) / 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=19434399. The leading edge was at n=18840665 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.15% as much as it had prior to the challenge!
Challenge: Magellan 500th Anniversary
App: 3 (WOO-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-22 19:46:24 UTC)
9553 tasks have been sent out. [CPU/GPU/anonymous_platform: 9553 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
1680 (18%) were aborted. [1680 (18%) / 0 (0%) / 0 (0%)]
495 (5%) came back with some kind of an error. [495 (5%) / 0 (0%) / 0 (0%)]
3793 (40%) have returned a successful result. [3793 (40%) / 0 (0%) / 0 (0%)]
3585 (38%) are still in progress. [3585 (38%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
589 (16%) are pending validation. [589 (16%) / 0 (0%) / 0 (0%)]
3204 (84%) have been successfully validated. [3204 (84%) / 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=19905501. The leading edge was at n=19356295 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.84% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
|
|
|
All 16 Tasks are error,
I give they back
I am out of this Challenge
perhaps in the next Challenge is all right
____________
| |
|
|
|
|
Been crunching for few days now, only too see top individual mr. Pavel A. having done over 26mil already 1.5k tasks.
Only to be further jaw dropped by seeing most are crunched by Intel Core2Quad Q9400 (with 10 cores/threads?)
and to see his tasks are really blazing fast
http://www.primegrid.com/workunit.php?wuid=685988921
and then even faster on i7-2600k
http://www.primegrid.com/workunit.php?wuid=685472220
am I seeing things, am I doing it wrong? | |
|
|
|
am I seeing things, am I doing it wrong?
yes, you need to buy/rent/steal a server farm and hide it behind a proxy. | |
|
|
|
am I seeing things, am I doing it wrong?
yes, you need to buy/rent/steal a server farm and hide it behind a proxy.
Precisely. It is a frequently asked question.
Behind what looks like just one single host on www.primegrid.com, Pavel Atnashev has several computers. When you know this, there are tiny clues. In the first task you linked, it says something with running 10.2.1.1/sllr64. In another task, also from what PrimeGrid calls Computer 905516 it is running 10.2.1.234/sllr64. So there are in reality a bunch of machines behind one host entry. It is the same for 905514, your other example.
/JeppeSN | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 390,667,578
RAC: 110,130
|
am I seeing things, am I doing it wrong?
He’s got a full rack of servers in his apartment, with custom BOINC software and a custom version of LLR to get them to run without disk drives. They talk to the PrimeGrid server through some small gateway computers. Those gateways are what you see in his host list. They are not the computers doing the actual crunching.
He is also the person who wrote our LLR2 software.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
Investigator
I think, the Ccleaner can bee the Problem
Who has experiense with this. ??? | |
|
Yves GallotVolunteer developer
Project scientist
Send message
Joined: 19 Aug 12
Posts: 800
ID: 164101
Credit: 305,636,592
RAC: 5,195
|
Who is " he " or Person ???
He is the author of LLR2 who recently eliminated a Riesel Project candidate: 146561 · 211280802 - 1. | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 390,667,578
RAC: 110,130
|
|
Somebody here or on Discord wanted to know when we passed n=20M on the challenge tasks. Woodall has now passed 20M. The highest that's been sent to a user so far is 20010019.
The highest Cullen task sent out so far is n=19537253.
____________
My lucky number is 75898524288+1 | |
|
|
|
|
Thanks for that update on going past 20m. We should get to 25m soon! | |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
Day 5:
Challenge: Magellan 500th Anniversary
App: 4 (CUL-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-23 17:32:55 UTC)
17583 tasks have been sent out. [CPU/GPU/anonymous_platform: 17583 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
2740 (16%) were aborted. [2740 (16%) / 0 (0%) / 0 (0%)]
435 (2%) came back with some kind of an error. [435 (2%) / 0 (0%) / 0 (0%)]
8520 (48%) have returned a successful result. [8520 (48%) / 0 (0%) / 0 (0%)]
5888 (33%) are still in progress. [5888 (33%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
1260 (15%) are pending validation. [1260 (15%) / 0 (0%) / 0 (0%)]
7260 (85%) have been successfully validated. [7260 (85%) / 0 (0%) / 0 (0%)]
4 (0%) were invalid. [4 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=19544549. The leading edge was at n=18840665 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.74% as much as it had prior to the challenge!
Challenge: Magellan 500th Anniversary
App: 3 (WOO-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-23 17:32:56 UTC)
11174 tasks have been sent out. [CPU/GPU/anonymous_platform: 11174 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
1813 (16%) were aborted. [1813 (16%) / 0 (0%) / 0 (0%)]
519 (5%) came back with some kind of an error. [519 (5%) / 0 (0%) / 0 (0%)]
4798 (43%) have returned a successful result. [4798 (43%) / 0 (0%) / 0 (0%)]
4044 (36%) are still in progress. [4044 (36%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
665 (14%) are pending validation. [665 (14%) / 0 (0%) / 0 (0%)]
4133 (86%) have been successfully validated. [4133 (86%) / 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=20019411. The leading edge was at n=19356295 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.43% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
|
|
|
I've never overclocked gamer PCs.
Thous Systems are ready for Gamer.
This is no Problem,
Boost Systems for Gamer are " out "
perhaps some People do this, but me not
perhaps are Mega Cache inside in LLR Tasks, but if its so, then all tasks are need this Cache.
But some People take a Defrag - and so. the Tasks are longer and longer
Tom | |
|
BurVolunteer tester
Send message
Joined: 25 Feb 20
Posts: 515
ID: 1241833
Credit: 413,783,846
RAC: 37,243
|
|
Tom, in my experience all these "tuning" or "cleaning" apps are more or less worthless or even harmful. In the old days of pre Windows 7 they might have had some use, but even then most were sh*t. And current Windows versions are quite optimized, so get rid of everything. 3rd party defrag tools aren't required for years now. I'd also use the build-in virus protection of Windows 10, it's been tested as being one of the best (av-test.org) and it's seamlessly integrated and quite fast.
But LLR2 is a real stress-test for any computer. I have one host that performs without flaw even quantum mechanical DFT calculations, but couldn't do a single GCW task. So it might be your host is just a bit too unstable.
____________
1281979 * 2^485014 + 1 is prime ... no further hits up to: n = 5,700,000 | |
|
|
|
|
Thanks for your Informations
Browser and his Settings
Windows 10 or higher-
The compatible Browser s Name is : ??? | |
|
|
|
|
It looks like the stats pages for CUL and WOO may be taking the double check tasks into account for the work unit totals since the number of WU in the most recent ranges are greater than the number of WUs in previous ranges by a large margin.
____________
 | |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
Day 6:
Challenge: Magellan 500th Anniversary
App: 4 (CUL-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-24 16:36:59 UTC)
20389 tasks have been sent out. [CPU/GPU/anonymous_platform: 20389 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
3048 (15%) were aborted. [3048 (15%) / 0 (0%) / 0 (0%)]
514 (3%) came back with some kind of an error. [514 (3%) / 0 (0%) / 0 (0%)]
10598 (52%) have returned a successful result. [10598 (52%) / 0 (0%) / 0 (0%)]
6229 (31%) are still in progress. [6229 (31%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
1156 (11%) are pending validation. [1156 (11%) / 0 (0%) / 0 (0%)]
9442 (89%) have been successfully validated. [9442 (89%) / 0 (0%) / 0 (0%)]
4 (0%) were invalid. [4 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=19652494. The leading edge was at n=18840665 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 4.31% as much as it had prior to the challenge!
Challenge: Magellan 500th Anniversary
App: 3 (WOO-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-24 16:37:00 UTC)
12737 tasks have been sent out. [CPU/GPU/anonymous_platform: 12737 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
2054 (16%) were aborted. [2054 (16%) / 0 (0%) / 0 (0%)]
577 (5%) came back with some kind of an error. [577 (5%) / 0 (0%) / 0 (0%)]
5954 (47%) have returned a successful result. [5954 (47%) / 0 (0%) / 0 (0%)]
4152 (33%) are still in progress. [4152 (33%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
533 (9%) are pending validation. [533 (9%) / 0 (0%) / 0 (0%)]
5421 (91%) have been successfully validated. [5421 (91%) / 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=20110309. The leading edge was at n=19356295 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.90% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
Day 7:
Challenge: Magellan 500th Anniversary
App: 4 (CUL-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-25 23:54:29 UTC)
24019 tasks have been sent out. [CPU/GPU/anonymous_platform: 24019 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
3528 (15%) were aborted. [3528 (15%) / 0 (0%) / 0 (0%)]
839 (3%) came back with some kind of an error. [839 (3%) / 0 (0%) / 0 (0%)]
13498 (56%) have returned a successful result. [13498 (56%) / 0 (0%) / 0 (0%)]
6154 (26%) are still in progress. [6154 (26%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
1028 (8%) are pending validation. [1028 (8%) / 0 (0%) / 0 (0%)]
12470 (92%) have been successfully validated. [12470 (92%) / 0 (0%) / 0 (0%)]
4 (0%) were invalid. [4 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=19792080. The leading edge was at n=18840665 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.05% as much as it had prior to the challenge!
Challenge: Magellan 500th Anniversary
App: 3 (WOO-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-25 23:54:30 UTC)
15300 tasks have been sent out. [CPU/GPU/anonymous_platform: 15300 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
2202 (14%) were aborted. [2202 (14%) / 0 (0%) / 0 (0%)]
931 (6%) came back with some kind of an error. [931 (6%) / 0 (0%) / 0 (0%)]
7427 (49%) have returned a successful result. [7427 (49%) / 0 (0%) / 0 (0%)]
4740 (31%) are still in progress. [4740 (31%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
663 (9%) are pending validation. [663 (9%) / 0 (0%) / 0 (0%)]
6764 (91%) have been successfully validated. [6764 (91%) / 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=20261005. The leading edge was at n=19356295 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 4.67% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
|
|
|
I m not in this Challenge
4 Tasks are Ready,
22.7.2020
4 days ago
Now not activity here in Challenge
-------------------------------------
I crunch ( pps-sieve ) | |
|
|
|
|
Probably tasks that failed to reach your BOINC client.
____________
My lucky number is 6219*2^3374198+1
| |
|
|
|
|
No, my Boinc client is right working.
Please look in your Private Message
Thank You
Tom
____________
| |
|
|
|
No, my Boinc client is right working.
Please look in your Private Message
Thank You
Tom
I mean that these tasks never reached your BOINC client due to some network problem.
____________
My lucky number is 6219*2^3374198+1
| |
|
|
|
|
I have a Checkbox
do you know it ?
dont know why
Tasks returned in the last 24 hours
I Think - this BOX is no good for LLR Tasks
This box is come 4 month ago
I am 10 Years here but have never seen this, Please delete this Box- in my Projekt Preferences
You can do it.
And if the Box be out
so we have no problems
| |
|
|
|
|
That's simply information on the work you've done in the past day.
From the little I can see you're not currently running any cpu tasks. Have you ticked the "use CPU" box in preferences.? | |
|
|
|
That's simply information on the work you've done in the past day.
From the little I can see you're not currently running any cpu tasks. Have you ticked the "use CPU" box in preferences.?
I am out of the Challenge 4 Days ago
I Cgrunch with my Graca rechencraft RTX 2080 ti
GTX 1080 ti.
I am 4 days ago out of this Challenge
but thanks for your iIdea.
| |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
Only one day left in the challenge - get your primes in now!
Challenge: Magellan 500th Anniversary
App: 4 (CUL-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-27 16:20:47 UTC)
28398 tasks have been sent out. [CPU/GPU/anonymous_platform: 28398 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
5056 (18%) were aborted. [5056 (18%) / 0 (0%) / 0 (0%)]
1154 (4%) came back with some kind of an error. [1154 (4%) / 0 (0%) / 0 (0%)]
16813 (59%) have returned a successful result. [16814 (59%) / 0 (0%) / 0 (0%)]
5375 (19%) are still in progress. [5374 (19%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
1255 (7%) are pending validation. [1256 (7%) / 0 (0%) / 0 (0%)]
15558 (93%) have been successfully validated. [15558 (93%) / 0 (0%) / 0 (0%)]
4 (0%) were invalid. [4 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=19922427. The leading edge was at n=18840665 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.74% as much as it had prior to the challenge!
Challenge: Magellan 500th Anniversary
App: 3 (WOO-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-27 16:20:50 UTC)
18472 tasks have been sent out. [CPU/GPU/anonymous_platform: 18472 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
4411 (24%) were aborted. [4411 (24%) / 0 (0%) / 0 (0%)]
1424 (8%) came back with some kind of an error. [1424 (8%) / 0 (0%) / 0 (0%)]
9540 (52%) have returned a successful result. [9540 (52%) / 0 (0%) / 0 (0%)]
3097 (17%) are still in progress. [3097 (17%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
982 (10%) are pending validation. [982 (10%) / 0 (0%) / 0 (0%)]
8558 (90%) have been successfully validated. [8558 (90%) / 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=20344117. The leading edge was at n=19356295 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.10% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
|
|
|
Feeling disappointed :(
FFT length 2304K
stderr.txt:
<core_client_version>7.14.2</core_client_version>
<![CDATA[
<stderr_txt>
BOINC PrimeGrid wrapper 2.01 (Aug 11 2020 22:09:56)
running ../../projects/www.primegrid.com/llr2_1.0.0_win64_200814.exe -v
LLR2 Program - Version 1.0.0, using Gwnum Library Version 29.8
running ../../projects/www.primegrid.com/llr2_1.0.0_win64_200814.exe -oGerbicz=1 -oProofName=proof -oProofCount=128 -oProductName=prod -oPietrzak=1 -oCachePoints=0 -pSavePoints -q19876581*2^19876581+1 -d -t4 -oDiskWriteTime=1
Starting Proth prime test of 19876581*2^19876581+1
Using zero-padded FMA3 FFT length 2304K, Pass1=384, Pass2=6K, clm=2, 4 threads, a = 5, L2 = 454*342, M = 155268
proof.10 is missing or corrupt.
Testing complete.
15:24:56 (14716): called boinc_finish(0)
</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>llrCUL_354146860_0_r400662640_10</file_name>
<error_code>-240 (stat() failed)</error_code>
</file_xfer_error>
<file_xfer_error>
<file_name>llrCUL_354146860_0_r400662640_11</file_name>
<error_code>-240 (stat() failed)</error_code>
</file_xfer_error>
<file_xfer_error>
<file_name>llrCUL_354146860_0_r400662640_12</file_name>
<error_code>-240 (stat() failed)</error_code>
</file_xfer_error>
<file_xfer_error>
<file_name>llrCUL_354146860_0_r400662640_13</file_name>
<error_code>-240 (stat() failed)</error_code>
</file_xfer_error>
</message>
]]>
BOINC Manager log
11/27/2020 3:24:59 PM | PrimeGrid | Computation for task llrCUL_354146860_0 finished
11/27/2020 3:24:59 PM | PrimeGrid | Output file llrCUL_354146860_0_r400662640_10 for task llrCUL_354146860_0 absent
11/27/2020 3:24:59 PM | PrimeGrid | Output file llrCUL_354146860_0_r400662640_11 for task llrCUL_354146860_0 absent
11/27/2020 3:24:59 PM | PrimeGrid | Output file llrCUL_354146860_0_r400662640_12 for task llrCUL_354146860_0 absent
11/27/2020 3:24:59 PM | PrimeGrid | Output file llrCUL_354146860_0_r400662640_13 for task llrCUL_354146860_0 absent
____________
"Accidit in puncto, quod non contingit in anno."
Something that does not occur in a year may, perchance, happen in a moment. | |
|
streamVolunteer moderator
Project administrator
Volunteer developer
Volunteer tester
Send message
Joined: 1 Mar 14
Posts: 1022
ID: 301928
Credit: 543,195,386
RAC: 4
    
|
Feeling disappointed :(
There is a big red WARNING on your previous task. This PC is unstable.
Considering that other tasks before these two finished without errors, most probably another straw finally broke this PC. It may even an extra degree of outside temperature, an extra bit of dust, etc.
| |
|
|
|
Feeling disappointed :(
There is a big red WARNING on your previous task. This PC is unstable.
Considering that other tasks before these two finished without errors, most probably another straw finally broke this PC. It may even an extra degree of outside temperature, an extra bit of dust, etc.
This is proven - sure when the PC housing is removed, the cooling is 5 to 8 percent better. Humidity can also cause. the dust is moistened and can burn firmly. Particles are not visible. (but with the large consumption nut the PC lie on the table, under the table the heat is enormously high. When the PC is on a carpet under the table, the dust is swirling at any time. If possible, open a window, the dust swirls into the radiator. ( 100% ) - Fan ( 100% ) cooling medium are also built with different differences, Blue Liquid is often in notebooks. Water Cooling Systems or Fan.The big warning is to read - about best X | |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
Only a few hours left! Some friendly reminders... :)
At the Conclusion of the Challenge
When the challenge completes, we would prefer users "moving on" to finish those tasks they have downloaded, if not then please ABORT the WU's (and then UPDATE the PrimeGrid project) instead of DETACHING, RESETTING, or PAUSING.
ABORTING WU's allows them to be recycled immediately; thus a much faster "clean up" to the end of a Challenge. DETACHING, RESETTING, and PAUSING WU's causes them to remain in limbo until they EXPIRE. Therefore, we must wait until WU's expire to send them out to be completed.
Likewise, if you're shutting down the computer for an extended period of time, or deleting the VM (Virtual Machine), please ABORT all remaining tasks first. Also, be aware that merely shutting off a cloud server doesn't stop the billing. You have to destroy/delete the server if you don't want to continue to be charged for it.
Thank you!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
|
|
|
Why number of Woodall tasks reduced and Cullen became larger in the new ranges?
____________
| |
|
|
|
|
Michael
Thank You for your Time and all Updates
Have a nice Day
Great Job
Tom | |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 390,667,578
RAC: 110,130
|
Why number of Woodall tasks reduced and Cullen became larger in the new ranges?
People decided to run more Cullen tasks. That's not under our control, nor can we explain what is in peoples' minds.
____________
My lucky number is 75898524288+1 | |
|
|
|
Why number of Woodall tasks reduced and Cullen became larger in the new ranges?
People decided to run more Cullen tasks. That's not under our control, nor can we explain what is in peoples' minds.
I think they were referring to why the stat pages for both look off. Cullen shows substantially more work units in the 18-19M and 19-20M ranges than in any of the previous ranges. I assume LLR2 and the separate double check work units are the culprit.
____________
| |
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 390,667,578
RAC: 110,130
|
Why number of Woodall tasks reduced and Cullen became larger in the new ranges?
People decided to run more Cullen tasks. That's not under our control, nor can we explain what is in peoples' minds.
I think they were referring to why the stat pages for both look off. Cullen shows substantially more work units in the 18-19M and 19-20M ranges than in any of the previous ranges. I assume LLR2 and the separate double check work units are the culprit.
That could be. One other item of note is that we have temporarily suppressed Woodall tasks with even n's because of an LLR2 bug. So there's a lot less Woodall tasks over a given n range than there normally wood be, at least until the fix for this goes into production.
____________
My lucky number is 75898524288+1 | |
|
|
|
Why number of Woodall tasks reduced and Cullen became larger in the new ranges?
People decided to run more Cullen tasks. That's not under our control, nor can we explain what is in peoples' minds.
I think they were referring to why the stat pages for both look off. Cullen shows substantially more work units in the 18-19M and 19-20M ranges than in any of the previous ranges. I assume LLR2 and the separate double check work units are the culprit.
That could be. One other item of note is that we have temporarily suppressed Woodall tasks with even n's because of an LLR2 bug. So there's a lot less Woodall tasks over a given n range than there normally wood be, at least until the fix for this goes into production.
for Fun this Joke
Maybe some still had "Thanks giving" in mind. Such a turkey is bigger than you think - no idea but real | |
|
|
|
That could be. One other item of note is that we have temporarily suppressed Woodall tasks with even n's because of an LLR2 bug. So there's a lot less Woodall tasks over a given n range than there normally wood be, at least until the fix for this goes into production.
Ah yes, I forgot about that. That also helped prevent Cullen leading edge from catching up on Woodall leading edge. /JeppeSN | |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
And we're done! Here are the final stats. Cleanup is beginning, I expect it to take about 2-3 weeks.
Challenge: Magellan 500th Anniversary
App: 4 (CUL-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-28 23:11:32 UTC)
35040 tasks have been sent out. [CPU/GPU/anonymous_platform: 35040 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
11076 (32%) were aborted. [11076 (32%) / 0 (0%) / 0 (0%)]
1443 (4%) came back with some kind of an error. [1443 (4%) / 0 (0%) / 0 (0%)]
19234 (55%) have returned a successful result. [19234 (55%) / 0 (0%) / 0 (0%)]
2818 (8%) are still in progress. [2818 (8%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
1267 (7%) are pending validation. [1267 (7%) / 0 (0%) / 0 (0%)]
17967 (93%) have been successfully validated. [17967 (93%) / 0 (0%) / 0 (0%)]
4 (0%) were invalid. [4 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=19938773. The leading edge was at n=18840665 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.83% as much as it had prior to the challenge!
Challenge: Magellan 500th Anniversary
App: 3 (WOO-LLR)
Fast DC tasks are NOT included.
(As of 2020-11-28 23:11:35 UTC)
22087 tasks have been sent out. [CPU/GPU/anonymous_platform: 22087 (100%) / 0 (0%) / 0 (0%)]
Of those tasks that have been sent out:
6959 (32%) were aborted. [6959 (32%) / 0 (0%) / 0 (0%)]
1719 (8%) came back with some kind of an error. [1719 (8%) / 0 (0%) / 0 (0%)]
10945 (50%) have returned a successful result. [10945 (50%) / 0 (0%) / 0 (0%)]
2235 (10%) are still in progress. [2235 (10%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
728 (7%) are pending validation. [728 (7%) / 0 (0%) / 0 (0%)]
10217 (93%) have been successfully validated. [10217 (93%) / 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=20361169. The leading edge was at n=19356295 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.19% as much as it had prior to the challenge!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
|
|
|
Thank you Michael for keep us informed.
____________
Thanks,
Jim
| |
|
streamVolunteer moderator
Project administrator
Volunteer developer
Volunteer tester
Send message
Joined: 1 Mar 14
Posts: 1022
ID: 301928
Credit: 543,195,386
RAC: 4
|
|
Expected cleanup time should be less, may be about 1-2 weeks. It's same for all LLR2 challenges because we only waiting for certificates which have equal timeout of 3 days for all LLR2 projects. | |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
Cleanup Status:
Nov 29: 971 tasks outstanding; 592 affecting individual (145) scoring positions; 110 affecting team (22) scoring positions.
Nov 30: 226 tasks outstanding; 93 affecting individual (42) scoring positions; 3 affecting team (3) scoring positions.
Dec 1: 82 tasks outstanding; 15 affecting individual (13) scoring positions; 0 affecting team (0) scoring positions.
Dec 2: 38 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Dec 3: 25 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
Michael GutierrezVolunteer moderator
Project administrator
Project scientist
Send message
Joined: 21 Mar 17
Posts: 341
ID: 764476
Credit: 46,281,510
RAC: 0
|
|
The results are final!
Our second LLR2 challenge was a success!
During these 5 days, we completed almost 30 thousand tasks. Interestingly, we completed almost twice the number of Cullen tasks as Woodall tasks - about 20,000 compared to 10,000. Unfortunately, we didn't find any new primes, but overall, that's still more than 7 times DIV's average LLR2 output.
151 teams and 728 individuals participated in the Challenge.
Top Three Individuals:
1. Pavel Atnashev
2. tng
3. vaughan
Top Three Teams:
1. Antarctic Crunchers
2. Czech National Team
3. Ural Federal University
The next Challenge is the Great Conjunction Challenge, which starts December 21. We hope to see you there! Thank you again to everyone. We appreciate your participation and hope you had fun!
____________
Time flies like an arrow. Fruit flies like a banana. | |
|
|
|
|
Again, thanks a lot for a great challenge!
I'm looking forward to joining the fun on the 21st!
____________
Greetings, Jens
147433824^131072+1 | |
|
Message boards :
Number crunching :
Magellan 500th Anniversary Challenge |
