Sorry. I skipped some details and I should never do that in this forum.Willyw wrote:ahhh... umm... I saw that term "ProtoMol" in the log, but that's all I know about it. By "core", what do you mean? ... is it the version of the Folding client that I'm running?
. . .
and the systray client.
There are two types of CLIENTS for Windows. One is called the Systray client and one is called the Console client. You can download either one. Once the client is running, it asks the server for a Work Unit. WUs are part of various Projects. Each Project uses a particular analysis method called a FahCore (or "core"). ProtoMol is one of those analysis methods, and it's also known by the name FahCore_b4.
That's a good question. As I implied earlier, there are a variety of analysis methods that may be required, depending on the particular project that your assigned WU comes from. Each of these analysis methods function as an extension of the client that you downloaded. From time to time there are new FahCores (analysis methods) and from time to time they're updated to extend their capabilities. The client downloads cores on demand, just like it downloads assignments (WUs) on demand. Normally this proceeds without a hitch and without any interaction with you. (Very rarely, the client is updated, and when it is, you have to download it yourself.)Here's a question for you:
Has something changed?
In other words, I've run this for a few months now. Almost daily, if not actually daily. No problems. Well... I think I saw it said a bad packet or something like that once, and that it was uploading early. It did, then it downloaded new stuff, and proceeded to continue perking right along. That was quite some time ago though.
This that I've reported, is new.
When something new happens, with something that has been working fine, logically one looks for what could have changed.
Why else would it work for so long, then quit working normally?
. . . so yes, something did change. Apparently you got a different core. Either that, or the WU that you were assigned exercised a rarely used portion of the core and you found a bug.
That's lots of information. You asked, and I don't mind explaining it -- or adding more detail if you missed part of it -- but you can fold without understanding it -- it isn't essential information. . . . . but you didn't ask a "Do this" kind of question.
That's cool.While I appreciate all the bits of info I've received here, and the poster's time in replying here, I really didn't want to take the time to really read all the info in some of those links for detail.
(Since I had changed nothing, I was kind of hoping it was something well known, with a simple "Do this:...." type of fix.)
As I skimmed around in the links provided, I saw that somebody mentioned to open Task Manager, with Folding running, and kill every instance of it. That this would cause it to d/l a new packet, etc.
So, I did that.
And, it did ... as best as I could tell from the log... start over again with a new packet.
This was yesterday.
Remember... it got stuck at 2% before... and yesterday it progressed on up to 20 something percent, before I had to go, and quit the program.
Today, I've started it again.
It seems to my untrained eye, to be running normally.
It is at 28% completed right now.
It seems that you are getting reports of this.... I hope with my blathering on in this post, that maybe I've said something that is useful to the powers that be, that are trying to solve it.
Unless you strongly recommend that I un-install the graphical client that I'm again using, and recommend that I then install the command line client - I'll go back to the way I've done it for so long... just click it, let it sit in the try all day running, and pretty much forget about it.
Again, thank you all for your time.
My hunch is that the bug you encountered is pretty rare so you probably won't run into it again. If you do, we'd be happy to give you a "Do this" sort of answer then, but even without asking, all that has been suggested is (A) Uninstall the systray client and (B) Install the Console client and you'll probably remember that if you ever need it.