N-body updated to 0.2
log in

Advanced search

Message boards : News : N-body updated to 0.2

Author Message
Matt Arsenault
Volunteer moderator
Project developer
Project tester
Project scientist
Send message
Joined: 8 May 10
Posts: 576
Credit: 15,979,383
RAC: 0

Message 42954 - Posted: 19 Oct 2010, 4:18:33 UTC

Report any problems here. These won't validate against the older versions since part of the likelihood calculation changed.

Jim Weisert
Send message
Joined: 18 Nov 07
Posts: 2
Credit: 831,101
RAC: 0

Message 42956 - Posted: 19 Oct 2010, 5:06:48 UTC - in response to Message 42954.

Is the version 0.2 or 0.02? On the "Applications" page, it's listed as 0.02, and my BOINC manager seems to be having problems downloading the 0.2 version for Windows (32 bit).

Matt Arsenault
Volunteer moderator
Project developer
Project tester
Project scientist
Send message
Joined: 8 May 10
Posts: 576
Credit: 15,979,383
RAC: 0

Message 42957 - Posted: 19 Oct 2010, 5:16:11 UTC - in response to Message 42956.

Is the version 0.2 or 0.02? On the "Applications" page, it's listed as 0.02, and my BOINC manager seems to be having problems downloading the 0.2 version for Windows (32 bit).


It's supposed to be 0.2. I have no idea why the page is reporting it as 0.02.

Matt Arsenault
Volunteer moderator
Project developer
Project tester
Project scientist
Send message
Joined: 8 May 10
Posts: 576
Credit: 15,979,383
RAC: 0

Message 42958 - Posted: 19 Oct 2010, 5:51:35 UTC

Now at 0.21 because I am good at releases.

Also new visible features include an OpenMP version on OS X. There would be a Linux one but I ran into a mysterious issue with my Linux BOINC libraries. MinGW seems to not support OpenMP, so Windows will be later.

Profile [AF>EDLS] Polynesia
Avatar
Send message
Joined: 5 Apr 09
Posts: 71
Credit: 6,120,786
RAC: 0

Message 42972 - Posted: 19 Oct 2010, 18:25:59 UTC - in response to Message 42958.

hello,

How to receive, because right now I only have 0.07?

Perhaps with a link to the file this under 0.21 and a change in the app_info would suffice?

thank you


____________
Team Alliance francophone, boinc: 7.0.18

GA-P55-UD5, i7 860, Win 7 64 bits, 8g DDR3, GTX 470

Emanuel
Send message
Joined: 18 Nov 07
Posts: 280
Credit: 2,442,757
RAC: 0

Message 42976 - Posted: 19 Oct 2010, 21:10:14 UTC - in response to Message 42958.

Probably won't make any difference, but are you using the TDM-GCC builds? (for MinGW)

Len LE/GE
Send message
Joined: 8 Feb 08
Posts: 261
Credit: 104,050,322
RAC: 0

Message 42978 - Posted: 19 Oct 2010, 21:57:49 UTC - in response to Message 42972.
Last modified: 19 Oct 2010, 22:01:58 UTC

hello,

How to receive, because right now I only have 0.07?

Perhaps with a link to the file this under 0.21 and a change in the app_info would suffice?

thank you



For Windows 7 x64:
milkyway_nbody_0.21_windows_x86_64__sse2.exe

And replace the part for nbody in your app_info.xml with:

<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.21_windows_intelx86_64__sse2.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>21</version_num>
<file_ref>
<file_name>milkyway_nbody_0.21_windows_intelx86_64__sse2.exe</file_name>
<main_program/>
</file_ref>
</app_version>

Profile [AF>EDLS] Polynesia
Avatar
Send message
Joined: 5 Apr 09
Posts: 71
Credit: 6,120,786
RAC: 0

Message 42986 - Posted: 19 Oct 2010, 23:17:14 UTC - in response to Message 42976.

Probably won't make any difference, but are you using the TDM-GCC builds? (for MinGW)


This question is for whom?
____________
Team Alliance francophone, boinc: 7.0.18

GA-P55-UD5, i7 860, Win 7 64 bits, 8g DDR3, GTX 470

Profile [AF>EDLS] Polynesia
Avatar
Send message
Joined: 5 Apr 09
Posts: 71
Credit: 6,120,786
RAC: 0

Message 42987 - Posted: 19 Oct 2010, 23:17:40 UTC - in response to Message 42978.

hello,

How to receive, because right now I only have 0.07?

Perhaps with a link to the file this under 0.21 and a change in the app_info would suffice?

thank you



For Windows 7 x64:
milkyway_nbody_0.21_windows_x86_64__sse2.exe

And replace the part for nbody in your app_info.xml with:

<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.21_windows_intelx86_64__sse2.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>21</version_num>
<file_ref>
<file_name>milkyway_nbody_0.21_windows_intelx86_64__sse2.exe</file_name>
<main_program/>
</file_ref>
</app_version>


Thanks You

____________
Team Alliance francophone, boinc: 7.0.18

GA-P55-UD5, i7 860, Win 7 64 bits, 8g DDR3, GTX 470

Emanuel
Send message
Joined: 18 Nov 07
Posts: 280
Credit: 2,442,757
RAC: 0

Message 43016 - Posted: 20 Oct 2010, 16:02:21 UTC - in response to Message 42986.

Probably won't make any difference, but are you using the TDM-GCC builds? (for MinGW)


This question is for whom?

For Matt, in reply to:
MinGW seems to not support OpenMP, so Windows will be later.

Matt Arsenault
Volunteer moderator
Project developer
Project tester
Project scientist
Send message
Joined: 8 May 10
Posts: 576
Credit: 15,979,383
RAC: 0

Message 43018 - Posted: 20 Oct 2010, 16:16:57 UTC - in response to Message 42976.

Probably won't make any difference, but are you using the TDM-GCC builds? (for MinGW)


No, I'm using TakeoffGW and it barely works. The normal MinGW distribution doesn't work at all. I guess I'll try this one too.

Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Send message
Joined: 30 Apr 09
Posts: 95
Credit: 24,003,766
RAC: 0

Message 43119 - Posted: 23 Oct 2010, 21:00:44 UTC

de_nbody_triaxial1_1_25104_1286870135
wuid=164876151

milkywayathome nbody 0.08 Darwin x86_64 double
milkywayathome nbody 0.08 Darwin x86_64 double

..were not similar, so my..

milkywayathome nbody 0.21 Windows x86 double

..made the 3rd result.
..now the other two are well and my result is invalid.

?

____________

Profile [SETI.Germany] Sutaru Tsureku (aka Dirk :-)
Send message
Joined: 30 Apr 09
Posts: 95
Credit: 24,003,766
RAC: 0

Message 43131 - Posted: 24 Oct 2010, 10:54:37 UTC - in response to Message 43119.
Last modified: 24 Oct 2010, 10:56:25 UTC

I answer my own question.. ;-)

First message in this thread:
(...)
These won't validate against the older versions...
(...)


..so it would be well not to have two wingman with old version.
____________

Profile Martin Ryba
Avatar
Send message
Joined: 24 Apr 09
Posts: 11
Credit: 5,298,005
RAC: 1,689

Message 43653 - Posted: 10 Nov 2010, 2:04:40 UTC - in response to Message 42954.

Perusing the logs on one of my (old laptop) crunchers I encountered the message:

11/4/2010 12:47:22 PM Message from server: MilkyWay@Home N-Body Simulation needs 476.84 MB RAM but only 444.98 MB is available for use.

So, it seems the N-body program is getting to be like Cosmology@Home in terms of being a memory hog. In some ways, I think the processing is similar. C@H maps how density fluctuations evolve in a potential field (that responds to the density fluctuations), M@H is mapping how stars evolve/move in a potential field that reacts to the star positions.

