Folding Forum

by **PantherX** » Wed Mar 19, 2014 9:41 pm

Welcome to the Official F@H Support Forum. Thank you for downloading the F@H Software and contributing to the F@H Project. Please find below sections of helpful information that will help you understand more about the F@H Software and your contribution to the F@H Project.

In all cases, if you have changed the "verbosity" setting, reset it to the default value before posting your log.
In all cases, include the segment beginning with ******* System *******

Below is an index to help you navigate this thread with ease:

1 - Getting Help With Folding@Home -> An introduction to the F@H support system

2 - Temporary Restrictions For New Members -> Newly registered members may find this useful

3 - Introduction To Common F@H Jargon -> Brief overview of vocabulary specific to the F@H Community

4 - How To Post A Log File (Windows Vista/7) -> Instructions on how to post a log file from the V7 F@H Client here on the Forum

5 - How To Post A Log File (Windows 8/8 +) -> Instructions on how to post a log file from the V7 F@H Client here on the Forum

6 - How To Post A Log File (Linux) -> Instructions on how to post a log file from the V7 F@H Client here on the Forum

7 - How To Post A Log File (OSX) -> Instructions on how to post a log file from the V7 F@H Client here on the Forum

8 - How To Post A Log Snippet (Chrome Folding App) -> Instructions on how to post a log snippet from the Chrome Folding App here on the Forum. See also NaCl Client open beta.

9 - Importance Of Deadlines -> Learn more about the time constraints of the work your computer is performing for F@H

10 - V7 Interface -> Information on the V7 F@H Client interface

11 - Adding Slot Options In V7 -> Instructions on how to tweak the Slots present in F@H Client V7

12 - Connectivity Issues In V7 -> What to do when Web Control, Advanced Control (AKA FAHControl) won't connect to FAHClient

13 - Troubleshooting Tips -> Advise for common issues for F@H Software

14 - Additional Links -> Other articles to learn more about the F@H Project

Thanks to bollix47, bruce, Joe_H, P5-133XL and 7im for helping me with this write-up. Additional comments are welcomed via Private Message (PM) to me.
Last Updated 23-Mar-2014 - PantherX

by **PantherX** » Wed Mar 19, 2014 9:41 pm

1 - Getting Help With Folding@Home

Some of you may have found this Forum because you encountered an issue when attempting to run a F@H Client, while others want to learn more about the F@H project. Either way, there are a number of resources allowing for self-helping and self-learning which you can avail:

1) You can start by searching this Forum to see if someone else has already reported the same problem. If so, you can try the suggested solutions (if applicable).
2) You could try reading the FAQs to see if your question is answered.
3) You can also find some helpful information in the FaHWiki if you are using an older version of the F@H Client.

We're happy to help you with any kind of F@H related problems. Most of the time we'll need information from you to help diagnose your problem. The log is a very vital source of information when it comes to troubleshooting the F@H Clients.

Two parts of the log are really important:
A) The first ~100 lines of the log, showing essential information about your system, including any settings that are in your Config file
B) Portions of the log showing any error messages that may be present, especially the first one.

For the registered Members, please note that our General Policies can be found here.

by **PantherX** » Wed Mar 19, 2014 9:42 pm

2 - Temporary Restrictions For New Members

Please note that if you have recently joined this Forum, you may not be able to use some of the Forums' features initially. Our anti-spam policy sets a threshold just high enough that a spam-bot is unlikely to reach, while the Donors can provided they are around long enough. Some of the features that you initially can't use are:

1) Can't post URLs.
2) Can't quote another user.

By participating normally, these temporary restrictions will be automatically removed.

by **PantherX** » Wed Mar 19, 2014 9:43 pm

3 - Introduction To Common F@H Jargon

While browsing this Forum, you may come across some unusual acronyms which are commonly used by F@H Donors. Below is a list of commonly used acronyms:

WU - Work Unit is a small time-slice of protein processing that is downloaded by your F@H Client from the appropriate Server. Your computer will process it and once it finishes folding, will upload the result to the Server and will request another WU.
Note: The duration to process this WU will vary from few minutes to few days depending on the type of WU, F@H Client, computer usage and several other factors. You will receive credits for a WU once it is successfully uploaded to the Servers and the Official Stats are updated (happens every hour).

PRCG - Project Run Clone Gen, is used to identify a WU that is assigned to you. A simple explanation and a detailed one can be read for further explanation.
Note: For a given Project number (and Protein name) there are many Runs, Clones and Gens so don't be alarmed if you seem to be processing the same Project/Protein again. The F@H Project doesn't assign duplicate WUs on purpose to keep Donors folding.

PPD - Points Per Day is the total number of points your computer is generating while folding the assigned WU(s).
Note: PPD will vary from WU to WU (even if they belong to the same Project) and will be effected by computer usage and other factors.

TPF - Time Per Frame means how long it takes to finish 1% of the assigned WU. 1% of a WU is equal to one frame.
Note: The TPF can vary significantly if the computer is being used. A dedicated folding computer experiences less fluctuations.

A list of further abbreviations is available here.

by **PantherX** » Wed Mar 19, 2014 9:44 pm

4 - How To Post A Log File (Windows Vista/7)

First: if you have adjusted the verbosity setting, remove that setting and restart FAH.
If you are using the V7 F@H Software, there are a couple of methods that you can use to locate, copy and paste your log to this Forum.
* We don't need the progress messages between 2% and 99% and they can be removed but be sure to include the first couple of pages.
* Please note that the Forum has a limit of 60,000 characters so if you encounter this limit, you can remove repetitive messages. Also, you can split your log file across multiple posts.
* Please use the default setting of Verbosity Level 3 since any higher will print additional data that is unnecessary which makes it very difficult to troubleshoot in the majority of cases.

You can choose any of the following methods.

Method 1
1) Ensure that FAHClient is running by looking for the F@H icon in the notification area of the task bar
2) Right click the F@H icon
3) Select Advanced Control from the menu options
4) Once Advanced Control opens, select the Log tab
5) Untick Follow
6) Click the Refresh button
7) Click the Copy button
8) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
9) Click the Code Tag button
10) Within the Code Tag, paste the log
11) Click the Submit button to post your post. %

Method 2
1) Click the Start Button
2) Click on All Programs
3) Click on FAHClient folder
4) Click on Data Directory folder
5) A window will open which will contain F@H files and folders. Depending on your need, focus on:
> A) log file -> This is the most recent log file
> B) logs folder -> This contains previous log files
6) Double click on the appropriate log file to open it
7) Copy the contents of it
8) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
9) Click the Code Tag button
10) Within the Code Tag, paste the log
11) Click the Submit button to post your post %

Method 3
1) Type %AppData%\FAHClient in Windows Explorer and hit Enter
2) A window will open which will contain F@H files and folders. Depending on your need, focus on:
> A) log file -> This is the most recent log file
> B) logs folder -> This contains previous log files
3) Double click on the appropriate log file to open it
4) Copy the contents of it
5) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
6) Click the Code Tag button
7) Within the Code Tag, paste the log
8) Click the Submit button to post your post %

A sample log file covering the important sections, System Info and Configuration along with normal folding process is shown below:

Code: Select all: *********************** Log Started 2014-03-07T23:27:10Z *********************** 23:27:10:************************* Folding@home Client ************************* 23:27:10: Website: http://folding.stanford.edu/ 23:27:10: Copyright: (c) 2009-2014 Stanford University 23:27:10: Author: Joseph Coffland <joseph@cauldrondevelopment.com> 23:27:10: Args: --open-web-control 23:27:10: Config: C:/Users/Anonymous/AppData/Roaming/FAHClient/config.xml 23:27:10:******************************** Build ******************************** 23:27:10: Version: 7.4.4 23:27:10: Date: Mar 4 2014 23:27:10: Time: 20:26:54 23:27:10: SVN Rev: 4130 23:27:10: Branch: fah/trunk/client 23:27:10: Compiler: Intel(R) C++ MSVC 1500 mode 1200 23:27:10: Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE 23:27:10: /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl 23:27:10: Platform: win32 XP 23:27:10: Bits: 32 23:27:10: Mode: Release 23:27:10:******************************* System ******************************** 23:27:10: CPU: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz 23:27:10: CPU ID: GenuineIntel Family 6 Model 30 Stepping 5 23:27:10: CPUs: 8 23:27:10: Memory: 4.00GiB 23:27:10: Free Memory: 2.84GiB 23:27:10: Threads: WINDOWS_THREADS 23:27:10: OS Version: 6.1 23:27:10: Has Battery: false 23:27:10: On Battery: false 23:27:10: UTC Offset: 4 23:27:10: PID: 980 23:27:10: CWD: C:/Users/Anonymous/AppData/Roaming/FAHClient 23:27:10: OS: Windows 7 Ultimate 23:27:10: OS Arch: AMD64 23:27:10: GPUs: 0 23:27:10: CUDA: Not detected 23:27:10:Win32 Service: false 23:27:10:*********************************************************************** 23:27:10:<config> 23:27:10:  23:27:10: <slot id='0' type='CPU'/> 23:27:10:</config> 23:27:10:Trying to access database... 23:27:10:Successfully acquired database lock 23:27:10:Enabled folding slot 00: READY cpu:7 23:27:10:WU00:FS00:Starting 23:27:10:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Anonymous/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 00 -suffix 01 -version 704 -lifeline 980 -checkpoint 15 -np 7 23:27:10:WU00:FS00:Started FahCore on PID 4032 23:27:10:WU00:FS00:Core PID:1000 23:27:10:WU00:FS00:FahCore 0xa4 started 23:27:11:WU00:FS00:0xa4: 23:27:11:WU00:FS00:0xa4:*------------------------------* 23:27:11:WU00:FS00:0xa4:Folding@Home Gromacs GB Core 23:27:11:WU00:FS00:0xa4:Version 2.27 (Dec. 15, 2010) 23:27:11:WU00:FS00:0xa4: 23:27:11:WU00:FS00:0xa4:Preparing to commence simulation 23:27:11:WU00:FS00:0xa4:- Looking at optimizations... 23:27:11:WU00:FS00:0xa4:- Files status OK 23:27:11:WU00:FS00:0xa4:- Expanded 546568 -> 843608 (decompressed 154.3 percent) 23:27:11:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=546568 data_size=843608, decompressed_data_size=843608 diff=0 23:27:11:WU00:FS00:0xa4:- Digital signature verified 23:27:11:WU00:FS00:0xa4: 23:27:11:WU00:FS00:0xa4:Project: 7646 (Run 6, Clone 3, Gen 134) 23:27:11:WU00:FS00:0xa4: 23:27:11:WU00:FS00:0xa4:Assembly optimizations on if available. 23:27:11:WU00:FS00:0xa4:Entering M.D. 23:27:14:12:127.0.0.1:New Web connection 23:27:16:WU00:FS00:0xa4:Mapping NT from 7 to 7 23:27:17:WU00:FS00:0xa4:Completed 0 out of 2500000 steps (0%) 23:47:12:WU00:FS00:0xa4:Completed 25000 out of 2500000 steps (1%)

Note: If you are using v6 F@H Client, please read this post for details on how to post the log file (Details)

% The forum has a limit to the amount of data that can be posted. If FAH has been running for a while, you may exceed that limit. If necessary, remove repetitive parts of your log and try again.

by **PantherX** » Wed Mar 19, 2014 9:45 pm

5 - How To Post A Log File (Windows 8-10)

If you are using the V7 F@H Software, there are a couple of methods that you can use to locate, copy and paste your log to this Forum.
* We don't need the progress messages between 2% and 99% and they can be removed but be sure to include the first couple of pages.
* Please note that the Forum has a limit of 60,000 characters so if you encounter this limit, you can remove repetitive messages. Also, you can split your log file across multiple posts.
* Please use the default setting of Verbosity Level 3 since any higher will print additional data that is unnecessary which makes it very difficult to troubleshoot in the majority of cases.

You can choose any of the following methods.

Method 1
1) Ensure that FAHClient is running by looking for the F@H icon in the notification area of the task bar
2) Right click the F@H icon
3) Select Advanced Control from the menu options
4) Once Advanced Control opens, select the Log tab
5) Untick Follow
6) Click the Refresh button
7) Click the Copy button
8) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
9) Click the Code Tag button
10) Within the Code Tag, paste the log
11) Click the Submit button to post your post %

Method 2
1) Click the Start Button or the lower left corner of the task bar
2) Right click on the Start Screen
3) Select All apps
4) Scroll until you see FAHClient
5) Click on Data Directory folder
6) A window will open which will contain F@H files and folders. Depending on your need, focus on:
> A) log file -> This is the most recent log file
> B) logs folder -> This contains previous log files
7) Double click on the appropriate log file to open it
8) Copy the contents of it
9) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
10) Click the Code Tag button
11) Within the Code Tag, paste the log
12) Click the Submit button to post your post %

Method 3
1) Type %AppData%\FAHClient in Windows Explorer and hit Enter
2) A window will open which will contain F@H files and folders. Depending on your need, focus on:
> A) log file -> This is the most recent log file
> B) logs folder -> This contains previous log files
3) Double click on the appropriate log file to open it
4) Copy the contents of it
5) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
6) Click the Code Tag button
7) Within the Code Tag, paste the log
8) Click the Submit button to post your post %

A sample log file covering the important sections, System Info and Configuration along with normal folding process is shown below:

Code: Select all: *********************** Log Started 2014-03-07T22:52:37Z *********************** 22:52:37:************************* Folding@home Client ************************* 22:52:37: Website: http://folding.stanford.edu/ 22:52:37: Copyright: (c) 2009-2014 Stanford University 22:52:37: Author: Joseph Coffland <joseph@cauldrondevelopment.com> 22:52:37: Args: --open-web-control 22:52:37: Config: C:/Users/Anonymous/AppData/Roaming/FAHClient/config.xml 22:52:37:******************************** Build ******************************** 22:52:37: Version: 7.4.4 22:52:37: Date: Mar 4 2014 22:52:37: Time: 20:26:54 22:52:37: SVN Rev: 4130 22:52:37: Branch: fah/trunk/client 22:52:37: Compiler: Intel(R) C++ MSVC 1500 mode 1200 22:52:37: Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE 22:52:37: /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT /Qmkl 22:52:37: Platform: win32 XP 22:52:37: Bits: 32 22:52:37: Mode: Release 22:52:37:******************************* System ******************************** 22:52:37: CPU: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz 22:52:37: CPU ID: GenuineIntel Family 6 Model 30 Stepping 5 22:52:37: CPUs: 8 22:52:37: Memory: 4.00GiB 22:52:37: Free Memory: 3.27GiB 22:52:37: Threads: WINDOWS_THREADS 22:52:37: OS Version: 6.2 22:52:37: Has Battery: false 22:52:37: On Battery: false 22:52:37: UTC Offset: 4 22:52:37: PID: 3148 22:52:37: CWD: C:/Users/Anonymous/AppData/Roaming/FAHClient 22:52:37: OS: Windows 8 Pro 22:52:37: OS Arch: AMD64 22:52:37: GPUs: 0 22:52:37: CUDA: Not detected 22:52:37:Win32 Service: false 22:52:37:*********************************************************************** 22:52:37:<config> 22:52:37:  22:52:37: <slot id='0' type='CPU'/> 22:52:37:</config> 22:52:37:Trying to access database... 22:52:37:Successfully acquired database lock 22:52:37:Enabled folding slot 00: READY cpu:7 22:52:37:WU00:FS00:Starting 22:52:37:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Anonymous/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a3.fah/FahCore_a3.exe -dir 00 -suffix 01 -version 704 -lifeline 3148 -checkpoint 15 -np 7 22:52:37:WU00:FS00:Started FahCore on PID 3436 22:52:37:WU00:FS00:Core PID:4000 22:52:37:WU00:FS00:FahCore 0xa3 started 22:52:38:WU00:FS00:0xa3: 22:52:38:WU00:FS00:0xa3:*------------------------------* 22:52:38:WU00:FS00:0xa3:Folding@Home Gromacs SMP Core 22:52:38:WU00:FS00:0xa3:Version 2.27 (Dec. 15, 2010) 22:52:38:WU00:FS00:0xa3: 22:52:38:WU00:FS00:0xa3:Preparing to commence simulation 22:52:38:WU00:FS00:0xa3:- Looking at optimizations... 22:52:38:WU00:FS00:0xa3:- Files status OK 22:52:38:WU00:FS00:0xa3:- Expanded 3850137 -> 4392432 (decompressed 114.0 percent) 22:52:38:WU00:FS00:0xa3:Called DecompressByteArray: compressed_data_size=3850137 data_size=4392432, decompressed_data_size=4392432 diff=0 22:52:38:WU00:FS00:0xa3:- Digital signature verified 22:52:38:WU00:FS00:0xa3: 22:52:38:WU00:FS00:0xa3:Project: 8581 (Run 0, Clone 5, Gen 444) 22:52:38:WU00:FS00:0xa3: 22:52:38:WU00:FS00:0xa3:Assembly optimizations on if available. 22:52:38:WU00:FS00:0xa3:Entering M.D. 22:52:40:11:127.0.0.1:New Web connection 22:52:44:WU00:FS00:0xa3:Mapping NT from 7 to 7 22:52:44:WU00:FS00:0xa3:Completed 0 out of 500000 steps (0%) 23:05:48:WU00:FS00:0xa3:Completed 5000 out of 500000 steps (1%) 23:17:47:WU00:FS00:0xa3:Completed 10000 out of 500000 steps (2%)

