Skip to content
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

Potential clipping and tiling issue with focalCpp for large rasters on Linux #479

Closed
ailich opened this issue Jan 10, 2022 · 1 comment
Closed

Comments

@ailich
Copy link
Contributor

ailich commented Jan 10, 2022

I believe there may be an issue occurring in terra::focalCpp for data too large to fit in memory (potentially specific to Linux systems). While I get the correct result on a Windows computer with 16GB of RAM and another user is getting correct results on a Linux computer with 128GB of RAM, their Linux computer with 16 GB of RAM is providing clipped/offset/striped outputs from the call to focalCpp and on an Ubuntu VM with ~10GB of RAM I'm getting clipped/offset results on two different functions that use focalCpp internally. When I overlay the original data with a single layer of the output you can see the two do not match up. Additionally, on Windows focalCpp for the second example results in a memory exhausted error. For more details see ailich/GLCMTextures#12. The data set is available here .

GLCMTextures Example

Using the function glcm_textures from the GLCMTextures package.

Overlay of the original data and a single layer of intermediate surface calculated with focalCpp plotted from debug mode on 10GB Linux VM
r_overlay

Intermediate surface calculated with focalCpp plotted from debug mode on 16GB Linux Computer
148659660-999fec9b-aa38-4f32-9a74-21bab4ca8a99

Surfaces from a 16GB Windows Computer (correct)
148409431-4df258c9-6318-496d-bd42-32504114b280

MultiscaleDEM Examples

Using the function Qfit from the MultiscaleDEM package

Overlay of a single layer of the output onto the original data from the 10GB Linux VM
qfit_overlay

Windows 16GB Computer
Error: memory exhausted (limit reached?)

@rhijmans
Copy link
Member

Closing because this is the same as #519 (fixed but awaiting confirmation)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants