Certainly correct, good catch Sid. If all of the tasks you download are CASP9 tasks, then a large download buffer defeats the purpose of the shorter deadline.

Will the energy WUs be handled by a separate application?
And if so, will users be able to choose which applications they receive WUs for?
And who owns the IP rights for what R@H might develop / discover in this sub-project?

I support those questions. In my team alone there are at least other 5 users with the same doubts.

Currently we do not plan to run many energy WUs on rosetta@home -- it will likely be less than 1% of the total. if later these calculations become more CPU demanding we will figure out how to give users the ability to choose. the IP rights for all of our research belong to public institutions like the university of washington.

Will the energy WUs be handled by a separate application?
And if so, will users be able to choose which applications they receive WUs for?
And who owns the IP rights for what R@H might develop / discover in this sub-project?

Folks, please do not take % complete and time to completion as any indication of a Rosetta problem. It is simply an estimate that your BOINC manager is making. This takes a number of factors in to account, including the speed of your machine, and time it took your last task to complete. So if your last task ran long, the % on the next task MAY (or MAY NOT) reflect that, or part of that information. BOINC tries not to presume all tasks are the same and sometimes looks at the last several tasks runtime as a frame of reference.

If you restart a task, you should be looking at the elapsed time change as the indication of what checkpoint (if any) the task was able to restart from.

Venturini, are you allowing BOINC to use 100% of CPU? And all of the available CPUs? Is the machine busy working on other applications that are running?

All of the cores (2) are dedicated to BOINC, both running 100%, and the only other application running is Word (I'm writing schemes for my next university exams) plus the background ones (antivirus and so on) ;)

Plus, I have only Rosetta on this PC (and WCG, but it's set to no new task).

OS is Windows Vista Home Premium, BOINC is 6.6.28, CPU is a Intel 7700.

And, btw, call me Dario, Venturini is my surname ;)

Venturini, are you allowing BOINC to use 100% of CPU? And all of the available CPUs? Is the machine busy working on other applications that are running?

adrianxw, please click the task from the task list and click the properties button. Does it show more then 10 hours of CPU time as well? (because the task list now shows "elapsed time" with the new BOINC version).

If you unsuspend the task (and get it running again, perhaps by suspending other tasks for a moment), is it using CPU time?

If it has more then 10 hours of actual CPU time, I would suggest aborting the task.

Validate error on a 84k+ seconds task (I'd say... rather annoying)

http://boinc.bakerlab.org/rosetta/result.php?resultid=162388905

stderr out	

<core_client_version>5.10.45</core_client_version>
<![CDATA[
<stderr_txt>
# cpu_run_time_pref: 14400
======================================================
DONE ::     1 starting structures  14353.2 cpu seconds
This process generated     14 decoys from      14 attempts
======================================================

BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...
called boinc_finish
# cpu_run_time_pref: 14400
======================================================
DONE ::     1 starting structures  15500.1 cpu seconds
This process generated      1 decoys from       1 attempts
======================================================

BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...
called boinc_finish

</stderr_txt>
]]>