Author |
Message |
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
Welcome to the Cinco de Mayo Challenge
A 2^3 day Challenge is being offered on PrimeGrid's The Riesel Problem (LLR) application. To participate in the Challenge, please select only the The Riesel Problem (LLR) project in your PrimeGrid preferences section. The challenge will begin 5 May 2011 18:00 UTC and end 13 May 2011 18:00 UTC. Application builds are available for Linux 32 bit, Windows 32 bit and MacIntel. These applications will be sent to 64 bit clients. As with all LLR application projects, there is no advantage of 64 bit over 32 bit.
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 ~6 hours on fast/newer computers and 12+ 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. :)
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 5 May 2011 18:00 UTC and received BEFORE 13 May 2011 18:00 UTC will be considered for credit. We will use the "prime score" method which is based on the n value (k*b^n-1) to score the challenge. The only difference is that the primary and double checker of a WU will receive the same score.
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 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. :)
About the Riesel Problem
Hans Ivar Riesel (born 1929 in Stockholm) is a Swedish mathematician. In 1956, he showed that there are an infinite number of positive odd integer k's such that k*2^n-1 is composite (not prime) for every integer n>=1. These numbers are now called Riesel numbers. He further showed that k=509203 was such one.
It is conjectured that 509203 is the smallest Riesel number. The Riesel problem consists in determining that 509203 is the smallest Riesel number. To show that it is the smallest, a prime of the form k*2^n-1 must be found for each of the positive integer k's less than 509203. As of April 2011, there remains 61 k's for which no primes have been found. They are as follows:
2293, 9221, 23669, 31859, 38473, 40597, 46663, 67117, 74699, 81041, 93839, 97139, 107347, 121889, 123547, 129007, 141941, 143047, 146561, 161669, 162941, 192971, 206039, 206231, 215443, 226153, 234343, 245561, 250027, 252191, 273809, 304207, 315929, 319511, 324011, 325123, 327671, 336839, 342847, 344759, 353159, 362609, 363343, 364903, 365159, 368411, 371893, 384539, 386801, 397027, 398023, 402539, 409753, 415267, 444637, 470173, 474491, 477583, 485557, 494743, 502573
For a more detailed history and status of the Riesel problem, please visit Wilfrid Keller's The Riesel Problem: Definition and Status.
Additional Information
The Riesel problem is to k*2^n-1 as the Sierpinski problem is to k*2^n+1. There is no equivalent to the 'prime' Sierpinski problem since k=509203, the conjectured smallest Riesel number, is prime.
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).
____________
|
|
|
|
I'm looking forward to this, my goal is to actually get my TRP LLR badge out of the way.
____________
|
|
|
Sysadm@Nbg Volunteer moderator Volunteer tester Project scientist
 Send message
Joined: 5 Feb 08 Posts: 1210 ID: 18646 Credit: 809,306,751 RAC: 244,363
                      
|
John wrote: Welcome to the Cinco de Mayo Challenge
...
WU's will take ~15 minutes on fast/newer computers and 25+ minutes on slower/older computers.
...
???
How does this fit to
ProjectPreferences wrote:
Recent average CPU time: 10:59:30
Think it is a copy & paste error
____________
Sysadm@Nbg
my current lucky number: 113856050^65536 + 1
PSA-PRPNet-Stats-URL: http://u-g-f.de/PRPNet/
|
|
|
Honza Volunteer moderator Volunteer tester Project scientist Send message
Joined: 15 Aug 05 Posts: 1931 ID: 352 Credit: 5,623,182,139 RAC: 5,252,366
                                   
