PDA

View Full Version : protein198 NOVO PROTEIN in water??


Hawk
08-24-02, 01:06 AM
I am getting a negitive progress when this protein comes up on one of my boxes I dumped the last one but don't really want to do that. Here is a screen shot attached. Whats the skinny on this one?
:confused:
Thanks

hooziewhatsit
08-24-02, 01:09 AM
hmm, I would think that it's a problem with EMIII. does your fahlog show anything strange?

NASsoccer
08-24-02, 01:10 AM
Originally posted by hawk646
I am getting a negitive progress when this protein comes up on one of my boxes I dumped the last one but don't really want to do that. Here is a screen shot attached. Whats the skinny on this one?
:confused:
Thanks

what version of em3 are you running? and what does it say in the log files? does it say that any errors have occured?

FOLD ON
NAS

Hawk
08-24-02, 01:38 AM
Im sorry for the ignorance but I don't know how to find the version info nor do I know where the "log" files are. Would ya mind giving me a little help?
Thanks

Arkaine23
08-24-02, 01:42 AM
No problem!!

www.em-dc.com

Download the 1.94 upgrade for EM3 and close EM3 out, then extract the files into the same directory that your current EM3 is in an overwrite them.


Wherever you installed folding@home, there is a file called fahlog. Its a text file and will open with notepad. Open it and scroll down to the bottom. Copy/paste some of the text and post it for us to examine.

Hawk
08-24-02, 01:53 AM
The updated files for EMIII seemed to do the trick.
Here is the log text any how.


# Windows Console Edition ################################################## ###
################################################## #############################

Folding@Home Client Version 2.19



Benchmarking ...
- Ask before connecting: No
- ID = A11640556191829

Loaded queue successfully.

+ Processing work unit
Core required: Core_78.exe (found)

[August 24 05:42:10] Working on Unit 00
+ Working ...
[05:42:10] Folding@Home Client Core Version 1.25 (August 19, 2002)
[05:42:10]
[05:42:10] Proj: work/wudata_00
[05:42:10] No information on assembly optimizations.
[05:42:10] Previous termination of core was improper.
[05:42:10] Will try without optimized assembly.
[05:42:10] Files status OK
[05:42:11] Writing local files:
[05:42:11] Entering M.D.
[05:42:17] arc file found...
[05:42:17] ... and we'll restart from it.
[05:42:17] Protein: DE NOVO PROTEIN in water
[05:42:18] Writing local files
[05:42:18] Completed 498000 out of 1200000 steps (41%)
[05:54:14] Writing local files
[05:54:14] Completed 504000 out of 1200000 steps (42%)
[06:18:02] Writing local files
[06:18:02] Completed 516000 out of 1200000 steps (43%)
[06:41:51] Writing local files
[06:41:51] Completed 528000 out of 1200000 steps (44%)
Thanks you guys are great! Glad I found these forums.:D

Arkaine23
08-24-02, 01:54 AM
Glad that fixed it. Anytime there's new proteins, Weatherman makes new code for EM3... its a good idea to look for updates every couple of weeks.

Hawk
08-24-02, 01:59 AM
Thx dude!

looktall
08-24-02, 02:21 AM
Originally posted by Arkaine23
Glad that fixed it. Anytime there's new proteins, Weatherman makes new code for EM3... its a good idea to look for updates every couple of weeks.

heh. i've started checking every few days because he does so many updates. :D
(which is great btw.)

which reminds me.....
/me heads of to em-dc.com

Hawk
08-24-02, 02:27 AM
Glad it's fixed this is a 5 pointer. Too bad I dumped the last one I got. Guess I should have asked earlier huh.
Fold on!

muddocktor
08-24-02, 08:46 AM
I want you guys to be aware that the fix that Stanford was suppoesd implement into the new FAHcore_78 didn't work on the 2 K6 rigs I still have folding for team 32. The following is what happened and what I did to get around the problem with Gromacs work on the K6 rigs.

I was at my brother's house yesterday, networking the 2 K6 rigs together so they can both fold and installed the version 3.11 console on both of them. The first WU the K6-3+ rig got was a Gromacs WU and after downloading the latest core, it was dumping the WU after 30 secs to 5 minutes for instability. This was the same problem that Stanford was having with K6 rigs the last time Gromacs was deployed. They were supposed to modify the core so that a rig turned in 2(I think) consecutive dumped WU's due to instability, then it was supposed to disable the SSE and 3DNow instructions. It seems that the older 3DNow instructions in K6 have problems with Gromacs for some reason. Anyways, the new core didn't disable those instructions like it was supposed to and kept dumping WU's for 30 minutes or so until it finally got a Tinker WU and proceeded to fold normally. The workaround to this problem should be to download the beta 3.14(either gui or console) and use it, because you can manually shut off all optimizations with that client. I've done that but unfortunatley both rigs were working on Tinker WU's at the time so I don't know for sure that this will cure the problem with Gromacs and K6-x procs. I will be going back to his house again today and will check to see if they have gotten any new Gromacs work since yesterday. I've also posted this at the folding community to let pandegroup know that I had this problem.

On a lighter and cooler note, all those dumped WU's counted as points for me and Team 32.:eek: For about 30 minutes I had the fastest folding K6 (or any X86 computer for that matter) on the planet. EM3 reported that K6-3+ 's production rate at 3240 points per day!:eek: :cool: In all, it gave me a 120+ point production jump, so anyone seeing those points at statsman doesn't think that I suddenly have all the colleges in Louisiana folding for me or anything.:burn:

Anyway, Fold on!

rich99million
08-24-02, 08:55 AM
Hey muddocktor, could this help:

Hi,
We've posted beta clients (v. 3.14) for Windows and Linux at folding.stanford.edu/beta3 . It doesn't have all the things listed in the To Do list some of you have prepared (we'll get to that), but just the following:
- Configuration option added of disabling assembly optimizations in core (applicable only to Core_78).
- Bug fixed where if changed certain Configuration options, core saw as an improper shutdown.
- Send/autosend conflict resolved.
- If core outdated error arises for a work unit, and still remains after a new core has been downloaded, that work unit is deleted.

Thanks,
Guha

hope this solves the problem, and doesn't cause too many others,

Rich

muddocktor
08-24-02, 09:55 AM
Yeah, I now have beta 3.14 on both rigs, will go by my brother's house and see if they've gotten any Gromacs work since I put it on those 2 rigs. Also, EM3 had a problem reading those beta proggies so I just renamed the FAHconsole.exe, just like 3.11 is named and EM3 picks them up with no problems then.

rich99million
08-24-02, 09:58 AM
Originally posted by muddocktor
Also, EM3 had a problem reading those beta proggies so I just renamed the FAHconsole.exe, just like 3.11 is named and EM3 picks them up with no problems then.
Thanks for the tip :D i was considering trying the beta and that would definately have annoyed me - thanks


Rich