KWSN Orbiting Fortress

[alpha_fruit]

This is a first................

Launch directory: C:\Program Files\Folding@Home


[12:13:18] - Ask before connecting: No
[12:13:18] - Use IE connection settings: Yes
[12:13:18] - User name: alpha_fruit (Team 117)
[12:13:18] - User ID: 48C032D794437D5
[12:13:18] - Machine ID: 1
[12:13:18]
[12:13:18] Loaded queue successfully.
[12:13:18] Initialization complete
[12:13:18] + Benchmarking ...
[12:13:23]
[12:13:23] + Processing work unit
[12:13:23] Core required: FahCore_78.exe
[12:13:23] Core found.
[12:13:29] Working on Unit 07 [August 11 12:13:29]
[12:13:29] + Working ...
[12:13:31]
[12:13:31] *------------------------------*
[12:13:31] Folding@Home Gromacs Core
[12:13:31] Version 1.81 (April 6, 2005)
[12:13:31]
[12:13:31] Preparing to commence simulation
[12:13:31] - Looking at optimizations...
[12:13:32] - Files status OK
[12:13:32] - Expanded 345195 -> 1761493 (decompressed 510.2 percent)
[12:13:33]
[12:13:33] Project: 2011 (Run 76, Clone 13, Gen 1)
[12:13:33]
[12:13:34] Assembly optimizations on if available.
[12:13:34] Entering M.D.
[12:13:55] (Starting from checkpoint)
[12:13:55] Protein: p2011_BBA5_ext
[12:13:55]
[12:13:56] Writing local files
[12:16:02] Completed 10000 out of 500000 steps (2)
[12:16:03] Extra SSE boost OK.
[12:45:23] Writing local files
[12:45:23] Completed 15000 out of 500000 steps (3)
[13:13:14] Writing local files
[13:13:14] Completed 20000 out of 500000 steps (4)
[13:41:06] Writing local files
[13:41:06] Completed 25000 out of 500000 steps (5)
[14:08:59] Writing local files
[14:08:59] Completed 30000 out of 500000 steps (6)
[14:36:54] Writing local files
[14:36:54] Completed 35000 out of 500000 steps (7)
[15:04:49] Writing local files
[15:04:49] Completed 40000 out of 500000 steps (
[15:32:44] Writing local files
[15:32:44] Completed 45000 out of 500000 steps (9)
[16:00:38] Writing local files
[16:00:38] Completed 50000 out of 500000 steps (10)
[16:28:31] Writing local files
[16:28:31] Completed 55000 out of 500000 steps (11)
[16:56:24] Writing local files
[16:56:24] Completed 60000 out of 500000 steps (12)
[17:24:19] Writing local files
[17:24:19] Completed 65000 out of 500000 steps (13)
[17:56:57] Writing local files
[17:56:57] Completed 70000 out of 500000 steps (14)
[18:13:23] + Working...
[18:31:51] Writing local files
[18:31:51] Completed 75000 out of 500000 steps (15)
[19:05:58] Writing local files
[19:05:59] Completed 80000 out of 500000 steps (16)
[19:44:27] Writing local files
[19:44:27] Completed 85000 out of 500000 steps (17)
[21:43:07] Writing local files
[21:43:07] Completed 90000 out of 500000 steps (1
[22:19:54] Writing local files
[22:19:54] Completed 95000 out of 500000 steps (19)
[22:55:46] Writing local files
[22:55:46] Completed 100000 out of 500000 steps (20)
[23:22:16] Writing local files
[23:22:16] Completed 105000 out of 500000 steps (21)
[23:48:47] Writing local files
[23:48:47] Completed 110000 out of 500000 steps (22)
[00:13:23] + Working...
[00:15:15] Writing local files
[00:15:15] Completed 115000 out of 500000 steps (23)
[00:41:42] Writing local files
[00:41:42] Completed 120000 out of 500000 steps (24)
[01:08:07] Writing local files
[01:08:07] Completed 125000 out of 500000 steps (25)
[01:34:32] Writing local files
[01:34:33] Completed 130000 out of 500000 steps (26)
[02:01:00] Writing local files
[02:01:00] Completed 135000 out of 500000 steps (27)
[02:27:27] Writing local files
[02:27:27] Completed 140000 out of 500000 steps (2
[02:53:54] Writing local files
[02:53:54] Completed 145000 out of 500000 steps (29)
[03:20:23] Writing local files
[03:20:23] Completed 150000 out of 500000 steps (30)
[03:46:50] Writing local files
[03:46:50] Completed 155000 out of 500000 steps (31)
[04:13:16] Writing local files
[04:13:16] Completed 160000 out of 500000 steps (32)
[04:39:44] Writing local files
[04:39:44] Completed 165000 out of 500000 steps (33)
[05:06:10] Writing local files
[05:06:10] Completed 170000 out of 500000 steps (34)
[05:32:38] Writing local files
[05:32:38] Completed 175000 out of 500000 steps (35)
[05:59:06] Writing local files
[05:59:06] Completed 180000 out of 500000 steps (36)
[05:59:37] Quit 101 - Fatal error:
[05:59:37] Step 180100, time 360.2 (ps) LINCS WARNING
[05:59:37] relative constraint deviation after LINCS:
[05:59:37] max 0.001252 (between atoms 32 and 34) rms 0.000112
[05:59:37]
[05:59:37] Simulation instability has been encountered. The run has entered a
[05:59:37] state from which no further progress can be made.
[05:59:37] This may be the correct result of the simulation, however if you
[05:59:37] often see other project units terminating early like this
[05:59:37] too, you may wish to check the stability of your computer (issues
[05:59:37] such as high temperature, overclocking, etc.).
[05:59:37] Going to send back what have done.
[05:59:37] logfile size: 18694
[05:59:37] - Writing 19372 bytes of core data to disk...
[05:59:37] ... Done.
[05:59:38]
[05:59:38] Folding@home Core Shutdown: EARLY_UNIT_END
[05:59:40] CoreStatus = 72 (114)
[05:59:41] Sending work to server
_________________
Don't fuss about growing older, many are denied the chance.

[KWSN_hgs]

not to worry frooty dear, that happens with folding. what it means is that the math in the simulation itself went wonky and the simulation was a dud. not your fault at all. i'm pretty sure you get partial credit. if your boxen is overclocked you might have more troubles especially if you use the -forceasm flag.

Here's what Stanford has to say about it:

What is simulation instability? The simulation of molecular motion involves a great deal of computation. Each run consists of a number of time steps (each very small). At each time step, the position of the various atoms is calculated and updated, based on a number of factors. Sometimes, the simulation enters into a state that is not legal (i.e. atoms are too close, bonds are in impossible angles, etc.). At times like this, the Core exits, and information is uploaded to the server. The client will then get another assignment. If your computer is stable, then you haven't done anything wrong. On unstable computers, it is possible that the simulation instability was brought on by a fault of the system rather than something intrinsic to the work unit. Because of this, a work unit may be sent out again at some time if it is returned as having run into instability. In a given project, we expect a small percentage of units to encounter legitimate instability.
_________________
now, where was I???

[alpha_fruit]

Whew, I thought because I didn't use that PC since early this AM I did something wrong. I was very mad at ME. Now I am OK with me and in love again.

Thanks for such a quick reply.
_________________
Don't fuss about growing older, many are denied the chance.

[Sir Furry Mark]

I get these from time to time. In fact I think nearly everyone does if they wait long enough. I just accept it as fate and reassure myself that finding an instability might be useful science in itself (it defines a region of the simulation that doesn't work).

If you start getting a lot then you need to suspect your PC. I had one that was failing almost every unit it got. When I took the side off the computer I discovered that the heatsink fan was completely full of dusty fluff (or was it fur? )

Ni!
_________________
(Sir Furry - Occasional member of the Migratory Coconuts)
"Never trust a computer you can't throw out a window." Steve Wozniak

[alpha_fruit]

Thanks Sir Furry, I vacuum and blow my fan all the time, also I keep my CPU up on my desk and off the floor, since I have doggies. My HP downstairs looked and smelled like sawdust as it was the one I was using when we were building this house. My PC guys said it smelled like new pine.
_________________
Don't fuss about growing older, many are denied the chance.

[Mildew]

Where do you sign up for the fan-club?
I might consider joining!
_________________


An nescis, mi fili, quantilla prudentia mundus regatur?

[alpha_fruit]

[Grawlfang]