Message boards :
Number crunching :
AstroPulse v7 - -Error while computing - Mac
Message board moderation
Author | Message |
---|---|
Trent Send message Joined: 3 Sep 05 Posts: 7 Credit: 367,182 RAC: 0 |
Hi all, I am a bit puzzled my mac has run two astopulse v7 workunites and both finished with the result "Error while computing" after running for over 240,000 seconds... what is going on and how do I fix it? I originally posted this in seti@home science but they suggested I post it here.. My client seems to have now stopped downloading astropulse workunits. |
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
The estimated time to complete was too short. We've seen this before when first testing work units. There is a way to change to estimated time but I can't recall at the moment. TBar knows how to do this. (he walked me thru it when it first happen to mine as well) Give it some time here and I'm sure one of the other MAC users will respond on how to address this issue. |
kittyman Send message Joined: 9 Jul 00 Posts: 51468 Credit: 1,018,363,574 RAC: 1,004 |
Hi all, No AP work being generated right now, so don't expect any. The last resend the kitties got, with 9 rigs asking every 5 minutes, was about 14 hours ago. "Freedom is just Chaos, with better lighting." Alan Dean Foster |
Trent Send message Joined: 3 Sep 05 Posts: 7 Credit: 367,182 RAC: 0 |
If Tbar could help that would be awesome |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Well, in this situation there isn't much help available, only suggestions. Zalster gave the hint when he said he had the same problem with his 330m. In fact, just about All the pre-Fermi Mac cards have problems with SETI tasks. What you are seeing is normal for that card. There are a few that actually finish the task, but, if you compare the CPU time spent you would have been better off just running a CPU task instead. Look at the CPU time on this task, http://setiathome.berkeley.edu/result.php?resultid=4402662717 Run time: 3 days 6 hours 13 min 58 sec CPU time: 2 days 14 hours 35 min 21 sec If that task would have finished you would have received around 500 credits, whereas if you would have run a CPU task for 2 days 14 hours you would have received about 1000 credits. So, you are losing by running the GPU task, better to just run the CPU tasks with those machines. I'm not sure how those cards would work if there is ever a Mac CUDA App released, however, my GTS250 is almost Twice as slow running CUDA on My Mac as opposed to other platforms. Also, in my experience the GTS250 is much faster on a Mac than a 330m, so, it probably wouldn't be much better running CUDA on the 330m. I would suggest turning Off AstroPulses on that machine and just running the CPU SETI@home v7 tasks, they seem to be working well on that machine, http://setiathome.berkeley.edu/prefs.php?subset=project |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.