| Author |
Message |
|---|
|
|
|
Welcome to the Low Country Festivities Challenge
Dutch people love a party and when the end of April draws near people start preparing for some of the biggest parties not related to religion. For the past 33 years we have celebrated Queens Day on April 30th. Not because our current queen Beatrix was actually born on that day, but because it was her mother's birthday and her own is on January 31st, which is not a very good date for having huge public parties outdoors in the northern hemisphere. Partying usually starts with "queens night", the night before. This year will be extra special, as the queen will abdicate and prince Willem-Alexander will be crowned king.
The next day, May 1st, Belgium celebrates International Workers' Day a.k.a. Labour Day.
May 3rd sees the sun rising on the international World Press Freedom Day, reminding us how important is to have freedom of speech and freedom of press.
Although strictly speaking not a festivity, May 4th sees the whole of the Netherlands commemorating all civilians and members of the armed forces of the Kingdom of the Netherlands who have died in wars or peacekeeping missions since the outbreak of World War II.
Following remembering all who have died in military service, liberation day is celebrated in the Netherlands on May 5th. This day celebrates the official liberation of the Netherlands on May 5th, 1945.
May 6th is a day with mixed emotions for some in the Netherlands. In 2002 a somewhat controversial politician was murdered on this day. On the plus side, several politicians were also born on this day in earlier years.
And finally May 7th sees the birthdays of several Dutch (former) prime ministers, making it the perfect day to round of this challenge.
Come join us to celebrate and commemorate all these events with an 8 day marathon on the Woodall Prime Search project. To participate in the Challenge, please select only the Woodall Prime Search (LLR) project in your PrimeGrid preferences section. The challenge will begin 29 April 2013 18:00 UTC and end 7 May 2013 18:00 UTC. Application builds are available for Linux , Windows and MacIntel 32 bit and 64 bit. CPU's with AVX capabilities will be significantly faster than the ones without, as this instruction set allows for more computing power.
ATTENTION: The primality program LLR is CPU intensive; so, it is vital to have a stable system with good cooling. It does not tolerate "even the slightest of errors." Please see this post for more details on how you can "stress test" your computer. WU's will take ~30 hours on fast/newer computers and 85+ hours on slower/older computers. If your computer is highly overclocked, please consider "stress testing" it. Sieving is an excellent alternative for computers that are not able to LLR. :)
Restricted airflow is one of the primary reasons for overheating. Take the time to monitor the fans and review the dust buildup. Please, please, please make sure your machines are up to the task.
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 29 April 2013 18:00 UTC and received BEFORE 7 May 2013 18:00 UTC will be considered for credit. We will use the same scoring method as for BOINC credits .
Therefore, each completed WU will earn a unique score based on its n value. The higher the n, the higher the score. This is different than BOINC cobblestones! A quorum of 2 is NOT needed to award Challenge score - i.e. no double checker. Therefore, each returned result will earn a Challenge score. Please note that if the result is eventually declared invalid, the score will be removed.
For details on how the score is calculated, please see this thread.
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 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, and 3752948 and composite for all other n less than 9108979.
It is conjectured that there are infinitely many such primes. Currently, PrimeGrid is testing for Woodall primes in the n=11M - n=12M level (M=mega, 10^6). The last 3 Woodall primes found by PrimeGrid are:
2013992*2^2013992−1 (Lasse Mejling Andersen): official announcement | decimal representation | Prime Pages Entry
2367906*2^2367906−1 (Stephen Kohlman): official announcement | decimal representation | Prime Pages Entry
3752948*2^3752948−1 (Matthew J. Thompson): official announcement | decimal representation | 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:(Edouard Lucas: 1842-1891, Derrick H. Lehmer: 1905-1991, Hans Riesel: born 1929)
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
|
|
|
|
|
|
I hoped someone would find time to rewrite the following as it has caused confusion in the past 2 challenges.
"At the Conclusion of the Challenge
We kindly ask users "moving on" to ABORT their 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. :)"
Could it be written clearer, I suggest
"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. :)"
Just an idea.
____________
Member team AUSTRALIA
My lucky number is 9291*2^1085585+1 |
|
|
|
|
|
Thanks DaveB, I've changed the text in the start post to what you suggested :)
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
|
|
|
|
|
|
Can we get please current Stats PDFs started since the first 3 challenges are complete?
____________
My lucky numbers are 121*2^4553899-1 and 3756801695685*2^666669±1
My movie https://vimeo.com/manage/videos/502242 |
|
|
|
|
Can we get please current Stats PDFs started since the first 3 challenges are complete?
Standings have been updated using my tool/site. See the link in my signature. Currently I don't have a pdf available, but you can always download the LaTeX code yourself and compile them to pdf. I'll look into auto-compiling the LaTeX code on my hoster somewhen in the near future, though I can't promise I can make it happen due to limited rights.
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
|
|
|
|
|
|
pitty, I can not take part, tried the app on V8-Xeon and it cooked my FBDIMMs upto 120grd Celsius...
good luck, don`t burn out your RAM
____________
|
|
|
|
|
|
Although I'm not really fond of royalty, it's always nice to have a day off and party.
So, happy Queens night/day from the Netherlands! |
|
|
 Sysadm@Nbg Volunteer moderator
Volunteer tester
Project scientist
Send message
Joined: 5 Feb 08
Posts: 1210
ID: 18646
Credit: 810,903,740
RAC: 251,782
                      
|
|
where can I get a yellow numberplate for my car for tomorrow??
alternative I will wear an orange t-shirt ...
:o)
Greetings from Germany
____________
Sysadm@Nbg
my current lucky number: 113856050^65536 + 1
PSA-PRPNet-Stats-URL: http://u-g-f.de/PRPNet/
 |
|
|
|
|
|
Almost all task for ComputerId=190315 take 1 second including Woodall Prime Search (LLR).
Is this normal behaviour? |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
                          
|
Almost all task for ComputerId=190315 take 1 second including Woodall Prime Search (LLR).
Is this normal behaviour?
Definitely not.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
I should clarify that by saying it's definitely not normal correct behavior.
It's fairly normal behavior for a computer that isn't set up properly. The programs aren't running correctly on there. If that was your computer, lots of people would offer suggestions as to what might be wrong and how to correct it. Since it's not your computer, just ignore it.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
OK this is probably a silly question, but if my CPU supports AVX will it be used automatically?
Using Win8 |
|
|
|
|
|
Yes, as long as you've not got any unusual app_config (etc...) files. The default BOINC applications use AVX whenever they can. Only your i5 will support it, so try to make the most of that. |
|
|
|
|
|
I know that the first challenge WUs wont be ready before, at least, a couple of hours (mine should finish in 6 or 7 hours from now).
But I've just noticed that, unlike team stats page, participant stats page is not being updated:
http://www.primegrid.com/challenge/2013_4/top_users.html
Last update: 2013 04 02 23:54:12
Rank Name Team Score
(Stats will be available shortly after the challenge begins.)
____________
676754^262144+1 is prime |
|
|
|
|
I know that the first challenge WUs wont be ready before, at least, a couple of hours (mine should finish in 6 or 7 hours from now).
But I've just noticed that, unlike team stats page, participant stats page is not being updated:
No WU's have been completed yet, so both should be blank. If you are seeing stats for the team page, try refreshing or clearing you browser cache.
At least the good news is that we are all coming tie first (or last?).
____________
Warped
  |
|
|
|
|
No WU's have been completed yet, so both should be blank. If you are seeing stats for the team page, try refreshing or clearing you browser cache.
At least the good news is that we are all coming tie first (or last?).
I'm seeing both blank, as no task has been returned yet. However, teams page shows this message:
Last update: 2013 04 30 10:30:03
Rank Name Score
So, the server is checking updates on teams, as it usually does during challenges.
Individual page, on the other hand, shows the message I've posted before.
____________
676754^262144+1 is prime |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
I know that the first challenge WUs wont be ready before, at least, a couple of hours (mine should finish in 6 or 7 hours from now).
But I've just noticed that, unlike team stats page, participant stats page is not being updated:
http://www.primegrid.com/challenge/2013_4/top_users.html
Last update: 2013 04 02 23:54:12
Rank Name Team Score
(Stats will be available shortly after the challenge begins.)
It's probably a browser cache problem on your end; hit F5 and you should see the correct up-to-date page. It will still be empty, however.
____________
My lucky number is 75898524288+1 |
|
|
|
|
It's probably a browser cache problem on your end; hit F5 and you should see the correct up-to-date page. It will still be empty, however.
Thanks Michael,
This is odd. I could swear your message was different a couple of hours ago...
But you're right. Participants page is being updated now and it is no longer empty, although a Wodall WU completed in less than 12 hours hours on a 1.8Ghz Atom cpu is very odd - so odd that it might even be a prime :)
____________
676754^262144+1 is prime |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
This is odd. I could swear your message was different a couple of hours ago...
For a couple of minutes, the message said "I'll look into it."
But only for a minute or two, because it didn't take long to see that both reports were up to date.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
AVX really rocks. The first challenge results took less than a day, whereas my Core2 will take about 3 days. The 32-bit AMD in my basement will probably take about 16 days -- it might miss the 14 day deadline, let alone the end of the 8 day challenge.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Yes, AVX is definitely great. Hopefully we are able to make significant progress during this challenge and its (what will probably take forever) clean up.
____________
 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Yes, AVX is definitely great. Hopefully we are able to make significant progress during this challenge and its (what will probably take forever) clean up.
Yes, it looks like we'll have two big challenge cleanups this year. I'm not sure if this will go faster or slower than the GFN cleanup. The deadline is shorter, but GPUs could do the GFN tasks a lot quicker than WOOs can be crunched on a CPU.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
The first post in this thread states, in part, "We will use the same scoring method as for BOINC credits". I did a trial run of some Woodall WUs just a couple of days ago, and those that have validated so far yielded roughly 4,100 BOINC credits (for example, this one). Yet from the challenge standings page for individuals, it appears each WU is granted about 6,200 challenge points. Is there something else that factors into the challenge scoring, or did I misunderstand something?
In fact, the next paragraph in the first post states in part, "This is different from BOINC cobblestones", so now I'm really confused. Thanks in advance.
--Gary |
|
|
HonzaVolunteer moderator
Volunteer tester
Project scientist
Send message
Joined: 15 Aug 05
Posts: 1931
ID: 352
Credit: 5,655,246,611
RAC: 5,286,722
                               
|
|
Gary, score used in challenges (and on PRPNet) has...different value comparing to BOINC cobblestone. 1 score point in not the same as BOINC cobblestone.
Scoring method is reffering formula used for calculating score - it uses digits lenght rather than BOINC's flawed benchmark/CPU runtime.
____________
My stats
Badge score: 1*1 + 5*1 + 8*3 + 9*11 + 10*1 + 11*1 + 12*3 = 186 |
|
|
|
|
|
Fair enough. As long as the formula is the same, except for any constants used as multipliers or divisors, we could multiply or divide everyone's challenge standing score by any amount and the overall rankings wouldn't change.
It's from the way I first read the announcement, I expected the challenge credit to equal the boinc credit. No worries. Just wanted to make sure something hadn't gone awry.
--Gary |
|
|
pschoeferVolunteer developer
Volunteer tester
Send message
Joined: 20 Sep 05
Posts: 673
ID: 845
Credit: 2,526,673,731
RAC: 1,416,224
              
|
Scoring method is reffering formula used for calculating score - it uses digits lenght rather than BOINC's flawed benchmark/CPU runtime.
Remember that the LLR credit system was changed a while ago. BOINC credits for LLR projects are now also based on the tested number. Since Challenge Scoring was also changed during the last challenge, there should be only some constant factor between BOINC credits and challenge score.
However, for future challenges I'd like to see that constant factor to be 1. Much less confusing, especially for newcomers. ;)
____________
  |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Scoring method is reffering formula used for calculating score - it uses digits lenght rather than BOINC's flawed benchmark/CPU runtime.
Remember that the LLR credit system was changed a while ago. BOINC credits for LLR projects are now also based on the tested number. Since Challenge Scoring was also changed during the last challenge, there should be only some constant factor between BOINC credits and challenge score.
100% correct. Scoring for LLR challenges is based directly on the size of the number, which differs from the credit formula only by omitting the constant used to normalize credit between different projects. Since challenges are only on a single project, there's no need to do that normalization.
However, for future challenges I'd like to see that constant factor to be 1. Much less confusing, especially for newcomers. ;)
I don't expect that to happen, but I do agree the wording in the introductory message could be better. For LLR, maybe something like "Scores are based upon the size of the number, which is similar, but not identical, to BOINC credits."
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Thanks Michael,
But I am interested what will be with those tasks.
All of them are marked as "Completed Successfully" for that machine.
Is this means that those tasks could be calculated incorrectly?
Thanks in advance. |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Thanks Michael,
But I am interested what will be with those tasks.
All of them are marked as "Completed Successfully" for that machine.
Is this means that those tasks could be calculated incorrectly?
Thanks in advance.
They are obviously not correct, and will be marked invalid once the validator processes them. That will happen once a second task is returned.
EDIT: If you look at his task list, you'll see that some of those tasks are marked invalid. This will eventually happen to all of them. As far as challenge score is concerned, what normally should happen is that those tasks would initially count as valid challenge points but would all eventually be removed as the tasks get marked invalid. HOWEVER, this is NOT an unusual occurrence since there are many hosts that are misconfigured in one way or another and are unable to crunch. Having so many invalid results in the challenge score, even temporarily, would make it difficult to tell what the actual player positions are, so there's special code in the challenge results processing that removes those results even before the validator officially marks them as invalid. Therefore, they don't affect challenge results at all.
____________
My lucky number is 75898524288+1 |
|
|
|
|
All of them are marked as "Completed Successfully" for that machine.
That is a BOINC term which means it communicated with the server correctly, not that anything is valid. Some of the BOINC terms are a little misleading but because BOINC is ported in many languages they used some generic terms so they would convert more fluently. These terms have been discussed since the BOINC program was created.
____________
My lucky numbers are 121*2^4553899-1 and 3756801695685*2^666669±1
My movie https://vimeo.com/manage/videos/502242 |
|
|
|
|
|
Judging from the subproject status page, it looks like this challenge may have advanced the leading edge by up to 1M.
____________
|
|
|
|
|
|
The end is nigh!
With about 9 hours left to crunch we would like to request the following
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. :)
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
|
|
|
|
|
|
Once the challenge is over, can someone produce the stats on how many WUs were completed, and how far the leading edge for the project was advanced during the challenge?
Also, I think the buffer should be lowered from 5000 back to 200 just to increase the odds of getting challenge WUs during the (probably long) clean up.
____________
|
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Once the challenge is over, can someone produce the stats on how many WUs were completed, and how far the leading edge for the project was advanced during the challenge?
I was planning on doing exactly that. :)
Also, I think the buffer should be lowered from 5000 back to 200 just to increase the odds of getting challenge WUs during the (probably long) clean up.
The buffer IS 200. That's down from 500, where it was for most of the challenge.
Remember, however, that's the minimum size for the queue. When it drops below that number, the system creates new work to fill up the queue. That's not the only source of new tasks, however. When a task errors out (bad result, invalidated result, timed out, etc.), the system automatically creates a new task to replace it. It seems as if a large number of tasks were replaced, possibly a bunch of those 3 second faulty results being removed by the validator, or lots of excess tasks being aborted.
As for "the odds of getting challenge results during the cleanup", things are different than they used to be. Challenge cleanup tasks now get priority over new tasks and the system will send them out ahead of other tasks. We don't have to shrink the queue to make sure the cleanup tasks go out in a timely fashion.
That being said, these are big jobs with long 14 day deadlines and the cleanup will likely take a month or more.
____________
My lucky number is 75898524288+1 |
|
|
|
|
As for "the odds of getting challenge results during the cleanup", things are different than they used to be. Challenge cleanup tasks now get priority over new tasks and the system will send them out ahead of other tasks. We don't have to shrink the queue to make sure the cleanup tasks go out in a timely fashion.
I had forgotten that this change was made. I am glad that this is the case, it will certainly help to speed up the clean up.
____________
|
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Once the challenge is over, can someone produce the stats on how many WUs were completed, and how far the leading edge for the project was advanced during the challenge?
I was planning on doing exactly that. :)
The challenge isn't quite over yet (there's about two hours to go), but here's some slightly early statistics:
54935 Woodall tasks have been sent out. Of those tasks that were sent out, 17500 have been successfully returned. Of those, 6834 have been validated, 10382 are pending validation, 24 were invalidated, and 265 are inconclusive and are awaiting a third result. (I suspect most of the invalidated and inconclusive results are from those 3-second faulty results.)
The leading edge prior to the challenge start was 11442872 and the leading edge is now 11957846, so we've increased the leading edge by about half a million. Another way of looking at this is that the size of the numbers being tested has grown from 3.44 million digits to 3.60 million digits. Also, the time to crunch each number has increased by about 9% during the challenge, as has the credit for each task.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Once the challenge is over, can someone produce the stats on how many WUs were completed, and how far the leading edge for the project was advanced during the challenge?
I was planning on doing exactly that. :)
The challenge isn't quite over yet (there's about two hours to go), but here's some slightly early statistics:
54935 Woodall tasks have been sent out. Of those tasks that were sent out, 17500 have been successfully returned. Of those, 6834 have been validated, 10382 are pending validation, 24 were invalidated, and 265 are inconclusive and are awaiting a third result. (I suspect most of the invalidated and inconclusive results are from those 3-second faulty results.)
The leading edge prior to the challenge start was 11442872 and the leading edge is now 11957846, so we've increased the leading edge by about half a million. Another way of looking at this is that the size of the numbers being tested has grown from 3.44 million digits to 3.60 million digits. Also, the time to crunch each number has increased by about 9% during the challenge, as has the credit for each task.
The challenge is now over! Update to the numbers released earlier:
55183 Woodall tasks have been sent out. Of those tasks that were sent out, 17640 have been successfully returned. Of those, 6993 have been validated, 10356 are pending validation, 25 were invalidated, and 267 are inconclusive and are awaiting a third result.
The leading edge is unchanged from the earlier numbers.
Here's the cleanup status:
May 7th: 10635 tasks outstanding; 9325 in individual (200) scoring positions; 9092 in team (98) scoring positions.
Note that this probably includes a lot of faulty 3 second results. I'll likely exclude those from the statistics at some point since there's no need to wait for those to inevitably fail validation.
EDIT: And, with the faulty 3 second results excluded, here's the cleanup status:
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
|
|
EDIT: And, with the faulty 3 second results excluded, here's the cleanup status:
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
Those 3 second errors could be a problem. I have 5 Woodalls pending, with 4 caused by 3 second errors. My wife has 2 pending both due to 3 second errors. This could make for a long clean up.
I was going to go for gold in 321 but I will stay on woodall until the next challenge and go for gold on that instead, except for 2 weeks needed on one slower system finishing of the last pair of SOB needed for gold.
Do we need some sort of 'post challenge' contest to help speed up the clean up?
____________
Member team AUSTRALIA
My lucky number is 9291*2^1085585+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
          
|
|
5 of the 8 tasks I completed during the challenge are still pending, and have been for many many hours. One has been pending for over a day. Is this normal? Or should I be worried?
 |
|
|
|
|
5 of the 8 tasks I completed during the challenge are still pending, and have been for many many hours. One has been pending for over a day. Is this normal? Or should I be worried?
That is quite normal, in fact it is pretty good to have 3 done already. The wait could be a few days for all of the wingmen to finish, a few weeks when they fail, note I say 'when' not 'if'.
You should try SOB where a wait of several months is normal!!!!
edit :- you can help others in the same situation by keeping on Woodall to get rid of the outstanding work from the challenge.
____________
Member team AUSTRALIA
My lucky number is 9291*2^1085585+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
|
Crud. What does inconclusive mean? Do I not get credit for those?
EDIT: I read something higher up in the thread about this. What is a 3-second thing?
All of these took ~33hrs to ~37hrs each, if the 3-second thing means the task took 3 seconds to complete.. |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Crud. What does inconclusive mean? Do I not get credit for those?
When a task is computed, it's sent out to two computers. When the results from both computers are returned, they should match. If they match, the results are declared valid.
If they don't match, they're inconclusive, and a third copy of the task is sent out to a third computer. When it is returned, if it matches one of the two original results, then the new result and the matching result are declared valid and the result that doesn't match (which would be due to some sort of error) is declared invalid. (In the unlikely event the third result doesn't match either of the original two results, then the process is repeated until eventually two results do match.)
If your results are good, you'll eventually get credit.
____________
My lucky number is 75898524288+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
Crud. What does inconclusive mean? Do I not get credit for those?
When a task is computed, it's sent out to two computers. When the results from both computers are returned, they should match. If they match, the results are declared valid.
If they don't match, they're inconclusive, and a third copy of the task is sent out to a third computer. When it is returned, if it matches one of the two original results, then the new result and the matching result are declared valid and the result that doesn't match (which would be due to some sort of error) is declared invalid. (In the unlikely event the third result doesn't match either of the original two results, then the process is repeated until eventually two results do match.)
If your results are good, you'll eventually get credit.
If they are turned out as wrong will I still get credit? |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
EDIT: I read something higher up in the thread about this. What is a 3-second thing?
All of these took ~33hrs to ~37hrs each, if the 3-second thing means the task took 3 seconds to complete..
There was ONE bad computer out there which was configured badly and could not run the app. It was reporting a successful result after only 3 seconds. Of course, the results are not valid, but at 3 seconds per task it returned thousands of these erroneous results.
This will slow down the challenge cleanup somewhat, but other than that it's not really a problem. The BOINC system is pretty adept at dealing with most problems of this nature.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Crud. What does inconclusive mean? Do I not get credit for those?
When a task is computed, it's sent out to two computers. When the results from both computers are returned, they should match. If they match, the results are declared valid.
If they don't match, they're inconclusive, and a third copy of the task is sent out to a third computer. When it is returned, if it matches one of the two original results, then the new result and the matching result are declared valid and the result that doesn't match (which would be due to some sort of error) is declared invalid. (In the unlikely event the third result doesn't match either of the original two results, then the process is repeated until eventually two results do match.)
If your results are good, you'll eventually get credit.
If they are turned out as wrong will I still get credit?
No, credit is only granted for valid results. If your computer is returning bad results, it's a computation error and you should probably try to figure out why.
You have no errors in your task list right now, so I wouldn't be particularly worried.
____________
My lucky number is 75898524288+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
|
Ok. so does that mean someone else's computer had bad results? |
|
|
|
|
There was ONE bad computer out there which was configured badly ....
My results show at least 3 users with at least 4 computers doing it. At least one of them is an experienced operator so some types of computers are currently having a problem, I hope they notice soon and sort it out or they will be wasting their time doing work.
____________
Member team AUSTRALIA
My lucky number is 9291*2^1085585+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Ok. so does that mean someone else's computer had bad results?
Yes, it means at least one of the two computers returned a bad result. In theory, it's possible both computers returned bad results, but statistically that's very unlikely.
____________
My lucky number is 75898524288+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
Ok. so does that mean someone else's computer had bad results?
Yes, it means at least one of the two computers returned a bad result. In theory, it's possible both computers returned bad results, but statistically that's very unlikely.
Ok. So I just have to wait for a 3rd computer to validate my results, or their results? And I have to wait for that to get my credit IF mine is validated? |
|
|
|
|
Ok. so does that mean someone else's computer had bad results?
Maybe. Until it is checked you will not know if it was you or the other person who got it wrong. Everyone gets errors occasionally, my worst was when my neighbour was drilling concrete and the inteference corrupted four jobs at once.
Overclocking and overheating can also cause errors. That is why I don't overclock, a 10% speed gain is not worth it if you error more than 1 in 9 WU, but some are skillful enough to overclock successfully.
As Micheal says your history is very good so you have a good chance of getting the credit for the work. If not then you have changed from those who have not errored yet to one of the majority who have had an error. Join the club!!!
____________
Member team AUSTRALIA
My lucky number is 9291*2^1085585+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Ok. so does that mean someone else's computer had bad results?
Yes, it means at least one of the two computers returned a bad result. In theory, it's possible both computers returned bad results, but statistically that's very unlikely.
Ok. So I just have to wait for a 3rd computer to validate my results, or their results? And I have to wait for that to get my credit IF mine is validated?
Yes.
____________
My lucky number is 75898524288+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
Ok. so does that mean someone else's computer had bad results?
Yes, it means at least one of the two computers returned a bad result. In theory, it's possible both computers returned bad results, but statistically that's very unlikely.
Ok. So I just have to wait for a 3rd computer to validate my results, or their results? And I have to wait for that to get my credit IF mine is validated?
Yes.
Thanks for your help :) |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
There's an unusually large number of cleanup tasks queued up, waiting to be sent out to a host. There's currently 1152 cleanup tasks in the queue. (That's about 10 CPU-core-years worth of processing on an "average" computer.) This is likely due to the faulty host with the thousands of bad results. Normally, there's very few cleanup tasks queued up on the server and most of them are out being crunched.
So if you can spare the processing power, we do need your help with this challenge's cleanup.
____________
My lucky number is 75898524288+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
There's an unusually large number of cleanup tasks queued up, waiting to be sent out to a host. There's currently 1152 cleanup tasks in the queue. (That's about 10 CPU-core-years worth of processing on an "average" computer.) This is likely due to the faulty host with the thousands of bad results. Normally, there's very few cleanup tasks queued up on the server and most of them are out being crunched.
So if you can spare the processing power, we do need your help with this challenge's cleanup.
Did you find who the fault host was? |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
There's an unusually large number of cleanup tasks queued up, waiting to be sent out to a host. There's currently 1152 cleanup tasks in the queue. (That's about 10 CPU-core-years worth of processing on an "average" computer.) This is likely due to the faulty host with the thousands of bad results. Normally, there's very few cleanup tasks queued up on the server and most of them are out being crunched.
So if you can spare the processing power, we do need your help with this challenge's cleanup.
Did you find who the fault host was?
The faulty host was pointed out to us by on of you, actually. So, technically, the answer is "no", since we didn't find out; you guys did.
____________
My lucky number is 75898524288+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
The faulty host was pointed out to us by on of you, actually. So, technically, the answer is "no", since we didn't find out; you guys did.
Okay then. Was it mainly one machine with hundereds of faulty tasks? Or was it many faulty hosts. And what were the causes of the fault. Or if you don't know just say that you don't know :P |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
The faulty host was pointed out to us by on of you, actually. So, technically, the answer is "no", since we didn't find out; you guys did.
Okay then. Was it mainly one machine with hundereds of faulty tasks? Or was it many faulty hosts. And what were the causes of the fault. Or if you don't know just say that you don't know :P
http://www.primegrid.com/forum_thread.php?id=4991
____________
My lucky number is 75898524288+1 |
|
|
|
|
....
http://www.primegrid.com/forum_thread.php?id=4991
We changed to the newest server code recently, but are still running the older (but almost new) validator because of the enormous number and complexity of changes required. Once I've got the validator updated, hosts like this that always fail will be restricted as to how many new jobs per day they can get. That number will never fall to zero though, as otherwise the host wouldn't get any work after being repaired.
The new badges were a very nice surprise. The validator fix will be even nicer.
My apologies for cross quoting.
... and now back to your regularly scheduled clean up... :) |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
There's an unusually large number of cleanup tasks queued up, waiting to be sent out to a host. There's currently 1105 cleanup tasks in the queue. (That's about 10 CPU-core-years worth of processing on an "average" computer.)
So if you can spare the processing power, we do need your help with this challenge's cleanup.
There's a notice on PrimeGrid's home page that indicates if there's cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Hi
Can can somebody explain me how can I participate to the Challenge (WOO-LLR) cleanup work IS ???
Thanks in advance
____________
|
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Hi
Can can somebody explain me how can I participate to the Challenge (WOO-LLR) cleanup work IS ???
Thanks in advance
Select Woodall tasks in the PrimegGrid preferences page.
The more people that process those tasks, the quicker the cleanup will go and the sooner the challenge results will be finalized.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Thx very easy... and logical....
____________
|
|
|
|
|
|
I have fired up 8x E5-2670's to run some cleanup units. They will be on WOO until all the cleanup work has been done! |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
I have fired up 8x E5-2670's to run some cleanup units. They will be on WOO until all the cleanup work has been done!
Thanks!
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
There's an unusually large number of cleanup tasks queued up, waiting to be sent out to a host. There's currently 631 cleanup tasks in the queue. (That's about 5 CPU-core-years worth of processing on an "average" computer.)
So if you can spare the processing power, we do need your help with this challenge's cleanup.
There's a notice on PrimeGrid's home page that indicates if there's cleanup work available.
We're making progress: at the end of the challenge there were about 1100 cleanup tasks waiting to be sent out. Thanks, and keep up the good work!
____________
My lucky number is 75898524288+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
|
So, looks like we're getting about 1 year of "CPU-core work" done per day. So should be done within another week :). At least that's what it looks like :P
EDIT: Also, were any large primes found during this competition on woodall LLR? |
|
|
|
|
|
After the challenges it is taking longer every year to do the clean up. I suggested some sort of post challenge challenge to get it done faster, that would not be very good but I have been thinking a bit more.
With some challenges taking months to clean up (GFN did and Woodall is heading that way) we may need to encourage more to stay on the tasks for the clean up. I am not sure if there are BOINC rules to stop it but one way would be to give a bonus for clean up jobs. I would suggest that making clean up tasks have a 50% bonus credit would work.
This may not be practical from the software point of view but it is an idea I would like considered.
Any comments?
____________
Member team AUSTRALIA
My lucky number is 9291*2^1085585+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
After the challenges it is taking longer every year to do the clean up. I suggested some sort of post challenge challenge to get it done faster, that would not be very good but I have been thinking a bit more.
With some challenges taking months to clean up (GFN did and Woodall is heading that way) we may need to encourage more to stay on the tasks for the clean up. I am not sure if there are BOINC rules to stop it but one way would be to give a bonus for clean up jobs. I would suggest that making clean up tasks have a 50% bonus credit would work.
This may not be practical from the software point of view but it is an idea I would like considered.
Any comments?
This challenge is a bit of an anomaly -- for most challenges, even ones that take months for the cleanup, mostly you're waiting for computers to return work. There's usually very few cleanup tasks sitting on the server waiting to be sent out. The long delay is often due to a few of those cleanup tasks timing out, which takes weeks in the case of these big tasks. That's what takes so long.
This challenge is a little different, as we started with about 1100 tasks sitting in the queue waiting to be sent out. But already, after 4 days, that's been reduced by half. So that's not that large a contributing factor to the overall cleanup time. The "critical path" will be the handful of tasks that are never returned and need to be sent out again after 14 days -- especially when that happens several times to the same workunit.
Therefore, giving a bonus to cleanup work won't actually do much to change the length of the cleanup.
We've already made changes to the challenges in order to better handle the long cleanup phases. In particular, we're doing fewer challenges like this, and we're only doing them early in the year so that they don't delay the final year-end challenge standings. If you remember, a few years ago we ran a PSP challenge in September, and the cleanup wasn't done until January or February.
____________
My lucky number is 75898524288+1 |
|
|
|
|
Therefore, giving a bonus to cleanup work won't actually do much to change the length of the cleanup.
OK so long as there is no problem.
____________
Member team AUSTRALIA
My lucky number is 9291*2^1085585+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
There was an unusually large number of cleanup tasks queued up at the end of the challeng, waiting to be sent out to a host. There's currently 328 cleanup tasks in the queue. (That's about 2.5 CPU-core-years worth of processing on an "average" computer.)
So if you can spare the processing power, we do need your help with this challenge's cleanup.
There's a notice on PrimeGrid's home page that indicates if there's cleanup work available.
We're making progress: at the end of the challenge there were about 1100 cleanup tasks waiting to be sent out. Thanks, and keep up the good work!
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
I have another idea - changing the value of initial replication from 2 to 3 for tasks from the particular subproject during a challenge.
____________
|
|
|
|
|
I have another idea - changing the value of initial replication from 2 to 3 for tasks from the particular subproject during a challenge.
That sounds a good idea, nice lateral thinking. I think it should be considered at least for the longer task challenges.
____________
Member team AUSTRALIA
My lucky number is 9291*2^1085585+1 |
|
|
|
|
|
I've run at least as many cleanup tasks as I did during the challenge. (Doing my part)
____________
"Apollo was astonished, Dionysus thought me mad. But they heard my story further and they wondered and were sad."
 |
|
|
|
|
I've run at least as many cleanup tasks as I did during the challenge. (Doing my part)
I'm trying to do the same and I have found an interesting fact. I stopped the GPUs for the challenge and restarted them for the clean up expecting little effect. This is the case with PPS SV on the ATI (about 10% slower) but with GFN on the CUDA I find the Woodalls running about half speed. Since it claims to be using 0.496 CPU that must be right, I thought it was just BOINC estimates being out.
This will need a bit of thought and planning for what jobs share the CUDA system in future.
I am still getting the clean up jobs out, Ruby on GFN can wait.
____________
Member team AUSTRALIA
My lucky number is 9291*2^1085585+1 |
|
|
|
|
|
Hi, I'll be happy to take some more wu, my concern right now is I have a wu 32+ hours in and about 48 hours left but it has like a 13 hours expiration. Should I abort this, or can I complete it?
Thanks,
Phil
____________
My lucky number is still 13. |
|
|
JimBHonorary cruncher
Send message
Joined: 4 Aug 11
Posts: 918
ID: 107307
Credit: 977,945,376
RAC: 3,009
   
|
Hi, I'll be happy to take some more wu, my concern right now is I have a wu 32+ hours in and about 48 hours left but it has like a 13 hours expiration. Should I abort this, or can I complete it?
Thanks,
Phil
By all means continue it. No Woodall workunits will be deleted until after the challenge stats are finalized. As long as the workunit still exists, you'll get credit (assuming of course your result matches that of another task). |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
There was an unusually large number of cleanup tasks queued up at the end of the challenge, waiting to be sent out to a host. There's currently 106 cleanup tasks in the queue. (That's about 10 CPU-core-months worth of processing on an "average" computer.)
So if you can spare the processing power, we do need your help with this challenge's cleanup.
There's a notice on PrimeGrid's home page that indicates if there's cleanup work available.
We're making progress: at the end of the challenge there were about 1100 cleanup tasks waiting to be sent out. Thanks, and keep up the good work!
____________
My lucky number is 75898524288+1 |
|
|
Scott BrownVolunteer moderator
Project administrator
Volunteer tester
Project scientist
Send message
Joined: 17 Oct 05
Posts: 2324
ID: 1178
Credit: 14,805,126,100
RAC: 22,303,779
                                        
|
|
Had some heating issues at the end of the challenge, so I pulled off to some less demanding work until I cleaned out some of the dust bunnies. Got a few of those done (still working on others), so a few cores back on the clean-up. :)
|
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
|
If this isn't done by the time I get my new heatsink I'll Go in full force |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
If this isn't done by the time I get my new heatsink I'll Go in full force
Your heatsink is coming the day after tomorrow, right? This cleanup will take weeks, if not months.
____________
My lucky number is 75898524288+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
|
Alrighty then. Will switch my prefs to Woodall and start when i get my new heatsink. I've had my RAC at 4000+, but now without running tasks it is down :( |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
There was an unusually large number of cleanup tasks queued up at the end of the challenge, waiting to be sent out to a host. There's currently 237 cleanup tasks in the queue.
So if you can spare the processing power, we do need your help with this challenge's cleanup.
There's a notice on PrimeGrid's home page that indicates if there's cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
|
|
CLEANUP UPDATE
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
Are you sure these figures are correct?
From 13 to 14th of May: -392 tasks outstanding; -301 tasks in individual; -980 tasks in team?? |
|
|
|
|
Are you sure these figures are correct?
That fits to about the average run time per unit, so on the 7th-9th a bunch were sent back into the wild and they finished. I bet the numbers are just fine.
____________
My lucky numbers are 121*2^4553899-1 and 3756801695685*2^666669±1
My movie https://vimeo.com/manage/videos/502242 |
|
|
|
|
Are you sure these figures are correct?
That fits to about the average run time per unit, so on the 7th-9th a bunch were sent back into the wild and they finished. I bet the numbers are just fine.
I meant the 980 results returned for the team positions, while only 392 results have been returned in total? |
|
|
|
|
I meant the 980 results returned for the team positions, while only 392 results have been returned in total?
Yes, if the unit is out on 3-4 different computers waiting to validate, each team is included in that count. If a bunch of those were the 3 second ones which became invalid, then valid for 2 other teams.
____________
My lucky numbers are 121*2^4553899-1 and 3756801695685*2^666669±1
My movie https://vimeo.com/manage/videos/502242 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
CLEANUP UPDATE
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
Are you sure these figures are correct?
From 13 to 14th of May: -392 tasks outstanding; -301 tasks in individual; -980 tasks in team??
That does NOT mean 980 results came back. It means 980 results no longer are significant as far as the standings are concerned. There's a difference.
Consider this situation:
Every task is worth 100 credits. Team A is 100,000 credits in front of team B. Team A has 1000 tasks that are not still pending, waiting for validation. Those tasks are worth 100,000 credits, so theoretically if ALL of them failed validation, team A could drop down into a tie with team B. So those 1000 tasks still affect validation.
Now assume JUST ONE of those 1000 tasks gets validated. Now there's only 999 tasks outstanding, representing 99,900 credits -- which is less than the difference between team A and team B. ALL of those tasks are no longer important to the team standings, so the total number of tasks that are important dropped by 1000, even though only a single task got validated.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
There was an unusually large number of cleanup tasks queued up at the end of the challenge, waiting to be sent out to a host. There's currently 23 cleanup tasks in the queue. That's down from ~1100, so the vast majority of the tasks required for finalizing the cleanup art being processed. There's still over 5000 tasks queued up for processing that don't affect challenge standings, however.
There's a notice on PrimeGrid's home page that indicates if there's cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
darkclownVolunteer tester
Send message
Joined: 3 Oct 06
Posts: 323
ID: 3605
Credit: 1,213,759,293
RAC: 359,660
        
|
|
The cleanup has inspired me to take Wn to Silver badge level. Curious if I'll get there before the cleanup is complete. I'm at 45k/100k needed, and the tasks are taking ~88h to complete.
____________
My lucky #: 60133106^131072+1 (GFN 17-mega) |
|
|
|
|
|
I'm not sure why I was sent this work unit as a Woodall cleanup task. There's no way it could have affected anyone's challenge score, once host 211480 timed out. Unless, I suppose, if host 361114's "validate error" status (one of the "3 second invalid tasks) wasn't assigned until after I returned mine. That would be a shame as it seems clear that the unit could be marked invalid basically immediately after being returned, due to the unreasonable duration. I thought the "validate error" status was being done differently as compared to "marked as invalid" when two reasonable-length tasks return differing residue. Perhaps I am mistaken.
I have a few similar now-pending Woodall units (e.g. this one) that appear to have been similarly needlessly sent, and now will remain pending until after the cleanup is done, it seems.
--Gary |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
I'm not sure why I was sent this work unit as a Woodall cleanup task. There's no way it could have affected anyone's challenge score, once host 211480 timed out. Unless, I suppose, if host 361114's "validate error" status (one of the "3 second invalid tasks) wasn't assigned until after I returned mine. That would be a shame as it seems clear that the unit could be marked invalid basically immediately after being returned, due to the unreasonable duration. I thought the "validate error" status was being done differently as compared to "marked as invalid" when two reasonable-length tasks return differing residue. Perhaps I am mistaken.
I have a few similar now-pending Woodall units (e.g. this one) that appear to have been similarly needlessly sent, and now will remain pending until after the cleanup is done, it seems.
--Gary
The entire scheduler system, taken as a whole, is an extremely complex algorithm with a lot of different parts operating on different schedules. While it's convenient to think of it in terms of simple rules, such as "cleanup tasks first", it's more of a suggestion than a rule because there's a lot of rules that take precedence.
That being said, however, that's not what happened here. You were sent that task because it was erroneously classified as a cleanup task. This is a new problem that we had not seen before, and it was corrected about 45 minutes after the challenge ended. There was a large queue of cleanup tasks to work through and undoubtedly some of those that were not really necessary for the cleanup didn't get sent out until a few days ago when you got that task.
EDIT: You won't have to wait until after the whole cleanup is done. Most of the time spent during the challenge cleanup is waiting for host computers to return the work they're processing. While that's going on, other work is being sent out. The initial backlog of cleanup work has been reduced to a manageable level and I suspect normal work will be mixed in shortly, and most likely already has been for the last day or two.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Thanks for the attention and explanation. I shall continue to run Woodall clean-up for a while, as I am (slowly) closing in on a new badge level. However there will be a brief interruption tomorrow as I have a PRPnet challenge to attend to :-)
Cheers,
--Gary |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
May 17th: 2739 tasks outstanding; 1945 in individual (195) scoring positions; 1333 in team (82) scoring positions.
May 18th: 2399 tasks outstanding; 1638 in individual (192) scoring positions; 1003 in team (76) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
|
Crunchin' some woodalls! :D |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
May 17th: 2739 tasks outstanding; 1945 in individual (195) scoring positions; 1333 in team (82) scoring positions.
May 18th: 2399 tasks outstanding; 1638 in individual (192) scoring positions; 1003 in team (76) scoring positions.
May 19th: 2124 tasks outstanding; 1357 in individual (187) scoring positions; 885 in team (75) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's currently cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
|
I saw another one of my woodalls from during the challenge was invalidated... (2 total now). This is probably because of my overheating (mentioned earlier)?
|
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
I saw another one of my woodalls from during the challenge was invalidated... (2 total now). This is probably because of my overheating (mentioned earlier)?
It's very likely.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
May 17th: 2739 tasks outstanding; 1945 in individual (195) scoring positions; 1333 in team (82) scoring positions.
May 18th: 2399 tasks outstanding; 1638 in individual (192) scoring positions; 1003 in team (76) scoring positions.
May 19th: 2124 tasks outstanding; 1357 in individual (187) scoring positions; 885 in team (75) scoring positions.
May 20th: 1879 tasks outstanding; 1127 in individual (182) scoring positions; 679 in team (70) scoring positions.
May 21st: 1657 tasks outstanding; 975 in individual (179) scoring positions; 562 in team (69) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's currently cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
TylerProject administrator
Volunteer tester
Send message
Joined: 4 Dec 12
Posts: 1077
ID: 183129
Credit: 1,365,637,185
RAC: 43
|
|
The nice thing about doing cleanup tasks: You get credit right away :D.
____________
275*2^3585539+1 is prime!!! (1079358 digits)
 Proud member of Aggie the Pew
 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
May 17th: 2739 tasks outstanding; 1945 in individual (195) scoring positions; 1333 in team (82) scoring positions.
May 18th: 2399 tasks outstanding; 1638 in individual (192) scoring positions; 1003 in team (76) scoring positions.
May 19th: 2124 tasks outstanding; 1357 in individual (187) scoring positions; 885 in team (75) scoring positions.
May 20th: 1879 tasks outstanding; 1127 in individual (182) scoring positions; 679 in team (70) scoring positions.
May 21st: 1657 tasks outstanding; 975 in individual (179) scoring positions; 562 in team (69) scoring positions.
May 22nd: 1473 tasks outstanding; 858 in individual (175) scoring positions; 462 in team (65) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's currently cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
|
|
CLEANUP UPDATE
May 22nd: 1473 tasks outstanding; 858 in individual (175) scoring positions; 462 in team (65) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's currently cleanup work available.
I noticed there are over 5.6K Woodall ready to send. With less than 1500 outstanding and many of them probably being crunched right now, the standard queue being about 100, is there really over 4K non challenge outstanding tasks to be sent?
____________
My lucky numbers are 121*2^4553899-1 and 3756801695685*2^666669±1
My movie https://vimeo.com/manage/videos/502242 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
I noticed there are over 5.6K Woodall ready to send. With less than 1500 outstanding and many of them probably being crunched right now, the standard queue being about 100, is there really over 4K non challenge outstanding tasks to be sent?
Yes. 5605, to be exact.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
I noticed there are over 5.6K Woodall ready to send. With less than 1500 outstanding and many of them probably being crunched right now, the standard queue being about 100, is there really over 4K non challenge outstanding tasks to be sent?
Yes. 5605, to be exact.
I could have, and should have, given you a more comprehensive response that also included the number of cleanup tasks waiting to be sent out. As of right now:
Non-cleanup tasks waiting to be sent out: 5574
Cleanup tasks for WUs that do NOT affect scoring positions: 0
Cleanup tasks for WUs that DO affect scoring positions: 1
It's only the last number that actually helps with the cleanup progress.
____________
My lucky number is 75898524288+1 |
|
|
|
|
I could have, and should have, given you a more comprehensive response.
Very nice and thanks.
Of the 13 I have pending I see I have 3 that I returned during the challenge still to be completed. The other 10 I have are ones I returned after the challenge (some started after the challenge but were not challenge tasks). So it will be a while before I get my Ruby in Woodall.
____________
My lucky numbers are 121*2^4553899-1 and 3756801695685*2^666669±1
My movie https://vimeo.com/manage/videos/502242 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
May 17th: 2739 tasks outstanding; 1945 in individual (195) scoring positions; 1333 in team (82) scoring positions.
May 18th: 2399 tasks outstanding; 1638 in individual (192) scoring positions; 1003 in team (76) scoring positions.
May 19th: 2124 tasks outstanding; 1357 in individual (187) scoring positions; 885 in team (75) scoring positions.
May 20th: 1879 tasks outstanding; 1127 in individual (182) scoring positions; 679 in team (70) scoring positions.
May 21st: 1657 tasks outstanding; 975 in individual (179) scoring positions; 562 in team (69) scoring positions.
May 22nd: 1473 tasks outstanding; 858 in individual (175) scoring positions; 462 in team (65) scoring positions.
May 23rd: 1246 tasks outstanding; 733 in individual (170) scoring positions; 368 in team (62) scoring positions.
May 24th: 1040 tasks outstanding; 590 in individual (159) scoring positions; 309 in team (57) scoring positions.
May 25th: 910 tasks outstanding; 492 in individual (150) scoring positions; 262 in team (51) scoring positions.
May 26th: 775 tasks outstanding; 417 in individual (144) scoring positions; 186 in team (43) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's currently cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
I finish about 50 Woodall Cleanup-WUs today :D |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
I finish about 50 Woodall Cleanup-WUs today :D
Great. Thank you!
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
May 17th: 2739 tasks outstanding; 1945 in individual (195) scoring positions; 1333 in team (82) scoring positions.
May 18th: 2399 tasks outstanding; 1638 in individual (192) scoring positions; 1003 in team (76) scoring positions.
May 19th: 2124 tasks outstanding; 1357 in individual (187) scoring positions; 885 in team (75) scoring positions.
May 20th: 1879 tasks outstanding; 1127 in individual (182) scoring positions; 679 in team (70) scoring positions.
May 21st: 1657 tasks outstanding; 975 in individual (179) scoring positions; 562 in team (69) scoring positions.
May 22nd: 1473 tasks outstanding; 858 in individual (175) scoring positions; 462 in team (65) scoring positions.
May 23rd: 1246 tasks outstanding; 733 in individual (170) scoring positions; 368 in team (62) scoring positions.
May 24th: 1040 tasks outstanding; 590 in individual (159) scoring positions; 309 in team (57) scoring positions.
May 25th: 910 tasks outstanding; 492 in individual (150) scoring positions; 262 in team (51) scoring positions.
May 26th: 775 tasks outstanding; 417 in individual (144) scoring positions; 186 in team (43) scoring positions.
May 27th: 669 tasks outstanding; 367 in individual (140) scoring positions; 149 in team (40) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's currently cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
For those who prefer a visual. Thanks MG for making this easy to import to Excel.
--Gary |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
I suspect that a logarithmic scale might be better, especially as we get close to the end.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
May 17th: 2739 tasks outstanding; 1945 in individual (195) scoring positions; 1333 in team (82) scoring positions.
May 18th: 2399 tasks outstanding; 1638 in individual (192) scoring positions; 1003 in team (76) scoring positions.
May 19th: 2124 tasks outstanding; 1357 in individual (187) scoring positions; 885 in team (75) scoring positions.
May 20th: 1879 tasks outstanding; 1127 in individual (182) scoring positions; 679 in team (70) scoring positions.
May 21st: 1657 tasks outstanding; 975 in individual (179) scoring positions; 562 in team (69) scoring positions.
May 22nd: 1473 tasks outstanding; 858 in individual (175) scoring positions; 462 in team (65) scoring positions.
May 23rd: 1246 tasks outstanding; 733 in individual (170) scoring positions; 368 in team (62) scoring positions.
May 24th: 1040 tasks outstanding; 590 in individual (159) scoring positions; 309 in team (57) scoring positions.
May 25th: 910 tasks outstanding; 492 in individual (150) scoring positions; 262 in team (51) scoring positions.
May 26th: 775 tasks outstanding; 417 in individual (144) scoring positions; 186 in team (43) scoring positions.
May 27th: 669 tasks outstanding; 367 in individual (140) scoring positions; 149 in team (40) scoring positions.
May 28th: 603 tasks outstanding; 319 in individual (130) scoring positions; 132 in team (35) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's currently cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Is this normal?
334160806
It was long time ago when this task was last sent out.
____________
 |
|
|
|
|
Is this normal?
334160806
It was long time ago when this task was last sent out.
Yes, during a challenge cleanup the challenge tasks take priority. If we were under normal conditions it "normally" would not take that long but might, depending on how many tasks are waiting to send to wingpeople.
You should try some other projects that do not prioritize their tasks. I had some waiting over 60 days before resent because it went to the back of a large queue.
____________
My lucky numbers are 121*2^4553899-1 and 3756801695685*2^666669±1
My movie https://vimeo.com/manage/videos/502242 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
Is this normal?
334160806
It was long time ago when this task was last sent out.
Normal? Not really. The aftermath of this challenge isn't the way things usually work. But there's nothing wrong. Work is going out as it is supposed to. It will just take some time.
This s primarily due to the unusually large number of unsent tasks left over from the challenge. That, in turn, is largely due to the 3 second bug causing a lot of tasks to be sent out a second time.
At this point, the amount of unsent tasks with elevated priority is insignificant.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
May 17th: 2739 tasks outstanding; 1945 in individual (195) scoring positions; 1333 in team (82) scoring positions.
May 18th: 2399 tasks outstanding; 1638 in individual (192) scoring positions; 1003 in team (76) scoring positions.
May 19th: 2124 tasks outstanding; 1357 in individual (187) scoring positions; 885 in team (75) scoring positions.
May 20th: 1879 tasks outstanding; 1127 in individual (182) scoring positions; 679 in team (70) scoring positions.
May 21st: 1657 tasks outstanding; 975 in individual (179) scoring positions; 562 in team (69) scoring positions.
May 22nd: 1473 tasks outstanding; 858 in individual (175) scoring positions; 462 in team (65) scoring positions.
May 23rd: 1246 tasks outstanding; 733 in individual (170) scoring positions; 368 in team (62) scoring positions.
May 24th: 1040 tasks outstanding; 590 in individual (159) scoring positions; 309 in team (57) scoring positions.
May 25th: 910 tasks outstanding; 492 in individual (150) scoring positions; 262 in team (51) scoring positions.
May 26th: 775 tasks outstanding; 417 in individual (144) scoring positions; 186 in team (43) scoring positions.
May 27th: 669 tasks outstanding; 367 in individual (140) scoring positions; 149 in team (40) scoring positions.
May 28th: 603 tasks outstanding; 319 in individual (130) scoring positions; 132 in team (35) scoring positions.
May 29th: 533 tasks outstanding; 281 in individual (123) scoring positions; 108 in team (30) scoring positions.
May 30th: 472 tasks outstanding; 250 in individual (112) scoring positions; 85 in team (24) scoring positions
May 31st: 413 tasks outstanding; 196 in individual (99) scoring positions; 75 in team (22) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's currently cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
My last challenge-wu was valid - thx Mr Scott Brown. ^^ |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
May 17th: 2739 tasks outstanding; 1945 in individual (195) scoring positions; 1333 in team (82) scoring positions.
May 18th: 2399 tasks outstanding; 1638 in individual (192) scoring positions; 1003 in team (76) scoring positions.
May 19th: 2124 tasks outstanding; 1357 in individual (187) scoring positions; 885 in team (75) scoring positions.
May 20th: 1879 tasks outstanding; 1127 in individual (182) scoring positions; 679 in team (70) scoring positions.
May 21st: 1657 tasks outstanding; 975 in individual (179) scoring positions; 562 in team (69) scoring positions.
May 22nd: 1473 tasks outstanding; 858 in individual (175) scoring positions; 462 in team (65) scoring positions.
May 23rd: 1246 tasks outstanding; 733 in individual (170) scoring positions; 368 in team (62) scoring positions.
May 24th: 1040 tasks outstanding; 590 in individual (159) scoring positions; 309 in team (57) scoring positions.
May 25th: 910 tasks outstanding; 492 in individual (150) scoring positions; 262 in team (51) scoring positions.
May 26th: 775 tasks outstanding; 417 in individual (144) scoring positions; 186 in team (43) scoring positions.
May 27th: 669 tasks outstanding; 367 in individual (140) scoring positions; 149 in team (40) scoring positions.
May 28th: 603 tasks outstanding; 319 in individual (130) scoring positions; 132 in team (35) scoring positions.
May 29th: 533 tasks outstanding; 281 in individual (123) scoring positions; 108 in team (30) scoring positions.
May 30th: 472 tasks outstanding; 250 in individual (112) scoring positions; 85 in team (24) scoring positions
May 31st: 413 tasks outstanding; 196 in individual (99) scoring positions; 75 in team (22) scoring positions.
June 1st: 371 tasks outstanding; 172 in individual (87) scoring positions; 65 in team (20) scoring positions.
June 2nd: 328 tasks outstanding; 147 in individual (77) scoring positions; 59 in team (20) scoring positions.
June 3rd: 273 tasks outstanding; 117 in individual (68) scoring positions; 49 in team (18) scoring positions.
June 4th: 246 tasks outstanding; 102 in individual (61) scoring positions; 46 in team (17) scoring positions.
June 5th: 223 tasks outstanding; 85 in individual (57) scoring positions; 39 in team (15) scoring positions.
June 6th: 196 tasks outstanding; 74 in individual (50) scoring positions; 34 in team (12) scoring positions.
June 7th: 159 tasks outstanding; 59 in individual (42) scoring positions; 19 in team (8) scoring positions.
June 8th: 142 tasks outstanding; 53 in individual (40) scoring positions; 13 in team (6) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's currently cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
No more clean up work listed on the home page at last.
As they say on X Files "The answer is out there somewhere"
____________
Member team AUSTRALIA
My lucky number is 9291*2^1085585+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
No more clean up work listed on the home page at last.
As they say on X Files "The answer is out there somewhere"
The cleanup flag has been on and off intermittently for many days now. There was only a significant amount of cleanup work for about the first week after the challenge (and even that was unusual.)
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
May 17th: 2739 tasks outstanding; 1945 in individual (195) scoring positions; 1333 in team (82) scoring positions.
May 18th: 2399 tasks outstanding; 1638 in individual (192) scoring positions; 1003 in team (76) scoring positions.
May 19th: 2124 tasks outstanding; 1357 in individual (187) scoring positions; 885 in team (75) scoring positions.
May 20th: 1879 tasks outstanding; 1127 in individual (182) scoring positions; 679 in team (70) scoring positions.
May 21st: 1657 tasks outstanding; 975 in individual (179) scoring positions; 562 in team (69) scoring positions.
May 22nd: 1473 tasks outstanding; 858 in individual (175) scoring positions; 462 in team (65) scoring positions.
May 23rd: 1246 tasks outstanding; 733 in individual (170) scoring positions; 368 in team (62) scoring positions.
May 24th: 1040 tasks outstanding; 590 in individual (159) scoring positions; 309 in team (57) scoring positions.
May 25th: 910 tasks outstanding; 492 in individual (150) scoring positions; 262 in team (51) scoring positions.
May 26th: 775 tasks outstanding; 417 in individual (144) scoring positions; 186 in team (43) scoring positions.
May 27th: 669 tasks outstanding; 367 in individual (140) scoring positions; 149 in team (40) scoring positions.
May 28th: 603 tasks outstanding; 319 in individual (130) scoring positions; 132 in team (35) scoring positions.
May 29th: 533 tasks outstanding; 281 in individual (123) scoring positions; 108 in team (30) scoring positions.
May 30th: 472 tasks outstanding; 250 in individual (112) scoring positions; 85 in team (24) scoring positions
May 31st: 413 tasks outstanding; 196 in individual (99) scoring positions; 75 in team (22) scoring positions.
June 1st: 371 tasks outstanding; 172 in individual (87) scoring positions; 65 in team (20) scoring positions.
June 2nd: 328 tasks outstanding; 147 in individual (77) scoring positions; 59 in team (20) scoring positions.
June 3rd: 273 tasks outstanding; 117 in individual (68) scoring positions; 49 in team (18) scoring positions.
June 4th: 246 tasks outstanding; 102 in individual (61) scoring positions; 46 in team (17) scoring positions.
June 5th: 223 tasks outstanding; 85 in individual (57) scoring positions; 39 in team (15) scoring positions.
June 6th: 196 tasks outstanding; 74 in individual (50) scoring positions; 34 in team (12) scoring positions.
June 7th: 159 tasks outstanding; 59 in individual (42) scoring positions; 19 in team (8) scoring positions.
June 8th: 142 tasks outstanding; 53 in individual (40) scoring positions; 13 in team (6) scoring positions.
June 9th: 129 tasks outstanding; 49 in individual (37) scoring positions; 12 in team (6) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's currently cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
I've taken on a few more WU's to help with the cleanup.
Although a potential prime is out of the question, at least they will help towards a silver badge!
____________
Warped
|
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
|
CLEANUP UPDATE
May 7th: 6682 tasks outstanding; 5398 in individual (200) scoring positions; 5161 in team (98) scoring positions.
May 8th: 6271 tasks outstanding; 5070 in individual (200) scoring positions; 4850 in team (97) scoring positions.
May 9th: 5771 tasks outstanding; 4653 in individual (200) scoring positions; 4462 in team (96) scoring positions.
May 10th: 5284 tasks outstanding; 4262 in individual (200) scoring positions; 4074 in team (96) scoring positions.
May 11th: 4927 tasks outstanding; 3963 in individual (200) scoring positions; 3566 in team (95) scoring positions.
May 12th: 4510 tasks outstanding; 3613 in individual (200) scoring positions; 3261 in team (95) scoring positions.
May 13th: 4039 tasks outstanding; 3048 in individual (199) scoring positions; 2909 in team (94) scoring positions.
May 14th: 3647 tasks outstanding; 2747 in individual (199) scoring positions; 1929 in team (87) scoring positions.
May 15th: 3327 tasks outstanding; 2504 in individual (198) scoring positions; 1704 in team (84) scoring positions.
May 16th: 3014 tasks outstanding; 2170 in individual (195) scoring positions; 1530 in team (84) scoring positions.
May 17th: 2739 tasks outstanding; 1945 in individual (195) scoring positions; 1333 in team (82) scoring positions.
May 18th: 2399 tasks outstanding; 1638 in individual (192) scoring positions; 1003 in team (76) scoring positions.
May 19th: 2124 tasks outstanding; 1357 in individual (187) scoring positions; 885 in team (75) scoring positions.
May 20th: 1879 tasks outstanding; 1127 in individual (182) scoring positions; 679 in team (70) scoring positions.
May 21st: 1657 tasks outstanding; 975 in individual (179) scoring positions; 562 in team (69) scoring positions.
May 22nd: 1473 tasks outstanding; 858 in individual (175) scoring positions; 462 in team (65) scoring positions.
May 23rd: 1246 tasks outstanding; 733 in individual (170) scoring positions; 368 in team (62) scoring positions.
May 24th: 1040 tasks outstanding; 590 in individual (159) scoring positions; 309 in team (57) scoring positions.
May 25th: 910 tasks outstanding; 492 in individual (150) scoring positions; 262 in team (51) scoring positions.
May 26th: 775 tasks outstanding; 417 in individual (144) scoring positions; 186 in team (43) scoring positions.
May 27th: 669 tasks outstanding; 367 in individual (140) scoring positions; 149 in team (40) scoring positions.
May 28th: 603 tasks outstanding; 319 in individual (130) scoring positions; 132 in team (35) scoring positions.
May 29th: 533 tasks outstanding; 281 in individual (123) scoring positions; 108 in team (30) scoring positions.
May 30th: 472 tasks outstanding; 250 in individual (112) scoring positions; 85 in team (24) scoring positions
May 31st: 413 tasks outstanding; 196 in individual (99) scoring positions; 75 in team (22) scoring positions.
June 1st: 371 tasks outstanding; 172 in individual (87) scoring positions; 65 in team (20) scoring positions.
June 2nd: 328 tasks outstanding; 147 in individual (77) scoring positions; 59 in team (20) scoring positions.
June 3rd: 273 tasks outstanding; 117 in individual (68) scoring positions; 49 in team (18) scoring positions.
June 4th: 246 tasks outstanding; 102 in individual (61) scoring positions; 46 in team (17) scoring positions.
June 5th: 223 tasks outstanding; 85 in individual (57) scoring positions; 39 in team (15) scoring positions.
June 6th: 196 tasks outstanding; 74 in individual (50) scoring positions; 34 in team (12) scoring positions.
June 7th: 159 tasks outstanding; 59 in individual (42) scoring positions; 19 in team (8) scoring positions.
June 8th: 142 tasks outstanding; 53 in individual (40) scoring positions; 13 in team (6) scoring positions.
June 9th: 129 tasks outstanding; 49 in individual (37) scoring positions; 12 in team (6) scoring positions.
June 10th: 115 tasks outstanding; 42 in individual (32) scoring positions; 8 in team (5) scoring positions.
There's a notice on PrimeGrid's home page that indicates if there's currently cleanup work available.
____________
My lucky number is 75898524288+1 |
|
|
darkclownVolunteer tester
Send message
Joined: 3 Oct 06
Posts: 323
ID: 3605
Credit: 1,213,759,293
RAC: 359,660
|
|
I've got 8 on one of my machines (4 in progress.) Are we seeing a mix of cleanup & non-cleanup WUs at this time?
____________
My lucky #: 60133106^131072+1 (GFN 17-mega) |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13787
ID: 53948
Credit: 345,142,938
RAC: 21,797
|
I've got 8 on one of my machines (4 in progress.) Are we seeing a mix of cleanup & non-cleanup WUs at this time?
If you consider 0.1% cleanup tasks and 99.9% non-cleanup tasks to be a mix, then the answer is yes.
Except for the first week after the challenge, the vast majority of tasks that went out have not been part of the cleanup. For the most part, during any cleanup, almost all of the cleanup tasks at any instant in time are out in the field being processed. There's usually only a handful waiting to be sent out, if any.
____________
My lucky number is 75898524288+1 |
|
|
darkclownVolunteer tester
Send message
Joined: 3 Oct 06
Posts: 323
ID: 3605
Credit: 1,213,759,293
RAC: 359,660
|
