| Author |
Message |
|---|
|
|
|
Welcome to the Cullen Birthday Challenge
The startdate is the 149th birthday of James Cullen, had he still been alive. With this being a a prime birthday, it seems like a very appropriate occasion to celebrate by hosting a challenge. And what projects are better suited in that case than our Cullen and Woodall (Cullen primes of the second kind) projects?
The person we're celebrating is Father James Cullen, born on 19 April 1867 in Ireland. He was a student of Mathematics and Theology.
To participate in the Challenge, please select either the Cullen (LLR) or Woodall (LLR) project in your PrimeGrid preferences section. The challenge will begin April 19th 2016, 18:00:00 UTC and end April 28th 2016, 18:00:00 UTC. Application builds are available for Linux , Windows and MacIntel 32 bit and 64 bit. Intel CPU's with AVX and FMA 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 about 1 to 2 days on very fast/newer computers and 4+ days 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 April 19th 2016, 18:00:00 UTC and received BEFORE April 28th 2016, 18:00:00 UTC will be considered for credit.
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.
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:
Cullen Primes
Cullen numbers are a special kind Proth number. They were first studied by James Cullen in 1905 and are of the form n * 2^n + 1.
As of August 2009, the largest known Cullen prime is 6679881 * 2^6679881 + 1. It is a megaprime with 2,010,852 digits and was discovered by a PrimeGrid participant from Japan.
A Cullen number Cn is divisible by p = 2n − 1 if p is a prime number of the form 8k - 3; furthermore, it follows from Fermat's little theorem that if p is an odd prime, then p divides Cm(k) for each m(k) = (2k − k) (p − 1) − k (for k > 0). It has also been shown that the prime number p divides C(p + 1) / 2 when the Jacobi symbol (2 | p) is −1, and that p divides C(3p − 1) / 2 when the Jacobi symbol (2 | p) is +1.
It is unknown whether there exists a prime number p such that Cp is also prime.
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)
Best of Luck!!!
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
|
|
|
|
|
|
Thanks Charley!
The team CRUNCHERS SANS FRONTIERES will participate in this challenge! :)
____________
Founder of CRUNCHERS SANS FRONTIERES
www.crunchersansfrontieres.org
CSF lucky number 22872882^65536+1 |
|
|
|
|
|
First time for me to participate, but I'm looking forward to join!
Kind regards |
|
|
|
|
(Edouard Lucas: 1842-1891, Derrick H. Lehmer: 1905-1991, Hans Riesel: born 1929)
As mentioned before in other threads, you can write: Hans Riesel: 1929-2014
/JeppeSN |
|
|
|
|
|
Might be too long tasks for my laptops to handle, but cool nonetheless! |
|
|
|
|
|
Countdown for us with different timezones
http://www.timeanddate.com/countdown/generic?msg=Cullen%20Birthday%20Challenge&p0=1440&year=2016&month=4&day=19&hour=18&min=0&sec=0 |
|
|
 Michael Goetz Volunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
                               
|
|
The challenge starts in a little less than one hour. Good luck everyone!
____________
My lucky number is 75898524288+1 |
|
|
mackerelVolunteer tester
Send message
Joined: 2 Oct 08
Posts: 2639
ID: 29980
Credit: 568,393,769
RAC: 3,323
                       
|
|
Crunchers are now idle waiting for the start. Is this the quiet before the storm for the server? At least the WUs are long so the load shouldn't last long... |
|
|
mackerelVolunteer tester
Send message
Joined: 2 Oct 08
Posts: 2639
ID: 29980
Credit: 568,393,769
RAC: 3,323
|
|
GO! GO! GO! |
|
|
|
|
|
The uptick in the number of Cullen and Woodall tasks in progress at the start of the challenge is quite amazing. I hope that we are able to find a prime in one of these two projects for the first time in a long time.
____________
 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
