% of Work done.

[Corsair]

Hi Fred,

I've notice some difference that are making me crazy.

e.g. Seti@home Beta with AP same WU at the same time,
reported by different programs:
Boinc Manager -- BoincView -- Boinc Tasks
37.86  ------------     37.86 ------- 23.99
23.57  ------------     23.57 ------- 13.44
11.79  ------------     11.79 ------- 10.77
06.60  ------------     06.60 ------- 09.20
00.97  ------------     00.97 ------- 05.70

I don't know how is calculated this, but I think this should be reported by the BOINC Manager ??.

Another thing, it use to be with WUs of some projects of Ibercivis, that in the Boinc Manager and
BoincView are working but progress bar is at 0% during the whole calculation but in BoincTasks
you could see % done (good).

[fred]

Hi Fred,

I've notice some difference that are making me crazy.

e.g. Seti@home Beta with AP same WU at the same time,
reported by different programs:
Boinc Manager -- BoincView -- Boinc Tasks
37.86  ------------     37.86 ------- 23.99
23.57  ------------     23.57 ------- 13.44
11.79  ------------     11.79 ------- 10.77
06.60  ------------     06.60 ------- 09.20
00.97  ------------     00.97 ------- 05.70

I don't know how is calculated this, but I think this should be reported by the BOINC Manager ??.

Another thing, it use to be with WUs of some projects of Ibercivis, that in the Boinc Manager and
BoincView are working but progress bar is at 0% during the whole calculation but in BoincTasks
you could see % done (good).

I've seen that, but I think BoincTasks version is better. It really goes from 0 - 100 .
But maybe the BOINC Manager way is more accurate.
Mine is more related to the real clock as is is using the elapsed time and the time left.
And the AP values are off most of the time anyway, so it's only an estimate.

[Corsair]

I've seen the exchange of that in version 0.26, but there is something curious.

e.g. AP beta, is a long time processing WU, BT reports during the firsts hours
0.01 .... 0.99 while BM is reporting 0.01 ... X.yz different, when BT arrives to
1.00 it immediately exchange to BM reading some of the cases 3x.xz %  and
now till the end of processing both are showing the same reading (BT and
the BOINC Manager)

[fred]

I've seen the exchange of that in version 0.26, but there is something curious.

e.g. AP beta, is a long time processing WU, BT reports during the firsts hours
0.01 .... 0.99 while BM is reporting 0.01 ... X.yz different, when BT arrives to
1.00 it immediately exchange to BM reading some of the cases 3x.xz %  and
now till the end of processing both are showing the same reading (BT and
the BOINC Manager)

That's correct < 1% I take the progress time divided by the ext time to completion. In that way I have an immediate % right from the start. Otherwise it may take up to a minute or a lot more for a WU to show actual progress.
It's a compromise... and AP tasks aren't that accurate in timing anyway.

[Corsair]

Another thing seen in this last version (0.26) with % of work done,
with MW I've seen:
- started crunching but no CPU bar shown, and % is growing, sometimes
happens when there is a crash in the GPU driver (CAL/ATI).
- if a MW WU has been stopped or "running" not properly the CPU bar is
coloured as the stated one in preferences (below certain %), if WU is restarted
the % of CPU is very little but the progress is correct, and for that reason the
color remains as error, when is really crunching correct. I've notice this e.g.
MW is "running"  for half an hour, and the WU is restarted, use to be crunched
in 1 minute this WU.

[fred]

Another thing seen in this last version (0.26) with % of work done,
with MW I've seen:
- started crunching but no CPU bar shown, and % is growing, sometimes
happens when there is a crash in the GPU driver (CAL/ATI).
- if a MW WU has been stopped or "running" not properly the CPU bar is
coloured as the stated one in preferences (below certain %), if WU is restarted
the % of CPU is very little but the progress is correct, and for that reason the
color remains as error, when is really crunching correct. I've notice this e.g.
MW is "running"  for half an hour, and the WU is restarted, use to be crunched
in 1 minute this WU.

You mean the CUDA of CPU Milkyway WU. The CUDA is very very short and uses only a few % of CPU time.
It is probably running properly, but something else may take up it's CPU time like a AP CAL task.
But I have some MW in stock.

[Corsair]

You mean the CUDA of CPU Milkyway WU.

no, CAL (ATI/AMD) Milkyway WU.