Join PrimeGrid
Returning Participants
Community
Leader Boards
Results
Other
drummers-lowrise
|
Message boards :
Number crunching :
Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice Challenge
Author |
Message |
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 375 ID: 764476 Credit: 46,579,215 RAC: 13,727
                 
|
Welcome to the Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice Challenge
The team scores. The crowd roars. You jump out of your seat, the happiest you've felt since those days during the summer of '98 you spent on Marley Beach, the savory smell of the barbie teasing your hungry stomach and the deep blue eyes of your now-ex-husband reassuring you that everything would be alright. Things were simpler then.
As you feel the sweet sting of sweat in your eyes under the hot Australian sun, you pity anyone who might be suffering under the height of winter in some poor, less fortunate part of the world. Across the stadium, someone shouts:
"Aussie Aussie Aussie!" OI! OI! OI!
"Aussie Aussie Aussie!" OI! OI! OI!
"Aussie!" OI! "Aussie!" OI!
"Aussie Aussie Aussie!" OI! OI! OI!
PrimeGrid will be celebrating the Summer Solstice by running a 10-day challenge with all the GFN projects where a prime is yet to be found; 21, 22 and DYFL. The Challenge will run from December 12th 04:19:00 UTC until December 22nd 04:19:00 UTC.
These GFN projects are part of the challenge:
GFN-21
GFN-22
GFN-DYFL
To participate in the Challenge, please select one or more of those projects in your PrimeGrid preferences section.
Note: The deadline for some of these WUs is significantly longer than ten days, so make sure your computer is able to return the WUs within the challenge time-frame. Only tasks issued AFTER the start time and returned BEFORE the finish time will be counted.
Application Builds
IMPORTANT: Overclocking -- including factory overclocking -- on Nvidia GPUs is very strongly discouraged. Even if your GPU can run other tasks without difficulty, it may be unable to run GFN tasks when overclocked.
Supported platforms:
- Windows: Nvidia GPU (OpenCL): 32 bit, AMD/ATI GPU (OpenCL): 32 bit, CPU: 64 bit, 32 bit
- Linux: Nvidia GPU (OpenCL): 32 bit, 64 bit, AMD/ATI GPU (OpenCL): 32 bit, 64 bit, CPU: 64 bit, 32 bit
- Mac: Nvidia GPU (OpenCL): 64 bit, AMD/ATI GPU (OpenCL): 64 bit, CPU: 64 bit, 32 bit
A Cautionary Reminder
ATTENTION: The primality programs Genefer (for CPUs) and GeneferOCL (for GPUs) are computationally 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 CPU, and please see this post for tips on running GFN on your GPU successfully.
As with all number crunching, excessive heat can potentially cause permanent hardware failure. Please ensure your cooling system is sufficient.
GFN-21 WU's are currently averaging 12 days on CPU and 20 hours on GPU.
GFN-22 WU's are currently averaging 69 hours on GPU.
GFN-DYFL WU's are currently averaging 54 hours on GPU (shorter not because WU's are shorter, but because the project self-selects for faster hardware).
For a general idea of how your GPU stacks up, you can have a look at the fastest GPUs list.
If your CPU is highly overclocked, please consider "stress testing" it. Overclocking your GPU is not recommended at all for GeneferCUDA. Sieving is an excellent alternative for computers that are not able to run Genefer. :)
Please, please, please make sure your machines are up to the task.
Multi-threading optimization instructions
If you're running GFN-21 on a CPU and looking to maximize your computer's performance during this challenge, or when running LLR in general, you may find this information useful.
- Your mileage may vary. Before the challenge starts, take some time and experiment and see what works best on your computer.
- If you have an Intel CPU with hyperthreading, either turn off the hyperthreading in the BIOS, or set BOINC to use 50% of the processors.
- If you're using a GPU for other tasks, it may be beneficial to leave hyperthreading on in the BIOS and instead tell BOINC to use 50% of the CPU's. This will allow one of the hyperthreads to service the GPU.
- Use GFN's multithreaded mode. It requires a little bit of setup, but it's worth the effort. Follow these steps:
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 December 12th 04:19:00 UTC and received BEFORE December 22nd 04:19:00 UTC will be considered for credit.
In this challenge we will be using the same scoring algorithm as we use to determine BOINC credits, including bonuses!. Because the score bonuses are included in the challenge score, it is advantageous to run the longer tasks if you can manage to finish them within the 10 day challenge window. This will land you a higher position in the leaderboard and therefor a higher score on the overall leaderboard.
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 alows 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.
Please consider either completing what's in the queue or ABORTING them. Thank you. :)
For those of you who wish to continue to help with GFN sieving, we are still sieving n=22 (World Record Units), as well as the n=20 (short) range and n=21 (next short) range. Please see We need your help with GFN Sieving! for more information.
More information on Generalized Fermat Numbers and the Genefer program
Best of Luck to everyone!
| |
|
|
For hyperthreading you use the syntax <cmdline>-nt 4</cmdline>
In LLR multithreading is is just -t 4 and not -nt 4.
Is this a typo or the GFN's are different ?? | |
|
Yves Gallot Volunteer developer Project scientist Send message
Joined: 19 Aug 12 Posts: 843 ID: 164101 Credit: 306,522,612 RAC: 5,341

|
For hyperthreading you use the syntax <cmdline>-nt 4</cmdline>
In LLR multithreading is is just -t 4 and not -nt 4.
Is this a typo or the GFN's are different ??
GFN's are different, -t was already used (test). | |
|
Chooka  Send message
Joined: 15 May 18 Posts: 335 ID: 1014486 Credit: 1,307,566,833 RAC: 4,901,678
                         
|
Sorry... it's too hot to run my GPU's in the middle of summer. I'll have to pass on this one.
____________
Слава Україні! | |
|
|
if anyone can let use know the stats on temp etc , when you do this project. | |
|
|
Sorry... it's too hot to run my GPU's in the middle of summer. I'll have to pass on this one.
I hear you mate, I will be doing very little as well. I am going to do a couple of GFN 21 CPU multithreaded as GPU just runs too hot when it is over 35C + room temperature. | |
|
|
I agree with Dingo, it is very hot in Australia at the moment but the real danger is from the bushfires (wildfires to those in the USA). Sydney is covered in smoke today at levels considered 11x hazardous. Visibility is low and the air burns the back of the throat if you are silly enough to go outside. Meanwhile our federal politicians do nothing about global warming and continue their love of coal.
For the upcoming GPU challenge my systems will likely be running GPU only and giving the CPUs a rest to minimise heat output so the a/c can cope.
ps I run the maximum number of solar PV panels on my roof that will physically fit. | |
|
|
I agree on the heat and GPU challenge in summer not being nice. I will be using TThrottle to limit my GPU's running temp if the ambient pushes their temps up. This will happen on 2 of my systems.
Currently I have a batch file and task scheduled so that my GPU's currently do not run from midday to 8pm due to the heat inside. I will play it day by day throughout the challenge based on forecast temps as to whether I run 24/7 or stick with the 16 hours per day for GPU's.
I just bought a new CPU 2 days ago so I will def be running the GFN21 CPU to see how it goes. Will run it multithreaded to take advantage of that option. Just trialing it now. | |
|
TimT  Send message
Joined: 2 Dec 11 Posts: 505 ID: 121414 Credit: 2,617,235,475 RAC: 317
                            
|
I seem to have a vague memory of multithreading on linux being somehow different, but I can't seem to find that info in real life. I've set up cpu-gfn21 on my linux box, and set it to run on 8 cores using the following in my app-config:
<app_config>
<app_version>
<app_name>genefer</app_name>
<cmdline>-nt 8</cmdline>
<plan_class>cpuGFN21</plan_class>
<avg_ncpus>8</avg_ncpus>
</app_version>
</app_config>
I notice a line in my log when the client restarts:
PrimeGrid 12/11/2019 2:03:27 PM Your app_config.xml file refers to an unknown application 'genefer21'. Known applications: 'llrPPS', 'llrPPSE', 'llrMEGA', 'llrTRP', 'ap26', 'llrGCW', 'llrTPS', 'llrWOO', 'llrCUL', 'llrSOB', 'llrPSP', 'llrESP', 'llr321', 'llrSR5', 'genefer17low', 'gcw_si
have I missed something, or maybe I'm not running the correct client version? I'm using 7.9.2
Edit: currently, the machine is downloading and running 1 task per core
--Tim | |
|
Monkeydee Volunteer tester
 Send message
Joined: 8 Dec 13 Posts: 548 ID: 284516 Credit: 1,707,334,225 RAC: 3,253,968
                            
|
That app_config looks right.
The warning message can usually be ignored and will go away when the first task of that type is run.
Is the app_config file in the project folder (boinc/projects/www.primegrid.com) or somewhere else?
After putting the app_config in place did you tell the BOINC manager to re-read the preferences files? Maybe try restarting the system (I know it's a Windows style suggestion, but for BOINC it might work too).
An update to the BOINC client likely isn't necessary, but can't hurt anything to try.
____________
My Primes
Badge Score: 4*2 + 6*2 + 7*1 + 8*11 + 9*1 + 11*3 + 12*1 = 169
| |
|
|
I get those errors as well but they are normal. When you actually start to run the sub project work then the error stops for that sub project. | |
|
TimT  Send message
Joined: 2 Dec 11 Posts: 505 ID: 121414 Credit: 2,617,235,475 RAC: 317
                            
|
That app_config looks right.
The warning message can usually be ignored and will go away when the first task of that type is run.
Is the app_config file in the project folder (boinc/projects/www.primegrid.com) or somewhere else?
After putting the app_config in place did you tell the BOINC manager to re-read the preferences files? Maybe try restarting the system (I know it's a Windows style suggestion, but for BOINC it might work too).
An update to the BOINC client likely isn't necessary, but can't hurt anything to try.
EDIT: strange enough, 5 minutes after posting this, I re-copy/pasted the app-config text into the file, reloaded and it's working properly -- still boggled as to exactly what happened, but must have been a typo or maybe a bad line-ending somewhere
--Tim | |
|
|
not allowing any tasks
please be specific how to correct. | |
|
|
<app_config>
<app_version>
<app_name>genefer</app_name>
<cmdline>-nt 8</cmdline>
<plan_class>cpuGFN21</plan_class>
<avg_ncpus>8</avg_ncpus>
</app_version>
</app_config>
...
PrimeGrid 12/11/2019 2:03:27 PM Your app_config.xml file refers to an unknown application 'genefer21'. Known applications: ...
There is nothing wrong with the app_config above. The unknown application is "genefer21" , which is not referenced in the above code. The in-memory version of app_config did contain such a reference. Perhaps you had not reloaded the config file when you got the message?
Query : Is 'genefer21' even a known application anymore? Or is that just the GPU application?
____________
Badge score: 5*1 + 6*1 + 7*8 + 8*5 + 10*2 + 11*2 + 12*1 + 13*1 = 174 | |
|
|
I have a GFN21 running under windows 10 and it had an estimated finish time of just over a day on CPU Multi Thread. I changed the number of threads in the script (14 to 15)and I rebooted my machine and when I started BOINC up again the estimate for the task is now over 40 days and he Prograss % is rising very slowly compared to other tasks on other machines using less threads.
Not sure I should let it continue to run or not ???
I also Have a GFN21 running on a 1080Ti GPU and the Estimated time on that has also jumped up from just over 7 hours to 2 days 22 hours ???
NOTE: I aborted the tasks.
I got 2 new tasks
CPU 15 threads = 1 day 9 hours
GPU = 11 hours 40 but dropping fast. Should end up abut 7 hours ? | |
|
|
I mentioned that I was going to use TThrottle to limit GPU heat.... didn't work. 95C for the GPU temp was a bit too high for my liking too.
I then decided to try MSI Afterburner after remembering that it could limit based on temperature (had to change priority from power limit). It is now limiting the GPU clock rate to keep the temp below 80C and working very effectively. The GPU isn't MSI branded either so this works with other cards for anyone else in the hot Australian summer trying to limit heat output from their cards. | |
|
|
GFN-21 i7-8700K 21h (mt)
GFN-21 GTX1080Ti 8h
GFN-22 GTX1080Ti 28h | |
|
|
It's not a problem, but I noticed that Genefer 22 (OCLcudaGFNWR) takes a full thread on Linux but hardly any CPU support in Windows. The Windows app requests 0.602 CPU and Linux 0.23 CPU (I'm aware the OS takes what it needs). I'm new to this app, run times initially don't look like they're going to be much different but I'm curious why there's such a difference in CPU use. | |
|
|
ASUS ROG OC RTX 2080ti > DYFL 23:27 h
____________
| |
|
Nick  Send message
Joined: 11 Jul 11 Posts: 2301 ID: 105020 Credit: 10,036,818,452 RAC: 29,389,478
                            
|
ASUS ROG OC RTX 2080ti > DYFL 23:27 h
I have 3 of that exact same card running DYFL at average of 23 hours
Temperatures are at 63, 64 and 68 degrees C | |
|
|
<app_config>
<app_version>
<app_name>genefer</app_name>
<cmdline>-nt 8</cmdline>
<plan_class>cpuGFN21</plan_class>
<avg_ncpus>8</avg_ncpus>
</app_version>
</app_config>
...
PrimeGrid 12/11/2019 2:03:27 PM Your app_config.xml file refers to an unknown application 'genefer21'. Known applications: ...
There is nothing wrong with the app_config above. The unknown application is "genefer21" , which is not referenced in the above code. The in-memory version of app_config did contain such a reference. Perhaps you had not reloaded the config file when you got the message?
Query : Is 'genefer21' even a known application anymore? Or is that just the GPU application?
The app_name is just genefer. I use this app_config.xml to control threads on GPU and CPU WUs.
<app_config>
<project_max_concurrent>2</project_max_concurrent>
<app_version>
<app_name>genefer</app_name>
<cmdline>-nt 27</cmdline>
<plan_class>cpuGFN21</plan_class>
<avg_ncpus>27</avg_ncpus>
</app_version>
<app>
<name>genefer</name>
<max_concurrent>3</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
</app_config>
BTW, how do you register for this challenge? I couldn't find how to do that. And where are the stats? | |
|
Monkeydee Volunteer tester
 Send message
Joined: 8 Dec 13 Posts: 548 ID: 284516 Credit: 1,707,334,225 RAC: 3,253,968
                            
|
BTW, how do you register for this challenge? I couldn't find how to do that. And where are the stats?
Registration is not required. All you have to do is run tasks of the associated type. The tasks have to start and finish within the challenge time.
You can find the challenge page under Leader Boards > Challenge Series
https://www.primegrid.com/challenge/challenge.php
____________
My Primes
Badge Score: 4*2 + 6*2 + 7*1 + 8*11 + 9*1 + 11*3 + 12*1 = 169
| |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
After 1 day...
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 16 (GFN-21)
(As of 2019-12-13 06:08:49 UTC)
4852 tasks have been sent out. [CPU/GPU/anonymous_platform: 3182 (66%) / 1670 (34%) / 0 (0%)]
Of those tasks that have been sent out:
1084 (22%) were aborted. [986 (20%) / 98 (2%) / 0 (0%)]
896 (18%) came back with some kind of an error. [317 (7%) / 579 (12%) / 0 (0%)]
376 (8%) have returned a successful result. [53 (1%) / 323 (7%) / 0 (0%)]
2496 (51%) are still in progress. [1826 (38%) / 670 (14%) / 0 (0%)]
Of the tasks that have been returned successfully:
311 (83%) are pending validation. [45 (12%) / 266 (71%) / 0 (0%)]
63 (17%) have been successfully validated. [8 (2%) / 55 (15%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
2 (1%) are inconclusive. [0 (0%) / 2 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=501710. The leading edge was at b=494424 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.47% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 17 (GFN-22)
(As of 2019-12-13 06:08:50 UTC)
902 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 900 (100%) / 2 (0%)]
Of those tasks that have been sent out:
21 (2%) were aborted. [0 (0%) / 20 (2%) / 1 (0%)]
618 (69%) came back with some kind of an error. [0 (0%) / 618 (69%) / 0 (0%)]
12 (1%) have returned a successful result. [0 (0%) / 12 (1%) / 0 (0%)]
251 (28%) are still in progress. [0 (0%) / 250 (28%) / 1 (0%)]
Of the tasks that have been returned successfully:
11 (92%) are pending validation. [0 (0%) / 11 (92%) / 0 (0%)]
1 (8%) have been successfully validated. [0 (0%) / 1 (8%) / 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 b=163690. The leading edge was at b=163228 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.28% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 31 (GFN-DYFL)
(As of 2019-12-13 06:08:50 UTC)
1367 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 1367 (100%) / 0 (0%)]
Of those tasks that have been sent out:
30 (2%) were aborted. [0 (0%) / 30 (2%) / 0 (0%)]
586 (43%) came back with some kind of an error. [0 (0%) / 586 (43%) / 0 (0%)]
28 (2%) have returned a successful result. [0 (0%) / 28 (2%) / 0 (0%)]
723 (53%) are still in progress. [0 (0%) / 723 (53%) / 0 (0%)]
Of the tasks that have been returned successfully:
26 (93%) are pending validation. [0 (0%) / 26 (93%) / 0 (0%)]
2 (7%) have been successfully validated. [0 (0%) / 2 (7%) / 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 b=884004. The leading edge was at b=882366 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.19% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
|
... I use this app_config.xml to control threads on GPU and CPU WUs.
<app_config>
<project_max_concurrent>2</project_max_concurrent>
<app_version>
<app_name>genefer</app_name>
<cmdline>-nt 27</cmdline>
<plan_class>cpuGFN21</plan_class>
<avg_ncpus>27</avg_ncpus>
</app_version>
<app>
<name>genefer</name>
<max_concurrent>3</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
</app_config>
...
I get this error:
13/12/2019 6:33:10 PM | PrimeGrid | Entry in app_config.xml for app 'genefer', plan class 'cpuGFN21' doesn't match any app versions
| |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
I just noticed something that may be of valve value to some of you: GeneferOCL (at least on GFN-22) and Steam (the game store/platform) don't like each other. I was getting a lot of lag. When I shut down Steam, the lag went away. I noticed this because the CPU version of Steam was stealing a lot of cycles from GFN21 running on the CPU.
____________
My lucky number is 75898524288+1 | |
|
|
LOL.. stil somebody crunch this??? easy win for cz team... but thats why they (cnt team) sit here on project..they like like easy win )) on other boinc projects they have poor numbers of day rac or TOP names in rac ,)) | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
After 2 (closer to 2.5) days...
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 16 (GFN-21)
(As of 2019-12-14 13:21:11 UTC)
7722 tasks have been sent out. [CPU/GPU/anonymous_platform: 4686 (61%) / 3036 (39%) / 0 (0%)]
Of those tasks that have been sent out:
1316 (17%) were aborted. [1208 (16%) / 108 (1%) / 0 (0%)]
2157 (28%) came back with some kind of an error. [993 (13%) / 1164 (15%) / 0 (0%)]
1388 (18%) have returned a successful result. [390 (5%) / 998 (13%) / 0 (0%)]
2861 (37%) are still in progress. [2095 (27%) / 766 (10%) / 0 (0%)]
Of the tasks that have been returned successfully:
856 (62%) are pending validation. [249 (18%) / 607 (44%) / 0 (0%)]
518 (37%) have been successfully validated. [140 (10%) / 378 (27%) / 0 (0%)]
2 (0%) were invalid. [0 (0%) / 2 (0%) / 0 (0%)]
12 (1%) are inconclusive. [1 (0%) / 11 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=505344. The leading edge was at b=494424 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.21% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 17 (GFN-22)
(As of 2019-12-14 13:21:12 UTC)
1302 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 1300 (100%) / 2 (0%)]
Of those tasks that have been sent out:
29 (2%) were aborted. [0 (0%) / 28 (2%) / 1 (0%)]
819 (63%) came back with some kind of an error. [0 (0%) / 819 (63%) / 0 (0%)]
125 (10%) have returned a successful result. [0 (0%) / 125 (10%) / 0 (0%)]
329 (25%) are still in progress. [0 (0%) / 328 (25%) / 1 (0%)]
Of the tasks that have been returned successfully:
109 (87%) are pending validation. [0 (0%) / 109 (87%) / 0 (0%)]
16 (13%) have been successfully validated. [0 (0%) / 16 (13%) / 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 b=164118. The leading edge was at b=163228 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.55% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 31 (GFN-DYFL)
(As of 2019-12-14 13:21:12 UTC)
1811 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 1811 (100%) / 0 (0%)]
Of those tasks that have been sent out:
43 (2%) were aborted. [0 (0%) / 43 (2%) / 0 (0%)]
768 (42%) came back with some kind of an error. [0 (0%) / 768 (42%) / 0 (0%)]
204 (11%) have returned a successful result. [0 (0%) / 204 (11%) / 0 (0%)]
796 (44%) are still in progress. [0 (0%) / 796 (44%) / 0 (0%)]
Of the tasks that have been returned successfully:
155 (76%) are pending validation. [0 (0%) / 155 (76%) / 0 (0%)]
47 (23%) have been successfully validated. [0 (0%) / 47 (23%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
2 (1%) are inconclusive. [0 (0%) / 2 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=884678. The leading edge was at b=882366 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.26% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
|
Very high number of "Error while computing" running Genefer 21 v3.21 (cpuGFN21) and Genefer 21 v3.21 (OCLcudaGFN) even on the same Workunit.
Outcome Computation error
Client state Compute error
Exit status -1073741795 (0xC000001D) STATUS_ILLEGAL_INSTRUCTION
Exit status 7 (0x00000007) Unknown error code
Is this an end user issue or an app issue?
https://www.primegrid.com/workunit.php?wuid=633161786
https://www.primegrid.com/workunit.php?wuid=633162454
https://www.primegrid.com/workunit.php?wuid=633162025 | |
|
|
Hosts such as https://www.primegrid.com/results.php?hostid=944079 can produce very many errors. Since provoking the error is much much faster than properly completing the task, such a host can "process" a big percentage of all workunits. /JeppeSN | |
|
|
I get this error:
13/12/2019 6:33:10 PM | PrimeGrid | Entry in app_config.xml for app 'genefer', plan class 'cpuGFN21' doesn't match any app versions
If you haven't downloaded any of the GFN 21 CPU WUs (and apps) you'll get that but I don't think it affects anything. | |
|
streamVolunteer moderator Project administrator Volunteer developer Volunteer tester Send message
Joined: 1 Mar 14 Posts: 1051 ID: 301928 Credit: 563,881,725 RAC: 1,288
                         
|
Very high number of "Error while computing" running Genefer 21 v3.21 (cpuGFN21) and Genefer 21 v3.21 (OCLcudaGFN) even on the same Workunit.
Outcome Computation error
Client state Compute error
Exit status -1073741795 (0xC000001D) STATUS_ILLEGAL_INSTRUCTION
Exit status 7 (0x00000007) Unknown error code
Is this an end user issue or an app issue?
https://www.primegrid.com/workunit.php?wuid=633161786
https://www.primegrid.com/workunit.php?wuid=633162454
https://www.primegrid.com/workunit.php?wuid=633162025
Different users, different problems.
Exit status -1073741795 (0xC000001D) STATUS_ILLEGAL_INSTRUCTION
Genefer app crashed (don't know why, the crash is inside Genefer code, may be generic bad memory/overheating CPU problem)
Exit status 7 (0x00000007) Unknown error code
See line above: No NVIDIA compatible OpenCL device found.
This is Windows 10 system. As usual, Windows update destroyed NVidia OpenCL drivers. Again.
../../projects/www.primegrid.com/geneferocl_linux64_3.3.3-2: /lib64/libc.so.6:
version `GLIBC_2.14' not found
(required by ../../projects/www.primegrid.com/geneferocl_linux64_3.3.3-2)
Alas, this Linux-based system has too old system library (2.12) but Genefer requires 2.14
Two last errors happens immediately. So a host with these problem could "touch" hundreds and thousands of tasks until server bans him. Actually, it does not much harm except a bit of extra server load.
| |
|
|
Very high number of "Error while computing" running Genefer 21 v3.21 (cpuGFN21) and Genefer 21 v3.21 (OCLcudaGFN) even on the same Workunit.
Outcome Computation error
Client state Compute error
Exit status -1073741795 (0xC000001D) STATUS_ILLEGAL_INSTRUCTION
Exit status 7 (0x00000007) Unknown error code
Is this an end user issue or an app issue?
https://www.primegrid.com/workunit.php?wuid=633161786
https://www.primegrid.com/workunit.php?wuid=633162454
https://www.primegrid.com/workunit.php?wuid=633162025
Different users, different problems.
Exit status -1073741795 (0xC000001D) STATUS_ILLEGAL_INSTRUCTION
Genefer app crashed (don't know why, the crash is inside Genefer code, may be generic bad memory/overheating CPU problem)
Exit status 7 (0x00000007) Unknown error code
See line above: No NVIDIA compatible OpenCL device found.
This is Windows 10 system. As usual, Windows update destroyed NVidia OpenCL drivers. Again.
../../projects/www.primegrid.com/geneferocl_linux64_3.3.3-2: /lib64/libc.so.6:
version `GLIBC_2.14' not found
(required by ../../projects/www.primegrid.com/geneferocl_linux64_3.3.3-2)
Alas, this Linux-based system has too old system library (2.12) but Genefer requires 2.14
Two last errors happens immediately. So a host with these problem could "touch" hundreds and thousands of tasks until server bans him. Actually, it does not much harm except a bit of extra server load.
Thank you for the information. | |
|
|
Not really seeing any CPU Usage (8%-9%)running on the CPU. Genefer 21 v3.21 (cpuGFN21)
Host: https://www.primegrid.com/show_host_detail.php?hostid=920343
Running Tasks: https://www.primegrid.com/results.php?hostid=920343&offset=0&show_names=0&state=0&appid=16
<app_config>
<app>
<name>genefer</name>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.1</cpu_usage>
</gpu_versions>
<app_version>
<app_name>genefer</app_name>
<cmdline>-nt 8</cmdline>
<plan_class>cpuGFN21</plan_class>
<avg_ncpus>8</avg_ncpus>
</app_version>
</app>
<report_results_immediately/>
</app_config>
Changed the settings to but No Difference as well
<app>
<name>genefer</name>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.1</cpu_usage>
</gpu_versions>
<app_version>
<cmdline>-nt 8</cmdline>
<plan_class>cpuGFN21</plan_class>
<avg_ncpus>8</avg_ncpus>
</app_version>
</app>
or this seems to make no difference.
<app>
<name>genefer</name>
<app_version>
<cmdline>-nt 8</cmdline>
<plan_class>cpuGFN21</plan_class>
<avg_ncpus>8</avg_ncpus>
</app_version>
<gpu_versions>
<gpu_usage>1.0</gpu_usage>
<cpu_usage>0.1</cpu_usage>
</gpu_versions>
</app> | |
|
Ken_g6 Volunteer developer
 Send message
Joined: 4 Jul 06 Posts: 940 ID: 3110 Credit: 265,153,553 RAC: 110,745
                            
|
Exit status -1073741795 (0xC000001D) STATUS_ILLEGAL_INSTRUCTION
Genefer app crashed (don't know why, the crash is inside Genefer code, may be generic bad memory/overheating CPU problem)
I think I've narrowed this one down. I was interested because he's using the same CPU as me but I didn't get the error. I think he's using Windows 7 Home Premium without a service pack, which doesn't support AVX. That produces the error. He needs to update his OS. And maybe the application should report systems that don't have AVX enabled. | |
|
robish Volunteer moderator Volunteer tester
 Send message
Joined: 7 Jan 12 Posts: 2223 ID: 126266 Credit: 7,942,315,293 RAC: 5,419,769
                               
|
Exit status -1073741795 (0xC000001D) STATUS_ILLEGAL_INSTRUCTION
Genefer app crashed (don't know why, the crash is inside Genefer code, may be generic bad memory/overheating CPU problem)
I think I've narrowed this one down. I was interested because he's using the same CPU as me but I didn't get the error. I think he's using Windows 7 Home Premium without a service pack, which doesn't support AVX. That produces the error. He needs to update his OS. And maybe the application should report systems that don't have AVX enabled.
Wow. Well spotted. Well done!!! 👍
____________
My lucky number 10590941048576+1 | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
After three days:
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 16 (GFN-21)
(As of 2019-12-15 05:54:38 UTC)
10516 tasks have been sent out. [CPU/GPU/anonymous_platform: 6279 (60%) / 4237 (40%) / 0 (0%)]
Of those tasks that have been sent out:
1487 (14%) were aborted. [1338 (13%) / 149 (1%) / 0 (0%)]
3481 (33%) came back with some kind of an error. [1552 (15%) / 1929 (18%) / 0 (0%)]
1999 (19%) have returned a successful result. [606 (6%) / 1393 (13%) / 0 (0%)]
3549 (34%) are still in progress. [2783 (26%) / 766 (7%) / 0 (0%)]
Of the tasks that have been returned successfully:
1083 (54%) are pending validation. [329 (16%) / 754 (38%) / 0 (0%)]
892 (45%) have been successfully validated. [273 (14%) / 619 (31%) / 0 (0%)]
4 (0%) were invalid. [0 (0%) / 4 (0%) / 0 (0%)]
20 (1%) are inconclusive. [4 (0%) / 16 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=508698. The leading edge was at b=494424 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.89% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 17 (GFN-22)
(As of 2019-12-15 05:54:38 UTC)
1542 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 1540 (100%) / 2 (0%)]
Of those tasks that have been sent out:
36 (2%) were aborted. [0 (0%) / 35 (2%) / 1 (0%)]
958 (62%) came back with some kind of an error. [0 (0%) / 958 (62%) / 0 (0%)]
193 (13%) have returned a successful result. [0 (0%) / 193 (13%) / 0 (0%)]
355 (23%) are still in progress. [0 (0%) / 354 (23%) / 1 (0%)]
Of the tasks that have been returned successfully:
147 (76%) are pending validation. [0 (0%) / 147 (76%) / 0 (0%)]
44 (23%) have been successfully validated. [0 (0%) / 44 (23%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
2 (1%) are inconclusive. [0 (0%) / 2 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=164356. The leading edge was at b=163228 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.69% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 31 (GFN-DYFL)
(As of 2019-12-15 05:54:38 UTC)
2315 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 2315 (100%) / 0 (0%)]
Of those tasks that have been sent out:
43 (2%) were aborted. [0 (0%) / 43 (2%) / 0 (0%)]
1036 (45%) came back with some kind of an error. [0 (0%) / 1036 (45%) / 0 (0%)]
352 (15%) have returned a successful result. [0 (0%) / 352 (15%) / 0 (0%)]
884 (38%) are still in progress. [0 (0%) / 884 (38%) / 0 (0%)]
Of the tasks that have been returned successfully:
211 (60%) are pending validation. [0 (0%) / 211 (60%) / 0 (0%)]
138 (39%) have been successfully validated. [0 (0%) / 138 (39%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
3 (1%) are inconclusive. [0 (0%) / 3 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=885384. The leading edge was at b=882366 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.34% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
After 4 days:
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 16 (GFN-21)
(As of 2019-12-16 07:15:31 UTC)
12562 tasks have been sent out. [CPU/GPU/anonymous_platform: 7378 (59%) / 5184 (41%) / 0 (0%)]
Of those tasks that have been sent out:
1596 (13%) were aborted. [1387 (11%) / 209 (2%) / 0 (0%)]
4330 (34%) came back with some kind of an error. [2191 (17%) / 2139 (17%) / 0 (0%)]
2822 (22%) have returned a successful result. [895 (7%) / 1927 (15%) / 0 (0%)]
3814 (30%) are still in progress. [2905 (23%) / 909 (7%) / 0 (0%)]
Of the tasks that have been returned successfully:
1464 (52%) are pending validation. [460 (16%) / 1004 (36%) / 0 (0%)]
1329 (47%) have been successfully validated. [429 (15%) / 900 (32%) / 0 (0%)]
9 (0%) were invalid. [0 (0%) / 9 (0%) / 0 (0%)]
20 (1%) are inconclusive. [6 (0%) / 14 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=511402. The leading edge was at b=494424 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.43% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 17 (GFN-22)
(As of 2019-12-16 07:15:32 UTC)
1816 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 1814 (100%) / 2 (0%)]
Of those tasks that have been sent out:
40 (2%) were aborted. [0 (0%) / 39 (2%) / 1 (0%)]
1109 (61%) came back with some kind of an error. [0 (0%) / 1109 (61%) / 0 (0%)]
312 (17%) have returned a successful result. [0 (0%) / 312 (17%) / 0 (0%)]
355 (20%) are still in progress. [0 (0%) / 354 (19%) / 1 (0%)]
Of the tasks that have been returned successfully:
204 (65%) are pending validation. [0 (0%) / 204 (65%) / 0 (0%)]
102 (33%) have been successfully validated. [0 (0%) / 102 (33%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
6 (2%) are inconclusive. [0 (0%) / 6 (2%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=164664. The leading edge was at b=163228 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.88% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 31 (GFN-DYFL)
(As of 2019-12-16 07:15:32 UTC)
2778 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 2778 (100%) / 0 (0%)]
Of those tasks that have been sent out:
53 (2%) were aborted. [0 (0%) / 53 (2%) / 0 (0%)]
1236 (44%) came back with some kind of an error. [0 (0%) / 1236 (44%) / 0 (0%)]
558 (20%) have returned a successful result. [0 (0%) / 558 (20%) / 0 (0%)]
931 (34%) are still in progress. [0 (0%) / 931 (34%) / 0 (0%)]
Of the tasks that have been returned successfully:
307 (55%) are pending validation. [0 (0%) / 307 (55%) / 0 (0%)]
248 (44%) have been successfully validated. [0 (0%) / 248 (44%) / 0 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
3 (1%) are inconclusive. [0 (0%) / 3 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=885920. The leading edge was at b=882366 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.40% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
We are half way done!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 16 (GFN-21)
(As of 2019-12-17 03:13:30 UTC)
14263 tasks have been sent out. [CPU/GPU/anonymous_platform: 8427 (59%) / 5834 (41%) / 2 (0%)]
Of those tasks that have been sent out:
2095 (15%) were aborted. [1865 (13%) / 229 (2%) / 1 (0%)]
4970 (35%) came back with some kind of an error. [2707 (19%) / 2263 (16%) / 0 (0%)]
3616 (25%) have returned a successful result. [1232 (9%) / 2384 (17%) / 0 (0%)]
3582 (25%) are still in progress. [2623 (18%) / 958 (7%) / 1 (0%)]
Of the tasks that have been returned successfully:
1710 (47%) are pending validation. [582 (16%) / 1128 (31%) / 0 (0%)]
1867 (52%) have been successfully validated. [644 (18%) / 1223 (34%) / 0 (0%)]
13 (0%) were invalid. [1 (0%) / 12 (0%) / 0 (0%)]
26 (1%) are inconclusive. [5 (0%) / 21 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=513998. The leading edge was at b=494424 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 3.96% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 17 (GFN-22)
(As of 2019-12-17 03:13:31 UTC)
2038 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 2036 (100%) / 2 (0%)]
Of those tasks that have been sent out:
47 (2%) were aborted. [0 (0%) / 46 (2%) / 1 (0%)]
1229 (60%) came back with some kind of an error. [0 (0%) / 1229 (60%) / 0 (0%)]
405 (20%) have returned a successful result. [0 (0%) / 404 (20%) / 1 (0%)]
357 (18%) are still in progress. [0 (0%) / 357 (18%) / 0 (0%)]
Of the tasks that have been returned successfully:
228 (56%) are pending validation. [0 (0%) / 228 (56%) / 0 (0%)]
167 (41%) have been successfully validated. [0 (0%) / 166 (41%) / 1 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
10 (2%) are inconclusive. [0 (0%) / 10 (2%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=164932. The leading edge was at b=163228 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.04% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 31 (GFN-DYFL)
(As of 2019-12-17 03:13:31 UTC)
3079 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 3079 (100%) / 0 (0%)]
Of those tasks that have been sent out:
59 (2%) were aborted. [0 (0%) / 59 (2%) / 0 (0%)]
1318 (43%) came back with some kind of an error. [0 (0%) / 1318 (43%) / 0 (0%)]
890 (29%) have returned a successful result. [0 (0%) / 890 (29%) / 0 (0%)]
812 (26%) are still in progress. [0 (0%) / 812 (26%) / 0 (0%)]
Of the tasks that have been returned successfully:
351 (39%) are pending validation. [0 (0%) / 351 (39%) / 0 (0%)]
533 (60%) have been successfully validated. [0 (0%) / 533 (60%) / 0 (0%)]
2 (0%) were invalid. [0 (0%) / 2 (0%) / 0 (0%)]
4 (0%) are inconclusive. [0 (0%) / 4 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=885920. The leading edge was at b=882366 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.40% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
Ken_g6 Volunteer developer
 Send message
Joined: 4 Jul 06 Posts: 940 ID: 3110 Credit: 265,153,553 RAC: 110,745
                            
|
Are bonuses on these GFN projects being calculated correctly? Or is the initial computation of points not working the same on all cards?
I computed a DYFL on a 750 Ti (I know!) for (a little less than) five days. It did (a little less than) 40% of the work. (I then switched the task to a faster card in the same system to finish.)
Now I'm doing GFN-21 on the same card. It's estimating 2 days (a little less) to finish.
If the 750 Ti did 40% of a DYFL in 5 days, it would have completed in 12.5 for about 950000 credit. That's about 76000 credits/day.
I expect the 750 Ti to complete a GFN-21 in 2 days for about 155000 credits. That's about 77500 credits/day. There's a big margin of error here, but they're about equal.
The GFN-21 has a 20% bonus. Without the bonus it would be about 129000 credits/day. So I'd expect a DYFL to be about 800000 points without bonus, or 1400000 points with 75% bonus!
I do notice they use different algorithms, GFN4 vs. GFN5. But that shouldn't affect the base credit. | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
Are bonuses on these GFN projects being calculated correctly? Or is the initial computation of points not working the same on all cards?
I computed a DYFL on a 750 Ti (I know!) for (a little less than) five days. It did (a little less than) 40% of the work. (I then switched the task to a faster card in the same system to finish.)
Now I'm doing GFN-21 on the same card. It's estimating 2 days (a little less) to finish.
If the 750 Ti did 40% of a DYFL in 5 days, it would have completed in 12.5 for about 950000 credit. That's about 76000 credits/day.
I expect the 750 Ti to complete a GFN-21 in 2 days for about 155000 credits. That's about 77500 credits/day. There's a big margin of error here, but they're about equal.
The GFN-21 has a 20% bonus. Without the bonus it would be about 129000 credits/day. So I'd expect a DYFL to be about 800000 points without bonus, or 1400000 points with 75% bonus!
I do notice they use different algorithms, GFN4 vs. GFN5. But that shouldn't affect the base credit.
Short answer: Yes.
Shortish answer: Different GPUs run different transforms at different speeds, so credit/time tends to vary between hardware.
____________
My lucky number is 75898524288+1 | |
|
Ken_g6 Volunteer developer
 Send message
Joined: 4 Jul 06 Posts: 940 ID: 3110 Credit: 265,153,553 RAC: 110,745
                            
|
Shortish answer: Different GPUs run different transforms at different speeds, so credit/time tends to vary between hardware.
So what's the baseline? CPU? Even on projects that don't allow CPU? | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
Shortish answer: Different GPUs run different transforms at different speeds, so credit/time tends to vary between hardware.
So what's the baseline? CPU? Even on projects that don't allow CPU?
The baseline is whatever GPU I happen to own at the time, so it has changed over time. I do try to normalize the results so it stays as consistent as possible.
____________
My lucky number is 75898524288+1 | |
|
|
Is the Error rate higher than normal?
A Much higher Rate than "3616 (25%) have returned a successful results:
14263 tasks have been sent out. [CPU/GPU/anonymous_platform: 8427 (59%) / 5834 (41%) / 2 (0%)]
Of those tasks that have been sent out:
2095 (15%) were aborted. [1865 (13%) / 229 (2%) / 1 (0%)]
4970 (35%) came back with some kind of an error. [2707 (19%) / 2263 (16%) / 0 (0%)]
3616 (25%) have returned a successful result. [1232 (9%) / 2384 (17%) / 0 (0%)]
3582 (25%) are still in progress. [2623 (18%) / 958 (7%) / 1 (0%)] | |
|
streamVolunteer moderator Project administrator Volunteer developer Volunteer tester Send message
Joined: 1 Mar 14 Posts: 1051 ID: 301928 Credit: 563,881,725 RAC: 1,288
                         
|
Is the Error rate higher than normal?
4970 (35%) came back with some kind of an error. [2707 (19%) / 2263 (16%) / 0 (0%)]
Quite normal for GPU project. It was discussed above - even a single host with wrong setup (e.g. Windows 10 update killed OpenCL drivers) could report hundreds of errors until server bans him.
| |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
6 days done...
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 16 (GFN-21)
(As of 2019-12-18 06:31:17 UTC)
16671 tasks have been sent out. [CPU/GPU/anonymous_platform: 9048 (54%) / 7620 (46%) / 3 (0%)]
Of those tasks that have been sent out:
2649 (16%) were aborted. [2376 (14%) / 272 (2%) / 1 (0%)]
6013 (36%) came back with some kind of an error. [2791 (17%) / 3222 (19%) / 0 (0%)]
4576 (27%) have returned a successful result. [1560 (9%) / 3015 (18%) / 1 (0%)]
3433 (21%) are still in progress. [2321 (14%) / 1111 (7%) / 1 (0%)]
Of the tasks that have been returned successfully:
1775 (39%) are pending validation. [625 (14%) / 1150 (25%) / 0 (0%)]
2745 (60%) have been successfully validated. [925 (20%) / 1819 (40%) / 1 (0%)]
21 (0%) were invalid. [1 (0%) / 20 (0%) / 0 (0%)]
35 (1%) are inconclusive. [9 (0%) / 26 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=514972. The leading edge was at b=494424 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 4.16% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 17 (GFN-22)
(As of 2019-12-18 06:31:18 UTC)
2624 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 2622 (100%) / 2 (0%)]
Of those tasks that have been sent out:
53 (2%) were aborted. [0 (0%) / 52 (2%) / 1 (0%)]
1651 (63%) came back with some kind of an error. [0 (0%) / 1651 (63%) / 0 (0%)]
531 (20%) have returned a successful result. [0 (0%) / 530 (20%) / 1 (0%)]
389 (15%) are still in progress. [0 (0%) / 389 (15%) / 0 (0%)]
Of the tasks that have been returned successfully:
242 (46%) are pending validation. [0 (0%) / 242 (46%) / 0 (0%)]
275 (52%) have been successfully validated. [0 (0%) / 274 (52%) / 1 (0%)]
0 (0%) were invalid. [0 (0%) / 0 (0%) / 0 (0%)]
14 (3%) are inconclusive. [0 (0%) / 14 (3%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=165368. The leading edge was at b=163228 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.31% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 31 (GFN-DYFL)
(As of 2019-12-18 06:31:18 UTC)
3438 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 3438 (100%) / 0 (0%)]
Of those tasks that have been sent out:
63 (2%) were aborted. [0 (0%) / 63 (2%) / 0 (0%)]
1419 (41%) came back with some kind of an error. [0 (0%) / 1419 (41%) / 0 (0%)]
1174 (34%) have returned a successful result. [0 (0%) / 1174 (34%) / 0 (0%)]
782 (23%) are still in progress. [0 (0%) / 782 (23%) / 0 (0%)]
Of the tasks that have been returned successfully:
394 (34%) are pending validation. [0 (0%) / 394 (34%) / 0 (0%)]
769 (66%) have been successfully validated. [0 (0%) / 769 (66%) / 0 (0%)]
3 (0%) were invalid. [0 (0%) / 3 (0%) / 0 (0%)]
8 (1%) are inconclusive. [0 (0%) / 8 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=886304. The leading edge was at b=882366 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.45% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
After 7 days:
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 16 (GFN-21)
(As of 2019-12-19 05:33:55 UTC)
18032 tasks have been sent out. [CPU/GPU/anonymous_platform: 9412 (52%) / 8616 (48%) / 4 (0%)]
Of those tasks that have been sent out:
2754 (15%) were aborted. [2430 (13%) / 323 (2%) / 1 (0%)]
6366 (35%) came back with some kind of an error. [2792 (15%) / 3574 (20%) / 0 (0%)]
5492 (30%) have returned a successful result. [1927 (11%) / 3563 (20%) / 2 (0%)]
3420 (19%) are still in progress. [2263 (13%) / 1156 (6%) / 1 (0%)]
Of the tasks that have been returned successfully:
1844 (34%) are pending validation. [675 (12%) / 1169 (21%) / 0 (0%)]
3573 (65%) have been successfully validated. [1237 (23%) / 2334 (42%) / 2 (0%)]
28 (1%) were invalid. [2 (0%) / 26 (0%) / 0 (0%)]
47 (1%) are inconclusive. [13 (0%) / 34 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=517338. The leading edge was at b=494424 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 4.63% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 17 (GFN-22)
(As of 2019-12-19 05:33:56 UTC)
3027 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 3025 (100%) / 2 (0%)]
Of those tasks that have been sent out:
61 (2%) were aborted. [0 (0%) / 60 (2%) / 1 (0%)]
1918 (63%) came back with some kind of an error. [0 (0%) / 1918 (63%) / 0 (0%)]
612 (20%) have returned a successful result. [0 (0%) / 611 (20%) / 1 (0%)]
436 (14%) are still in progress. [0 (0%) / 436 (14%) / 0 (0%)]
Of the tasks that have been returned successfully:
267 (44%) are pending validation. [0 (0%) / 267 (44%) / 0 (0%)]
332 (54%) have been successfully validated. [0 (0%) / 331 (54%) / 1 (0%)]
1 (0%) were invalid. [0 (0%) / 1 (0%) / 0 (0%)]
12 (2%) are inconclusive. [0 (0%) / 12 (2%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=165624. The leading edge was at b=163228 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.47% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 31 (GFN-DYFL)
(As of 2019-12-19 05:33:56 UTC)
3704 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 3704 (100%) / 0 (0%)]
Of those tasks that have been sent out:
78 (2%) were aborted. [0 (0%) / 78 (2%) / 0 (0%)]
1480 (40%) came back with some kind of an error. [0 (0%) / 1480 (40%) / 0 (0%)]
1432 (39%) have returned a successful result. [0 (0%) / 1432 (39%) / 0 (0%)]
714 (19%) are still in progress. [0 (0%) / 714 (19%) / 0 (0%)]
Of the tasks that have been returned successfully:
368 (26%) are pending validation. [0 (0%) / 368 (26%) / 0 (0%)]
1038 (72%) have been successfully validated. [0 (0%) / 1038 (72%) / 0 (0%)]
4 (0%) were invalid. [0 (0%) / 4 (0%) / 0 (0%)]
22 (2%) are inconclusive. [0 (0%) / 22 (2%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=886810. The leading edge was at b=882366 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.50% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
Just two days remaining...
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 16 (GFN-21)
(As of 2019-12-20 04:20:30 UTC)
19641 tasks have been sent out. [CPU/GPU/anonymous_platform: 9825 (50%) / 9811 (50%) / 5 (0%)]
Of those tasks that have been sent out:
2883 (15%) were aborted. [2525 (13%) / 357 (2%) / 1 (0%)]
6851 (35%) came back with some kind of an error. [2814 (14%) / 4037 (21%) / 0 (0%)]
6412 (33%) have returned a successful result. [2259 (12%) / 4150 (21%) / 3 (0%)]
3495 (18%) are still in progress. [2227 (11%) / 1267 (6%) / 1 (0%)]
Of the tasks that have been returned successfully:
1968 (31%) are pending validation. [697 (11%) / 1270 (20%) / 1 (0%)]
4355 (68%) have been successfully validated. [1542 (24%) / 2811 (44%) / 2 (0%)]
35 (1%) were invalid. [2 (0%) / 33 (1%) / 0 (0%)]
54 (1%) are inconclusive. [18 (0%) / 36 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=519936. The leading edge was at b=494424 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.16% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 17 (GFN-22)
(As of 2019-12-20 04:20:31 UTC)
3442 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 3440 (100%) / 2 (0%)]
Of those tasks that have been sent out:
63 (2%) were aborted. [0 (0%) / 62 (2%) / 1 (0%)]
2200 (64%) came back with some kind of an error. [0 (0%) / 2200 (64%) / 0 (0%)]
749 (22%) have returned a successful result. [0 (0%) / 748 (22%) / 1 (0%)]
430 (12%) are still in progress. [0 (0%) / 430 (12%) / 0 (0%)]
Of the tasks that have been returned successfully:
268 (36%) are pending validation. [0 (0%) / 268 (36%) / 0 (0%)]
465 (62%) have been successfully validated. [0 (0%) / 464 (62%) / 1 (0%)]
4 (1%) were invalid. [0 (0%) / 4 (1%) / 0 (0%)]
12 (2%) are inconclusive. [0 (0%) / 12 (2%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=165974. The leading edge was at b=163228 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.68% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 31 (GFN-DYFL)
(As of 2019-12-20 04:20:31 UTC)
3937 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 3937 (100%) / 0 (0%)]
Of those tasks that have been sent out:
113 (3%) were aborted. [0 (0%) / 113 (3%) / 0 (0%)]
1538 (39%) came back with some kind of an error. [0 (0%) / 1538 (39%) / 0 (0%)]
1663 (42%) have returned a successful result. [0 (0%) / 1663 (42%) / 0 (0%)]
623 (16%) are still in progress. [0 (0%) / 623 (16%) / 0 (0%)]
Of the tasks that have been returned successfully:
353 (21%) are pending validation. [0 (0%) / 353 (21%) / 0 (0%)]
1281 (77%) have been successfully validated. [0 (0%) / 1281 (77%) / 0 (0%)]
8 (0%) were invalid. [0 (0%) / 8 (0%) / 0 (0%)]
21 (1%) are inconclusive. [0 (0%) / 21 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=887144. The leading edge was at b=882366 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.54% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
There's less than one day to go!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 16 (GFN-21)
(As of 2019-12-21 09:47:49 UTC)
21805 tasks have been sent out. [CPU/GPU/anonymous_platform: 10343 (47%) / 11455 (53%) / 7 (0%)]
Of those tasks that have been sent out:
3235 (15%) were aborted. [2822 (13%) / 412 (2%) / 1 (0%)]
7387 (34%) came back with some kind of an error. [2900 (13%) / 4487 (21%) / 0 (0%)]
7730 (35%) have returned a successful result. [2690 (12%) / 5035 (23%) / 5 (0%)]
3453 (16%) are still in progress. [1931 (9%) / 1521 (7%) / 1 (0%)]
Of the tasks that have been returned successfully:
2123 (27%) are pending validation. [737 (10%) / 1385 (18%) / 1 (0%)]
5512 (71%) have been successfully validated. [1933 (25%) / 3575 (46%) / 4 (0%)]
48 (1%) were invalid. [3 (0%) / 45 (1%) / 0 (0%)]
47 (1%) are inconclusive. [17 (0%) / 30 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=523142. The leading edge was at b=494424 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 5.81% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 17 (GFN-22)
(As of 2019-12-21 09:47:50 UTC)
3878 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 3876 (100%) / 2 (0%)]
Of those tasks that have been sent out:
95 (2%) were aborted. [0 (0%) / 94 (2%) / 1 (0%)]
2474 (64%) came back with some kind of an error. [0 (0%) / 2474 (64%) / 0 (0%)]
932 (24%) have returned a successful result. [0 (0%) / 931 (24%) / 1 (0%)]
377 (10%) are still in progress. [0 (0%) / 377 (10%) / 0 (0%)]
Of the tasks that have been returned successfully:
295 (32%) are pending validation. [0 (0%) / 295 (32%) / 0 (0%)]
614 (66%) have been successfully validated. [0 (0%) / 613 (66%) / 1 (0%)]
5 (1%) were invalid. [0 (0%) / 5 (1%) / 0 (0%)]
18 (2%) are inconclusive. [0 (0%) / 18 (2%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=166396. The leading edge was at b=163228 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.94% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 31 (GFN-DYFL)
(As of 2019-12-21 09:47:50 UTC)
4187 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 4187 (100%) / 0 (0%)]
Of those tasks that have been sent out:
139 (3%) were aborted. [0 (0%) / 139 (3%) / 0 (0%)]
1603 (38%) came back with some kind of an error. [0 (0%) / 1603 (38%) / 0 (0%)]
1983 (47%) have returned a successful result. [0 (0%) / 1983 (47%) / 0 (0%)]
462 (11%) are still in progress. [0 (0%) / 462 (11%) / 0 (0%)]
Of the tasks that have been returned successfully:
305 (15%) are pending validation. [0 (0%) / 305 (15%) / 0 (0%)]
1644 (83%) have been successfully validated. [0 (0%) / 1644 (83%) / 0 (0%)]
13 (1%) were invalid. [0 (0%) / 13 (1%) / 0 (0%)]
21 (1%) are inconclusive. [0 (0%) / 21 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=887576. The leading edge was at b=882366 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.59% as much as it had prior to the challenge!
____________
My lucky number is 75898524288+1 | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
With less than a day remaining in the challenge, it's time to remind everyone...
At the Conclusion of the Challenge
When the challenge completes, we would prefer users "moving on" to finish those tasks they have downloaded, if not then please ABORT the WU's (and then UPDATE the PrimeGrid project) instead of DETACHING, RESETTING, or PAUSING.
ABORTING WU's allows them to be recycled immediately; thus a much faster "clean up" to the end of a Challenge. DETACHING, RESETTING, and PAUSING WU's causes them to remain in limbo until they EXPIRE. Therefore, we must wait until WU's expire to send them out to be completed.
Likewise, if you're shutting down the computer for an extended period of time, or deleting the VM (Virtual Machine), please ABORT all remaining tasks first. Also, be aware that merely shutting off a cloud server doesn't stop the billing. You have to destroy/delete the server if you don't want to continue to be charged for it.
Thank you!
____________
My lucky number is 75898524288+1 | |
|
|
Late solstice this year (December 22, 04:19 UTC).
Every time we do not have a leap day (29 days in February), the solstice etc. moves approximately 6 hours later. When we do have a leap day (extra 24 hours inserted in calendar year), the net result is that solstice moves approximately 18 hours earlier.
In 2020, the December solstice will be at December 21, 10:02 UTC.
/JeppeSN | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
And we're done! Great job everyone.
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 16 (GFN-21)
(As of 2019-12-22 05:18:29 UTC)
22869 tasks have been sent out. [CPU/GPU/anonymous_platform: 10525 (46%) / 12336 (54%) / 8 (0%)]
Of those tasks that have been sent out:
3415 (15%) were aborted. [2902 (13%) / 512 (2%) / 1 (0%)]
7620 (33%) came back with some kind of an error. [2925 (13%) / 4695 (21%) / 0 (0%)]
8834 (39%) have returned a successful result. [2979 (13%) / 5850 (26%) / 5 (0%)]
2922 (13%) are still in progress. [1703 (7%) / 1218 (5%) / 1 (0%)]
Of the tasks that have been returned successfully:
2118 (24%) are pending validation. [716 (8%) / 1402 (16%) / 0 (0%)]
6605 (75%) have been successfully validated. [2240 (25%) / 4360 (49%) / 5 (0%)]
55 (1%) were invalid. [4 (0%) / 51 (1%) / 0 (0%)]
56 (1%) are inconclusive. [19 (0%) / 37 (0%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=524750. The leading edge was at b=494424 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 6.13% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 17 (GFN-22)
(As of 2019-12-22 05:18:30 UTC)
4155 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 4153 (100%) / 2 (0%)]
Of those tasks that have been sent out:
101 (2%) were aborted. [0 (0%) / 100 (2%) / 1 (0%)]
2693 (65%) came back with some kind of an error. [0 (0%) / 2693 (65%) / 0 (0%)]
1033 (25%) have returned a successful result. [0 (0%) / 1032 (25%) / 1 (0%)]
323 (8%) are still in progress. [0 (0%) / 323 (8%) / 0 (0%)]
Of the tasks that have been returned successfully:
317 (31%) are pending validation. [0 (0%) / 317 (31%) / 0 (0%)]
689 (67%) have been successfully validated. [0 (0%) / 688 (67%) / 1 (0%)]
7 (1%) were invalid. [0 (0%) / 7 (1%) / 0 (0%)]
20 (2%) are inconclusive. [0 (0%) / 20 (2%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=166546. The leading edge was at b=163228 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 2.03% as much as it had prior to the challenge!
Challenge: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice
App: 31 (GFN-DYFL)
(As of 2019-12-22 05:18:30 UTC)
4280 tasks have been sent out. [CPU/GPU/anonymous_platform: 0 (0%) / 4280 (100%) / 0 (0%)]
Of those tasks that have been sent out:
150 (4%) were aborted. [0 (0%) / 150 (4%) / 0 (0%)]
1640 (38%) came back with some kind of an error. [0 (0%) / 1640 (38%) / 0 (0%)]
2181 (51%) have returned a successful result. [0 (0%) / 2181 (51%) / 0 (0%)]
304 (7%) are still in progress. [0 (0%) / 304 (7%) / 0 (0%)]
Of the tasks that have been returned successfully:
273 (13%) are pending validation. [0 (0%) / 273 (13%) / 0 (0%)]
1872 (86%) have been successfully validated. [0 (0%) / 1872 (86%) / 0 (0%)]
17 (1%) were invalid. [0 (0%) / 17 (1%) / 0 (0%)]
19 (1%) are inconclusive. [0 (0%) / 19 (1%) / 0 (0%)]
The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is b=887662. The leading edge was at b=882366 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.60% as much as it had prior to the challenge!
We'll have the challenge schedule for 202 available soon, We'll give you enough time to get ready, so it won't be at the beginning of January. Until then, Happy New Year everyone!
See you in 2020!
____________
My lucky number is 75898524288+1 | |
|
|
Thank You for The Race ... and Congratulations to both ... Czech National Team ... and Mr. Svantner ... sincerely, Grzegorz Roman Granowski ... ( TSBT ) ...
____________
| |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
Now the cleanup begins. It will probably take 2 to 4 months.
Cleanup Status:
Dec 22: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 2785 tasks outstanding; 2496 affecting individual (252) scoring positions; 1520 affecting team (55) scoring positions.
Dec 23: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 2281 tasks outstanding; 2058 affecting individual (240) scoring positions; 1202 affecting team (51) scoring positions.
Dec 24: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 2074 tasks outstanding; 1875 affecting individual (228) scoring positions; 1093 affecting team (49) scoring positions.
Dec 25: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1937 tasks outstanding; 1755 affecting individual (225) scoring positions; 1037 affecting team (48) scoring positions.
Dec 26: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1843 tasks outstanding; 1669 affecting individual (219) scoring positions; 987 affecting team (44) scoring positions.
Dec 27: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1777 tasks outstanding; 1617 affecting individual (218) scoring positions; 959 affecting team (44) scoring positions.
Dec 28: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1727 tasks outstanding; 1576 affecting individual (215) scoring positions; 929 affecting team (42) scoring positions.
Dec 29: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1664 tasks outstanding; 1523 affecting individual (214) scoring positions; 848 affecting team (41) scoring positions.
Dec 30: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1605 tasks outstanding; 1468 affecting individual (210) scoring positions; 816 affecting team (40) scoring positions.
Dec 31: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1562 tasks outstanding; 1432 affecting individual (209) scoring positions; 792 affecting team (40) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
Michael Goetz Volunteer moderator Project administrator
 Send message
Joined: 21 Jan 10 Posts: 14037 ID: 53948 Credit: 477,161,398 RAC: 289,514
                               
|
The cleanup will probably take 2 to 4 months.
Cleanup Status:
Dec 22: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 2785 tasks outstanding; 2496 affecting individual (252) scoring positions; 1520 affecting team (55) scoring positions.
Dec 31: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1562 tasks outstanding; 1432 affecting individual (209) scoring positions; 792 affecting team (40) scoring positions.
Jan 1: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1513 tasks outstanding; 1364 affecting individual (206) scoring positions; 744 affecting team (40) scoring positions.
Jan 2: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1466 tasks outstanding; 1326 affecting individual (205) scoring positions; 724 affecting team (39) scoring positions.
Jan 3: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1439 tasks outstanding; 1302 affecting individual (204) scoring positions; 710 affecting team (37) scoring positions.
____________
My lucky number is 75898524288+1 | |
|
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 375 ID: 764476 Credit: 46,579,215 RAC: 13,727
                 
|
Cleanup Status:
Jan 5: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1295 tasks outstanding; 1163 affecting individual (192) scoring positions; 635 affecting team (33) scoring positions.
Jan 6: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1216 tasks outstanding; 1076 affecting individual (185) scoring positions; 547 affecting team (31) scoring positions.
Jan 7: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1138 tasks outstanding; 1008 affecting individual (181) scoring positions; 510 affecting team (31) scoring positions.
Jan 8: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 1034 tasks outstanding; 910 affecting individual (170) scoring positions; 479 affecting team (29) scoring positions.
Jan 9: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 975 tasks outstanding; 846 affecting individual (163) scoring positions; 394 affecting team (27) scoring positions.
Jan 10: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 905 tasks outstanding; 759 affecting individual (158) scoring positions; 302 affecting team (24) scoring positions.
Jan 11: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 824 tasks outstanding; 690 affecting individual (152) scoring positions; 278 affecting team (24) scoring positions.
Jan 12: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 738 tasks outstanding; 600 affecting individual (143) scoring positions; 246 affecting team (22) scoring positions.
Jan 13: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 648 tasks outstanding; 519 affecting individual (136) scoring positions; 139 affecting team (21) scoring positions.
Jan 14: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 581 tasks outstanding; 460 affecting individual (127) scoring positions; 120 affecting team (20) scoring positions.
Jan 15: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 536 tasks outstanding; 415 affecting individual (116) scoring positions; 108 affecting team (18) scoring positions.
Jan 16: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 483 tasks outstanding; 374 affecting individual (110) scoring positions; 99 affecting team (18) scoring positions.
Jan 17: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 446 tasks outstanding; 319 affecting individual (105) scoring positions; 94 affecting team (17) scoring positions.
Jan 18: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 419 tasks outstanding; 287 affecting individual (100) scoring positions; 84 affecting team (16) scoring positions.
Jan 19: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 393 tasks outstanding; 257 affecting individual (96) scoring positions; 81 affecting team (16) scoring positions.
Jan 20: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 376 tasks outstanding; 234 affecting individual (93) scoring positions; 80 affecting team (16) scoring positions.
Jan 21: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 357 tasks outstanding; 220 affecting individual (89) scoring positions; 75 affecting team (16) scoring positions.
Jan 22: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 342 tasks outstanding; 210 affecting individual (87) scoring positions; 71 affecting team (16) scoring positions.
Jan 23: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 329 tasks outstanding; 186 affecting individual (84) scoring positions; 68 affecting team (15) scoring positions.
Jan 24: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 311 tasks outstanding; 174 affecting individual (82) scoring positions; 65 affecting team (15) scoring positions.
Jan 25: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 299 tasks outstanding; 167 affecting individual (79) scoring positions; 63 affecting team (15) scoring positions.
Jan 26: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 288 tasks outstanding; 160 affecting individual (77) scoring positions; 62 affecting team (15) scoring positions.
Jan 27: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 269 tasks outstanding; 151 affecting individual (75) scoring positions; 60 affecting team (14) scoring positions.
Jan 28: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 254 tasks outstanding; 138 affecting individual (72) scoring positions; 57 affecting team (14) scoring positions.
Jan 29: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 229 tasks outstanding; 121 affecting individual (67) scoring positions; 54 affecting team (14) scoring positions.
Jan 30: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 205 tasks outstanding; 107 affecting individual (63) scoring positions; 50 affecting team (14) scoring positions.
Jan 31: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 180 tasks outstanding; 91 affecting individual (56) scoring positions; 45 affecting team (13) scoring positions. | |
|
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 375 ID: 764476 Credit: 46,579,215 RAC: 13,727
                 
|
Cleanup Status:
Feb 1: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 173 tasks outstanding; 88 affecting individual (54) scoring positions; 42 affecting team (12) scoring positions.
Feb 2: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 160 tasks outstanding; 79 affecting individual (48) scoring positions; 38 affecting team (11) scoring positions.
Feb 3: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 148 tasks outstanding; 66 affecting individual (46) scoring positions; 33 affecting team (10) scoring positions.
Feb 4: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 121 tasks outstanding; 51 affecting individual (39) scoring positions; 25 affecting team (7) scoring positions.
Feb 5: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 112 tasks outstanding; 41 affecting individual (32) scoring positions; 23 affecting team (6) scoring positions.
Feb 6: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 99 tasks outstanding; 40 affecting individual (31) scoring positions; 20 affecting team (6) scoring positions.
Feb 7: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 90 tasks outstanding; 38 affecting individual (30) scoring positions; 19 affecting team (6) scoring positions.
Feb 8: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 86 tasks outstanding; 35 affecting individual (29) scoring positions; 17 affecting team (6) scoring positions.
Feb 9: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 80 tasks outstanding; 31 affecting individual (27) scoring positions; 15 affecting team (6) scoring positions.
Feb 10: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 68 tasks outstanding; 29 affecting individual (25) scoring positions; 13 affecting team (6) scoring positions.
Feb 11: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 63 tasks outstanding; 26 affecting individual (22) scoring positions; 13 affecting team (6) scoring positions.
Feb 12: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 57 tasks outstanding; 23 affecting individual (19) scoring positions; 11 affecting team (5) scoring positions.
Feb 13: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 54 tasks outstanding; 19 affecting individual (17) scoring positions; 10 affecting team (5) scoring positions.
Feb 14: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 48 tasks outstanding; 17 affecting individual (15) scoring positions; 6 affecting team (4) scoring positions.
Feb 15: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 48 tasks outstanding; 17 affecting individual (15) scoring positions; 6 affecting team (4) scoring positions.
Feb 16: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 43 tasks outstanding; 14 affecting individual (13) scoring positions; 5 affecting team (3) scoring positions.
Feb 17: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 42 tasks outstanding; 13 affecting individual (12) scoring positions; 5 affecting team (3) scoring positions.
Feb 18: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 37 tasks outstanding; 12 affecting individual (11) scoring positions; 1 affecting team (1) scoring positions.
Feb 19: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 29 tasks outstanding; 5 affecting individual (5) scoring positions; 0 affecting team (0) scoring positions.
Feb 20: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 26 tasks outstanding; 2 affecting individual (2) scoring positions; 0 affecting team (0) scoring positions.
Feb 21: Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice: 21 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions. | |
|
Michael Gutierrez Volunteer moderator Project administrator Project scientist
 Send message
Joined: 21 Mar 17 Posts: 375 ID: 764476 Credit: 46,579,215 RAC: 13,727
                 
|
The results are final!
Top three individuals:
1: Viktor Svantner
2: tng*
3: ChelseaOilman
Top three teams:
1: Czech National Team
2: Sicituradastra.
3: Aggie The Pew
Congratulations to the winners, and thanks to all participants for making my first challenge as Challenge Coordinator a success! | |
|
|
Great !
Current Overall Standings updated.
____________
"Accidit in puncto, quod non contingit in anno."
Something that does not occur in a year may, perchance, happen in a moment. | |
|
Message boards :
Number crunching :
Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice Challenge |