|
Congratulations to Van Zimmerman and team Aggie The Pew for returning the first completed tasks in this challenge. So far, three Cullen tasks have been returned after just under 20 hours.
If there was ever any doubt about how fast the Skylake CPUs are, that should settle it.
____________
My lucky number is 75898524288+1 |
|
|
mackerelVolunteer tester
Send message
Joined: 2 Oct 08
Posts: 2639
ID: 29980
Credit: 568,393,769
RAC: 3,323
|
|
Now that's quick... my fast box, which was first to return in a previous challenge late last year, is estimating around 24h mark. That's a Skylake running at "only" 4.2 GHz. Ideal CPU clock scaling would suggest 5+ GHz but somehow I don't think that was the approach taken.
Edit: refined clock speed based on elapsed time taken |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
Now that's quick... my fast box, which was first to return in a previous challenge late last year, is estimating around 24h mark. That's a Skylake running at "only" 4.2 GHz. Ideal CPU clock scaling would suggest 5+ GHz but somehow I don't think that was the approach taken.
Edit: refined clock speed based on elapsed time taken
I would guess overclocking the memory is more important that increasing the clock on the CPU. Especially on large WU's like these, the CPU is going to be waiting on the memory.
____________
My lucky number is 75898524288+1 |
|
|
RafaelVolunteer tester
Send message
Joined: 22 Oct 14
Posts: 909
ID: 370496
Credit: 528,656,660
RAC: 383,837
              
