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

[Help]: sbas.compute_align() freezes in low RAM environment #172

Open
georgeboldeanu opened this issue Oct 2, 2024 · 3 comments
Open

[Help]: sbas.compute_align() freezes in low RAM environment #172

georgeboldeanu opened this issue Oct 2, 2024 · 3 comments

Comments

@georgeboldeanu
Copy link

Hello Alexey! I try to run some processing chain for a combined SBAS and PS analysis on a small AOI, more exactly 4 km2. I do this using the latest docker image, which has the following pygmtsar version 2024.8.30.post3. All of this is necesarry because I try to limit the resources used by the environment to 4GB of RAM, cause the processing chain will be implemented on a low resources environment for small areas processing.

I run the docker as following:
docker run -p 8085:8085 -m 6g -v mount_volume:/home/data/ --rm -it --entrypoint bash pechnikov/pygmtsar. The data that I use is a whole year of Sentinel 1 data which is located in the mounted_volume.

When I use sbas.compute_align() the process stales in that point, no matter the time that I leave it (maximum time 4 hours), but when i hit stop from the jupyter lab notebook the process shows that somehow is completed, for the Aligning Repeat: step.
image

When I run the docker image without the memory constrictions everything runs ok, but the sbas.compute_align() takes too much RAM memory, so that is not a solutions (almost 30 GB of RAM are needed for the sbas.compute_align() function.)

Are there are known issues for this?!?

@AlexeyPechnikov
Copy link
Owner

You’ve allocated 6 GB of memory to the container using the -m 6g flag, but you haven’t specified a swap size.

It’s strange that aligning requires so much RAM. Are you processing individual bursts or entire subswaths?

@georgeboldeanu
Copy link
Author

@AlexeyPechnikov Individual bursts.

@AlexeyPechnikov
Copy link
Owner

Try adding a couple of gigabytes of swap memory at first.

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