I have a condition on two of my computers that I have not seen before.

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=13402092

Its a HBLR_1.0 unit.

It does not appear to be stuck, just VERY SLOW. It gains about 0.01% per 200 seconds. It has been running for 16 hours 50 minutes and is now at 5.15%. It looks like others have had "trouble" with this unit before (I am the third to receive it). Is it of value to allow it to continue? At this rate it should be done in 13 days which is beyond the due date. Its app is Rosetta 5.01, running on an Win XP with SP2.

On the other computer, there is also an HBLR_1.0 work unit that appears to have completed successfully by another person but was re-issued to me anyway. Its a much faster computer but has been running for 5 hours and is 2.91% complete.
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=13420677

---

I have a condition on two of my computers that I have not seen before.

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=13402092

Its a HBLR_1.0 unit.

It does not appear to be stuck, just VERY SLOW. It gains about 0.01% per 200 seconds. It has been running for 16 hours 50 minutes and is now at 5.15%. It looks like others have had "trouble" with this unit before (I am the third to receive it). Is it of value to allow it to continue? At this rate it should be done in 13 days which is beyond the due date. Its app is Rosetta 5.01, running on an Win XP with SP2.

On the other computer, there is also an HBLR_1.0 work unit that appears to have completed successfully by another person but was re-issued to me anyway. Its a much faster computer but has been running for 5 hours and is 2.91% complete.
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=13420677

Per FAQ on Thread 1453


"3. More aggressive full atom sampling:

HBLR_1.0_xxxx_ROT_TRIALS_TRIE
The final stage Rosetta's folding strategy consists of fine movements that try to fit the protein pieces togeth iner atomic detail (the "fullatom" stage, often abbreviated FA). These simulations use David Baker's latest energy terms (the "HBLR_1.0" refers to the weight on long-range hydrogen bonding) using an aggressive minimization protocol ("rotamer trials") that is made efficient with a neat graph representation within rosetta (the "trie").

So I take it these units are by their nature complex and do require a long of computing time and thus they are sloooooooooooooooooooooow. They will be completed for sure; they will be as exciting as watching two sloths mating and they will test your faith on computer's data processing powers but they will be completed. :)

I cannot tell you why the resent unit was resent.

---

This and no other is the root from which a Tyrant springs; when he first appears he is a protector.”
Plato

If it is still doing Model #1 and/or switches between AbInitio/FullAtom (or is in Model #1, with many red dots in lower right RMSD/Energy chart), I'd abort it, as it's probably in an endless loop (this particular bug is a new 5.01 issue...), see:

https://boinc.bakerlab.org/rosetta/forum_thread.php?id=1447#14324

I see, but I think it's in a endless loop, because

1/ It has "switched" from Full-atom-relax Model 1 / Step 34k+, back to Ab-initio and Model 1 / Step 1 in front of my eyes (I enabled the graphics to monitor it for a while). In the past it was always Ab-initio -> Full-atom-relax -> done this model, process next Model, right?

Oddly, the WU graphics show several (~14) red-dots (energy min), which afaik should mean that at least 14 Models were processed. But Model # remains at 1.

2/ It's been running for 15.5hr already (my time setting is 8hr/WU) on a P4 CPU which has never exceeded 4hr/model in the past.

---

Best UFO Resources
Wikipedia R@h
How-To: Join Distributed Computing projects that benefit humanity

I have a condition on two of my computers that I have not seen before.

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=13402092

Its a HBLR_1.0 unit.

It does not appear to be stuck, just VERY SLOW. It gains about 0.01% per 200 seconds. It has been running for 16 hours 50 minutes and is now at 5.15%. It looks like others have had "trouble" with this unit before (I am the third to receive it). Is it of value to allow it to continue? At this rate it should be done in 13 days which is beyond the due date. Its app is Rosetta 5.01, running on an Win XP with SP2.

On the other computer, there is also an HBLR_1.0 work unit that appears to have completed successfully by another person but was re-issued to me anyway. Its a much faster computer but has been running for 5 hours and is 2.91% complete.
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=13420677

Per FAQ on Thread 1453


"3. More aggressive full atom sampling:

HBLR_1.0_xxxx_ROT_TRIALS_TRIE
The final stage Rosetta's folding strategy consists of fine movements that try to fit the protein pieces togeth iner atomic detail (the "fullatom" stage, often abbreviated FA). These simulations use David Baker's latest energy terms (the "HBLR_1.0" refers to the weight on long-range hydrogen bonding) using an aggressive minimization protocol ("rotamer trials") that is made efficient with a neat graph representation within rosetta (the "trie").

So I take it these units are by their nature complex and do require a long of computing time and thus they are sloooooooooooooooooooooow. They will be completed for sure; they will be as exciting as watching two sloths mating and they will test your faith on computer's data processing powers but they will be completed. :)

I cannot tell you why the resent unit was resent.

WOUZA !!!! I processed a 2 hour one of these on RALPH and it finished wo error. ( Insert Dancing Emotie)

---

This and no other is the root from which a Tyrant springs; when he first appears he is a protector.”
Plato

1 day 4hrs and still going... currently at 8.31% complete. Is there a timer on these units that if they take too long they self abort? App is Rosetta 5.01

---

1 day 4hrs and still going... currently at 8.31% complete. Is there a timer on these units that if they take too long they self abort? App is Rosetta 5.01

That definitely looks like one of those WUs that creeps foward in percent complete, but which is actually in an endless loop and will never finish.

I suspect it will auto-abort eventually, but that could take several days.

Once we get the new client with the watchdog (maybe early next week) stuck WUs should auto-end after about an hour.