A mere 12h of dddt2 cache will not move me to far towards blue, but the 5days of PV should inch me forward, over the next ten days or so. While my orientation has changed back towards points (the right place), I would still like to see this one out.

There are projects outside WCG that have much longer deadlines... 14-30-60 days...1-2 years but also shorter 1-2-3 days, so it was capped at 10 days as else this would/could have tremendous scheduling issues both for the client as well as for the projects for those doing multi grid crunching more so... particular those grids with large daily turnover in WU and storage needs.

If you have a cache of 10 days and you'd select to include HCC which has 7 day deadline, you be seeing permanent panic whenever a HCC is in cache and since the client would schedule these ahead continuously, the servers would think your large cache machine is still returning fast, to a point that chaos will rule for the client. Too complex for it to handle elegantly, so the recommendation is to at least set the cache lower than the shortest deadline ever occurring for any assigned work for a smoothest possible ride.

The simplified description :D

--//--

You've got it down near perfect. If your deadlines are presently showing 7 days out and assuming there's presently only C type in circulation, your cache is likely over 3 days, which knocks you out of the point 2 eligibility. B Type is 7 days deadline too together with HCC and Beta is 4 days, though latter will be send to anyone enrolled in the testing program, regardless of the cache size.

If your client consistently runs with return times longer than 7 days, you'd not be getting the HCC+B type as the client and server would agree that timely return is implausible **. So, if running a cache of > 7days for longer and switching from DDDT2 to HCC, this would very probably cause a message to be send to say that the device is tardy. When then the "If there is no work for....send anything else" is not selected, the chance of an idle device mounts, if only crunching at WCG, which of course we like all member to do ;)

Happy crunching.

--//--

edit: ** Then the client message/event log show: No Work Sent (Won't Finish In Time)

I am still wondering how many more days we have of new work here.. its definatly a nice rainshower...


I am only sitting at about 3 pages of PV but i also dont have a large cache.

470,000 have validated since last release starting about April 19. Just had a d434 queing up. If this continues to the full, e500, then we could be hitting 700-750k tasks when C-Type dg02 is done.

Taking 22 million for 18 targets, this means about 1.2 million of C-Type to complete for each, but that depends on A and B type... are those all complete for dg02? If not maybe more C is imminent in this round.

Think we're now at a point where it becomes tedious for the techs to keep calling out detail work totals for this science. It's a frequent hands on for DDDT2, so really no automated process to make it easy to know how much there's coming through at any one time, pre- or in-feeder ... at any rate, started to work seriously on getting year 2 on the road, for me badge... i.e. there's as of now more suction ;>)

Still enjoying the hunt.

--//--