Can you explain F@H?

[Mellman]

Well joined up yesterday, so far have the 2.4, 1.7 dothan, and my 2.3Ghz AMD at home all folding them proteins good. Now something im attempting to learn

The number out of 400, This is ONE Work Unit (WU) correct?

From reading other peoples posts, i take it this number may change from time to time? Be more, or less?

What is the normal time it takes to process one WU? i realize this is dependent on CPU power, but I'm just trying to scale how im doing. I see other DC projects seem to go through the work units faster.

also an extra question...I like both F@H and SETI(there is WAY too much space out there for it just to be us idiots on earth) is it better to dedicate a single machine to each, or what are the performance dips if i run both on the same machine?

 

[r0tt3n1]

Welcome to the TeAm!! Glad you are folding with us.
This page shows us all the current projects that Stanford is sending out to participants of the F@H project. Note the `Frames` column on this page. It lets you know how many frames a single work unit of that type has.
There are 2 types of work units, Gromacs and Tinkers. Most Tinkers have 400 frames per work unit, Gromacs have 100 frames. Meaning that 1 Tinker work unit needs to finish 400 steps or frames to be complete, a Gromacs work unit has to finish 100 frames. Stanford will decide which work units you recieve, based on what they are currently working towards and which areas of thier study need attention.
I have tried to run SETI and F@H at the same time and found that SETI takes over, leaving very little CPU power to process F@H. You may want to leave a single project on each computer.

 

[Wolfsraider]

i had that problem with lm taking over seti as well but raising the priorty of the weaker project 1 notch in lifemapper allowed both to crunch 50% and no difference in computer responsiveness

hope this helps

mike

 

[GLeeM]

Welcome to the TeAm, Mellman

F@H WUs are all different sizes. If the point value is more it will take longer to finish. The point values range from 12 to 249 (at present). A guess at time: 2 hours for small and 2 to 4 days for large. A large WU takes 4+ days on my P3 1 ghz laptop.

There is a program called F@H LogStats that will give you an idea of how you are doing. There is a link to it in the info link in my sig.

If the 2.4 has HT you can get up to 31 percent more production running two consoles, depending on WUs!

If you have any more questions or need help of any kind, someone here is willing and able.

 

[Mellman]

appriciate all the help guys....it looks like my systems are all on track to complete a 400 frame WU in under two days. i take it a 400 frame WU is one of the 'larger' WU's? Just wanted to make sure someting wasn't totally fvcked up on my systems and it was taking forever to process them once i start finishing WU's i am sure i'll start to see how its getting "done" much faster.

 

[ProviaFan]

Originally posted by: Mellman
appriciate all the help guys....it looks like my systems are all on track to complete a 400 frame WU in under two days. i take it a 400 frame WU is one of the 'larger' WU's? Just wanted to make sure someting wasn't totally fvcked up on my systems and it was taking forever to process them once i start finishing WU's i am sure i'll start to see how its getting "done" much faster.

400 frame WUs are usually the larger ones. However, the number of frames doesn't necessarily indicate the complexity of the WU. I've had 20 frame WUs that took forever to finish on my Duron, but that was a long time ago.

Glad to have you on the TeAm with us.... happy folding!

 

[Zuke]

Heheh, it's funny to me to listen to all the different approaches to DC projects. Some guys pay attention to each work unit and how long it takes to process it, etc. Other people never pay any attention to their machines. Quite the range of attentiveness.

 

[lobadobadingdong]

if you want to set up f@h and seti on the same machine it's not difficult, all you have to do is install the gui client (not the screen saver) and in the configuration, under the advanced tab, set it to use a slightly higher core priority (low instead of idle) and on the CPU percent slider, slide it to whatever amount of spare cpu cycles you want the F@H client to use and using seti driver set it to idle, it will then use the idle cycles that you let it have from the settings in the F@H configuration.

personally I have a 2800+ a 2200+m and a 933 p3 crunching F@H 24/7 and my parents/grandparents computers are running SETI as a service (many are on dial up and seti works way better than F@H on dial up.)

edit: forgot to say.....

Welcome to the TeAm and make sure your team number is 198, and what is your id on the F@H client?