The revised total according to Dashboard as of 30/11 is 111 days. A increase of 3 days

Smells like about 6 batches per day are completing. With 340 left, that's ~ 60 days, at present production... end December / early January for the 30 days last new work call, last result return, about 90 days from now... the Dash now says 87.

Priority does as yet not seem to have been upped from medium... running at about 44-46 CPU years per day, same as as the medium set for DSFL.

--//--

I'd say, 30 days *new batch* call i.e. for parents. Not winking back, this science is seemingly still, as I said, on medium i.e. could go imminently much faster. Looking at Jean's post, 2130 parent and 2125 grand-child closely passing by [i.e. a gap of 5 batches], remember we resumed at 2072 less than 2 weeks ago, slowly, so you decide for yourself if still pursuing badge goals, how much time these input factors will buy at present 6 batches per day.



--//--

Ok, should be Friday by board time now.

I decided to draw a cache to see what what batches I'd get (normally only operate on .1 day buffer and do a project mix) and in my cache I currently have:

Parent workunits for 2131, 2132, 2133
Children for 2078, 2079, 2083, 2085, 2090, 2091, 2118, 2119, 2129, 2130, 2131
Grandchildren for 2078, 2083, 2087, 2093, 2095, 2096, 2100, 2116

Thanks all. I'll plug these in... then watch what that does to days left ;D

--//--