Comments?

____________
Better is the enemy of the good. -Voltaire
Never ascribe to malice that which is adequately explained by incompetence. - Napoleon

Matt Arsenault
Volunteer moderator
Project developer
Project tester
Project scientist
Send message
Joined: 8 May 10
Posts: 576
Credit: 15,979,383
RAC: 0

Message 43654 - Posted: 10 Nov 2010, 2:20:59 UTC - in response to Message 43653.

Perusing the logs on one of my (old laptop) crunchers I encountered the message:
[quote]11/4/2010 12:47:22 PM Message from server: MilkyWay@Home N-Body Simulation needs 476.84 MB RAM but only 444.98 MB is available for use.
The N-body doesn't need that much memory. 15MB at most would be a high estimate for the 32k body workunits, which are the current largest.

Chris S
Avatar
Send message
Joined: 20 Sep 08
Posts: 1386
Credit: 186,616,887
RAC: 1

Message 43669 - Posted: 10 Nov 2010, 12:32:27 UTC
Last modified: 10 Nov 2010, 12:33:24 UTC

If it hasn't already been reported, there is a typo in that quoted app_info.xml. The word "intel" is not needed to agree with the name of the file to download.

For Windows 7 x64:
milkyway_nbody_0.21_windows_x86_64__sse2.exe

And replace the part for nbody in your app_info.xml with:

<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.21_windows_intelx86_64__sse2.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>21</version_num>
<file_ref>
<file_name>milkyway_nbody_0.21_windows_intelx86_64__sse2.exe</file_name>
<main_program/>
</file_ref>
</app_version>
____________
Don't drink water, that's the stuff that rusts pipes

Len LE/GE
Send message
Joined: 8 Feb 08
Posts: 261
Credit: 104,050,322
RAC: 0

Message 43706 - Posted: 10 Nov 2010, 22:47:06 UTC - in response to Message 43669.

You are right; I did a copy/paste from my file (for Win32) and made that mistake when modifying for Win64. Sorry for that.

So, here again for both windows versions with correct exe names:

For Win64 it's
milkyway_nbody_0.21_windows_x86_64__sse2

<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.21_windows_x86_64__sse2.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>21</version_num>
<file_ref>
<file_name>milkyway_nbody_0.21_windows_x86_64__sse2.exe</file_name>
<main_program/>
</file_ref>
</app_version>


and for Win32 it's
milkyway_nbody_0.21_windows_intelx86__sse2

<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.21_windows_intelx86__sse2.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>21</version_num>
<file_ref>
<file_name>milkyway_nbody_0.21_windows_intelx86__sse2.exe</file_name>
<main_program/>
</file_ref>
</app_version>

Profile Martin Ryba
Avatar
Send message
Joined: 24 Apr 09
Posts: 11
Credit: 5,298,005
RAC: 1,689

Message 43801 - Posted: 13 Nov 2010, 17:00:32 UTC - in response to Message 43654.

Perusing the logs on one of my (old laptop) crunchers I encountered the message:
[quote]11/4/2010 12:47:22 PM Message from server: MilkyWay@Home N-Body Simulation needs 476.84 MB RAM but only 444.98 MB is available for use.
The N-body doesn't need that much memory. 15MB at most would be a high estimate for the 32k body workunits, which are the current largest.


It happened again, so I think there's an error in the build configuration for the N-body application that it tells BOINC client that it needs that much RAM.
Host Project Date Message
PamLaptop Milkyway@home 11/13/2010 9:12:31 AM Message from server: MilkyWay@Home N-Body Simulation needs 476.84 MB RAM but only 444.98 MB is available for use.

Marty
____________
Better is the enemy of the good. -Voltaire
Never ascribe to malice that which is adequately explained by incompetence. - Napoleon


Post to thread

Message boards : News : N-body updated to 0.2


Main page · Your account · Message boards


Copyright © 2018 AstroInformatics Group