UbuntuHelp:FoldingAtHome
来自Ubuntu中文
Overview
Folding@Home is a project from Stanford University that uses millions of networked PCs to form a supercomputer for protein folding simulations. The client software is loaded on a PC, it contacts the central servers, and receives "work units". The client then runs on spare CPU time, and uploads finished work units to the server.
When proteins are created, they undergo a complex process known as folding, so-called because the protein molecule transforms from a long chain of amino acids to a complex shape (it "folds up"). The final shape of the protein is absolutely critical to determining its properties and function. Scientists have created software to simulate the folding process to better understand how proteins work, which in turn makes it possible to develop new drugs, cure diseases, etc.
Folding@Home is a great way to make your computer do useful work even when you're not using it. Since it runs at a very low priority, you should never realize it's running when you're using the computer to do your work. Note that "using the computer" refers to doing heavy computations. Generally, tasks like web browsing and word processing involve very little CPU usage, so the Folding@Home client will be running at near 100% even when doing those kinds of tasks. It helps to leave your computer on at all times, but is not necessary, as the project will benefit from virtually any time that the client runs on your computer.
Installation
Two installers are mentioned here. fah_install is an installer/init script that works with Debian systems (including Ubuntu). finstall seems to be the all-purpose Unix installer. You can also do things by hand, by just downloading the client and running it some directory. I recommend fah_install, but I'm biased because I wrote it <wink>.
Before using either installer, you may want to pick a username and a team. Neither is necessary, but having a unique username lets you know how much you are folding, and folding for a team adds to the fun. Because you're a fan of Ubuntu, you probably want to fold for Team Ubuntu; the team number is 45104. You can pick any username you want, but if you pick one that's already being used, that will make it impossible to track your score and will inflate someone else's score, which may or may not be welcome. Search for unused names here. The default for both username and team is anonymous.
fah_install
Edgy users: Due to the change from bash to dash in Edgy, previous init scripts don't work. The fix is easy: download the latest installer, untar it, and run sudo ./install.sh update. It will replace the old init script with a new one. You do not have to stop a running client to do this update, but it is probably a good idea to stop it anyway. Please report any Edgy problems to the how-to thread.
The following script will download the latest client from the Folding@Home website, and install it to opt/foldingathome, either in / or $HOME. It will ask you to set up the client (the defaults are usually sufficient), and copy that configuration for every CPU in your machine.
- attachment:fah_install-20061219.tar.gz
It is not possible to provide a .deb package for Folding@Home, because the client must be downloaded from Stanford's website. This is to ensure the integrity of the research. (Maybe it is possible to have a .deb; after all, this is how Macromedia Flash works. The point is that the executable has to be downloaded from Stanford.)
To install, download the tarball and do
tar zxvf fah_install-20061219.tar.gz
</code>
This should extract the archive to a directory called <code>fah_install/</code>. Then
<pre>
cd fah_install
less README
</code>
to read the documentation.
Finally,
<pre>
sudo ./install.sh install
</code>
to install the client.
You can also install to your <code>$HOME</code>, in case you do not have root access to the computer. Clearly, you would not have to prefix the command with sudo in this case. If you install to your <code>$HOME</code>, a cron job will be created to start the client automatically. If you install to the system, the client will automatically start when your computer boots up.
You can reconfigure the client using the supplied <code>reconfigure</code> script, which is placed in <code>opt/foldingathome</code>. You can also give the client command line options in <code>/etc/default/foldingathome</code>. See the README for more details.
Should you choose to uninstall the client, it's easy. The first installation script contains an uninstalling script too. Just go to the directory fah_install and run <code>install.sh</code> with uninstall parameter. Use sudo to uninstall if you used sudo to install. The README file provides instructions for manual uninstall.
<pre>
sudo ./install.sh uninstall
</code>
==== finstall ====
1. Download the finstall script with wget:
<pre>
cd ~
wget -c http://www.vendomar.ee/~ivo/finstall
</code>
2.#2 Make the script runnable:
<pre>
chmod +x finstall
</code>
3.#3 Start it:
<pre>
./finstall
</code>
After the client is installed You can start/stop/... FAH client with ./foldingathome/folding script. For Example(s)
<pre>
~/foldingathome/folding start
or
~/foldingathome/folding stop
or
~/foldingathome/folding status
</code>
For me this was all I needed as it automatically created the init scripts I needed to start after reboot. However the init scripts don't seem to work for everyone, so if you need to do it manually:
1. Make a file called foldingathome in the /etc/init.d directory:
<pre>
gksudo gedit /etc/init.d/foldingathome
</code>
2.#2 Paste this in:
<pre>
#!/bin/sh
# /etc/init.d/foldingathome for Ubuntu
# Start the F@H service.
pushd /home/YOUR_USERNAME_HERE/foldingathome/
su YOUR_USERNAME_HERE -c "screen -d -m ./folding start"
popd
</code>
3.#3 Save and exit
4. Make a symlink into the /etc/rc2.d directory:
<pre>
sudo ln -s /etc/init.d/foldingathome /etc/rc2.d/S99fah
</code>
Here are a couple more hints to make things go smoother:
1. Pick a username before you start, to see if your username is in use visit this page first [http://folding.stanford.edu/download.html]. There is a search box at the top that you can use to see if your selected username is in use.
2. Have your team number ready, it is question two right after your username. You should use '''''45104''''' for this.
3. If you have an old computer you should run deadlineless work units. To select the option to do this select yes when asked if you want to set advanced options, then continue to select the defaults until you are asked about deadlineless workunits and select yes. ''Note: There are frequent shortages of the deadlineless WUs. If you haven't gotten one for several days, you might as well ask for both deadlineless and normal WUs.''
4. Finally here is a link to the original thread for using the finstall script from the folding community forums, it is where I found my answers and definitely the easiest way to get this working under Dapper Drake. [http://forum.folding-community.org/viewtopic.php?t=2283]
=== Other Issues ===
==== Questions and Discussion ====
For technical questions and bug reports, go to the [http://ubuntuforums.org/showthread.php?t=101817 HowTo forum thread]. For casual talk about Folding@Home, use the [http://ubuntuforums.org/showthread.php?t=102313 Ubuntu Team recruiting thread].
==== Security ====
Folding@Home is [http://folding.stanford.edu/faq.html#misc.security secure]. The Stanford team has gone to great lengths to ensure security, both for the integrity of their research and the safety of donors' computers. However, the more secure the better. The Gentoo ebuild for Folding@Home creates a new user foldingathome whose sole purpose is to run the client. Now ''fah_install'' offers the same. It creates a user whose account is disabled, and runs the client as this user when the init script is run as root, so the client is never run as root.
==== Hyper Threading ====
For those with Hyper Threading CPUs, you probably know that an SMP kernel sees two processors. Then clearly, if you run two clients, you will get more work done than if you only run one (probably about 10-30% more). However, results that are done quickly are more useful than more results done slowly. The reason is that each work unit is a step in a giant simulation, with future steps depending on past ones. So the faster you get your work done, the faster the simulation can move along. Long story short, run one client for each ''physical'' CPU, not for each ''logical'' CPU. The installer should automatically count the number of CPUs in your system. See this [http://forum.folding-community.org/viewtopic.php?t=10427 post] in the Folding@Home forums.
==== Laptop Systems ====
Because the client runs at low priority, the client should not cause the CPU governor to kick up the frequency. In other words, even though the client runs at 100% CPU usage, it should not cause the CPU frequency to go up, which keeps the fan slow and quiet. If this is not the case, then the frequency governor should be reconfigured.
'''Note: Feisty uses different default cpu governing method than Dapper (I don't know about Edgy).''' Feisty uses a kernelspace governor whereas Dapper uses a userspace one (<code>powernowd</code>). The consensus seems to be that kernelmode is the superior implementation. The trouble is that the default is not to ignore nice'd processes (i.e. low priority processes like the folding@home client) in kernelmode, while <code>powernowd</code>'s default is to ignore nice'd processes in it's calculations. To get <code>powernowd</code> behavior, you must do the following:
<pre>
sudo -i
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load
</code>
To enable this behavior in the future, add the above (just the <code>echo</code> line, not the <code>sudo</code> one) to <code>/etc/rc.local</code>.
There is a utility called <code>cpulimit</code> that will limit the CPU time of a given application. Look at this [http://pykeylogger.sourceforge.net/wiki/index.php/Ubuntu:Chronicles#Folding.40Home_.5BFAH.5D_on_a_Laptop link] for a quick how-to. If there is demand, I will add support for it to ''fah_install''.
One can configure ACPI (the power regulation subsystem) to stop the client when the system goes on battery power, and to start it again when the power cord is plugged back in.
===== Breezy and older =====
Edit <code>/etc/acpi/power.sh</code>. Inside the <code>if [ $? = 0 ] && [ x$1 != xstop ]; then</code> block, add
<pre>
# stop folding at home
if [[ -x /etc/init.d/foldingathome ]] ; then
/etc/init.d/foldingathome stop
fi
</code>
and inside the <code>else</code> block, add
<pre>
if [[ -x /etc/init.d/foldingathome ]] ; then
/etc/init.d/foldingathome start
fi
</code>
===== Dapper and newer =====
Simply create two scripts in the relevant directories.
<pre>
sudo -i
echo "/etc/init.d/foldingathome stop" > /etc/acpi/battery.d/fah.sh
echo "/etc/init.d/foldingathome start" > /etc/acpi/ac.d/fah.sh
exit
</code>
This assumes that the client has been installed for the entire system (as opposed to installing just for your user), which it should be if you are able to edit files in <code>/etc</code> in the first place!
=== TeamUbuntu (45104) ===
A competitive Folding@Home team called [https://wiki.ubuntu.com/FoldingAtHomeTeamUbuntu TeamUbuntu] exists to represent the Ubuntu community and to have some fun while doing good. The team number is '''45104'''. To join the team, simply enter 45104 when the setup dialog requests a team number.
=== FAQ ===
==== ''How do I uninstall?'' ====
If you used ''fah_install'', the installer on this page, rerun the installation script with the "uninstall" option. The README file has a detailed description of what the uninstall command does. If you used ''finstall'', cd to <code>$HOME/foldingathome</code> and run <code>./uninstallService</code>. If you just downloaded it to some directory, just delete the client and the directory. See also the next question about random files.
==== ''Why does F@H write files to random directories?'' ====
If you use ''fah_install'' or ''finstall'', it shouldn't. That was half of the reason why those scripts were written. The client writes a bunch of files to some directory, we'll call it the working directory or WD, if the WD doesn't have all of the files already. So if you have no F@H files in the WD, the client will write them. How do you figure out what the WD is? It is the current directory of the shell that starts the client; in other words, it could be anything. If you have a script of some sort that you wrote to start up the client, you need to <code>cd</code> to whatever directory you want all of those files to be written to before starting the client.
<pre>
cd /working/directory
/path/to/FAH502-Linux.exe
</code>
==== ''How do I find out how much I'm folding?'' ====
The client writes a log file in <code>WD/FAHlog.txt</code>. For ''fah_install'', this is in <code>/opt/foldingathome/#/FAHlog.txt</code> or <code>$HOME/opt/foldingathome/#/FAHlog.txt</code>, where '#' is a digit from 1 to 9, but probably only 1 will exist unless you have a multiprocessor system. If you use ''finstall'', it is in <code>$HOME/foldingathome/CPU#</code>.
There is also a more concise progress file <code>unitinfo.txt</code>, in the same directory as <code>FAHlog.txt</code>.
There are nice graphical programs that will display the information in these files, for example [http://sourceforge.net/project/screenshots.php?group_id=164311 Protein Think]. You can see how many points your current work unit is worth by looking up your protein on http://fah-web.stanford.edu/psummary.html
==== ''I don't seem to be making any progress.'' ====
If the log looks something like this:
<pre>
[19:39:55] + Attempting to get work packet
[19:39:55] - Connecting to assignment server
[19:39:57] - Successful: assigned to (171.64.122.133).
[19:39:57] + News From Folding@Home: Welcome to Folding@Home
[19:39:57] Loaded queue successfully.
[19:39:58] + Could not connect to Work Server
[19:39:58] - Error: Attempt #9 to get work failed, and no other work to do.
</code>
then you probably have everything set up correctly, and the problem is on Stanford's side. Some people have encountered this when asking for deadlineless units, because there appears to be shortages of those.
If you can't connect to the assignment server, then probably you're behind a firewall or proxy or something else that is preventing the connection. Ask your network administrator how to get around this. F@H can be set to use different TCP ports, but the default is 8080.
==== ''How do I backup my work?'' ====
It's a good idea to stop folding before making your backup, though it isn't absolutely necessary. Assuming you used ''fah_install'', then make a tarball of foldingathome directory.
<pre>
sudo tar zcvf fahbck.tar.gz /opt/foldingathome/ /etc/default/foldingathome
</code>
If you haven't modified the file <code>/etc/default/foldingathome</code>, then you don't need to add it. Clearly, <code>/opt/foldingathome</code> would become <code>/home/$USER/opt/foldingathome</code> if you installed it in your home directory.
==== ''How do I restore my backup?'' ====
<pre>
cd /
sudo tar zxvf /path/to/fahbck.tar.gz
</code>
If you somehow destroyed the <code>/etc</code> directory (e.g. you reinstalled the operating system), then use the installer with the "update" option to replace the init symlinks, so it can start automatically at boot time.
=== Links ===
* [http://folding.stanford.edu/ Folding@Home project home page]
* [https://wiki.ubuntu.com/FoldingAtHomeTeamUbuntu Homepage for the Ubuntu F@H Team]
* [http://fah-web.stanford.edu/cgi-bin/main.py?qtype=teampage&teamnum=45104 Team Ubuntu statistics]
* [http://ubuntuforums.org/showthread.php?t=102313 Team Ubuntu recruiting forum thread, casual discussion]
* [http://www.ubuntuforums.org/showthread.php?t=101817 Ubuntu Forms F@H HowTo, technical discussion]
* [http://fah-web.stanford.edu/psummary.html Practical information on the current projects]
* [http://sourceforge.net/project/screenshots.php?group_id=164311 'Protein Think' folding progress monitor]
* [http://fahstats.com/t.php?t=45104 Folding@Home statistics for Team Ubuntu]
* [http://folding.extremeoverclocking.com/team_summary.php?s=&t=45104 Another statistics site]
* [http://techreport.com/etc/2002q4/foldingimpact/index.x?pg=1 Report on the impact of F@H to the system; a bit outdated, but still true.]
* [http://fahwiki.net/index.php/Sneakernetting Sneakernetting] How to deal with non-networked machines.
* [http://fah-web.stanford.edu/psummary.html Current proteins summary.] You can look up your current protein and see how many points a WU is worth.
----
CategoryDocumentation
[[category:UbuntuHelp]]
