A (possibly) silly question!

Viking

Viking

Viking

Associate
Joined
11 Jul 2006
Posts
293
Location
The Isle of Wight, UK
Quick question for you all...

I want to play a game on my folding machine, so..

What is the proper method (assuming there is one!) of shutting down WinSMP folding without losing all progress on the WU?

Or is it better to leave it running during the game?

I tried to play while running folding and the machine crashed (not saying it was F@Hs fault, you understand!), but the upshot was, that when I rebooted I'd lost all the data and the WU started from scratch. :(

Any suggestions?

Ta!
 
It should be OK to leave running. But WinSMP can be a bit temperamental... the right way to shut it down is to press Ctrl+C in the console window.
 
Can that be done at any time without losing data or does it go back to a checkpoint or something?
 
It goes back to the last checkpoint, which will usually be at the end of the previous frame (%) unless you have it set up to run timed checkpoints more frequently.
 
back to last step - only time I've even had it start part way through, was with ubuntu (smp as a service) following a shutdown.

Actually the standard client does the same when it's a service (if you stop a service manually it restart a last step)
 
shadowscotland said:
back to last step - only time I've even had it start part way through, was with ubuntu (smp as a service) following a shutdown.

Actually the standard client does the same when it's a service (if you stop a service manually it restart a last step)
Click to expand...

Checkpoints have never worked for me on any client - standard/winSMP or linSMP

Edit - pesky quick reply window on a minimised screen
 
Timered checkpoints work fine on my WinSMP

[23:03:14] Completed 80000 out of 500000 steps (16 percent)
[23:13:15] Timered checkpoint triggered.
[23:23:15] Timered checkpoint triggered.
[23:33:16] Timered checkpoint triggered.
[23:33:24] Killing all core threads
[23:33:24] Killing SMP core threads
[23:33:25] Killing 4 cores
[23:33:25] Killing core 0
[23:33:25] Killing core 1
[23:33:25] Killing core 2
[23:33:25] Killing core 3
Click to expand...

[23:53:39] Project: 2610 (Run 0, Clone 0, Gen 49)
[23:53:39]
[23:53:40] Assembly optimizations on if available.
[23:53:40] Entering M.D.
[23:53:46] Calling FAH init
[23:53:48] Read topology
[23:53:48] (Starting from checkpoint)
[23:53:48] f 500000 steps (16 percent)
[23:53:48] ein
[23:53:48] Writing local files
[23:53:48] Completed 83500 out of 500000 steps (16 percent)
[23:53:50] Extra SSE boost OK.
[00:03:49] Timered checkpoint triggered.
[00:07:17] Writing local files
[00:07:17] Completed 85000 out of 500000 steps (17 percent)
Click to expand...

Also the standard Gromacs core should save its current progress before it exits so you shouldn't even lose the work since the last checkpoint - not sure if that's the same for the SMP (doesn't seem so from the nice round number above)

When I've had to stop the client I like to restart the machine before starting the client again - probably just me being over reactive but since my machine is usually on for weeks at a time it doesn't hurt to reboot every now and then :)
 
The client will save a checkpoint if a certain amount of time has elapsed since the last frame was completed. I think the default is 15 minutes, so if your system completes frames quicker than that then you might never have seen it!
 
You must log in or register to reply here.
Back
Top Bottom