FAHlog Messages

NOTE::Incomplete

The following information purports to messages created by the folding@home clients which are written to FAHLog.txt. Since the messages reported are affected by the verbosity set by the client, these will be noted as verbosity dependant. Any messages that always appear in the same place in the log file, like the inital startup sections will be noted also. All messages are preceded by a timestamp in GMT. Unless explicitely specified, all messages are normal (not problem reporting) output from the client.

Currently messages are listed in order they appear whilst output by the console client with a verbosity of 9

="Static Messages"= The following messages are always output by the console versions of the F@H Client every time it starts. These messages are NOT preceded by timestamps. This will always be written at the start of FAHlog.txt, and at any subsequent client (re)starts: -- Opening Log file [DATE TIME (GMT)] Folding@Home Client Version $.$$(Beta) http://folding.stanford.edu Launch directory: $$ Executable: $$ Arguments: $$
 * 1) $$$$$ Edition ###############################################################

=Client Specific=

Windows
Entered installed folding folder to do work.

Console
Launched as a service.

- Use IE connection settings: [Yes/No]

Mac OS X
=Client independent= - Ask before connecting: No

- User name: XXXXXXXX (Team XXXXX) - User ID: XXXXXXXXXXXXXXXX - Machine ID: X

Loaded queue successfully. + Benchmarking ...

The following message is verbosity dependant The benchmark result is XXXX

If a WU is found, and the core is present: + Processing work unit Core required: FahCore_XX.exe Core found.

If a WU is not found { + Attempting to get work packet The following message is verbosity dependant - Will indicate memory of XXX MB - Connecting to assignment server - Successful: assigned to (xx.xx.xxx.xxx).

+ News From Folding@Home: Welcome to Folding@Home

The following message is verbosity dependant Loaded queue successfully. - Receiving payload (expected size: XXXXXXX) - Downloaded at ~XXX kB/s - Averaged speed for that direction ~XXX kB/s

+ Received work. }

The following message is verbosity dependant - Autosending finished units... Trying to send all finished work units + No unsent completed units remaining. - Autosend completed

Working on Unit XX [DATE TIME] (GMT) + Working ...

The following message is verbosity dependant - Calling 'FahCore_XX.exe -dir work/ -suffix XX -checkpoint X -service -verbose -lifeline XXX -version XXX'

Core produced messages appear here in the log

End of core produced messages

The following message is verbosity dependant Unit X finished with 98 percent of time to deadline remaining. Updated performance fraction: 0.978617

Sending work to server + Attempting to send results The following message is verbosity dependant - Reading file work/wuresults_03.dat from core (Read 2287700 bytes from disk) - Uploaded at ~18 kB/s - Averaged speed for that direction ~17 kB/s

+ Results successfully sent Thank you for your contribution to Folding@Home. + Number of Units Completed: 149

The following message is verbosity dependant

The SIGTERM ID differes between OSes Service stop request received. ***** Got a SIGTERM signal (2) Killing all core threads

Folding@Home Client Shutdown.

=Core Messages=

GROMACS
Folding@Home Gromacs Core Version 1.86 (August 28, 2005) Preparing to commence simulation - Looking at optimizations... - Created dyn - Files status OK - Expanded XXXXXX -> XXXXXXXX (decompressed XXX.X percent) - Starting from initial work packet Project: P (Run R, Clone C, Gen G) Assembly optimizations on if available. Entering M.D.

Optionally (Starting from checkpoint)

Protein: [PROTEIN NAME] Writing local files

If SSE is enabled Extra SSE boost OK.

Writing local files Completed 0 out of XXXXXXX steps (0) Timered checkpoint triggered.

Writing local files Completed XXXXXX out of XXXXXX steps (100) Writing final coordinates. Past main M.D. loop Finished Work Unit: - Reading up to XXXXXXX from "work/wudata_XX.arc": Read XXXXXXX - Reading up to XXXXXXX from "work/wudata_XX.xtc": Read XXXXXXX goefile size: 0 logfile size: XXXXX Leaving Run - Writing XXXXXX bytes of core data to disk... ... Done. - Shutting down core Folding@home Core Shutdown: FINISHED_UNIT CoreStatus = 64 (100)

