Overclock.net banner

1 - 13 of 13 Posts

·
Premium Member
Joined
·
5,573 Posts
Discussion Starter #1
[07:18:24] Completed 960000 out of 1000000 steps (96)
[07:19:19] Quit 101 - Fatal error:
[07:19:19] Step 963103, time 1926.21 (ps) LINCS WARNING
[07:19:19] relative constraint deviation after LINCS:
[07:19:19] max 0.001078 (between atoms 511 and 514) rms 0.000054
[07:19:19]
[07:19:19] Simulation instability has been encountered. The run has entered a
[07:19:19] state from which no further progress can be made.
[07:19:19] This may be the correct result of the simulation, however if you
[07:19:19] often see other project units terminating early like this
[07:19:19] too, you may wish to check the stability of your computer (issues
[07:19:19] such as high temperature, overclocking, etc.).
[07:19:19] Going to send back what have done.
[07:19:19] logfile size: 43898
[07:19:19] - Writing 44580 bytes of core data to disk...
[07:19:19] ... Done.
[07:19:19]
[07:19:19] [email protected] Core Shutdown: EARLY_UNIT_END
[07:19:21] CoreStatus = 72 (114)
[07:19:21] Sending work to server
 

·
Premium Member
Joined
·
5,573 Posts
Discussion Starter #3
Quote:

Originally Posted by shajbot
So it says that your computer could be instable...
...Or, the folding geometry did not work. Which is a successful outcome if you are a scientist.
 

·
Registered
Joined
·
510 Posts
Happens every now and then. Unless you get this message regularly it means nothing except that that simulation didn't work. If you do get it regularly than it could mean your rig is unstable.
 

·
Overclockiit
Joined
·
3,419 Posts
Dont feel bad i just rebooted one of my folding rigs and lost all my work i was 96% done with the wu i dunno what happen now ive got a whole new wu thats gonna take 20days ***....
 

·
Premium Member
Joined
·
45,674 Posts
Quote:

Originally Posted by |2A|N
Dont feel bad i just rebooted one of my folding rigs and lost all my work i was 96% done with the wu i dunno what happen now ive got a whole new wu thats gonna take 20days ***....
Suspend the WU before shutting down.
 

·
Premium Member
Joined
·
13,422 Posts
I got the same error after I just checked (never checked before). What project were you working on?

[19:29:16] Step 73961, time 147.922 (ps) LINCS WARNING
[19:29:16] relative constraint deviation after LINCS:
[19:29:16] max 0.340575 (between atoms 545 and 546) rms 1.#QNAN0
[19:29:16]
[19:29:16] Simulation instability has been encountered. The run has entered a
[19:29:16] state from which no further progress can be made.
[19:29:16] This may be the correct result of the simulation, however if you
[19:29:16] often see other project units terminating early like this
[19:29:16] too, you may wish to check the stability of your computer (issues
[19:29:16] such as high temperature, overclocking, etc.).
[19:29:16] Going to send back what have done.
[19:29:16] logfile size: 26465
[19:29:16] - Writing 27146 bytes of core data to disk...
[19:29:16] ... Done.
[19:29:16]
[19:29:16] [email protected] Core Shutdown: EARLY_UNIT_END
[19:29:18] CoreStatus = 72 (114)
[19:29:18] Sending work to server
 

·
Premium Member
Joined
·
5,573 Posts
Discussion Starter #8
Quote:


Originally Posted by pauldovi

I got the same error after I just checked (never checked before). What project were you working on?

[19:29:16] Step 73961, time 147.922 (ps) LINCS WARNING
[19:29:16] relative constraint deviation after LINCS:
[19:29:16] max 0.340575 (between atoms 545 and 546) rms 1.#QNAN0
[19:29:16]
[19:29:16] Simulation instability has been encountered. The run has entered a
[19:29:16] state from which no further progress can be made.
[19:29:16] This may be the correct result of the simulation, however if you
[19:29:16] often see other project units terminating early like this
[19:29:16] too, you may wish to check the stability of your computer (issues
[19:29:16] such as high temperature, overclocking, etc.).
[19:29:16] Going to send back what have done.
[19:29:16] logfile size: 26465
[19:29:16] - Writing 27146 bytes of core data to disk...
[19:29:16] ... Done.
[19:29:16]
[19:29:16] [email protected] Core Shutdown: EARLY_UNIT_END
[19:29:18] CoreStatus = 72 (114)
[19:29:18] Sending work to server

This one:

[02:35:27] [email protected] Gromacs Core
[02:35:27] Version 1.90 (March 8, 2006)
[02:35:27]
[02:35:27] Preparing to commence simulation
[02:35:27] - Assembly optimizations manually forced on.
[02:35:27] - Not checking prior termination.
[02:35:27] - Expanded 206395 -> 1009291 (decompressed 489.0 percent)
[02:35:27] - Starting from initial work packet
[02:35:27]
[02:35:27] Project: 773 (Run 15, Clone 77, Gen 5)
[02:35:27]
[02:35:27] Assembly optimizations on if available.
[02:35:27] Entering M.D.
[02:35:34] Protein: p773_vln2.8nopbc-com
 

·
Premium Member
Joined
·
5,573 Posts
Discussion Starter #10
Quote:


Originally Posted by pauldovi

Same project as mine.

BAD molecule BAD!
 

·
Registered
Joined
·
1,102 Posts
Yeah, projects 772 and 773 have been giving me the same messages on occasion. I've probably failed 2 (maybe three) in the past week, only with those work units. The beefier Gromacs never gave me problems....

For the past couple of days though those two projects are all I've been getting...

EDIT: I have had 2 of them in the past 24H... I'll wait until I get some different work units to see if it's a problem on my end.
 
1 - 13 of 13 Posts
Top