Posts by Tim Norton

1) Message boards : Number crunching : Computation Errors on new Nvidia 470 (Message 41552) Posted 18 Aug 2010 by Tim Norton Post: Guys turn off gpu in your preferences on the website for the host computer you have your fermi in so you do not get GPU work units for now until the new app is released if you have remaining GPU wu it would be better to abort them and let others get them as resends if you leave the GPU processing it will eat through an large number of wu for no result and they would have to be sent again anyway etc You gpu can work away on SETI etc until the new app is ready Happy Crunching!
2) Message boards : News : windows intelx86 and x86_64 binaries added for the nbody simulations (Message 41551) Posted 18 Aug 2010 by Tim Norton Post: try this one - its for 64bit though its opp apps for both cpu and gpu if what you are after is gPU only then set that in you account preferences or delete out the cpu refernce block below - but boinc will show errors if you do <app_info> <app> <name>milkyway</name> </app> <file_info> <name>astronomy_0.21_x64_SSE3.exe</name> <executable/> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>21</version_num> <file_ref> <file_name>astronomy_0.21_x64_SSE3.exe</file_name> <main_program/> </file_ref> </app_version> <app_version> <app_name>milkyway</app_name> <version_num>20</version_num> <file_ref> <file_name>astronomy_0.21_x64_SSE3.exe</file_name> <main_program/> </file_ref> </app_version> <app> <name>milkyway</name> </app> <file_info> <name>milkyway_0.24_windows_intelx86__cuda23.exe</name> <executable/> </file_info> <file_info> <name>cudart.dll</name> <executable/> </file_info> <file_info> <name>cutil32.dll</name> <executable/> </file_info> <app_version> <app_name>milkyway</app_name> <version_num>24</version_num> <plan_class>cuda23</plan_class> <avg_ncpus>0.040000</avg_ncpus> <max_ncpus>0.040000</max_ncpus> <coproc> <type>CUDA</type> <count>1</count> </coproc> <file_ref> <file_name>milkyway_0.24_windows_intelx86__cuda23.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart.dll</file_name> </file_ref> <file_ref> <file_name>cutil32.dll</file_name> </file_ref> </app_version> </app_info>
3) Message boards : Number crunching : Waiting for validation... (Message 41319) Posted 7 Aug 2010 by Tim Norton Post: That could be true, but I have a lot of WU's from months ago and where done with nVidia cuda. Wingman used ATI or even CPU. A lot of these WU's have at least two "good" results, but we (wingman and me) are not getting the credits for it. I have not been using Milkyway that long but have always been puzzled by the waiting for validation element of the server status page as it never goes below approx 6200 - 6300. Also you would have thought it would vary with wu in the field and wu to be assimilated and the variability of users returning wu on an ad hoc basis Could this possibly be that the validator just keeps missing the completed wu as TJ describes or will only look at new entries hence why there is a base level it does not go below and cant clear the 6000+ backlog? From reading the forums there has it appears been problems with the validator in the past which may (or may not) be a clue All speculation on my part and could be shouting up the incorrect tree on this :)
4) Message boards : Number crunching : Checks for high error count reporting (Message 41305) Posted 6 Aug 2010 by Tim Norton Post: done
5) Message boards : Number crunching : 3rd.in - optimized apps (Message 41293) Posted 6 Aug 2010 by Tim Norton Post: Just a quick update HD 3850 working well on 0.23 ati opp app ave completion time 9:12 not too shabby :) less cpu load than stock app although completion times are only a few seconds quicker on opp app vs stock app
6) Message boards : Number crunching : Checks for high error count reporting (Message 41292) Posted 6 Aug 2010 by Tim Norton Post: Hi was just checking up on progress of my wu and looking at one of my pending results i noticed that one of my wingmen has been returning error results for the last week or so for every wu (or thats all the results i can see) this has amounted to 500+ wu errors while computing with no valid results - looks like the GTX 465 has either the wrong app loaded or some other config error or he needs to use a fermi app (do we have one?) are there checks for this because he is being sent wu on a regular basis and if he does not spot the error and correct it this could continue for a long time with the associated waste of work i have noted his computer number but was not going to "out" him here - is there an admin account i could contact to look into this perhaps?
7) Message boards : Number crunching : 3rd.in - optimized apps (Message 41153) Posted 30 Jul 2010 by Tim Norton Post: Thanks download works now will try 023 when latest downloads have finished crunching T
8) Message boards : Number crunching : 3rd.in - optimized apps (Message 41147) Posted 29 Jul 2010 by Tim Norton Post: Just got my hands on a agp 3850 card for my old cruncher got the latest Cat drivers from ati But looking at the opp apps just have a query on which ones to use CPU is an old Intel(R) Pentium(R) 4 CPU 3.06GHz which has sse2 running win7 32bit looking at the opp apps should i use the 0.22 sse2 amd or the 0.23 sse2 ati its not a amd cpu (unless this is something to do with amd owning ati?) so i should use the 0.23 but when i click on the link at www.arkayn.us the zip file is no longer there could somebody clarify please Ta T