Does rosetta give other tasks (other apps or other molecules) if you change your prefrence time to 1hour for example.

What are the (pro's and) conta's for taking short WU times?

The tasks are the same. But you will run fewer models on each. So, you will typically require more bandwidth to keep your machine busy, because you will tend to contact the scheduler more often and will require more tasks per day.

---

Rosetta Moderator: Mod.Sense

Does rosetta give other tasks (other apps or other molecules) if you change your prefrence time to 1hour for example.

What are the (pro's and) conta's for taking short WU times?

I don't think the project makes a distinction based on runtime preference. The only distinction (to my knowledge) is available RAM.

From personal experience, some types of errors can be avoided by setting a shorter runtime preference. There was a bad stretch with one of the rosetta minis (1.20 or something like that) where two of my crunchers were reliably crashing between 12 and 16 hours into a task. By cutting my runtime preference below that threshold, I was able to keep those crunchers online and contributing to the project.

The downside of this is that some of the proteins we study are so complex that it may take a very long time to complete a single model.

If the time to complete a single model exceeds your preferred runtime by more than a factor of four, the watchdog will kill the workunit.

As an example: one of the crunchers I described above recently completed a workunit in which a single model took over 15 hours. If the runtime preference on that computer had been set to 3 hours or less, the watchdog would have killed the workunit.

I hope you will be able to find a way to stay with the project.

---

Rosie, Rosie, she's our gal,
If she can't do it, no one shall!

Oh thanks for your answers,

I'm back at rosetta now, but I did put my WU time on 1hour. The advantage is that I can see many different projects.

However I don't want to miss out on the complex molecules.

You won't miss out on the variety of tasks. Just be aware that some will take significantly longer then 1 hour, because a single model is the smallest amount of useful work. And some tasks can take over 6 hours to do a single model. And so when you run in to these, BOINC is going to begin to get confused about how much Rosetta work to try and request and keep on-hand to keep your desired buffer size. Also, as pointed out previously, the watch dog may kill such a task before it is able to complete that very long model. It steps in once the task has reached 4 times your run time preference.

---

Rosetta Moderator: Mod.Sense

I don't understand what is better for the project and its research's work: short or long WU?
Thanks

I don't understand what is better for the project and its research's work: short or long WU?
Thanks

What the project needs overall is more models produced. But it doesn't much matter if 10,000 models are produced by 1000 tasks, or 2000 tasks. So choose a runtime that best fits your environment, with how much your machine is on, what resource share you devote to Rosetta, how often you connect to the internet, etc.

If you run all day long and have Rosetta as your primary project, then I generally suggest the maximum 24hr runtime. I just like to see a concise list of tasks. It also reduces the number of times per month you have to contact the scheduler to get new work, and the bandwidth of downloading tasks. But others prefer short runtimes. They like to see work churning through, and seeing their credit total climb by the hour.

It really doesn't make much difference to the project. And that is why they have added the ability for you to define your runtime preference. This is done in the Rosetta preferences, found by clicking on the "[Participants]" link at the top of these message boards.

---

Rosetta Moderator: Mod.Sense