Difference between revisions of "Folding@home"

From ArchWiki
Jump to: navigation, search
m (Fixed reference to FAHControl AUR package)
m (Format)
Line 1: Line 1:
 
[[Category:Mathematics and science]]
 
[[Category:Mathematics and science]]
From the [https://aur.archlinux.org/packages.php?do_Details=1&ID=11852&O=0&L=&C=&K=folding&SB=&SO=&PP=&do_MyPackages=&do_Orphans=&SeB= AUR package page]: "''Folding@home is a distributed computing project which studies protein folding, misfolding, aggregation, and related diseases.''" For more information, see [http://folding.stanford.edu/].
+
 
 +
From the project [http://folding.stanford.edu/ home page]:
 +
: ''Help Stanford University scientists studying Alzheimer's, Huntington's, Parkinson's, and many cancers by simply running a piece of software on your computer. The problems we are trying to solve require so many calculations, we ask people to donate their unused computer power to crunch some of the numbers. In just 5 minutes... Add your computer to over 333,684 others around the world to form the world's largest distributed supercomputer.''
 +
 
 
== Installation ==
 
== Installation ==
  
Install {{AUR|foldingathome}} from the [[Arch User Repository]].
+
Install {{AUR|foldingathome}} from the [[AUR]].
  
 
== Configuration ==
 
== Configuration ==
Line 13: Line 16:
 
  # systemctl enable foldingathome
 
  # systemctl enable foldingathome
  
===The graphical way===
+
=== The graphical way ===
  
 
You can manage the daemon by opening a web browser and heading to http://localhost:7396/. Alternately, you can install {{AUR|fahcontrol}} and use the FAHControl program.
 
You can manage the daemon by opening a web browser and heading to http://localhost:7396/. Alternately, you can install {{AUR|fahcontrol}} and use the FAHControl program.
Line 19: Line 22:
 
The daemon can also be controlled remotely. Instructions for doing so are listed in {{ic|/opt/fah/sample-config.xml}}. Remember to open firewall ports if necessary.
 
The daemon can also be controlled remotely. Instructions for doing so are listed in {{ic|/opt/fah/sample-config.xml}}. Remember to open firewall ports if necessary.
  
===The terminal way===
+
=== The terminal way ===
  
 
To see the current progress of foldingathome, simply {{ic|tail /opt/fah/log.txt}}.
 
To see the current progress of foldingathome, simply {{ic|tail /opt/fah/log.txt}}.
Line 35: Line 38:
 
As of version 7.x, multi-core CPUs no longer require any special configuration. If you are using version 6.x, read on.
 
As of version 7.x, multi-core CPUs no longer require any special configuration. If you are using version 6.x, read on.
  
=== A Quick Note On Hyperthreading ===
+
=== 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.
 
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.
Line 41: Line 44:
 
{{Accuracy|"Hyperthreading is usually enabled in the BIOS by default, and we recommend that it stays enabled, as the SMP cores can use it to process Work Units faster." [http://folding.stanford.edu/English/FAQ-SMP#ntoc6]}}
 
{{Accuracy|"Hyperthreading is usually enabled in the BIOS by default, and we recommend that it stays enabled, as the SMP cores can use it to process Work Units faster." [http://folding.stanford.edu/English/FAQ-SMP#ntoc6]}}
  
=== Multiple Folding@home Installs ===
+
=== 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.
 
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 ==
+
== 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.  
 
There are several ways of monitoring the progress of your FAH client/s, both on the command line and by GUI.  
Line 59: Line 62:
 
  fahstat() {
 
  fahstat() {
 
  echo
 
  echo
  echo `date`
+
  echo $(date)
 
  echo
 
  echo
 
  cat /opt/fah/FAH_USER/unitinfo.txt  #(replacing FAH_USER first)
 
  cat /opt/fah/FAH_USER/unitinfo.txt  #(replacing FAH_USER first)
Line 68: Line 71:
 
  fahstat() {
 
  fahstat() {
 
         echo
 
         echo
         echo `date`
+
         echo $(date)
 
         echo
 
         echo
 
         echo "Core 1:";cat /opt/fah/FAH_USER/unitinfo.txt      #(replace FAH_USER first)
 
         echo "Core 1:";cat /opt/fah/FAH_USER/unitinfo.txt      #(replace FAH_USER first)
Line 79: Line 82:
 
On foldingathome-smp 6.43, the unitinfo.txt file is not placed inside the user folder. The correct directory would be {{ic|/opt/fah-smp/unitinfo.txt}}.
 
On foldingathome-smp 6.43, the unitinfo.txt file is not placed inside the user folder. The correct directory would be {{ic|/opt/fah-smp/unitinfo.txt}}.
  
== External Resources ==
+
== See also ==
*Folding@home [http://folding.stanford.edu/ Site]  
+
 
*Folding@home [http://folding.stanford.edu/English/FAQ FAQ]  
+
* Folding@home [http://folding.stanford.edu/ Site]  
*Folding@home [http://folding.stanford.edu/English/FAQ-Configure Configuration FAQ]
+
* Folding@home [http://folding.stanford.edu/English/FAQ FAQ]  
*Folding@home Client in the [https://aur.archlinux.org/packages/foldingathome/ AUR]  
+
* Folding@home [http://folding.stanford.edu/English/FAQ-Configure Configuration FAQ]
*Folding@home  [http://folding.stanford.edu/English/FAQ-SMP SMP Client FAQ]
+
* Folding@home  [http://folding.stanford.edu/English/FAQ-SMP SMP Client FAQ]
*Arch Folding@home [http://fah-web.stanford.edu/cgi-bin/main.py?qtype=teampage&teamnum=45032 team page]
+
* Arch Folding@home [http://fah-web.stanford.edu/cgi-bin/main.py?qtype=teampage&teamnum=45032 team page]
*Extended Arch team statistics in [http://folding.extremeoverclocking.com/team_summary.php?s=&t=45032 extremeoverclocking.com]
+
* Extended Arch team statistics in [http://folding.extremeoverclocking.com/team_summary.php?s=&t=45032 extremeoverclocking.com]

Revision as of 08:45, 6 July 2013


From the project home page:

Help Stanford University scientists studying Alzheimer's, Huntington's, Parkinson's, and many cancers by simply running a piece of software on your computer. The problems we are trying to solve require so many calculations, we ask people to donate their unused computer power to crunch some of the numbers. In just 5 minutes... Add your computer to over 333,684 others around the world to form the world's largest distributed supercomputer.

Installation

Install foldingathomeAUR from the AUR.

Configuration

Run /opt/fah/FAHClient --configure as root to generate a configuration file at /opt/fah/config.xml. (the Arch Linux team number is 45032) Alternately, you can write opt/fah/config.xml by hand and use /opt/fah/sample-config.xml as a reference. With a config file in place, you can start the daemon, check it's status, and make the daemon automatically start at boot time:

# systemctl start foldingathome
$ systemctl status foldingathome
# systemctl enable foldingathome

The graphical way

You can manage the daemon by opening a web browser and heading to http://localhost:7396/. Alternately, you can install fahcontrolAUR and use the FAHControl program.

The daemon can also be controlled remotely. Instructions for doing so are listed in /opt/fah/sample-config.xml. Remember to open firewall ports if necessary.

The terminal way

To see the current progress of foldingathome, simply tail /opt/fah/log.txt.

The behaviour of foldingathome can be customized by editing /opt/fah/config.xml. Some options that can be specified:

  • 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 uniquely identify you. Though not needed, it provides some measure of security. For details, see [1]
<passkey v='passkey'/>
  • Slots for CPU or GPU
<slot id='0' type='CPU'/>

Multi-Core CPUs and Folding@home

As of version 7.x, multi-core CPUs no longer require any special configuration. If you are using version 6.x, read on.

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.

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: "Hyperthreading is usually enabled in the BIOS by default, and we recommend that it stays enabled, as the SMP cores can use it to process Work Units faster." [2] (Discuss in Talk:Folding@home#)

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.

See also