Welcome to MilkyWay@home

Source Code and Optimized FreeBSD Binaries


Advanced search

Message boards : Application Code Discussion : Source Code and Optimized FreeBSD Binaries
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
boinc127

Send message
Joined: 16 Mar 11
Posts: 14
Credit: 689,067
RAC: 1
500 thousand credit badge9 year member badge
Message 63315 - Posted: 2 Apr 2015, 5:06:58 UTC - in response to Message 63314.  

Ya i've had some that validate also. I don't see any kind of recognizable pattern in it either. Its always hard to tell with Milkyway@home because so many workunits come back validation inconclusive, only to be validated later on. Of course it could also be my setup. One of the many risks following a stable FreeBSD branch.
ID: 63315 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Torfinn Ingolfsen

Send message
Joined: 17 Aug 08
Posts: 8
Credit: 3,561,238
RAC: 0
3 million credit badge10 year member badge
Message 63959 - Posted: 1 Oct 2015, 15:19:30 UTC

Hello, it seems that nbody workunits now require version 1.52 of the application:
<search_application> milkyway_nbody 1.48 FreeBSD x86_64 double  , Crlibm </search_application>
Application version too old. Workunit requires version 1.52, but this is 1.48

Any chance of an updated version?
ID: 63959 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Brian Neal

Send message
Joined: 9 Oct 14
Posts: 14
Credit: 1,893,890
RAC: 0
1 million credit badge5 year member badge
Message 64043 - Posted: 27 Oct 2015, 16:58:22 UTC - in response to Message 63959.  

Hello, it seems that nbody workunits now require version 1.52 of the application:
<search_application> milkyway_nbody 1.48 FreeBSD x86_64 double  , Crlibm </search_application>
Application version too old. Workunit requires version 1.52, but this is 1.48

Any chance of an updated version?


Sure thing. I'll do it tonight.
ID: 64043 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Brian Neal

Send message
Joined: 9 Oct 14
Posts: 14
Credit: 1,893,890
RAC: 0
1 million credit badge5 year member badge
Message 64047 - Posted: 30 Oct 2015, 5:59:48 UTC

NBody 1.52 is now available for FreeBSD 10:

https://aceshardware.files.wordpress.com/2015/10/milkyway_1-52_1-36_x86_64-pc-freebsd.zip

milkyway_nbody 1.52:

% make check
Test project milkywayathome_client/nbody/tests
    Start 1: checkpoint_test
1/4 Test #1: checkpoint_test ..................   Passed    2.39 sec
    Start 2: custom_arg_test
2/4 Test #2: custom_arg_test ..................   Passed    7.99 sec
    Start 3: emd_test
3/4 Test #3: emd_test .........................   Passed    0.80 sec
    Start 4: invalid_input_test
4/4 Test #4: invalid_input_test ...............   Passed   19.99 sec

100% tests passed, 0 tests failed out of 4

Total Test time (real) =  31.18 sec
Built target check


Cheers!

-Brian
ID: 64047 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Torfinn Ingolfsen

Send message
Joined: 17 Aug 08
Posts: 8
Credit: 3,561,238
RAC: 0
3 million credit badge10 year member badge
Message 64067 - Posted: 6 Nov 2015, 18:56:11 UTC

Thanks!. I have been running it for a few days now, and it runs well - no issues discovered.
ID: 64067 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Brian Neal

Send message
Joined: 9 Oct 14
Posts: 14
Credit: 1,893,890
RAC: 0
1 million credit badge5 year member badge
Message 64370 - Posted: 10 Mar 2016, 18:57:35 UTC

I've been getting failures recently, so I'm going to look into updating nbody to 1.56 tonight.
ID: 64370 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Torfinn Ingolfsen

Send message
Joined: 17 Aug 08
Posts: 8
Credit: 3,561,238
RAC: 0
3 million credit badge10 year member badge
Message 66164 - Posted: 7 Feb 2017, 19:49:50 UTC

Quick question: should the latest binaries in this thread work on FreeBSD 10.3-stable?
I recently upgraded my BOINC machine to
root@kg-vm# uname -a
FreeBSD kg-vm.kg4.no 10.3-STABLE FreeBSD 10.3-STABLE #0 r311695: Sun Jan 8 20:58:02 CET 2017 root@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
and the newest boinc client in ports
root@kg-vm# pv boinc*
[Reading data from pkg(8) ... - 58 packages found - done]
boinc-client-7.2.33_7 = up-to-date with port

