I received a "batch" of 10 ARP workunits to one host at about 11:30 UTC today. The interesting thing is they were all _2 versions of generation 142. The next interesting thing is that all of the _0 versions were Server Aborted less than 1 day after sending. Why? No other version had been returned as of abort time. If there was something wrong with the work unit why didn't the _1 versions get aborted since they were sent out concurrent with the _0 versions which assumes they were identical.

Only 1 extreme moved yesterday from 129 to 130 so there are still 320..

1 accelerated escaped to normal. There may only be 6 accelerated moving out of 456.

1,252 normals moved out of 30,965 in the generations being released.

There are now 2,320 held up in generation 143.

Mike

Sunday Report

ARP is running slowly.

The forecast is now being averaged over the last 5 weeks.

All classifications have stayed put..

There are still 3 ultras in generations 21 & 22.

There are now 319 extremes in generations 21 to 131 but only 1 seems to be moving, the rest assumed to be stuck.

There are now 456 accelerated units in generations 132 to 136 and 34,834 normal units in generations 137 to 146. Most of the accelerated units would seem to be stuck - maybe as low as 8 moving.

WCG are now only releasing units in generations up to 142, so the number available to be released has increased.

9,129 units have validated this week.

Based on the last 5 weeks, we would complete ARP1 in April 2027 but the number of units currently being issued is less than the earlier averaged units.

Mike

I'm two hours into ARP1_033717_134_0

Dear ARP1-collectors,

Just a thought. It could be strategy to take care that all moving workunits will finish first. Just letting them run until the end. After that — mind you, still strategy — configure all remaining (stuck) workunits so that they will start moving or - in a worse case - reconfigure them to have them restarted (from the very beginning).

Adri