Thank you, Kevin.

60 stuck units have now been freed up so only 70 remain.

7 days have passed since the last full report. In that time, the last of the ultra laggards has moved on 6 generations to generation 070 and their 3 leaders have moved on 4 generations to 079 and are now alongside the oldest stuck unit.

I now have 73 candidates for the 70 units still stuck. They are generation 079 x 1, 086 x 1, 089 x 4, 090 x 12, 091 x 16, 092 x 7, 093 x 8, 094 x 5, 095 x 4, 098 x 1, 099 x 10, 102 x 2 & 105 x 1. The list reduces daily but may get confused when Kevin releases the rest this week????

There are 62 units listed as extreme. 6 are the ultras, so there are 56 others, which are unstuck units 1 unstuck unit has escaped the extreme range, so 3 unstuck units have yet to be validated.

The last of the accelerated (Priority) generations is 113 and their leader is 117.

The current leading generation is 127.

Each of those leaders has moved on 2 generations so the definition for extreme laggard is still -15 generations with accelerated remaining at -10 generations. However, the leading unstuck unit is yet to achieve that definition.

58,341 units have been validated in the last 7 days (down to 8,334.4 per day).

There are now 2,282,312 units to be crunched to finish the project assuming that a full generation 182 is the last. My target for completion is now calculated as 9 October 2022. That is 8 days later than my last summary, assumes everyone works as now until the last day and reflects the decrease in work returned.

It is likely that we will see the project finish before the end of 2022 due to the efforts to close up the laggards. My guess would be October 2022 assuming those university computers come back on line after their holiday. However, the step change on the unstuck units may delay that as those units are taking longer.

Mike

Mike,

Thank you for your report. Here’s another triplet:

0033554_095.

I’m not sure what the time step is. How do you find out which slot a particular ARP task is in?

Cheers,
Mark

Thank you Mark & geophi

There is a much simpler method to determine the time step. If you are in BOINC Manager there is a Progress column.
With a time step of 36 secs, the task progress advances in increments of 0.02083'.
With a time step of 24 secs, the task progress advances in increments of 0.01388'.
There are only 3 decimal places displayed so with a 36 second time step, the increments are mostly 0.021 and occasionally 0.020. For 24 seconds that would be mostly 0.014 and occasionally 0.013.

No need for any computer knowledge there.

Mike

It seems to be 24 secs for all the unstuck units. That means they are taking at least 50% longer to crunch.

Mike

Thank you, adriverhoef. We now have 14 unstuck units identified. The reduction in CPU time is interesting. What was your 36 sec norm?

Mike