I have attached to the project, but it doesn't look like I get any work.
root@kg-vm# l projects/milkyway.cs.rpi.edu_milkyway/
./ milkyway_nbody_1.52_x86_64-pc-freebsd*
../ milkyway_separation_1.36_x86_64-pc-freebsd*
app_info.xml

Do I need something more with the new BOINC client?
ID: 66164 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
haegga

Send message
Joined: 5 Aug 10
Posts: 2
Credit: 2,276,912
RAC: 0
2 million credit badge9 year member badge
Message 66173 - Posted: 10 Feb 2017, 21:12:32 UTC

Hello,

I also try to bring milkyway back to life on FreeBSD. I got two boxes FreeBSD 10.3 with boinc (7.7.0 x86_64-pc-freebsd)

I have two issues, the first one I am not able to build nbody, I get an error when linking the binary, please see below.

Separation seems to build fine, I also can compute WU but there always getting invalid.

Anyone some idea what to do?

Stderr output

<core_client_version>7.7.0</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkyway_separation 1.44 FreeBSD x86_64 double </search_application>
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' 
Switching to Parameter File 'astronomy_parameters.txt'
<number_WUs> 5 </number_WUs>
<number_params_per_WU> 20 </number_params_per_WU>
Using SSE4.1 path
Integral 0 time = 1220.132963 s
Running likelihood with 84046 stars
Likelihood time = 2.580050 s
<background_integral> 0.000212866612270 </background_integral>
<stream_integral>  11.052744949797388  817.159170372060885  109.130815816830406 </stream_integral>
<background_likelihood> -4.651561785105243 </background_likelihood>
<stream_only_likelihood>  -113.713296588452295  -4.022403079983629  -3.501974246059814 </stream_only_likelihood>
<search_likelihood> -3.082695565964225 </search_likelihood>
Using SSE4.1 path
Integral 0 time = 1233.598307 s
Running likelihood with 84046 stars
Likelihood time = 3.603997 s
<background_integral1> 0.000212838144066 </background_integral1>
<stream_integral1>  10.949244652008920  817.659233980863860  109.205496211738037 </stream_integral1>
<background_likelihood1> -4.652624660762022 </background_likelihood1>
<stream_only_likelihood1>  -113.787381713235703  -4.023628756096747  -3.501600699887517 </stream_only_likelihood1>
<search_likelihood1> -3.082856795761225 </search_likelihood1>
Using SSE4.1 path
Integral 0 time = 1239.927631 s
Running likelihood with 84046 stars
Likelihood time = 1.593017 s
<background_integral2> 0.000212834447340 </background_integral2>
<stream_integral2>  10.954161682689559  816.244744521691587  109.376219097210296 </stream_integral2>
<background_likelihood2> -4.653054044135508 </background_likelihood2>
<stream_only_likelihood2>  -113.807643297739105  -4.021327776051136  -3.502784073758317 </stream_only_likelihood2>
<search_likelihood2> -3.082891112561942 </search_likelihood2>
Using SSE4.1 path
Integral 0 time = 1250.308573 s
Running likelihood with 84046 stars
Likelihood time = 2.588594 s
<background_integral3> 0.000212862165641 </background_integral3>
<stream_integral3>  10.870168995888916  817.232504983257968  109.438116761323883 </stream_integral3>
<background_likelihood3> -4.651197615823827 </background_likelihood3>
<stream_only_likelihood3>  -114.034937992900211  -4.022429172397606  -3.502372349440707 </stream_only_likelihood3>
<search_likelihood3> -3.083007996963124 </search_likelihood3>
Using SSE4.1 path
Integral 0 time = 1236.596065 s
Running likelihood with 84046 stars
Likelihood time = 3.594462 s
<background_integral4> 0.000212858052620 </background_integral4>
<stream_integral4>  10.986189707954960  816.009265169384435  109.246791527447158 </stream_integral4>
<background_likelihood4> -4.651493592344064 </background_likelihood4>
<stream_only_likelihood4>  -114.019642801570100  -4.021332873418171  -3.502477991411791 </stream_only_likelihood4>
<search_likelihood4> -3.082910409934012 </search_likelihood4>
08:39:49 (86179): called boinc_finish(0)

</stderr_txt>
]]>




##### NBODY build problem


