Why the Stat's export can't be automated like most other projects is puzzling. Manual export on a periodic basis is still more work than an automated script.

It is normally run automatically though on a weekly basis rather than daily like many other projects. (Macs are an exception because of a problem with the app that means the trickles that the credit is based on don't work properly meaning credits for them are based on completed tasks.

The script to calculate the credit takes the best part of a day to run which is why it was changed to weekly so as to use up less resources.

Running the script manually is reserved for when it hasn't worked automagically and for working out bugs in the credit system.

Or that is my understanding as a volunteer cruncher who has followed discussions here and in other places over many years.

Yep, Dave's right about this.
I suspect that the current problem, which started a few weeks ago, is due to the ongoing infrastructure changes going on in the University of Oxford. Which is a large part of the City of Oxford.

Last year we had for months not enough (or properly set) Linux users to crunch the MOSES II TRIFIDS WUs, and in the end they were pulled out (for some reason)

This is not a complaint.

I have my Linux machine ready and willing to run any ClimatePrediction work. But for the reasons already described, they are sending me none.
I finished the last ones 2013-10-29.These were Weather At Home 2 (wah2) v8.12
i686-pc-linux-gnu.

That is all I have been getting since 2016-03-14 when I got some UK Met Office Coupled Model Full Resolution Ocean v6.07 i686-pc-linux-gnu units that mostly failed, but some are still waiting for validation.

---

That is all I have been getting since 2016-03-14 when I got some UK Met Office Coupled Model Full Resolution Ocean v6.07 i686-pc-linux-gnu units that mostly failed, but some are still waiting for validation.

I may well end up pretending the last of my three machines is Wondpws by installing Wine on it as I have with the other two :(