Page 3 - The Ultimate Folding Thread

This program prints out point value information from the qd data file in readable form. It expects to find a recent copy of the data file qdinfo.dat (see above) in the folding directory, the same way qd does. With no arguments, qdiprint will produce a full dump of the point table, including all history information. If it is given numeric arguments, it will print data only for projects with those numbers. The program is started and run the same way as qd, but with a reduced set of command line flags. Here is a complete list:


Here is a sample of the output, showing the point history for projects 210 to 219 and 1108, including one which has been changed several times:


The times are not necessarily very accurate, being determined not so much by when the points were actually changed as by the time I noticed the changes on the Stanford project summary web page. I check the Stanford page automatically at 0635 and 1835 UTC (0535 and 1735 UTC during the summer), and occasionally when I use the network for other reasons, so my times could be late by as much as twelve hours.

Three precompiled binaries of this command-line version of qdiprint are available. Depending on the download method, non-Windows users may have to change the permissions of the downloaded file to make it executable.

Linux Version qdiprint (8K)
Windows Version qdiprint.exe (7K)
Mac OS X CLI Version mac_qdiprint.gz (6K)

This program converts a molecule display file in .xyz format into .pdb format. The .xyz format is used by the Folding@home client and cores, usually seen as the file work/current.xyz, which contains the XYZ coordinates and bonding information for the molecule currently being simulated. The .pdb format is an industry-standard file format for representing similar information. There are publicly-available utilities for both Windows and Linux which can display .pdb files.

Most of the code in xyz2pdb is borrowed from fpd, which also does all of this processing of the .xyz data, with the exception of outputting it in .pdb format.

With no arguments, xyz2pdb will act as a filter, that is, it will read the .xyz data from its standard input, and write the .pdb data on its standard output. It can be given command-line arguments, however, to change this behavior, including several to select only certain features for conversion. It also will, by default, ignore the bond information in its input file, and rederive it itself, sometimes avoiding errors in the input data. There is a flag to disable this default.

Here is a list of all of its flag arguments:


Two precompiled binaries of this command-line version of xyz2pdb are available. Depending on the download method, non-Windows users may have to change the permissions of the downloaded file to make it executable.

Linux Version xyz2pdb (15K)
Windows Version xyz2pdb.exe (15K)

This program is a stripped-down version of qd, which only calculates and prints a benchmark value I've proposed for predicting the performance of a machine with Folding@home work units. A similar value is printed by qd as the last line of its output, differing slightly because qd takes the partial current unit into account and qbm does not.

NOTICE: Put a recent copy of the data file qdinfo.dat (see above) into the folding directory and qbm will use it.

qbm.c

This program will attempt to repair the queue.dat file if it is suffering from several sorts of errors the client has, from time to time, made. It will try to do the following repairs:

• Check for obsolete status code 3
• Free up old entries still showing "downloading" status
• Reverse server IP addresses which are endian swapped
• Supply port 8080 if the port address is missing
• Check for orphaned results files
• Check for P limit smaller than results file

Note that this program is potentially dangerous to your Folding@home work queue, since if it finds something it thinks is wrong, it will rewrite the queue.dat file. It is strongly recommended that a copy be made of queue.dat before running qfix. It will also be a good idea to stop the running client while running qfix. If you don't, nothing really bad will happen, except that the client won't notice that anything has been done, and it will eventually overwrite the fixed queue with its own internal data.

Three precompiled binaries of this command-line version of qfix are available. Depending on the download method, non-Windows users may have to change the permissions of the downloaded file to make it executable.

Linux Version qfix (8K)
Windows Version qfix.exe (9K)
Mac OS X CLI Version mac_qfix.gz (6K)

This program will attempt to rebuild the queue.dat file if it has been lost or is unavailable. It can be used to recover orphaned work, or to prepare results to be returned by a machine which did not do the calculations. In cases where qfix can not adjust an existing queue.dat file, qgen might still succeed, but it is more complicated to run. Use qgen only if other methods have failed.

