Ranjan Anantharaman

Correct, I'd have to do this for all functions. I think I can capture this in the docs.

If you're using the OpenCL backend, that probably has to do with the different in the value returned by clFFT and FFTW. I'm not sure what we can do about...

Do you think it's worth noting in the README about the differences in the values?

I've added notes on both.

You're right, `var` should return a `Float32` if it's a `Float32` Array. I'll fix that.

My tests haven't ever failed though. This is quite strange: does it have something to do with `Device[0] has no support for OpenGL Interoperation` ? I've never seen that message...

Probably. I haven't used Beignet before, so if those floating point errors are possible on that platform, I suppose `@test_approx_eq` makes sense. Does that work for your platform?

Hi @alha02, thanks for pointing this out. This is an error in the original C++ library, and I've filed a bug report here (https://github.com/arrayfire/arrayfire/issues/1660).

cc: @shashi

I find that rounding seems to help convergence here. Introducing a rounding step that rounds everything to 15 decimal places seems to aid convergence