Posts by Angus

1) Message boards : Current tests : Help us debug minirosetta. (Message 3758)
Posted 18 Feb 2008 by Profile Angus
Post:
AMD 2600+ Windows, 5.10.20, consistently getting 45% of claimed, less than 5 cr/hour
2) Message boards : Current tests : Help us debug minirosetta. (Message 3753)
Posted 18 Feb 2008 by Profile Angus
Post:
I can\'t run the minirosetta client any longer.

It fails to honor run-time preference: My one hour run-time was exceeded by many times. I ditched the rest of the WUs.

Also, the credits granted are much too low.


This is something that shouldn\'t be released into the wild.
3) Message boards : Current tests : Help us debug minirosetta. (Message 3721)
Posted 13 Feb 2008 by Profile Angus
Post:
I have one at 95.2% and it\'s 4X runtime preference. I\'ll let it soak until morning, the it gets whacked.
4) Message boards : Current tests : Help us debug minirosetta. (Message 3709)
Posted 12 Feb 2008 by Profile Angus
Post:
Out of work again?? Says there are 6000+ WU queued on the front page, and 10000+ on the server status page. Getting \"no work available\" messages.

<grump> Can\'t help if there\'s no work. </grump>
5) Message boards : Current tests : Help us debug minirosetta. (Message 3708)
Posted 12 Feb 2008 by Profile Angus
Post:
First problem (or two)

Ralph (or the mini app) does not appear to honor the runtime preference set in Ralph Preferences

It also does not even recognize the preferences were changed. I had to change the General Preferences for a Boinc manager Update to recognize a change had been made and download new preferences. I still don\'t know if it has the correct run-time preference set. I configured it for 1 hour, and the \"To Completion\" in the Boinc Manager shows 5:24:14 for all tasks.

6) Message boards : Current tests : Help us debug minirosetta. (Message 3705)
Posted 10 Feb 2008 by Profile Angus
Post:
No work. Can\'t debug nothingingness.
7) Message boards : RALPH@home bug list : removed from memory by benchmark (Message 815)
Posted 5 Mar 2006 by Profile Angus
Post:
The way to solve it is to manually do a benchmark when a RALPH or Rosetta WU is not in the cache if at all possible

That is NOT a solution - that is a work-around.

A solution would be to fix the Rosetta client application so that it does not lose the work when suspended and removed from memory for the scheduled benchmark calibration.
8) Message boards : Feedback : Credit scores (Message 432)
Posted 21 Feb 2006 by Profile Angus
Post:
The whole point is that RALPH is the right place to test fixes to credit issues, as well as science, or download size, or any other Rosetta-specific issue.

The broken credit problem is a Rosetta issue, self-inflicted by their chosen method of the implementation of BOINC.
9) Message boards : Feedback : Credit scores (Message 422)
Posted 21 Feb 2006 by Profile Angus
Post:
I think the point is that this issue has been beaten to death on all of the project and team forums. The Rosetta people have already said that they are not going to switch to a canonical validation system because it cuts down on the amount of processing that can be done. It is also very clear that they do not plan on modifying the BOINC software beyond the baseline, unless there is a science based reason to do so. So the whole issue is moot for the rosetta/ralph project and it is therefore a BOINC issue.

In any case this project does not seem to be about credits. Did I miss something? I can\'t count the number of times I have seen that said on the boards here. The fact is that no matter how many credits are awarded, you can\'t even use them to get a cup of coffee. So they are totally meaningless in a \"not for profit\" project environment. Now if people were being paid by how many credits they got I could understand the rabid obsession with them. But that is not the case. This is about curing sickness and saving peoples lives, not useless credits.

Even if you concede that credits are important to some people for whatever reason, it is a game, not a life and death problem. You would think people would want the application to run right first and worry about the credits later. People are constantly threatening to leave the project or suspend the project unless they get the 20 credits they lost from a failed WU. Well, lets forget the credit system for a while and fix the failed WU problems that are aggravating people and slowing down the science. You know, like Ralph is trying to do. As you point out there are ways to cheat the credit system, so why make such a big deal out of them. At best they are just for bragging rights.


If you have been around Distributed Computing since it\'s infancy, you should realize by now that a fair and equitable credit system is what keeps people at a project.

Sure, you get a few percent who are in it \"for the science\", but reality is that the biggest portion of the crunching power comes for the credits, and leaves rather quickly when the credit system goes awry.

10) Message boards : Current tests : Switching between projects with applications removed from memory (Message 226)
Posted 18 Feb 2006 by Profile Angus
Post:
http://ralph.bakerlab.org/result.php?resultid=3669

Nothing in log for almost 30 minutes prior to error. Not task switching.

NOT left in memory. Just crashed.






©2019 University of Washington
http://www.bakerlab.org