-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPU Support #15
Comments
Since we define our own version of
What are your thoughts on a fix for this? I would have imagined that it would be straightforward to modify these to just return a similar kind of array to whatever is passed in as an input, but perhaps I'm missing something? |
The problem with
so, I suppose a simple fix would be to replace the current implementation
with
|
Hmm that's unfortunate -- it would be a shame to move to a mutating implementation. Another option would be to create a function |
It looks like the reason it doesn't work is that GPUArrays can only broadcast over wrapped array types if the wrapped array is also an I think you're right - we'd need a custom
although that would introduce a dependency on I don't see an easy way to fix it in general though since wrapped arrays have to be dealt with explicity (see this and related issues). So, I think you'd have to somehow deal with wrapped fill arrays explicitly as well? A more general version of the above using
|
The issues I know of that currently prevent GPU support are:
Vector
fields and add vectors constructors KernelFunctions.jl#299Distances.jl
doesn't work with CuArrays Quite different performance of pairwise on CPU vs GPU JuliaStats/Distances.jl#143mean(fx)
andcov(fx)
return standard arrays (not CuArrays)The text was updated successfully, but these errors were encountered: