Folding@home

From ArchWiki
Revision as of 19:43, 10 June 2013 by Thermi (Talk | contribs) (The graphical way)

Jump to: navigation, search

From the AUR package page: "Folding@home is a distributed computing project which studies protein folding, misfolding, aggregation, and related diseases."

Please see the Folding@home site for a fuller description.

Installation

Just install "foldingathome" from the AUR.

$ yaourt -S foldingathome

Configuration

The graphical way

Simply run ./FAHClient --configure in /opt/fah/ to configure your client for the first time. Afterwards you can use a webbrowser or FAHControl on the same machine to set slots.

If you want to control it from a remote host, you have to remove the proxy line
Template error: are you trying to use the = sign? Visit Help:Template#Escape template-breaking characters for workarounds.
and perhaps add an "allow" entry and password entry.
<allow v='<ip of the host supposed to be controling the machine>'/>
<password v='password'/>

You can also allow a remote host to connect to the python web server. Just add a line like this:

<web-allow v='ip of the remote host'/>

The terminal way

In order to edit the configuration, edit the file "client.xml" in /opt/fah with the editor of your choice. For example nano:

# nano /opt/fah/client.xml 

The most important settings here are:

  • username, username associated to the work-units you return (not related to the User variable in /etc/systemd/system/foldingathome.service).
<user v='your username'/>
  • team, the team number you wish to contribute points to (earned for work units returned), you will of course want to fill in 45032, the arch-linux team number.
<team v='your team number'/>
  • bigpackets, defines whether you will accept memory intensive work loads. If you have no problem with Folding@home using up more of your RAM, then set this to big. Other settings are normal and small.
  • passkey to identify your machine. You can get one of these on the homepage. They are used to distinguish different users and/or clients.

A passkey is not actually needed. It is only used to preserve your other stats, if a client running under your own username is going nuts and is sending wrong results!

<passkey v='passkey'/>
  • Slots for CPU or GPU
 <slot id='0' type='CPU'/>

After editing that, run

# systemctl start foldingathome

to start Folding@home up.

Assuming it all ran correctly, you will want to start it when the system boots:

# systemctl enable foldingathome

Folding@home is now installed and running.

Multi-Core CPUs and Folding@home

A Quick Note On Hyperthreading

If you have a single-core hyperthreading CPU, you may be tempted to follow the multi-core instructions. It is highly recommenced that you do not do this as the Folding@home team prefers fewer results quickly, than more results slowly. There is also a time-limit on work-units, so if it runs slower, your work-units may not be returned in time, and so distributed to another user. If you have one core, run one folding process.

Multiple Folding@home Installs

Multiple installations of FAH on a single machine are useless, as in v7, you can use slots for every workload. The software is uniform now for gpu and cpu.

Monitoring Work-Unit Progress

There are several ways of monitoring the progress of your FAH client/s, both on the command line and by GUI.

The FAHControl software distributed by folding at home provides you with efficient means to control remote hosts. Just add another client with the corresponding button "Add" and enter the name, ip address, port and password (if you set one) and hit save. The software should now try to establish a connection to the remote host and show you the progress in a seperate client tab.

In AUR there is silent blades fahmon, which provides a GUI with the ability to watch multiple clients and get info on the work-unit itself. Fahmon has a dedicated site at http://www.fahmon.net/

On the CLI, you can add a command to your .bashrc , .zshrc or .whateverrc :

fahstat() {
	echo
	echo `date`
	echo
	cat /opt/fah/FAH_USER/unitinfo.txt   #(replacing FAH_USER first)
}

Or for multiple clients :

fahstat() {
        echo
        echo `date`
        echo
        echo "Core 1:";cat /opt/fah/FAH_USER/unitinfo.txt      #(replace FAH_USER first)
        echo
        echo "Core 2:";cat /opt/fah2/FAH_USER/unitinfo.txt     #(replace FAH_USER first)
}

Also, replacing cat with tail -n1 will give just the percentage of work unit complete.

On foldingathome-smp 6.43, the unitinfo.txt file is not placed inside the user folder. The correct directory would be /opt/fah-smp/unitinfo.txt.

External Resources