Does anyone know of a single list of all BOINC projects that utilize GPU's?

There are to date only three, GPUGrid, Seti Beta and Seti@Home.
I'll be updating that list in my CUDA FAQ as showing in my signature.

---

You can Add Aqua@home to that list!

http://aqua.dwavesys.com/

Benefits - it facilitates slower CUDA devices as the completion deadlines are longer than GPU-GRID. Although it is a developing project it is developing rapidly and there is plenty of support in the forums for new contributors.

I expect the World Community Grid will be on the list within the next few months. The Milkyway@home appears to be preparing to get there but I think they are still Alpha testing (June 09), perhaps next month?

There are to date only three, GPUGrid, Seti Beta and Seti@Home.
I'll be updating that list in my CUDA FAQ as showing in my signature.

Which lists Aqua as CUDA for win only... which I don't think is the case today. However I quit running Aqua Cuda on my Linux machines so I can't confirm state of affairs today... however their "Apps" link shows Linux 64b Cuda

Also MW is Windoze only on their ATI (CAL) apps.

---

- da shu @ HeliOS,
"A child's exposure to technology should never be predicated on an ability to afford it."

AQUA have temporarily suspended development of their CUDA apps (which were much slower than their CPU apps). They show no sign of releasing new work targeted at CUDA, so the only stuff available will be the occasional (very rare) resend.

They plan to start testing a new CPU app 'next week' (it's been 'next week' for several weeks now), and at that point will cancel all existing work from the database, so even the limited CUDA resends will stop.

Whether/when they will restart CUDA testing is anybody's guess.

Collatz (which isn't shown as a project to join from the client but is out there at http://boinc.thesonntags.com/collatz/ is the current broadest support project out there.

One can run CPU projects, and both ATI and CUDA GPU projects. Further, unlike MilkyWay (which does support ATI, CUDA and CPU projects), Collatz doesn't require double precision GPU cards. So those with older slower cards (or newer less power consuming and pricey cards for that matter) are supported over there.

The downside with Collatz -- it is CUDA 2.3 and the ATI support requires the 6.10 client. In fact, if you are running an ATI GPU -- you would want to be a 6.10.9 and up plus of course a relatively new Catalyst driver.

I've one system running Collatz ATI support using 6.10.11, Windows 7 RTM and the 9.9 Catalyst drivers.

On the ATI GPU front, it is apparent that the folks over at GPUGrid are not going to support ATI GPU anytime soon....

Aqua project folks utilize what I call 'Airport time' -- you have a delayed flight, the service desk indicates they will begin the delayed boarding in 20 minutes. You return 20 minutes later and ask again, they give the same answer, the delayed boarding will begin in 20 minutes. Turns out, the answer at Aqua is 'next week' -- anytime you ask ;)

They plan to start testing a new CPU app 'next week' (it's been 'next week' for several weeks now), and at that point will cancel all existing work from the database, so even the limited CUDA resends will stop.

On the ATI GPU front, it is apparent that the folks over at GPUGrid are not going to support ATI GPU anytime soon....

It's not that easy to whip up some ATI applications. Your code may work perfectly fine on a CPU, you may even have a wobbly CUDA app built with it, but then to also do an ATI app is quite difficult.

I've been trying to build one for DD for the past month or so, when I have finally made a stable dynamic linked library, the executable won't build. I can't use the latest Brook/CAL libraries as the code I have is geared up for Brook/CAL 1.2, any higher and the build will break from point one. 957 build errors. Fun.

So I know what they're into.

---

also Milkyway@home, PrimeGrid, The Lattice Project
it shows up with a green icon in the Boinc Manager

More generally, what we really need is a matrix that shows GPU vs. Project vs. OS. I suggest we start one.

Such as is shown in the FAQ on the subject?

---

We need one that is a matrix of project vs. platform vs. GPU.