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

The LiCSBAS13_sb_inv.py does not finish. #6

Open
sakuya-izayoi-0518 opened this issue Jan 11, 2025 · 4 comments
Open

The LiCSBAS13_sb_inv.py does not finish. #6

sakuya-izayoi-0518 opened this issue Jan 11, 2025 · 4 comments

Comments

@sakuya-izayoi-0518
Copy link

Morishita-san,
I am running LiCSBAS13_sb_inv.py, but the process stops midway.
I have set n_para=1.
The output log is as follows:

batch_LiCSBAS2_ALOS.txt
`LiCSBAS13_sb_inv.py ver1.5.2 20210311 Y. Morishita
LiCSBAS13_sb_inv.py -d GEOCml1 --mem_size 21000 --n_para 1 --n_para 1

In geographical coordinates

Not enough memory available compared to mem_size (21000.0 MB).
Reduce mem_size automatically to 10473 MB.
Read cum data on memory (fast but need memory).

Size of image (w,l) : 3400, 2800

of all images : 13

of images to be used : 13

of all ifgs : 76

of ifgs to be used : 68

of removed ifgs : 8

Threshold of used unw : 6

Reference area (X/Y) : 2580:2581/2313:2314
Allowed memory size : 10473 MB
Number of patches : 1
Inversion algorism : LS
Gamma value : 0.0001

Process 2800/2800th line (1/1th patch)...
Reading 68 ifg's unw data...
2651037/9520000 points removed due to not enough ifg data...

Identifing gaps, and counting n_gap and n_ifg_noloop,
with 1 parallel processing...
Running 1/ 1th patch...
`

Do you have any suggestions for how to resolve this issue?

Since GitHub does not allow attachments with the .sh extension, I have changed the file extension to .txt.

@yumorishita
Copy link
Owner

Did it really stop? How long did you wait? It could take a very long time (e.g., a few days or more) because the size is very large.

@sakuya-izayoi-0518
Copy link
Author

Thank you for your reply.
I have been running the analysis for 12 hours.
Since you mentioned that the range might be too broad, I will review the range if it does not finish after another 12 hours.
Thank you for your advice.

@sakuya-izayoi-0518
Copy link
Author

Morishita san

After waiting for approximately another 36 hours since then, the analysis has been completed.
I apologize for the inconvenience.

Regarding the analysis results, could you kindly confirm if the output units are the same as those obtained using LiCSAR, i.e., in mm or mm/year?

@yumorishita
Copy link
Owner

Yes.

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