Oh noes, link to fahwatch is "The page cannot be found". Where can I downloads it again to check it.
Printable View
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.