I've noticed that I'm still getting a fair number of hits on fahmon.fahinfo.org so just in case you haven't been keeping up to date with the official FahMon development, here's what happening:

I have taken over official maintenance of FahMon from Francois (athropos_666), and as such I've release FahMon 2.2.0 which includes all the fixes I implemented in the unofficial versions. This means that all the unofficial versions are unsupported, and you should install the latest official build of FahMon from http://fahmon.silent-blade.org

]]>

In this release we have some more bug fixes and some added features by request

Bugs fixed

• Fixed bug which caused fahmon to crash when a FAHlog.txt without a Project identifier was loaded.
• Fixed "bug" in the way PPD was grabbed from the benchmarks manager. It is now managed as part of the client class.

Features added

• Sort by PPD now works, thanks to the above fix to PPD management
• PPD is now not show for stopped clients, which means total PPD now only includes clients which are active or inactive, but not stopped or "dead".
• The state of a client has now been added to it's own column, which allows sorting by client state.
• As a partner to the above feature, a new option has been added to the General Preferences page that allows you to choose whether inaccessible clients are always shown last in the client list (this is the default behaviour). Disabling this may be useful for people monitoring large numbers of clients.

Download (Windows): fahmon_2.1.5b.6.zip

Download (Linux): fahmon_2.1.5b.6.tbz2

]]>

Since for the moment psummary isn't displaying data for SMP WUs, I've created a mini psummary that will allow you to update fahmon's internal project database with Win SMP WUs and allow you to monitor them correctly.

• Download WinSMP.html from http://fahmon.fahinfo.org/WinSMP.html (Right click, save as. In IE change the filename to WinSMP.html as by default it will try and save as WinSMP.htm which will not work)
• Open up fahmon preferences and go to the advanced tab.
• Select the option to use a local file, and select the WinSMP.html file you just downloaded.
• Press OK
• Manually update the project list, by using "Download New Projects" from the FahMon menu. - This will then load the local WinSMP.html file and update the internal database with the Win SMP WUs.
• Go back to the fahmon preferences and deselect the local file option, this will ensure that any other projects are then updated correctly from psummary

]]>

OK, so you may be wondering how/why I got this release out so quickly. Well the answer is, I've just finished my last lecture of the year, and wanted to relax before I start revising for finals and writing reports and essays.

So without further ado, here's what new (cringe):

• Fixed a bug that causes fahmon not to update the Work Unit Information panel properly. See here. Thanks to RipD for the heads up on this one.
• Added a system tray menu which display some useful info, and lets you show/hide the client and open the benchmarks and preferences windows
  
• Added an option to the per-client right-click menu, to allow you to open the containing folder. On the menu this is called "View Client Files". Thanks to Bruce for this suggestion.
  

This last option also introduces a change to the Preferences Dialog. A new "System" page has been added, the Browser configuration has been moved from the General page to Settings, and renamed to Web Browser. In addition, to support the "View Client Files" feature, another option has been added to the System Page: File Manager.

This comes in the form of a dropdown list containing common file manager selections for Windows and Linux, depending on host OS, and also a manual command box for you to either edit the default commands, or enter new ones.

Choosing an unavailable file manager, or incorrect/invalid command will fail silently.

Download (Windows): fahmon_2.1.5b.5.zip

Download (Linux): fahmon_2.1.5b.5.tbz2

]]>

The problem: If a client you are monitoring is processing a project that happens to be missing from psummary, the Work Unit Information Panel isn't cleared. If you monitor multiple clients, switching to this "broken" client will leave all the information from the previous client in view, except for the project number. This happens if you have auto update projects enabled. The reason for this breakage, is that fahmon assumes that once the project database is updated it will then contain the data you need, and won't bother clearing it, it just waits for the information to be overwritten. Unfortunately there is no fallback procedure for when the updated database is still missing the data.

The solution: Reset all the data before updating the project list. This way everything gets set to N/A, and if the project info doesn't exist, it doesn't get overwritten.

mainDialog.diff

--- a/mainDialog.cpp	2007-02-01 00:02:29.000000000 +0000
+++ b/mainDialog.cpp	2007-03-16 13:16:04.000000000 +0000
@@ -377,6 +377,16 @@
     // This project can be unknown, if the database is not up to date
     if(project == NULL)
     {
+
+        // Fallback to reset all info in case psummary doesn't contain the data we need
+        // Otherwise bad things happen like the data remaining from the last client viewed
+
+        mProjectId->SetLabel(wxT("N/A"));
+        mCoreName->SetLabel(wxT("N/A"));
+        mCredit->SetLabel(wxT("N/A"));
+        mPreferredDeadline->SetLabel(wxT("N/A"));
+        mFinalDeadline->SetLabel(wxT("N/A"));
+
         // Update the database, if the user wants to
         // This update is not forced, it will occur only if the elapsed time since the last one is high enough
         // This way, we ensure that we won't perform many multiple requests for the file, while it does not

]]>

