Re: Folding Control
Originally posted by MacAztec
And, I had folding control running for about a day, and it maybe finised 1/15th of the total bar....
The graphical version and the folding control store the config/WU files in different places. They don't help each other out. You need to pick a client and stick with it. That's why yout times are even longer than they should be.
The best overall IMO is the GUI folding app provided by stanford. It's never given me problems.
The best "nerdy" client is console, but that takes a lot of will-power, and has given me a few problems.
Then there's Folding Control, which is beta software running over the console version which I only recommened if you have a DP machine and don't want to run 2 Cores through Darwin w/o GUI assistance.
Straight console will always be faster but not by that much and there is sort of a learning curve. I would stick with the GUI it is straightforward and does its job well. Run the GUI client hidden using cmd-h or by opt-clicking onto another window (it loads this way default for a reason). If you minimize the window or look at the protein moving, you will make your WU take longer because it will be using more CPU. The GUI and console are almost the same if you run the GUI client hidden. You get to see what's going on directly with the GUI, but with the console you have to look elsewhere.
For maximum CPU I usually run logged in through >console so X doesn't have to launch window services, and other GUI processes.
If you get a proteinA or some variant thereof (which is all they have given me lately), then it should take ~3-5 days if you give it most of the CPU. But since you ran the other client, you effectively doubled the idle processor workload for the period that you were running the two cores-- so it will take you longer to finish this WU.
You will be rewareded for your patience. Welcome to the team.