Note: If you are using v6 F@H Client, please read this post for details on how to post the log file (Details)

% The forum has a limit to the amount of data that can be posted. If FAH has been running for a while, you may exceed that limit. If necessary, remove repetitive parts of your log and try again.

by **PantherX** » Wed Mar 19, 2014 9:45 pm

6 - How To Post A Log File (Linux)

If you are using the V7 F@H Software, there are a couple of methods that you can use to locate, copy and paste your log to this Forum.
* We don't need the progress messages between 2% and 99% and they can be removed but be sure to include the first couple of pages.
* Please note that the Forum has a limit of 60,000 characters so if you encounter this limit, you can remove repetitive messages. Also, you can split your log file across multiple posts.
* Please use the default setting of Verbosity Level 3 since any higher will print additional data that is unnecessary which makes it very difficult to troubleshoot in the majority of cases.

You can choose any of the following methods.

Method 1
1) Open up up FAHControl
2) Select the Log tab
3) Untick Follow
4) Click the Refresh button
5) Click the Copy button
6) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
7) Click the Code Tag button
8) Within the Code Tag, paste the log
9) Click the Submit button to post your post %

Method 2
1) Navigate to /var/lib/fahclient
2) You will see F@H files and folders. Depending on your need, focus on:
> A) log file -> This is the most recent log file
> B) logs folder -> This contains previous log files
3) Double click on the appropriate log file to open it
4) Copy the contents of it
5) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
6) Click the Code Tag button
7) Within the Code Tag, paste the log
8) Click the Submit button to post your post %

A sample log file covering the important sections, System Info and Configuration along with normal folding process is shown below:

Code: Select all: *********************** Log Started 2014-03-08T00:14:54Z *********************** 00:14:54:************************* Folding@home Client ************************* 00:14:54: Website: http://folding.stanford.edu/ 00:14:54: Copyright: (c) 2009-2014 Stanford University 00:14:54: Author: Joseph Coffland <joseph@cauldrondevelopment.com> 00:14:54: Args: --child --lifeline 1698 /etc/fahclient/config.xml --run-as 00:14:54: fahclient --pid-file=/var/run/fahclient.pid --daemon 00:14:54: Config: /etc/fahclient/config.xml 00:14:54:******************************** Build ******************************** 00:14:54: Version: 7.4.4 00:14:54: Date: Mar 4 2014 00:14:54: Time: 12:02:38 00:14:54: SVN Rev: 4130 00:14:54: Branch: fah/trunk/client 00:14:54: Compiler: GNU 4.4.7 00:14:54: Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math 00:14:54: -fno-unsafe-math-optimizations -msse2 00:14:54: Platform: linux2 3.2.0-1-amd64 00:14:54: Bits: 64 00:14:54: Mode: Release 00:14:54:******************************* System ******************************** 00:14:54: CPU: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz 00:14:54: CPU ID: GenuineIntel Family 6 Model 30 Stepping 5 00:14:54: CPUs: 8 00:14:54: Memory: 3.85GiB 00:14:54:Free Memory: 3.44GiB 00:14:54: Threads: POSIX_THREADS 00:14:54: OS Version: 3.8 00:14:54:Has Battery: false 00:14:54: On Battery: false 00:14:54: UTC Offset: 0 00:14:54: PID: 1700 00:14:54: CWD: /var/lib/fahclient 00:14:54: OS: Linux 3.8.0-36-generic x86_64 00:14:54: OS Arch: AMD64 00:14:54: GPUs: 0 00:14:54: CUDA: Not detected 00:14:54:*********************************************************************** 00:14:54:<config> 00:14:54:  00:14:54: <fold-anon v='true'/> 00:14:54: 00:14:54:  00:14:54: <gpu v='false'/> 00:14:54: 00:14:54:  00:14:54: <slot id='0' type='CPU'/> 00:14:54:</config> 00:14:54:Switching to user fahclient 00:14:54:Trying to access database... 00:14:55:Successfully acquired database lock 00:14:55:Enabled folding slot 00: READY cpu:7 00:14:55:WU00:FS00:Starting 00:14:55:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper /var/lib/fahclient/cores/www.stanford.edu/~pande/Linux/AMD64/Core_a3.fah/FahCore_a3 -dir 00 -suffix 01 -version 704 -lifeline 1700 -checkpoint 15 -np 7 00:14:55:WU00:FS00:Started FahCore on PID 1923 00:14:55:WU00:FS00:Core PID:2016 00:14:55:WU00:FS00:FahCore 0xa3 started 00:14:56:WU00:FS00:0xa3: 00:14:56:WU00:FS00:0xa3:*------------------------------* 00:14:56:WU00:FS00:0xa3:Folding@Home Gromacs SMP Core 00:14:56:WU00:FS00:0xa3:Version 2.27 (Dec. 15, 2010) 00:14:56:WU00:FS00:0xa3: 00:14:56:WU00:FS00:0xa3:Preparing to commence simulation 00:14:56:WU00:FS00:0xa3:- Looking at optimizations... 00:14:56:WU00:FS00:0xa3:- Files status OK 00:14:56:WU00:FS00:0xa3:- Expanded 3845612 -> 4375408 (decompressed 113.7 percent) 00:14:56:WU00:FS00:0xa3:Called DecompressByteArray: compressed_data_size=3845612 data_size=4375408, decompressed_data_size=4375408 diff=0 00:14:56:WU00:FS00:0xa3:- Digital signature verified 00:14:56:WU00:FS00:0xa3: 00:14:56:WU00:FS00:0xa3:Project: 8579 (Run 0, Clone 0, Gen 495) 00:14:56:WU00:FS00:0xa3: 00:14:56:WU00:FS00:0xa3:Assembly optimizations on if available. 00:14:56:WU00:FS00:0xa3:Entering M.D. 00:15:02:WU00:FS00:0xa3:Mapping NT from 7 to 7 00:15:06:WU00:FS00:0xa3:Completed 0 out of 500000 steps (0%) 00:26:18:WU00:FS00:0xa3:Completed 5000 out of 500000 steps (1%) 00:37:06:WU00:FS00:0xa3:Completed 10000 out of 500000 steps (2%) 00:47:53:WU00:FS00:0xa3:Completed 15000 out of 500000 steps (3%) 00:58:39:WU00:FS00:0xa3:Completed 20000 out of 500000 steps (4%) 01:09:28:WU00:FS00:0xa3:Completed 25000 out of 500000 steps (5%)

