Below is the reason for the slow-down. They (WCG) basically had some sort of problem transferring work back to the researchers so they reduced the number of WUs we were crunching for a few days.


https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,31127

jochrupp, The WUs we crunch today are processed by the scientist tomorrow. This means that there is always a delay from the scientist point of view on when a slowdown or speedup happens. Since it was resolved on the 13th, The scientist will start noticing it a few days later (14th - 29th analysis period)

For me, 4 inputs are used to compute a best present progress.

1: The batch we're crunching real time... the last I saw was 1599, but not participating presently, so don't know which is the last actively crunched batch. Usual one or the other poster has a current WU name in a message to reveal that.
2: Is the work parent, child, grandchild, to est. how far we're into a batch.
3: The WU total at top of this page http://graal.ens-lyon.fr/~nbard/WCGStats/ . This is the net from all quorums.
4: The WU total per the project page: http://www.worldcommunitygrid.org/stat/viewProject.do?projectShortName=hcmd2 An assumed error rate is used to derive a ''field'' net in relation to point 3 above.

This goes into the frier which throws out a ''real time'' percent progress estimate which can be found in the WCG dashboard chart (link returned in my sig).

Commonly, we're about 1.2-1.5 percent ahead of the "official" progress value, but that depends on how current the info at pages, point 3 are... could be more too.

Often times, when other sciences at WCG have an issue, it's HCMD2 that picks up a major portion of the diverted crunching contribution, and sure enough, HCMD2 is running at a 7 day average of 98 TFL, biggest contributed science at WCG. Chart 4 (WCGSHR) in the sig-link depicts this best.

--//--

edit: completed an unfinished line

1704 is the highest parent I can find in my queues.
Grand-children range from a single 1596 to many 1700 and 1701.