cmake ../milkywayathome_client -DBOINC_RELEASE_NAMES=ON -DSEPARATION=ON -DNBODY_OPENMP=OFF -DSEPARATION_OPENCL=OFF -DCMAKE_C_COMPILER=gcc49 -DCMAKE_CXX_COMPILER=clang -DNBODY=ON

Scanning dependencies of target milkyway_nbody
[100%] Building C object nbody/CMakeFiles/milkyway_nbody.dir/src/main.c.o
/milkywayathome_client/nbody/src/main.c:205:29: warning: missing field 'verbose' initializer [-Wmissing-field-initializers]
    static NBodyFlags nbf = EMPTY_NBODY_FLAGS;
                            ^
/milkywayathome_client/nbody/include/nbody.h:81:148: note: expanded from macro 'EMPTY_NBODY_FLAGS'
#define EMPTY_NBODY_FLAGS { NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }
                                                                                                                                                   ^
/milkywayathome_client/nbody/src/main.c:525:32: warning: unused parameter 'numThreads' [-Wunused-parameter]
static int nbSetNumThreads(int numThreads)
                               ^
2 warnings generated.
[100%] Linking CXX executable ../bin/milkyway_nbody_1.62_amd64-unknown-freebsd
../lib/libnbody.a(nbody_caustic.c.o): In function `causticHaloAccel':
/milkywayathome_client/nbody/src/nbody_caustic.c:(.text+0x2b2): undefined reference to `cpow'
/milkywayathome_client/nbody/src/nbody_caustic.c:(.text+0x9a4): undefined reference to `cpow'
/milkywayathome_client/nbody/src/nbody_caustic.c:(.text+0x10a7): undefined reference to `cpow'
/milkywayathome_client/nbody/src/nbody_caustic.c:(.text+0x1780): undefined reference to `cpow'
../lib/libnbody.a(nbody_caustic.c.o): In function `f4':
/milkywayathome_client/nbody/src/nbody_caustic.c:(.text+0x26c7): undefined reference to `cpow'
../lib/libnbody.a(nbody_caustic.c.o):/milkywayathome_client/nbody/src/nbody_caustic.c:(.text+0x292e): more undefined references to `cpow' follow
c++: error: linker command failed with exit code 1 (use -v to see invocation)
*** Error code 1

Stop.
make[2]: stopped in /build
*** Error code 1

Stop.
make[1]: stopped in /build
*** Error code 1

Stop.
make: stopped in /build
ID: 66173 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Brian Neal

Send message
Joined: 9 Oct 14
Posts: 14
Credit: 1,893,890
RAC: 0
1 million credit badge5 year member badge
Message 66203 - Posted: 18 Feb 2017, 10:29:11 UTC

NBody took a bit of massaging to build. I have a set of diffs that I'll post up soon. As for separation, it tends to work so long as you are running with a custom app_info.xml.
ID: 66203 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
haegga

Send message
Joined: 5 Aug 10
Posts: 2
Credit: 2,276,912
RAC: 0
2 million credit badge9 year member badge
Message 66212 - Posted: 21 Feb 2017, 18:29:27 UTC
Last modified: 21 Feb 2017, 19:24:51 UTC

Great looking forward for the nbody patches.

Can you please have a look at my app file? Maybe I have done something wrong with it? Still unclear for me why my WU are marke es invalid


<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_separation_1.44_amd64-unknown-freebsd</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>144</version_num>
<file_ref>
<file_name>milkyway_separation_1.44_amd64-unknown-freebsd</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>
ID: 66212 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
boinc127

Send message
Joined: 16 Mar 11
Posts: 14
Credit: 689,067
RAC: 1
500 thousand credit badge9 year member badge
Message 66214 - Posted: 23 Feb 2017, 4:07:08 UTC

I tried compiling nbody a while back... basically FreeBSD doesn't implement cpow() in its msun library, and I was never sure how to write the function into the nbody code properly, so that it would compute accurately.

BTW, the Linux 32 bit version of separation does work on FreeBSD with the linuxulator (and it uses the SSE 4.1 path as well). I'm not sure about 64 bit Linux though, I've tried 64 bit Linux binaries before and have never been able to get ANY 64 bit Linux BOINC projects to work with the linuxulator. They all segmentation fault and error out after a few seconds.
ID: 66214 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Previous · 1 · 2

Message boards : Application Code Discussion : Source Code and Optimized FreeBSD Binaries

©2020 Astroinformatics Group