Posts by luz

1) Message boards : Number crunching : Compiling MilkyWay@home (Message 67649) Posted 3 Jul 2018 by luz Post: milkyway_separation works perfectly, 100% validation rate, roughly twice as fast as the stock app. I'm going to start a new account now to get a high daily average.
2) Message boards : Number crunching : Compiling MilkyWay@home (Message 67648) Posted 2 Jul 2018 by luz Post: I've realized that the milkyway_separation executable is the standard MilkyWay@home program. I'm testing that now. Updating the BOINC libraries made no difference for milkyway_nbody.
3) Message boards : Number crunching : Compiling MilkyWay@home (Message 67647) Posted 2 Jul 2018 by luz Post: Thanks for the input; it's a single-threaded version, the code isn't compiled as multi-threaded nor is it intended as such. BOINC spawns an instance for every thread that my CPU has.
4) Message boards : Number crunching : Compiling MilkyWay@home (Message 67642) Posted 1 Jul 2018 by luz Post: I've tried updating the BOINC libraries and recompiling, I notice that the size of the binary has changed, so it's made a difference. I'm currently testing the new build.
5) Message boards : Number crunching : Compiling MilkyWay@home (Message 67641) Posted 30 Jun 2018 by luz Post: Hi, everyone. I'm new to MilkyWay@home. I'm running Linux and I would like to be able to use the optimized binary I compiled for my CPU architecture. It completes WUs faster than the standard binary, but they get marked as invalid. The source I used is the official git clone and I compiled it yesterday. I would love to know how to fix the problem. Any help would be greatly appreciated.