-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory Issues #299
Comments
Hello, But there is another problem associated to this error, because you're not able to control which datatype, like numpy.float32, the Pykrige program is using. It seems to always default to numpy.float64, which is in most cases too memory expensive. |
@mihtm13 , Thanks but I couldn't get to that line because I get an error on the line below. OK = OrdinaryKriging(X[:, 0], X[:, 1], y, variogram_model='linear', verbose=True, enable_plotting=False) |
After some digging there seems to be an issue with the "ok.py", where for most Numpy functions inside the "OrdinaryKriging" class no dtype is defined. Numpy will then default to numpy.float64 which increases memory consumption drastically. If there would be a way of using numpy.float32 you'll be able to half the memory cunsumption. I think this cloud be a new feature, to be able to define the dtype in the |
@MuellerSeb Hello, I want to use your kriging interpolation method but I'm getting a memory error. How can I overcome this? However, although I waited for the same data in the SmartMap plugin in QGIS, I got a result. Is there anything I can change or suggest I make?
The text was updated successfully, but these errors were encountered: