Posts by pvh

1) Message boards : Number crunching : Rosetta@Home Version 3.24 (Message 72519) Posted 15 Mar 2012 by pvh Post: I noticed that the 3.24 app did not have the execute bit set after download (in openSUSE 11.4, Boinc 7.0.18), which caused all WUs to fail. I have fixed this manually, but that should not be necessary of course...
2) Message boards : Number crunching : minirosetta 2.05 (Message 65349) Posted 16 Feb 2010 by pvh Post: Try closing down BOINC and re-opening it. That seems to do the trick. Thanks for the tip, but why did you remove my post?
3) Message boards : Number crunching : minirosetta 2.05 (Message 65346) Posted 16 Feb 2010 by pvh Post: I am seeing WUs that seem to be "stuck". If you look at the properties of the WU, you typically see something like: CPU time at last checkpoint 00:35:26 CPU time 06:02:29 If you look at the graphics, you see that the protein is not changing shape at all and the energy and RMSD are perfectly constant. These jobs run on for around 25,000 seconds and (I assume) are then terminated by the watchdog. You get very low credit for these jobs. I assume this is a bug in the code. If so, please fix it quickly since it is wasting lots of CPU time. When I see such a WU, should I abort it, or is it better to leave it running? This is with Rosetta Mini 2.05 on a 64-bit Linux system. I have seen this on both of my OpenSUSE 11.2 systems with the 2.6.31.8-0.1-desktop kernel (so hardware problems are ruled out). I have so far not seen this on my dual-core OpenSUSE 11.0 system with a custom 2.6.28.2-vanilla kernel. The latter is by far the least performant machine, so there is a (small) chance that this is just random chance. I do not see an obvious pattern which WUs suffer from this.