A smile puts off many pains, judson.

Though there was a big general carry over from Sunday due many clients backing off reporting work (the Ready to Report part), HCMD2 had no visible dip. The Monday morning catch up inclusive [maybe 5-8 CPU years] suggest the project will have it's strongest day today, somewhere in the 65 CPU years range. Visit chart update tomorrow to find how it turned out.

crunch on

Working through some grandchildren for batches 110+114 i.e. there will probably always be some toughees in every batch we do.

Sekerob explained it here...

https://secure.worldcommunitygrid.org/forums/...ad,26183_offset,20#251491

Here a client arrived at a batch 130 child, got past the 60% at 6 hours, but cut off at 12 hours exact indicating it was not getting all positions of the remaining 40%. First for me and blew the client's DCF to 2.73.

The weekly progress update by Nico_B has not happened yet, so no indication how the 'scientists received' progress compares to what's estimated here. Child for 118-127 in queue plus a 141 parent. Well, 141 of 2467 is starting to look like we're beginning to make a dent.

ttyl

edit: typo

Martin, I think that "achieved" is not exactly the right word. 4.4% is the amount of work done and already sent back to our servers. Look carefully at the "Batch completion status" chart and compare it to the "batch number" your client is actually crunching on. You will then have a rough idea of the difference.