There should be some way to provide a path to a file containing a pre-created FFTW wisdom in the config file when running the standalone code. As currently written, it cannot be provided under either the alogrithm or mesh blocks as both lead to unrecognised keyword errors during initialisations. This negatively impacts the speed of FFT reconstruction when running the standalone code.
In addition, there should be a functionality provided to write the wisdom file created during a run to file – I think this could be simply by writing to a file called something like wisdom.<nmesh>.<nthreads>.npy in the run directory by default, maybe based on a user-provided save_wisdom option in the config if necessary.
Finally, it would make sense for the code to check for the existence of this default wisdom file in the run directory, and to use it even if no wisdom is provided by the user.
There should be some way to provide a path to a file containing a pre-created FFTW wisdom in the config file when running the standalone code. As currently written, it cannot be provided under either the
alogrithmormeshblocks as both lead to unrecognised keyword errors during initialisations. This negatively impacts the speed of FFT reconstruction when running the standalone code.In addition, there should be a functionality provided to write the wisdom file created during a run to file – I think this could be simply by writing to a file called something like
wisdom.<nmesh>.<nthreads>.npyin the run directory by default, maybe based on a user-providedsave_wisdomoption in the config if necessary.Finally, it would make sense for the code to check for the existence of this default wisdom file in the run directory, and to use it even if no wisdom is provided by the user.