FAHClient V7.1.52 released (1st Public-Release)

[7im]

Software version did not change the fahcores, and the fahcore is what runs on the GPU. So v.52 did not change anything there. If you are seeing higher temps, it's because you received work units that run hotter, i.e. using more of your computing resources, folding more for science. Er, folding less, now that you shut it off.

No attempt to reduce the CPU usage to slow down the client, thus reducing temps?

[VijayPande]

Thanks. PressFAQ fixed.

[bruce]

The GPU throughput and heat have nothing to do with the client version. The project that you're assigned specifies a specific FahCore and the FahCore does all the processing of the WU. All client versions will call the exact same FAHCore and process the project in the same way.

Some PROJECT can be processed more efficiently than other PROJECTS, hence more or less heat.

[Evil Penguin]

Did PG release the v7 client as a public release?
I only ask because the milestone for public release isn't complete yet.

The viewer for example can still only display demo proteins until there's a way to read trr, tpr files to produce visuals of the actual protein being folded.
That's a trivial feature as far as science is concerned and serves more as eye candy to the average joe, but still.

[7im]

Public release of a beta version, yes.

This in not the public release of a released version, so that milestone has not been completed yet.

[7im]

Why is an SMP slot connecting to a GPU assignment server?

Code: Select all

13:43:28:</config>
13:43:28:Trying to access database...
13:43:28:Successfully acquired database lock
13:43:28:Enabled folding slot 00: READY gpu:0:"G94 [GeForce 9600 GT]"
13:43:28:Enabled folding slot 01: READY gpu:1:"GF114 [GeForce GTX 560 Ti]"
13:43:28:Enabled folding slot 02: READY smp:6  <---------------------------------------------  SMP Slot
13:43:28:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
13:43:28:WU01:FS01:Connecting to assign-GPU.stanford.edu:80
13:43:28:WU02:FS02:Connecting to assign-GPU.stanford.edu:80 <--------------------------------------  on GPU AS?
13:43:29:WU00:FS00:Connecting to assign-GPU.stanford.edu:80
13:43:29:WU02:FS02:Connecting to assign3.stanford.edu:8080 <--------------- Shouldn't an SMP slot go here first?
13:43:29:WU01:FS01:Connecting to assign-GPU.stanford.edu:80
13:43:30:WU00:FS00:News: Welcome to Folding@Home
13:43:30:WU00:FS00:Assigned to work server 171.67.108.11


* http://foldingforum.org/viewtopic.php?p=211139#p211139

[Pick2]

I can't get the un-tar to work. Debian Squeeze

pluto@LP:~/FAH7$ ls -asl
1876 -rw-r--r-- 1 pluto pluto 1914198 Mar 23 11:32 fahclient_7.1.52-64bit-release.tar.bz2
pluto@LP:~/FAH7$ tar xjvf ./fahclient_7.1.52-64bit-release.tar.bz2
tar (child): bzip2: Cannot exec: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now

Any suggestions ?

[7im]

Still getting Transaction / Dependency errors from Fedora 16 trying to install FAHControl.

fahcontrol-7.1.52-1.noarch requires python(abi) = 2.6

[bollix47]

Another thread showing an smp slot going to a gpu AS:

viewtopic.php?p=211120#p211120

[bruce]

I built a SR-2 computer this week so I could both get higher PPD with A4 WUs and have the possibility of A5s. It has e5649 chips clocked at 3743mhz, well within the limits of some I have read about, and the temps run from 55c to 65c according to Coretemp. The computer has a Nvidia 8400GS, but I'm not using that for folding. I have it paused all the time so it won't slow down the CPUs. The problem is that v7.152 is showing that I'm only getting 6657 PPD while running a 7809 WU. Log is as follows:

Code: Select all

 *********************** Log Started 2012-03-23T06:30:58Z ***********************
