Welcome to MilkyWay@home

N-body updated to 0.80


Advanced search

Message boards : News : N-body updated to 0.80
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3

AuthorMessage
paris
Avatar

Send message
Joined: 26 Apr 08
Posts: 77
Credit: 27,957,001
RAC: 15,899
20 million credit badge10 year member badge
Message 51997 - Posted: 18 Dec 2011, 0:48:06 UTC
Last modified: 18 Dec 2011, 0:51:29 UTC

I don't know for sure what is going on. I just got several new n-body units for my Mac mini Core Duo running Tiger (10.4) and they are continuing to error out within seconds. The separation units are fine and everything works on my Core 2 Duo under Leopard (10.5). No rush, just thought you might want to know. Thanks.

I just noticed that it was running version .82. If that makes a difference, what do I need to do to update to either .84 or .88 or whatever works?
ID: 51997 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Matt Arsenault
Volunteer moderator
Project developer
Project tester
Project scientist

Send message
Joined: 8 May 10
Posts: 576
Credit: 15,979,383
RAC: 0
10 million credit badge9 year member badge
Message 52008 - Posted: 18 Dec 2011, 20:59:21 UTC - in response to Message 51997.  

I don't know for sure what is going on. I just got several new n-body units for my Mac mini Core Duo running Tiger (10.4) and they are continuing to error out within seconds. The separation units are fine and everything works on my Core 2 Duo under Leopard (10.5). No rush, just thought you might want to know. Thanks.

I just noticed that it was running version .82. If that makes a difference, what do I need to do to update to either .84 or .88 or whatever works?
You need to be using 0.84 on OS X 10.4 The problem was apparently OpenMP support wasn't added until Leopard so the multithreaded 0.82 ones don't work (the 32bit one was supposed to target 10.4). I just noticed I forgot to mark the old ones thought.
ID: 52008 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
paris
Avatar

Send message
Joined: 26 Apr 08
Posts: 77
Credit: 27,957,001
RAC: 15,899
20 million credit badge10 year member badge
Message 52014 - Posted: 19 Dec 2011, 0:36:06 UTC

OK, thanks. Will this be automatic or do I need to reset, detach and reattach, or something else?
ID: 52014 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Matt Arsenault
Volunteer moderator
Project developer
Project tester
Project scientist

Send message
Joined: 8 May 10
Posts: 576
Credit: 15,979,383
RAC: 0
10 million credit badge9 year member badge
Message 52018 - Posted: 20 Dec 2011, 18:29:50 UTC - in response to Message 52014.  

OK, thanks. Will this be automatic or do I need to reset, detach and reattach, or something else?
Should be
ID: 52018 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
paris
Avatar

Send message
Joined: 26 Apr 08
Posts: 77
Credit: 27,957,001
RAC: 15,899
20 million credit badge10 year member badge
Message 52020 - Posted: 20 Dec 2011, 21:20:57 UTC

Well, it automatically updated to version 84 but it still errors out in about 5 seconds on a Mac mini Core Duo running Tiger (10.4). The separation units are still fine. Fortunately, the time lost is negligible.
ID: 52020 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileSamuel

Send message
Joined: 23 Apr 11
Posts: 2
Credit: 16,856
RAC: 0
10 thousand credit badge8 year member badge
Message 52581 - Posted: 20 Jan 2012, 9:09:44 UTC

How can i get mor of these tasks? i only get 1- this task is finished after 10 seconds, then i have to wait 1 minute for a new one.
it would be fine to get 100 of these tasks or so...
ID: 52581 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Kurt*

Send message
Joined: 19 Dec 11
Posts: 2
Credit: 37,497
RAC: 0
10 thousand credit badge7 year member badge
Message 53489 - Posted: 29 Feb 2012, 9:55:30 UTC

Off topic but, I couldn't post a new thread.

I have a question about: task duration correction factor which can be seen by me in a finished work unit when I select my computer ID.

I thought I read somewhere here that the # won't go below a (1) when I view mine they are sitting at 0.022553 how did this happen?

ID: 53489 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilebanditwolf
Avatar

Send message
Joined: 12 Nov 07
Posts: 2425
Credit: 524,164
RAC: 0
500 thousand credit badge10 year member badge
Message 53495 - Posted: 29 Feb 2012, 18:48:11 UTC - in response to Message 53489.  

Off topic but, I couldn't post a new thread.

I have a question about: task duration correction factor which can be seen by me in a finished work unit when I select my computer ID.

I thought I read somewhere here that the # won't go below a (1) when I view mine they are sitting at 0.022553 how did this happen?


The n-body tasks were wwaaaayyy off on the estimated run time. I'm guessing they still are, but I haven't had any of those since the new server went up. I would have an estimate of 4-6 hours and they would run 30 min to 40+ hours.
Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.
ID: 53495 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Kurt*

Send message
Joined: 19 Dec 11
Posts: 2
Credit: 37,497
RAC: 0
10 thousand credit badge7 year member badge
Message 53514 - Posted: 2 Mar 2012, 11:28:11 UTC - in response to Message 53495.  

Thanks for your reply!
ID: 53514 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Previous · 1 · 2 · 3

Message boards : News : N-body updated to 0.80

©2019 Astroinformatics Group