It seems my time to completion counter in BoincManager is counting upwards instead of downwards.

I made a little video so you can see for yourself:
click here to see what's happening

Can anyone tell me why it does this? It's the latest version for OS X. Running 10.4.6. Not doing anything else, just Boincing.

---

which project?

It seems my time to completion counter in BoincManager is counting upwards instead of downwards.

I made a little video so you can see for yourself:
click here to see what's happening

Can anyone tell me why it does this? It's the latest version for OS X. Running 10.4.6. Not doing anything else, just Boincing.

Sorry, I can't see your mov file. Which project?

My guess is that the estimated time provided by the project was wrong. I know that the QMC project has a problem with its estimates.

The first units I got from them slowly counted up from 33 hrs until it reached about 50% then started counting down. With all the projects I crunch, it required intervention on my part to give it extra resource share (even suspension of other projects) and allow it to finish within due date. Boinc can only work with the info it's given. I had to crunch a couple of WU before the Boinc compensation factor was able adjust the estimate to the correct amount. New WU now displays the correct completion time for the project despite the bad estimates and counts down from 95 hrs it takes on my system.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

It's Rosetta.

---

It's Rosetta.

I haven't seen this problem at Rosetta, but then, I haven't paid to much attention to what's going on there recently. Unless I'm mistaken, they now issue WU with different completion times so it is possible that your correction factor number is now off the mark and temporarily causing a similar issue to what I saw at QMC. The WU may still be able to complete properly and Boinc will revise its correction factor for that project. I would keep an eye on it for now.

I doubt that it is a Boinc issue as such, so, I suggest you post your observations on the Rosetta number crunching board. Someone there may have experience the same problem.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

Boramor, did you recently change your "cpu run time" preference? This usually occurs when the DCF (duration correction factor) is expecting a shorter run time than it's actually getting. (I.E you were at the default (not selected) and went to a much higher figure. It also might be related to Casp7 trials, but I'm not a rosetta guru. The new "estimated run times" should be higher for your next wus than it was for that one. I'd just let it run, and watch it to see if it's continuing. If it is then post to Rosetta Number Crunching, and I'll see your post there.

tony