I had a download which started from the beginning which said about 5 hours 22 mins to complete and this is the usual amount so I ran it overnight and it ran for 9 hours with 16 hours still to go.
a second one has just started and has been running for over 25 minutes and the show graphics shows this amount and keeps changing from initialzing to App suspended and shows 0.00 complete and still 5 hours 22 to complete so this looks like it is getting to be an infinity before it finishes.
should I just give up on Rosetta as the other 10 projects are working ok

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.

---

Rosetta Moderator: Mod.Sense

Your oldest completed task indicates it was ended due to too many restarts with no progress, and the message there suggests (as do I) that you keep tasks in memory while suspended.

I appreciate your enthusiasm for BOINC projects.... but that's a LOT of projects for one machine. So, to make it up to BOINC for stressing it across so many projects, be nice to it and keep tasks in memory, and double check your settings for how often to switch between applications. This setting should be at LEAST an hour. 4 to 6 hours would be better yet. This will assure more work is preserved and that your machine runs efficiently.

---

Rosetta Moderator: Mod.Sense

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.

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

Hi
we crossed messages I have set my preferances to 180 minutes 9 it was set at 60 Minutes to see if that changes anything
Paul

I ran both files after downloading last night and this is the extract my my messages which shows they started running at 22:41 gmt and 22:43 gmt until 06:45 gmt just over 8 hours each

18/03/2009 22:41:38|rosetta@home|Resuming task lb_alnmatrix_1800_2100_hb_t363__IGNORE_THE_REST_1iue_93_8481_4_0 using minirosetta version 154
18/03/2009 22:43:23|rosetta@home|Resuming task lb_alnmatrix_1800_2100_hb_t370__IGNORE_THE_REST_1w9a_105_8485_4_0 using minirosetta version 154
19/03/2009 06:45:41|climateprediction.net|Resuming task hadsm3mh_kl7i_006016043_8 using hadsm3mh version 602


The progress in both cases was only showing just over 3 hours the progress was 0:00 and the time to complete was still 05:42:21 which it was when it started

so nothing happened so I have aborted these 2 files like the previous ones as these never looked like starting either so I am not downloading any more rosetta files

regards Paul