Hi i would just like to say, i have read https://boinc.bakerlab.org/rosetta/forum_thread.php?id=3054 about constant restaring of the project, and i have allowed the program to update several times, but every time i turn my computer on again it have the problem that the % done drops nack to 0% and it starts from the beginning.
What can i do? I have my computer on for about 30min slots, but they cannot do the projects as they restart when the program starts up again. I have only managed to complete work when it has been left on over dinner.
What can i do?

---

Hi i would just like to say, i have read https://boinc.bakerlab.org/rosetta/forum_thread.php?id=3054 about constant restaring of the project, and i have allowed the program to update several times, but every time i turn my computer on again it have the problem that the % done drops nack to 0% and it starts from the beginning.
What can i do? I have my computer on for about 30min slots, but they cannot do the projects as they restart when the program starts up again. I have only managed to complete work when it has been left on over dinner.
What can i do?

First - i am not a techie - but - try setting in 'general preferences' 'processor usage' YES.
if that does not work suggest you repost in number crunching forum.

---

In general, 30 minutes is not going to be enough time to get much done. But the checkpointing changes that are in the works will help a little.

I believe Michael was trying to point you to the setting for "Do work while computer in use". And to set it to YES. As he says, you will find this in the General Preferences (not the Rosetta Preferences).

---

Rosetta Moderator: Mod.Sense

Hi i would just like to say, i have read https://boinc.bakerlab.org/rosetta/forum_thread.php?id=3054 about constant restaring of the project, and i have allowed the program to update several times, but every time i turn my computer on again it have the problem that the % done drops nack to 0% and it starts from the beginning.
What can i do? I have my computer on for about 30min slots, but they cannot do the projects as they restart when the program starts up again. I have only managed to complete work when it has been left on over dinner.
What can i do?

I am having the same friggen problem and Im about to switch over to setti@home if it continues Iv spent several days running this now its set to run all day ever day in high priority on a fast computer and Iv only been able to complete 1 work unit in 3 days. I put about 22 hours of computational time into one work unit and when it gets about 60-90% done thats when it resets and Im getting very irritated about this. There is nothing wrong with my computer all my programs work flawlessly and I have no lockups when running United Devices projects or the Setti project only this one. They need to make the program more stable so that this wouldnt happen and more work could be completed. Im going to trying taking off Runn 1 Day to ever hour hopeing that will shorten the length of the work unites so that I could complete a task. Iv spent alot of money on building this system just for these kind of projects and if shortening the lengh unites doesnt stop the fixing rosetta@home just lost a volunteer and I would really hate to go because I like this program alot but Im not happy with its performance.. The restart procedure recount needs to be vastly shortened.

---

CHRISX, looking at this task, I see that at some point, you increased your Rosetta preferred runtime to 24hrs. It was later changed back to 1hour, and so the task was completed when it reached the end of it's current model. So, for a period of time, Rosetta was told to crunch the task 24hrs, and it was doing just that.

The version of Rosetta just released has the correction to the % complete. Which is how BOINC estimates the time left to completion. So any tasks you get from now on have the fix.

Please review the settings in your Rosetta preferences. There you will find the preferred runtime. Set it as you wish, the default is 3hrs. Just be aware that your system was running properly the whole time. Also be aware that some of how BOINC runs expects consistency in how long tasks take to run, so by making the dramatic switches in runtime, you are making it difficult for BOINC to accurately predict how much work it should download for the future. And so if you have 10 tasks downloaded and then change your preference to 12 hours, you have 120 hours of work there all the sudden (60hrs actually, because you have a dual core).

If you have any other questions or concerns, please post to the Number Crunching board.

---

Rosetta Moderator: Mod.Sense