The source for qgen is not being distributed at this time. If you think you want qgen, go to this page and read the directions.

This program will look for wuinfo_xx.dat files in your folding work subdirectory and print the unit progress it sees there. It is an extremely simple program, meant to be used mainly as a diagnostic in case unitinfo.txt doesn't contain what is expected.

Two precompiled binaries of this command-line version of wuinfo are available. Depending on the download method, non-Windows users may have to change the permissions of the downloaded file to make it executable.

Linux Version wuinfo (4K)
Windows Version wuinfo.exe (5K)

Reccomended settings and installation info:
To start with I recomend you creating a new folder on your desktop in which you download the cleint to, or extract the zip file too. With a folder titled folding with all the downloaed files in (or extracted) there should be one which is a red symbol called FAH###-Console. You will need to open this.

For those who just want to reconfigure their client then you will need to open your folding folder and find the file called "client.cfg". See picture below:


When you have sicovered this folder you will need to delete it. You will not lose any of the work you have been forlding only, your information.

You are now ready to set up the console. The guidlines below are reccomendations, but every case will be differant and if you feel that the best option for you is differant to what I suggest do not worry:

After the question it will display options you can put ie: no / yes / no preferance.
The word wrapped in [] is the default anwer (if you just hit enter that is what it will take as the anwer) ie. [yes]


1) User name [annonomus] - The name you wish to fold under (for ease of use we reccomend using your forum name)

2) Team - 12912

3) Launch at startup, installing this as a service - If you have adminastative rights you can install the console as a service, after you complete all the steps , reboot and it will be running as a service. This will mean that the console will run automatically on start up and there will not be the console minimised the whole time. It will run is a way that you cannot see it, and then you can download add-ons to allow easy veiwing. Check this post: ******

4) Ask before fetching work no/yes [no] - If you are constantly connected to the internet then enter no, as it will finish the work unit and wait for you to allow it to send, wasting valuable folding time. If you are on a modem connection you should type yes, but there are other ways you can get round this issue (explained later on)

5) Use Internet Explorer settings no/yes [no] - If you do not want to use a proxy then select yes, if you do what to use a proxy then you will need to select no.

6) Use proxy yes/no [no] - This option only occurs if you select no to the above question.

7) Allow receipt of work assignments and return of results greater than 5MB in size no/yes [no] ? - If you select no, then you might download very large packets. this is not a problem for super pumped systems, but it can use lots of memory and not recomended unless you have atleat 512mb ram. I personally would select yes, alowing it to return the large packets.

8) Change advanced options yes/no [no] - If you want to fine tune things (recomended) select yes. If not select no.

9) Core priority (idle/low) [idle] - I would always pick lowest possible option (recommended) . The slightly higher option is good if another program is causing FAH to lag or stop working. Just note that it might cause your other programs to Lag.

10) CPU usage requested (5-100) [100] - You will of course be setting it to 100%. If you are on a laptop then you may want to put this as lower to deal with the heat. FAH will only use spare cycles so having it on wont in theory impair your performance.

11) Disable highly optimized assembaly core (no/yes) [no] - This will turn off FAH's ability to use your CPU's SSE and SSE2 code. This will slow down the folding process, so you should type no.

12) Pause if batterypower is being used (no/yes) [no] -This will stop the folding console when you are using battery power on your laptop. Usefull if on a laptop, but if on a sesktop then type no.

13) Interval Between Checkpoints (3-30) [15?] - IF you only have your computer on a few hours at a time st it to about 10. If you are folding 24/7 then set it at 20 or 30. Note: the shorter the checkpoint interval the longer the Workunit takes because FAH has to write checkpoint files more often, which means less time actual folding.

14) Request work units without deadlines (no-pref/no/yes) [no-pref] - "no-pref" will alolow you to run all the units available. " no " will make you run normal units with deadlines, " yes " will set your workunits for timeless, this is good for systems under 500Mhz or faster systems that do not run 24/7.