|
~10 hours on average for 1M+ digits TRPtest looks OK, copy&paste is working fine - those 15-25 mins are not fitting.
____________
My stats
Badge score: 1*1 + 5*1 + 8*3 + 9*11 + 10*1 + 11*1 + 12*3 = 186 |
|
|
|
To participate in the Challenge, please select only the The Riesel Problem (LLR) project in your PrimeGrid preferences section.
Necessarily select only The Riesel Problem (LLR), or can select together with GPU-application? |
|
|
|
To participate in the Challenge, please select only the The Riesel Problem (LLR) project in your PrimeGrid preferences section.
Necessarily select only The Riesel Problem (LLR), or can select together with GPU-application?
I believe you will be able to run both the TRP on a cpu and CW or PPS sieves your gpu. Just don't have the cpu version of the gpu project checked as well.
Rick
____________
@AggieThePew
|
|
|
|
On Intel Q6600@3510MHz calculation speed ~1300 ppd/core, elapsed time varies widely (4h-11h) |
|
|
|
Please see this post for more details on how you can "stress test" your computer
What "this post" could be?
____________
I'm counting for science,
Points just make me sick. |
|
|
|
Please see this post for more details on how you can "stress test" your computer
What "this post" could be?
http://www.primegrid.com/forum_thread.php?id=857&nowrap=true#8311 |
|
|
|
Is there advantages (head start I mean) in processing the WU early for the projects in general (especially this one coming up)? |
|
|
|
Is there advantages (head start I mean) in processing the WU early for the projects in general (especially this one coming up)?
No advantage to the challenge as far as credits go but you can verify how long the wu's will take and that your system(s) are all ready to go.
Rick |
|
|
|
Is there advantages (head start I mean) in processing the WU early for the projects in general (especially this one coming up)?
No advantage to the challenge as far as credits go but you can verify how long the wu's will take and that your system(s) are all ready to go.
Rick
I disagree about the challenge points (credits are not relevant) because boinc needs to download the latest versions of the files before it will start on that host. Sure this is more important to sieves (and John does inform people to do this) than LLR's and less important when you have fast connection to PrimeGrid. But there is a fixed deadline so those few minutes may result in failure to report within the deadline for all WUs on that host.
|
|
|
|
Is there advantages (head start I mean) in processing the WU early for the projects in general (especially this one coming up)?
No advantage to the challenge as far as credits go but you can verify how long the wu's will take and that your system(s) are all ready to go.
Rick
I disagree about the challenge points (credits are not relevant) because boinc needs to download the latest versions of the files before it will start on that host. Sure this is more important to sieves (and John does inform people to do this) than LLR's and less important when you have fast connection to PrimeGrid. But there is a fixed deadline so those few minutes may result in failure to report within the deadline for all WUs on that host.
No challenge points are awarded for wu's downloaded prior to or after the challenge time line so I'm not sure what there is to disagree about.
Doing a wu on each system prior to the challenge is a good idea as you state so that it will get the latest versions AND to insure they will run on the systems. Nothing worse than starting the challenge only to find out your wu's are erroring out. |
|
|
|
I notice there are long and short WU's.
Will there be a difference in the credits received between the two in the challenge? Or will all WU's be the same size in the challenge?
____________
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
How to Join the Challenge
To participate in the Challenge, please select only the The Riesel Problem (LLR) project in your PrimeGrid preferences section. Also, set "Send work from any subproject if selected projects have no work" to no to guarantee that no other work will be sent. The challenge will begin 5 May 2011 18:00 UTC and end 13 May 2011 18:00 UTC.
ATTENTION: The primality program LLR is CPU intensive and the WU's for this Challenge are several hours long; so, it is vital to have a stable system (solid hardware) with GOOD COOLING. Invalid WU's will not receive credit.
Application builds are available for the following:
- Microsoft Windows (98 or later) running on an Intel x86-compatible CPU
- Linux running on an Intel x86-compatible CPU
- Mac OS 10.4 or later running on Intel
Note: As with all LLR application projects, there is no advantage of 64 bit over 32 bit.
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 5 May 2011 18:00 UTC and received BEFORE 13 May 2011 18:00 UTC will be considered for credit. We will use the "prime score" method which is based on the n value (k*b^n-1) to score the challenge. The only difference is that the primary and double checker of a WU will receive the same score.
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. 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.
Stats will be available on the front page next to the clock within 30 minutes after the start...but don't expect any results for several hours due to the length of the TRP (LLR) tasks.
What to expect at Challenge start
The server always gets hit hard at the beginning of the Challenge. However, TRP (LLR) tasks are quite long so we don't expect a heavy load. Nevertheless, a few hours before the start (5 May 2011 18:00 UTC) "max cache" will be dropped. Additionally, "max to send" will be dropped. Anyone attempting to request more will be met with "max cache" messages.
We'll raise the front page buffer before the start of the Challenge. These settings will be adjusted as necessary. Afterwards, as conditions allow, we'll raise "max cache". We'll continue to increase "max cache" when the server can handle it.
This method allows the greatest opportunity for the most clients to get work. Even if it's just 1 task for the first few minutes, at least the client is crunching. Past Challenges have shown that clients have an excellent chance to reach "max cache" before their first task is complete. We expect the same this time.
Strategies for starting the Challenge
Depending on a variety of factors, different strategies work for different users. Here are just a few to consider:
- large farm, user can be present at start
-Set Computer is connected to the Internet about every to 0 days
-Set Maintain enough work for an additional to 0 days
-Change PrimeGrid preferences to a fast WU project such as SGS (LLR)
-At Challenge start, update PrimeGrid preferences and only select The Riesel Problem (LLR) project
-At worse, you'll only be 1 SGS (LLR) WU late on each core starting the Challenge.
-After all machines have work, increase Maintain enough work for an additional
- large farm, user NOT able to be present at start
-Same connection settings as above except choose The Riesel Problem (LLR) project before the start
-At worse, you'll only be 1 TRP (LLR) WU late on each core starting the Challenge.
- a few computers, user can be present at start
-Change PrimeGrid preferences and only select The Riesel Problem (LLR) project
-Set computers to "No New Tasks" for PrimeGrid
-At Challenge Start, update computers to "Allow New Tasks"
- a few computers, user NOT able to be present at start
-Set Computer is connected to the Internet about every to 0 days
-Set Maintain enough work for an additional to 0 days
-Change PrimeGrid preferences and only select The Riesel Problem (LLR) project
-At worse, you'll only be 1 TRP (LLR) WU late on each core starting the Challenge.
NOTE: This presumes you have all other BOINC projects suspended.
Best of Luck to everyone!
____________
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
Special Download Note
If you have not completed an LLR task in the past several months, please consider completing one before the Challenge. The new LLR application is substantially larger than the previous.
If you have completed an LLR task since 6 Feb 2011 then you are fine. If not, then it is suggested that you complete 1 task from a short task project such as SGS (LLR) or PPS (LLR). This will insure that you have the latest application and free up resources for the server to deliver tasks instead of the large application. :)
____________
|
|
|
|
(...)
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 ~6 hours on fast/newer computers and 12+ 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. :)
Please, please, please make sure your machines are up to the task.
(...)
And again as in every LLR-challenge with the longer LLR-WUs
Message from syslogd@rr020 at May 5 20:05:05 ...
kernel:EDAC MC0: UE row 0, channel-a= 0 channel-b= 1 labels "-": (Branch=0 DRAM-Bank=0 RDWR=Read RAS=16303 CAS=0 FATAL Err=0x4 (>Tmid Thermal event with intelligent throttling disabled))
sensors|grep C
Ch. 0 DIMM 0: +78.0°C (low = +74.5°C, high = +124.0°C)
Ch. 1 DIMM 0: +73.5°C (low = +74.5°C, high = +124.0°C)
Core 0: +55.0°C (high = +74.0°C, crit = +100.0°C)
Core 1: +52.0°C (high = +74.0°C, crit = +100.0°C)
Core 2: +49.0°C (high = +74.0°C, crit = +100.0°C)
Core 3: +49.0°C (high = +74.0°C, crit = +100.0°C)
Core 4: +49.0°C (high = +74.0°C, crit = +100.0°C)
Core 5: +44.0°C (high = +74.0°C, crit = +100.0°C)
Core 6: +59.0°C (high = +74.0°C, crit = +100.0°C)
Core 7: +54.0°C (high = +74.0°C, crit = +100.0°C)
temp1: +41.0°C (high = +100.0°C, hyst = +95.0°C) sensor = Intel PECI
temp2: +35.0°C (high = +100.0°C, hyst = +95.0°C) sensor = Intel PECI
temp5: +39.0°C (high = +100.0°C, hyst = +95.0°C) sensor = thermistor
temp6: +41.0°C (high = +100.0°C, hyst = +95.0°C) sensor = thermistor
It is way more RAM-intensive than CPU-intensive! lol |
|
|
|
Even with the Boinc GPU challenge going and now the start of PG challenge it looks like the server is running real smooth.
Very good job server admins ! |
|
|
|
Was just wondering if anyone knew when the BoincStats web page would be updating the Cinco results. |
|
|
|
been participating in the challenge but my name isn't mentioned on the list of participants.
____________
|
|
|
|
been participating in the challenge but my name isn't mentioned on the list of participants.
You are crunching WUs that were download before the challenge started, so:
Credits: Yes (after the WUs are validated).
Challenge points: No.
____________
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
Was just wondering if anyone knew when the BoincStats web page would be updating the Cinco results.
BS is having server issues. Looks like we won't see any BS stats for this challenge. Sorry.
____________
|
|
|
|
been participating in the challenge but my name isn't mentioned on the list of participants.
You are crunching WUs that were download before the challenge started, so:
Credits: Yes (after the WUs are validated).
Challenge points: No.
You and me James Nelson; I haven't downloaded or completed any WUs since May 5th 18:00.
Not yet
____________
|
|
|
|
been participating in the challenge but my name isn't mentioned on the list of participants.
You are crunching WUs that were download before the challenge started, so:
Credits: Yes (after the WUs are validated).
Challenge points: No.
well sense i screwed up on the start of the challenge i guess I'll just sit this one out, and just restore my old settings
____________
|
|
|
|
almost halftime and still no prime found...
how many WUs were done and (if necessary) double-checked so far? |
|
|
|
almost halftime and still no prime found...
how many WUs were done and (if necessary) double-checked so far?
I'm contributing only a small part as I left my machines on the 5oB double check crunching there. Additionally, I give 5:1 priority for DistrRTgen and yet since the start my pending credit waiting for a quorum of 2 just keeps rising. I have about 8k of credit pending. |
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
almost halftime and still no prime found...
how many WUs were done and (if necessary) double-checked so far?
~55K tasks completed...unfortunately, no prime yet. The trailing and leading edges of n are approximately 3.67M to 4.11M.
____________
|
|
|
|
What were the trailing and leading edges when we started the challenge?
____________
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
What were the trailing and leading edges when we started the challenge?
Around 3.6M-3.7M.
____________
|
|
|
|
Seems like something is wrong with one of my hosts.
Awkward was running normal before the challenge, will withdraw from challenge... |
|
|
Scott Brown Volunteer moderator Project administrator Volunteer tester Project scientist
 Send message
Joined: 17 Oct 05 Posts: 2323 ID: 1178 Credit: 14,674,918,678 RAC: 23,405,183
                                           
|
Well...a few hours of power outage due to the complete incompetence of some university staff (a test of university wide back-up power that is supposed to avoid power supply interruption...of course, unannounced), and now I have dropped two places....AAAGGGGGHHHHH!
Oh well...back at it and I'll see how it goes over the last 2 days...
____________
141941*2^4299438-1 is prime!
|
|
|
|
At home with storm season, I've had 6 outages of power in 10 days with the most recent last Saturday. The irony is that my new UPS arrived Monday. |
|
|
|
I would just like to say, that I find it quite difficult to join these challenges lately, as I always need to write down what subprojects are active on each of the venues I use for different HW/OS configurations. It would be so much easier if there would be a checkbox in (venue) preferences settings that would say and do something like this: "Automatically join to challenges? (whenever there is an active challenge, you will receive only work from that subproject)". Just an idea, I'm not quite sure if it could be done.
BR
____________
|
|
|
mackerel Volunteer tester
 Send message
Joined: 2 Oct 08 Posts: 2583 ID: 29980 Credit: 550,189,840 RAC: 37,015
                             
|
I'm looking forward to the end of this challenge... it's far too warm at home with the extra computers running. It is making me debate how hard I should try on the remaining ones over summer... was originally hoping to get top100 in each event but that's looking unlikely now unless I produce even more heat! |
|
|
|
I always scale down in summer, sometimes to one core per host, sometimes I just turn them off.
____________
Thanks,
Jim
|
|
|
mackerel Volunteer tester
 Send message
