Hi!
I know you can choose the length for each Wu you crunch but...
Do you know what's the estimated time for a "simultaneous folfing & docking with symmetry imposed between monomers" Wu (id. Twist Ring Twist angle Symm fold & dock) ?
I set my prefs on 4h Wu but it seems to be longer.
Should I choose longer time in order to finish correctly this kind of Wu which seems to display nothing on searching/accepted frames ?
Thanks.

It will finish correctly regardless of your preference. But I've seen some tasks with similar names take over 6hrs. So it will run ok, just be aware that the estimated time to completion is based on your 4hr preference... not any concrete idea about the protein you are working on. So, it will show 10min left for the last 2hrs if yours takes 6hrs like mine did.

---

Rosetta Moderator: Mod.Sense

So, it will show 10min left for the last 2hrs if yours takes 6hrs like mine did

That's what I suspected.

It will finish correctly regardless of your preference

Ok. Thank you.

Hi, I record all my work. To date I have 7343 recorded wus across my hosts. To give you some idea, I put together my "longest three" decoys per host/OS. The time shown is the time it took to do ONE decoy. I removed many which were of the same job type, so it would show 3 different job types. Ofcourse, the number of decoys done depends on "run time", but here's the list.



Hope this also helps.

tony

Falconfly has reminded me of one possible exception to my "It will finish correctly regardless of your preference" statement. If your prefered runtime were really short, like the 1hr minimum, the watchdog will end the task if it runs longer then 4 times your preferred runtime. So, watchdog will end if it runs longer then 4hrs in the case where the preference is one hour. And if the particular task happens to be one where it takes 6hrs for a single model, then in that case the task is not going to finish correctly.

---

Rosetta Moderator: Mod.Sense

And if the particular task happens to be one where it takes 6hrs for a single model, then in that case the task is not going to finish correctly.

Well, I think I'm going to crunch it, allowing a longer CPU time. (set to 7 or 8h, seems to be possible to change this parameter while crunching, right?)
Thank you.
And thank you too, Astro.

Yes, when you change the runtime preference in the Rosetta preferences, and then you complete an update to the project, it will revise the runtimes of your existing tasks, even those already in progress. It has a little trouble again with the estimated time to completion, but it will try to target the new runtime.

---

Rosetta Moderator: Mod.Sense