This is being asked as I am watching a WU reach the 2 Million Steps mark for a model: Model 12 for JUMP_AllBARCODE01_1tul_468_4983. The processing is slowwwwwwwwwwwwwww... ( I started early in the morning and I am still less than 50% done )but it is interesting to notice how demanding and how complex the new models are.

---

This is being asked as I am watching a WU reach the 2 Million Steps mark for a model: Model 12 for JUMP_AllBARCODE01_1tul_468_4983. The processing is slowwwwwwwwwwwwwww... ( I started early in the morning and I am still less than 50% done )but it is interesting to notice how demanding and how complex the new models are.

I'm guessing, since you are new, perhaps you decided to change the preferred WU runtime setting in your Rosetta Preferences?

Review of the FAQ will explain you must run at least 1 model, you say you've run 12, that's good. I think there was a quirk where the steps kept increasing rather than resetting each model, so don't worry about the large number of steps. And the fact that it's 50% done basically means it's "planning" to run for about another 12 models. And this is based on your preferred runtime setting. So, it should finish normally at about that time.

If you just changed your preferred runtime, the estimated time to complete takes several updates to the project to accurately reflect your preference. Once it sees this one run for 12 hours (or whatever), then it will begin learning that your WUs are taking that long. This flexible work unit thing is unique to Rosetta, so it's a little awkward at first in BOINC. In the meantime, the estimated time to completion should basically be ignored. At this point a truer representation is to take your CPU time so far, divide by the % complete and that's the total runtime it's shooting for.

For example I run with a 24hr time preference, I've got a WU that has been running for 17:09 (9min/60min per hr = .15hrs) and says it is 70.34% complete. Take 17.15 / .7034 and you get 24.38hrs. And if you subtract the 17hrs we've got in to it so far, I expect it will wrap up in about 7hrs, give or take (in spite of the well "trained" 12hr estiamted time to completion shown on my screen :)

Hope this helps.

Bottom line, in MOST CASES, just be patient and it will take care of itself.

Welcome to Rosetta! I hope you find you enjoy crunching and learning with the scientists as much as I do!

---

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/

I had one of these "Jump" Work Units on one of my systems two days ago. The time setting on that system if for 2 hours. After 9 hours I began to get worried just as you have. The step count was well above 3,000,000. I let it run and it finished after 14 hours with one model. What you are seeing is normal, just let it run.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

I had one of these "Jump" Work Units on one of my systems two days ago. The time setting on that system if for 2 hours. After 9 hours I began to get worried just as you have. The step count was well above 3,000,000. I let it run and it finished after 14 hours with one model. What you are seeing is normal, just let it run.

It ended with a client error message https://boinc.bakerlab.org/rosetta/result.php?resultid=18998714

---

I had one of these "Jump" Work Units on one of my systems two days ago. The time setting on that system if for 2 hours. After 9 hours I began to get worried just as you have. The step count was well above 3,000,000. I let it run and it finished after 14 hours with one model. What you are seeing is normal, just let it run.

It ended with a client error message https://boinc.bakerlab.org/rosetta/result.php?resultid=18998714

Well it shows a ...00005 type errors. Which does not really say very much, but you have sent a lot of diagnostic data that does. This will get credit in the next credit sweep.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact