Work Units that cannot continue any further

[jfb9301]

This log is cut from a Double Gromacs that was worth a fair amount of points (over 100 I think. As you can see it could not continue right around 13%. How does FaH assign points for work that did not finish all the way

[05:26:01] + Processing work unit
[05:26:01] Core required: FahCore_79.exe
[05:26:01] Core found.
[05:26:01] Working on Unit 03 [March 6 05:26:01]
[05:26:01] + Working ...
[05:26:02]
[05:26:02] *------------------------------*
[05:26:02] Folding@Home Double Gromacs Core
[05:26:02] Version 1.72 (February 4, 2005)
[05:26:02]
[05:26:02] Preparing to commence simulation
[05:26:02] - Looking at optimizations...
[05:26:02] - Created dyn
[05:26:02] - Files status OK
[05:26:02] - Expanded 88443 -> 628065 (decompressed 710.1 percent)
[05:26:02] - Starting from initial work packet
[05:26:02]
[05:26:02] Project: 970 (Run 1056, Clone 2, Gen 2)
[05:26:02]
[05:26:02] Assembly optimizations on if available.
[05:26:02] Entering M.D.
[05:26:08] Protein: p970_fklig_dock
[05:26:08]
[05:26:08] Writing local files
[05:26:09] Writing local files
[05:26:09] Completed 0 out of 2000000 steps (0)
[06:13:21] Writing local files
.
.
[14:52:38] Completed 240000 out of 2000000 steps (12)
[15:39:59] Writing local files
[15:39:59] Completed 260000 out of 2000000 steps (13)
[16:22:46] Gromacs cannot continue further.
[16:22:46] Going to send back what have done.
[16:22:46] logfile size: 8013
[16:22:46] - Writing 8549 bytes of core data to disk...
[16:22:46] ... Done.
[16:22:46]
[16:22:46] Folding@home Core Shutdown: EARLY_UNIT_END
[16:22:49] CoreStatus = 72 (114)
[16:22:49] Sending work to server


[16:22:49] + Attempting to send results
[16:22:49] + Results successfully sent
[16:22:49] Thank you for your contribution to Folding@Home.


The [H]orde needs You!

 

[Mayhem33]

You get partial credit for what you completed.
Usually this happens from an overclock that is not stable, or a computer restart before the proggy could write the results for a save.


Thanks xENo!!!

 

[jfb9301]

good to know. Thanks

Odd tho, the machine did not restart, and it's not overclocked. It's my P3 700 on a BX chipset web/mp3 server. Hasn't shown any instabilities in the 4 years since I built it.


The [H]orde needs You!

 

[Mayhem33]

good to know. Thanks

Odd tho, the machine did not restart, and it's not overclocked. It's my P3 700 on a BX chipset web/mp3 server. Hasn't shown any instabilities in the 4 years since I built it.


The [H]orde needs You!

Well occasionally you will get one that ends early. If it happens alot though, start to investigate.


Thanks xENo!!!

 

[DaSmurf]

Sometimes they send out proteins that arent quite up to snuff, I've gotten a few that ended early on an otherwise rock solid rig. Ofc, the second I saw that on my logs it sent me on an invisible gremlin hunt that yielded nothing. The problem cleared itself, and I havent had another happen in quite some time.

So I'm guessing that the problem was on their end, unless you have a fan going bad and your stocker is overheating...

 

[OSUguy98]

From time to time you may get early end units... I had one this morning as a matter of fact... But most of the time, it's the protien's fault, not yours.... although, if you see one, you do want to make sure you're not overheating,etc... my P4 2.4C has been OCed to 3.0 for the last 2 years, and is stable... but will have an early end unit from time to time (like this morning)....

As others have said, I wouldn't worry unless it happens again (soon)... if it doesn't happen on that boxen for months, don't worry.... but if every other protein is ending early, you have an issue...


Keep on Folding!!