06:30:58:************************* Folding@home Client *************************
06:30:58:      Website: http://folding.stanford.edu/
06:30:58:    Copyright: (c) 2009-2012 Stanford University
06:30:58:       Author: Joseph Coffland <joseph@cauldrondevelopment.com>
06:30:58:         Args: --lifeline 3176 --command-port=36330
06:30:58:       Config: C:/Users/Fred/AppData/Roaming/FAHClient/config.xml
06:30:58:******************************** Build ********************************
06:30:58:      Version: 7.1.52
06:30:58:         Date: Mar 20 2012
06:30:58:         Time: 19:37:42
06:30:58:      SVN Rev: 3515
06:30:58:       Branch: fah/trunk/client
06:30:58:     Compiler: Intel(R) C++ MSVC 1500 mode 1200
06:30:58:      Options: /TP /nologo /EHa /Qdiag-disable:4297,4103,1786,279 /Ox -arch:SSE
06:30:58:               /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qopenmp /Qrestrict /MT
06:30:58:     Platform: win32 XP
06:30:58:         Bits: 32
06:30:58:         Mode: Release
06:30:58:******************************* System ********************************
06:30:58:          CPU: Intel(R) Xeon(R) CPU E5649 @ 2.53GHz
06:30:58:       CPU ID: GenuineIntel Family 6 Model 44 Stepping 2
06:30:58:         CPUs: 24
06:30:58:       Memory: 11.99GiB
06:30:58:  Free Memory: 10.40GiB
06:30:58:      Threads: WINDOWS_THREADS
06:30:58:   On Battery: false
06:30:58:   UTC offset: -7
06:30:58:          PID: 1760
06:30:58:          CWD: C:/Users/Fred/AppData/Roaming/FAHClient
06:30:58:           OS: Windows 7 Professional
06:30:58:      OS Arch: AMD64
06:30:58:         GPUs: 1
06:30:58:        GPU 0: NVIDIA:1 G98 [GeForce 8400 GS]
06:30:58:         CUDA: 1.1
06:30:58:  CUDA Driver: 4020
06:30:58:Win32 Service: false
06:30:58:***********************************************************************
06:30:58:<config>
06:30:58:  <!-- FahCore Control -->
06:30:58:  <cpu-affinity v='true'/>
06:30:58:
06:30:58:  <!-- Folding Slot Configuration -->
06:30:58:  <gpu v='true'/>
06:30:58:
06:30:58:  <!-- Network -->
06:30:58:  <proxy v=':8080'/>
06:30:58:
06:30:58:  <!-- User Information -->
06:30:58:  <passkey v='********************************'/>
06:30:58:  <team v='75255'/>
06:30:58:  <user v='Sailer'/>
06:30:58:
06:30:58:  <!-- Folding Slots -->
06:30:58:  <slot id='0' type='GPU'>
06:30:58:    <next-unit-percentage v='98'/>
06:30:58:  </slot>
06:30:58:  <slot id='1' type='SMP'>
06:30:58:    <client-type v='bigadv'/>
06:30:58:    <cpus v='-1'/>
06:30:58:    <max-packet-size v='big'/>
06:30:58:    <next-unit-percentage v='95'/>
06:30:58:  </slot>
06:30:58:</config>
06:30:58:Trying to access database...
06:30:59:Successfully acquired database lock
06:30:59:Enabled folding slot 00: READY gpu:0:"G98 [GeForce 8400 GS]"
06:30:59:Enabled folding slot 01: READY smp:24
06:30:59:WU00:FS00:Starting
06:30:59:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Fred/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/NVIDIA/G80/Core_11.fah/FahCore_11.exe -dir 00 -suffix 01 -version 701 -lifeline 1760 -checkpoint 15 -gpu 0
06:30:59:Server connection id=1 on 0.0.0.0:36330 from 127.0.0.1
06:31:00:WU00:FS00:Started FahCore on PID 388
06:31:00:WU00:FS00:Core PID:2952
06:31:00:WU00:FS00:FahCore 0x11 started
06:31:00:WU01:FS01:Starting
06:31:00:WU01:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Fred/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/Core_a4.fah/FahCore_a4.exe -dir 01 -suffix 01 -version 701 -lifeline 1760 -checkpoint 15 -np 24
06:31:00:WU01:FS01:Started FahCore on PID 2868
06:31:00:WU01:FS01:Core PID:3264
06:31:00:WU01:FS01:FahCore 0xa4 started
06:31:01:WU00:FS00:0x11:
06:31:01:WU00:FS00:0x11:*------------------------------*
06:31:01:WU00:FS00:0x11:Folding@Home GPU Core
06:31:01:WU00:FS00:0x11:Version 1.31 (Tue Sep 15 10:57:42 PDT 2009)
06:31:01:WU00:FS00:0x11:
06:31:01:WU00:FS00:0x11:Compiler  : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
06:31:01:WU00:FS00:0x11:Build host: amoeba
06:31:01:WU00:FS00:0x11:Board Type: Nvidia
06:31:01:WU00:FS00:0x11:Core      :
06:31:01:WU00:FS00:0x11:Preparing to commence simulation
06:31:01:WU00:FS00:0x11:- Looking at optimizations...
06:31:01:WU00:FS00:0x11:- Files status OK
06:31:01:WU00:FS00:0x11:- Expanded 45505 -> 251112 (decompressed 551.8 percent)
06:31:01:WU00:FS00:0x11:Called DecompressByteArray: compressed_data_size=45505 data_size=251112, decompressed_data_size=251112 diff=0
06:31:01:WU00:FS00:0x11:- Digital signature verified
06:31:01:WU00:FS00:0x11:
06:31:01:WU00:FS00:0x11:Project: 5771 (Run 4, Clone 253, Gen 3752)
06:31:01:WU00:FS00:0x11:
06:31:01:WU00:FS00:0x11:Assembly optimizations on if available.
06:31:01:WU00:FS00:0x11:Entering M.D.
06:31:01:WU01:FS01:0xa4:
06:31:01:WU01:FS01:0xa4:*------------------------------*
06:31:01:WU01:FS01:0xa4:Folding@Home Gromacs GB Core
06:31:01:WU01:FS01:0xa4:Version 2.27 (Dec. 15, 2010)
06:31:01:WU01:FS01:0xa4:
06:31:01:WU01:FS01:0xa4:Preparing to commence simulation
06:31:01:WU01:FS01:0xa4:- Looking at optimizations...
06:31:01:WU01:FS01:0xa4:- Files status OK
06:31:02:WU01:FS01:0xa4:- Expanded 2079133 -> 5386224 (decompressed 259.0 percent)
06:31:02:WU01:FS01:0xa4:Called DecompressByteArray: compressed_data_size=2079133 data_size=5386224, decompressed_data_size=5386224 diff=0
06:31:02:WU01:FS01:0xa4:- Digital signature verified
06:31:02:WU01:FS01:0xa4:
06:31:02:WU01:FS01:0xa4:Project: 7809 (Run 8, Clone 71, Gen 43)
06:31:02:WU01:FS01:0xa4:
06:31:02:WU01:FS01:0xa4:Assembly optimizations on if available.
06:31:02:WU01:FS01:0xa4:Entering M.D.
06:31:06:WU00:FS00:0x11:Will resume from checkpoint file
06:31:06:WU00:FS00:0x11:Tpr hash 00/wudata_01.tpr:  1027662128 3126348985 871212678 3502266858 4146295246
06:31:06:WU00:FS00:0x11:
06:31:06:WU00:FS00:0x11:Calling fah_main args: 14 usage=100
06:31:06:WU00:FS00:0x11:
06:31:07:WU00:FS00:0x11:Working on Protein
06:31:08:WU01:FS01:0xa4:Mapping NT from 24 to 24
06:31:08:WU00:FS00:0x11:Client config unavailable.
06:31:08:WU00:FS00:0x11:Resuming from checkpoint
06:31:08:WU00:FS00:0x11:fcCheckPointResume: retreived and current tpr file hash:
06:31:08:WU00:FS00:0x11:   0   1027662128   1027662128
06:31:08:WU00:FS00:0x11:   1   3126348985   3126348985
06:31:08:WU00:FS00:0x11:   2    871212678    871212678
06:31:08:WU00:FS00:0x11:   3   3502266858   3502266858
06:31:08:WU00:FS00:0x11:   4   4146295246   4146295246
06:31:08:WU00:FS00:0x11:fcCheckPointResume: file hashes same.
06:31:08:WU00:FS00:0x11:fcCheckPointResume: state restored.
06:31:08:WU00:FS00:0x11:Verified 00/wudata_01.log
06:31:08:WU00:FS00:0x11:Verified 00/wudata_01.edr
06:31:08:WU00:FS00:0x11:Verified 00/wudata_01.xtc
06:31:08:WU00:FS00:0x11:Starting GUI Server
06:31:10:WU01:FS01:0xa4:Completed 0 out of 1500000 steps  (0%)
06:32:04:FS00:Paused
06:32:04:FS00:Shutting core down
06:32:10:WU00:FS00:0x11:Client no longer detected. Shutting down core
06:32:10:WU00:FS00:0x11:
06:32:10:WU00:FS00:0x11:Folding@home Core Shutdown: CLIENT_DIED
06:32:27:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)
06:35:23:WU01:FS01:0xa4:Completed 15000 out of 1500000 steps  (1%)
06:39:09:WU01:FS01:0xa4:Completed 30000 out of 1500000 steps  (2%)
06:42:53:WU01:FS01:0xa4:Completed 45000 out of 1500000 steps  (3%)
06:46:37:WU01:FS01:0xa4:Completed 60000 out of 1500000 steps  (4%)
06:50:22:WU01:FS01:0xa4:Completed 75000 out of 1500000 steps  (5%)
06:54:09:WU01:FS01:0xa4:Completed 90000 out of 1500000 steps  (6%)
06:57:58:WU01:FS01:0xa4:Completed 105000 out of 1500000 steps  (7%)
07:01:53:WU01:FS01:0xa4:Completed 120000 out of 1500000 steps  (8%)
07:05:41:WU01:FS01:0xa4:Completed 135000 out of 1500000 steps  (9%)
07:09:27:WU01:FS01:0xa4:Completed 150000 out of 1500000 steps  (10%)
07:13:21:WU01:FS01:0xa4:Completed 165000 out of 1500000 steps  (11%)
07:17:04:WU01:FS01:0xa4:Completed 180000 out of 1500000 steps  (12%)
07:20:49:WU01:FS01:0xa4:Completed 195000 out of 1500000 steps  (13%)
07:24:39:WU01:FS01:0xa4:Completed 210000 out of 1500000 steps  (14%)


