Hey Everyone,

We will be releasing a new Nbody application this week. This version of the application utilizes a different method of initializing the bodies, sampling a distribution function instead of a potential. This version will hopefully resolve issues many of you have been having.

thanks for your effort.
Lets try asap

---

How can we identify the new version? I really don't want to run nbody until I'm sure the old versions are flushed out of the system.

/Dave

Task 913001117

Eric Findley · log out

Name de_nbody_12_19_orphan_sim_1_1413455402_1430184_0
Workunit 675296482
Created 19 Dec 2014, 22:19:18 UTC
Sent 19 Dec 2014, 22:36:42 UTC
Report deadline 31 Dec 2014, 22:36:42 UTC
Received 20 Dec 2014, 2:38:48 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 15 (0xf) Unknown error number
Computer ID 554457
Run time 15 min 14 sec
CPU time 1 hours 48 min 11 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 33.03 GFLOPS
Application version MilkyWay@Home N-Body Simulation v1.46 (mt)
Peak working set size 18.29 MB
Peak swap size 17.02 MB
Peak disk usage 4.69 MB

Stderr output
<core_client_version>7.4.27</core_client_version>
<![CDATA[
<message>
The system cannot find the drive specified.
(0xf) - exit code 15 (0xf)
</message>
<stderr_txt>
<search_application> milkyway_nbody 1.46 Windows x86_64 double OpenMP, Crlibm </search_application>
Using OpenMP 8 max threads on a system with 8 processors
Error reading histogram line 37: 1 -48.5294117647 0.0439655511 0.0013148967
21:34:07 (4552): called boinc_finish

</stderr_txt>
]]>




Main page · Your account · Message boards


Copyright © 2014 AstroInformatics Group
I have 3 of these recently

---