First, sorry if my responses seem a little bit slow.

Now, the main question that folks are asking is,

"IS THIS THE END OF THE WORK?"
Short answer "NO"
Long answer "No, there is still planned to be over 100 days of work left for the grid. This could be longer or shorter depending on actual number of final batches we get from the researchers AND how fast everyone can process the work units when they're available.

(sorry for caps, not screaming, just wanting to make sure members see the question that seems to be causing the most grief. )

Onto the other questions:
"Why was there not more of a warning on running out of work?"
Answer: "We have been processing most of the work units as they have become available from the researchers. With the high volume of batches we were doing each day, the researchers have been keeping our backlog of a few days. Thus if there is any sort of hiccup in the process it causes an issue similar to what we are seeing today. We are working with the researchers to hopefully get that few days backlog up. But there are logistics behind how the backlog on their end is created, which is something I have no knowledge of so any comments from me on it would be a total guess."

Please note that we are working with the researchers towards getting new work loaded and as soon as it is available we will let everyone know. The estimated time for this could be anything from 1 day to next week. As you can probably guess, we really don't have a good ETA for new work to be sent out.

Thank you for your patience as we work through this issue,
-Uplinger

Thanks for letting us know, Uplinger

To the professional WCG paid staff:

While no one elected me spokesman, I'm taking the role. Thanks for your hard work, technical expertise and professional attitude. Please take a well deserved rest over thanksgiving. What ever is going on with HCC GPU can wait until Monday. My GPUs have spundown and my CPUs are quietly crunching away on other projects. You do the same.

the volunteers

AFAIC, think WCG is better off if electing to get a good swath of data in and [I've mentioned this before], maybe consider a 1st of month / 16th of month release. This way crunchers can adapt and know what to expect].

On Back-Up projects, reading various, but the proper back-up project setting [as of client 6.10.58] is a resource share of 0 (zero)... not sure if all projects support a zero setting yet... they needed to upgrade the server software ass well. When the client is out of work, and only when out of work, will it go fetch work from the backup project(s), and only so much to keep all threads busy, that otherwise would be idling. Soon as the main project has work again, the backup project is parked [that I've never seen and rather if the backup project has work **, to finish it... why else have a backup!]. Auto-Parking or not, think it is proper to finish the fetched work. If not, don't keep projects waiting or be served with aborts, because A/B/C had work again.

One day asked knreed to implement a delayed kick-in of the "if there is no work for... ", to only send alternate work if the client has run dry of WCG work. This combined with the zero resource for backup project would give the maximum "favored research".

edit: ** already running on the client.