Joined: 2 Oct 08 Posts: 2583 ID: 29980 Credit: 550,189,840 RAC: 37,015
                             
|
I only leave my main system on in summer. The others were turned on just for the challenge. They serve as my winter heating system although some are really due for retirement. |
|
|
|
~55K tasks completed...unfortunately, no prime yet. The trailing and leading edges of n are approximately 3.67M to 4.11M.
The increasing range is probably a double-edged sword:
- good for a large number of tasks being crunched;
- bad for the time the cleanup will take.
I expect it will be the best part of a month to cleanup afterwards.
____________
Warped
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
On 8 May 2011 7:29:52 UTC, PrimeGrid’s The Riesel Problem project eliminated k=123547 by finding the Mega prime: 123547*2^3804809-1
The prime is 1,145,367 digits long and enters Chris Caldwell's The Largest Known Primes Database ranked 28th overall. This is the largest prime found in The Riesel Problem and PrimeGrid's fourth elimination. 60 k's now remain.
The discovery was made by Jakub Łuszczek of Poland using an Intel Core i5 2500 @ 3.3GHz with 8 GB RAM running Windows 7 Home Premium x64. This computer took just over 4 hours and 35 minutes to complete the primality test using LLR. Jakub is a member of the Polish National Team.
For more details, please see the official announcement.
____________
|
|
|
|
It is great that there was progress made on the project during the challenge, let's all cross our fingers and hope for another prime to be found!
____________
|
|
|
|
Well done, Jakub.
Now it's Sixty or Bust.
____________
Warped
|
|
|
|
Well done, Jakub.
Yes. well done made Jakub Łuszczek of the Polish National Team !!!
____________
|
|
|
|
So do we just Abort (recycle) the WU that we have now or just keep crunching till the end? Since the largest Prime has been found for this challenge? |
|
|
|
A prime was found for 1 of 61 k's which means 60 remain to find a prime for. That's plenty of work left to do for quite some time so keep crunching! |
|
|
|
I have no wingman on this WU.
I this correct? |
|
|
|
yes, it's correct.
SGS (LLR), PPS (LLR), and TRP (LLR) use Adaptive replication. That's why sometimes you see a minimum quorum of 1. |
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
3 hours remain!
Final preparations are ongoing now for the conclusion of the Challenge. Time to get those last tasks turned in and start emptying the cache. For those "moving on" after the Challenge it's best to abort the remaining tasks in your cache that are not in progress. For those remaining, continue on as usual. :)
Please update your clients early and often to get those completed WU's reported and counted.
-----------------------------------------------------
A quorum of 2 is NOT needed to award Challenge score - i.e. no double checker. Each returned result will earn a Challenge score. Please note that if the result is eventually declared invalid, the score will be removed. Therefore, the Challenge will not be considered final until all quorum's affecting scoring positions are completed. Because of this, we have a "clean up" period where the goal is to complete these quorums.
We hope for a fast "clean-up". If everyone can remember to either complete their cache or ABORT their WU's, then we'll be able to finalize earlier rather than later. Expect up to 3 to 4 weeks or more before results become final.
Good Luck to everyone as we finish these last remaining hours...
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. :)
____________
|
|
|
RytisVolunteer moderator Project administrator
 Send message
Joined: 22 Jun 05 Posts: 2653 ID: 1 Credit: 86,414,269 RAC: 1,016
                     
|
One more prime has been found. Stay tuned.
____________
|
|
|
|
One more prime has been found. Stay tuned.
Awesome! Right at the buzzer!
____________
Proud member of Team Aggie the Pew
"Wir müssen wissen. Wir werden wissen."
"We must know, we shall know."
- David Hilbert, 1930 |
|
|
|
I was able to hold on the 25th place in the challenge!
<big exhale>
____________
|
|
|
mfbabb2 Volunteer tester
 Send message
Joined: 10 Oct 08 Posts: 510 ID: 30360 Credit: 15,676,996 RAC: 32,482
                     
|
I am happy to be in the top 1/3 ...
____________
Murphy (AtP)
|
|
|
rroonnaalldd Volunteer developer Volunteer tester
 Send message
Joined: 3 Jul 09 Posts: 1213 ID: 42893 Credit: 34,634,263 RAC: 0
                 
|
I was able to hold on the 25th place in the challenge!
<big exhale>
Congrats brinktastee.
I am far, far behind you on places 330 (individual) and 71 (team)...
____________
Best wishes. Knowledge is power. by jjwhalen
|
|
|
|
Congrats out to everyone who made it through the challenge :)
Rick |
|
|
|
I am happy to be in the top 1/3 ...
____________
Murphy
183916*5^519597-1 is my first Top 5000 Prime
I am very happy to have finished "in the money" (Top 100) for the first time ever!
____________
Proud member of Team Aggie the Pew
"Wir müssen wissen. Wir werden wissen."
"We must know, we shall know."
- David Hilbert, 1930 |
|
|
|
I managed to maintain my goal of top 500 for all of the LLR challenges, got a badge, and I am glad that we got another prime out of the way.
____________
|
|
|
|
Congrats out to everyone who made it through the challenge :)
Congrats Indeed! - Not easy to keep so many "plates-in-the-air" for that long.
-Was also glad to squeak a place on the leader-board despite losing a handful of carefully-juggled tasks to an unexpected power-outage 5 hours before the deadline.. :-(
This is my first top-100 place this year, despite having more than double the processing-power I had last year. It seems Moore's Law is out to force us into penury just to stay in the same place... :)
____________
|
|
|
|
Nice challenge ! WCG missed me :)
No errors this time... all WU'S valid :)
____________
Greetz
Chris
561*2^1423021+1
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
Preliminary data
While the Challenge is officially over, the "clean up" process now begins. If you have the resources to help, please see: The "Clean Up" Phase below. All that is required is to continue crunching The Riesel Problem (LLR) to complete the aborted and timed-out resends.
For only the 2nd time in a "longer WU" Challenge, we were successful if finding something significant…doubly so. The Earth Day Challenge last year found a 321 mega prime. In this Challenge, two mega primes were found eliminating k=123547 and k=415267 for the Riesel Problem. The first mega prime, 123547*2^3804809-1 (1,145,367 digits), was found by Jakub Łuszczek of Poland and a member of the Polish National Team. The second mega prime, 415267*2^3771929-1 (1,135,470 digits), was found by Alexey Tarasov of the Ukraine and a member of the Ukraine team.
As expected, the server was able to handle both the Challenge and Pentathlon with no problems. Official results are probably 3-4 weeks away, but here is some preliminary data to ponder. :)
Just under 114.6K tasks were completed resulting in over 232M Challenge points awarded. 208 teams and 1131 individuals participated in the Challenge.
Thank you to everyone. We appreciate your participation and hope you had fun! We'll see you at the next time at PrimeGrid's Birthday/Summer Solstice Challenge beginning 21 June at 17:16 UTC lasting 24 hours on the Cullen/Woodall (Sieve).
The preliminary top 10 in each category are listed below. Note: scores are not final as tasks later determined to be invalid will be deducted from the total score.
Top 10 Teams
Rank Name Score
1 Sicituradastra. 34798541.06
2 Ukraine 30168240.74
3 SETI.USA 19943111.12
4 Polish National Team 15489551.16
5 Team 2ch 10903073.76
6 Czech National Team 10085766.42
7 PrimeSearchTeam 9876988.97
8 TeAm AnandTech 7531342.74
9 SETI.Germany 6913081.56
10 Duke University 6611787.61
Top 10 Individuals
Rank Name Team Score
1 Alexus78 Ukraine 12977774.13
2 Scott Brown Duke University 6611787.61
3 Mumps [MM] SETI.USA 6400702.22
4 Snf* Sicituradastra. 5728070.15
5 Lennart SM5YMT PrimeSearchTeam 5686377.22
6 pascaltec Sicituradastra. 3995267.72
7 nyabe Team 2ch 3803455.41
8 tng* Sicituradastra. 3415891.63
9 ..:: Thor ::.. Polish National Team 3410102.55
10 Sitarow SETI.USA 3195299.22
The "Clean Up" Phase
Past observation has shown that a quick "clean up" phase is primarily based on how many "timed out" tasks there are. We expect this "clean up" to take several weeks. Immediately after the Challenge, the initial "clean up" handles all the aborted tasks. Then, for the next 5 days, "timed out" tasks are the focus of the "clean up". After those 5 days, then tasks that have "timed out" twice will be the focus...and so on. The Challenge will not be considered final until all quorums affecting scoring positions are completed.
The dilemma of only doing Challenge tasks is that after the initial "clean up" of aborted tasks, the buffer would remain at 0 until a "timed out" task was returned. Hosts that only have TRP (LLR) selected would sit idle until a "timed out" task was recycled. Therefore, work is always made available to keep hosts from going idle.
A couple of measures are taken to maximize the opportunity for Challenge tasks to be sent out first and to minimize new work. First, new work will have a longer deadline. The task with the shorter deadline will be crunched first. Second, the buffer will be set initially at 200 so that at most, there's only 200 new tasks at any given time.
If one participates in the "clean up", almost certainly new work will be processed. To minimize this, observe the following key times:
- Any time the The Riesel Problem (LLR) buffer on the front page is above 200, resends are available.
- Most work sent out right after the Challenge completes will be recycled "aborted tasks"...most likely for the first 4-5 days.
- 5 days (18 May 18:00 UTC) after the Challenge completes, another wave of resends typically are available ("timed out" from abandoned tasks at the end of the Challenge).
As long as the buffer on the front page is at 200 or below, there's enough resources participating in the "clean up". Additional resources will not speed up the process.
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
____________
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
On 8 May 2011 15:43:27 UTC UTC, PrimeGrid’s The Riesel Problem project eliminated k=415267 by finding the Mega prime: 415267*2^3771929-1
The prime is 1,135,470 digits long and enters Chris Caldwell's The Largest Known Primes Database ranked 29th overall. This is the 2nd largest prime found in The Riesel Problem and PrimeGrid's fifth elimination. 59 k's now remain.
The discovery was made by Alexey Tarasov of the Ukraine using an Intel Core2 Duo E6550 @ 2.33GHz with 1 GB RAM running Windows XP Professional. This computer took just over 10 hours and 18 minutes to complete the primality test using LLR. Alexey is a member of the Ukraine team.
For more details, please see the official announcement.
____________
|
|
|
|
Well done Alexey Tarasov of the Ukraine team.
____________
|
|
|
|
Congrats to Alexey!
Поздравления Алексею и команде Украина! Молодцы! |
|
|
yank  Send message
Joined: 14 May 07 Posts: 111 ID: 8367 Credit: 11,474,819,218 RAC: 0
                    
