Posts by Kerwin

1) Message boards : Number crunching : not sending workunits to multiple users (Message 17683) Posted 5 Jun 2006 by Kerwin Post: Hi Dragokatzov, the short answer is that Rosetta doesn't rely on a quorum of 3 or 4 results before granting credit, unlike the other BOINC projects. What you claim is what you get.
2) Message boards : Number crunching : Report Problems with Rosetta Version 5.16 I (Message 16636) Posted 19 May 2006 by Kerwin Post: Wow, that's totally weird. I've never seen that on my Mac. Does the text ever return to normal? Here, I just caught one on Ralph. These two snaps were taken within 10 seconds of each other: The words get stretched out lower and longer to the point that it just becomes a straight line. I also saw this on both my machines but it seems harmless. As more points are plotted on the Accepted Energy graph, that Accepted Energy text in the Low Energy box gets stretched out until it disappears.
3) Message boards : Number crunching : What to do with 5.13 WUs? (Message 16446) Posted 17 May 2006 by Kerwin Post: For the last few versions, the project has asked that you do not abort units and just let them finish. This was stated for versions 5.12 and 5.13. Thought I didn't see it explicitly stated for 5.16, I'm sure the same holds true.
4) Message boards : Number crunching : Improvements to Rosetta@home based on user feedback (Message 16173) Posted 13 May 2006 by Kerwin Post: Aglarond, I agree with you. I was on the Einstein boards a few days ago and it was stated by Bernd Machenschalk, a project developer, that they hired him a consultant from the project. In fact, during the time of his posting, Akos was sitting next to Bernd looking over the code. I do remember a few weeks ago that he expressed interest in trying to optimize Rosetta. It would be great to have him. Because of his S41.06 client, my crunch time for a 'long' Einstein unit now hovers in the 45 - 48 minutes range, compared to about 2 hours 45 minutes and more with the standard client. If he could bring his magic here now, I think it would be very good considering CASP has started. I posted this idea on other thread, but now I think it belongs here: What about kindly asking Akos Fekete, who made optimizations on Einstein, if he could look at Rosetta and try to make optimizations here? Although, it may be necessary to pay him for his effort, as he is rather busy.
5) Message boards : Number crunching : Report Problems with Rosetta Version 5.13 (Message 16009) Posted 12 May 2006 by Kerwin Post: I just noticed that as with 5.12, my machine is experiencing the same problem that I first reported here. I also noticed that someone else is experiencing the same problem. Perhaps this screen crashing problem is only limited to ATI gpus? I completed a 5.13 work unit on my office computer earlier today with the graphics open the whole time and experienced no screen crashes (it uses an Intel integrated gpu) For further clarification, the screen crashes don't happen during full atom relax. You might want to try upgrading your BOINC client to version 5.4.9. See Here. I installed BOINC 5.4.9 and the problem still persisted. However, I think I found the cause. If I don't attempt to rotate or zoom in/out of the native protein model, my system can make it all the way through without a screen crash. I've been able to replicate this somewhat. Everytime I rotate the model with my mouse even a small amount, a screen crash does happen but a random time afterward. Interesting bug. ;-)
6) Message boards : Number crunching : Report Problems with Rosetta Version 5.13 (Message 15994) Posted 12 May 2006 by Kerwin Post: I just noticed that as with 5.12, my machine is experiencing the same problem that I first reported here. I also noticed that someone else is experiencing the same problem. Perhaps this screen crashing problem is only limited to ATI gpus? I completed a 5.13 work unit on my office computer earlier today with the graphics open the whole time and experienced no screen crashes (it uses an Intel integrated gpu) For further clarification, the screen crashes don't happen during full atom relax.
7) Message boards : Number crunching : Report Problems with Rosetta Version 5.13 (Message 15972) Posted 11 May 2006 by Kerwin Post: This isn't exactly an error but more of a cosmetic thing, but the descriptive text in the graphics doesn't wrap to the next line. For my current unit is says, "This test is looking to see whether we fold evolutionary similar proteins using the same protocol, we are ab" and it cuts off right in the middle of that last 'b'.
8) Message boards : Number crunching : 5.12 Windows Media Player and ffdshow (Message 15878) Posted 11 May 2006 by Kerwin Post: I can confirm the delay in video playback using media player classic while 5.12 is running. It doesn't appear to slow down any of my other apps. I also found that watching the graphics sometimes causes the video card to stop responding. Eventually things go back to normal with an error message from the driver (Catalyst version 5.13; ATI X850 XT) stating that the video card stopped responding to the driver. 4.7% into my current result, this happened 4 times in a row and by the fourth time, it had reverted to software rendering so I had to restart my machine.
9) Message boards : Number crunching : Report Problems with Rosetta Version 5.12 (Message 15854) Posted 11 May 2006 by Kerwin Post: I was looking at the graphics for 5.12 and suddenly they stopped, the computer froze, my screen went blank and all of a sudden it reappeared with a message from my Catalyst driver stating that the video card was no longer accepting commands from the driver and that it had to be reset. Once this error message popped up, everything went back to normal, graphics and all. I'm using an ATI X850 XT. This is the second time this happened. It also happened with a result using 5.07 with the same outcome. Edit: I continued watching the graphics and it happened again, but this time 4 in a row a few seconds apart. By the fourth time, the video card stopped responding and the driver reverted to software rendering. At this point I chose to restart my machine. This happened 4.70% into JUMP_CLOSE_CHAINBREAK_ALLBARCODE_1q7sA_SAVE_ALL_OUT_493_4697_0