Posts by Temujin

41) Message boards : Number crunching : new WUs (Message 9922) Posted 7 Feb 2009 by Temujin Post: We're having some problem with something hammering the database, which is making the transitioner do nothing, which I think is the issue... trying to track it down. Have you optimised your tables?
42) Message boards : Number crunching : No work being D/Led & no warning messages (Message 9523) Posted 1 Feb 2009 by Temujin Post: My understanding from Logan is that anything less than .02 BOINC will not request work. I've got 3 machines showing DCFs of 0.011, 0.014 & 0.018 - all quite happily downloading WUs
43) Message boards : Number crunching : Is anyone glad with the project? (Message 9348) Posted 29 Jan 2009 by Temujin Post: another for the happy list :-)
44) Message boards : Application Code Discussion : optimized app suggestion (Message 9339) Posted 29 Jan 2009 by Temujin Post: What is the GMLE_BOINC option for? But now I get 6 errors of can not open include file 'boinc_win.h' I defined GMLE_BOINC because it was defined in make.linux :/ and I don't get an error for boinc_win.h so I reckon you've missed some include directories.
45) Message boards : Application Code Discussion : optimized app suggestion (Message 9305) Posted 28 Jan 2009 by Temujin Post: I'm also wondering how the APP_NAME/APP_VERSION stuff is supposed to work. right then, this is how I did it right click on project, select properties, set the configuration box to All configurations, then Configuration Properties, C/C++, Command Line and added them into the Additional Options box with /D "APP_NAME=Temujin" /D "APP_VERSION=0.16" /D "GMLE_BOINC"
46) Message boards : Application Code Discussion : optimized app suggestion (Message 9303) Posted 28 Jan 2009 by Temujin Post: I'm also wondering how the APP_NAME/APP_VERSION stuff is supposed to work. In Linux, that is handled in the Makefile. I'm going to try some more tonight. Yep, its much easier with a makefile :-) I found how to define APP_NAME/APP_VERSION but again I can't remember where I did it. I'll post what I did when I get home tonight
47) Message boards : Application Code Discussion : Recompiled Linux 32/64 apps (Message 9297) Posted 28 Jan 2009 by Temujin Post: I found out that PNI = SSE3 According to this intel document, my Intel Xeon L5420 supports SSE4.1 cat /proc/cpuinfo flags shows - fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl est tm2 xtpr I know pni = SSE3 but how is SSE4.1 indicated?
48) Message boards : Application Code Discussion : optimized app suggestion (Message 9292) Posted 28 Jan 2009 by Temujin Post: I tried. I munged around for 3 hours trying to get WX and then Boinc to compile, only to find that there is NOTHING that tells me how to set up VS to compile milkyway. How do the admins do it? There is a make file for linux and mac. What do you guys do for windows? How is it compiled. Just some general direction to get me going would be appreciated. I'm used to compiling in linux with makefiles, so I'm in the same boat as you. To start with I made a C++ project from source files, pointing VS at the astronomy directory. Somewhere in VS you must be able to specify to compile .c files as c++ but I couldn't find it so renamed all the milkyway .c files to .cpp. Once I did that and recreated the project it came together much better. I found in VS that if you right click the project, select properties, C/C++ General you can add extra include directories, and Library directories in Linker/Genreal Also found to specify libraries somewhere that escapes me, I'll find out tonight. I have no idea if this is the right or wrong way to do it but at least I'm making progress (I think).
49) Message boards : Application Code Discussion : What's needed to compile the app? (Message 9273) Posted 27 Jan 2009 by Temujin Post: I'm attempting to compile the app in winxp with visual studio. Its the first time I've used VS so its slow going but I'm making progress. isn't google wonderful :-)
50) Message boards : Application Code Discussion : GPU app teaser (Message 9233) Posted 26 Jan 2009 by Temujin Post: I agree, excellent work!! I know nvidia cards aren't as fast as ATI for this kind of work but when you have completed the ATI app would you consider a CUDA app?
51) Message boards : Application Code Discussion : How to install the new optimised clients for Linux? (Message 9206) Posted 26 Jan 2009 by Temujin Post: Could we rename this thread How to install the new optimised clients because the method is the same for Linux/Windows/OSX, the only thing that changes is the install directory Common project directories are Windows C:\Program Files\BOINC\projects\milkyway.cs.rpi.edu_milkyway C:\Documents and Settings\All Users\Application Data\BOINC\projects\milkyway.cs.rpi.edu_milkyway Linux ~/BOINC/projects/milkyway.cs.rpi.edu_milkyway /var/lib/boinc-client/projects/milkyway.cs.rpi.edu_milkyway OSX ~/BOINC/projects/milkyway.cs.rpi.edu_milkyway /Library/Application Support/BOINC Data/projects/milkyway.cs.rpi.edu_milkyway Whichever OS you have OS, you copy the contents of the zip/tar file into one of those directories. stop boinc copy the files start boinc
52) Message boards : Application Code Discussion : How to install the new optimised clients for Linux? (Message 9172) Posted 26 Jan 2009 by Temujin Post: sledgehammer to crack a nut time :-) type the following sudo find / -name milkyway.cs.rpi.edu_milkyway and give it the root password, it will then find your milkyway folder STOP BOINC copy the unzipped (or untared) files from speedimics download into that folder start boinc thats normally all that is needed
53) Message boards : Number crunching : app v12 (Message 8947) Posted 24 Jan 2009 by Temujin Post: ok scratch compiling the i686 with sse3 :) NO!!!! SSE3 is ok SSSE3 doesn't work on my T2500 ;-)
54) Message boards : Number crunching : app v12 (Message 8944) Posted 24 Jan 2009 by Temujin Post: You can bump i686-apple-darwin too. The earliest Intel processor in Macs was the Core Duo/Solo, which supported SSSE3 (notice the three S's, not two). So you can enabled all the (S)SSEx optimizations for all Intel Macs. I've just tried an SSSE3 compile and get the following message Fatal Error: This program was not built to run on the processor in your system. The allowed processors are: Intel(R) Core(TM) Duo processors and compatible Intel processors with supplemental Streaming SIMD Extensions 3 (SSSE3) instruction support. So it looks like my T2500 CPU doesn't support SSSE3 :(
55) Message boards : Application Code Discussion : optimized app suggestion (Message 8913) Posted 23 Jan 2009 by Temujin Post: Any Window's Optimized Apps working? @Travis Please could we have a sticky and read-only thread listing optimised apps for the various OS flavours that are approved by the project? The app suppliers could PM you (or other admin) with the results of their efforts and then everyone would have one place to find the latest opti app.
56) Message boards : Application Code Discussion : What's needed to compile the app? (Message 8788) Posted 20 Jan 2009 by Temujin Post: Does anyone have the Intel icpc compiler on Mac? I've compiled a i686 SSE3 app with g++ and while it is faster, its only slightly faster. If we could get it compiled with icpc then I'm sure we could have a much faster app. Anyone?
57) Message boards : Application Code Discussion : source v11 released (Message 8767) Posted 20 Jan 2009 by Temujin Post: The source also has three new test parameters (for stripes 79, 82 and 86, respectively): . . . I've added the set_parameters.sh to automate this, just run ./set_parameters.sh 79 for example. I've been having terrible trouble with fitness results from my app. Speedimic suggested deleting all files produced by running the app against the test WUs and that has corrected my fitness. So, i've amended set_parameters.sh to be rm -f boinc_finish_called rm -f init_data.xml rm -f astronomy_checkpoint rm -f out rm -f stderr.txt cp stars-$1.txt stars.txt cp astronomy_parameters-$1.txt astronomy_parameters.txt cp search_parameters-$1.txt search_parameters.txt that takes care of things automatically
58) Message boards : Number crunching : app v12 (Message 8752) Posted 20 Jan 2009 by Temujin Post: Yep , but you see here , I still have some bad wus ... without changing anything.... I think that the new assimilator/validator has some problem ... for validating wus... I installed speedimics new 64bit SSSE3 opti app on one of my quad cores and it has also suffered from invalid WUs. I've just replaced the SSSE3 app with the SSE3 version, i'll see how that goes. 2 other quads have returned all valid SSSE3 WUs so far.
59) Message boards : Application Code Discussion : What's needed to compile the app? (Message 8654) Posted 19 Jan 2009 by Temujin Post: Thanks for that, just a question, if I modify the app-info.xml file I only have to change the line <version_num>9</version_num> to <version_num>10</version_num> don't I ?? Err.... Probably :/ I didn't edit app_info.xml on any of my rigs, I just let it download more WUs against v0.9 Give it a go and see what happens, remember to stop boinc first though
60) Message boards : Application Code Discussion : What's needed to compile the app? (Message 8648) Posted 19 Jan 2009 by Temujin Post: I tried your application Speedimic, unfortunately it trashed a complete load of work units with the error "Process exited with code 1". that could be because speedimic apps are set for version 0.9 and you had already downloaded WUs marked for app version 0.10. Try it again, let it trash your current WUs and it will then download another set and should work ok it did the same for me edit or amend the app_info.xml to suit the WUs you already have

Previous 20 · Next 20