|
CONGRATULATIONS TO THE SICITURADASTRA PRIMEGRID TEAM. THIS TEAM DID SOME EXCELLENT WORK FOR THIS CHALLENGE.
____________
|
|
|
|
CONGRATULATIONS TO THE SICITURADASTRA. PRIMEGRID TEAM. THIS TEAM DID SOME EXCELLENT WORK FOR THIS CHALLENGE.
;-) On behalf of the members in Sicituradastra. I say Thank you!
They are great guys and good crunchers! ;-)
Also i will congratulate Snf* with the Year Total Lead. ;-D
(Not official yet - but still..)
And thanx to Alexus78 and Ukraine for a good challenge. ;-)
____________
|
|
|
|
Definitely a big thanks to Team Ukraine - made for a nice tense eight days. Obvious that there was a lot of effort up and down the scoring sheets. |
|
|
|
Definitely a big thanks to Team Ukraine - made for a nice tense eight days. Obvious that there was a lot of effort up and down the scoring sheets.
That's very nice of you to say so, and a big thanks to you. Not sure about tense but I wasn't there for eight days. Starting a few days late gives the interest of steadilly rising for the rest of the event.
____________
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
Clean up Progress
It appears the "clean up" phase will be a challenge in itself. Since the 13th, the buffer has risen to its current level of 5835. This means current resources on TRP (LLR) are not enough to handle the resends. Hopefully it's leveled off, and we see a downward trend soon. However, on the 18th, we should expect another sharp rise as the first set of tasks expire from the conclusion of the Challenge.
Currently there are 7525 outstanding Challenge tasks, of which, 4881 are in scoring positions...affecting the outcome of 27 team positions and 91 individual positions.
The first round of time-outs will be fully recycled by 18 May 18:00 UTC.
Thanks to everyone for helping out with the clean up.
History
15 May: 7525 tasks outstanding; 4881 in scoring positions (27 team, 91 individual)
If one participates in the "clean up", almost certainly new work will be processed. To minimize this, observe the following key times:
- Any time the The Riesel Problem (LLR) buffer on the front page is above 200, resends are available.
- Most work sent out right after the Challenge completes will be recycled "aborted tasks"...most likely for the first 4-5 days.
- 5 days (18 May 18:00 UTC) after the Challenge completes, another wave of resends typically are available ("timed out" from abandoned tasks at the end of the Challenge).
As long as the buffer on the front page is at 200 or below, there's enough resources participating in the "clean up". Additional resources will not speed up the process.
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
____________
|
|
|
Scott Brown Volunteer moderator Project administrator Volunteer tester Project scientist
 Send message
Joined: 17 Oct 05 Posts: 2323 ID: 1178 Credit: 14,674,918,678 RAC: 23,405,183
                                           
|
I am maintaining challenge levels, at least that is until sometime later this week as rebuilds are scheduled for several machines that I have currently working.
...and the buffer is now over 6100...we're gonna need more help on this one.
____________
141941*2^4299438-1 is prime!
|
|
|
|
Congratulations to the PrimeGrid team for outstanding server performances.
I will participate to the cleaning phase. Please keep us informed of what is needed. |
|
|
pan2000Volunteer tester Send message
Joined: 23 Jan 07 Posts: 26 ID: 5226 Credit: 328,291,395 RAC: 0
                    
