| Author |
Message |
|---|
|
|
|
Welcome to the Winter Solstice Challenge
The Final Challenge of the 2014 Challenge series is upon us. The Winter Solstice Challenge will be a 3 day (72 hour) celebration on account of the winters solstice. The challenge is being offered on PrimeGrid's most successful sieve, the Proth Prime Search (Sieve) application. Come join us and warm yourself by the Solstice fires!
The Winter Solstice...a predictable event in nature that has occurred for billions of years. A way point in the cyclic motion of the Universe. Many of the today's major winter festivals and celebrations can trace their origins back to this event...the longest night of the year (or the shortest day).
We'd like to wish everyone a Happy Holiday...whatever festival or celebration you may observe.
NOTE: The servers are located in the Northern Hemisphere; therefore, we'll observe winter. However, the Southern Hemisphere will be experiencing the Summer Solstice.
To participate in the Challenge, please select only the PPS (Sieve) project in your PrimeGrid preferences section. The challenge will begin 18 December 2014 23:03 UTC and end 21 December 2014 23:03 UTC. Application builds are available for the following:
- Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 1.40 (ati13ati)
- Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 1.39 (cuda23)
- Microsoft Windows (98 or later) running on an Intel x86-compatible CPU 1.39
- Microsoft Windows running on an AMD x86_64 or Intel EM64T CPU 1.39
- Linux running on an Intel x86-compatible CPU 1.40 (ati13ati)
- Linux running on an Intel x86-compatible CPU 1.39 (cuda23)
- Linux running on an Intel x86-compatible CPU 1.39
- Linux running on an AMD x86_64 or Intel EM64T CPU 1.40 (ati13ati)
- Linux running on an AMD x86_64 or Intel EM64T CPU 1.39 (cuda23)
- Linux running on an AMD x86_64 or Intel EM64T CPU 1.39
- Mac OS 10.4 or later running on Intel 1.39
- Mac OS 10.4 or later running on Intel 1.39 (cuda32)
- Mac OS 10.5+ running on an Intel 64-bit CPU 1.39
- Mac OS 10.5+ running on an Intel 64-bit CPU 1.39 (cuda32)
- Mac OS 10.5+ running on an Intel 64-bit CPU 1.49 (openclPPSieveMAC)
Time zone converter:
The World Clock - Time Zone Converter
NOTE: The countdown clock on the front page uses the host computer time. Therefore, if your computer time is off, so will the countdown clock. For precise timing, use the UTC Time in the data section to the left of the countdown clock.
Scoring Information
Scores will be kept for individuals and teams. Only work units issued AFTER 18 December 2014 23:03 UTC and received BEFORE 21 December 2014 23:03 UTC will be considered for credit. Since this is a fixed credit project, we'll be using cobblestones for scoring. Unlike what some of you might still be used to, there will be a clean up.
Credit is currently set at 3371 cobblestones per WU.
At the Conclusion of the Challenge
We would prefer users "moving on" to finish those tasks they have downloaded, if not then please ABORT the WU's instead of DETACHING, RESETTING, or PAUSING.
ABORTING WU's allows them to be recycled immediately; thus a much faster "clean up" to the end of an LLR Challenge. DETACHING, RESETTING, and PAUSING WU's causes them to remain in limbo until they EXPIRE. Therefore, we must wait until WU's expire to send them out to be completed.
Please consider either completing what's in the queue or ABORTING them. Thank you. :)
About the Proth Prime Search
The Proth Prime Search is done in collaboration with the Proth Search project. This search looks for primes in the form of k*2^n+1. With the condition 2^n > k, these are often called Proth primes. This project also has the added bonus of possibly finding factors of "classical" Fermat numbers or Generalized Fermat numbers. As this requires PrimeFormGW (PFGW) (a primality-testing program), once PrimeGrid finds a prime, it is then tested on PrimeGrid's servers for divisibility.
Our initial goal was to double check all previous work up to n=500K for odd k<1200 and to fill in any gaps that were missed. We have accomplished that now and have increased it to n=800K. PG LLRNet searched up to n=200,000 and found several missed primes in previously searched ranges. Although primes that small did not make it into the Top 5000 Primes database, the work was still important as it may have led to new factors for "classical" Fermat numbers or Generalized Fermat numbers. While there are many GFN factors, currently there are only about 292 "classical" Fermat number factors known. Current primes found in PPS definitely make it into the Top 5000 Primes database.
Once the 800K goal is reached, we may head to 1M before turning our focus to smaller k values and higher n values. For example, k<300 complete to n=2M, k<600 complete to n=1.5M and so on.
For more information about "Proth" primes, please visit these links:
About Proth Search
The Proth Search project was established in 1998 by Ray Ballinger and Wilfrid Keller to coordinate a distributed effort to find Proth primes (primes of the form k*2^n+1) for k < 300. Ray was interested in finding primes while Wilfrid was interested in finding divisors of Fermat number. Since that time it has expanded to include k < 1200. Mark Rodenkirch (aka rogue) has been helping Ray keep the website up to date for the past few years.
Early in 2008, PrimeGrid and Proth Search teamed up to provide a software managed distributed effort to the search. Although it might appear that PrimeGrid is duplicating some of the Proth Search effort by re-doing some ranges, few ranges on Proth Search were ever double-checked. This has resulted in PrimeGrid finding primes that were missed by previous searchers. By the end of 2008, all new primes found by PrimeGrid were eligible for inclusion in Chris Caldwell's Prime Pages Top 5000. Sometime in 2009, over 90% of the tests handed out by PrimeGrid were numbers that have never been tested.
Since then a great deal of proth primes have been founds, including over 10 mega primes!
PrimeGrid intends to continue the search indefinitely for Proth primes.
What is sieving?
Sieving is the first step to prime finding. In general, a sieve separates wanted/desired elements from unwanted material using a tool such as a mesh, net or other filtration or distillation methods. The word "sift" derives from this term. (Wikipedia - Sieve)
In PrimeGrid's case, the desired elements ultimately are prime numbers and the unwanted material are composite numbers. Our tool of choice for PPS sieve is Geoff Reynolds'/Ken Brazier's tpsieve program. It eliminates possible candidates by removing numbers that have small factors. As this process is much faster than primality testing, it is good to thoroughly sieve a data set before primality testing.
Sieving removes many candidates at the beginning. However, the deeper the sieve goes, the slower the rate of removal, till eventually sieving removes candidates at the same rate as primality testing. This is sometimes referred to as "optimal depth". Primality testing is recommended at this point.
There are many factors that determine how much time and how deep to sieve. After sieving, all the remaining candidates must be primality tested to determine their "prime" status.
About the Winter Solstice
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
|
|
|
|
|
|
Looking forward to the contest. Do I have to start with an empty cache like the previous contest and then load up right at/after the start time in order to receive credit? Or can I keep existing wu's in the cache and then crunch them as they receive their turn?
Thanks. |
|
|
 Michael Goetz Volunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
                               
