Posts by WimTea

1) Message boards : Number crunching : Validation inconclusive? (Message 40344) Posted 11 Jun 2010 by WimTea Post: Tx for the referal Elton. I did scan the forum for anything on it. Wasn't so bright at that time though to look at the news section or use the search option... Having read the thread I am confident my hosts are 90%+ of the time producing valid results. I still would like to be able though to check the error rate every now and then, just to make sure. In the thread Travis mentioned he was going to look into making the error rate visible, he even mentioned it shouldn't be too hard. Any news on that?
2) Message boards : Number crunching : Validation inconclusive? (Message 40337) Posted 11 Jun 2010 by WimTea Post: Haven't noticed this earlier, but all my comps seem to consequently have a few recent WUs with status "completed but validation inconclusive", eg. http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=116149431 Judged by runtime and claimed credits they all seem fine. I haven't been able to 'catch' one whose wingman got finished, so I cannot tell how they validated in the end. The wingman are of all varieties (comp & program). Does anyone know what is going on? How these WU tend to validate?
3) Message boards : Number crunching : Why No Work? (Message 31212) Posted 19 Sep 2009 by WimTea Post: Looks like the validator needs to be kicked again. Once that happens WUs will flow again aplenty (I hope).
4) Message boards : Number crunching : Invalidated WUs?? (Message 30669) Posted 13 Sep 2009 by WimTea Post: Travis posted this in the 11th. However on my host these units were from the 12th around 20:30 UT till this morning around 07:30 UTC. Just this single host, my other hosts got non of these units. Seems to be fine now though, guess it was sorted out.
5) Message boards : Number crunching : Invalidated WUs?? (Message 30659) Posted 13 Sep 2009 by WimTea Post: My host 46925 suddenly has the 9.somethng WUs ps_constrainted_82_2s_4 and gs_constrainted_82_2s_4 invalidated. I've been OC'ing this host a bit but can't think of why only these WUs are affected. Anyone else got these invalidated too? I'll try running one without OC'ing in the meantime. [edit] gotta ca(t)ch(e) one first ofcourse and I don't really feel like trashing a perfectly OK cache...
6) Message boards : Number crunching : Temporary Availability of the ATI application through BOINC (Message 30658) Posted 13 Sep 2009 by WimTea Post: Mega LOL! Still dreaming of a HD4870, should never have gotten that slightly cheaper NV9600... Will have to wait for a HD9876 or something moneywise now.
7) Message boards : Number crunching : No work?! (Message 29979) Posted 30 Aug 2009 by WimTea Post: Looks like the validater stopped around 10:00 UTC, possibly a bit later. All the WUs uploaded from my comps after that are still pending. Guess the process creating WUs stopped as a result of the stopped validator or something like tha.t. Labbies 6 WUS look to me like some of the always present few resents which somehow still get resent. We'll find out sooner or later but ofcourse we prefer to hear from Travis or see WUs flowing again sooner rather than later :).
8) Message boards : Number crunching : No work?! (Message 29946) Posted 30 Aug 2009 by WimTea Post: Looks like a few hours ago the problems started as stated in this thread. Guess we'll find out, won't we... My comps run several projects, so they'll catch up on the missed MW WUs later.
9) Message boards : Number crunching : No work?! (Message 29940) Posted 30 Aug 2009 by WimTea Post: Caches are depleting and nothing is coming in. http://milkyway.cs.rpi.edu/milkyway/server_status.php reports 0 ready to send :( .
10) Message boards : Number crunching : New sgr WUs slower on P4? (Message 24362) Posted 6 Jun 2009 by WimTea Post: My good ol' P4 1.8 seems to take about twice as long for s1 and s2 sgr WUs than for the comparable short and long ones we had before. This is also reflected in the credits claimed. My Q9550 however seems to take only marginally longer than before. Anyone have the same results? And/or info on why this increase seems to affect my P4 only?
11) Message boards : Number crunching : Server Updates and Status (Message 17101) Posted 29 Mar 2009 by WimTea Post: At least the web pages are up :) Progress is progress. From the server page, looks like 5 of the services aren't running. How 'bout that, 2 posts in the same second. Nice...
12) Message boards : Number crunching : Server Updates and Status (Message 17100) Posted 29 Mar 2009 by WimTea Post: Looks like MW is almost back again... Just the server that "can't attach shared memory"... 5 more minutes maybe?!?!
13) Message boards : Number crunching : Returned Invalid Result WHY?? (Message 15317) Posted 14 Mar 2009 by WimTea Post: Had 1 too in a looooong time: <core_client_version>6.6.9</core_client_version> <![CDATA[ <stderr_txt> Running Milkyway@home version 0.19 by Gipsel CPU: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz (4 cores/threads) 2.84 GHz (261ms) WU completed. It took 736.141 seconds CPU time and 815.468 seconds wall clock time @ 2.84 GHz. </stderr_txt> ]]> app version 0.19
14) Message boards : Number crunching : 3rd.in - optimized apps (Message 11504) Posted 18 Feb 2009 by WimTea Post: The Boinc client works just fine for quite a while now on that single core host. It's still Crunch3rs v6.1.0 as it ran on my dual core comps and I wanted all comps to run the same CC. Reminds me it's time to synchronize all of them one of these days... Anyway I just took a look at the particular host and it happens to run another abnormally long WU. It's at 1:45 now, where they usually take 15 to 20 mins. I'll keep an eye on it. Looking at the resultlust for the host I found another one. Took 1:20, validated OK though.
15) Message boards : Number crunching : 3rd.in - optimized apps (Message 11264) Posted 17 Feb 2009 by WimTea Post: Had to abort a WU that ran on a host running the SSE2 zslip.com code after 6.155 seconds... It was the second one in two days. If anyone is interested, I caught the stderrout this time: <core_client_version>6.1.0</core_client_version> <![CDATA[ <message> aborted by user </message> <stderr_txt> Unhandled Exception Detected... - Unhandled Exception Record - Reason: Breakpoint Encountered (0x80000003) at address 0x7C901230 Engaging BOINC Windows Runtime Debugger... ******************** BOINC Windows Runtime Debugger Version 6.3.11 Dump Timestamp : 02/17/09 22:52:31 Install Directory : C:\Program Files\BOINC\ Data Directory : C:\Program Files\BOINC Project Symstore : Loaded Library : C:\Program Files\BOINC\\dbghelp.dll Loaded Library : C:\Program Files\BOINC\\symsrv.dll Loaded Library : C:\Program Files\BOINC\\srcsrv.dll LoadLibraryA( C:\Program Files\BOINC\\version.dll ): GetLastError = 126 Loaded Library : version.dll Debugger Engine : 4.0.5.0 Symbol Search Path: C:\Program Files\BOINC\slots\0;C:\Program Files\BOINC\projects\milkyway.cs.rpi.edu_milkyway;srvC:\WINDOWS\TEMP\symbolshttp://msdl.microsoft.com/download/symbols;srvC:\WINDOWS\TEMP\symbolshttp://boinc.berkeley.edu/symstore ModLoad: 00400000 000eb000 C:\Program Files\BOINC\projects\milkyway.cs.rpi.edu_milkyway\astronomy_0.16_SSE2.exe (-nosymbols- Symbols Loaded) ModLoad: 7c900000 000b6000 C:\WINDOWS\system32\ntdll.dll (5.1.2600.2180) (-exported- Symbols Loaded) File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) Company Name : Microsoft Corporation Product Name : Besturingssysteem Microsoft? Windows? Product Version : 5.1.2600.2180 ModLoad: 7c800000 000ff000 C:\WINDOWS\system32\kernel32.dll (5.1.2600.3119) (-exported- Symbols Loaded) File Version : 5.1.2600.3119 (xpsp_sp2_gdr.070416-1301) Company Name : Microsoft Corporation Product Name : Besturingssysteem Microsoft? Windows? Product Version : 5.1.2600.3119 ModLoad: 7e390000 00090000 C:\WINDOWS\system32\USER32.dll (5.1.2600.3099) (-exported- Symbols Loaded) File Version : 5.1.2600.3099 (xpsp_sp2_gdr.070308-0222) Company Name : Microsoft Corporation Product Name : Besturingssysteem Microsoft? Windows? Product Version : 5.1.2600.3099 ModLoad: 77e40000 00048000 C:\WINDOWS\system32\GDI32.dll (5.1.2600.3466) (-exported- Symbols Loaded) File Version : 5.1.2600.3466 (xpsp_sp2_gdr.081022-1254) Company Name : Microsoft Corporation Product Name : Microsoft? Windows? Operating System Product Version : 5.1.2600.3466 ModLoad: 77f40000 000ab000 C:\WINDOWS\system32\ADVAPI32.dll (5.1.2600.2180) (-exported- Symbols Loaded) File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) Company Name : Microsoft Corporation Product Name : Besturingssysteem Microsoft? Windows? Product Version : 5.1.2600.2180 ModLoad: 77da0000 00092000 C:\WINDOWS\system32\RPCRT4.dll (5.1.2600.3173) (-exported- Symbols Loaded) File Version : 5.1.2600.3173 (xpsp_sp2_gdr.070709-0051) Company Name : Microsoft Corporation Product Name : Microsoft? Windows? Operating System Product Version : 5.1.2600.3173 ModLoad: 77f10000 00011000 C:\WINDOWS\system32\Secur32.dll (5.1.2600.2180) (-exported- Symbols Loaded) File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) Company Name : Microsoft Corporation Product Name : Microsoft? Windows? Operating System Product Version : 5.1.2600.2180 ModLoad: 03000000 00115000 C:\Program Files\BOINC\dbghelp.dll (6.6.7.5) (-exported- Symbols Loaded) File Version : 6.6.0007.5 (debuggers(dbg).051021-1446) Company Name : Microsoft Corporation Product Name : Debugging Tools for Windows(R) Product Version : 6.6.0007.5 ModLoad: 77be0000 00058000 C:\WINDOWS\system32\msvcrt.dll (7.0.2600.2180) (-exported- Symbols Loaded) File Version : 7.0.2600.2180 (xpsp_sp2_rtm.040803-2158) Company Name : Microsoft Corporation Product Name : Microsoft? Windows? Operating System Product Version : 7.0.2600.2180 ModLoad: 01d00000 00083000 C:\Program Files\BOINC\symsrv.dll (6.6.7.5) (-exported- Symbols Loaded) File Version : 6.6.0007.5 (debuggers(dbg).051021-1446) Company Name : Microsoft Corporation Product Name : Debugging Tools for Windows(R) Product Version : 6.6.0007.5 ModLoad: 01000000 0003a000 C:\Program Files\BOINC\srcsrv.dll (6.6.7.5) (-exported- Symbols Loaded) File Version : 6.6.0007.5 (debuggers(dbg).051021-1446) Company Name : Microsoft Corporation Product Name : Debugging Tools for Windows(R) Product Version : 6.6.0007.5 ModLoad: 77bd0000 00008000 C:\WINDOWS\system32\version.dll (5.1.2600.2180) (-exported- Symbols Loaded) File Version : 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158) Company Name : Microsoft Corporation Product Name : Microsoft? Windows? Operating System Product Version : 5.1.2600.2180 * Dump of the Process Statistics: * - I/O Operations Counters - Read: 479, Write: 0, Other 91 - I/O Transfers Counters - Read: 0, Write: 309, Other 0 - Paged Pool Usage - QuotaPagedPoolUsage: 16272, QuotaPeakPagedPoolUsage: 16444 QuotaNonPagedPoolUsage: 1592, QuotaPeakNonPagedPoolUsage: 1592 - Virtual Memory Usage - VirtualSize: 20119552, PeakVirtualSize: 20119552 - Pagefile Usage - PagefileUsage: 3788800, PeakPagefileUsage: 3788800 - Working Set Size - WorkingSetSize: 4300800, PeakWorkingSetSize: 4300800, PageFaultCount: 1046 * Dump of thread ID 1356 (state: Ready): * - Information - Status: Base Priority: Unknown, Priority: Unknown, , Kernel Time: 0.000000, User Time: 0.000000, Wait Time: 51884712.000000 - Unhandled Exception Record - Reason: Breakpoint Encountered (0x80000003) at address 0x7C901230 - Registers - eax=00000001 ebx=00000000 ecx=0044722e edx=0000613c esi=00000000 edi=00000000 eip=7c901230 esp=00b3fb90 ebp=00b3ffec cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202 - Callstack - ChildEBP RetAddr Args to Child 00b3ffec 00000000 00408ee0 00000000 00000000 00000008 ntdll!DbgBreakPoint+0x0 * Dump of thread ID 3168 (state: Ready): * - Information - Status: Base Priority: Above Normal, Priority: Above Normal, , Kernel Time: 2031250.000000, User Time: 61555781632.000000, Wait Time: 51884712.000000 - Registers - eax=0012f8e0 ebx=003d6ea1 ecx=18bc12ab edx=00915b88 esi=ffffffff edi=c0c3a3c8 eip=0044081e esp=0012f8dc ebp=0012fd78 cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000286 - Callstack - ChildEBP RetAddr Args to Child 0012fd78 00401482 00408ee0 00000000 7c90e64e 7c80c136 astronomy_0.16_SSE2!+0x0 0012fd84 7c90e64e 7c80c136 00000000 3ff00000 00d48ea0 astronomy_0.16_SSE2!+0x0 00000000 00000000 00000000 00000000 00000000 00000000 ntdll!NtSetInformationThread+0x0 * Debug Message Dump * Foreground Window Data *** Window Name : Window Class : Window Process ID: 0 Window Thread ID : 0 Exiting... </stderr_txt> ]]>
16) Message boards : Number crunching : Insta-Purge (Message 10725) Posted 14 Feb 2009 by WimTea Post: Since the probs seem to be solved it would be nice if insta-purge is converted to say in-an-hour-purge to start with. Or are we not there yet?
17) Message boards : Application Code Discussion : source v0.18 (Message 10723) Posted 14 Feb 2009 by WimTea Post: Guess i'll have to install some nix real soon now on my new quad... It runs XP64 after a few tries with drivers and stuff, but tx to a crappy GPU bios (reports itself as an engineering version, would you believe that?) I have no GPU crunching atm. Now I only need a few 'recreational' hours (plus a few, plus a few, hey it's IT...) to install nix. Any recommendations for the flavour? I'm not a total newbie, did some AIX sysadm in my early days (and not only smitty). But I would also like to use some regular programs like a spreadsheet, mail, photoeditor and stuff.
18) Message boards : Application Code Discussion : milkyway code license (Message 8656) Posted 19 Jan 2009 by WimTea Post: There is also the issue to consider that there are two kind of optimizations, sourcecode based and runtime based. The discussion in this thread is mainly about the sourcecode. I support Paul D. Buck's reasoning on this. As long as someone develops and uses modifications and, for whatever reason, doesn't publicize them there will be no benefits to other users and there will be the possibility of incorrect computations turning up and thus the difficulties to weed these out. A different form of optimization is altering the runtime software. This includes using different compilerflags, using a different compiler altogether and manual optimizing the compiled code. IMO especially manual optimizations can add to the difficulty of figuring out incorrect computations. Just like no open source licensing model can force publication of changes to sourcecode, no (any!) licensing model can prevent changes to be made (and used) to runtime software. In the end all depends on the willingness of people to share enhancements, which is the main idea behind any open source licensing model. In the end also incorrect results are, well, incorrect results no matter the reason they were generated. This also includes random events like an overheated CPU or faulty RAM. A mechanism is needed to weed all these results out. Well known mechanisms are the use of redundancy and checks made by the validator. Redundancy has well known pros and cons, the usefullness of a validator strongly depends on the science of and algorithms used by a particular project. Another mechanism is to ignore results from specific hosts or specific users. These unfortunately have to be coded somewhere, eg in the validator. So in the end I think yes, an open source license will definitely help getting less incorrect computations but also no, it won't be the silver bullet that prevents all incorrect computations, some manual labor will always be needed for this.
19) Message boards : Cafe MilkyWay : Eagles Football Fans? (Message 7983) Posted 24 Dec 2008 by WimTea Post: I'm a bit of a fan of the Eagles too, except that it's officially called the Go Ahead Eagles over here :). Fansite is here. Handy if you understand Dutch btw.
20) Message boards : Number crunching : post milkyway_windows_intelx86 problems here (Message 7737) Posted 14 Dec 2008 by WimTea Post: Just a very minor glitch to report. I allowed a host attached to MW a couple of weeks ago to crunch some MWs. However BOINC couldn't download the executable astronomy_1.22_V3_win32.exe... The most likely candidate is astronomy_1.22_windows_intel86.exe, but this is of the wrong size when I compare it with one of my other Win32 hosts... And AFAIK we are running milkyway_0.7_windows_intelx86.exe now. Luckily there is the oh so often last resolve: reset the project. So I did and everything is working fine now. To help people in the same circumstances as me but not so advanced in using BOINC I'd like to suggest putting the right .exe back.

Next 20