Setting length of tasks

Questions and Answers : Preferences : Setting length of tasks

To post messages, you must log in.

AuthorMessage
Odysseus

Send message
Joined: 4 May 07
Posts: 23
Credit: 16,331
RAC: 0
Message 3077 - Posted: 6 May 2007, 3:33:27 UTC
Last modified: 6 May 2007, 3:34:43 UTC

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?
ID: 3077 · Report as offensive    Reply Quote
Profile anders n

Send message
Joined: 16 Feb 06
Posts: 166
Credit: 131,419
RAC: 0
Message 3081 - Posted: 6 May 2007, 17:25:44 UTC - in response to Message 3077.  

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?


It means that the WU got stuck and was aborted by the watchdog.

The first estimate is often off by alot :) but comes close to your preferred setting after a few WU-s.

Happy Cruching
Anders n
ID: 3081 · Report as offensive    Reply Quote

Questions and Answers : Preferences : Setting length of tasks



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