[Numpy-discussion] GPU Numpy

Nicolas Pinto pinto@mit....
Fri Aug 21 19:30:12 CDT 2009


Agreed! What would be the best name? Our package will provide non-pythonic
bindings to cuda (e.g. import cuda; cuda.cudaMemcpy( ... ) ) and some numpy
sugar (e.g. from cuda import sugar; sugar.fft.fftconvolve(ndarray_a,
ndarray_b, 'same')).

How about cuda-ctypes or ctypes-cuda? Any suggestion?

At the same time we may wait for Nvidia to unlock this Driver/Runtime issue,
so we don't need this anymore.

Best,

N

2009/8/21 Stéfan van der Walt <stefan@sun.ac.za>

> 2009/8/21 Nicolas Pinto <pinto@mit.edu>:
> > For those of you who are interested, we forked python-cuda recently and
> > started to add some numpy "sugar". The goal of python-cuda is to
> > *complement* PyCuda by providing an equivalent to the CUDA Runtime API
> > (understand: not Pythonic) using automatically-generated ctypes bindings.
> > With it you can use CUBLAS, CUFFT and the emulation mode (so you don't
> need
> > a GPU to develop):
> > http://github.com/npinto/python-cuda/tree/master
>
> Since you forked the project, it may be worth giving it a new name.
> PyCuda vs. python-cuda is bound to confuse people horribly!
>
> Cheers
> Stéfan
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>



-- 
Nicolas Pinto
Ph.D. Candidate, Brain & Computer Sciences
Massachusetts Institute of Technology, USA
http://web.mit.edu/pinto
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20090821/77da036c/attachment.html 


More information about the NumPy-Discussion mailing list