Nothing higher than Tony from my side.

@anhhai
In my post on Dec 31 I have clearly shown how I was playing this big guess game intended mainly for anxious badge hunters:
So, the rough estimate of 5 batches per day is still conservative (from a badge hunting viewpoint ) and using it that gives at least:
- 41 days until receiving parents for batch 2467
- 46 days until receiving children for batch 2467
- 47 days until receiving grand-children for batch 2467
- and probably 56 days for clearing everything.

The first three numbers were supposed to be a minimum number of days before seeing the first WUs for batch 2467 (the last one). They were strictly based on a progress of 5 batch numbers per day and when reading that again I realize that 46 and 47 would be probably 42 since there will be nothing new to distribute but child and grandchild WUs once the last parents will have been sent.
So the big number (56 then, 47 today) is of course for having distributed all new WUs, children and grandchildren included. Then we should not see anything else than repair jobs.

And don't forget that estimates for parents depend completely on decisions made by the techs: if (for whatever reason) they would prefer to get rid of parents faster they only need to distribute them all during as many days as necessary and then we would have to deal only with child and grandchild WUs.
But the global duration would be more or less the same.

thx JmBoullier!!

This will be down to the wire for me for both HCC and HCMD2. Hopefully I will be able to reach my goal of 125 yrs and 50 yrs.

It sent out up to 2286 before returning to child units.

From my reading, seeds can be generated quasi real time and is not depending on parent batch completion... in short, when quorum of a parent is complete, a child could be created shortly after, which is why we see the constant back and forth. Mind you, for efficiency this process is likely running on a schedule, possibly with a priority assignment in the feeder, so when there are seed batches, they'll go ahead of parents. This promotes the clearing of a whole batch number, so it can be migrated to the master database and uploaded to Paris. Remember, batches kept live [that what shows on the Result Status pages] has a performance impact on the scheduler, so the driving strategy is probably dictated by that. The Friday reporting allows to guesstimate the range that is live and enter this into the pot for computing progress and days left [for any non-repair tasks].

46 days left and holding at 30 [or skipping forward to 30 if techs give the formal alert]... we make it up as we go :D

--//--

I appreciate all the discussion about the end date. I'm on a sapphire run and I estimate I'll need 35-40 calendar days. So, I've been feeling a little nervous seeing the remaining time figures fluctuate as I'd hate to end the project just short of a sapphire.