|
Looking forward to the contest. Do I have to start with an empty cache like the previous contest and then load up right at/after the start time in order to receive credit? Or can I keep existing wu's in the cache and then crunch them as they receive their turn?
Thanks.
All of the challenges we run on BOINC work the same way in that ONLY tasks sent after the challenge starts and received before the challenge ends count towards the challenge. Of course, you still get BOINC credit for valid tasks no matter when they're sent and received, but to count for the challenge score they have to be sent out and returned during the challenge.
The challenges that we run on PRPNet have different rules.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Thank you, do I have to start with an empty cue?
|
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
Thank you, do I have to start with an empty cue?
Yes, you should absolutely start with an empty queue (or cache).
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Thank you. |
|
|
|
|
|
That becomes for me the first competition at which I for me and my team Seti-Germany participates. I look forward to it. ;-) |
|
|
Ken_g6Volunteer developer
Send message
Joined: 4 Jul 06
Posts: 938
ID: 3110
Credit: 258,690,389
RAC: 92,022
                      
|
|
Over in the CUDA testing thread I've been trying to come up with an app_config.xml file that might speed up the CUDA WUs a few percent. Other people on my TeAm have tested it and aren't having much luck so far. Any help would be appreciated!
____________
|
|
|
|
|
|
I went by the home page and downloaded several before the time, even though the counter started going up. I realize my home clock and the server clock are different, but my clock is synced correctly, I just double checked it and I was not off, but PG was off by about 5 seconds, so I had to abort a bunch of units that downloaded too early.
|
|
|
|
|
|
No stats page?
Good luck everyone.
____________
676754^262144+1 is prime |
|
|
|
|
|
No tasks for Ati
NeoMetal-PC
3709519 PrimeGrid 12/18/2014 4:16:27 PM Sending scheduler request: To fetch work.
3709520 PrimeGrid 12/18/2014 4:16:27 PM Requesting new tasks for AMD/ATI GPU
3709521 PrimeGrid 12/18/2014 4:16:29 PM Scheduler request completed: got 0 new tasks
3709522 PrimeGrid 12/18/2014 4:16:29 PM Project has no tasks available
____________
Largest Primes to Date:
As Double Checker: SR5 109208*5^1816285+1 Dgts-1,269,534
As Initial Finder: SR5 243944*5^1258576-1 Dgts-879,713
 |
