[Egon]

This is for all you FAHMonitor users, who are also using the new SMP client. (That should narrow it down some!)

There is a bug (reported to F@H by me, et al.) in the way that the new SMP beta client (or the projects assigned to it) are reporting status in the unitinfo.txt file. This is causing problems with FAHMonitor's ability to match the WU with the official WU entry, so that points aren't being tallied/reported correctly by FAHMonitor-- and, presumably, other third-party reporting apps.

Until Stanford fixes the problem, please let me know the project number of the SMP WU (found in the FAHLog.txt file) as soon as your machine finishes it, and I'll correct the history entries manually... assuming you even care about this! ;-)

Thanks for your patience!

---

For the technically minded, here's the issue:

The project name usually consists of a number and a name, and is reported in the unitinfo.txt file like this:

Current Work Unit
-----------------
Name: p2124_lambda_5way_melt_4_10011
Download time: January 2 01:45:46
Due time: April 22 01:45:46
Progress: 93%  [|||||||||_]

Instead, for the new SMP WUs, only the name is being reported-- and often isn't even matching the official entry.

Current Work Unit 
----------------- 
Name: SMP-nsv-03 
Tag: - 
Download time: January 8 19:43:05 
Due time: January 10 19:43:05 
Progress: 88% [||||||||__]

In this particular case, the name matches three different entries, with two different point values.

[Egon]

A FAHMonitor/SMP update:

I've put in a work-around to help deal with the bug in the SMP client (or projects).

If you give me the WU number from your FAHLog.txt files, I can update the projects/history on the fly now.

Of course, in looking at the FAHMonitor history and server records to date, I'm talking to a group of one: me!

[texas booster]

http://forum.folding-community.org/viewtopic.php?t=17551&highlight=

Here is a request from the folding forums for a Linux SMP monitor.

Might be fun to read about someone elses' travails for a bit.