thanks for your extensive feedback. if i got you right, we can't state the
outperformance in all cases, because it is measured by an insufficiently
precise function and a relatively short period of time.
I understand your point of view and thank you for your observation. we will
start working o
On Tue, 12 Mar 2024 11:34:40 -
via NumPy-Discussion wrote:
> https://github.com/2D-FFT-Project/2d-fft/blob/main/notebooks/comparisons.ipynb
Hi,
Since you are using a notebook to perform the benchmark, I would advise you to
use:
```
timing = %timeit -o some_function(*args)
```
Because you
i appreciate your correction, indeed you are right, it was my fault.
i changed everything and i believe it is in the correct order of things right
now.
our current best result is
FFT:
-46%(no multithreading, no type conversions) from scipy and +0.37% is the worst
case (multithreaded, no type co
