Questions and Answers : Windows : 79 hour work unit, 4 hours of credit WHAT??
Author | Message |
---|---|
Acrazar Send message Joined: 2 Jan 06 Posts: 1 Credit: 1,152,280 RAC: 0 |
i left my rig on for 3 days while i was away, i come back to find that it crunched for 79 hours on the same unit, i had to move back home and when i rebooted the computer it ran for 4 more hours than finished, but i only recieved credit as it had been run for 4 hours, as seen here https://boinc.bakerlab.org/rosetta/workunit.php?wuid=9655806 heres a screen shot taken just before i shut my computer down for the move. |
Moderator9 Volunteer moderator Send message Joined: 22 Jan 06 Posts: 1014 Credit: 0 RAC: 0 |
The work unit had either become stuck, the restart of your system restared the Work Unit over at the begining of processing, and that is why it only claimed a nominal 4 hours worth of work. This still occurs with some Rosetta Work Units, but the problem is being worked on. Moderator9 ROSETTA@home FAQ Moderator Contact |
Feet1st Send message Joined: 30 Dec 05 Posts: 1755 Credit: 4,690,520 RAC: 0 |
I'm having similar issue with a ABINTew_hom... and a PRODUCTION_ABINITIO_RANDOMFRAG... WU. But they're not stuck on 1%. Seems to be progressing. Shows 35hrs used, 36.66% done and 28hrs ta go. The graphic shows I'm now on model 224, and it's been increasing. The est. time to completion is still increasing, but at a slower rate as it runs further here. Right now I've got several of these 8hr work units, and looks like all of them have resulted in computation errors with other users. I'm just wondering, is it getting any useful science done here? Or will the time to completion continue to climb? I'm not clear on what the work unit problems have been. Are there certain WU file names that we should be aborting? Add this signature to your EMail: Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might! https://boinc.bakerlab.org/rosetta/ |
Moderator9 Volunteer moderator Send message Joined: 22 Jan 06 Posts: 1014 Credit: 0 RAC: 0 |
I hope you will excuse my referring you to read something on this topic, but the answers to the questions you pose have been repeated so often that we prepared a FAQ to answer them. Please read this FAQ. I would ask you to check your preferences to see what your time setting is. It looks from your description that you may have the time set to some value like 2 or or 4 days. An 8 hour WU will not run for 36 hours unless it is stuck. If your percent complete is increasing, and the number of models completed (as shown in the graphic display) is increasing, then the WU is not stuck. But the FAQ will explain all this in more detail. Moderator9 ROSETTA@home FAQ Moderator Contact |
Feet1st Send message Joined: 30 Dec 05 Posts: 1755 Credit: 4,690,520 RAC: 0 |
...excuse my referring you to read something... FAQ. More than happy to read. Thanks for specific link rather than "Read the FAQ" (which I had already done). That description nailed a stack of questions I'd been having trouble finding. I had missed it due to the description in the FAQ. It says "how to set the work unit time parameter", but I hadn't really realized that was my question. Until one understands that the "size" is actually handled by the number of models the client choses to invoke, it isn't clear that this is the question. Like using a dictionary for spelling ("How do I look it up, if I can't spell it?"). So I kept skipping that one because I already KNOW how to change my preferences. I just didn't fully understand what effect that was having. I kept reading about the hung WUs, but my symptoms didn't match. My WU finally completed normally after about 56hrs. And yes, I had time set to 2 days. And yep, sure enough, after that work unit reported in and updated with the project, my remaining WUs got estimated runtimes of 90hrs (rather than the 8hrs they had previously). I was expecting that preference to find larger WUs and that the estimates would reflect that. Reading the FAQ, this disparity and the resulting problems already seems well understood. I just wanted to recap. for future readers. For future readers, set your preference to a shorter runtime, and then update to the project, and your existing WUs can still complete before the deadline. Beware, this change to WU size seems to cause existing work in a WU to be discarded, and restarted. So, best to suspend unstarted WUs, finish what you've started, and then do the update, and resume the WUs. May I suggest rewording the FAQ to something broader like "Discussion of work unit size"?Because setting it in your preferences is only part of the picture discussed there. Add this signature to your EMail: Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might! https://boinc.bakerlab.org/rosetta/ |
Questions and Answers :
Windows :
79 hour work unit, 4 hours of credit WHAT??
©2024 University of Washington
https://www.bakerlab.org