15) Ignore any deadline information (no/yes) [no] - This is usfull as, if you are overclocking, or often reset your cmos then if you boot up the folding console it will think you have missed the hand in date when you have not. " yes " if your computer has frequent clock errors. " no " if not.

16) Machine ID (1-8) [1] - Always pick " 1 '' unless you are running 2 clients on each machine. This however is not reccomended. See this post: *****

After you are done it should look somthing like this:

Recommended settings and installation info:
The first thing you will notice about the graphical client is that it had a proper GUI (Graphical User Interface) for you to input your details into. This makes the process a lot easier if you are a novice to DOS command prompt. This version is pretty well self explanatory but we have still provided a simplified guide to setting it up correctly.

Pages:

1) Welcome: This page serves no actual purpose for folding, but is there to welcome new people to the folding community.

2) Licence Agreement: Just agree to this.

3) Readme Information: This presents the history of updates and versions of the F@H client.

4) User Information:
Name – The name you wish to fold under (to save confusion of use we recommend using your forum name)

5) Choose Destination Directory: This is where you want the graphical client to be installed. You can either select your own folder, or simply use the default: C:\Program Files\ Folding@Home.

6) Select Program Folder: again this is basic instillation stuff. Just leave it as the default to save time.

7) Start Copying Files: Click next to begin the instillation of the client.

8) Once the Instillation is complete you will be presented with a page asking you to continue (this should have two check boxes, one for Open the Application and one for View readme). You do not need to view the readme as you have already seen it earlier. However you may do so if you wish. Click next and the clients Control panel will open.








Control Panel:
User –
User Name: this will be the same as the one entered earlier, but you can change it here if you wish.

Team Number: This is most important. Dev.Hardware’s team number is 12912.

There are also three buttons that allow you to View:
-Team Stats
-User Stats
-Log Files

These are useful for checking up on how you and Dev.Hardware are doing.







Connection -

Ask before fetching/sending work: Unless you have dial up we recommend No for this option. This allows F@H to automatically send off completed work units and download more.

Use Internet Explorer Settings: If you do not want to use a proxy then select yes, if you do what to use a proxy then you will need to select no.

Proxy Settings: This will allow you to configure your own Proxy settings if you do not wish the client to use IE settings.





Display -

Molecule Draw Rate: this slider allows you to set how fast the visualisations will appear on screen (not this will control the speed at which the client folds)

Title: You can add personal text to the title if you wish.

Logo: You can also add a personal logo to be displayed in the client window.




Advanced -

Core Priority: Low or Idle. Low may cause some low priority programs to lag slightly (however 9.x does not have many Low processes, and you will be unlikely to notice a difference). Or Idle, which will permit the client to only use Idle clocks from the CPU. We recommend Low, as it will allow for maximum folding.

Processor Usage: this slider sets a percentage of the CPU to be used. The more you allow, the faster you will fold. We recommend 100% for this. If you are on a laptop you may wish to put this lower to deal with the heat. This option can be used to restrict the amount of cycles F@H can use (for instance if 98% CPU is Idle, and you set it to 5% then F@H will only be able to use 5%. But if you set it to 100% then F@H will use the full amount of Idle cycles, 98%).

Disable Highly Optimised Assembly Code: This will turn off F@H's ability to use your CPU's SSE, 3Dnow and SSE2 code. This will slow down the folding process, so you should not select this.

Check Points: This slider allows you to select how often F@H makes checkpoints of it‘s work. It allows you to select values between 3 and 30 minutes.

Ignore Deadline Information: This is useful as, if you are overclocking, or often reset your CMOS, then if you boot up the folding console it will think you have missed the return date when you have not. Select it if your computer has frequent clock errors. But leave it blank if not. Note that if you return a WU after the actual date it was requested for it may not be used.

Client Type: this dropdown menu allows you to select from Folding@Home Genome@Home or “No Preference”. Selecting G@H will give you WU’s with no deadlines. We recommend selecting no-pref. For this option.




Once fully configuerd it should look something like this:

Whilst there was a version available for download, it has been taken down due to a few reasons. This is now currently under development, so check back here fore updates!

