Print This Page

FAQ

1. DCMonitor shows the status of a client as stopped but when I check, the client is running. Why does that happen?

This is caused by the system time on the client box being more than five minutes faster/slower than system time on the box running DCMonitor. Set the time on the client box to the correct time then refresh DCMonitor should fix the problem.

2. Why am I only shown the protein download time and deadline time when I try to view the protein detail of a F@H client?

The protein has not been found in the project.csv file. Re-downloading the file (see the options menu) should fix the problem.

3. Why is the 'Update projects.csv' option unavailable from the options menu?

DCMonitor is not 'Net-aware' by default. Go to the options dialog and enable the net aware options to make the update option available.

4. On the F@H tab, what do the characters in the type column mean?

There is a character for each core type. 'G' means the client is using a Gromacs core, 'T' means the client is using a Tinker core and 'U' means the client is using an unknown core or a Genome@Home core.

5. What do the column name abbreviations on the Distributed Folding table mean?

STCG = Structures To Complete Generation
CGP = Current Generation Points
TBGP = Total Buffered Generation Points

6. Why is the Seventeen or Bust monitoring so erratic?

The Seventeen or Bust client is very hard to monitor accurately due to the output from the client. It isn't possible to monitor more than one SoB client running from the same directory as the log file does not give any indication as to which status line relates to which client. For the monitoring to work at all intermediate block reporting needs be enabled and there must only be one client being run from each directory.


Previous page: Version history
Next page: Related links