Error in new protein

[yellowfin]

The DF GUI keep displaying Foldtrajlite.lock found. And the folding takes hours take a long time to fold one generation.

I have check the error file in the folding folder. This is the error message display.

========================[ Oct 29, 2003 4:11 PM ]========================
Starting foldtrajlite built Oct 27 2003
Wed Oct 29 16:12:48 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

Should I redownload the new file.


PS. I am using the DF GUI 3.2 version. I have restarted the folding and the error file did not display the above message again.

[erk]

I am getting similar under linux:

Wed Oct 29 22:52:37 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

Wed Oct 29 23:50:41 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

Thu Oct 30 17:03:02 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

Thu Oct 30 17:03:38 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

Thu Oct 30 17:23:05 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates


This is happening on both overclocked and regular machines.

And I just found a FreeBSD box as well:

Thu Oct 30 08:16:41 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates


That make 5 machines this afternoon, and I just had another report of a windows machine with the same error. At least the problem is cross platform

Woops I just found the error on one of my MacOS X machines:

Thu Oct 30 11:13:32 2003 ERROR: [002.002] {buildit.c, line 256} Cannot set co-ordinates

That's it I have had enough, I have 50GHz of machines doing DF I am switching them off it until this code is fixed.

[rstarr]

I think alot of folks will switch their machines off until the DF Team does something about this new protein. It's killing our machines will errors and overheating, looping.

[Brian the Fist]

Please ignore the cannot set co-ordinates error. It is harmless and will be fixed shortly. As for the slowness, well, this is the first shot at a new algorithm, we need to see how well it does and then adjust accordingly. Please do not go around accusing our software of overheating your machine though, that's
:bs:

[Grumpy]

It is not overheating, just spending longer at the point that the previous Client worked its hardest, thus the cpu was a tad warmer at that point. As the new Client spends longer at this point, the result is the cpu gets a bit warmer. If you are not in air con and have an over clocked cpu, this then magnifies the warm period It just proves how hard the new Algorithm is working towards its goal