Hi,

the current progress estimation is rather confusing to new participants and a bit uninformative. What about calculating the progress with the help of the WU duration?
percentage = [cpu time] / [wu length set by the user] * 100%

Wouldn't that be more informative and logical?

Hi,

the current progress estimation is rather confusing to new participants and a bit uninformative. What about calculating the progress with the help of the WU duration?
percentage = [cpu time] / [wu length set by the user] * 100%

Wouldn't that be more informative and logical?

That would still be approximate since it may stop after 4 hrs on a 6 hr task length and I'm sure you'll get some 101%+ situations. But isn't that what is used already or somthing very similar anyway.

---

Team mauisun.org

I'm sure you'll get some 101%+ situations.

You would have to check if the cpu time is more than the target wu length.

But isn't that what is used already or somthing very similar anyway.

Yes, but it's only updated when a model completes and starts at 1%. It would be more logical if it starts at 0% and is updated all the time.

percentage = [cpu time] / [wu length set by the user] * 100%

Wouldn't that be more informative and logical?

I think that's a great idea! As Fluffy points out, it would have it's own quirks, but... for a new participant, it would take longer to find THOSE then it would to see the time to completion INCREASING, and panic and abort! ...which some people do!

I would simply revise the forumla to avoid reaching oer 100%
percentage = [cpu time] / [ 1.05 * (wu runtime preference)] * 100%

or you could compute it sort of backwards
time remaining = [1.05 - (cpu time / wu runtime pref)] * wu runtime pref

The project team actually has embedded some special meanings in to the completion percentages displayed... it let's them more fully understand where the WU is in the program if you report the full value for % complete... but we haven't needed them for a very very long time. (i.e. no more 1% bug!)

---

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/

The project team actually has embedded some special meanings in to the completion percentages displayed... it let's them more fully understand where the WU is in the program if you report the full value for % complete... but we haven't needed them for a very very long time. (i.e. no more 1% bug!)

Ah, I didn't know that. But if they don't need them...

The project team actually has embedded some special meanings in to the completion percentages displayed... it let's them more fully understand where the WU is in the program if you report the full value for % complete... but we haven't needed them for a very very long time. (i.e. no more 1% bug!)

Ah, I didn't know that. But if they don't need them...

There is actually no reason why they cannot have both and they could report the time based to BOINC and then use the other either as an addition in the graphics or with a debug switch in the (rosetta) command line when they needed, say at ralph.

---

Team mauisun.org

No comments of the developers?

We will discuss about your suggestion and come back with a proposal on how to make this feather best reflect what is actually happening in Rosetta.

No comments of the developers?

---