Welcome to MilkyWay@home

Posts by SETI.USA Cluster

1) Message boards : Number crunching : Invalid WUs (Message 33673)
Posted 24 Nov 2009 by Profile SETI.USA Cluster
Post:
Well that fixed it I think. No invalids for over 2 hours now. Strange that they were both overclocked equally but only one was having the problem. Oh well, full steam ahead again.
2) Message boards : Number crunching : Invalid WUs (Message 33665)
Posted 24 Nov 2009 by Profile SETI.USA Cluster
Post:
Yes Travis. They were both mildly overclocked. I have set them both back to factory default. Let's see what happens now. Thanks.
3) Message boards : Number crunching : Invalid WUs (Message 33655)
Posted 24 Nov 2009 by Profile SETI.USA Cluster
Post:
I am getting about a 10% invalid rate on one of my HD 4850s, but cannot figure out why. The stderror_out text looks exactly the same as for a valid WU. Here is what it looks like:
Name	de_s222_3s_best_4p_05r_22_596170_1259083707_0
Workunit	597171
Created	24 Nov 2009 17:28:30 UTC
Sent	24 Nov 2009 17:29:11 UTC
Received	24 Nov 2009 17:35:17 UTC
Server state	Over
Outcome	Success
Client state	Done
Exit status	0 (0x0)
Computer ID	118608
Report deadline	27 Nov 2009 17:29:11 UTC
Run time	52.78125
stderr out	

<core_client_version>6.10.17</core_client_version>
<![CDATA[
<stderr_txt>
Running Milkyway@home ATI GPU application version 0.20b (Win32, x87, CAL 1.4) by Gipsel
instructed by BOINC client to use device 1
CPU: Pentium(R) Dual-Core  CPU      E5200  @ 2.50GHz (2 cores/threads) 2.63307 GHz (409ms)

CAL Runtime: 1.4.255
Found 2 CAL devices

Device 0: ATI Radeon HD4700/4800 (RV740/RV770) 512 MB local RAM (remote 64 MB cached + 256 MB uncached)
GPU core clock: 700 MHz, memory clock: 993 MHz
800 shader units organized in 10 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads
supporting double precision

Device 1: ATI Radeon HD4700/4800 (RV740/RV770) 512 MB local RAM (remote 64 MB cached + 256 MB uncached)
GPU core clock: 700 MHz, memory clock: 993 MHz
800 shader units organized in 10 SIMDs with 16 VLIW units (5-issue), wavefront size 64 threads
supporting double precision

Starting WU on GPU 1

main integral, 320 iterations
predicted runtime per iteration is 150 ms (33.3333 ms are allowed), dividing each iteration in 5 parts
borders of the domains at 0 320 640 960 1280 1600
Calculated about 8.22242e+012 floatingpoint ops on GPU, 1.23583e+008 on FPU. Approximate GPU time 52.7813 seconds.

probability calculation (stars)
Calculated about 3.34818e+009 floatingpoint ops on FPU.

WU completed.
CPU time: 6.625 seconds,  GPU time: 52.7813 seconds,  wall clock time: 56.508 seconds,  CPU frequency: 2.63308 GHz

</stderr_txt>
]]>

Validate state	Invalid
Claimed credit	0.242683513700349
Granted credit	0
application version	0.20

Does anyone out there see anything I am missing? I can see no reason for it to be invalid.
4) Message boards : Number crunching : new hard drive installed (Message 33631)
Posted 24 Nov 2009 by Profile SETI.USA Cluster
Post:

The irony is that people complained for years about cross-project parity, and when steps are made to try and address that problem more complaints come across :)

Only a few (the so called credit cops) ever complained about high credit and cross-project parity (which is a myth by the way). When you actually start talking about lowering credit, then is when you hear from the masses (read that as majority) of volunteers. And yes, if you lower credits you will see an exodus of volunteers from your project. You can bank on that.

The new credit scheme is honestly just a way to track credit in a project independent manner so when new projects come along they don't have to deal with all the credit issues.

That is not the way I read it. It talked about controlling the credit for all projects from the BOINC software. That takes the choice away from the project admins.

I know you all want to think there's some big brother keeping you down in the credit ranks, but honestly Dave and the rest of us really want to make it so that credit is distributed correctly across projects in some kind of fair manner.

Like I said, taking the choice away from the project admins. So much for "free enterprise"!




©2026 Astroinformatics Group