|
Clean Up?
Clean Up! |
|
|
|
I was sent this workunit which has already been "Completed and validated" by two computers.
Why would a third be necessary?
____________
Warped
|
|
|
|
I was sent this workunit which has already been "Completed and validated" by two computers.
Why would a third be necessary?
Very good question!
|
|
|
|
I was sent this workunit which has already been "Completed and validated" by two computers.
Why would a third be necessary?
Very good question!
I have received two of those as well... both of them validated and received credit. |
|
|
|
I was sent this workunit which has already been "Completed and validated" by two computers.
Why would a third be necessary?
Very good question!
I have received two of those as well... both of them validated and received credit.
The linked WU was reported just over 4 hours after the deadline passed and before you successfully returned it. With a 5 day deadline a WU sent at 11 May 2011 | 6:23:46 UTC must be returned by 16 May 2011 | 6:23:46 UTC before the WU is resent. There is no realistic way to stop a WU from being resent once it enters the resend queue especially with the massive cleanup needed. So it gets sent - too much resources etc to check that it is needed before sending it out.
If you catch these WUs within a suitable timeframe (like before starting), you can abort them. Otherwise just crunch them as you will also get the credit that others got if the WU is successfully completed.
|
|
|
|
I drew 6 WUs from the challenge cleanup and aborted some that are not from the cleanup.
Every little bit helps i think. |
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
I was sent this workunit which has already been "Completed and validated" by two computers.
Why would a third be necessary?
A third task is not necessary. As ConflictingEmotions noted, the 2nd task timed out, 3rd task was generated and sat in the queue to be sent out. Unfortunately, BOINC did not cancel the 3rd task once the 2nd task returned to validate the WU. I'm not sure if BOINC can cancel WU's in the buffer, but I'm pretty sure it can cancel them once they've been sent out. Unfortunately, if the host does not have a cache, BOINC doesn't have time to cancel it before it starts processing. I'm sure Rytis can clarify this process better.
____________
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
I drew 6 WUs from the challenge cleanup and aborted some that are not from the cleanup.
Every little bit helps i think.
It appears that during the DB issue shortly after the end of the Challenge, new WU's were generated and placed in the buffer. Unfortunately, they will have to be "cleaned up" as well. Good news though, buffer is starting to drop.
____________
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
Clean up Progress
Currently there are 4573 outstanding Challenge tasks, of which, 2984 are in scoring positions...affecting the outcome of 17 team positions and 78 individual positions.
Thanks to everyone for helping out with the clean up.
History
16 May: 4573 tasks outstanding; 2984 in scoring positions (17 team, 78 individual)
15 May: 7525 tasks outstanding; 4881 in scoring positions (27 team, 91 individual)
If one participates in the "clean up", almost certainly new work will be processed. To minimize this, observe the following key times:
- Any time the The Riesel Problem (LLR) buffer on the front page is above 200, resends are available.
- Most work sent out right after the Challenge completes will be recycled "aborted tasks"...most likely for the first 4-5 days.
- 5 days (18 May 18:00 UTC) after the Challenge completes, another wave of resends typically are available ("timed out" from abandoned tasks at the end of the Challenge).
As long as the buffer on the front page is at 200 or below, there's enough resources participating in the "clean up". Additional resources will not speed up the process.
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
____________
|
|
|
|
I was sent this workunit which has already been "Completed and validated" by two computers.
Why would a third be necessary?
A third task is not necessary. As ConflictingEmotions noted, the 2nd task timed out, 3rd task was generated and sat in the queue to be sent out. Unfortunately, BOINC did not cancel the 3rd task once the 2nd task returned to validate the WU. I'm not sure if BOINC can cancel WU's in the buffer, but I'm pretty sure it can cancel them once they've been sent out. Unfortunately, if the host does not have a cache, BOINC doesn't have time to cancel it before it starts processing. I'm sure Rytis can clarify this process better.
Thanks for the feedback. I am the third person to crunch the task and received it 8 hours after the second of the two valid returns. Yes, my cache was quite small at the time and it started crunching, so I'll just let it complete. |
|
|
|
Sorry about the cleanup phase I can't maintain the same effort after the challenge as I could during it. I do allow new work and the project stays on my active list for awhile so I do help a bit but just not at the same rate as during the challenge. I have suspended work that is at risk of timing out after the challenge in some cases as little as 2 days after the end of the challenge. I crunch 12 projects so I always am splitting my efforts during normal crunching days. |
|
|
|
I was sent this workunit which has already been "Completed and validated" by two computers.
Why would a third be necessary?
Very good question!
I have received two of those as well... both of them validated and received credit.
I think it's possible that more than just the TRP was affected. I've had a pps sieve wu "cancelled by server" and when I looked at the task it had been completed and validated and my job was cancelled. |
|
|
|
I drew 6 WUs from the challenge cleanup and aborted some that are not from the cleanup.
Every little bit helps i think.
It appears that during the DB issue shortly after the end of the Challenge, new WU's were generated and placed in the buffer. Unfortunately, they will have to be "cleaned up" as well. Good news though, buffer is starting to drop.
I eliminated one WU, Nosferatu's computer was wrong. |
|
|
|
Looks like the clean up is going well.. down to 1159 current units.. not sure where that is on the actual challenge cleanup but it's way down from the 4573. |
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
Clean up Progress
Currently there are 1100 outstanding Challenge tasks, of which, 733 are in scoring positions...affecting the outcome of 8 team positions and 40 individual positions.
Thanks to everyone for helping out with the clean up.
History
19 May: 1100 tasks outstanding; 733 in scoring positions (8 team, 40 individual)
16 May: 4573 tasks outstanding; 2984 in scoring positions (17 team, 78 individual)
15 May: 7525 tasks outstanding; 4881 in scoring positions (27 team, 91 individual)
If one participates in the "clean up", almost certainly new work will be processed. To minimize this, observe the following key times:
- Any time the The Riesel Problem (LLR) buffer on the front page is above 200, resends are available.
- Most work sent out right after the Challenge completes will be recycled "aborted tasks"...most likely for the first 4-5 days.
- 5 days (18 May 18:00 UTC) after the Challenge completes, another wave of resends typically are available ("timed out" from abandoned tasks at the end of the Challenge).
As long as the buffer on the front page is at 200 or below, there's enough resources participating in the "clean up". Additional resources will not speed up the process.
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
____________
|
|
|
|
The buffer is down to less than 200. I would expect that means the cleanup will be complete in few days, since the second wave of resends should now be crunching.
Amazing. Well done to all concerned.
____________
Warped
|
|
|
|
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
The desire for another silver badge outweighs the desire to move on :D
____________
|
|
|
|
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
The desire for another silver badge outweighs the desire to move on :D
I with you on this MC - the desire for a different colored badge does out weigh the need to move on :) |
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
Clean up Progress
Currently there are 730 outstanding Challenge tasks, of which, 489 are in scoring positions...affecting the outcome of 5 team positions and 28 individual positions.
Thanks to everyone for helping out with the clean up.
History
20 May: 730 tasks outstanding; 489 in scoring positions (5 team, 28 individual)
19 May: 1100 tasks outstanding; 733 in scoring positions (8 team, 40 individual)
16 May: 4573 tasks outstanding; 2984 in scoring positions (17 team, 78 individual)
15 May: 7525 tasks outstanding; 4881 in scoring positions (27 team, 91 individual)
If one participates in the "clean up", almost certainly new work will be processed. To minimize this, observe the following key times:
- Any time the The Riesel Problem (LLR) buffer on the front page is above 200, resends are available.
- Most work sent out right after the Challenge completes will be recycled "aborted tasks"...most likely for the first 4-5 days.
- 5 days (18 May 18:00 UTC) after the Challenge completes, another wave of resends typically are available ("timed out" from abandoned tasks at the end of the Challenge).
As long as the buffer on the front page is at 200 or below, there's enough resources participating in the "clean up". Additional resources will not speed up the process.
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
____________
|
|
|
|
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
The desire for another silver badge outweighs the desire to move on :D
I with you on this MC - the desire for a different colored badge does out weigh the need to move on :)
It's time for a clean up badge: The golden mop ;)
____________
|
|
|
|
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
The desire for another silver badge outweighs the desire to move on :D
I with you on this MC - the desire for a different colored badge does out weigh the need to move on :)
Got mine to gold so I am moving on as my buffer clears:-)
Other subprojects also need a gold badge or better, if available.
I only have 7 challenge WUs pending, but, due to aborts, only 3 of these that will influence the results. I am cleaning up 1 WU issued during challenge but it will not affect the results because it timed out for eligible user. Hopefully all finished within the next 12 hours.
Anyhow kudos to all since most people either aborted or completed their buffers!
|
|
|
|
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
The desire for another silver badge outweighs the desire to move on :D
Well said! |
|
|
mfbabb2 Volunteer tester
 Send message