This guide was written by Anubis, and I would like to say a big THANKYOU to him for his efforts...

Recommended settings and installation info:
As with the XP versions, we recommend that you create a new folder on your desktop in which you download or extract the client. Open this folder once you have downloaded or extracted the files and open “FAH#Console”. You will now have a Command Prompt DOS window open.


Baisic settings
1) User name [anonymous] - The name you wish to fold under (to save confusion of use we recommend using your forum name).

2) Team Number [0] - This is most important. Dev Hardware’s team number is 12912.

3) Ask before fetching/sending work <yes/no> [no] - Unless you have dial up we recommend No for this option. This allows F@H to automatically send off completed work units and download more.

4) Use Internet Explorer Settings <yes/no> [no] - If you do not want to use a proxy then select yes, if you do what to use a proxy then you will need to select no.

5) Use Proxy Settings <yes/no> [no] - This will only appear if you select ‘no’ above. This option allows you to use a proxy.

6) Change Advanced options <yes/no> [no] - We recommend yes for this. It will allow you to fine-tune F@H.

B]Advanced Settings:[/B]

1.) Client Type <no-pref/fah/gah> [no-pref] - this allows you to select the clients you will be running (any, Folding at Home or Genome at Home). We recommend no-pref for this. However if you wish to receive WU’s with no deadline (this is useful if you are folding no an old machine with little power…) than select GAH.

2.) Core Priority <idle/low> [Idle] - You can either use Low, which may cause some low priority programs to lag slightly (however 9.x does not have many Low processes, and you will be unlikely to notice a difference). Or Idle, which will permit the console to only use Idle clocks from the CPU. We recommend Low, as it will allow for maximum folding.

3.) CPU usage requested <5-100> [100] – We recommend 100% for this. If you are on a laptop you may wish to put this as lower to deal with the heat. This option can be used to restrict the amount of cycles F@H can use (for instance if 98% CPU is Idle, and you set it to 5% then F@H will only be able to use 5%. But if you set it to 100% then F@H will use the full amount of Idle cycles, 98%).

4.) Disable highly optimised assembly core <no/yes> [no] - This will turn off F@H's ability to use your CPU's SSE and SSE2 code. This will slow down the folding process, so you should type no.

5.) Interval Between Checkpoints <3-30> [15?] - If you only have your computer on a few hours at a time set it to about 10. If you are folding 24/7 then set it at 20 or 30. Note: the shorter the checkpoint interval the longer the Workunit takes because F@H has to write checkpoint files more often, which means less time actually folding.

6.) Ignore deadline information <no/yes> [no] - This is useful as, if you are overclocking, or often reset your CMOS then if you boot up the folding console it will think you have missed the return date when you have not. "yes" if your computer has frequent clock errors. "no" if not. Note that if you return a WU after the actual date it was requested for it may not be used.

7.) Machine Id <1-8> [1] – Use a different number for each machine you install the client on. You CAN install the client under the same user on multiple machines (meaning you can fold on all the machines you have access too). Note you should NOT install multiple clients on the same machine, see post *****

After you are done it should look something like this:



The client will then begin to fold straight away. It will automatically download a WU (unless you have specified it to ask first, in which case it will) and start folding.



You can close the client if you need to by pressing “Ctrl-C” and then exiting. However we don’t recommend you do this unless the workunit has finished and been sent off or it has just created a check point as you will loose any work done between then and the previous checkpoint.

We also recommend that you set-up a selection of shortcut for the client (for easy access and alteration).

-First make a shortcut to the desktop, right click it and go to Properties. Add the tag “ -configonly” to the shortcut directory. This, when opened, will allow you to alter your settings, but then close off without starting to fold (this is useful if you are already running the client). Then re-name the shortcut to something like F@H Config.

-If you want the client to start up with windows then simply create a shortcut to it, name it whatever you please (F@H to be simple) and go to system tools, Scheduled Tasks. Simply drag and drop the shortcut into the scheduled tasks window and then double click on it. Go to the schedule tab and set it to start “At system startup” (alternatively you could set it to “At Login” however we do not recommend this as it will only run when that single user logs into windows and so the rest of the time the client will not run).

Every time a frame is completed the console will add a line saying "[time] Finished a frame [#]".

Good luck and happy folding

This guide was written by Anubis, and I would like to say a big THANKYOU to him for his efforts...

This guide was written by Anubis, and I would like to say a big THANKYOU to him for his efforts...

Recommended settings and installation info:
The first thing you will notice about the graphical client is that it had a proper GUI (Graphical User Interface) for you to input your details into. This makes the process a lot easier if you are a novice to DOS command prompt. This version is pretty well self explanatory but we have still provided a simplified guide to setting it up correctly.

Pages:

1) Welcome: This page serves no actual purpose for folding, but is there to welcome new people to the folding community.

2) Licence Agreement: Just agree to this.



3) Readme Information: This presents the history of updates and versions of the F@H client.



4) User Information:
Name – The name you wish to fold under (to save confusion of use we recommend using your forum name)



5) Choose Destination Directory: This is where you want the graphical client to be installed. You can either select your own folder, or simply use the default: C:\Program Files\ Folding@Home.



6) Select Program Folder: again this is basic instillation stuff. Just leave it as the default to save time.

7) Start Copying Files: Click next to begin the instillation of the client.



__________________________________________________ ___________________


Once the Instillation is complete you will be presented with a page asking you to continue (this should have two check boxes, one for Open the Application and one for View readme). You do not need to view the readme as you have already seen it earlier. However you may do so if you wish. Click next and the clients Control panel will open.

Control Panel:
User –
User Name: this will be the same as the one entered earlier, but you can change it here if you wish.

Team Number: This is most important. Dev.Hardware’s team number is 12912.

There are also three buttons that allow you to View:
-Team Stats
-User Stats
-Log Files

These are useful for checking up on how you and Dev.Hardware are doing.




Connection -

Ask before fetching/sending work: Unless you have dial up we recommend No for this option. This allows F@H to automatically send off completed work units and download more.

Use Internet Explorer Settings: If you do not want to use a proxy then select yes, if you do what to use a proxy then you will need to select no.

Proxy Settings: This will allow you to configure your own Proxy settings if you do not wish the client to use IE settings.




Display -

Molecule Draw Rate: this slider allows you to set how fast the visualisations will appear on screen (not this will control the speed at which the client folds)

Title: You can add personal text to the title if you wish.

Logo: You can also add a personal logo to be displayed in the client window.



Advanced -

Core Priority: Low or Idle. Low may cause some low priority programs to lag slightly (however 9.x does not have many Low processes, and you will be unlikely to notice a difference). Or Idle, which will permit the client to only use Idle clocks from the CPU. We recommend Low, as it will allow for maximum folding.

Processor Usage: this slider sets a percentage of the CPU to be used. The more you allow, the faster you will fold. We recommend 100% for this. If you are on a laptop you may wish to put this lower to deal with the heat. This option can be used to restrict the amount of cycles F@H can use (for instance if 98% CPU is Idle, and you set it to 5% then F@H will only be able to use 5%. But if you set it to 100% then F@H will use the full amount of Idle cycles, 98%).

Disable Highly Optimised Assembly Code: This will turn off F@H's ability to use your CPU's SSE, 3Dnow and SSE2 code. This will slow down the folding process, so you should not select this.

Check Points: This slider allows you to select how often F@H makes checkpoints of it‘s work. It allows you to select values between 3 and 30 minutes.

Ignore Deadline Information: This is useful as, if you are overclocking, or often reset your CMOS, then if you boot up the folding console it will think you have missed the return date when you have not. Select it if your computer has frequent clock errors. But leave it blank if not. Note that if you return a WU after the actual date it was requested for it may not be used.

Client Type: this dropdown menu allows you to select from Folding@Home Genome@Home or “No Preference”. Selecting G@H will give you WU’s with no deadlines. We recommend selecting no-pref. For this option.



