WCG takes great pride in DIRFT [and nobody is perfect]. Difference with WCG, full production, and other projects operating under the Alpha label for months, some years, it will maybe need the set up of a separate Alpha testing segment, so volunteers do not get volunteered without expressly joining any GPU crunch testing.

We've had some back room discussion on this, such as the WCG client package default disabling GPU functions. Think some of that is already included in the 6.6-6.10 clients put out by Berkeley at WCG's request.

Interesting times ahead.

<no_gpus> is part of the <options> in cc_config.xml, since WCG supplies a customized file it's possible to include this if it's really desired...

The BOINC-defaults (client and preferences) is to only run GPU then idle, so users won't see any performance-impacts except if they've explisitely changed this. Also, for all projects with GPU-application (except GPUGRID for obvious reasons...) there's a preference to enable/disable using the GPU.

Neither of these options was available then SETI@home released their 1st. GPU-application in December, but it's included in v6.6.xx, and "only use GPU then idle" is part of standard-BOINC-web-setup.

Now, since WCG uses customized web-pages must enable these options yourself, but wouldn't expect one more or less preference should be a problem.

Making a GPU-application that gives a significant speedup and don't constantly crash is the hard part...