Are the p1499_tet_1499's as good as they seem to be?
DanG
I AM CANADIAN Icrontian
13:37:33] Project: 1499 (Run 46, Clone 0, Gen 6)
[13:37:33]
[13:37:33] Assembly optimizations on if available.
[13:37:33] Entering M.D.
[13:37:40] Protein: p1499_tet_1499
[13:37:40]
[13:37:40] Writing local files
[13:37:43] Extra SSE boost OK.
[13:37:43] Writing local files
[13:37:43] Completed 0 out of 125000 steps (0)
[13:42:03] Writing local files
[13:42:03] Completed 1250 out of 125000 steps (1)
[13:46:24] Writing local files
[13:46:24] Completed 2500 out of 125000 steps (2)
[13:50:44] Writing local files
[13:50:44] Completed 3750 out of 125000 steps (3)
[13:55:05] Writing local files
[13:55:05] Completed 5000 out of 125000 steps (4)
[13:59:25] Writing local files
[13:59:25] Completed 6250 out of 125000 steps (5)
[14:03:45] Writing local files
[14:03:46] Completed 7500 out of 125000 steps (6)
[14:08:06] Writing local files
[14:08:06] Completed 8750 out of 125000 steps (7)
[14:12:26] Writing local files
[14:12:26] Completed 10000 out of 125000 steps (8)
By my math, it's about 4 minutes and 21 seconds per frame, 100 frames and 364 points per WU, which is about 1200 points a day, and almost 8500 per week.
Or is my math screwed up somewhere? For some reason EMIII doesn't show a point value for this protien, but the stanford site shows it as 364.
Can it be this good?
0
Comments
Now, if we can get the QMDs back! :bigggrin:
[settings]
...
asknet=no
bigpackets=yes
machineid=2
local=70
[http]
active=no
host=localhost
port=8080
usereg=no
[clienttype]
type=3
_______________
From FAH WIKI for client types:
S: type=3
O: Request work units without deadlines (no/yes) [no]?
O: Set -advmethods flag always, requesting new advanced
scientific cores and/or work units if available (no/yes) [yes]
N: This is option was added in client v5.04.
I pretty sure I have it right- yes?
I may simply have not drawn one yet and/or not have had EM running to log it when I did.
Note: Inadvertent reference to private beta WU removed.
-Prof
Here's the log I receive:
[06:10:42] + Core successfully engaged
[06:10:47]
[06:10:47] + Processing work unit
[06:10:47] Core required: FahCore_78.exe
[06:10:47] Core found.
[06:10:47] Working on Unit 01 [January 19 06:10:47]
[06:10:47] + Working ...
[06:10:47]
[06:10:47] *
*
[06:10:47] Folding@Home Gromacs Core
[06:10:47] Version 1.90 (March 8, 2006)
[06:10:47]
[06:10:47] Preparing to commence simulation
[06:10:47] - Looking at optimizations...
[06:10:47] - Created dyn
[06:10:47] - Files status OK
[06:10:49] - Expanded 857201 -> 12361133 (decompressed 1442.0 percent)
[06:10:49] - Starting from initial work packet
[06:10:49]
[06:10:49] Project: 1499 (Run 598, Clone 0, Gen 8)
[06:10:49]
[06:10:50] Assembly optimizations on if available.
[06:10:50] Entering M.D.
[06:10:57] Protein: p1499_tet_1499
[06:10:57]
[06:10:57] Writing local files
[06:10:57] Gromacs error.
[06:10:57]
[06:10:57] Folding@home Core Shutdown: UNKNOWN_ERROR
[06:11:01] CoreStatus = 79 (121)
[06:11:01] Client-core communications error: ERROR 0x79
[06:11:01] Deleting current work unit & continuing...
[06:11:21] - Preparing to get new work unit...
[06:11:21] + Attempting to get work packet
[06:11:21] - Connecting to assignment server
[06:11:22] - Successful: assigned to (171.64.122.134).
[06:11:22] + News From Folding@Home: Welcome to Folding@Home
[06:11:22] Loaded queue successfully.
[06:11:35] + Closed connections
[06:11:40]
[06:11:40] + Processing work unit
[06:11:40] Core required: FahCore_78.exe
[06:11:40] Core found.
[06:11:40] Working on Unit 02 [January 19 06:11:40]
[06:11:40] + Working ...
[06:11:40]
[06:11:40] *
*
[06:11:40] Folding@Home Gromacs Core
[06:11:40] Version 1.90 (March 8, 2006)
[06:11:40]
[06:11:40] Preparing to commence simulation
[06:11:40] - Looking at optimizations...
[06:11:40] - Created dyn
[06:11:40] - Files status OK
[06:11:42] - Expanded 857201 -> 12361133 (decompressed 1442.0 percent)
[06:11:42] - Starting from initial work packet
[06:11:42]
[06:11:42] Project: 1499 (Run 598, Clone 0, Gen 8)
[06:11:42]
[06:11:43] Assembly optimizations on if available.
[06:11:43] Entering M.D.
[06:11:49] Protein: p1499_tet_1499
[06:11:49]
[06:11:49] Writing local files
[06:11:49] Gromacs error.
[06:11:49]
[06:11:49] Folding@home Core Shutdown: UNKNOWN_ERROR
[06:11:52] CoreStatus = 79 (121)
[06:11:52] Client-core communications error: ERROR 0x79
[06:11:52] Deleting current work unit & continuing...
Folding@Home Client Shutdown.
I don't know why the Gromacs error occurs and whether I have to change something in the console configuration to prevent this cycle of errors that prevents the task from starting properly.
Thank you in advance for all your comments and any advice you wish to provide.
I'm not sure why the error occurred and whether it was related to the abrupt interruption of the 1499_tet_1499 task or bad memory like you suggest.
I made an adjustment in the FAH console configuration just now and removed the -advmethods flag. The Gromacs core fortunately started properly and I got a new task so I'm folding again.
I think the incorrect interruption of the 1499_tet_1499 must have had a negative effect on the client.cfg file and prevented the correct use of -advmethods flag. Once the task I received now completes I will add -advmethods again and hopefully there will be no client-core errors.
______
//EDIT:
I will perform the Memtest after the current work unit completes, to ensure there is nothing wrong with the memory stick of the computer.
The processor is overclocked and it has been performing very well for a low grade Sempron socket 754
Yes, run Memtest like Leo suggested. Your CPU might be overheating (when was the last time you cleaned out your PC?) as well. Keep checking your logs. Hardware problems can be intermittent and your WUs may continue to fail and abort even though the FAH servers will continue to give you new WUs. Try backing off your overclock if you still have problems.
If everything checks out but Wus are still failing, post with your FAH log. You might have a bad core.
Thermalfish-
Two days after my last post in this thread I FINALLY got a 1499 (with my posted client.cfg settings) after many moons. I might add they run pretty good on an AMD too. However, I doubt having a Mac is the issue- I think it might be what your assignment server has when.
omg ...he went there.
Hehe thanks. I thought I had edited that myself and only now am I finding out that I only quoted myself.
Thank you Spike and Prof.
It's back to p2125_lambda_5way_melt_4_10011 at the moment but I'm not complaining
back to the scheduled programming, the P149x series are great until you get 2 on the same machine frame times rose from 7min 30s with a five way patty on the other core to 20 mins, with 2 1499's. this is on an E6400 with 2 Gb of DDR2 667.
The reason I'm wondering is I was going to hold out for the 4xxx series Intels with the lower fsb.
Didn't you and mudd each have a core2duo a while back?