Wish list

Message boards : Number crunching : Wish list

To post messages, you must log in.

AuthorMessage
Profile robertmiles

Send message
Joined: 13 Oct 09
Posts: 105
Credit: 21,462
RAC: 0
Message 1547 - Posted: 15 Oct 2009, 5:41:06 UTC

Some things I'd like to see:

Modify your home page to make it more obvious if you're planning to offer GPU workunits any time soon.

Also, if you do, modify the names of the GPU applications to make it more obvious what type of GPU they use. For example, you could adopt GPUGRID's convention of adding (cuda) to those which can use CUDA 2.2 or older, and (cuda23) to those which require CUDA 2.3 instead.
ID: 1547 · Rating: 0 · rate: Rate + / Rate - Report as offensive
Profile Ageless
Avatar

Send message
Joined: 11 Apr 09
Posts: 172
Credit: 7,631
RAC: 0
Message 1548 - Posted: 15 Oct 2009, 6:02:22 UTC - in response to Message 1547.  

For example, you could adopt GPUGRID's convention of adding (cuda) to those which can use CUDA 2.2 or older, and (cuda23) to those which require CUDA 2.3 instead.

That isn't GPUGrid's convention, but BOINC's application plan_class instead. It'll also show ATI (CAL 1.2.1 and below), ATI13AMD (CAL 1.3.0 with AMDCALxx.DLL files), ATI13ATI (CAL 1.3.0 with ATICALxx.DLL files), ATI14 (CAL 1.4 and above).

See the Coprocessor application page and the Plan Class pages in the BOINC Wiki for more information on that.
Jord

'Cause you seem like an orchard of mines, Just take one step at a time.
ID: 1548 · Rating: 0 · rate: Rate + / Rate - Report as offensive
Profile Jack Shultz
Avatar

Send message
Joined: 10 Apr 09
Posts: 503
Credit: 120,150
RAC: 0
Message 1578 - Posted: 18 Oct 2009, 17:21:35 UTC - in response to Message 1548.  

I'll be learning a bit more about GPUs next week at the BOINC workshop. It will be held in Barcelona and I'll finally get to meet some of these guys from GPUGrid! Application plans is something of a boinc naming convention that, well I have not explored fully. It is possible to create custom plan names to make it more obvious what we support.

My challenge since June has been trying to make a version of GROMACS' mdrun app integrated into our project. It has proven difficult. I first had to get some help from the developers of OpenMM project to make their Zephyr version of gromacs accept --device m command line option. Then once I had that, it still did not run using the Cuda platform. It is supposed to work using environmental variables detecting the presence of certain DLLS. It never worked that way and I also tried setting the paths to the current working directories.

I cannot make any predictions on when the cuda will work, all I can say if I start working on it, I won't be able to work on other issues. Enlisting help from volunteer developers and testers is beneficial. Ageless has already had some mixed results in compiling this software, but it has proved challenging.
ID: 1578 · Rating: 0 · rate: Rate + / Rate - Report as offensive

Message boards : Number crunching : Wish list


©2017 All rights reserved | Design by Digital BioPharm Ltd