A few minor patches applied today over the existing ones present in 2.1.5b.3

The new patches add the ability to change the project data download source. It can either be set as a web resource, with the appropriate settings, or as a local file.

Using a local file as an update source can be useful in cases where data on psummary is incorrect, or simply missing. It allows users to alter the file to correct erroneous data, like p2604 listing only 2 frames when in fact there are 100, or add projects manually which for one reason or another are not present on psummary.

Using the advanced network settings

To contruct the url used to download new project data, fahmon does this:

http://$server:$port/$resource

Therefore with the default settings of:

• server = fah-web.stanford.edu
• port = 80
• resource = psummary.html

Note the lack of trailing and leading backslashes in the above.
The contructed url is:

http://fah-web.stanford.edu:80/psummary.html

If you wanted to alter the download settings to connect to:

http://www.foo.com:8080/bar/psummary.html

The settings would be:

• server = www.foo.com
• port = 8080
• resource = bar/psummary.html

Disabling the advanced settings causes fahmon to revert to its default internal values, which should always work.

This patch also fixes the regression introduced in 2.1.5b.1 which prevented fahmon from monitoring Tinker workunits.

Download (Windows): fahmon_2.1.5b.4.zip

Download (Linux): fahmon_2.1.5b.4.tbz2

]]>

A bug fix release

• Fixed a sloppy code issue introduced in 2.1.5b.1 which caused compilation failures with gcc > 4. Thanks to ck_wong of CustomPC and goober_dvd for the notification and fixes.
• Fixed an issue with the preferences dialog causing a segfault on pressing OK when compiled with gcc > 4. Thanks to ck_wong of CustomPC for the fix.

Download (Windows): fahmon_2.1.5b.3.zip

Download (Linux): fahmon_2.1.5b.3.tbz2

]]>

This new release fixes a longstanding bug present in the official version of fahmon (2.1.5). fahmon can now save its preferences when it is left in the system tray on logoff or shutdown in Windows or Linux.

Previously if you forgot to close fahmon before you shutdown of logged off, fahmon would just die silently and the preferences or benchmarks accumulated since it was started would be lost. Well no more, after looking around the wxwidgets docs and poking around their forums, I found out what was going wrong, and it's a really stupid problem with wxwidgets itself. It appears you need a special routine to handle logoff/shutdown events, otherwise they are never trapped. Once I knew this it was relatively simple to redirect these events to the current exit procedure and now everything saves and exits gracefully.

A bug that causes some client paths to be set to lines from FAHlog.txt should also be fixed in this release.

Download (Windows): fahmon_2.1.5b.2.zip

Download (Linux): fahmon_2.1.5b.2.tbz2

]]>

I've just patched up 2.1.5b.1 to correct the GPU eta problem.

The problem occured because the GPU FAHlog.txt doesn't enclose the frame markers in parentheses. A GPU FAHLog.txt looks like this:

[01:56:00] Completed 93
[02:04:01] Completed 94
[02:12:02] Completed 95
[02:20:02] Completed 96

Instead of like this (for a CPU or SMP log):

[20:34:15] Completed 3700000 out of 5000000 steps  (74%)
[20:49:15] Timered checkpoint triggered.
[20:52:20] Writing local files
[20:52:20] Completed 3750000 out of 5000000 steps  (75%)
[21:07:19] Timered checkpoint triggered.
[21:10:12] Writing local files
[21:10:12] Completed 3800000 out of 5000000 steps  (76%)

Now fahmon looks for (xx) first, then if it can't find a match it tries looking for the numbers on their own

Download (Windows): fahmon_2.1.5b.1.zip

Download (Linux): fahmon_2.1.5b.1.tbz2

]]>

fahmon is now capable of monitoring fully both SMP and GPU clients thanks to some major fixes I've just applied to 2.1.5b.

Basically I've removed the method for finding the project number by parsing unitinfo.txt and replaced it with an alternative method.

When looking for a project number, FahMon now backtracks up FAHlog.txt until it finds a

Project: xxx (Run xx, Clone xx, Gen xx)

line and simply grabs the project number from there.

This means that it won't work for tinker wus ("oh no" I hear you say ;) ), but it does mean that the project number can be accessed for all clients...and it works.
I've tested these builds on my SMP and GPU clients, and they work as expected. The only problem I can see, is that it can sometimes take a while to get the Project number if the log is quite long.

This patch alters the way xyz files are stored, so be careful. The official builds store the project name as obtained from unitinfo.txt, whereas the unofficial builds from 2.1.5b.1 store the file as simple the project number.

Apologies for the incorrect title on the screenshot below, I took it before I altered the build number.

Download (Windows): fahmon_2.1.5b.1.zip

Download (Linux): fahmon_2.1.5b.1.tbz2

]]>