FAH files

From FaHWiki

Some files are good to know - FAHlog.txt, FAHlog-Prev.txt and unitinfo.txt.

Some 3rd party utilities can read/modify some FAH client files, but generally there is no need to edit FAH client files as that may cause more harm than good (corrupted settings, corrupted work unit, etc.).

A list of the most common FAH client files:

File	Description
`FAHlog.txt`	Client log file. See also: FAHlog_Messages
`FAHlog-Prev.txt`	Previous client log file. See also: FAHlog_Messages
`FahCore_10.exe`	GPU core.
`FahCore_65.exe`	Tinker core
`FahCore_78.exe`	Gromacs core.
`FahCore_79.exe`	Double Gromacs core.
`FahCore_7a.exe`	GBGromacs core.
`FahCore_7b.exe`	Double Gromacs B core.
`FahCore_80.exe`	Gromacs SREM core
`FahCore_82.exe`	Amber core
`FahCore_96.exe`	QMD core.
`FahCore_a0.exe`	Gromacs 33 core.
`FahCore_a1.exe`	Gromacs SMP core.
`MyFolding.html`	Simple HTML page with links to useful other pages.
`client.cfg`	Client configuration. Do not edit manually, it looks like a text file but it's not.
`machinedependent.dat`	Binary file containing the User ID. Only created by the Linux and Mac OS X clients.
`mpiexec` / `mpiexec.exe`	Application used by the SMP client
`smpd.exe`	Application used only by the Windows SMP client
`queue.dat`	Binary file containing information about the queue of WU. qd is a useful utility that will list it's contents. Download qd \| See also: Howto use qd to debug the FAH client
`unitinfo.txt`	Simple text file with information about the current WU. It is generated from the `work/wuinfo_<XX>.dat` file.
`work/`	Directory containing the WUs. Almost all the files in the work directory are in the filename format `<name>_<queue index>.<extension>`. The name indicates what kind of data is in the file together with the file extention. The queue index is a 2 digit number representing the position of the WU in the queue (the file `queue.dat`). The filename extentions often hint to which Gromacs file format it is in.
`work/current.xyz`	Contains the atom positions of the current WU. It can be displayed using Jmol or other visualization tools.
`work/step<XXXX>.pdb`	Protein Data Bank file, the standard format of the wwPDB. Contains the atom positions of a WU. It's more detailed than `current.xyz`, but is created only in certain EUE conditions. It can be displayed using Jmol.
`work/logfile_<XX>.txt`	Contains the log for that particular WU as generated by the core (mdrun logfile in the case of Gromacs-based cores). This file is usually only available for the current WU and has its content is also in `FAHlog.txt`. The F@H client scans the `work/logfile_<XX>.txt` file and logs changes together with a timestamp in the `FAHlog.txt`.
`work/wuresults_<XX>.dat`	Binary file containing the results of the processed WU. This file is only available when the results have not been sent to Stanford servers, for instance when the client uses Minimized Networking aka Batched Processing and/or when the client is configured to ask for confirmation before connecting to the Internet.
`work/wuinfo_<XX>.dat`	Binary file containing the Work Unit name and some other data. This file is usually only available for the current WU. It is used by the FAH client to generate the `unitinfo.txt` file.
`work/wudata_<XX>.dat`	Binary file which is the actualy Work Unit. This file is usually only available for the current WU or for the WUs which have been downloaded and queued for processing when using Minimized Networking.
`work/wudata_<XX>.arc`	ASCII text file which is an Insight II Cartesian Coordinate Archive File. Insight II is a molecular modeling environment that provides a graphical interface to algorithms for molecular dynamics, homology modeling, de novo design, and electrostatics. This file is usually only available for the current WU.
`work/wudata_<XX>.chk`	Binary file which is a newzmat Gaussian 03 checkpoint file. This file is usually only available for the current WU.