Welcome to MilkyWay@home

Compiling MilkyWay@home


Advanced search

Message boards : Number crunching : Compiling MilkyWay@home
Message board moderation

To post messages, you must log in.

AuthorMessage
luz

Send message
Joined: 8 Jun 18
Posts: 5
Credit: 652,082
RAC: 0
500 thousand credit badge
Message 67641 - Posted: 30 Jun 2018, 14:55:07 UTC

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.
ID: 67641 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
luz

Send message
Joined: 8 Jun 18
Posts: 5
Credit: 652,082
RAC: 0
500 thousand credit badge
Message 67642 - Posted: 1 Jul 2018, 7:34:52 UTC - in response to Message 67641.  

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.
ID: 67642 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
alanb1951

Send message
Joined: 16 Mar 10
Posts: 35
Credit: 30,255,641
RAC: 9,409
30 million credit badge9 year member badgeextraordinary contributions badge
Message 67643 - Posted: 2 Jul 2018, 1:25:56 UTC - in response to Message 67642.  

As no-one else has offered anything, a thought or two. (If you've already been through all this, my apologies.)

Whilst I've never tried building a MilkyWay program, especially not a multi-threaded one(!), I can't help wondering whether you're having problems because you've built an MT version and it's only getting to use one core...

Now, I don't know whether that's a build issue, a problem with the way your version is being fired up by BOINC or something else, but if I'd been doing the builds that's what I'd be looking at.

By the way, there is also a non-MT version, and if the source of that is also available it might be worth fetching that, building it and seeing if that also gives Invalids -- that might help you discover whether it's a build issue or something else...

Unfortunately, I have no idea as to what you might do to sort out a build issue; as I said, I've never tried building the NBody application...

Good luck getting it sorted.

P.S. Nice system!
ID: 67643 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
luz

Send message
Joined: 8 Jun 18
Posts: 5
Credit: 652,082
RAC: 0
500 thousand credit badge
Message 67647 - Posted: 2 Jul 2018, 19:28:26 UTC - in response to Message 67643.  

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.
ID: 67647 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
luz

Send message
Joined: 8 Jun 18
Posts: 5
Credit: 652,082
RAC: 0
500 thousand credit badge
Message 67648 - Posted: 2 Jul 2018, 22:59:20 UTC - in response to Message 67647.  

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.
ID: 67648 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
luz

Send message
Joined: 8 Jun 18
Posts: 5
Credit: 652,082
RAC: 0
500 thousand credit badge
Message 67649 - Posted: 3 Jul 2018, 1:26:28 UTC - in response to Message 67648.  

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.
ID: 67649 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Compiling MilkyWay@home

©2019 Astroinformatics Group