Question on protein stats

[spinne]

I signed up for the AS folding@home team yesterday. This is the first distributed computing project that I can really get behind. I'd been running SETI@home since mid-February, and I did a brief stint with RC5-64, but I'm not terribly concerned with off-planet life that is probably hundreds of light years away right now and I'm not an encryption junkie, either. Normal and rogue proteins, though... yeehaw! I'm so in for this... as soon as it finished installing, I shut off SETI@home and ran Console Folding. :bgrin:

Anyway, I have some questions.

1. Is there a list out there that gives the details of each of the proteins we're working on? Name, attributes, what it's responsible for, etc.?

2. I read somewhere that larger proteins take longer to fold and that users get more credits for working those. I lost the page that was on... does anyone know the address for it and if it listed the different amounts of credit for each different type of protein?

3. Is the genome@home project still running? I thought they'd finished mapping the human genome already. Are they working on something else?

4. How many people on AS are members of more than one distributed computing project?
4a. How many of those people use one computer to run multiple clients?
4b. When running multiple clients, how do they split up your spare cycles, and did you choose to give one a higher priority over the other? If so, which?

Cheers!
-spinne-

[Diesel]

First off, let me say both welcome to the team, and thanks for helping the effort.

To answer your questions:

1> I believe that Stanford has information on each of the proteins being worked on. You can check it out at http://foldingathome.stanford.edu

2> Yes, depending on the number of Nsteps (listed in the console client at the beginning of work unit processing), larger work units will yield more credit. Generally speaking, figure that for every 100,000 Nsteps, you will get credit for one work unit. Right now, my main system is processing a bbalphaht work unit with 500,000 Nsteps, so when I turn this in, I will get credit for 5 work units.

3> Yes, the Genome@Home project is still running. We are currently looking into the possibility of fielding a team for that project as well, but our primary focus will remain with Folding@Home.

4> Only each individual can answer that, but I'm totally focused on Folding@Home right now. To date, it's still the only worthwhile project I can throw my support behind, for the same reasons you listed above.
4a> I have several machines that have run more than one client, but generally speaking, it's better to just run a single project and let it have full acess to the whole CPU.
4b> I can speak for how a few different clients interact.
[list]
SETI@Home and Folding@Home - SETI monopolizes the CPU and uses 100%. F@H will get nothing while SETI is running at the same priority.
Folding@Home and Genome@Home - split the CPU time 50-50. In some cases, I've set up both and gave higher priority to F@H. Worked out well, for the most part, as full processing was given to F@H, and G@H only got the downtime in between work units. If you want details, PM me.