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

LiCSBAS12_loop_closure.py Killed #350

Open
PeymanPython opened this issue Apr 28, 2024 · 4 comments
Open

LiCSBAS12_loop_closure.py Killed #350

PeymanPython opened this issue Apr 28, 2024 · 4 comments

Comments

@PeymanPython
Copy link

Dear Morishita,
I have 8000 ifgs (SR=30m) and when I run the step 1-2 (Loop Closure) running program is immediately killed, as you can see below;
111

As far as I know, it's happened owing to the Memo-Size/RAM of the system, I'm wondering if there is a way to tackle that issue. Here is my system config:

  • RAM 32
  • Processor: 13th Gen Intel(R) Core(TM) i9-13900HX 2.20 GHz
  • Memory: 2TB SSD
@yumorishita
Copy link
Owner

Step1-2 does not require such a large memory (at least at the killed timing). I have no idea.
You can try

  • large nlook
  • crop by step05
  • decrease ifgs

or please upload the full log.

@PeymanPython
Copy link
Author

Many Thanks for your prompt reply...

@PeymanPython
Copy link
Author

Dear morishita,
I already have clipped based on my study area and is not too large area, and for step 0-2 I used nlook=1 because I need high precision results. Moreover, the number of my connections is differen e.g., from 15 connection to 53...
Do you have any idea about the nlook parameter? which nlook value does not degrade the resolusion and exactness?
Does high connection number (long temporal baseline) heps us to get better results in urban and rock-outcrop area?

@yumorishita
Copy link
Owner

Do you have any idea about the nlook parameter? which nlook value does not degrade the resolusion and exactness?

I just suggest trying a large nlook to confirm if it works or not. Not for the final result.

Does high connection number (long temporal baseline) heps us to get better results in urban and rock-outcrop area?

I don't think so. You can reduce the number of connections if the AOI is urban or rock area.

If you show me the full log (using batch_LiCSBAS.sh), I might be able to find the root cause.

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