Another Sunday, so another full report.

The remaining stuck units have all been restarted. However, 3 had to be restarted from the beginning. These 'new' ultras are currently in generations 000, 001 & 002.

Only the last of the 'old' ultras is still discernible in generation 086. The rest are mixed in with the other unstuck units.

There are 122 units in the extreme range of which 113 are listed by WCG. That means 9 have yet to move since being restarted.

The definitions of extreme, accelerated(priority) & normal have all moved on 1 generation since last week to 118, 123 & 133, respectively, but might move on another tomorrow.

55,752 units have validated in the week (7,964.6 per day) so wenow have 2,055,155 remaining until the end of the project. Maybe we will crack the 2 million next week.

My calculated completion date is now 21 October 2022. This assumes that a full generation 182 will be the last and everyone continues as now until the end. If those University machines return from their holiday that might shorten the timespan but it currently means that those 3 new ultras will have to be validated every 34 hours average for the whole period. The end of the year would be more likely.

Mike

Thank you, entity.

Please see the postings yesterday from Kevin and myself.

Because of the reset of 3 units to generation 000, the extremes have had a further acceleration. They were on half the original deadline of 7 days. That has been halved again to 1.75 days plus the extra 1 day leeway. It seems they couldn't differentiate those 3 from the other extremes so have had to accelerate them all.

These 3 new ultras need to be validated every 34 hours for the rest of the project if they are to finish by October.

It is now even more important to minimise the queues to avoid the problem you mention. I think that the project limits should now be a maximum of one spare in excess of the number actually running.

The units are readily available if not immediately available so there is no need for a significant queue. One extra should be enough to tide over until the next download.

Mike

Thank you, Sgt.Joe.

I presume you mean 2.75 days.

Mike

Reporting a sighting of this one ARP1_0033320_107_1 It has 36 second time step.

Should be completed in about 23-24 hours.

I did see those. That's why I'm not asking what changed.

I can't do that on my 128 thread machine because project limits don't allow the plus one but is manageable. It would require extreme babysitting on the 256 thread machine due to project limits (I can't get 128 WUs). You can't run half the threads because you can't get enough work without setting project limits to unlimited and all that entails. App_config won't help in that case.