% The forum has a limit to the amount of data that can be posted. If FAH has been running for a while, you may exceed that limit. If necessary, remove repetitive parts of your log and try again.

by **PantherX** » Wed Mar 19, 2014 9:46 pm

7 - How To Post A Log File (OSX)

If you are using the V7 F@H Software, there are a couple of methods that you can use to locate, copy and paste your log to this Forum.
* We don't need the progress messages between 2% and 99% and they can be removed but be sure to include the first couple of pages.
* Please note that the Forum has a limit of 60,000 characters so if you encounter this limit, you can remove repetitive messages. Also, you can split your log file across multiple posts.
* Please use the default setting of Verbosity Level 3 since any higher will print additional data that is unnecessary which makes it very difficult to troubleshoot in the majority of cases.

You can choose any of the following methods.

Method 1
1) Open up up FAHControl
2) Select the Log tab
3) Untick Follow
4) Click the Refresh button
5) Click the Copy button
6) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
7) Click the Code Tag button
8) Within the Code Tag, paste the log
9) Click the Submit button to post your post

Method 2
1) Navigate to /Library/Application Support/FAHClient
2) You will see F@H files and folders. Depending on your need, focus on:
> A) log file -> This is the most recent log file
> B) logs folder -> This contains previous log files
3) Double click on the appropriate log file to open it
4) Copy the contents of it
5) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
6) Click the Code Tag button
7) Within the Code Tag, paste the log
8) Click the Submit button to post your post

A sample log file covering the important sections, System Info and Configuration along with normal folding process is shown below:

Code: Select all: *********************** Log Started 2014-03-08T01:42:21Z *********************** 01:42:21:************************* Folding@home Client ************************* 01:42:21: Website: http://folding.stanford.edu/ 01:42:21: Copyright: (c) 2009-2014 Stanford University 01:42:21: Author: Joseph Coffland <joseph@cauldrondevelopment.com> 01:42:21: Args: --child --lifeline 65 --respawn 01:42:21: Config: /Library/Application Support/FAHClient/config.xml 01:42:21:******************************** Build ******************************** 01:42:21: Version: 7.4.4 01:42:21: Date: Mar 4 2014 01:42:21: Time: 20:27:54 01:42:21: SVN Rev: 4130 01:42:21: Branch: fah/trunk/client 01:42:21: Compiler: GNU 4.2.1 (Apple Inc. build 5666) (dot 3) 01:42:21: Options: -std=gnu++98 -O3 -funroll-loops -mfpmath=sse -ffast-math 01:42:21: -fno-unsafe-math-optimizations -msse3 -arch x86_64 01:42:21: -mmacosx-version-min=10.6 01:42:21: Platform: darwin 10.8.0 01:42:21: Bits: 64 01:42:21: Mode: Release 01:42:21:******************************* System ******************************** 01:42:21: CPU: Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz 01:42:21: CPU ID: GenuineIntel Family 6 Model 30 Stepping 5 01:42:21: CPUs: 8 01:42:21: Memory: 4.00GiB 01:42:21:Free Memory: 3.39GiB 01:42:21: Threads: POSIX_THREADS 01:42:21: OS Version: 10.9 01:42:21:Has Battery: false 01:42:21: On Battery: false 01:42:21: UTC Offset: 0 01:42:21: PID: 173 01:42:21: CWD: /Library/Application Support/FAHClient 01:42:21: OS: Darwin 13.1.0 x86_64 01:42:21: OS Arch: AMD64 01:42:21: GPUs: 0 01:42:21: CUDA: Not detected 01:42:21:*********************************************************************** 01:42:21:<config> 01:42:21:  01:42:21: <slot id='0' type='CPU'/> 01:42:21:</config> 01:42:21:Trying to access database... 01:42:29:Successfully acquired database lock 01:42:29:Enabled folding slot 00: READY cpu:7 01:42:29:WU00:FS00:Starting 01:42:29:WU00:FS00:Running FahCore: /usr/bin/FAHCoreWrapper "/Library/Application Support/FAHClient/cores/www.stanford.edu/~pande/OSX/AMD64/Core_a4.fah/FahCore_a4" -dir 00 -suffix 01 -version 704 -lifeline 173 -checkpoint 15 -np 7 01:42:29:WU00:FS00:Started FahCore on PID 224 01:42:32:WU00:FS00:Core PID:228 01:42:32:WU00:FS00:FahCore 0xa4 started 01:42:34:WU00:FS00:0xa4: 01:42:34:WU00:FS00:0xa4:*------------------------------* 01:42:34:WU00:FS00:0xa4:Folding@Home Gromacs Core 01:42:34:WU00:FS00:0xa4:Version 2.27 (Thu Feb 10 09:46:40 PST 2011) 01:42:34:WU00:FS00:0xa4: 01:42:34:WU00:FS00:0xa4:Preparing to commence simulation 01:42:34:WU00:FS00:0xa4:- Looking at optimizations... 01:42:34:WU00:FS00:0xa4:- Files status OK 01:42:34:WU00:FS00:0xa4:- Expanded 882159 -> 1469104 (decompressed 166.5 percent) 01:42:34:WU00:FS00:0xa4:Called DecompressByteArray: compressed_data_size=882159 data_size=1469104, decompressed_data_size=1469104 diff=0 01:42:34:WU00:FS00:0xa4:- Digital signature verified 01:42:34:WU00:FS00:0xa4: 01:42:34:WU00:FS00:0xa4:Project: 9005 (Run 139, Clone 3, Gen 37) 01:42:34:WU00:FS00:0xa4: 01:42:34:WU00:FS00:0xa4:Assembly optimizations on if available. 01:42:34:WU00:FS00:0xa4:Entering M.D. 01:42:40:WU00:FS00:0xa4:Mapping NT from 7 to 7 01:42:43:WU00:FS00:0xa4:Completed 0 out of 250000 steps (0%) 01:44:34:WU00:FS00:0xa4:Completed 2500 out of 250000 steps (1%) 01:46:18:WU00:FS00:0xa4:Completed 5000 out of 250000 steps (2%) 01:48:02:WU00:FS00:0xa4:Completed 7500 out of 250000 steps (3%) 01:49:47:WU00:FS00:0xa4:Completed 10000 out of 250000 steps (4%) 01:51:31:WU00:FS00:0xa4:Completed 12500 out of 250000 steps (5%) 01:53:17:WU00:FS00:0xa4:Completed 15000 out of 250000 steps (6%)

by **PantherX** » Wed Mar 19, 2014 9:47 pm

8 - How To Post A Log Snippet (Chrome Folding App)

Unlike other F@H Clients, the Folding App isn't a traditional desktop application. Instead, it is an App that runs entirely within the Chrome browser. Thus, you will not find a log file which is present in other F@H Clients. Instead, you will have to use the Chrome's developer's tool to gain access to on-screen messages that the Folding App generates. For most users, there shouldn't be any need to access these messages. However, in the rare case that additional information is needed, below are the methods that you can use to gain access to these on-screen messages.

Method 1
1) Start Chrome Folding App
2) Click on Chrome menu which is present on the top right side
3) From the menu, select Tools
4) From the fly-out menu, select Developer tools
5) The DevTools window opens
6) Click on Console
7) Highlight the appropriate messages by using the cursor
8) Copy it by using the shortcut keys
9) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
10) Click the Code Tag button
11) Within the Code Tag, paste the log
12) Click the Submit button to post your post