DGROMACS
Folding@Home Double Gromacs Core Version 1.72 (February 4, 2005) Preparing to commence simulation - Looking at optimizations... - Files status OK - Expanded XXXXXXXX -> XXXXXXXX (decompressed XXX.X percent) Project: P (Run R, Clone C, Gen G) Assembly optimizations on if available. Entering M.D.

Optionally (Starting from checkpoint)

Protein: [PROTEIN NAME] Writing local files

If SSE2 is enabled Extra SSE2 boost OK

Completed X out of XXXXX steps (X) Timered checkpoint triggered.

Writing local files Completed XXXXXX out of XXXXXX steps (100) Writing final coordinates. Past main M.D. loop Finished Work Unit: - Reading up to XXXXXXX from "work/wudata_XX.arc": Read XXXXXXX - Reading up to XXXXXXX from "work/wudata_XX.xtc": Read XXXXXXX goefile size: 0 logfile size: XXXXX Leaving Run - Writing XXXXXX bytes of core data to disk... ... Done. - Shutting down core Folding@home Core Shutdown: FINISHED_UNIT CoreStatus = 64 (100)

GBGROMACS
Folding@Home GB Gromacs Core Version 1.90 (March 8, 2006) Preparing to commence simulation - Looking at optimizations... - Created dyn - Files status OK - Expanded XXXXX -> XXXXXX (decompressed XXX.X percent)

Optionally (Starting from checkpoint) Else - Starting from initial work packet

Project: P (Run R, Clone C, Gen G) Assembly optimizations on if available. Entering M.D. Protein: [PROTEIN NAME] Writing local files GB activated If SSE is enabled Extra SSE boost OK.

Writing local files Completed X out of XXXXXXXX steps (X) Timered checkpoint triggered.

Completed XXXXXXXX out of XXXXXXXX steps (100) Writing final coordinates. Past main M.D. loop Finished Work Unit: - Reading up to XXXX from "work/wudata_XX.arc": Read XXXX - Reading up to XXXXXX from "work/wudata_XX.xtc": Read XXXXXX goefile size: X logfile size: XXXXXX Leaving Run - Writing XXXXXX bytes of core data to disk...  ... Done. - Shutting down core Folding@home Core Shutdown: FINISHED_UNIT CoreStatus = 64 (100)

GROMACS33
Folding@Home Gromacs 3.3 Core Version 1.70 (February 3, 2006) Preparing to commence simulation Looking at optimizations... - Expanded XXXXXXX -> XXXXXXX (decompressed XXX.X percent)

Optionally (Starting from checkpoint) Else - Starting from initial work packet

Project: P (Run R, Clone C, Gen G) Assembly optimizations on if available. Entering M.D. Protein: [PROTEIN NAME] Writing local files

If system has an AMD CPU Extra 3DNow boost OK.

If SSE is enabled Extra SSE boost OK.

Writing local files Completed X out of XXXXXXXX steps (X%) Timered checkpoint triggered.

Completed XXXXXXXX out of XXXXXXXX steps (100%) Writing final coordinates. Past main M.D. loop Finished Work Unit: - Reading up to XXXXXXX from "work/wudata_XX.arc": Read XXXXXXX - Reading up to XXXXXXX from "work/wudata_XX.xtc": Read XXXXXXX goefile size: X logfile size: XXXXX Leaving Run - Writing XXXXXXX bytes of core data to disk... ... Done. - Shutting down core Folding@home Core Shutdown: FINISHED_UNIT CoreStatus = 64 (100)

AMBER
Here is an example of the output from the AMBER/PMD core.

*--* Folding@Home PMD Core Version 1.03 (September 7, 2005) Preparing to commence simulation - Looking at optimizations... - Created dyn - Files status OK - Expanded 83495 -> 561874 (decompressed 672.9 percent) Project: 1808 (Run 10, Clone 344, Gen 20) Assembly optimizations on if available. Entering M.D. Protein: p1808_Collagen_Brodsky_refolding Completed 0 out of 500000 steps (0%) Writing checkpoint files Writing local files Completed 5000 out of 500000 steps (1%)

Writing local files Completed 495000 out of 500000 steps (99%) Writing checkpoint files Writing local files Completed 500000 out of 500000 steps (100%) Writing checkpoint files Finished Work Unit: Leaving Run - Writing 369457 bytes of core data to disk...  ... Done. - Shutting down core Folding@home Core Shutdown: FINISHED_UNIT CoreStatus = 64 (100) Sending work to server

