Specify output array and in-place operations?

[eickenberg]

Either I am missing something or it is not present in this package:

Is there a way to specify target output arrays for the fft? If not, is this planned?

Cufft can do inplace fft, which one could then invoke simply by specifying the output array as the input array.

Having this would make memory-intense work which requires precise control possible. Related to this: Are the cufft plans cached somewhere in memory or on gpu and reusable? Are there plans to make these accessible?

[eickenberg]

Looks like plans are destroyed always

pytorch_fft/pytorch_fft/src/generic/th_fft_cuda.c

Line 84 in 2ca24e3

cufftDestroy(plan);

Any plans to make it possible to keep them?

[riceric22]

There is not currently a way to specify the output tensor, however that is a fairly simple change to make (the internal C call allows specified output already, so this is just a matter of adjusting the python interface).

Cufft plans are, as you pointed out, currently destroyed. I hadn't thought about making then reusable and it didn't seem to be that costly, do you have a way in mind of exposing the plan through the interface?

[eickenberg]

It would have to be persisted in a pytorch module or something (like e.g. nn.Conv2d stores its own weights) and initialized when the object is created, with a specific shape. There could be an option to keep or not the fft plan. The thing is that for big ffts recreating the plan every time can actually make it slower than even a normal implementation on CPU. So for large amounts of data it makes quite a difference.

…

On Mon, Nov 20, 2017 at 3:06 PM, Eric Wong ***@***.***> wrote: There is not currently a way to specify the output tensor, however that is a fairly simple change to make (the internal C call allows specified output already, so this is just a matter of adjusting the python interface). Cufft plans are, as you pointed out, currently destroyed. I hadn't thought about making then reusable and it didn't seem to be that costly, do you have a way in mind of exposing the plan through the interface? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABPwCz04PruHBwgC6Pzi9NDagL7cyWDKks5s4gYAgaJpZM4Qjjpj> .