Posts by Stefan_Strauß

1) Message boards : Cafe Rosetta : So... About that #1 position... (Message 76229)
Posted 26 Nov 2013 by Stefan_Strauß
Post:
I joined your team some days ago for just one reason: Your team gives so much dynamic to the project, it's absolutely amazing. There are so many new rosetta@home users just because of you and your funny and interesting way to convince people of volunteer computing! :)
2) Message boards : Number crunching : Long-running and failing rb_06_21_* work units (Message 76219)
Posted 25 Nov 2013 by Stefan_Strauß
Post:
I think your run-time is causing the problem. I could be wrong, but I believe that BOINC (or maybe Rosetta in this instance?) will cancel the task if it runs for double the selected target run-time. I'd recommend increasing that to at least 4 hrs.

Danny


That's what I did (see my comment) and now the "rb_" WUs work just fine. :)
3) Message boards : Number crunching : Long-running and failing rb_06_21_* work units (Message 76213)
Posted 23 Nov 2013 by Stefan_Strauß
Post:
Edit: Sorry for double-posting. :D
4) Message boards : Number crunching : Long-running and failing rb_06_21_* work units (Message 76212)
Posted 23 Nov 2013 by Stefan_Strauß
Post:
Not wishing to tempt fate but this problem seems to have gone away with 3.48.


Not for me. I'm using Boinc (Version 7.2.7) on my Ubuntu 13.10 (64-bit) machine and every WU starting with "rb_" is failing. My runtime preference was set to two hours because of various reasons. I recently had two of the "rb_" workunits running and they did'nt finish. The difference between those WUs and the ones my computer finishes are the checkpoints. Every WU that sets checkpoints gets finished, while most of the "rb_" ones don't set any checkpoints and keep working and working and working, even if the computer is not shutdown after starting those WUs.

So I tried something out: I cancelled the two recent WUs that wouldn't end and set the runtime preference up to four hours. Now I got a new "rb_" WU, but this time, it sets checkpoints, so it's likely going to finish.



So it seems to be a checkpointing problem in my case. The marked zone on the screenshot was empty on the other two (failing) workunits.






©2024 University of Washington
https://www.bakerlab.org