Method 2
1) Start Chrome with the command --enable-logging --v=1
2) Run the Folding App until you log the required messages
3) Exit Chrome
4) Navigate to the User Data Directory
5) Open chrome_debug.log file
6) Copy the appropriate messages
7) Go to the Full Editor in this Forum by clicking on; New Topic or Post Reply or Full Editor
8) Click the Code Tag button
9) Within the Code Tag, paste the log
10) Click the Submit button to post your post

A sample log snippet showing some Folding App related information is shown below:

Code: Select all: DEBUG: Config: power = medium main.js:73 DEBUG: NaCl module loading main.js:73 DEBUG: Status: downloading: Downloading the Folding@home software in your Web browser. On your first visit this can take awhile. main.js:73 DEBUG: load progress: 0.0% (0 of 18000000 bytes) main.js:73 DEBUG: load progress: 0.0% (0 of 18446744073709552000 bytes) main.js:73 SNIP DEBUG: load progress: 0.0% (17086055 of 18446744073709552000 bytes) main.js:73 DEBUG: load progress: 0.0% (17106340 of 18446744073709552000 bytes) main.js:73 DEBUG: load progress: 0.0% (17125192 of 18446744073709552000 bytes) main.js:73 DEBUG: load progress: 100.0% (17125192 of 17125192 bytes) main.js:73 DEBUG: NaCl module loaded main.js:73 DEBUG: NaCl module responded main.js:73 DEBUG: Status: downloading: Requesting ID. main.js:73 DEBUG: Status: downloading: Requesting ID. main.js:73 DEBUG: Config: id = 0x1ec53118530cef60 main.js:73 DEBUG: Status: downloading: Requesting a work server assignment. main.js:73 DEBUG: Status: downloading: Requesting a work server assignment. main.js:73 DEBUG: WS: {"client_id":"0x1ec53118530cef60","threads":8,"version":"8.0.0","type":"NACL","os":"NACL","user":"Anonymous","team":0,"ts":"2014-02-25T19:30:41Z","ws":"143.89.28.86","project":2981} main.js:73 DEBUG: Status: downloading: Downloading a work unit. main.js:73 DEBUG: Status: downloading: Downloading a work unit. main.js:73 Resource interpreted as Image but transferred with MIME type text/plain: "data:;base64, SNIP DEBUG: WU: {"client_id":"0x1ec53118530cef60","threads":8,"version":"8.0.0","type":"NACL","os":"NACL","user":"Anonymous","team":0,"ts":"2014-02-25T19:30:41Z","ws":"143.89.28.86","project":2981,"server_version":703,"core":176,"core_version":227,"unit_id":"0x000000770893a18a52e6da85807cea17","run":0,"clone":28,"gen":86,"wu_ts":"2014-02-25T19:30:43Z","deadline":"2014-02-26T19:30:43Z","timeout":"2014-02-25T21:54:43Z","credit":10,"compression":"bzip2","checksum":"mwkD5fo9cjLAQsOKM9ip8EGg7mlAmsv5taCtcR9qMQI="} main.js:73 DEBUG: Status: running: Starting work unit. main.js:73 DEBUG: core: checksum verified main.js:73 DEBUG: core: unpacking: frame86.tpr main.js:73 DEBUG: :-) G R O M A C S (-: main.js:73 DEBUG: Groningen Machine for Chemical Simulation main.js:73 DEBUG: :-) VERSION 4.6.5 (-: main.js:73 DEBUG: Contributions from Mark Abraham, Emile Apol, Rossen Apostolov, Herman J.C. Berendsen, Aldert van Buuren, Pär Bjelkmar, Rudi van Drunen, Anton Feenstra, Gerrit Groenhof, Christoph Junghans, Peter Kasson, Carsten Kutzner, Per Larsson, Pieter Meulenhoff, Teemu Murtola, Szilard Pall, Sander Pronk, Roland Schulz, Michael Shirts, Alfons Sijbers, Peter Tieleman, main.js:73 DEBUG: Berk Hess, David van der Spoel, and Erik Lindahl. main.js:73 DEBUG: Copyright (c) 1991-2000, University of Groningen, The Netherlands. Copyright (c) 2001-2012,2013, The GROMACS development team at Uppsala University & The Royal Institute of Technology, Sweden. check out http://www.gromacs.org for more information. main.js:73 DEBUG: main.js:73 DEBUG: :-) Gromacs (-: main.js:73 DEBUG: Option------------------------------------------------------------ main.js:73 DEBUG: -s frame86.tpr Input Run input file: tpr tpb tpa -o traj.trr Output Full precision trajectory: trr trj cpt -x traj.xtc Output, Opt. Compressed trajectory (portable xdr format)-cpi state.cpt Input, Opt. Checkpoint file-cpo state.cpt Output, Opt. Checkpoint file -c confout.gro Output Structure file: gro g96 pdb etc. -e ener.edr Output Energy file -g md.log Output Log file-dhdl dhdl.xvg Output, Opt. xvgr/xmgr file-field field.xvg Output, Opt. xvgr/xmgr file-table table.xvg Input, Opt. xvgr/xmgr file-tabletf tabletf.xvg Input, Opt. xvgr/xmgr file-tablep tablep.xvg Input, Opt. xvgr/xmgr file-tableb table.xvg Input, Opt. xvgr/xmgr file-rerun rerun.xtc Input, Opt. Trajectory: xtc trr trj gro g96 pdb cpt-tpi tpi.xvg Output, Opt. xvgr/xmgr file-tpid tpidist.xvg Output, Opt. xvgr/xmgr file -ei sam.edi Input, Opt. ED sampling input -eo edsam.xvg Output, Opt. xvgr/xmgr file -j wham.gct Input, Opt. General coupling stuff -jo bam.gct Output, Opt. General coupling stuff-ffout gct.xvg Output, Opt. xvgr/xmgr file-devout deviatie.xvg Output, Opt. xvgr/xmgr file-runav runaver.xvg Output, Opt. xvgr/xmgr file -px pullx.xvg Output, Opt. xvgr/xmgr file -pf pullf.xvg Output, Opt. xvgr/xmgr file -ro rotation.xvg Output, Opt. xvgr/xmgr file -ra rotangles.log Output, Opt. Log file -rs rotslabs.log Output, Opt. Log file -rt rottorque.log Output, Opt. Log file-mtx nm.mtx Output, Opt. Hessian matrix -dn dipole.ndx Output, Opt. Index file-multidir rundir Input, Opt., Mult. Run directory-membed membed.dat Input, Opt. Generic data file -mp membed.top Input, Opt. Topology file -mn membed.ndx Input, Opt. Index file main.js:73 DEBUG: Option------------------------------------------------------ main.js:73 SNIP

by **PantherX** » Wed Mar 19, 2014 9:48 pm

9 - Importance Of Deadlines

Each F@H Client will download a WU which has a Preferred Deadline and a Final Deadline. You can run any supported F@H Client(s) as long as you can return the WU before the Preferred Deadline. Credit is granted for completed WUs and rarely for WUs which cannot be completed because of an error. In all cases, they will not appear in the official stats pages until at least an hour or more after the results are uploaded. Some WUs use the Quick Return Bonus (QRB) scheme to get more points the faster it is folded while other don't. Below is the relationship between the WU assigned to you and its deadlines:

Non-Bonus WUs:
Before Preferred Deadline - You will get assigned credit once you have folded the WU.
Exceed Preferred Deadline - WU will be reissued to another system while yours is currently folding it. You will get assigned credit once you have folded the WU.
Exceed Final Deadline - WU is deleted from your system. You won't get any credit
Note: WUs using FahCore_11, FahCore_15, FahCore_16 are not QRB designated WUs.

