interp1() broken on GPUs in 2017a?

Hello,

When I run:

interp1( [1;3], gpuArray.zeros(2), single(2) )

I get a pair of NaNs as a result. However, I am reasonably certain that 2 is between 1 and 3.

This problem only appears when all of these conditions are true:

• the 1st argument is doubles
• the 2nd argument is a gpuArray
• the 2nd argument is a matrix, not a vector
• the 3rd argument is a single

If any of these conditions is false, I get the correct answer (zeros). Anyone else seeing this? Does this problem only exist with 2017a or are newer versions also affected?

Answer 1

[Joss Knight]

This is a bug, thanks for reporting it to us.

To work around, make sure the data X and query Xq are the same datatype.