Thanks to gb009761 for the support and to uplinger for your labors!

Dry again !!

10/15/2015 7:31:53 AM | World Community Grid | Scheduler request completed: got 0 new tasks
10/15/2015 7:31:53 AM | World Community Grid | No tasks sent
10/15/2015 7:31:53 AM | World Community Grid | No tasks are available for FightAIDS@Home - Phase 2
10/15/2015 7:31:53 AM | World Community Grid | No tasks are available for the applications you have selected.
10/15/2015 7:31:56 AM | World Community Grid | work fetch suspended by user
10/15/2015 7:32:05 AM | World Community Grid | work fetch resumed by user

Spout23

And since the validator for FAHB has been off since at least 19:29 there are no next generation tasks being generated either, that is if that validation for credit is a requirement for the next gen.

Kay, did you really have to slow down the validator on Thursday, to get many to be recorded on Friday, so you would get closer to your 100K FAHB results in a day [Just kidding, but this morning with 223 years was the highest session total since long long time, 49 years / 30K results for FAHB * ;]

Now I'm going to type this slowly, as to maybe get an answer [3rd try].

I'll do this in double spacing the way Americans and English ** seem to prefer the printed word these days, so maybe they can dump all the 'in between the lines nonsense there, that ain't there.].

Hypothetical: If a result is near it's mature deadline, 96 hours after submitting, and at say 80%, 90%.

Will the next trickle, which puts it -over- the deadline, be allowed to finish in overtime?

This before the next gen result is created.

* That's 14.41 hours average per result. If 60K is being returned today 30K*2, it would imply with the 120K issued at any time [stemming from 1st gen], the 100K step cycle equivalent is back in 2 days. Not shabby.

** Don't know about the Welsh, the Scottish, or the Northern Irish ;]

To expand on my point / query example (others may have expressed the concern differently):

1) Result is at 80 or 90 percent and at 95 hours trickles up
2) Continues on with the 9th or 10th 10K block
3) Deadline is reached at the 96th hour

Will it be soft- or hard-stop instructed?

Is there some call-home maybe that tells client to check in, say every 30 minutes? If hard stop instructed at 96:00 hours, but there's no reconnect until the 97th or 98th hours, some part would go to waste [the feared 9.99%]. Some deadline extension rule would optimize the situation further to make that time of use, even lesser duplication. Maybe there could be code inserted to autonomously stop at 80-90% ** and the next 10K block going over the 96th hour i.e. not wait on the comms to happen.

Anyway, with 4 days standard, running a smaller than 2 day buffer is recommended as else the client goes in EDF state anyhow. So far allow 4-5 tasks in buffer, 2 concurrent app_config, and the 3rd-4th task seem always to be running against the 72 hour clock. All have made it so far, but it's only because I've aborted several before hand as they would not possible have gotten at 70%/72 hours first threshold.

** Similarly, CEP2 goes to 18:00 hours and is hard stopped. Can't there be logic to just skip if by extrapolation of the Nth job time in progress the 18:00 does not lead to completion. Yes we get credit, but the last job running whilst hitting 18:00 is incomplete. Is that piece actually included in the uploaded data?