Bonus (QRB) WUs:
Before Preferred Deadline - You will get bonus credit once you have folded the WU (bonus varies from system to system and increases for faster completion).
Exceed Preferred Deadline - WU will be reissued to another system while yours is currently folding it. You will get base credit once you have folded the WU (it is significantly less when compared to bonus credits).
Exceed Final Deadline - WU is deleted from your system. You won't get any credit
Note: WUs using FahCore_a3, FahCore_a4, FahCore_a5, FahCore_17, FahCore_ 176 are all QRB designated WUs.

Please note that if you constantly fail to finish the assigned WUs, you may want to uninstall V7 and use the Folding App which is meant for casual Donors (Details).

In order for Donors to take advantage of Bonus Points (QRB), there are some basic requirements which they must meet:
1) Use SMP2 Beta Client v6.3X or higher
2) Configure the Client with a Passkey (Details).
3) Successfully fold 10 QRB designated WUs before their preferred deadline by using the same combination of Username and Passkey.
4) Maintain a successful return rate of >= 80% for QRB WUs, i.e. out of every 10 QRB WUs assigned, you must return at least 8 of them.

by **PantherX** » Wed Mar 19, 2014 9:48 pm

10 - V7 Interface

Below are some tips and information regarding the interface of V7:

1) A Donor can use either interface to access their F@H Client:
> A) WebControl -> For Donors who want a simple-to-understand-and-operate interface
> B) Advanced Control (AKA FAHControl) -> For Donors who want to get more information and more precise control over their contribution

2) The following message means that your F@H Slot is properly configured but is not currently folding since the system is not idle. It is configured so that it only folds when the system is idle (this is the default setting for a GPU Slot):
paused: waiting for idle
Note: There are different methods used to identify the idle state of the system. You can read about it here.

3) If a value "Unknown" appears, it just means that not enough information is available to the client to display meaningful information. However, it means that the client is working properly.

by **PantherX** » Wed Mar 19, 2014 9:50 pm

11 - Adding Slot Options In V7

Generally, the default settings ought to be fine for most Donors. However, if you would like to tweak some settings specific to the Slot, you can still do so. Below is the procedure to change the slot settings.

1) Open up Advanced Control (AKA FAHControl)
2) Click on Configure
3) Select the Slots Tab
4) Select the slot you would like to configure with a single click
5) Click the Edit button
6) Scroll down the Folding Slot window to the Extra slot options (expert only) section
7) Click on the Add button
8) A Edit Options box will appear where you have to enter the correct values for Name and Value (details are mentioned below).
9) Click OK button to close the Edit Options box
10) Click OK button to close the Folding Slot window
11) Click on the Save button to save the changes made to the slot

A list of Basic options are:

Code: Select all: Name Value Description client-type advanced Assigns WUs in late-stage beta if available client-type bigadv Assigns bigadv WUs on capable systems if available (CPU slot only) next-unit-percentage X X should be between 90 and 100. It tells when the next WU should be downloaded after the current WU reaches X percentage

A list of Advanced options are:

Code: Select all: Name Value Description max-units X X can be any number; 0 is indefinite. It tells when to pause the slot after X WUs are completed checkpoint X X is a value between 3 and 30. It will create a checkpoint after X minutes pause-on-start true FAHClient starts the slot in the pause state pause-on-start false FAHClient will start the slot normally max-packet-size small Configures the slot to get small WUs (~5MB) max-packet-size normal Configures the slot to get normal WUs (~10MB) max-packet-size big Configures the slot to get big WUs (~500MB)

Below is a list of all available options and their default settings (some settings may vary depending on the OS):

Code: Select all: Usage: FAHClient.exe [[--config] <filename>] [OPTIONS]... Command line options: --chdir <string> Change directory before starting server. All files opened after this point, such as the configuration file, must have paths relative to the new directory. --config <string=config.xml> Set configuration file. --configure Create a basic configuration file, then exit. --dump <string> Dump either 'all' or a specific work unit, identified by its queue ID, then exit. --finish Finish all current work units, send the results, then exit. --help [string] Print help screen or help on a particular option and exit. --info Print application and system information and exit. --install-service Install the application as a Win32 service then exit. --license License information and exit. --lifeline <integer> The application will watch for this process ID and exit if it goes away. Usually the calling process' PID. --lspci List the PCI bus devices, which can be helpful for finding GPU vendor and device IDs. --print Print configuration and exit. --queue-info Print work unit queue then exit. --send Send all finished work units, then exit. --send-command <string> Send a command to an already running client. --send-finish [string] Finish a slot or all slots on an already running client. --send-pause [string] Pause a slot or all slots on an already running client. --send-unpause [string] Unpause a slot or all slots on an already running client. --start-service Start Win32 service then exit. --stop-service Stop Win32 service then exit. --uninstall-service Uninstall the application as a Win32 service then exit. -v Increase verbosity level. --version Print application version and exit. -v Increase verbosity level. Configuration options: The following options can be specified in a configuration file or on the command line using the following syntax: --<option> <value> or: --<option>=<value> or when marking boolean values true: --<option> service-description <string=Folding@home Client> The description for the Windows service control manager. service-restart <boolean=true> Configure Windows service to automatically restart on failure. service-restart-delay <integer=5000> The amount of time in milliseconds to delay between restarts of the Windows service. Client Control: client-threads <integer=6> The number of client processing threads. cycle-rate <double=4> The maximum cycle frequency in Hz of client threads. cycles <integer=-1> Run at most this many cycles. A value less than zero means run indefinitely. data-directory <string=.> The directory, relative to the current directory, where WU data and cores are stored. disable-sleep-when-active <boolean=true> Attempt to keep the system from sleeping when folding, unless on battery. exec-directory <string=C:\Program Files (x86)\FAHClient> The directory, relative to the current executable, where executables and dynamic libraries are located. exit-when-done <boolean=false> Exit when all slots are paused. fold-anon <boolean=false> Start folding even if not configured. open-web-control <boolean=false> Make an operating system specific call to open the Web Control in a browser once client is fully loaded Configuration: config-rotate <boolean=true> Rotate the configuration file to a backup when saving would overwrite the previous configuration. config-rotate-dir <string=configs> Put rotated configs in this directory. config-rotate-max <integer=16> The maximum number of rotated configuration files to keep. A value of zero will keep all configuration file backups. Error Handling: max-slot-errors <integer=10> The maximum number of errors before a slot is paused. max-unit-errors <integer=5> The maximum number of errors before a work unit is dumped. Folding Core: checkpoint <integer=15> Tell cores to checkpoint at least every # minutes. core-dir <string=cores> The directory to store core files in. core-prep <string> Run this command on cores after they are downloaded. This option is useful for running Linux cores on BSD machines. core-priority <string=idle> Set the core priority. Valid values are: idle or low cpu-affinity <boolean=false> If true, try to lock core processes to a fixed CPU cpu-usage <integer=100> The maximum percentage of the CPU a core should use. Not implemented by all cores. gpu-usage <integer=100> GPU usage as a percent from 10-100 no-assembly <boolean=false> Tell cores to disable optimized assembly code. Folding Slot Configuration: cause <string=ANY> The cause you prefer to support. client-subtype <string=STDCLI> The client subtype client-type <string=normal> The client type. Can be 'normal', 'advanced' or 'beta'. cpu-species <string=X86_PENTIUM_II> CPU species. cpu-type <string=AMD64> CPU type. cpus <integer=-1> How many CPUs a slot should use. <= 0 will use all the CPUs detected in the system. cuda-index <string> The CUDA device index of the GPU, counting starts from 0. extra-core-args <string> Pass extra arguments to the core. gpu <boolean=true> Enable or disable auto-confiugration of GPU slots, requires appropriate hardware. gpu-index <string> The index of the GPU as detected by the client. This index corresponds directly to the GPUs listed in the client's '--info' output. max-packet-size <string=normal> Max size in bytes of a work unit packet. Can be small=5MB, normal=10MB, big=500MB or a number. memory <string> Override memory, in bytes, reported to Folding@home. opencl-index <string> The OpenCL device index of the GPU, counting starts from 0. os-species <string=UNKNOWN> Operating system species. os-type <string=WIN32> Operating system type. project-key <integer=0> Key for access to restricted testing projects. smp <boolean=true> Enable or disable auto-configuration of SMP slots, requires appropriate hardware. GUI: gui-enabled <boolean=true> Set to false to disable the GUI. A GUI is not currently supported on all operating systems. HTTP Server: allow <string=127.0.0.1> Client addresses which are allowed to connect to this server. This option overrides IPs which are denied in the deny option. The pattern 0/0 matches all addresses. connection-timeout <integer=60> The maximum amount of time, in seconds, a connection can be idle before being dropped. deny <string=0/0> Client address which are not allowed to connect to this server. http-addresses <string=0:7396> A space separated list of server address and port pairs to listen on in the form <ip | hostname>[:<port>] https-addresses <string=> A space separated list of secure server address and port pairs to listen on in the form <ip | hostname>[:<port>] max-connect-time <integer=900> The maximum amount of time, in seconds, a client can be connected to the server. max-connections <integer=800> Sets the maximum number of simultaneous connections. max-request-length <integer=52428800> Sets the maximum length of a client request packet. min-connect-time <integer=300> The minimum amount of time, in seconds, a client must be connected to the server before it can be dropped in favor or a new connection. threads <integer=8> Sets the number of server threads. HTTP Server SSL: certificate-file <string> The servers certificate file in PEM format. crl-file <string> Supply a Certificate Revocation List. Overrides any internal CRL private-key-file <string> The servers private key file in PEM format. Logging: log <string=log.txt> Set log file. log-color <boolean=false> Print log messages with ANSI color coding. log-crlf <boolean=true> Print carriage return and line feed at end of log lines. log-date <boolean=false> Print date information with log entries. log-date-periodically <integer=21600> Print date to log before new log entries if so many seconds have passed since the last date was printed. log-debug <boolean=true> Disable or enable debugging info. log-domain <boolean=false> Print domain information with log entries. log-domain-levels <string ...> Set log levels by domain. Format is: <domain>[:i|d|t]:<level> ... Entries are separated by white-space and or commas. i - info d - debug For example: server:i:3 module:6 Set 'server' domain info messages to level 3 and 'module' info and debug messages to level 6. All other domains will follow the system wide log verbosity level. If <level> is negative it is relative to the system wide verbosity. log-header <boolean=true> Enable log message headers. log-level <boolean=true> Print level information with log entries. log-no-info-header <boolean=true> Don't print 'INFO(#):' in header. log-redirect <boolean=false> Redirect all output to log file. Implies !log-to-screen. log-rotate <boolean=true> Rotate log files on each run. log-rotate-dir <string=logs> Put rotated logs in this directory. log-rotate-max <integer=16> Maximum number of rotated logs to keep. log-short-level <boolean=false> Print shortened level information with log entries. log-simple-domains <boolean=true> Remove any leading directories and trailing file extensions from domains so that source code file names can be easily used as log domains. log-thread-id <boolean=false> Print id with log entries. log-thread-prefix <boolean=true> Print thread prefixes, if set, with log entries. log-time <boolean=true> Print time information with log entries. log-to-screen <boolean=true> Log to screen. log-truncate <boolean=false> Truncate log file. verbosity <integer=3> Set logging level for INFO and DEBUG messages. Network: proxy <string=> Set proxy for outgoing HTTP connections proxy-enable <boolean=false> Enable proxy configuration proxy-pass <string=> Set password for proxy connections proxy-user <string=> Set user name for proxy connections Process Control: child <boolean=false> Disable 'daemon', 'fork', 'pid' and 'respawn' options. Also defaults 'log-to-screen' to false. Used internally. daemon <boolean=false> Short for --pid --service --respawn --log='' pid <boolean=false> Create PID file. pid-file <string=Folding@home Client.pid> Name of PID file. priority <string> Set the process priority. Valid values are: idle, low, normal, high or realtime. respawn <boolean=false> Run the application as a child process and respawn if it is killed or exits. service <boolean=false> Ignore user logout or hangup and interrupt signals Remote Command Server: command-address <string=0.0.0.0> The address to which the command server should be bound. command-allow-no-pass <string=127.0.0.1> IP address ranges that are allowed access to the command server with out a password if the 'password' option is set. These addresses will also have to be allowed IP based access. command-deny-no-pass <string=0/0> IP address ranges that are not allowed access to the command server with out a password if the 'password' option is set. Overriden by command-allow-no-pass command-enable <boolean=true> Set to false to disable the command server. command-port <integer=36330> The port to which the command server should be bound. eval <string> Evaluate the argument as a script. password <string> Set a command server password. Warning, setting a password disables the default IP address blocking. script <string> Run commands from a script file. Slot Control: idle <boolean=false> Only run slot when idle. max-shutdown-wait <integer=60> The maxumum amount of time to wait in seconds for a unit to exit on shutdown. pause-on-battery <boolean=true> Pause the client or slot when the OS indicates the machine is running on battery power. pause-on-start <boolean=false> If true the slot will be started in a paused state. paused <boolean=false> True of client is paused. power <string=medium> Set the client's power level. Valid values are 'light', 'medium' or 'full'. This setting affects the defaults of several other options such as 'cpus', 'pause-on-battery', etc. User Information: machine-id <integer=0> The machine ID. passkey <string=> Your passkey. team <integer=0> Your team number. user <string=Anonymous> Your user name. Web Server: web-allow <string=127.0.0.1> Client addresses which are allowed to connect to this Web server. This option overrides IPs which are denied in the web-deny option. This option differs from the 'allow'/'deny' options in that clients that are not allowed are served an access denied page rather than simply dropping the connection. The value '0/0' matches all IPs. web-deny <string=0/0> Client address which are not allowed to connect to this Web server. web-enable <boolean=true> Set to false to disable the web server. Web Server Sessions: session-cookie <string=sid> The name of the session cookie. session-lifetime <integer=86400> The maximum session lifetime in seconds. Zero for unlimited session lifetime. session-timeout <integer=3600> The max maximum amount of time in seconds since the last time a session was used before it timesout. Zero for no session timeout. Work Unit Control: dump-after-deadline <boolean=true> Dump units if their deadline has passed. max-queue <integer=16> Maximum units per slot in the work queue. max-units <integer=0> Process at most this number of units, then pause. next-unit-percentage <integer=99> Pre-download the next work unit when the current one is this far along. Values less than 90 are not allowed. stall-detection-enabled <boolean=false> Attempt to detect stalled work units and restart them. stall-percent <integer=5> Minimum estimated percent work unit completion since last frame before a WU can be considered stalled, if zero the percentage is ignored. stall-timeout <integer=1800> Minimum time, in seconds, since last frame before a WU can be considered stalled.

In addition to the above settings, there is another set of options which are applicable only to the FAHViewer. This can be done by:

1) Open up Advanced Control
2) Click on Preferences
3) Under the Visualization Panel, in the Command box, add the appropriate option
4) Click on Save

Below is a list of all available options and their default settings (some settings may vary depending on the OS):