Once fully configuerd it should look something like this:



This guide was written by Anubis, and I would like to say a big THANKYOU to him for his efforts...

This guide was written by Moistmule, and I would like to say a big THANKYOU to him for his efforts...

Firstly I recommend you create a new folder on your desktop or in your home directory, to which you will download the client, as several files are created and it is both tidier and safer to keep them all in their own folder. In this example we will create a folder called 'fold' in your home directory. We will be using the terminal throughout this how-to, so open up a terminal now.

With the terminal open, type; (Note: All of the following commands are to be run as you, not root)

Now list the contents of this directory;

The output should be something like this;



Now we need to modify your freshly downloaded client so that it is executable;

Now execute it;


You are now ready to set up the console. The guidelines below are recommendations, but every case will be different and if you feel that the best option for you is different to what I suggest do not worry:

After the question it will display options you can put ie: no / yes / no preference. The word wrapped in [] is the default answer (if you just hit enter that is what it will take as the answer). i.e. [yes]

Basic Options:

1) User name [anonymous] - The name you wish to fold under (for ease of use we recommend using your forum name)

2) Team - 12912, this is DevFolding's Team Number

3) Ask before fetching work no/yes [no] - If you are constantly connected to the Internet then enter no, as it will finish the work unit and wait for you to allow it to send, wasting valuable folding time. If you are on a modem connection you should enter 'yes', but there are other ways you can get round this issue (explained later on)

4) Use proxy yes/no [no] - This option only occurs if you select no to the above question. If you have a proxy connection at home, you probably know about it. If this is at work, or at another institution then please see your System Administrator.

5) Allow receipt of work assignments and return of results greater than 5MB in size no/yes [no] ? - If you select yes, then you might download very large packets. This is not a problem for super pumped systems, but it can use lots of memory and not recommended unless you have at least 512MB of RAM. I have selected no, denying the download of large WU.

6) Change advanced options yes/no [no] - If you want to fine tune things (recommended) select yes. If not select no.

Advanced Options:

1) Core priority (idle/low) [idle] - I would always pick lowest possible option (recommended) . The slightly higher option is good if another program is causing FAH to lag or stop working. Just note that it might cause your other programs to lag. Loss of game performance has been seen. I would suggest you stopped your client before launching any games or other resource-heavy programs, then started up again once it has finished.

2) Disable highly optimized assembly core (no/yes) [no] - This will turn off FAH's ability to use your CPU's SSE and SSE2 code. This will slow down the folding process, so you should keep the default, no.

3) Interval Between Checkpoints (3-30) [15?] - If you only have your computer on a few hours at a time set it to about 10. If you are folding 24/7 then set it at 20 or 30. Note: the shorter the checkpoint interval the longer the work unit takes because FAH has to write checkpoint files more often, which means less time actually folding.

4) Request work units without deadlines (no-pref/no/yes) [no-pref] - "no-pref" will allow you to run all the units available. "no" will make you run normal units with deadlines, "yes" will set your work units to be only of the 'timeless' variety, this is good for systems under 500Mhz or faster systems that do not run 24/7.

5) Ignore any deadline information (no/yes) [no] - This is useful as, if you are overclocking, or often reset your CMOS then if you boot up the folding console it will think you have missed the hand in date when you have not. "yes" if your computer has frequent clock errors. "no" if not.

6) Machine ID (1-8) [1] - You'll only be reading this if this is your first experience with F@H, so therefore I can assume this is your first machine. If so, choose "1". If you start using other machines at a later date, then number them subsequently. It is not advised to run two clients on the same machine.

After you are done it should look something like this:


Press enter for a final time and watch the magic happen! The above settings you entered will be saved in a file called 'client.cfg' and used every time you start your client. Delete this file if you need to re-start the setup process from scratch.

Welcome to DevFolding! FOLD to CURE!

This guide was written by Moistmule, and I would like to say a big THANKYOU to him for his efforts...

Mac command line

Mac graphical

Mac screensaver...