|
Now that's quick... my fast box, which was first to return in a previous challenge late last year, is estimating around 24h mark. That's a Skylake running at "only" 4.2 GHz. Ideal CPU clock scaling would suggest 5+ GHz but somehow I don't think that was the approach taken.
Edit: refined clock speed based on elapsed time taken
I would guess overclocking the memory is more important that increasing the clock on the CPU. Especially on large WU's like these, the CPU is going to be waiting on the memory.
Funningly enough, I get errors when OCing my RAM with WOO WUs, even though other projects (and even SoB) do perfectly fine... |
|
|
|
|
|
That machine isn't really overclocked, it stays at a turbo freq of 4.4ghz. Memory is gskill ddr4-3200, running at spec speed.
It does throw sporadic errors, like one every 2-3 weeks on the larger llr tasks.
Edit: my i5-6500 should be weighing in around the 25.25-25.5 hour mark. |
|
|
RafaelVolunteer tester
Send message
Joined: 22 Oct 14
Posts: 909
ID: 370496
Credit: 528,656,660
RAC: 383,837
|
That machine isn't really overclocked, it stays at a turbo freq of 4.4ghz. Memory is gskill ddr4-3200, running at spec speed.
It does throw sporadic errors, like one every 2-3 weeks on the larger llr tasks.
Exactly. RAM OC (which your's is) > CPU OC when running large LLR. |
|
|
Ken_g6Volunteer developer
Send message
Joined: 4 Jul 06
Posts: 937
ID: 3110
Credit: 258,244,148
RAC: 79,904
                
|
|
I'm amazed that I'm #2 with my i3-6100, which isn't overclocked although the DDR4 is at 2666.
____________
|
|
|
|
|
I'm amazed that I'm #2 with my i3-6100, which isn't overclocked although the DDR4 is at 2666.
Assuming you are running dual channel ram and one unit per core, I suspect you aren't getting as much contention for memory bandwidth as the i5s/i7s running 3-4 tasks on dual channel ram. |
|
|
mackerelVolunteer tester
Send message
Joined: 2 Oct 08
Posts: 2639
ID: 29980
Credit: 568,393,769
RAC: 3,323
|
|
If I were to buy a lot of PCs for LLR, I think the i3-6100 is one of the best ways to go. You could argue it depending on the configuration but they're pretty fast without needing overclock, and even standard ram is enough to feed only two cores. Since everything is stock, it helps keep the cost low too. No expensive ram or mobos needed. My faster quad which just got units in is somewhat hindered by the ram even with dual channel 3200. In theory an overclocked Haswell-E could do well here.
Oh, with those 4 units I just dropped I'll have temporary 1st position thank you! I expect the rapid drop in position soon as slower boxes start returning.
Occasional errors obviously aren't a good thing. I had that early on and it only went away when I replaced the ram with totally different model. |
|
|
|
|
|
I have the wrong memory on the wrong system, LOL
The dual AMD Interlagos 12 core each server has 256gb of DDR3.
Need to get a new mobo with an Intel E5-2600 V3 cpu and then I can install the 256gb memory.
____________
 |
|
|
mackerelVolunteer tester
Send message
Joined: 2 Oct 08
Posts: 2639
ID: 29980
Credit: 568,393,769
RAC: 3,323
|
|
It's ram bandwidth where it counts, not quantity, although with higher density ram there does seem to be some benefit with having 2 rank per channel compared to single. I haven't had anything to test what happens above 2 rank per channel which I presume will be the case in heavily loaded server configurations. |
|
|
|
|
|
Agreed, but AMD cpus don't work great with primegrid.
____________
|
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
|
Here's the 1.75-day status report...of course, there's more to say about tasks being sent out than tasks being returned. Most computers haven't finished their first set of tasks yet, but there have still been over 300 tasks returned so far.
Challenge: Cullen Birthday
App: 3 (WOO-LLR)
(As of 2016-04-21 11:54:18 UTC)
3500 tasks have been sent out. [CPU/GPU/anonymous_platform: 3474 (99%) / 0 (0%) / 26 (1%)]
Of those tasks that have been sent out:
396 (11%) came back with some kind of an error. [396 (11%) / 0 (0%) / 0 (0%)]
99 (3%) have returned a successful result. [93 (3%) / 0 (0%) / 6 (0%)]
3005 (86%) are still in progress. [2985 (85%) / 0 (0%) / 20 (1%)]
Of the tasks that have been returned successfully:
91 (92%) are pending validation. [85 (86%) / 0 (0%) / 6 (6%)]
8 (8%) have been successfully validated. [8 (8%) / 0 (0%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=15163742. The leading edge was at n=15110732 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.35% as much as it had prior to the challenge!
Challenge: Cullen Birthday
App: 4 (CUL-LLR)
(As of 2016-04-21 11:54:18 UTC)
5577 tasks have been sent out. [CPU/GPU/anonymous_platform: 5553 (100%) / 0 (0%) / 24 (0%)]
Of those tasks that have been sent out:
312 (6%) came back with some kind of an error. [312 (6%) / 0 (0%) / 0 (0%)]
239 (4%) have returned a successful result. [226 (4%) / 0 (0%) / 13 (0%)]
5026 (90%) are still in progress. [5015 (90%) / 0 (0%) / 11 (0%)]
Of the tasks that have been returned successfully:
219 (92%) are pending validation. [209 (87%) / 0 (0%) / 10 (4%)]
20 (8%) have been successfully validated. [17 (7%) / 0 (0%) / 3 (1%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
0 (0%) are inconclusive. [0 (0%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=14591367. The leading edge was at n=14465075 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.87% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
Not bad, as of right now, I'm number 60.
____________
|
|
|
MonkeydeeVolunteer tester
Send message
Joined: 8 Dec 13
Posts: 532
ID: 284516
Credit: 1,426,165,631
RAC: 1,420,308
            
|
Not bad, as of right now, I'm number 60.
Well done!
I'm in 113th right now and am expecting to fall a bit as neither of my computers will be able to put in any more units before the deadline.
____________
My Primes
Badge Score: 4*2 + 6*2 + 7*4 + 8*8 + 11*3 + 12*1 = 157
 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
|
Just one day to go!
Challenge: Cullen Birthday
App: 3 (WOO-LLR)
(As of 2016-04-27 18:08:12 UTC)
8988 tasks have been sent out. [CPU/GPU/anonymous_platform: 8914 (99%) / 0 (0%) / 74 (1%)]
Of those tasks that have been sent out:
1458 (16%) came back with some kind of an error. [1458 (16%) / 0 (0%) / 0 (0%)]
4315 (48%) have returned a successful result. [4253 (47%) / 0 (0%) / 62 (1%)]
3215 (36%) are still in progress. [3203 (36%) / 0 (0%) / 12 (0%)]
Of the tasks that have been returned successfully:
1354 (31%) are pending validation. [1336 (31%) / 0 (0%) / 18 (0%)]
2880 (67%) have been successfully validated. [2836 (66%) / 0 (0%) / 44 (1%)]
15 (0%) were invalid. [15 (0%) / 0 (0%) / 0 (0%)]
66 (2%) are inconclusive. [66 (2%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=15241464. The leading edge was at n=15110732 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.87% as much as it had prior to the challenge!
Challenge: Cullen Birthday
App: 4 (CUL-LLR)
(As of 2016-04-27 18:08:13 UTC)
12046 tasks have been sent out. [CPU/GPU/anonymous_platform: 11993 (100%) / 0 (0%) / 53 (0%)]
Of those tasks that have been sent out:
2450 (20%) came back with some kind of an error. [2449 (20%) / 0 (0%) / 1 (0%)]
6046 (50%) have returned a successful result. [6004 (50%) / 0 (0%) / 42 (0%)]
3550 (29%) are still in progress. [3540 (29%) / 0 (0%) / 10 (0%)]
Of the tasks that have been returned successfully:
2105 (35%) are pending validation. [2091 (35%) / 0 (0%) / 14 (0%)]
3799 (63%) have been successfully validated. [3775 (62%) / 0 (0%) / 24 (0%)]
24 (0%) were invalid. [24 (0%) / 0 (0%) / 0 (0%)]
118 (2%) are inconclusive. [114 (2%) / 0 (0%) / 4 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=14693608. The leading edge was at n=14465075 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.58% as much as it had prior to the challenge!
One a normal day, we would do about 125-150 each of Cullen and Woodall tasks. During the challenge we've been doing almost 900 Woodalls and almost 1300 Cullens. Well done!
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
With just about 19 hours to go, it's time for the usual end of challenge reminder:
At the Conclusion of the Challenge
We would prefer users "moving on" to finish those tasks they have downloaded, if not then please ABORT the WU's instead of DETACHING, RESETTING, or PAUSING.
ABORTING WU's allows them to be recycled immediately; thus a much faster "clean up" to the end of a Challenge. DETACHING, RESETTING, and PAUSING WU's causes them to remain in limbo until they EXPIRE. Therefore, we must wait until WU's expire to send them out to be completed.
____________
PrimeGrid Challenge Overall standings --- Last update: From Pi to Paddy (2016)
|
|
|
Ken_g6Volunteer developer
Send message
Joined: 4 Jul 06
Posts: 937
ID: 3110
Credit: 258,244,148
RAC: 79,904
|
|
Is that an unusually high number of inconclusives and invalid WUs? Because I got one inconclusive on a machine that's been completely stable, vs. someone else's machine with no other inconclusives or invalids, and a couple of teammates of mine were also surprised to get inconclusives or invalids.
____________
|
|
|
mackerelVolunteer tester
Send message
Joined: 2 Oct 08
Posts: 2639
ID: 29980
Credit: 568,393,769
RAC: 3,323
|
|
I was wondering the same. I had one of my machines recently give an invalid unit, which was otherwise ok up to that point. I was wondering if there was any pattern as to CPU family and the inconclusive units? For sure any system can go bad, but there's a little part of me wondering if something else might be happening... |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
|
Final statistics:
Challenge: Cullen Birthday
App: 3 (WOO-LLR)
(As of 2016-04-28 18:13:08 UTC)
9458 tasks have been sent out. [CPU/GPU/anonymous_platform: 9384 (99%) / 0 (0%) / 74 (1%)]
Of those tasks that have been sent out:
1650 (17%) came back with some kind of an error. [1650 (17%) / 0 (0%) / 0 (0%)]
5128 (54%) have returned a successful result. [5054 (53%) / 0 (0%) / 74 (1%)]
2673 (28%) are still in progress. [2673 (28%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
1364 (27%) are pending validation. [1340 (26%) / 0 (0%) / 24 (0%)]
3673 (72%) have been successfully validated. [3623 (71%) / 0 (0%) / 50 (1%)]
27 (1%) were invalid. [27 (1%) / 0 (0%) / 0 (0%)]
64 (1%) are inconclusive. [64 (1%) / 0 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=15245900. The leading edge was at n=15110732 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.89% as much as it had prior to the challenge!
Challenge: Cullen Birthday
App: 4 (CUL-LLR)
(As of 2016-04-28 18:13:09 UTC)
12462 tasks have been sent out. [CPU/GPU/anonymous_platform: 12409 (100%) / 0 (0%) / 53 (0%)]
Of those tasks that have been sent out:
2679 (21%) came back with some kind of an error. [2678 (21%) / 0 (0%) / 1 (0%)]
7401 (59%) have returned a successful result. [7349 (59%) / 0 (0%) / 52 (0%)]
2373 (19%) are still in progress. [2373 (19%) / 0 (0%) / 0 (0%)]
Of the tasks that have been returned successfully:
1606 (22%) are pending validation. [1592 (22%) / 0 (0%) / 14 (0%)]
5622 (76%) have been successfully validated. [5588 (76%) / 0 (0%) / 34 (0%)]
44 (1%) were invalid. [43 (1%) / 0 (0%) / 1 (0%)]
129 (2%) are inconclusive. [126 (2%) / 0 (0%) / 3 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=14693829. The leading edge was at n=14465075 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.58% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
|
The cleanup now starts. Given that these tasks have 14 day deadlines, I expect the cleanup to take between 6 weeks and 3 months to complete.
Cleanup Status:
Apr-28: Cullen Birthday: 3164 tasks outstanding; 2790 affecting individual (280) scoring positions; 2345 affecting team (62) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
I apologize in advance if this is a stupid question, but this has been the first challenge I participated in (since I just recently joined PrimeGrid a few weeks ago): is there anything I need to do or can do to help with the cleanup tasks, or will they automatically be assigned, as long as I keep the Woodall and Cullen tasks on my primegrid preferences?
____________
best regards,
alexander falk |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
I apologize in advance if this is a stupid question, but this has been the first challenge I participated in (since I just recently joined PrimeGrid a few weeks ago): is there anything I need to do or can do to help with the cleanup tasks, or will they automatically be assigned, as long as I keep the Woodall and Cullen tasks on my primegrid preferences?
Automatically assigned, but to be honest the cleanups take care of themselves. What takes so long is there will always be a handful of tasks that get sent to a computer and never returned, so we wait for the 14-day deadline to expire before sending out a replacement. There's not a lot you can do to help with that.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
|
Cleanup Status:
Apr-28: Cullen Birthday: 3164 tasks outstanding; 2790 affecting individual (280) scoring positions; 2345 affecting team (62) scoring positions.
Apr-29: Cullen Birthday: 2796 tasks outstanding; 2408 affecting individual (274) scoring positions; 2081 affecting team (60) scoring positions.
Apr-30: Cullen Birthday: 2432 tasks outstanding; 2094 affecting individual (265) scoring positions; 1757 affecting team (54) scoring positions.
May-1: Cullen Birthday: 2131 tasks outstanding; 1742 affecting individual (258) scoring positions; 1537 affecting team (52) scoring positions.
May-2: Cullen Birthday: 1902 tasks outstanding; 1539 affecting individual (250) scoring positions; 1028 affecting team (48) scoring positions.
May-3: Cullen Birthday: 1683 tasks outstanding; 1365 affecting individual (237) scoring positions; 883 affecting team (43) scoring positions.
May-4: Cullen Birthday: 1575 tasks outstanding; 1277 affecting individual (234) scoring positions; 805 affecting team (40) scoring positions.
May-5: Cullen Birthday: 1426 tasks outstanding; 1157 affecting individual (231) scoring positions; 707 affecting team (38) scoring positions.
May-6: Cullen Birthday: 1291 tasks outstanding; 1044 affecting individual (224) scoring positions; 608 affecting team (35) scoring positions.
May-7: Cullen Birthday: 1183 tasks outstanding; 920 affecting individual (215) scoring positions; 331 affecting team (30) scoring positions.
May-8: Cullen Birthday: 1063 tasks outstanding; 786 affecting individual (208) scoring positions; 275 affecting team (29) scoring positions.
May-9: Cullen Birthday: 916 tasks outstanding; 655 affecting individual (189) scoring positions; 229 affecting team (24) scoring positions.
May-10: Cullen Birthday: 815 tasks outstanding; 546 affecting individual (178) scoring positions; 196 affecting team (23) scoring positions.
May-11: Cullen Birthday: 728 tasks outstanding; 476 affecting individual (172) scoring positions; 168 affecting team (21) scoring positions.
May-12: Cullen Birthday: 629 tasks outstanding; 411 affecting individual (163) scoring positions; 154 affecting team (21) scoring positions.
May-13: Cullen Birthday: 559 tasks outstanding; 359 affecting individual (151) scoring positions; 134 affecting team (21) scoring positions.
May-14: Cullen Birthday: 497 tasks outstanding; 309 affecting individual (139) scoring positions; 125 affecting team (21) scoring positions.
May-15: Cullen Birthday: 455 tasks outstanding; 279 affecting individual (133) scoring positions; 119 affecting team (20) scoring positions.
May-16: Cullen Birthday: 393 tasks outstanding; 239 affecting individual (118) scoring positions; 102 affecting team (19) scoring positions.
May-17: Cullen Birthday: 364 tasks outstanding; 219 affecting individual (113) scoring positions; 96 affecting team (18) scoring positions.
May-18: Cullen Birthday: 334 tasks outstanding; 196 affecting individual (106) scoring positions; 83 affecting team (18) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
|
|
|
I fired up a few woodall last night to help with the clean up.
How is the cleanup going? It is still going on right?
If it is not that's ok too. |
|
|
|
|
I fired up a few woodall last night to help with the clean up.
How is the cleanup going? It is still going on right?
If it is not that's ok too.
Michael's post above yours details cleanup progress with pretty much daily updates. |
|
|
|
|
|
Thank you, I did not notice that. I am used to clicking on the main thread and if there is a new post it takes me to it. Just an edit of a post does not do that.
Thanks again.
Bill |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
|
Cleanup Status:
Apr-28: Cullen Birthday: 3164 tasks outstanding; 2790 affecting individual (280) scoring positions; 2345 affecting team (62) scoring positions.
Apr-29: Cullen Birthday: 2796 tasks outstanding; 2408 affecting individual (274) scoring positions; 2081 affecting team (60) scoring positions.
Apr-30: Cullen Birthday: 2432 tasks outstanding; 2094 affecting individual (265) scoring positions; 1757 affecting team (54) scoring positions.
May-1: Cullen Birthday: 2131 tasks outstanding; 1742 affecting individual (258) scoring positions; 1537 affecting team (52) scoring positions.
May-2: Cullen Birthday: 1902 tasks outstanding; 1539 affecting individual (250) scoring positions; 1028 affecting team (48) scoring positions.
May-3: Cullen Birthday: 1683 tasks outstanding; 1365 affecting individual (237) scoring positions; 883 affecting team (43) scoring positions.
May-4: Cullen Birthday: 1575 tasks outstanding; 1277 affecting individual (234) scoring positions; 805 affecting team (40) scoring positions.
May-5: Cullen Birthday: 1426 tasks outstanding; 1157 affecting individual (231) scoring positions; 707 affecting team (38) scoring positions.
May-6: Cullen Birthday: 1291 tasks outstanding; 1044 affecting individual (224) scoring positions; 608 affecting team (35) scoring positions.
May-7: Cullen Birthday: 1183 tasks outstanding; 920 affecting individual (215) scoring positions; 331 affecting team (30) scoring positions.
May-8: Cullen Birthday: 1063 tasks outstanding; 786 affecting individual (208) scoring positions; 275 affecting team (29) scoring positions.
May-9: Cullen Birthday: 916 tasks outstanding; 655 affecting individual (189) scoring positions; 229 affecting team (24) scoring positions.
May-10: Cullen Birthday: 815 tasks outstanding; 546 affecting individual (178) scoring positions; 196 affecting team (23) scoring positions.
May-11: Cullen Birthday: 728 tasks outstanding; 476 affecting individual (172) scoring positions; 168 affecting team (21) scoring positions.
May-12: Cullen Birthday: 629 tasks outstanding; 411 affecting individual (163) scoring positions; 154 affecting team (21) scoring positions.
May-13: Cullen Birthday: 559 tasks outstanding; 359 affecting individual (151) scoring positions; 134 affecting team (21) scoring positions.
May-14: Cullen Birthday: 497 tasks outstanding; 309 affecting individual (139) scoring positions; 125 affecting team (21) scoring positions.
May-15: Cullen Birthday: 455 tasks outstanding; 279 affecting individual (133) scoring positions; 119 affecting team (20) scoring positions.
May-16: Cullen Birthday: 393 tasks outstanding; 239 affecting individual (118) scoring positions; 102 affecting team (19) scoring positions.
May-17: Cullen Birthday: 364 tasks outstanding; 219 affecting individual (113) scoring positions; 96 affecting team (18) scoring positions.
May-18: Cullen Birthday: 334 tasks outstanding; 196 affecting individual (106) scoring positions; 83 affecting team (18) scoring positions.
May-19: Cullen Birthday: 307 tasks outstanding; 180 affecting individual (101) scoring positions; 69 affecting team (16) scoring positions.
May-20: Cullen Birthday: 273 tasks outstanding; 159 affecting individual (93) scoring positions; 59 affecting team (15) scoring positions.
May-21: Cullen Birthday: 251 tasks outstanding; 145 affecting individual (87) scoring positions; 54 affecting team (15) scoring positions.
May-22: Cullen Birthday: 220 tasks outstanding; 120 affecting individual (78) scoring positions; 46 affecting team (15) scoring positions.
May-23: Cullen Birthday: 196 tasks outstanding; 104 affecting individual (70) scoring positions; 39 affecting team (13) scoring positions.
May-24: Cullen Birthday: 171 tasks outstanding; 90 affecting individual (62) scoring positions; 36 affecting team (13) scoring positions.
May-25: Cullen Birthday: 158 tasks outstanding; 86 affecting individual (58) scoring positions; 14 affecting team (11) scoring positions.
May-26: Cullen Birthday: 145 tasks outstanding; 80 affecting individual (55) scoring positions; 10 affecting team (9) scoring positions.
May-27: Cullen Birthday: 124 tasks outstanding; 68 affecting individual (48) scoring positions; 6 affecting team (5) scoring positions.
May-28: Cullen Birthday: 110 tasks outstanding; 61 affecting individual (45) scoring positions; 6 affecting team (5) scoring positions.
May-29: Cullen Birthday: 99 tasks outstanding; 53 affecting individual (41) scoring positions; 5 affecting team (5) scoring positions.
May-30: Cullen Birthday: 89 tasks outstanding; 48 affecting individual (39) scoring positions; 5 affecting team (5) scoring positions.
May-31: Cullen Birthday: 75 tasks outstanding; 40 affecting individual (32) scoring positions; 4 affecting team (4) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
|
Cleanup Status:
Apr-28: Cullen Birthday: 3164 tasks outstanding; 2790 affecting individual (280) scoring positions; 2345 affecting team (62) scoring positions.
May-1: Cullen Birthday: 2131 tasks outstanding; 1742 affecting individual (258) scoring positions; 1537 affecting team (52) scoring positions.
Jun-1: Cullen Birthday: 66 tasks outstanding; 34 affecting individual (28) scoring positions; 4 affecting team (4) scoring positions.
Jun-2: Cullen Birthday: 62 tasks outstanding; 34 affecting individual (28) scoring positions; 4 affecting team (4) scoring positions.
Jun-3: Cullen Birthday: 57 tasks outstanding; 30 affecting individual (24) scoring positions; 3 affecting team (3) scoring positions.
Jun-4: Cullen Birthday: 52 tasks outstanding; 28 affecting individual (22) scoring positions; 3 affecting team (3) scoring positions.
Jun-5: Cullen Birthday: 48 tasks outstanding; 27 affecting individual (22) scoring positions; 3 affecting team (3) scoring positions.
Jun-6: Cullen Birthday: 45 tasks outstanding; 24 affecting individual (21) scoring positions; 3 affecting team (3) scoring positions.
Jun-7: Cullen Birthday: 40 tasks outstanding; 23 affecting individual (20) scoring positions; 2 affecting team (2) scoring positions.
Jun-8: Cullen Birthday: 38 tasks outstanding; 22 affecting individual (19) scoring positions; 2 affecting team (2) scoring positions.
Jun-9: Cullen Birthday: 37 tasks outstanding; 21 affecting individual (18) scoring positions; 2 affecting team (2) scoring positions.
Jun-10: Cullen Birthday: 35 tasks outstanding; 20 affecting individual (17) scoring positions; 2 affecting team (2) scoring positions.
Jun-11: Cullen Birthday: 32 tasks outstanding; 17 affecting individual (14) scoring positions; 2 affecting team (2) scoring positions.
Jun-12: Cullen Birthday: 29 tasks outstanding; 15 affecting individual (14) scoring positions; 2 affecting team (2) scoring positions.
Jun-13: Cullen Birthday: 28 tasks outstanding; 15 affecting individual (14) scoring positions; 2 affecting team (2) scoring positions.
Jun-14: Cullen Birthday: 27 tasks outstanding; 15 affecting individual (14) scoring positions; 2 affecting team (2) scoring positions.
Jun-15: Cullen Birthday: 24 tasks outstanding; 13 affecting individual (12) scoring positions; 1 affecting team (1) scoring positions.
Jun-16: Cullen Birthday: 23 tasks outstanding; 12 affecting individual (11) scoring positions; 0 affecting team (0) scoring positions.
Jun-17: Cullen Birthday: 16 tasks outstanding; 7 affecting individual (7) scoring positions; 0 affecting team (0) scoring positions.
Jun-18: Cullen Birthday: 15 tasks outstanding; 7 affecting individual (7) scoring positions; 0 affecting team (0) scoring positions.
Jun-19: Cullen Birthday: 15 tasks outstanding; 7 affecting individual (7) scoring positions; 0 affecting team (0) scoring positions.
Jun-20: Cullen Birthday: 15 tasks outstanding; 7 affecting individual (7) scoring positions; 0 affecting team (0) scoring positions.
Jun-21: Cullen Birthday: 15 tasks outstanding; 7 affecting individual (7) scoring positions; 0 affecting team (0) scoring positions.
Jun-22: Cullen Birthday: 15 tasks outstanding; 7 affecting individual (7) scoring positions; 0 affecting team (0) scoring positions.
Jun-23: Cullen Birthday: 13 tasks outstanding; 6 affecting individual (6) scoring positions; 0 affecting team (0) scoring positions.
Jun-24: Cullen Birthday: 12 tasks outstanding; 5 affecting individual (5) scoring positions; 0 affecting team (0) scoring positions.
Jun-25: Cullen Birthday: 12 tasks outstanding; 5 affecting individual (5) scoring positions; 0 affecting team (0) scoring positions.
Jun-26: Cullen Birthday: 12 tasks outstanding; 5 affecting individual (5) scoring positions; 0 affecting team (0) scoring positions.
Jun-27: Cullen Birthday: 11 tasks outstanding; 5 affecting individual (5) scoring positions; 0 affecting team (0) scoring positions.
Jun-28: Cullen Birthday: 9 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Jun-29: Cullen Birthday: 8 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Jun-30: Cullen Birthday: 7 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
|
Cleanup Status:
Apr-28: Cullen Birthday: 3164 tasks outstanding; 2790 affecting individual (280) scoring positions; 2345 affecting team (62) scoring positions.
May-1: Cullen Birthday: 2131 tasks outstanding; 1742 affecting individual (258) scoring positions; 1537 affecting team (52) scoring positions.
Jun-1: Cullen Birthday: 66 tasks outstanding; 34 affecting individual (28) scoring positions; 4 affecting team (4) scoring positions.
Jul-1: Cullen Birthday: 7 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Jul-2: Cullen Birthday: 5 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Jul-3: Cullen Birthday: 5 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Jul-4: Cullen Birthday: 5 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Jul-5: Cullen Birthday: 5 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Jul-6: Cullen Birthday: 5 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Jul-7: Cullen Birthday: 5 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Jul-8: Cullen Birthday: 4 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Jul-9: Cullen Birthday: 4 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Jul-10: Cullen Birthday: 4 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Jul-11: Cullen Birthday: 3 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
Jul-12: Cullen Birthday: 3 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
Jul-13: Cullen Birthday: 3 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
Jul-14: Cullen Birthday: 3 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
____________
My lucky number is 75898524288+1 |
|
|
Michael GoetzVolunteer moderator
Project administrator
Send message
Joined: 21 Jan 10
Posts: 13951
ID: 53948
Credit: 391,563,667
RAC: 138,161
|
|
Here are the final results for the Cullen Birthday Challenge:
Individuals:
1) zunewantan
2) Scott Brown
3) tng*
Teams:
1) Aggie The Pew
2) Sicituradastra.
3) Czech Nation Team
Congratulations to the winners, and to all participants. See you tomorrow at the start of the Summer Olympics Challenge.
____________
My lucky number is 75898524288+1 |
|
|
