I've updated all the N-body applications to 0.80.

These add a new kind of likelihood calculation (and soon validation method) we're probably going to switch to using that will allow adding GPU versions sometime in the near future (the GPU version is pretty much ready to go, but we need to fiddle with these kinds of issues first).

Since the n-body is statistical, for any simulation the result can be anywhere in a distribution. So far for validation we have relied on the results from any 2 system being identical, but this is more problematic when you try to include GPUs. The new results should be "fuzzier" and more resistant to some other types potential problems the old likelihood calculation could have.

Good to hear!

On my Windows Vista 64 these tasks seem to fail as soon as they are started. They cause Windows to pop and error box and does not clear until the box is acknowledged. Left unattended, they stall in the boinc queue stopping boinc from running another job.

On my 64-bit Unbutu these tasks either give a computation error at the beginning of the task or run very quickly, under a minute.

I'm having a similar problem on a pair on Mac mini computers. One is a Core Duo running Tiger (10.4) and the other is a Core 2 Duo running Leopard (10.5).

---

Plus SETI Classic = 21,082 WUs

I have 3 i7 windows 7 machines and am experiencing the same problem

I'm having a similar problem on a pair on Mac mini computers. One is a Core Duo running Tiger (10.4) and the other is a Core 2 Duo running Leopard (10.5).

I was absurdly careful to avoid that too. I rebuilt it as 0.82

Thanks for the quick attempt to fix things. Unfortunately, both machines are still showing errors after only a few seconds. (Although the Core Duo on Tiger / 10.4 now makes it through a few seconds instead of producing an immediate error.) The separation units are still working properly.

Thanks for the quick attempt to fix things. Unfortunately, both machines are still showing errors after only a few seconds. (Although the Core Duo on Tiger / 10.4 now makes it through a few seconds instead of producing an immediate error.) The separation units are still working properly.

Interesting. -1 processors. I have a guess about this but I might not get to it until Sunday.

Not to worry. I can continue to run the separation units or go to my backup projects. Thanks again.

Not to worry. I can continue to run the separation units or go to my backup projects. Thanks again.

Try 0.84

My first N-Body 0.60 received since the last outage quit with a "Computation Error" at 8 seconds. I have 3 N-body 0.80's in the queue which won't run until tomorrow in the a.m. and 5 N-Body 0.82's...not seeing any 0.84's. Will report back with dispositions tomorrow. iMac 3.4ghz i7 (2600K) 16GB OSX 10.6.8.

:)

Not to worry. I can continue to run the separation units or go to my backup projects. Thanks again.

Try 0.84

I will report back as soon as I can. Since yesterday all I have been able to get is a message from the server saying that the project is shut down for maintenance. It does seem to be intermittent but my timing for trying to get new work units and report finished ones has been bad. It is down when I check and it is up when I'm away (Murphy's Law, no doubt). I'll keep trying.

Not to worry. I can continue to run the separation units or go to my backup projects. Thanks again.

Try 0.84

I will report back as soon as I can. Since yesterday all I have been able to get is a message from the server saying that the project is shut down for maintenance. It does seem to be intermittent but my timing for trying to get new work units and report finished ones has been bad. It is down when I check and it is up when I'm away (Murphy's Law, no doubt). I'll keep trying.

The site has been down for hours now if you didn't know. Most of the server is still off.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

The site has been down for hours now if you didn't know. Most of the server is still off.

I shut everything off since the database was having issues again

Hi,
I have several N-body tasks that went to 100% in a suspiciously short time. I bet that when I download them they will show an error.

When the scheduler is back up do I need to do anything to fix this.

Hi,
I have several N-body tasks that went to 100% in a suspiciously short time. I bet that when I download them they will show an error.

When the scheduler is back up do I need to do anything to fix this.

The current n-body work units are a bit small and are running very quickly.

Yea, I'm getting computation errors almost instantly. I actually had around 10 of these N-body tasks assigned to me after the server went back up and they all just gave a computation error after about 2 seconds.

My first N-Body 0.60 received since the last outage quit with a "Computation Error" at 8 seconds. I have 3 N-body 0.80's in the queue which won't run until tomorrow in the a.m. and 5 N-Body 0.82's...not seeing any 0.84's. Will report back with dispositions tomorrow. iMac 3.4ghz i7 (2600K) 16GB OSX 10.6.8.

:)

Looks like we had another outage overnight, but it looks like things are back up again for the time being...

N-Body update:

My 3 x 0.80's and 5 x 0.82's each processed in less than 30-seconds apiece. Server finally took the returns moments ago and issued a small serving of WU's for the trouble...5 x 0.82 Separations and 1 x 0.84 N-Body Plum.

Well, I'm half-way there. The n-body units are short and are running fine on my Mac mini Core 2 Duo with OS 10.5, but they still error out on the Mac mini Core Duo running OS 10.4 (see above). And thanks to banditwolf for the heads up on the server.