Rosetta doesn't suspend itself. Either BOINC scheduled another task, or perhaps BOINC was told not to run at certain times of day?

The length of a Rosetta task is something you can configure a preference for on the website here, click the '[Participants]' link above and then click the option for Rosetta preferences, and set the run time preference for the venue of your machine.

The default runtime is 3 hours. And the watchdog will end any task that runs for more then 4 hours longer then your configured preference.

BOINC's estimated completion time will not reflect your runtime preference properly until several tasks complete. And even then, some of the new BOINC versions are having trouble with duration correction factors... so, focus on time used, and % complete rather then time remaining.

From what you describe on the second task, it sounds like Rosetta never gets to run long enough to reach a checkpoint for that specific tasks. Some types of work can checkpoint more frequently then others. But as long as BOINC is still running, if you would configure BOINC to keep tasks in memory when suspended, then it will preserve all of the work from the last stint on the CPU it received and then reach a checkpoint after which you could reboot the machine and still have the work preserved.

Hi my computer is set for 24 hours a day and with 2 processors and just had a climate change and a rosetta running all night with everything set for no new tasks and everything else suspended so I knew it had run for the whole night which is it was up to 9 hours cpu time and the percentage was about 29% and stayed at the same figure and to complete was over 16 hours and this figure was increasing quicker than the cpu time
previously everything was completed in 3 hours and the percentage started almost immediatly so it does look as though all the new ones will not run properly. so I cannot risk upsetting all the other projects by having a problem with rosetta

Rosetta doesn't suspend itself. Either BOINC scheduled another task, or perhaps BOINC was told not to run at certain times of day?

The length of a Rosetta task is something you can configure a preference for on the website here, click the '[Participants]' link above and then click the option for Rosetta preferences, and set the run time preference for the venue of your machine.

The default runtime is 3 hours. And the watchdog will end any task that runs for more then 4 hours longer then your configured preference.

BOINC's estimated completion time will not reflect your runtime preference properly until several tasks complete. And even then, some of the new BOINC versions are having trouble with duration correction factors... so, focus on time used, and % complete rather then time remaining.

From what you describe on the second task, it sounds like Rosetta never gets to run long enough to reach a checkpoint for that specific tasks. Some types of work can checkpoint more frequently then others. But as long as BOINC is still running, if you would configure BOINC to keep tasks in memory when suspended, then it will preserve all of the work from the last stint on the CPU it received and then reach a checkpoint after which you could reboot the machine and still have the work preserved.