That takes up a lot of space. Don't know how to make it smaller. Anyway, I did run v6.34 on the SR-2 and it was showing about 78,000-79,000 PPD running A3 WUs, So my question concerns as to whether or not v7.152 is reporting the PPD correctly? I have checked Task Manager and it shows that all 24 cores are at 100% and the CPU process is at 99%, for what that is worth.

[bollix47]

According to the bonus calculator ( http://www.linuxforge.net/bonuscalc2.php ) you're getting ~70K PPD with the TPFs showing in your log. The Estimated TPF/PPD in v7 is wrong for some(most in my case) SMP WUs. Looks like your rig is performing as you would expect.

btw ... HFM.net now supports v7 as well as v6 and the TPF/PPD figures are accurately calculated in it.

[Joe_H]

That takes up a lot of space. Don't know how to make it smaller. Anyway, I did run v6.34 on the SR-2 and it was showing about 78,000-79,000 PPD running A3 WUs, So my question concerns as to whether or not v7.152 is reporting the PPD correctly? I have checked Task Manager and it shows that all 24 cores are at 100% and the CPU process is at 99%, for what that is worth.

First, use the "Code" tags of the full editor to wrap your section of log file instead of "Quote". That will put the log into a scrolling window.
Edit by Mod: Fixed.

As mentioned already, V7 does have a known bug on its display of PPD and TPF. They have the fix targeted for the full public release.

One other thing, here you mention you have your GPU slot paused:

...The computer has a Nvidia 8400GS, but I'm not using that for folding. I have it paused all the time so it won't slow down the CPUs.

It would be better to delete the GPU slot completely if you are not going to use it. Otherwise you end up downloading GPU WU's and not processing them as seen in this log section:

Code: Select all

06:31:01:WU00:FS00:0x11:
06:31:01:WU00:FS00:0x11:*------------------------------*
06:31:01:WU00:FS00:0x11:Folding@Home GPU Core
06:31:01:WU00:FS00:0x11:Version 1.31 (Tue Sep 15 10:57:42 PDT 2009)
06:31:01:WU00:FS00:0x11:
06:31:01:WU00:FS00:0x11:Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
06:31:01:WU00:FS00:0x11:Build host: amoeba
06:31:01:WU00:FS00:0x11:Board Type: Nvidia
06:31:01:WU00:FS00:0x11:Core :
06:31:01:WU00:FS00:0x11:Preparing to commence simulation
06:31:01:WU00:FS00:0x11:- Looking at optimizations...
06:31:01:WU00:FS00:0x11:- Files status OK
06:31:01:WU00:FS00:0x11:- Expanded 45505 -> 251112 (decompressed 551.8 percent)
06:31:01:WU00:FS00:0x11:Called DecompressByteArray: compressed_data_size=45505 data_size=251112, decompressed_data_size=251112 diff=0
06:31:01:WU00:FS00:0x11:- Digital signature verified
06:31:01:WU00:FS00:0x11:
06:31:01:WU00:FS00:0x11:Project: 5771 (Run 4, Clone 253, Gen 3752)
06:31:01:WU00:FS00:0x11:
06:31:01:WU00:FS00:0x11:Assembly optimizations on if available.
06:31:01:WU00:FS00:0x11:Entering M.D.06:31:06:WU00:FS00:0x11:Will resume from checkpoint file
06:31:06:WU00:FS00:0x11:Tpr hash 00/wudata_01.tpr: 1027662128 3126348985 871212678 3502266858 4146295246
06:31:06:WU00:FS00:0x11:
06:31:06:WU00:FS00:0x11:Calling fah_main args: 14 usage=100
06:31:06:WU00:FS00:0x11:
06:31:07:WU00:FS00:0x11:Working on Protein
06:31:08:WU01:FS01:0xa4:Mapping NT from 24 to 24
06:31:08:WU00:FS00:0x11:Client config unavailable.
06:31:08:WU00:FS00:0x11:Resuming from checkpoint
06:31:08:WU00:FS00:0x11:fcCheckPointResume: retreived and current tpr file hash:
06:31:08:WU00:FS00:0x11: 0 1027662128 1027662128
06:31:08:WU00:FS00:0x11: 1 3126348985 3126348985
06:31:08:WU00:FS00:0x11: 2 871212678 871212678
06:31:08:WU00:FS00:0x11: 3 3502266858 3502266858
06:31:08:WU00:FS00:0x11: 4 4146295246 4146295246
06:31:08:WU00:FS00:0x11:fcCheckPointResume: file hashes same.
06:31:08:WU00:FS00:0x11:fcCheckPointResume: state restored.
06:31:08:WU00:FS00:0x11:Verified 00/wudata_01.log
06:31:08:WU00:FS00:0x11:Verified 00/wudata_01.edr
06:31:08:WU00:FS00:0x11:Verified 00/wudata_01.xtc
06:31:08:WU00:FS00:0x11:Starting GUI Server
06:31:10:WU01:FS01:0xa4:Completed 0 out of 1500000 steps (0%)
06:32:04:FS00:Paused
06:32:04:FS00:Shutting core down
06:32:10:WU00:FS00:0x11:Client no longer detected. Shutting down core
06:32:10:WU00:FS00:0x11:
06:32:10:WU00:FS00:0x11:Folding@home Core Shutdown: CLIENT_DIED
06:32:27:WU00:FS00:FahCore returned: INTERRUPTED (102 = 0x66)

That slows down the project as the WU will not get reassigned to someone else until it reaches its preferred deadline. The next WU in its series can not be generated until it is returned.

[bollix47]

They have the fix targeted for the full public release.

Sorry, but these old eyes are having a problem finding a ticket for the above. Do you have a ticket number?

Thanks

[7im]

Was this one, so not sure where we are at right now.

https://fah-web.stanford.edu/projects/FAHClient/ticket/395

There is another ticket open on a different development system to upgrade all of the work servers so they support calculating the estimated PPD, but that is not a client issue, that is a server issue, so no V7 ticket on that.

[bollix47]

Code: Select all

            20:57:59:WU00:FS00:0xa4:Completed 212500 out of 250000 steps  (85%)
52.5   42   20:58:41:WU00:FS00:0xa4:Completed 215000 out of 250000 steps  (86%)
35     42   20:59:23:WU00:FS00:0xa4:Completed 217500 out of 250000 steps  (87%)
52.5   42   21:00:05:WU00:FS00:0xa4:Completed 220000 out of 250000 steps  (88%)
35     42   21:00:47:WU00:FS00:0xa4:Completed 222500 out of 250000 steps  (89%)
52.5   42   21:01:29:WU00:FS00:0xa4:Completed 225000 out of 250000 steps  (90%)
35     43   21:02:12:WU00:FS00:0xa4:Completed 227500 out of 250000 steps  (91%)
52.5   42   21:02:54:WU00:FS00:0xa4:Completed 230000 out of 250000 steps  (92%)


The above is one example showing Estimated TPF, Actual TPF and log entry for a P8001. The times are in seconds. The same fluctuation occurs in all the 80xx projects as well as 690x projects. The differences for the bigadv WUs are higher but display the same pattern. On a 6901 with actual TPF of 13:40 the Estimated TPF fluctuates from a high of 17:02 to a low of 11:23 after each step in the same pattern as above.

I have seen some SMP WUs where the Estimated TPF and the actual were within a second of each other. If memory serves me right it was a P7905 but the majority of projects I get are as mentioned above and all of them show the same pattern of fluctuation.

I have FAHControl setup on Windows Vista 32 bit and my current v7 remotes are all Ubuntu 11.10 64 bit but this pattern shows up with both my local Window's client and the remote clients.