AstroPulse v7 7.10 windows_intelx86 (opencl_nvidia_100)
	Number of tasks completed 	0
	Max tasks per day 		64
	Number of tasks today 		12
	Consecutive valid tasks 	31
	Average turnaround time 	0.00 days

And that's leading to no adjustment of the Remaining (estimate) time

Which means Beta is taking a greater share of the total Cache.

This is new computer and first time it has processed Astropulse.

AstroPulse v7 7.10 windows_intelx86 (opencl_nvidia_100)
	Number of tasks completed 	0
	Max tasks per day 		64
	Number of tasks today 		12
	Consecutive valid tasks 	31
	Average turnaround time 	0.00 days

And that's leading to no adjustment of the Remaining (estimate) time

Which means Beta is taking a greater share of the total Cache.

This is new computer and first time it has processed Astropulse.

Since all the AP tasks now is highly blanked, the only counters that updates is "Number of tasks today ", "Max tasks per day ", and "Consecutive valid tasks",
but NOT "Number of tasks completed ", and "Average turnaround time ".
You don't have the "Average processing rate" counter yet.

That's by design, and not an error, even though I agree that it should be considered an error. However it would lead to other problems, if highly blanked tasks was
actually counted as "Number of tasks completed ". I'm sure others here (Richard Haselgrove for example) , who fully understand the technical (algorithms) stuff,
can explain exactly what other problems that is. (I'm too old and worn out in my head, to remember :-) )

It's the same for everyone crunching AP here now. If I remember correctly, the tasks has to be <10% blanked before "Number of tasks completed " updates.

AstroPulse v7 7.10 windows_intelx86 (opencl_nvidia_100)
	Number of tasks completed 	0
	Max tasks per day 		64
	Number of tasks today 		12
	Consecutive valid tasks 	31
	Average turnaround time 	0.00 days

And that's leading to no adjustment of the Remaining (estimate) time

Which means Beta is taking a greater share of the total Cache.

This is new computer and first time it has processed Astropulse.

Since all the AP tasks now is highly blanked, the only counters that updates is "Number of tasks today ", "Max tasks per day ", and "Consecutive valid tasks",
but NOT "Number of tasks completed ", and "Average turnaround time ".
You don't have the "Average processing rate" counter yet.

That's by design, and not an error, even though I agree that it should be considered an error. However it would lead to other problems, if highly blanked tasks was
actually counted as "Number of tasks completed ". I'm sure others here (Richard Haselgrove for example) , who fully understand the technical (algorithms) stuff,
can explain exactly what other problems that is. (I'm too old and worn out in my head, to remember :-) )

It's the same for everyone crunching AP here now. If I remember correctly, the tasks has to be <10% blanked before "Number of tasks completed " updates.

Thanks,
My surviving brain cells now remember some of that, but I too fail to understand why tasks with large amounts of blanking are still processed and taking longer to crunch are not counted.

Note. I now have 5 logged against the "Number of tasks completed " tag.
At this rate I am going to have about 200 "Consecutive valid tasks", presently on 83, before I get a realistic estimated processing estimate.