Joined: 10 Oct 08 Posts: 510 ID: 30360 Credit: 15,676,996 RAC: 32,482
                     
|
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
The desire for another silver badge outweighs the desire to move on :D
I with you on this MC - the desire for a different colored badge does out weigh the need to move on :)
Me three! (Going for Silver)
____________
Murphy (AtP)
|
|
|
|
Just 1 WU left in the Challenge
http://www.primegrid.com/workunit.php?wuid=182469844
____________
From the High Desert in New Mexico
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
Clean up Progress
Currently there are 39 outstanding Challenge tasks, of which, 27 are in scoring positions...affecting the outcome of 0 team positions and 4 individual positions.
Thanks to everyone for helping out with the clean up.
History
25 May: 39 tasks outstanding; 27 in scoring positions (0 team, 4 individual)
22 May: 195 tasks outstanding; 135 in scoring positions (0 team, 11 individual)
20 May: 730 tasks outstanding; 489 in scoring positions (5 team, 28 individual)
19 May: 1100 tasks outstanding; 733 in scoring positions (8 team, 40 individual)
16 May: 4573 tasks outstanding; 2984 in scoring positions (17 team, 78 individual)
15 May: 7525 tasks outstanding; 4881 in scoring positions (27 team, 91 individual)
If one participates in the "clean up", almost certainly new work will be processed. To minimize this, observe the following key times:
- Any time the The Riesel Problem (LLR) buffer on the front page is above 200, resends are available.
- Most work sent out right after the Challenge completes will be recycled "aborted tasks"...most likely for the first 4-5 days.
- 5 days (18 May 18:00 UTC) after the Challenge completes, another wave of resends typically are available ("timed out" from abandoned tasks at the end of the Challenge).
As long as the buffer on the front page is at 200 or below, there's enough resources participating in the "clean up". Additional resources will not speed up the process.
We greatly appreciate any help in the "clean-up" process. However, we fully understand the need/desire to "move on".
____________
|
|
|
John Honorary cruncher
 Send message
Joined: 21 Feb 06 Posts: 2875 ID: 2449 Credit: 2,681,934 RAC: 0
                 
|
The results are Final!
Just over two weeks after the end of the challenge, the results are officially final. Challenge points have been awarded and the overall Challenge series standings have been updated.
For only the 2nd time in a "longer WU" Challenge, we were successful if finding something significant…doubly so. The Earth Day Challenge last year found a 321 mega prime. In this Challenge, two mega primes were found eliminating k=123547 and k=415267 for the Riesel Problem. The first mega prime, 123547*2^3804809-1 (1,145,367 digits), was found by Jakub Łuszczek of Poland and a member of the Polish National Team. The second mega prime, 415267*2^3771929-1 (1,135,470 digits), was found by Alexey Tarasov of the Ukraine and a member of the Ukraine team.
Just under 114.6K tasks were completed resulting in over 232M Challenge points awarded. 208 teams and 1131 individuals participated in the Challenge.
Congratulations to Sicituradastra. as the top team and Alexus78 as the top individual. Remember, the top 100 individual and top 50 team places earn points for this Challenge.
Thank you to everyone. We appreciate your participation and hope you had fun! We'll see you at the next Challenge - PrimeGrid's Birthday/Summer Solstice Challenge beginning 21 June at 17:16 UTC lasting 24 hours on the Cullen/Woodall (Sieve).
Stats: Participants | Teams
The top 10 in each category are listed below.
Top 10 Teams
Rank Name Score
1 Sicituradastra. 34588103.33
2 Ukraine 30071855.27
3 SETI.USA 19894220.43
4 Polish National Team 15383990.21
5 Team 2ch 10850036.94
6 Czech National Team 9974088.86
7 PrimeSearchTeam 9837968.93
8 TeAm AnandTech 7436028.68
9 SETI.Germany 6902886.18
10 Duke University 6611787.61
Top 10 Individuals
Rank Name Team Score
1 Alexus78 Ukraine 12975985.13
2 Scott Brown Duke University 6611787.61
3 Mumps [MM] SETI.USA 6400702.22
4 Snf* Sicituradastra. 5697664.79
5 Lennart SM5YMT PrimeSearchTeam 5686377.22
6 pascaltec Sicituradastra. 3995267.72
7 nyabe Team 2ch 3803455.41
8 tng* Sicituradastra. 3415891.63
9 ..:: Thor ::.. Polish National Team 3406056.18
10 Sitarow SETI.USA 3195299.22
____________
|
|
|