I like 4.80 - thanks.

But, am a bit puzzled by the progess% shown in the BOINC Manager Work tab. With Rosetta, I often see it is at 1.00%, regardless of how much crunching has been going on. This morning my current Rosetta WU Progress is 40.00%, whereas CPU Time is ~1hr and To Completion is ~3hrs.

?!

---

I believe that first the time is a estimate and second, some if not all projects take more time to process the front end, than it takes for the backend....

The 1% can be caused by the above or the WU is hung up....

The 5.x.x ver of Boinc have a better correction factor to help bring the process time more in line with reallity....

---

BOINC Wiki

I believe that first the time is a estimate and second, some if not all projects take more time to process the front end, than it takes for the backend....

The 1% can be caused by the above or the WU is hung up....

The 5.x.x ver of Boinc have a better correction factor to help bring the process time more in line with reallity....

I can appreciate that the times are estimates; what I wasn't clear about is why the progress% doesn't match the times, regardless of whether the time-to-go is a guess.

In other words, if rosetta estimates the time-to-go, why doesn't it use the time-so-far and estimated time-to-go to generate a progress%? If rosetta estimates the progress%, why doesn't it use the time-so-far and estimated progress% to generate the time-to-go? Surely there is no reason why they can't add up?

The other projects have no problems with this.

---

This project has a very granular percent complete calculation. I think it only has 1%, 10%, 20%, ect. Also I believe that the percent complete only updates when a checkpoint is made.

---

BOINC WIKI

BOINCing since 2002/12/8