Hello, I am experiencing an error that can be reproduced with the following lines:
using Interpolations, CUDA, Adapt
N = 5
x = range(0f0, 1f0, N)
y = rand(Float32, N)
itp = interpolate((x,), y, Gridded(Linear()))
cuitp = adapt(CuArray{Float32}, itp);
xp = range(0f0, 1f0, N)
u = cuitp.(xp)
I do not know if this is a bug from Metal and oneAPI or if it is the expected behaviour.
What is strange is the fact that it only fails for Metal and oneAPI.
Note that this works for all backends:
using Interpolations, CUDA, Adapt
N = 5
x = collect(range(0f0, 1f0, N))
y = rand(Float32, N)
itp = interpolate((x,), y, Gridded(Linear()))
cuitp = adapt(CuArray{Float32}, itp);
xp = rand(N); xp = adapt(CuArray{Float32}, xp)
u = cuitp.(xp)
But I need input nodes to be ranges instead of arrays, to avoid extra allocations.
Thank you, I really appreciate what this package offers and it would be awesome to put a solution to this :smile:
Cheers,
Pablo
Hello, I am experiencing an error that can be reproduced with the following lines:
This works with CUDA and AMDGPU arrays but, when:
or:
The following errors appear:
Full stacktrace is here.
I do not know if this is a bug from Metal and oneAPI or if it is the expected behaviour. What is strange is the fact that it only fails for Metal and oneAPI. Note that this works for all backends:
But I need input nodes to be ranges instead of arrays, to avoid extra allocations. Thank you, I really appreciate what this package offers and it would be awesome to put a solution to this :smile: Cheers, Pablo