TINKER
Here is an example of the output from the Tinker core. The "Finished a frame (X)" message is printed for each completed frame.

Folding@Home Client Core Version 2.53 (June 29, 2004) Proj: work/wudata_09 Done: 22864 -> 142983 (decompressed 625.3 percent) nsteps: 5000000 dt: 2.000000 dt_dump: 250.000000 temperature: 298.000000 xyzfile: "  393  p1136_p1130_L939_K12M_355K      1  N     -4.433577   77.576251  -25.2492..." keyfile: "parameters ./proj1136.prm NOVERSION ARCHIVE cutoff        16.0 taper         12..." - Couldn't get size info for dyn file: work/wudata_09.dyn Starting from initial work packet Protein: p1136_p1130_L939_K12M_355K - Run: 197 (Clone 92, Gen 2) - Frames Completed: 0, Remaining: 400 - Dynamic steps required: 5000000 Writing local files: parameters         work/wudata_09.prm - Writing "work/wudata_09.key": (overwrite) successful. - Writing "work/wudata_09.xyz": (overwrite) successful. - Writing "work/wudata_09.prm": (overwrite) successful. - Writing "work/wudata_09.key": (append) successful. PROJECT="work/wudata_09", NSTEPS=5000000, DT=2.0000, DTDUMP=25.000000, TEMP=298.00 TINKER: Software Tools for Molecular Design Version 3.8 October 2000 Copyright (c) Jay William Ponder 1990-2000 portions Copyright (c) Michael Shirts 2001 portions Copyright (c) Vijay S Pande 2001 Finished a frame (1)

Finished a frame (400) TINKER is Exiting following Normal Termination Finished Work Unit: ARC file integrity verified logfile size: 432503 Leaving Run - Writing 1477067 bytes of core data to disk. end (WriteWorkResults) - Shutting down core Folding@home Core Shutdown: FINISHED_UNIT CoreStatus = 64 (100) Sending work to server

QMD
Below is an EXAMPLE log, the numbers are retained because QMD has a slightly different format, in that the number of steps continually increases until convergence. Folding@Home QMD Core Version 1.04 (Apr 7, 2005) Preparing to commence simulation - Looking at optimizations... - Files status OK - Expanded XXXXXX -> XXXXXX (decompressed XXX.X percent) Project: P (Run R, Clone C, Gen G) Writing local files Extra SSE2 boost OK. Entering QMD... System: [PROTEIN NAME] Performing initial WF calculations - Number of total steps will change until convergence Completed 0 out of 2000 steps (0) Writing local files Completed 21 out of 2021 steps (1) Writing local files Completed 41 out of 2041 steps (2) Writing local files Completed 62 out of 2062 steps (3) Writing local files Timered checkpoint triggered. WF converged, jumping to MD Verifying checksum Finished Completed 63 out of 2063 steps (3) Writing local files Timered checkpoint triggered.

Completed 2063 out of 2063 steps (100)

GPU
*--* Folding@Home GPU Core - Alpha Version 0.04 (Wed Sep 27 16:59:31 PDT 2006) Compiler : Build host:

*--* Folding@Home GPU Core - Beta Version 0.05 (Sat Sep 30 16:08:52 PDT 2006) Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 13.10.3077 for 80x86 Build host: CYGWIN_NT-5.1 vishal-gpu 1.5.19(0.150/4/2) 2006-01-20 13:28 i686 Cygwin

Preparing to commence simulation - Assembly optimizations manually forced on. - Not checking prior termination. - Expanded 87033 -> 443729 (decompressed 509.8 percent) Project: 2720 (Run 1, Clone 1, Gen 9) Assembly optimizations on if available. Entering M.D. Will resume from checkpoint file Completed 0 Starting GUI Server Resuming from checkpoint Verified Verified Verified Verified Completed 1

Completed 100 Finished Work Unit: - Reading up to 45408 from "work/wudata_01.trr": Read 45408 - Reading up to 24368 from "work/wudata_01.xtc": Read 24368 logfile size: 10811 Leaving Run - Writing 81659 bytes of core data to disk... Done: 81147 -> 74703 (compressed to 92.0 percent) ... Done. - Shutting down core Folding@home Core Shutdown: FINISHED_UNIT CoreStatus = 64 (100) Unit 1 finished with 99 percent of time to deadline remaining. Updated performance fraction: 0.896914 Sending work to server

=Core independent=