ARP1_0034392_089_1 errored out on my system, and also on whoever had the _0, as well as the _2 earlier noted. Looks like we have a stuck one? It got to the same place on all of them, and my system has been rock-steady with 32 GB of ECC RAM.

I don't have any way of knowing. It was 36 when I saw it running, at least.

Thank you, Mark.

That could be an unstuck unit or the leading ultra.

Mike

Thank you, Kevin.

There were only 70 stuck units but 2 more seem to have joined them. 33711 has errored 6 times in generation 099 and a 7th aborted by server. 34392 has errored at least 3 times in generation 089.

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 079 and caught the last stuck unit. Their leader is now progressing through the stuck units.

The trailing unstuck unit is also in generation 079. Their leader is now somewhere in the accelerated (priority) units.

There are now 64 units listed as extreme. 6 are the ultras, 56 are unstuck and 2 others. The leader is in generation 115.

The last of the accelerated (Priority) generations is 116 and their leader is 120.

The current leading generation is 130.

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.

57,391 units have been validated in the last 7 days (up to 8,198.7per day).

There are now 2,168,225 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 13 October 2022. That is 4 days earlier 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.

The step change on the unstuck units has now reverted to 36 seconds so they are now being crunched faster, but we expect the remaining stuck units to have the same treatment.

Mike

Thank you, Mark.

That is confirmed. 15 days to move 6 generations is not very fast for a triplet, but some of those would have been 24 second time steps.

Mike