|
|
|
|
|
where statistics? |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
No stats page?
Good luck everyone.
I just turned the stats on, so the first run will be at 23:30 UTC (8 minutes from now).
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
I went by the home page and downloaded several before the time, even though the counter started going up. I realize my home clock and the server clock are different, but my clock is synced correctly, I just double checked it and I was not off, but PG was off by about 5 seconds, so I had to abort a bunch of units that downloaded too early.
Just checked the server clock and as far as I can tell it's off by no more than a second. It's synced with NTP, so it should be off by even less than that, but that's the best I can tell with my eyeballs.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Now no nVidia tasks
Alpha_n_Omega
16835 PrimeGrid 12/18/2014 4:28:19 PM Sending scheduler request: Requested by user.
16836 PrimeGrid 12/18/2014 4:28:19 PM Requesting new tasks for CPU and NVIDIA GPU
16837 PrimeGrid 12/18/2014 4:28:32 PM Scheduler request completed: got 0 new tasks
16838 PrimeGrid 12/18/2014 4:28:32 PM No tasks sent
16839 PrimeGrid 12/18/2014 4:28:32 PM No tasks are available for PPS (Sieve)
16840 PrimeGrid 12/18/2014 4:28:32 PM Tasks for CPU are available, but your preferences are set to not accept them
16841 PrimeGrid 12/18/2014 4:28:32 PM Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
16842 PrimeGrid 12/18/2014 4:28:32 PM This computer has reached a limit on tasks in progress
16843 PrimeGrid 12/18/2014 4:28:32 PM Project has no tasks available
16844 PrimeGrid 12/18/2014 4:28:43 PM Sending scheduler request: To fetch work.
16845 PrimeGrid 12/18/2014 4:28:43 PM Requesting new tasks for NVIDIA GPU
16846 PrimeGrid 12/18/2014 4:28:51 PM Scheduler request completed: got 0 new tasks
16847 PrimeGrid 12/18/2014 4:28:51 PM Project has no tasks available
____________
Largest Primes to Date:
As Double Checker: SR5 109208*5^1816285+1 Dgts-1,269,534
As Initial Finder: SR5 243944*5^1258576-1 Dgts-879,713
|
|
|
|
|
Now no nVidia tasks
Alpha_n_Omega
16835 PrimeGrid 12/18/2014 4:28:19 PM Sending scheduler request: Requested by user.
16836 PrimeGrid 12/18/2014 4:28:19 PM Requesting new tasks for CPU and NVIDIA GPU
16837 PrimeGrid 12/18/2014 4:28:32 PM Scheduler request completed: got 0 new tasks
16838 PrimeGrid 12/18/2014 4:28:32 PM No tasks sent
16839 PrimeGrid 12/18/2014 4:28:32 PM No tasks are available for PPS (Sieve)
16840 PrimeGrid 12/18/2014 4:28:32 PM Tasks for CPU are available, but your preferences are set to not accept them
16841 PrimeGrid 12/18/2014 4:28:32 PM Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
16842 PrimeGrid 12/18/2014 4:28:32 PM This computer has reached a limit on tasks in progress
16843 PrimeGrid 12/18/2014 4:28:32 PM Project has no tasks available
16844 PrimeGrid 12/18/2014 4:28:43 PM Sending scheduler request: To fetch work.
16845 PrimeGrid 12/18/2014 4:28:43 PM Requesting new tasks for NVIDIA GPU
16846 PrimeGrid 12/18/2014 4:28:51 PM Scheduler request completed: got 0 new tasks
16847 PrimeGrid 12/18/2014 4:28:51 PM Project has no tasks available
Do you have any suspended tasks in BOINC? |
|
|
|
|
Now no nVidia tasks
Alpha_n_Omega
16835 PrimeGrid 12/18/2014 4:28:19 PM Sending scheduler request: Requested by user.
16836 PrimeGrid 12/18/2014 4:28:19 PM Requesting new tasks for CPU and NVIDIA GPU
16837 PrimeGrid 12/18/2014 4:28:32 PM Scheduler request completed: got 0 new tasks
16838 PrimeGrid 12/18/2014 4:28:32 PM No tasks sent
16839 PrimeGrid 12/18/2014 4:28:32 PM No tasks are available for PPS (Sieve)
16840 PrimeGrid 12/18/2014 4:28:32 PM Tasks for CPU are available, but your preferences are set to not accept them
16841 PrimeGrid 12/18/2014 4:28:32 PM Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
16842 PrimeGrid 12/18/2014 4:28:32 PM This computer has reached a limit on tasks in progress
16843 PrimeGrid 12/18/2014 4:28:32 PM Project has no tasks available
16844 PrimeGrid 12/18/2014 4:28:43 PM Sending scheduler request: To fetch work.
16845 PrimeGrid 12/18/2014 4:28:43 PM Requesting new tasks for NVIDIA GPU
16846 PrimeGrid 12/18/2014 4:28:51 PM Scheduler request completed: got 0 new tasks
16847 PrimeGrid 12/18/2014 4:28:51 PM Project has no tasks available
Do you have any suspended tasks in BOINC?
No. I know BOINC very well. I did get a few before this message started. I even set the cache to 4 days.
EDIT: I just got 1 task then back to the "Project has no tasks available "
____________
Largest Primes to Date:
As Double Checker: SR5 109208*5^1816285+1 Dgts-1,269,534
As Initial Finder: SR5 243944*5^1258576-1 Dgts-879,713
|
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
No tasks for Ati
Now no nVidia tasks
When you got this, did your computer already have work to do, or was it empty and requesting its first tasks? If it already had work to do, then it's likely this was what was supposed to happen.
At the time of your posts, I still had rather strict task limits in place (no single computer could get more than two tasks per GPU in each request, and no more than 10 tasks per GPU total), and the server was holding almost 1000 tasks in memory. The memory gets checked and refilled every second (or faster), and except for the very first minute of the challenge we never exceeded 1000 task in any single minute.
So the server wasn't ever out of work to send. (And, of course, looking at the bigger picture, there's almost an infinite amount of sieve tasks that can be generated on demand.)
How many GPU tasks (running, pending, or waiting to be reported back to the server) were on your computer at the time? If you already had 10 tasks, that would explain why you were getting "no work available".
The limit is now back to its normal setting (100 tasks per GPU).
If you now have more tasks, then what you saw was the normal behavior given that we lower the limits at the beginning of a challenge. We do that so that big computers (either with a lot of GPUs or servers with lots of cores) can't deplete the entire in-memory supply of tasks and possibly cause the next computer to get a REAL "no work" message when they don't already have anything to crunch.
Note that even with the normal 100 task limit, if you are using a large cache and a fast GPU, your BOINC client may want to grab more than 100 tasks and you'll still get that "no work" message, but that's as it should be.
____________
My lucky number is 75898524288+1 |
|
|
|
|
No tasks for Ati
Now no nVidia tasks
When you got this, did your computer already have work to do, or was it empty and requesting its first tasks? If it already had work to do, then it's likely this was what was supposed to happen.
At the time of your posts, I still had rather strict task limits in place (no single computer could get more than two tasks per GPU in each request, and no more than 10 tasks per GPU total), and the server was holding almost 1000 tasks in memory. The memory gets checked and refilled every second (or faster), and except for the very first minute of the challenge we never exceeded 1000 task in any single minute.
So the server wasn't ever out of work to send. (And, of course, looking at the bigger picture, there's almost an infinite amount of sieve tasks that can be generated on demand.)
How many GPU tasks (running, pending, or waiting to be reported back to the server) were on your computer at the time? If you already had 10 tasks, that would explain why you were getting "no work available".
The limit is now back to its normal setting (100 tasks per GPU).
If you now have more tasks, then what you saw was the normal behavior given that we lower the limits at the beginning of a challenge. We do that so that big computers (either with a lot of GPUs or servers with lots of cores) can't deplete the entire in-memory supply of tasks and possibly cause the next computer to get a REAL "no work" message when they don't already have anything to crunch.
Note that even with the normal 100 task limit, if you are using a large cache and a fast GPU, your BOINC client may want to grab more than 100 tasks and you'll still get that "no work" message, but that's as it should be.
Server cache must have been it. Tasks are flowing now. I did have 1 system that had only 2 GPU tasks with CPU tasks in the 20s on all systems and got a dozen or so GPU tasks initially on the other 3 systems. I have 2 nVidia cards each on 3 systems and 1 Ati on the 4th.
____________
Largest Primes to Date:
As Double Checker: SR5 109208*5^1816285+1 Dgts-1,269,534
As Initial Finder: SR5 243944*5^1258576-1 Dgts-879,713
|
|
|
|
|
|
My scores are not showing in the list.
Cheers
S. |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
My scores are not showing in the list.
Cheers
S.
Your scores should show up during the next stats update at 00:45 UTC, about 8 minutes from now.
____________
My lucky number is 75898524288+1 |
|
|
|
|
My scores are not showing in the list.
Cheers
S.
Did you download tasks before the challenge started? If so they won't count and you should abort all and download new tasks.
EDIT: You beat me Mike. Still good info for newbies to know.
____________
Largest Primes to Date:
As Double Checker: SR5 109208*5^1816285+1 Dgts-1,269,534
As Initial Finder: SR5 243944*5^1258576-1 Dgts-879,713
|
|
|
|
|
|
Is there a link to the challenge statistics handy?
Thanks,
-Brian |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
Is there a link to the challenge statistics handy?
Thanks,
-Brian
Look on the home page (click on the big PrimeGrid logo at the top of any page.)
Right below the countdown clock are links to the stats for challenges that are in progress or are in the cleanup phase.
You can also click on the "PrimeGrid 2014 Challenge Series" link to get to a page that shows the challenges for the whole year.
____________
My lucky number is 75898524288+1 |
|
|
|
|
I went by the home page and downloaded several before the time, even though the counter started going up. I realize my home clock and the server clock are different, but my clock is synced correctly, I just double checked it and I was not off, but PG was off by about 5 seconds, so I had to abort a bunch of units that downloaded too early.
I think it is worth re-emphasizing that for PrimeGrid challenges (and I'm quite sure that P.B.27 knows this, but more for the benefit of newcomers) that the animated count-down clock on the main PG web page is driven from your local computer's clock, so if that's wrong, then the count-down counter will be wrong too. For challenge timing, there's another little blurb on the PG home page that says "UTC Time" followed by the date and time. That is the one that matters for the timing of challenge units. Of course you have to manually update the page and allow for network delays. Back in the "olden days" even the server clock could be off by a couple minutes, but recently (maybe coinciding with the move to rackspace?) it has been extremely accurate when compared with (for example) the USNO Master Clock.
Very smooth start to the challenge IMHO. I wonder how many Commodore-64s, TRS-80's, and Apple 2's it would take to match the crunching power currently being applied for these three days? :-)
--Gary
____________
"I am he as you are he as you are me and we are all together"
87*2^3496188+1 is prime! (1052460 digits)
4 is not prime! (1 digit) |
|
|
|
|
|
dangit 6hrs late on clearing out tasks
____________
My Lucky Number is 1893*2^1283297+1 |
|
|
|
|
My scores are not showing in the list.
Cheers
S.
Did you download tasks before the challenge started? If so they won't count and you should abort all and download new tasks.
EDIT: You beat me Mike. Still good info for newbies to know.
No, in fact I missed the start by 20 "nap time" minutes.
But all is well now and I'm on the board... |
|
|
|
|
I think it is worth re-emphasizing that for PrimeGrid challenges (and I'm quite sure that P.B.27 knows this...
Which is why I did a reboot and an NNTP update (being a network engineer I am very time centric because we need this information as exact as possible for logs). I double checked and there was no drift after I found out that I got tasks too early. Just confused about this. It was only 3 seconds, but that got me a few minutes off deciphering what happened.
|
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
|
Here in the northern hemisphere, the nights are long but the tasks are short. After the first day of the challenge:
Challenge: Winter Solstice
App: (PPS-Sieve)
(As of 2014-12-19 23:23:03 UTC)
191424 tasks have been sent out. [CPU/GPU/anonymous_platform: 14491 (8%) / 174046 (91%) / 2887 (2%)]
Of those tasks that have been sent out:
5183 (3%) came back with some kind of an error. [1841 (1%) / 2842 (1%) / 500 (0%)]
99112 (52%) have returned a successful result. [805 (0%) / 97526 (51%) / 784 (0%)]
87131 (46%) are still in progress. [11845 (6%) / 73682 (38%) / 1603 (1%)]
Of the tasks that have been returned successfully:
38020 (38%) are pending validation. [244 (0%) / 37498 (38%) / 281 (0%)]
61085 (62%) have been successfully validated. [561 (1%) / 60021 (61%) / 503 (1%)]
1 (0%) were invalid. [0 (0%) / 1 (0%) / 0 (0%)]
6 (0%) are inconclusive. [0 (0%) / 6 (0%) / 0 (0%)]
Nearly 200K tasks sent out, and 100K returned in the first day!
____________
My lucky number is 75898524288+1 |
|
|
streamVolunteer moderator
Project administrator
Volunteer developer
Volunteer tester
Send message
Joined: 1 Mar 14
Posts: 1022
ID: 301928
Credit: 543,195,386
RAC: 2
                
|
|
Forgot to run one system, but it refused to get work:
20.12.2014 15:08:28 Message from server: PPS (Sieve) needs 97.34MB more disk space. You currently have 379.49 MB available and it needs 476.84 MB.
What? 476.86 Megabytes of disk space required? The application file is less then one megabyte and no extra files needed.
I worked around this by letting boinc to use 90% of disk instead of default 50%. The question is how such a insane requirement could initially appear.
|
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
Forgot to run one system, but it refused to get work:
20.12.2014 15:08:28 Message from server: PPS (Sieve) needs 97.34MB more disk space. You currently have 379.49 MB available and it needs 476.84 MB.
What? 476.86 Megabytes of disk space required? The application file is less then one megabyte and no extra files needed.
I worked around this by letting boinc to use 90% of disk instead of default 50%. The question is how such a insane requirement could initially appear.
That requirement probably dates back to when PPS-Sieve used a very large sieve file. It no longer needs a sieve file, and, as you say, the actual disk requirements are rather small.
Although the change that removed the sieve file happened quite a few years ago, this is the first time I'm aware of this causing a problem -- probably because on "normal" computers, getting down to half a gigabyte of free space would cause all sorts of other problems. For a dedicated crunching machine with a minimal thumb drive disk, I could see how this might create problems.
I'll look into whether there's any not-so-obvious reason why the requirement shouldn't be lowered. Thanks for bringing it to my attention!
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
I'll look into whether there's any not-so-obvious reason why the requirement shouldn't be lowered. Thanks for bringing it to my attention!
After some discussion, we will make some changes as follows:
- The disk requirement for the TRP sieve will be lowered from 200 MB to 50 MB.
- The disk requirement for the SoB/PSP/ESP sieve will be lowered from 200 MB to 20 MB.
- The disk requirement for the PPS sieve will be lowered from 500 MB to 20 MB after the challenge is over.
When these changes are made, it will only affect new workunits generated after the change, so any work currently in the system will still have the older, larger limits.
____________
My lucky number is 75898524288+1
|
|
|
streamVolunteer moderator
Project administrator
Volunteer developer
Volunteer tester
Send message
Joined: 1 Mar 14
Posts: 1022
ID: 301928
Credit: 543,195,386
RAC: 2
|
For a dedicated crunching machine with a minimal thumb drive disk, I could see how this might create problems.
Yes, I'm running some PCs in diskless cruncher mode, booting them to TinyCoreLinux right from network server. In TinyCoreLinux everything is running on RAM disk, so sometimes only a 1-2Gb of virtual disk space is available. Thanks for fixing this!
|
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
|
After two days:
Challenge: Winter Solstice
App: (PPS-Sieve)
(As of 2014-12-20 23:09:42 UTC)
329245 tasks have been sent out. [CPU/GPU/anonymous_platform: 21164 (6%) / 303358 (92%) / 4723 (1%)]
Of those tasks that have been sent out:
9192 (3%) came back with some kind of an error. [3442 (1%) / 5250 (2%) / 500 (0%)]
221347 (67%) have returned a successful result. [3109 (1%) / 216036 (66%) / 2204 (1%)]
98706 (30%) are still in progress. [14613 (4%) / 82073 (25%) / 2019 (1%)]
Of the tasks that have been returned successfully:
52108 (24%) are pending validation. [563 (0%) / 51085 (23%) / 462 (0%)]
169222 (76%) have been successfully validated. [2546 (1%) / 164934 (75%) / 1742 (1%)]
11 (0%) were invalid. [0 (0%) / 11 (0%) / 0 (0%)]
6 (0%) are inconclusive. [0 (0%) / 6 (0%) / 0 (0%)]
____________
My lucky number is 75898524288+1 |
|
|
tngSend message
Joined: 29 Aug 10
Posts: 465
ID: 66603
Credit: 45,671,973,980
RAC: 23,463,053
                                                  
|
|
How many factors have been found?
____________
 |
|
|
|
|
|
I have been working for two days now tying to get my AMD R9 290X Graphics Card to run this or any ATI GPU Tasks. SDK installed both x86 and x64 running the current driver crossover is disabled.
I getting to the point of posting and the AMD Cards are just not supported on PRIMEGRID.
Any help as to they are supported or they are not supported.
OS Windows 7 x64. Thanks |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
I have been working for two days now tying to get my AMD R9 290X Graphics Card to run this or any ATI GPU Tasks. SDK installed both x86 and x64 running the current driver crossover is disabled.
I getting to the point of posting and the AMD Cards are just not supported on PRIMEGRID.
Any help as to they are supported or they are not supported.
OS Windows 7 x64. Thanks
There's a problem running the newer ATI GPUs and I believe you'll need to use app_info to get it to work correctly.
I *think* this will work, but you may get better advice from others; I don't have an ATI so I can't test it myself:
<app_info>
<app>
<name>pps_sr2sieve</name>
<user_friendly_name>Proth Prime Search (Sieve)</user_friendly_name>
</app>
<file_info>
<name>primegrid_tpsieve_1.40_windows_intelx86__atiPPSsieve.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>pps_sr2sieve</app_name>
<version_num>140</version_num>
<api_version>6.2.18</api_version>
<plan_class>atiPPSsieve</plan_class>
<file_ref>
<file_name>primegrid_tpsieve_1.40_windows_intelx86__atiPPSsieve.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
You'll need to put that content into C:\ProgramData\boinc\projects\www.primegrid.com\app_info.xml, as well as downloading http://www.primegrid.com/download/primegrid_tpsieve_1.40_windows_intelx86__atiPPSsieve.exe into the same directory. Then restart BOINC. Turning on app_info will abort any tasks on your computer, so don't try this if you have tasks in progress.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
How many factors have been found?
I'm not sure if there's an easy way to get that number. Currently, each task is returning about a dozen factors, but because the app doesn't use a sieve file, many of those factors are for candidates we've already removed. Jim might be able to give you a better answer, if there is one. There might not be one, however.
____________
My lucky number is 75898524288+1 |
|
|
|
|
I have been working for two days now tying to get my AMD R9 290X Graphics Card to run this or any ATI GPU Tasks. SDK installed both x86 and x64 running the current driver crossover is disabled.
I getting to the point of posting and the AMD Cards are just not supported on PRIMEGRID.
Any help as to they are supported or they are not supported.
OS Windows 7 x64. Thanks
There's a problem running the newer ATI GPUs and I believe you'll need to use app_info to get it to work correctly.
I *think* this will work, but you may get better advice from others; I don't have an ATI so I can't test it myself:
<app_info>
<app>
<name>pps_sr2sieve</name>
<user_friendly_name>Proth Prime Search (Sieve)</user_friendly_name>
</app>
<file_info>
<name>primegrid_tpsieve_1.40_windows_intelx86__atiPPSsieve.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>pps_sr2sieve</app_name>
<version_num>140</version_num>
<api_version>6.2.18</api_version>
<plan_class>atiPPSsieve</plan_class>
<file_ref>
<file_name>primegrid_tpsieve_1.40_windows_intelx86__atiPPSsieve.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
You'll need to put that content into C:\ProgramData\boinc\projects\www.primegrid.com\app_info.xml, as well as downloading http://www.primegrid.com/download/primegrid_tpsieve_1.40_windows_intelx86__atiPPSsieve.exe into the same directory. Then restart BOINC. Turning on app_info will abort any tasks on your computer, so don't try this if you have tasks in progress.
I will give this a try, Thanks.
Added, so for it is not working but thanks for this info. Sometimes it is the little things that really count.
I know now it can be done, I was looking at some users like 288larsson running CAL AMD Radeon HD 7870/7950/7970/R9 280X series (Tahiti) (3072MB) driver: 1.4.1848 link: http://www.primegrid.com/results.php?hostid=401915 |
|
|
288larssonVolunteer tester
Send message
Joined: 17 Apr 10
Posts: 136
ID: 58815
Credit: 5,385,664,942
RAC: 2,455,310
                              
|
|
Hi my app_info for R9 290X
<app_info>
<app>
<name>genefer</name>
<user_friendly_name>Genefer</user_friendly_name>
</app>
<file_info>
<name>primegrid_genefer_3_2_5_0_3.06_windows_intelx86__atiGFN.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>genefer</app_name>
<version_num>306</version_num>
<api_version>7.0.64</api_version>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<file_ref>
<file_name>primegrid_genefer_3_2_5_0_3.06_windows_intelx86__atiGFN.exe</file_name>
<main_program/>
</file_ref>
<platform>windows_intelx86</platform>
<coproc>
<type>ATI</type>
<count>1.000000</count>
</coproc>
</app_version>
<app>
<name>genefer_wr</name>
<user_friendly_name>Genefer (World Record)</user_friendly_name>
</app>
<file_info>
<name>primegrid_genefer_3_2_5_0_3.06_windows_intelx86__atiGFNWR.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>genefer_wr</app_name>
<version_num>306</version_num>
<api_version>7.0.64</api_version>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
<file_ref>
<file_name>primegrid_genefer_3_2_5_0_3.06_windows_intelx86__atiGFNWR.exe</file_name>
<main_program/>
</file_ref>
<platform>windows_intelx86</platform>
<coproc>
<type>ATI</type>
<count>1.000000</count>
</coproc>
</app_version>
<app>
<name>pps_sr2sieve</name>
<user_friendly_name>Proth Prime Search (Sieve)</user_friendly_name>
</app>
<file_info>
<name>primegrid_tpsieve_1.40_windows_intelx86__atiPPSsieve.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>pps_sr2sieve</app_name>
<version_num>140</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>1</avg_ncpus>
<max_ncpus>1</max_ncpus>
<flops>1.0e11</flops>
<coproc>
<type>ATI</type>
<count>0.5</count>
</coproc>
<cmdline></cmdline>
<file_ref>
<file_name>primegrid_tpsieve_1.40_windows_intelx86__atiPPSsieve.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>psp_sr2sieve</name>
<user_friendly_name>Sierpinski Problem ESP/PSP/SoB(Sieve)</user_friendly_name>
</app>
<file_info>
<name>primegrid_sr2sieve_wrapper_1.12_windows_x86_64.exe</name>
<executable/>
</file_info>
<file_info>
<name>primegrid_sr2sieve_1.8.10_windows_x86_64.exe.orig</name>
<executable/>
</file_info>
<app_version>
<app_name>psp_sr2sieve</app_name>
<version_num>112</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>1</avg_ncpus>
<max_ncpus>1</max_ncpus>
<file_ref>
<file_name>primegrid_sr2sieve_wrapper_1.12_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>primegrid_sr2sieve_1.8.10_windows_x86_64.exe.orig</file_name>
</file_ref>
</app_version>
<app>
<name>trp_sr2sieve</name>
<user_friendly_name>The Riesel Problem (Sieve)</user_friendly_name>
</app>
<file_info>
<name>primegrid_sr2sieve_wrapper_1.12_windows_x86_64.exe</name>
<executable/>
</file_info>
<file_info>
<name>primegrid_sr2sieve_1.8.10_windows_x86_64.exe.orig</name>
<executable/>
</file_info>
<app_version>
<app_name>trp_sr2sieve</app_name>
<version_num>112</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>1</avg_ncpus>
<max_ncpus>1</max_ncpus>
<file_ref>
<file_name>primegrid_sr2sieve_wrapper_1.12_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>primegrid_sr2sieve_1.8.10_windows_x86_64.exe.orig</file_name>
</file_ref>
</app_version>
</app_info> |
|
|
|
|
|
You are the Man, thank you very much!
Not working yet, giving up for the night. |
|
|
|
|
|
Has anyone else had the "15 seconds" run-time BOINC reporting anomaly yet?
It looks like it happened right around 1:06 UTC through 1:16 UTC 21 DEC.
I almost fell out of my chair when the 550Ti finished in 15 seconds! My Titan finished just a bit faster at 14 seconds.
http://www.primegrid.com/workunit.php?wuid=415587306
http://www.primegrid.com/workunit.php?wuid=415560798 |
|
|
RogerVolunteer developer
Volunteer tester
Send message
Joined: 27 Nov 11
Posts: 1138
ID: 120786
Credit: 268,668,824
RAC: 0
         
|
Has anyone else had the "15 seconds" run-time BOINC reporting anomaly yet?
It looks like it happened right around 1:06 UTC through 1:16 UTC 21 DEC.
I almost fell out of my chair when the 550Ti finished in 15 seconds! My Titan finished just a bit faster at 14 seconds.
http://www.primegrid.com/workunit.php?wuid=415587306
http://www.primegrid.com/workunit.php?wuid=415560798
I have seen this before with GFN GPU app. Your video driver has crashed. Just restart your PC. Results with crashed video card should be rejected by the server as invalid. |
|
|
JimBHonorary cruncher
Send message
Joined: 4 Aug 11
Posts: 918
ID: 107307
Credit: 977,945,376
RAC: 0
  
|
Has anyone else had the "15 seconds" run-time BOINC reporting anomaly yet?
It looks like it happened right around 1:06 UTC through 1:16 UTC 21 DEC.
I almost fell out of my chair when the 550Ti finished in 15 seconds! My Titan finished just a bit faster at 14 seconds.
http://www.primegrid.com/workunit.php?wuid=415587306
http://www.primegrid.com/workunit.php?wuid=415560798
If you click on the Task link for each of those two, they took a lot more time than the workunit page indicates. That's why they validated - both computers in each workunit found identical lists of factors. At the moment I'm not sure why there's a time discrepancy. |
|
|
JimBHonorary cruncher
Send message
Joined: 4 Aug 11
Posts: 918
ID: 107307
Credit: 977,945,376
RAC: 0
|
How many factors have been found?
As Mike said, that's not an easy question to answer precisely. The validator doesn't currently record the factor count for a given workunit - there's no good place in the workunit table to put it. When a workunit is validated, the list of factors is added to a master list. Once an hour, that master list is dumped to a textfile. Since that file is named according to the date and time it was dumped, I can tell you that so far on workunits returned during the challenge period there were 1,832,974 factors found. A number of those date from before the challenge start. At the p range we're at, a total of 26.5% of those (about 486K) will result in new removals from the 6 sieve files involved. Every removal represents an LLR test that doesn't need to be run because the candidate has been proven nonprime already.
The other 73.5% are factors for candidates already removed by earlier sieving. That's because PPS Sieving runs without a sieve file. It's both faster that way and users don't need to download 2.4GB of sieve files that change about once a month.
For the entire month of November there were 13,583,955 factors found. We're probably running at double the normal rate.
Finding the exact factor count after cleanup starts (separating challenge factors from non-challenge) won't be practical unless we write a new program to calculate that count. I'm interested in knowing myself, so I'll see if I can't write one. The program will be relatively simple, but running it will take quite a while. It'll have to total the factors in the upload file for each canonical challenge result.
Later edit: OK, wrote the program and currently we have 1,654,337 factors found during the challenge. |
|
|
|
|
|
With a little over 10 hours left on the clock, it's time for the usual end of challenge reminder :)
At the Conclusion of the Challenge
We would prefer users "moving on" to finish those tasks they have downloaded, if not then please ABORT the WU's instead of DETACHING, RESETTING, or PAUSING.
ABORTING WU's allows them to be recycled immediately; thus a much faster "clean up" to the end of a Challenge. DETACHING, RESETTING, and PAUSING WU's causes them to remain in limbo until they EXPIRE. Therefore, we must wait until WU's expire to send them out to be completed.
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
|
|
|
|
|
Has anyone else had the "15 seconds" run-time BOINC reporting anomaly yet?
It looks like it happened right around 1:06 UTC through 1:16 UTC 21 DEC.
I almost fell out of my chair when the 550Ti finished in 15 seconds! My Titan finished just a bit faster at 14 seconds.
http://www.primegrid.com/workunit.php?wuid=415587306
http://www.primegrid.com/workunit.php?wuid=415560798
I have a few as well. |
|
|
|
|
|
Great contest, looking forward to the next one. Thanks for all the work, that I am sure you have to do to run it efficiently. |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
|
Final Statistics:
Challenge: Winter Solstice
App: (PPS-Sieve)
(As of 2014-12-22 01:33:18 UTC)
465721 tasks have been sent out. [CPU/GPU/anonymous_platform: 26653 (6%) / 432211 (93%) / 6857 (1%)]
Of those tasks that have been sent out:
19688 (4%) came back with some kind of an error. [6710 (1%) / 12339 (3%) / 639 (0%)]
349705 (75%) have returned a successful result. [5878 (1%) / 339801 (73%) / 4026 (1%)]
78772 (17%) are still in progress. [10710 (2%) / 66140 (14%) / 1920 (0%)]
Of the tasks that have been returned successfully:
52065 (15%) are pending validation. [554 (0%) / 50958 (15%) / 553 (0%)]
297610 (85%) have been successfully validated. [5324 (2%) / 288813 (83%) / 3473 (1%)]
18 (0%) were invalid. [0 (0%) / 18 (0%) / 0 (0%)]
12 (0%) are inconclusive. [0 (0%) / 12 (0%) / 0 (0%)]
Great job everyone!
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
|
Cleanup:
21-Dec: Winter Solstice: 51977 tasks outstanding; 42579 affecting individual (297) scoring positions; 24751 affecting team (90) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Shoot.. I think I completely blanked on what the onscreen timer actually said, or something didn't update on my end, but somehow I thought it all began today.
One of my PCs was illegally liberated from my custody, and I spend the day scrambling to find notable information on it..
Quite notably, it seems it contacted PrimeGrid from an unknown IP several hours ago
If the TV crime dramas are any example, perhaps the river scum with my computer is still at that location.
Needless to say I was distracted. Maybe next time
I couldn't figure out why I wasn't on the boards. Well I can help with cleanup I suppose. |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
|
Cleanup:
21-Dec: Winter Solstice: 51977 tasks outstanding; 42579 affecting individual (297) scoring positions; 24751 affecting team (90) scoring positions.
22-Dec: Winter Solstice: 36385 tasks outstanding; 26953 affecting individual (293) scoring positions; 15350 affecting team (82) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
I'll look into whether there's any not-so-obvious reason why the requirement shouldn't be lowered. Thanks for bringing it to my attention!
After some discussion, we will make some changes as follows:
- The disk requirement for the TRP sieve will be lowered from 200 MB to 50 MB.
- The disk requirement for the SoB/PSP/ESP sieve will be lowered from 200 MB to 20 MB.
- The disk requirement for the PPS sieve will be lowered from 500 MB to 20 MB after the challenge is over.
When these changes are made, it will only affect new workunits generated after the change, so any work currently in the system will still have the older, larger limits.
The disk limit for PPS-sieve has now been lowered as described above. The TRP and Sierpinski sieve limits were lowered several days ago.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Hmm, ran out of PPS (Sieve) work and got the following:
<snip...>
12/23/2014 1:28:25 AM | PrimeGrid | Requesting new tasks for CPU and NVIDIA GPU
12/23/2014 1:28:26 AM | PrimeGrid | Scheduler request completed: got 0 new tasks
12/23/2014 1:28:26 AM | PrimeGrid | No tasks sent
12/23/2014 1:28:26 AM | PrimeGrid | No tasks are available for PPS (Sieve)
12/23/2014 1:28:26 AM | PrimeGrid | No tasks are available for the applications you have selected.
12/23/2014 1:28:26 AM | PrimeGrid | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
12/23/2014 1:44:36 AM | PrimeGrid | update requested by user
12/23/2014 1:44:36 AM | PrimeGrid | Sending scheduler request: Requested by user.
12/23/2014 1:44:36 AM | PrimeGrid | Requesting new tasks for CPU and NVIDIA GPU
12/23/2014 1:44:38 AM | PrimeGrid | Scheduler request completed: got 0 new tasks
12/23/2014 1:44:38 AM | PrimeGrid | No tasks sent
12/23/2014 1:44:38 AM | PrimeGrid | No tasks are available for PPS (Sieve)
12/23/2014 1:44:38 AM | PrimeGrid | No tasks are available for the applications you have selected.
12/23/2014 1:44:38 AM | PrimeGrid | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
12/23/2014 1:44:48 AM | PrimeGrid | Sending scheduler request: To fetch work.
12/23/2014 1:44:48 AM | PrimeGrid | Requesting new tasks for CPU and NVIDIA GPU
12/23/2014 1:44:49 AM | PrimeGrid | Scheduler request completed: got 0 new tasks
12/23/2014 1:44:49 AM | PrimeGrid | No tasks sent
12/23/2014 1:44:49 AM | PrimeGrid | No tasks are available for PPS (Sieve)
12/23/2014 1:44:49 AM | PrimeGrid | No tasks are available for the applications you have selected.
12/23/2014 1:44:49 AM | PrimeGrid | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
I am able to obtain work for other subprojects, just not PPS (Sieve) at this time. |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
|
Cleanup:
21-Dec: Winter Solstice: 51977 tasks outstanding; 42579 affecting individual (297) scoring positions; 24751 affecting team (90) scoring positions.
22-Dec: Winter Solstice: 36385 tasks outstanding; 26953 affecting individual (293) scoring positions; 15350 affecting team (82) scoring positions.
23-Dec: Winter Solstice: 17706 tasks outstanding; 11866 affecting individual (282) scoring positions; 5155 affecting team (63) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
Hmm, ran out of PPS (Sieve) work and got the following:
We seem to have some issues. We're looking into it.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Did anyone else encounter a problem with PPS Sieve wu's? For the first time, ever, it switched from Prime Grid to Seti on its own and had to manually "resume" Prime Grid. Also, one task suddenly at 95% done just stopped running and two others started to run. |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
Did anyone else encounter a problem with PPS Sieve wu's? For the first time, ever, it switched from Prime Grid to Seti on its own and had to manually "resume" Prime Grid. Also, one task suddenly at 95% done just stopped running and two others started to run.
We're having some issues with the BOINC server at the moment, and it looks like there was a temporary lack of some tasks. That would explain why you got no tasks.
It's likely that the reason your tasks stopped running was normal BOINC behavior when it downloaded tasks from SETI.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Thank you Michael. |
|
|
|
|
|
I am able to obtain PPS (Sieve) work again. Thanks. |
|
|
|
|
|
I wonder how to upload any of the available PPS work units that are still available from the Winter Solstice Challenge? |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
I wonder how to upload any of the available PPS work units that are still available from the Winter Solstice Challenge?
If it's available it will be sent to you when you request PPS-Sieve tasks. HOWEVER, in cleanups, while there may be lots of tasks that we're waiting for, there's usually little or no work available to be sent out -- the tasks we're waiting for are already out being crunched.
So there's usually nothing from the challenge to download.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
|
Cleanup:
21-Dec: Winter Solstice: 51977 tasks outstanding; 42579 affecting individual (297) scoring positions; 24751 affecting team (90) scoring positions.
22-Dec: Winter Solstice: 36385 tasks outstanding; 26953 affecting individual (293) scoring positions; 15350 affecting team (82) scoring positions.
23-Dec: Winter Solstice: 17706 tasks outstanding; 11866 affecting individual (282) scoring positions; 5155 affecting team (63) scoring positions.
24-Dec: Winter Solstice: 6428 tasks outstanding; 3571 affecting individual (233) scoring positions; 1001 affecting team (37) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Thanks again Michael. |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
|
Cleanup:
21-Dec: Winter Solstice: 51977 tasks outstanding; 42579 affecting individual (297) scoring positions; 24751 affecting team (90) scoring positions.
22-Dec: Winter Solstice: 36385 tasks outstanding; 26953 affecting individual (293) scoring positions; 15350 affecting team (82) scoring positions.
23-Dec: Winter Solstice: 17706 tasks outstanding; 11866 affecting individual (282) scoring positions; 5155 affecting team (63) scoring positions.
24-Dec: Winter Solstice: 6428 tasks outstanding; 3571 affecting individual (233) scoring positions; 1001 affecting team (37) scoring positions.
26-Dec: Winter Solstice: 815 tasks outstanding; 183 affecting individual (77) scoring positions; 28 affecting team (7) scoring positions.
27-Dec: Winter Solstice: 125 tasks outstanding; 29 affecting individual (22) scoring positions; 5 affecting team (4) scoring positions.
28-Dec: Winter Solstice: 62 tasks outstanding; 14 affecting individual (13) scoring positions; 4 affecting team (3) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
JimBHonorary cruncher
Send message
Joined: 4 Aug 11
Posts: 918
ID: 107307
Credit: 977,945,376
RAC: 0
|
JimB in Message 81525 - Posted: 21 Dec 2014 | 10:24:37 UTC wrote: For the entire month of November there were 13,583,955 factors found. We're probably running at double the normal rate.
Finding the exact factor count after cleanup starts (separating challenge factors from non-challenge) won't be practical unless we write a new program to calculate that count. I'm interested in knowing myself, so I'll see if I can't write one. The program will be relatively simple, but running it will take quite a while. It'll have to total the factors in the upload file for each canonical challenge result.
Later edit: OK, wrote the program and currently we have 1,654,337 factors found during the challenge.
As of 00:00:15 on 29 Dec 2014 there were 2,866,533 factors found. This number represents 2.1x the daily rate from November. The 60 or so remaining tasks won't significantly change either the total factor count or the rate at which they were found. |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13954
ID: 53948
Credit: 392,572,906
RAC: 180,256
|
|
Cleanup:
21-Dec: Winter Solstice: 51977 tasks outstanding; 42579 affecting individual (297) scoring positions; 24751 affecting team (90) scoring positions.
22-Dec: Winter Solstice: 36385 tasks outstanding; 26953 affecting individual (293) scoring positions; 15350 affecting team (82) scoring positions.
23-Dec: Winter Solstice: 17706 tasks outstanding; 11866 affecting individual (282) scoring positions; 5155 affecting team (63) scoring positions.
24-Dec: Winter Solstice: 6428 tasks outstanding; 3571 affecting individual (233) scoring positions; 1001 affecting team (37) scoring positions.
26-Dec: Winter Solstice: 815 tasks outstanding; 183 affecting individual (77) scoring positions; 28 affecting team (7) scoring positions.
27-Dec: Winter Solstice: 125 tasks outstanding; 29 affecting individual (22) scoring positions; 5 affecting team (4) scoring positions.
28-Dec: Winter Solstice: 62 tasks outstanding; 14 affecting individual (13) scoring positions; 4 affecting team (3) scoring positions.
31-Dec: Winter Solstice: 7 tasks outstanding; 0 affecting individual (0) scoring positions; 1 affecting team (1) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
With only hours to spare (for most of the world) the 2014 challenge series has been completed in 2014, with the finished clean up of this challenge.
Winners of this challenge are RaymondFO*, Ross* and zunwantan. Top teams for this challenge were Sicituradastra., SETI.Germany and Crunching@EVGA.
Looking at the 2014 overall leaderboard we can see 1077 people who managed to place for a scoring position in at least one challenge. In total 3878 unique people have participated in the challenges. The top 3 are RaymondFO*, zunwantan and tng*.
For teams there are exactly 300 participating teams who managed to place for a scoring position and a grand total of 509 teams that participated. The top 3 teams are Sicituradastra., Czech National Team and SETI.Germany
Thanks for the huge support and participation and we hope to see you next year too! :)
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
|
|
|
