Folding Forum

I have received a work unit that is calculated to be finished on the 29th of October 2012! (WU End from the folding@home Windows client). You see the WU details in the log file below. I cannot guarantee that my computer will be available for folding@home without interruption until then.

What I find strange is that in the client window it says that the current WU is run on AMBER. The log shows FahCore_82 however.

Here is the relevant part from my log:
[16:15:16] - Preparing to get new work unit...
[16:15:16] + Attempting to get work packet
[16:15:16] - Connecting to assignment server
[16:15:17] - Successful: assigned to (171.65.103.160).
[16:15:17] + News From Folding@Home: Welcome to Folding@Home
[16:15:17] Loaded queue successfully.
[16:15:23] + Connections closed: You may now disconnect
[16:15:23]
[16:15:23] + Processing work unit
[16:15:23] Core required: FahCore_82.exe
[16:15:23] Core not found.
[16:15:23] - Core is not present or corrupted.
[16:15:23] - Attempting to download new core...
[16:15:23] + Downloading new core: FahCore_82.exe
[16:15:23] - Presenting message box asking to network.
[16:15:27] + 10240 bytes downloaded
<...snip...>
[16:15:53] + 716479 bytes downloaded
[16:15:53] Verifying core Core_82.fah...
[16:15:53] Signature is VALID
[16:15:53]
[16:15:53] Trying to unzip core FahCore_82.exe
[16:16:03] Decompressed FahCore_82.exe (1683456 bytes) successfully
[16:16:03] + Core successfully engaged
[16:16:08]
[16:16:08] + Processing work unit
[16:16:08] Core required: FahCore_82.exe
[16:16:08] Core found.
[16:16:08] Working on Unit 09 [May 26 16:16:08]
[16:16:08] + Working ...
[16:16:08]
[16:16:08] *------------------------------*
[16:16:08] Folding@Home PMD Core
[16:16:08] Version 1.03 (September 7, 2005)
[16:16:08]
[16:16:08] Preparing to commence simulation
[16:16:08] - Looking at optimizations...
[16:16:09] - Created dyn
[16:16:09] - Files status OK
[16:16:09] - Expanded 93157 -> 599777 (decompressed 643.8 percent)
[16:16:09]
[16:16:09] Project: 2170 (Run 12, Clone 151, Gen 6)
[16:16:09]
[16:16:09] Assembly optimizations on if available.
[16:16:09] Entering M.D.
[16:16:16] Protein: p2170_lambda_obc_300K
[16:16:16]
[16:16:16] Completed 0 out of 500000 steps (0)
...

Welcome, cahok, to the forums.

As you would have realized by now, the Graphical client takes a couple of hours before it can come up with a sensible approximation.

I'd be dead if I gave estimates like that to my manager

Beyond the GUI client really sucking at giving intial ETAs, there might be a couple other tings to look at. Are you running with the -verbosity 9 flag? More info in the logs is helpful. In the next few lines did it log starting the optimizations (SSE, SSE2)?

Usually just waiting for it to finish 3-5 steps will give you a good ETA.

PMD (Amber) doesn't support any optimisation ... it's using FPU like Tinker did

cahok wrote:What I find strange is that in the client window it says that the current WU is run on AMBER. The log shows FahCore_82 however.

Here is the relevant part from my log:
[16:16:08] Folding@Home PMD Core

Just to clarify:
the PMD Core = FahCore_82 = the AMBER analysis method

(With so many obscure names/acronyms running around, it's a wonder that anybody figures out what's happening.)

I have had several of them and they seem to run very slowly

My old AMD machines (an Athlon XP2000+ and an Athlon 1500) loves them

Thanks for your fast responses. I'll give WU 2170 a chance then.

Funny ... now that I have started up my client again, it shows a completely reasonable execution time. Hm. Anyway - problem seems to be solved.

toTOW wrote:My old AMD machines (an Athlon XP2000+ and an Athlon 1500) loves them

A 2.2 GHz Athlon 64 x2 runs AMBER significantly faster than a 2.6 GHz C2D.

On the other hand, if you give both of them Double GROMACS, the C2D will run away with it.