I was planning on maybe getting PPC applications to work. I got my roommate to bring his G4 to get it working, but I haven't had time to try it yet.

a few examples:

this Milkyway@home 0.40 MilkyWay@Home de_16_2s_5_19106_1286482216_0
22:17:35 (22:13:34) 10/9/2010 4:14:37 PM 10/9/2010 6:00:44 PM Reported: Computation error (0,)

this Milkyway@home 0.40 MilkyWay@Home de_13_2s_5_609171_1286475411_0 21:31:01 (21:27:20) 10/9/2010 1:03:55 PM 10/9/2010 2:00:26 PM Reported: Computation error (0,)

this Milkyway@home 0.40 MilkyWay@Home de_16_3s_5_612076_1286476176_0 20:20:48 (20:16:59) 10/9/2010 12:24:45 PM 10/9/2010 12:54:46 PM Reported: Computation error (0,)

I have the same computation error result.
In the Tasks tab I get this info:

Project - Milkyway@home
Application - Milkyway@Home 0.04
Name - de_14_3s_5_647365_1286570597_0
Elapsed 50:27:26
Progress 100.000%
Status - Computation error

In the Messages tab I get this info:

Milkyway@home 10/11/2010 10:21:17 AM Output file de_14_3s_5_647365_1286570597_0_0 for task de_14_3s_5_647365_1286570597_0 absent

Hi! I'm crunching on WinXp SP3 32 using milkyway version 40.
I've got the same messagem as other guys:
11.10.2010 19:46:25 Milkyway@home Computation for task de_15_3s_5_200586_1286509695_0 finished
11.10.2010 19:46:25 Milkyway@home Output file de_15_3s_5_200586_1286509695_0_0 for task de_15_3s_5_200586_1286509695_0 absent

So, I decided not to download new tasks till the bug would be fixed... :/

Same problem on my G5 since 3 days.

Lun 11 oct 20:07:08 2010 Milkyway@home update requested by user
Lun 11 oct 20:07:08 2010 Milkyway@home Sending scheduler request: Requested by user.
Lun 11 oct 20:07:08 2010 Milkyway@home Requesting new tasks
Lun 11 oct 20:07:10 2010 Milkyway@home Scheduler request completed: got 0 new tasks
Lun 11 oct 20:07:10 2010 Milkyway@home Message from server: No work sent
Lun 11 oct 20:07:10 2010 Milkyway@home Message from server: MilkyWay@Home N-Body Simulation is not available for your type of computer.
Lun 11 oct 20:07:10 2010 Milkyway@home Message from server: MilkyWay@Home is not available for your type of computer.

Both my mac and i7 get allmost done 30 plus hours then get a computational error. I think i will set NNT. Id rather get ghosts from seti than to error out all the time.

---

I think it has a bug. The first task my CPU ran after the update ran to completion and then the upload failed with a Message "Output file ... absent". The task was # 216429150, work unit 163715939, de_11_3s_5_1447892_1286681319_0. It was also predicted to take about 16:14:-- of CPU time, but it took close to 23 hrs. (This is the first time that one of my Milky Way tasks has been more than a little bit over the prediction, and the first error case.) That caused me to monitor the second work unit after it started. It has been running for 16 hrs now (16:14:-- predicted initially) and is only 68.8% done. There is no output file accumulating that I can find, and MW disk usage has not increased during this task. I suspect it is headed for the same fate as the first so I am suspending it and will not allow it or the other 3 in the set of 5 I received to start until the problem is resolved. I received no credit for the failed job.

hey what's up with the tasks... there are all "high priority", it's kind annoying

Would this also explain why I have 4 4-core Xeon systems cranking on MW tasks, and for the past 3 days it looks like no credit has been earned? Some of the tasks are MW 0.04, some are N-Body 0.07. They seem to be completing, a couple are listed as error, one was invalid, and only two are pending. These systems usually get ~1500-2000 cred/day on each machine. Systems running different OS's (Linux, Vista, Win7). None do GPU work.

Like many of you here, my last 4 or 5 WU's crunched on my CPU all ended with "computational error". Each of them took 18 to 20 to crunch before they errored out. They subsequently were crunched and validated by someone else with a GPU. So I am going NNT and aborting all my tasks until this is resolved. I don't mean to sound like a whiner, but continuing to crunch WU's that are just going to error out is just a waste of my time and the project's time. I love crunching for MW and I hope this get resolved soon so I can start up again.

---

Hi Wes! :-) Yes, it's the same story... Here's my last wu's details:

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=215969153

Continuing to crunch WU's that are just going to error out is not just a waste of time, but in some cases even a waste of electricity! Anyway, I always suggest not to run PCs only for BOINC.
Please let us know when it's all ok again. Meanwhile I'll run other projects.

Good work!

The Dreamer

---

I've seen this error for a long time now...should I'd be happy to hang in there for a fix or should I detach...please let me know. Thanks.

Power Macintosh [Power Macintosh Model PowerMac8,1] [AltiVec]

Sat Oct 16 01:48:47 2010 Milkyway@home Sending scheduler request: To fetch work.
Sat Oct 16 01:48:47 2010 Milkyway@home Requesting new tasks
Sat Oct 16 01:48:48 2010 Milkyway@home Scheduler request completed: got 0 new tasks
Sat Oct 16 01:48:48 2010 Milkyway@home Message from server: No work sent
Sat Oct 16 01:48:48 2010 Milkyway@home Message from server: MilkyWay@Home N-Body Simulation is not available for your type of computer.

---

I'm going to try to get PowerPC/ OS X N-body working this week.

I'm also getting work units fail with the message "computation error". In my case, thorugh, they fail in about 60 seconds.

Is there anything I can do to help diagnose the problem?

++PLS

I'm also getting work units fail with the message "computation error". In my case, thorugh, they fail in about 60 seconds.

Is there anything I can do to help diagnose the problem?

++PLS

Are you using the applications from the server, or old outdated 'optimized' ones? Is this for the GPU or CPU applications, and on what operating system?

---

Will the updated code be added to the code release repository?

My intel dual core mac is not getting any more comp errors but the nbodys are are using 1.95% of my cores. Is this something new?

Also I had aborted all tasks on my i7 920, and downloaded the new work units. They got to 32 hours and then went to comp error. So I aborted most of them and kept 8 to see what happens to them.

Im running stock apps on both computers. CPU only.

I will keep my NNT on untill things settle down.

---

Will the updated code be added to the code release repository?

All of the code is available and GPL3 at http://github.com/Milkyway-at-home/milkywayathome_client The various releases are tagged, however I've been mostly lazy and not putting tarball releases up, but I will eventually.

Thanks :) Maybe this topic could be updated to point to the new link? source code and sample workunits

My intel dual core mac is not getting any more comp errors but the nbodys are are using 1.95% of my cores. Is this something new?

That's not 1.95%, but 1.95 processors. There's a new multithreaded N-body which should be a more effective use of a CPU than running an individual N-body on each core. BOINC tells the application how many threads to use, which in this case would be 2. The OpenMP one is also right now only on OS X; Linux should be soon and then Windows if I can get it to work.[/quote]

Also I had aborted all tasks on my i7 920, and downloaded the new work units. They got to 32 hours and then went to comp error. So I aborted most of them and kept 8 to see what happens to them.

How recently? It seems your errors have been removed from the database.