Open GatesDupont opened 6 years ago
@GatesDupont Did you ever solve this issue? I was just rerunning some code that worked previously with a newly updated landcover raster and now have this error and am trouble interpreting what it means.
EDIT: Upon further investigation, this looks to be a memory allocation error. Likely solved by using smaller rasters, fewer in a stack, or running it on a machine with more memory.
@mvevans89 I didn't solve the issue directly. I ended up using a workaround that minced up the land cover raster and ran the velox extraction in parallel across 16 cores. Works great, very fast, but a bit tedious to code.
@GatesDupont do you have the code that you ran for velox in parallel? I'm running into the same issue and having trouble implementing it. TY!
Hi @John-Mola – Sure, I just saw your email on your website, sending it there now.
@GatesDupont would also be interested in seeing your parallel code, just ran into this issue today
@GatesDupont facing the same issue right now. Although I am working on a 360GB RAM R cloud, velox is producing these errors. Do you mind sharing your code with me as well? Thanks!
Hello,
I'm trying to extract raster data from a grid of points (right now, n=8), but I keep getting am ambiguous error message, and I don't have any idea why. This seems like a fairly straightforward operation with Velox. I guess it could be something wrong with my code? I have followed the vignette pretty closely, however.
Any help you could offer would be greatly appreciated!