sounds great. Keep up the good work. I like that alerts option since I have a few network clients that are down myself.
Printable View
sounds great. Keep up the good work. I like that alerts option since I have a few network clients that are down myself.
I think the windows update yesterday fubbared this app.. I tried it this morning and all I get is a quick flash and it shuts down..
so I updated to the latest here just now and same thing. all it does is flash the window for a microsecond and close.
Ow uhm.. that's not a fluke, I had the expiration date set to 11-11-08, only one with a working copy atm is WFO I think :sofa:
Reason: wanted to make sure people would update to the latest version, and I been just to stressed due to people making 'mistakes' which cause me to be unable to pay bills or buy food for the kid. It's not that bad, I got my money just today ( 9 weeks to late though :mad: ) and we weren't starving or close to being in real trouble, just had some bills bounce because of the debit limit, and well the only bday gift I threated myself on is still not in :( but even that's a luxery compared to what I know some other people have to live with.
I got a problem with finishing things I start with :horse: but the changes I made were pretty simple and I could just the version wfo also has online, but half the extra options don't work ( haven't been tested to say the least ). It's not the windowsupdates, I should have it put up an "expired" message but I just let it check and exit sorry for that.
Brb :)
edit: done uploaded the intermediate build but did not change version info. If it works as it should it will pop up on new found eue's ( tbh I forgot to have it running as well, so the 2 eue's it picks up in my logs now were never detected as new during runtime.. so I haven't confirmed it works but uhm.. it should :sofa:
Just figuring out what to do now, have it generate charts itself (bitmaps.. making charts isn't that hard I can save the content of a form as a picture ).
And I just noticed that due to the 3 updates the program missed during the night my 'totalpointsincontest' are off as well ( yeah I know, calculate it from new 'total points' minus 'total points at contest start' instead off adding up each update to get the number, that's an alternative way ).
But the way I had the download function work is the reason it chocked during the night, changed it to be allot more forgiving and keeping the application responsive.. but that means the download and subsequent processing takes close to 15 minutes or so :poke:
I wonder how quick the back end of eoc processes an entire update, and then to think I only do the donor list not the teams list ( thoug.. donor list is 25mb of text.. team list is a couple off hundred kb afaik ).
I can take 25% of the parsing time needed to process the statistics but that means the application will show up as 'hung' or not responsive during the parsing and I want to prevent that.
Just to be clear, it processes the entire donor list and fillters out xs members, saves them to a seperate datapoints text file for each update ( each datapoint is about 13kb, so it won't fill up that quick and I haven't thought about implementing a limit but I can in the future, just need time ( and not go around work on this and then on something else lol ).
You like Mike? It's ment to help you, I won't give this to everyone as it's get's the 25mb list from their servers each update, think if every xs member would have it the strain would be to high. It's abit like a stats generator, but then really focused on our contests.
Nice work Marvin. That looks amazing. What do the charts look like that it generates?
yay! We have a new scorekeep volunteer. :up: :clap:
that's nice, work on it for the next comp and showcase it... I've done these last 2 races manually, so that would be an excellent tool to use on the next one... and who better to utilize it than the man himself. :up: we need some new volunteer blood on the field as refs..
No I don't think you want me to do it, I'm abit unreliable :horse:
You see Team Tracker, but the assembly name is 'Mike Helper' :poke:
catawalks it currently just gives numbers.. not charts. Trying to work out wether to do charts using a form and dynamic controls on them or by using a 3rd party rapport generator :sofa:
What do you think :idea:
Edit: btw idk if you noticed but the server binary for fahwatch was updated after you reminded me about it.
Edit2: Another option is to generate an html page on each update and upload that to my server, then I could run it after a contest is set up (need to define teams and members & start date) and it would run unattended. Problem is I got a bandwidth limit on my isp's webspace and their monitor doesn't work so it's impossible to check how much bw is used :down:
Updated fahWATCH, now reliable pops up on new eue's. Still not working with the own clients list hat some bug which bugged me and I didn't want to mess with it now. So that's still disabeld, as is the export and 'send repport' option ( which will be included in a future version which will have an installer included since I use a 3rd party zip lib. )
Working on the stats keeper is more interesting atm, also hit a bug.. somehow my contest members during an update now include every fah donor listed.. easy fix but I was wondering why it took so long to fill a listbox with team members :rofl:
just dl'ed the new ver..
got new prob...
On launch I get this error..
http://img224.imageshack.us/img224/9758/44639443df5.jpg
full text of the error:
Code:See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.FormatException: String was not recognized as a valid DateTime.
at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
at g.c(Object A_0, EventArgs A_1)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
FAHwatch
Assembly Version: 1.0.0.7
Win32 Version: 1.0.0.7
CodeBase: file:///D:/Software/Folding/fahwatch/fahwatch.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
so I click continue and get here, but it's not reading anything.
http://img262.imageshack.us/img262/1742/24882567ov9.jpg
30-12-08 isn't really a valid date there... I knew that but still, I also knew I had to use an unc time and convert the local date to that but I didn't.
Should not error now. <- means server has updated binary :)
I PWN EUE !
If I had more clients my percentage.. naw ok I'm trying to feel less bad hehe. 3 from 27 here, two on the 9600gt and a smp wu failed. That's not counting the vm on the other rig, which I don't have acces to anyway.
Mike play around with it, besides the unabeld features I think it's abit as it should be, I mean it should be stable and do as advertised without strange issues.
Edit: nope 2 from 27 not 3. Still high though, especially after reading how each eue is for the singularity of the gpu wu's. ( which I already knew though but needed a reminder ).
Jezus am I psychic.. it eue'd just the second after I posted.. well ok not exactly but still :rofl:
Frsshly downloaded wu btw, not a checkpoint to resume from :shrug: It got the same prcg again and it picked it up as it should now. Strange ( and reported :up: ).Code:-FAHMON NAME: 9600GT
INDEX: 1
LOCATION: C:\Program Files (x86)\Electronic Arts\
LOCAL CLIENT: True
CLIENT: Windows GPU Console Edition - Folding@Home Client Version 6.20r1
FLAGS: -forceasm -verbosity 9
CORE: Folding@Home GPU Core - Beta - Version 1.19 (Mon Nov 3 09:34:13 PST 2008)
StartTime: 21:09:30
StartPercentage: 35
EndTime: 21:09:31
EndPercentage: 35
-VIDEO CARD
Caption NVIDIA GeForce 9600 GT
Description NVIDIA GeForce 9600 GT
AdapterRam 512MB
DriverVersion 7.15.11.7784
DriverDate 20080806232600.000000-000
Index 0
InfSection nv_G9x_HD
COMPILER: Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
BUILDHOST: amoeba
BOARD: Nvidia
PROJECT: Project: 5506 (Run 0, Clone 169, Gen 310)
CORESTATUS: CoreStatus = 7A (122)
TIMESTAMP: [21:09:34]
[21:09:18] Version 1.19 (Mon Nov 3 09:34:13 PST 2008)
[21:09:18]
[21:09:18] Compiler : Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 14.00.50727.762 for 80x86
[21:09:18] Build host: amoeba
[21:09:18] Board Type: Nvidia
[21:09:18] Core :
[21:09:18] Preparing to commence simulation
[21:09:18] - Assembly optimizations manually forced on.
[21:09:18] - Not checking prior termination.
[21:09:19] - Expanded 45485 -> 246249 (decompressed 541.3 percent)
[21:09:19] Called DecompressByteArray: compressed_data_size=45485 data_size=246249, decompressed_data_size=246249 diff=0
[21:09:19] - Digital signature verified
[21:09:19]
[21:09:19] Project: 5506 (Run 0, Clone 169, Gen 310)
[21:09:19]
[21:09:19] Assembly optimizations on if available.
[21:09:19] Entering M.D.
[21:09:24] Will resume from checkpoint file
[21:09:27] Working on p5506_supervillin_e1
[21:09:30] Client config found, loading data.
[21:09:30] Resuming from checkpoint
[21:09:30] Starting GUI Server
[21:09:31] Verified work/wudata_08.log
[21:09:31] Verified work/wudata_08.edr
[21:09:31] Verified work/wudata_08.xtc
[21:09:31] Completed 35%
[21:09:31] mdrun_gpu returned
[21:09:31] Calculated & specified T inconsisitent
[21:09:31]
[21:09:31] Folding@home Core Shutdown: UNSTABLE_MACHINE
[21:09:34] CoreStatus = 7A (122)
Team tracker is fully working ( eg, no missed updates and I got the memory usage down to 300mb at peak ( with 112xxxx donors updates all in memory, before I sort it. Talking about working backwards.. think I did that so I could generate more graphs as well but it's not really needed ). Think I'm going to put it on the gf's rig after I upgraded her ram. Got some initial results with that chart lib as well, it's allot easier then I thought :yepp:
What files does this thing use in fahmon? After usong fahwatch once and closing it then trying open it again a few minutes later it hung and now fahmon is borked it seems, I have rebooted 4 times trying to get my network straitened out, is there something I can delete?
Edit: Nevermind, looks like my router, modem and switches needed another power cycling after the power outage last night... http://www.xtremesystems.org/forums/...EMOTICON13.gif
Lol I only read that text file for clients name and location I don't write to anything involving fahmon. Every file I create is located in appdata\fahwatch\
I just noticed I made a lil oops on the update, as it pops out of the tray every update and not only when a new eue is found :horse: brb :)
Great work Marvin - the tool is now running fine across all clients.
I did find a defect, however. When I clicked "options", there was an exception generated:
Code:See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '0' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at g.d(Object A_0, EventArgs A_1)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
FAHwatch
Assembly Version: 1.0.0.7
Win32 Version: 1.0.0.7
CodeBase: file:///C:/Documents%20and%20Settings/Mike/My%20Documents/fahwatch.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.ServiceProcess
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------
1.0.0.8 up. minor changes ( mostly small bug fixes ).
Coo-coo-clocker thanks for the bugreport I know what caused it and it's now fixed. And I added proper error handling to that sub :sofa:
down to 3% eue
I'm down to 6% of 2264. I hit a high of 13% when G0-3 was acting up. :rolleyes: Fahmon still wants a 100% of 1 core on my quad so I won't be running this the way I would like to for a while. :(
LOL...FahWatch just alerted on an outdated core. I still had a 1.15 on one of my 9600GSO. Oh noes further points reductions starting now.:(
uh oh. 1.0.0.8 when I pressed on the options button:
Code:See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '0' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at g.d(Object A_0, EventArgs A_1)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
FAHwatch
Assembly Version: 1.0.0.8
Win32 Version: 1.0.0.8
CodeBase: file:///C:/Users/Administrator/Downloads/fahwatch.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.ServiceProcess
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
See coo-coo-clockers post on page 2, it's fixed if you download again. Sorry for not updating build number :)Quote:
Originally Posted by catawalks
I downloaded from the link on the first page and get a FAHwatch has encountered a problem and needs to close error. Is there another client I should be getting or is it the current one? XP32
Marvin, I got that error when I ran the one from the first page yesterday. I posted like 3 minutes after downloading and running it last night.
Nope should be good. You haven't downloaded/ran this before? If you did, try deleting the folder %application data%\fahWatch as that might cause an error, even if I thought I cleanly handeld any settings not being in the file.Quote:
Originally Posted by MaK2000
Yeah but I updated it seconds after coo-coo-clocker posted, I had an initial value set to 0 for a property which is teid to a numeric up and down control with a min value off 1. That property is now always 1 if there is no settings file, so either you have a bad settings file and you need to do delete it and start new, or you need to post more data because atm I don't know what's exactly happening :(Quote:
Originally Posted by catawalks
Working on a stats page for xs now to, and a signature generator, have to admit I should concentrate on fahwatch first that's something which could be usefull I think more so then the other things :)
Thanks for the raports both :up: Keep em coming :yepp:
Oh noes, link to fahwatch is "The page cannot be found". Where can I downloads it again to check it.
Got some server problems, I'll upload it later today again.
Server up again, version still 1.0.0.8 as no changes needed to be made. That error does not happen ( and infact it can not happen anymore but that was already uploaded before catawalks reported his rapport :shrug: I know, update those build numbers on every change and it's easier to spot )
I just downloaded right now and got the same error....
That's a new messagebox though :yepp: Looks pretty nice, must be the jit debugger as it's not something I created :confused:
Hope the settings file will work for you, or I'm out of options. I just ran it on the missus pc which is xp32 pro and didn't have a problem there.
Still getting that error. So what about the settings file should I be looking at?
http://i71.photobucket.com/albums/i1...watcherror.jpgCode:See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentOutOfRangeException: Value of '0' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at g.d(Object A_0, EventArgs A_1)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
FAHwatch
Assembly Version: 1.0.0.8
Win32 Version: 1.0.0.8
CodeBase: file:///C:/Users/Administrator/Downloads/fahwatch.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
System.ServiceProcess
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.ServiceProcess/2.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
1.0.0.9 ( with a catch all error handling/preventing in place for the option screen :sofa: )
This is ran before the screen is shown wether it's a first run detection or when you press the options button in the menu. ;)Code:If AlertRate < frmOpt.nudAllert.Minimum Then
AlertRate = frmOpt.nudAllert.Minimum
ElseIf AlertRate > frmOpt.nudAllert.Maximum Then
AlertRate = frmOpt.nudAllert.Maximum
ElseIf UpdateInterval < frmOpt.nudUpdate.Minimum Then
UpdateInterval = frmOpt.nudUpdate.Minimum
ElseIf UpdateInterval > frmOpt.nudUpdate.Maximum Then
UpdateInterval = frmOpt.nudUpdate.Maximum
ElseIf LinesBefore < frmOpt.nudBefore.Minimum Then
LinesBefore = frmOpt.nudBefore.Minimum
ElseIf LinesBefore > frmOpt.nudBefore.Maximum Then
LinesBefore = frmOpt.nudBefore.Maximum
ElseIf LinesAfter < frmOpt.nudAfter.Minimum Then
LinesAfter = frmOpt.nudAfter.Minimum
ElseIf LinesAfter > frmOpt.nudAllert.Maximum Then
LinesAfter = frmOpt.nudAfter.Maximum
End If
frmOpt.chkNewEUE.Checked = AllertEUE
frmOpt.nudUpdate.Value = UpdateInterval
frmOpt.chkBalloon.Checked = ShowBalloon
frmOpt.chkTray.Checked = StartInTray
frmOpt.chkBeforeAfter.Checked = boolUseBeforeAfter
frmOpt.nudAllert.Value = AlertRate
frmOpt.nudBefore.Value = LinesBefore
frmOpt.nudAfter.Value = LinesAfter
frmOpt.ShowDialog()
and where would I find said 1.0.0.9?
same url, I update the binaries each time.
edit: www.mtm78.nl/fahwatch/fahwatch.exe
Btw, if you're experiencing slow start ups it's because the project browser checks at startup for new projects and the tray icon is created afterwards not before. I really should change that because I'm running mj12 and my connection is abit bogged down so it takes 30s to show the icon in the tray :sofa:
ok, just redownloaded. Still says 1.0.0.8 in the top corner. Still getting the same problem too.
think there a caching issue going on here. I'll create a seperate url for this time :)
Awesome, works perfectly now. Thanks.
Phhheww *wipes sweat of forehead*
down to a 2% eue rate
:eek:
Maybe ver 1.1xx will have a special Mike Award for people who get at or below 1% :up:
there's no gpu eue's in those 295, just smp's... I think it's up to luck of the draw now on pulling all good wu's that aren't flawed... which may a bit like winning the lottery in PG terms.. :(
I'd love to see 1% or lower, but not too hopeful... seems a bad wu sneaks in before that happens... if QC was a little better on producing wu's, it might happen more often, but 2-5% is better than the 10-15% I used to see..
It's not QC, the nature of the project actually makes it inevitable that some wu's fail. If they could predict which wu's would eue they would probably be able to predict which one's will generate a transitional state as well :poke: ;)
what's a transitional state ?
The thing we're looking for with folding wu's.
There is a nice thread at the folding forums about it ( yes.. I posted in it :sofa: )
First read this http://fahwiki.net/index.php/Runs,_Clones_and_Gens
Then my amendment http://foldingforum.org/viewtopic.ph...&t=7104#p70414
The wiki link is summarised in the amendment, and most of the reference is actually taken from Dan's statement which you already read.
thanks. I was just confused by the term "transitional state" you're using... the wiki you linked never uses it.
and a fahforum search only turns up 2 hits:
totow is using it in reference to system cooling.
'transitional state"
http://foldingforum.org/search.php?k...&submit=Search
and your post
"transitional states"
http://foldingforum.org/search.php?k...&submit=Search
anyway I was just confused about what you were saying...
if they could predict eue's, then they could predict transitional states...
I'm still a little confused about what a transitional state is, but suffice to say in laymens terms I guess it means they would be able to predict the results and wouldn't need simulations to begin with. at least that's what I can grasp from it... but I'm not into the technical details of how wu's are produced or how they run and code these simulations... nor do I want to be.. so I'll just simplify the statement for my brain. I still wish they could eliminate bad wu's, that would be something everyone would enjoy. but I guess some have bugs in them, so we just accept it as normal business...
Wiki does list it.
edit: btw maybe import diffrence but didn't I say ' if they.. then they could probably also.. ' ??
You know how I been misquoted, think about my hearthrate lol :rotf: Big diffrence taking an asumption which even while probably true is not the same as something I state as absolute.
My post was summarizing wiki, dan's info and my interpretation on being able to make a distinction between uniprocessor wu's and the hpc wu's. Something I would like to inform allot of people about but they seem to not want to listen anyway as it 'attacks' their dc project as only f@h atm is able to take the new approach enabling the former mentioned distinction :soap:Quote:
But the path which connects "unfolded" protein with folded protein is not so easy to get to -- but if we identify the transition state, then we've found (at least one of) the paths by which proteins fold, and that's research in protein folding.
Meh, I gave up already.
ah, I see it. I was searching for "transitional" like in your comment, not "transition" like in the wiki.
LOL
you know what I hear when I read all that stuff?
"blah, blah, protein, bada, bada, folding, ding, ding, biology, blah, blah, science, blahhhh, zzzzzzzzzzz.... click" :rofl:
Come on.. you're trying to make me say you should be capable of understanding allot more about it.. or are you trying to show me how most people think.. Had a talk with a person on the folding forum about that article I been working on, got a comment back on it which I think says it all.. do not fuel the flames.
It's just that I don't think that's the whole truth :) The stance taken is historically proven to be true, but people learn from history ( well... ok maybe not :horse: )
You know all this stuff, getting the sql server up and tracking ( it's up now, no more text files just nice sql tables ) and the installer I took a new look at ( going to finish that tomorrow, well maybe not fix the bugs but include the traycontroller hehe ) and the eue parser of which I want to add autoreport functions ( damn isp without proper support :poke: ) ect, it all is pretty exhausting when I also got to care for my son on most days full time and now the dog as well.
I should just drop everything and do one thing which is the most important :up: Kid :oscar: :rofl:
I've just narrowed my interest in folding to running gpu and smp clients, cranking out wu's... and having fun here at xs...
so if it's ouside that realm, i've lost focus and attention in comprehending it.
I rarely read the fah forum anymore, and haven't run a beta flag machine in months.
as long as I can run the clients I guess I've been reduced to not caring about PG junk.
only reason I posted in this thread today was to show off my 2% eue rate a couple posts up above,
and bump the thread. it was falling down the totem pole "last post 11/19", 6 days ago.
Doens't need to stay, only reason I made this is because I said I could and xilikon seemed to like the idea of having something like this. Though I should also finish the export function or save the eue data in a local dbase so I can generate statistics based the collected data ( that's the most usefull thing besides being allerted on new eue's ).
Could make somehting to track clients progress like fahmon, could add it to fahwatch but it would take time and effort and why try to reinvent the wheel? Think the stats page for xs is a much more usefull thing to spend time on, having nice charts and ability to follow the races on a webpage ( with an iframe containing the folding forum :rotf: ) might get us some more active participants :)
Sparky is also right though, having a tested and confirmed working installer on every possible system would also be real handy. I just test on what I got and it works, got some ideas to improve the detection ect but I need to make lists of NOT supported ati cards for that ( nvidia is allot easier as using the inf section is enough when every g80 and up is folding capable, should only add the quadro inf sections as well ).
I just ran this for the first time since the race. My EUE rate is currently 7%. :eek: 65/918. Atone point my EUE rate was 13%.
I've restored fahWatch on a temporary basis. It will eventually be integrated in my installer/monitor/manager project.
Url is the same as before, and the notes still apply. Does not export data/save data so no information other then current fahlog.txt and fahlog-prev.txt contain will be given. The version is still 1.0.0.9
Is it normal for it to not see clients on the network?
I have Fahmon, and Fahwatch see's the GPU and SMP client on my main rig, but not my bro's SMP client. (Both are VMware Linux clients).
Uhmm no it should read them all. I couldn't test though. I did test vm'd nf's and that worked iirc. WFO and MikeB12 have networked clients and reported it to work for them, I'm not sure what could cause what you're saying :(
Here's an image: (kinda big, so didn't use img tags)
http://i133.photobucket.com/albums/q...chproblems.jpg
Ok I see, yes clientstab can be edited by now and I haven't added any checks. Especially 'disabeld' clients will probably not be picked up. Enable them in fahmon and restart fahwatch? The other one's ( yellow ) I'm not sure I would need to see the clientstab file.
Ah, just had to close out of FahWatch, then open it again. Now it shows them.
This occurs when you have Fahwatch open, then start up a client (While FahMon is open).
fahMon has some tabs where it stores the client's state, fahwatch only watches green clients on default ( to prevent trying to read unavailable clients over and over ).