There MUST be a way round this....

Viking

Viking

Viking

Associate
Joined
11 Jul 2006
Posts
293
Location
The Isle of Wight, UK
I'm sure someone out there can answer this...

I use EM3 to manage my folding, which works out fine on the whole, BUT, if I have to restart my box part way through a unit, I get the same problem every time.

What happens is that the unit runs about half the speed it was running before the reload.

Now, I know why it's happening, but not what to to do to fix it.

This is the log file....

###############################################################################
###############################################################################

Launch directory: C:\Program Files\Folding@Home
Executable: C:\Program Files\Folding@Home\FAH500-Console.exe
Arguments: -local -advmethods

[10:13:18] - Ask before connecting: No
[10:13:18] - User name: _Viking_ (Team 10)
[10:13:18] - User ID: 72E9AC322899A56A
[10:13:18] - Machine ID: 1
[10:13:18]
[10:13:18] Loaded queue successfully.
[10:13:18] + Benchmarking ...
[10:13:21]
[10:13:21] + Processing work unit
[10:13:21] Core required: FahCore_78.exe
[10:13:21] Core found.
[10:13:21] Working on Unit 02 [January 12 10:13:21]
[10:13:21] + Working ...
[10:13:21]
[10:13:21] *------------------------------*
[10:13:21] Folding@Home Gromacs Core
[10:13:21] Version 1.90 (March 8, 2006)
[10:13:21]
[10:13:21] Preparing to commence simulation
[10:13:21] - Ensuring status. Please wait.


Here's the problem bit...

[10:13:38] - Looking at optimizations...
[10:13:38] - Working with standard loops on this execution.
[10:13:38] - Previous termination of core was improper.
[10:13:38] - Going to use standard loops.
[10:13:38] - Files status OK
[10:13:38] - Expanded 78921 -> 420497 (decompressed 532.8 percent)
[10:13:39]
[10:13:39] Project: 2125 (Run 9, Clone 93, Gen 4)
[10:13:39]
[10:13:39] Entering M.D.
[10:13:59] (Starting from checkpoint)
[10:13:59] Protein: p2125_lambda_5way_melt_4_10011
[10:13:59]
[10:13:59] Writing local files
[10:13:59] Using table 1
[10:13:59] Completed 12400000 out of 20000000 steps (62)

Now, I think it's set up right (as per the instructions on this forum!) but as you can see, whenever I shut down the PC, folding doesn't shut down *gently*, and as a consequence turns off all optimizations when it restarts!

This is a right pain in the bum, and I feel sure it's fixable.

Hope someone out there can shed some light on this...

Cheers in advance.
 
You can force Folding to run with enhanced loops even when shut down incorrectly by adding the -forceasm argument to the path, along with -local and -advmethods.

If it does this every time, however, Folding isn't being shut down the right way, which can lead to corruption of WUs. Do you run Folding from a shortcut which launches a black command window? If so, you need to close that window by pressing Ctrl+C rather than clicking the cross, before you shut down.
 
Mattus said:
You can force Folding to run with enhanced loops even when shut down incorrectly by adding the -forceasm argument to the path, along with -local and -advmethods.
Click to expand...
Adding the -forceasm flag should do the trick.

FYI, the -local flag is redundant - the core no longer takes it into account. As long as you have separate clients running in separate folders, folding will be fine without it. That could do with being changed in the sticky really, although it doesn't do any harm, so I guess it isn't really important.
 
-local isn't used if it's run as a service - however in this case it's not being run as a service so the -local flag should still be used

and yep -forceasm will sort this problem out once and for all :)
 
It's because you're not closing the client properly. As above, press CTRL+C to shut down the core before shutting down. Otherwise you might lose a wu. I wouldn't use -forceasm, will make things worse.
 
-forceasm is just a convenience thing really, so the client starts up with enhancements if your computer crashes. You still need to shut the client down properly as -forceasm won't prevent you from losing WUs.
 
Not sure I get this, EM3 starts the core at startup, and it also hides the 'black box' thingy (I never see it). I assumed that when I exit EM3 it shuts down the core properly (is this not the case?). If I need to use these other settings, where in EM3 do I put them? I have the 'use advmethods' box tickedin EM3 but am not sure where the other things talked about here need to go.

Or would it be easier to stop using EM3 if it's not doing it's job properly?
 
Viking said:
Or would it be easier to stop using EM3 if it's not doing it's job properly?
Click to expand...
that would be my choice - though I'll fire up EMIII and see if I can see a way of doing it

edit: ok where you tick to select -advmethods you can write extra flags into the text box after -advmethods, just put a space between them and it should work fine :)

-advmethods -forceasm
 
Last edited:
Just the job!

Oh yes, so you can!

I had a feeling it would be something obvious I was missing like that, well spotted that man!

Fresh eyes and all that....
 
You must log in or register to reply here.
Back
Top Bottom