Code: Select all: Usage: FAHViewer.exe [OPTIONS]... Command line options: --chdir <string> Change directory before starting server. All files opened after this point, such as the configuration file, must have paths relative to the new directory. --config <string=viewer.xml> Set configuration file. --help [string] Print help screen or help on a particular option and exit. --info Print application and system information and exit. --license License information and exit. --print Print configuration and exit. -v Increase verbosity level. --version Print application version and exit. -v Increase verbosity level. Configuration options: The following options can be specified in a configuration file or on the command line using the following syntax: --<option> <value> or: --<option>=<value> or when marking boolean values true: --<option> background <string> Specify an alternative background image to use. Must be in PPM format. The value 'none' will disable the background image. basic <boolean=false> Disable advanced modes which require OpenGL 2.2 blur <boolean=true> Enable blur (advanced only) connect <string=127.0.0.1:36330> An address and port to connect to in the form: <host | IP>:<port> cycle-snapshots <boolean=true> Cycle through snapshot frames. force <boolean=false> Force running on blacklisted GPUs or in advanced modes fps <double=8> Snapshot display speed in frames per second. fullscreen <boolean=false> Display in fullscreen mode height <integer=600> Screen height interpolation-steps <integer=9> The number of interpolated protein views to calculate between snapshots. mode <integer=4> Render mode password <string=> A password for accessing the remote client profile <string=default> Set performance profile. This effects the CPU usage vs. smooth rendering. Valid options are: lean, default & mean recompute-bonds <boolean=false> Recompute bonds from expected bond lengths show-buttons <boolean=true> Display buttons show-info <boolean=true> Display simulation info show-logos <boolean=true> Display logos slot <integer=0> Slot on the client to view test <boolean=true> Load test data tpr <string> Load Gromacs .tpr file trn <string> Load Gromacs .trr or .trx file width <integer=800> Screen width wiggle <boolean=true> Enable atom wiggling which approximates simulation activity x-rotation <double=0> Rotation about the X-axis in degrees per second xtc <string> Load Gromacs .xtc file xyz <string> An XYZ file to read and display y-rotation <double=10> Rotation about the Y-axis in degrees per second zoom <double=1.05> Zoom level Logging: log <string> Set log file. log-color <boolean=false> Print log messages with ANSI color coding. log-crlf <boolean=true> Print carriage return and line feed at end of log lines. log-date <boolean=false> Print date information with log entries. log-date-periodically <integer=0> Print date to log before new log entries if so many seconds have passed since the last date was printed. log-debug <boolean=true> Disable or enable debugging info. log-domain <boolean=false> Print domain information with log entries. log-domain-levels <string ...> Set log levels by domain. Format is: <domain>[:i|d|t]:<level> ... Entries are separated by white-space and or commas. i - info d - debug For example: server:i:3 module:6 Set 'server' domain info messages to level 3 and 'module' info and debug messages to level 6. All other domains will follow the system wide log verbosity level. If <level> is negative it is relative to the system wide verbosity. log-header <boolean=true> Enable log message headers. log-level <boolean=true> Print level information with log entries. log-no-info-header <boolean=false> Don't print 'INFO(#):' in header. log-redirect <boolean=false> Redirect all output to log file. Implies !log-to-screen. log-rotate <boolean=true> Rotate log files on each run. log-rotate-dir <string=logs> Put rotated logs in this directory. log-rotate-max <integer=0> Maximum number of rotated logs to keep. log-short-level <boolean=false> Print shortened level information with log entries. log-simple-domains <boolean=true> Remove any leading directories and trailing file extensions from domains so that source code file names can be easily used as log domains. log-thread-id <boolean=false> Print id with log entries. log-thread-prefix <boolean=false> Print thread prefixes, if set, with log entries. log-time <boolean=true> Print time information with log entries. log-to-screen <boolean=true> Log to screen. log-truncate <boolean=false> Truncate log file. verbosity <integer=1> Set logging level for INFO and DEBUG messages. Viewer key commands: a Show about screen. 1 Space Filling render mode. 2 Ball & Stick render mode. 3 Stick render mode. 4 Advanced Space Filling render mode. (Requires OpenGL 2.2) 5 Advanced Ball & Stick render mode. (Requires OpenGL 2.2) 6 Advanced Stick render mode. (Requires OpenGL 2.2) 7 Cartoon Space Filling render mode. (Requires OpenGL 2.2) 8 Cartoon Ball & Stick render mode. (Requires OpenGL 2.2) b Toggle blur (advanced modes only). i Toggle info display. l Toggle logo display. f Toggle fullscreen. 0 Toggle snapshot cycling. + Increase snapshot cycle rate. - Decrease snapshot cycle rate. [ Decrease slot ID. ] Increase slot ID. <Space> Toggle rotation. <Up> Increase X-axis rotation speed in the upward direction. <Down> Increase X-axis rotation speed in the downward direction. <Left> Increase Y-axis rotation speed in the left direction. <Right> Increase Y-axis rotation speed in the right direction. <Page Up> Zoom in. <Page Down> Zoom out. <ESC> Quit popup. q Quit application or popup. h Show help screen. Viewer mouse commands: Left Drag Rotate protein. Wheel Zoom in and out.

by **PantherX** » Wed Mar 19, 2014 9:50 pm

12 - Connectivity Issues In V7

If you have problems with Web Control or Advanced Control connecting to FAHClient, you can find some quick troubleshooting techniques below.

Web Control Issues
If the Web Control can't connect to the FAHClient, possible reasons are:
1) FAHClient isn't running. Please ensure that it is.
2) Browser isn't supported. Make sure that you are using the latest browser version
3) Sandbox limitations of JavaScript is preventing a remote connection.

Advanced Control Issues (Local)
If the Advanced Control can't connect to the FAHClient on the same system, possible reasons are:
1) FAHClient isn't running. Please ensure that it is.
2) A security application might be blocking the local connection to FAHClient. Please create an exception.
3) If you have a Windows system, make sure that you meet the minimum requirements (Details)

Advanced Control Issues (Remote)
If the Advanced Control can't connect to the FAHClient on the remote system, possible reasons are:
1) FAHClient isn't running on the remote system. Please ensure that it is.
2) Firewall is blocking the remote connection. Ensure that the firewall rules permit F@H connections.
3) Passwords on the local and remote system is the same. Please ensure that they are the same.
4) Remote system is using a different version of V7 than the local system. Please ensure that both systems are running the same V7 version.
5) The allow/deny settings might be incorrect. Please ensure that the settings are correct.
6) Remote client wasn't restarted after configuring remote access. Please restart the client after configuring remote access.
7) If you have a Windows system, make sure that you meet the minimum requirements (Details)

Last Updated 23-Mar-2014 - PantherX

by **PantherX** » Wed Mar 19, 2014 9:51 pm

13 - Troubleshooting Tips

Below are some broad suggestions to help fix an issue that you might have. Please note that these are generic tips and suggestions so it may not apply to your particular setup. We do encourage you to create a thread in the appropriate Forum to get help specific to your needs.

For overheating of the CPU, you can try the following:
A) Make sure that the cooling system is properly set-up
B) Make sure that the cooling system is clean and that no dust or debris is blocking the ventilation
C) Reduce the number the CPUs used by F@H. In V7, this is done via the Advanced Control -> Configure -> Slots Tab -> CPU -> Replace -1 with a number greater than or equal to 1
D) If you CPU is overclocked, consider reducing the frequencies to lower the heat output

For overheating of the GPU, you can try the following:
A) Make sure that the cooling system is properly set-up
B) Make sure that the cooling system is clean and that no dust or debris is blocking the ventilation
C) If you GPU is overclocked, consider reducing the frequencies to lower the heat output

Despite fulfilling all the requirements for QRB, if you are not getting bonus points, you may check:
A) Are there any typos in the Username and/or Passkey?
B) Is the Username/Passkey combination qualified for the QRB?
C) Are any of your clients producing errors which may have caused you to fall below the 80% WU return rate?
D) Are you finishing the WU before the Preferred Deadline?
E) Is the Client properly configured?

If you can't upload WUs, make sure:
1) You are connected to the internet
2) Your security application isn't blocking F@H connections. If it is, please create an exception

by **PantherX** » Wed Mar 19, 2014 9:51 pm

14 - Additional Links

Below is a list of links which you may find helpl:

Installation Guide: Details
F@H Username Selection: Details
F@H Passkey: Details
F@H Wikipedia Article: Details
F@H Homepage: Details