Did I get burned again by SMP client?

Joined
Dec 13, 2003
Messages
2,238
[21:14:46] Loaded queue successfully.
[21:14:46]
[21:14:46] + Processing work unit
[21:14:46] Core required: FahCore_a1.exe
[21:14:46] Core found.
[21:14:46] Working on Unit 01 [March 22 21:14:46]
[21:14:46] + Working ...
[21:14:46]
[21:14:46] *------------------------------*
[21:14:46] Folding@Home Gromacs SMP Core
[21:14:46] Version 1.74 (March 10, 2007)
[21:14:46]
[21:14:46] Preparing to commence simulation
[21:14:46] - Ensuring status. Please wait.
[21:15:03] - Looking at optimizations...
[21:15:03] - Working with standard loops on this execution.
[21:15:03] - Previous termination of core was improper.
[21:15:03] - Going to use standard loops.
[21:15:03] - Files status OK
[21:15:14] - Expanded 4001777 -> 21620008 (decompressed 540.2 percent)
[21:15:17]
[21:15:17] Project: 2610 (Run 1, Clone 304, Gen 1)
[21:15:17]
[21:15:18] Entering M.D.
[21:15:24] Calling FAH init
[21:15:25] Writing local files
[21:15:25] Completed 410000 out of 500000 steps (82 percent)
[21:15:25] in
[21:15:25] Writing local files
[21:15:25] Completed 410000 out of 500000 steps (82 percent)
[21:15:26] Extra SSE boost OK.
[21:30:56] Writing local files
[21:30:56] Completed 415000 out of 500000 steps (83 percent)
[21:45:58] Writing local files
[21:45:58] Completed 420000 out of 500000 steps (84 percent)
[21:59:18] Writing local files
[21:59:18] Completed 425000 out of 500000 steps (85 percent)
[22:13:03] Writing local files
[22:13:03] Completed 430000 out of 500000 steps (86 percent)
[22:26:33] Writing local files
[22:26:33] Completed 435000 out of 500000 steps (87 percent)
[22:39:40] Writing local files
[22:39:40] Completed 440000 out of 500000 steps (88 percent)
[22:53:35] Writing local files
[22:53:35] Completed 445000 out of 500000 steps (89 percent)
[23:05:48] Writing local files
[23:05:48] Completed 450000 out of 500000 steps (90 percent)
[23:17:06] Writing local files
[23:17:06] Completed 455000 out of 500000 steps (91 percent)
[23:28:12] Writing local files
[23:28:13] Completed 460000 out of 500000 steps (92 percent)
[23:40:13] Writing local files
[23:40:13] Completed 465000 out of 500000 steps (93 percent)
[23:52:49] Writing local files
[23:52:49] Completed 470000 out of 500000 steps (94 percent)
[00:05:49] Writing local files
[00:05:50] Completed 475000 out of 500000 steps (95 percent)
[00:17:01] Writing local files
[00:17:02] Completed 480000 out of 500000 steps (96 percent)
[00:28:20] Writing local files
[00:28:20] Completed 485000 out of 500000 steps (97 percent)
[00:40:05] Writing local files
[00:40:05] Completed 490000 out of 500000 steps (98 percent)
[01:51:42] Writing local files
[01:51:42] Unit 1's deadline (March 26 03:53) has passed.
[01:51:42] Going to interrupt core and move on to next unit...
[01:51:42] Completed 495000 out of 500000 steps (99 percent)
[01:51:42] Unit 1's deadline (March 26 03:53) has passed.
[01:51:42] Going to interrupt core and move on to next unit...


This has happened to me twice now. I'm probably not getting any credit for these units as well. Frustrating...
 
My smp client is also working ona 2610 and frame times are almost 20% faster than mine. How can I find out the deadline for my unit? It's not in the log file?

Kandor
 
What type and speed of processor are you running the Windows SMP client on? The SMP wus need to be returned quickly, and it looks like you are close to finnishing ontime, but not. Are you leaving your computer on 24x7? If you aren't, it looks like you'll need to leave it on another hour or two longer every day.
 
I think he's more concerned that it states the deadline is March 26th, and today is March 23rd.... maybe clock issues? Does your machine use an SNTP server to get/set the current time? If not then post your OS and I am pretty sure someone on here can tell you how to get the current time on any OS you have.
 
Believe it or not, this was simply a stupid mistake on my part. It would seem that I somehow changed my computer's time (either me or my kids I guess) to December of 2007. LOL....two units cooked by a 'noob' mistake! :(
 
As soon as I read the log file, I thought 'his clock is probably set wrong'.. but i didn't want to insult your intelligence. :p
 
Back
Top