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

Programme being killed after 1 interaction #50

Closed
mikeyJ-1999 opened this issue Sep 8, 2022 · 4 comments
Closed

Programme being killed after 1 interaction #50

mikeyJ-1999 opened this issue Sep 8, 2022 · 4 comments

Comments

@mikeyJ-1999
Copy link

Hi, I keep getting this issue after 1 Interaction:

~/src/demcoreg/demcoreg/dem_align.py -max_offset 250 28-06-2012_E_BI.tif 22-04-2016_E_BI.tif

Reference: 28-06-2012_E_BI.tif
Source: 22-04-2016_E_BI.tif
Mode: nuth
Output: 22-04-2016_E_BI_dem_align/22-04-2016_E_BI_28-06-2012_E_BI

Warping all inputs to the following:
Resolution: 2.0
Extent: [-1970264.0, -517090.0, -1899022.0, -482764.0]
Projection: '+proj=stere +lat_0=90 +lat_ts=70 +lon_0=-45 +x_0=0 +y_0=0 +datum=WGS84 +units=m +no_defs'
Resampling alg: cubic

1 of 2: 28-06-2012_E_BI.tif
nl: 17163 ns: 35621 res: 2.000
0...10...20...30...40...50...60...70...80...90...100 - done.
2 of 2: [memory]

Reference DEM res: 2.00
Source DEM res: 2.00
Resolution for coreg: mean (2.00 m)

*** Iteration 1 ***

Warping all inputs to the following:
Resolution: 2.0
Extent: [-1970264.0, -517090.0, -1899022.0, -482764.0]
Projection: '+proj=stere +lat_0=90 +lat_ts=70 +lon_0=-45 +x_0=0 +y_0=0 +datum=WGS84 +units=m +no_defs'
Resampling alg: cubic

1 of 2: 28-06-2012_E_BI.tif
2 of 2: [memory]
Killed

I'm using a Ubuntu Virtual Machine with minicoda 3

@dshean
Copy link
Owner

dshean commented Sep 8, 2022

Hi @mikeyJ-1999. Thanks for filing an issue. This looks like a memory issue. How much memory do you have available on your VM?
Your inputs are relatively large, and assuming float32 or float64, will require a lot of RAM for in-memory warping. Depending on VM OS config, there may also be some monitoring that kills processes occupying lots of RAM.

@mikeyJ-1999
Copy link
Author

Hi

Thank you for the reply

I'm current allocating 10gb of ram to the virtual machine and allocated 250gb of storage. When I try to run the terminal now it closes without giving any errors

@dshean
Copy link
Owner

dshean commented Sep 12, 2022

OK. 10 GB is not much for uncompressed in-memory storage of your large rasters, but maybe OK swapping to disk.

Just to confirm "closes without giving any errors" means that the script successfully ran to completion, or that it prematurely exits without throwing an error?

@mikeyJ-1999
Copy link
Author

Sorry for the cofusion. It closes without giving any errors.

@dshean dshean closed this as completed Sep 12, 2022
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