You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed in the source code for DirectionalVariogram.py that the @jit decorators have been commented out. Are there any immediate plans to accommodate GPU use with gstat?
The text was updated successfully, but these errors were encountered:
Yes, the jit decorator is all over the place and numba is also a dependency for a few versions now. Mainly, because I am using it in the skgstat.estimators module to speed calculations of Variograms with large input data sets up, at the cost of a bit overhead on small samples.
I am not really sure if that is a good idea though. I am running into issues while developing with these jitted functions all the time and it sometimes really slows me down in development. On the other hand, it's working most of the time. Also, I am not sure if all jit's are placed in meaningful places. To do that correctly, I need to build a benchmarking framework for the unittests and see, where a jit can really speed things up. I.e.:
in _direction_mask; line 490
there I think it might be really useful, but I couldn't manage to make it work with the shapely objects.
in local_reference_system; line 432
I don't think that jit would make any difference as this is not as slow as expected and the numpy usage is fairly fast here.
The last point to consider is that there a more ways to get parts of the code compiled. Cython, for example, is just another very popular solution. I also have a lot of old Fortran code here and thought that maybe I can incorporate that somehow.
So to answer your question, I am not planning to implement more numba usage on the short term, but mainly because of lack of time. So if you want / need that, we can surely discuss how and where to implement which solution and how to do it in a systematic way.
I noticed in the source code for DirectionalVariogram.py that the @jit decorators have been commented out. Are there any immediate plans to accommodate GPU use with gstat?
The text was updated successfully, but these errors were encountered: