This is one of the reasons we’re looking for alternatives like python or Julia.

Don’t get me wrong, it’s not about the price, we’re happy to pay for functionality and documentation.
But not if the trend is to make things more and more unaccessible

I had no doubt you would find other ways to keep busy if you were not heading to the States this spring.

It will only make a small difference since in your example this line of code is not called as often, but in “Main Loop – Bottom Part” you can eliminate the repetitive call to sqrt() in the inner for loop by precalculating it:

TWO_PI = 2*pi;
SQRT_TWO_PI = sqrt(TWO_PI); 
...
                elseif isKernelNormal
                    fk = exp(-0.5 * (z.*z)) ./ SQRT_TWO_PI);

If I understand your final profile viewer screenshot showing the 13 seconds, the non-vectorized branch under if any(nearby) gets called around 300K times, which looks like 300K calls to sqrt(). This speedup won’t show up in your profiler results (that line is even in the top results now), but it’s another easy speedup some folks may overlook.

In the common case I see that you cleverly avoid using sqrt() at all by instead dividing by TWO_PI at the end of the snippet.

Stay healthy and safe.

Very nice example showing people how to delve in – plus a nice heads up for us to always go back and look at our shipping code. Probably feval was the only option for evaluation at the time the functionality was first introduced. But I’m only guessing.

Hag Sameach and take care!
–loren