Posts by Odysseus

21) Message boards : Number crunching : Credits (Message 3082)
Posted 6 May 2007 by Odysseus
Post:
My first two tasks each took about four hours (on a Mac G4/733) and claimed between 12 and 13 credits. The first one, which was terminated by “Watchdog”, was granted 80 CS, but the second, which completed normally AFAICT, was granted less than 5. It certainly seems inconsistent—especially with no ‘quorum partners’ involved.
22) Questions and Answers : Preferences : Setting length of tasks (Message 3077)
Posted 6 May 2007 by Odysseus
Post:
In the output from my first successful result, from version 5.63, SEARCH_PAIRINGS_-1dhn_-round2_1976_120 I see:
Rosetta score is stuck or going too long. Watchdog is ending the run!
CPU time: 14813 seconds. Greater than 4X preferred time: 3600 seconds

Does this mean I should increase my preferred run-length? (At the moment I’ve left the project preferences at their default settings.) BOINC’s initial to-completion estimate was something like 24 hours. Are these messages fairly common here, or might this be indicative of a problem?
23) Message boards : RALPH@home bug list : Bug reports for 5.63 (Message 3065)
Posted 5 May 2007 by Odysseus
Post:
Hello, everyone! I seem to have been recruited into my first alpha project (the first that identifies itself as such, at least). I regret that my first posting here has to be negative. Well, mixed …

After getting “No work from project” messages for a few hours after attaching, my G4/400 running BOINC v5.4.9 under Mac OS 10.3.9 received its first WU, 2tif__DIVERSE_ABRELAX__NEWRELAXFLAGS_BCFROMFRAGS20_SAVE_ALL_OUT_frags83__1986_4. It got a “Compute error” in less than twenty seconds:
<message>
process exited with code 1 (0x1)
</message>
<stderr_txt>
Rosetta@home Macintosh Stack Size checker.
  Original size:            0.
  Maximum size:      8388608.
  RLIM_INFINITY            0
# cpu_run_time_pref: 3600
ERROR:: Unable to determine sequence length from pdb file
# random seed: 2680619
ERROR:: Exit from: pose.cc line: 1929
</stderr_txt>

The other two hosts that crunched it, both Windows/AMD, also had errors.

On the brighter side, the next WU I received seems to be doing OK. It began with an estimate of around 25 hours and kicked my host into “panic mode”, but got most of the way through the task in just a couple of hours. Then it seemed to slow down; when I left the shop it was somewhat over 90% done, having found a configuration that vaguely resembled the ‘template’, but still showing about 13 hours to go. When I got home, however, I was encouraged to see that the host had downloaded another WU, indicating that BOINC thinks the current one is almost done.

Awesome graphics, BTW. :)

P.S. Re checkpoints: I forgot to mention that my Mac crashed while running this task (@#$%! Acrobat!) but when I rebooted it resumed very near where it had been when interrupted.


Previous 20



©2024 University of Washington
http://www.bakerlab.org