*Beta* Want to check your EUE rate?

[Marvin_The_Martian]

Back on request, but not longer actively 'developed'. fahWatch will be integrated in a client installer/monitor/manager ( which is finished but not public yet ).
Updated version 1.0.0.9

Publish page -> http://www.mtm78.nl/fahwatch/publish.htm Uninstall using add remove programs. Same binary just a publish page deployment ( if you want a zipped exe I'll ad that later ).

Before uninstalling, enter options and press 'Clear application data' to clear registry stored settings.

The attachment should give a good insight in what it does, I'll just a short list of current features.

• Provides a run down of EUE rate.
• Pops on when a new EUE is found
• Has a project browser hidden in the options screen.
• Preliminary values for Project time's which are non eue and run from 1 to 100 percent ( displays more but this I will use for some graphs so you can compare clients/project that way )
• Gives an easy to use interface to look up specific clients or projects.
• Outputs core status information and a log snippet for easy reporting of problems.
• Gives a rundown of hardware information and some environment values for local clients.
• Checks service status for local smp clients and checks the correct configuration of either Deino or Mpich.
• Local gpu clients is presented with data about you driver and gpu *awaiting confirmation it works now without assigning a local gpu to networked gpu clients.
• Can hide in the system tray, animated icon during timer based updates.
• Options include threshold value for showing the main form, showing a balloon tip after an update, let the application start in the system tray and the update interval.
• Debug messages can be seen by pressing the debug button in the options screen.

To do list

• Fix any bugs you may find!
• Integrate in maxFAH

Changelog *I'm not keeping track of everything sorry

• Bug fixes incl. Value out of range for the options screen ( FIXED! ) / Switching parsing method for log snippets ( FIXED ).
• Projects.xml now properly stored under %appdata%\fahwatch instead of %appdata%
• Clean application data now sets a value indicating subsequent option changes should not be saved
• Added debug output for the hardwareinfo class as it throws errors when running on an athlon xp and I can't duplicate that so I need the output
• Minor code changes

[catawalks]

Nice work. I'll take it for a spin when I get home.

[MikeB12]

I must be doing something wrong... I'm on Vista64, this is what I tried...

edit: fixed see Marvin's reply below....

[Shadowtester]

Nice Job Marvin but no Linux version Had to yank your chain some

[road-runner]

Works on Vista Business 64...

[MikeB12]

how did you get it to work RR? just a basic install procedure...

[road-runner]

I just ran the exe from the desktop and it found everything after about 30 seconds...

[Marvin_The_Martian]

No Mike it's my fault sorry

Notice your slashes in the file path of clientstab? Those are supposed to be the other way around. Your FAHmon is outdated

Latest version of FAHmon stores the clientstab in the %appdata% folder which is where I try to look for it, since you never installed the new 2.3.3 your's isn't there and I actually even removed some code which changed the "/" to a 'proper' "\" so it really is my fault

Brb with an update for you

Edit: RR how many clients are you monitoring with fahmon? I was afraid it wouldn't work for the most of you as I need to debug the gpu enumeration but I'm a single gpu guy still

Edit2: Mike download again please, location is now .replace("/","\") ( isn't basic such a wonderfull language, if you know some english you come a long way )

[MikeB12]

I can update to fahmon 2.3.3, no biggie.. that's an easy fix..

[Marvin_The_Martian]

No I mean dl my file again. fahMON has that refresh problem remember. And it will just ask for the location each time you start it. ( I'll edit the location if not in appdate then the path will be stored in the settings.txt file as well )

I'm pretty quick with making small changes, it's not that much code atm

[Sparky]

Cool app, I can see this coming in handy. Will give it a go when I have some time back at my PC. This afternoon perhaps or tomorrow evening.

[sc00p]

Good job, again, Marvin.

*thinking about relaunching folding machines before Christmas (this year) and with a newer box... might as well try this app*

[MikeB12]

I needed to upgrade fahmon anyway... I've been hanging onto 2.31 forever. and 2.32b was a disappointment.. but 2.33 doesn't seem too bad..
now that you mentioned the client.txt format though, I think part of my problem with 2.32b is I used an old client.txt file from my previous installs/backups.
this time with 2.33 I let fahmon create a new clienttab.txt and just reinput all the pc's by typing them in as new client adds, instead of using the old client txt file..

fahwatch immediately reads everything and it looks accurate..
but I get a message when it launches or when I click update..
is this something I need to fix...

[Marvin_The_Martian]

@Mike

That's the multi gpu enumeration issue I could disable that code section for now untill I fix it, but it will mean the gpu info presented in your text field will not be accurate or not valid at all

When you press ok, does the text area get filled with the right amount of projects? I think that was the known issue, after this error the loop get's exited and you're left with either an empty screen if the first clients in clientstab.txt is a gpu client with the -gpu x flag, or with a partially filled area broken off at the first wu from a client with that flag???

@Sparky and in general:

The more the merrier, though I would urge people to realise the existing bugs I mentioned in the first post. If you have any v5 clients you monitor in fahmon, the application will break. It will not exit, not display a message as it will exit a loop with an error I'm not going to handle as the code will be updated soon to handle the older cores output. Also like I said I was surprised RR got it running as I know ( iirc ) that he has multi gpu boxes and during testing on the folding forums I got reports that it breaks for people with that setup. And I can't test locally yet, so I assumed they were correct, even saw the output indeed being broken and I thought I found the flaw. I also thought I fixed it but I was not sure.

I'm open to all impressions, thoughts and remarks btw. This was concieved as an easy way to report problems to Stanford for beta testers, I thought it would come in handy for everyone though as it might give you an insight in how stable your client really is or isn't. I got screenshots from a few days back where I had a close to 70% eue rate for example

I'm also thinking about setting up a web front end to enable collecting data from voluentiers who will select to allow that. I think most off you feel it's to much trouble to keep a close watch on your eue's/logfiles for any problems and with a select, not to large and not to small group of people allowing me to collect this data, I might be able to spot things going wrong and present a detailed report to Stanford, or just give them the url of the front end which will show the current eue rate and the log snippets ( no user identifiable information will ever be collected, the windows information presented at the top of the textbox was asked for when this application was 'born' on the folding forums ).

I explained today or yesterday already how important our bug reports are for them, and as I am not smart enough to help them directly I saw this as an opportunity to maybe indirectly with the help of you all help them in a way other then only folding their work units.

Sorry for the emo

[road-runner]

I am monitoring 22 clients at the moment...

[Sparky]

*thinking about relaunching folding machines before Christmas (this year) and with a newer box... might as well try this app*

Do it

[Marvin_The_Martian]

I am monitoring 22 clients at the moment...

You're not getting the error Mike shown? Then I guess the system you're running on has only one gpu?

[Marvin_The_Martian]

*thinking about relaunching folding machines before Christmas (this year) and with a newer box... might as well try this app*

Uhm what? I can't hear you Listen to Sparky, if you don't he might enforce some shock theraphy on you

[road-runner]

You're not getting the error Mike shown? Then I guess the system you're running on has only one gpu?

No it has 2 and no errors here...

[SnW]

Hey Marvin the F@H software man

[MikeB12]

@Mike

That's the multi gpu enumeration issue I could disable that code section for now untill I fix it, but it will mean the gpu info presented in your text field will not be accurate or not valid at all

When you press ok, does the text area get filled with the right amount of projects? I think that was the known issue, after this error the loop get's exited and you're left with either an empty screen if the first clients in clientstab.txt is a gpu client with the -gpu x flag, or with a partially filled area broken off at the first wu from a client with that flag???

I'm running console clients with no flags.. they're all single gpu's in 4 different pc's as console clients (sig). but once I click ok to the message it looks like it's running fine... but I think you're right it's only reading my smp units, because that's all that show's in the big windows text.. I switched to console clients a couple weeks back just for grins.... I'm guessing that's what my issue is here.. but the smp info is nice... I've been meaning to switch back to systray clients, just haven't gotten around to messing with all the pc's... I'll test that in a minute and see if it was the console clients causing it... and post back.

[Marvin_The_Martian]

Lol Ray well this one seems to run abit better then last attempt

You're free to download and try, it's not team locked (yet) though this version has an expiration date to keep bug reports in the future to complain about old versions.

I actually have finished that installer I always wanted to make but I still haven't gotten official permission for it. As in Vijah told me they needed to have an internal discussion before changing the one thing I would like them to, allowing me to programaticly without user interaction setup of the smp and gpu clients

I got most of my old parsing code still as well, but I need to put that in this app so I can deal with the v5 clients. Then I got some licensed software as a gift from a guy here, and that I plan to use to put up a website dedicated to fah

[road-runner]

I am running gpu console clients also....

[Marvin_The_Martian]

No it has 2 and no errors here...

This is allot of work. but I am afraid to accept it's fully working for some reason.



What I would like to ask is if you're willing to check the number of wu's listed for each client with the number of' corestatus =' appearences in your clients fahlog.txt and fahlog-prev.txt. Don't have to check each client, just pick a gpu and a smp from somewhere in the middle of the list?

[Marvin_The_Martian]

I'm running console clients with no flags.. they're all single gpu's in 4 different pc's as console clients (sig). but once I click ok to the message it looks like it's running fine... but I think you're right it's only reading my smp units, because that's all that show's in the big windows text.. I switched to console clients a couple weeks back just for grins.... I'm guessing that's what my issue is here.. but the smp info is nice... I've been meaning to switch back to systray clients, just haven't gotten around to messing with all the pc's... I'll test that in a minute and see if it was the console clients causing it... and post back.

RR also runs console's it should not matter. The only issue I think it could be is a flag which get's read wrongly. Remember it parses the whole log so when you change machine config the old logfile entries will have factual incorrect information. ( need to add that to 'todo' list asap ).

What happens when you select a gpu client from the most left combo box and uncheck 'only eue'??

I'm looking at the code now, but I can't find what goes wrong

I'm waiting on the mailman