LiCSBAS12_loop_closure.py #399
Comments
|
Try n_para=1. Line 24 in 5db6516 |
|
@yumorishita , I try by setting n12_para to 1 |
|
@yumorishita , Now I'm stuck here, which n_para should I change? |
|
I already mentioned above. |
|
202409052217batch_LiCSBAS_01_16.log |
|
Maybe some of the GEOCml1/*/*unw files are corrupted. Please check all the files have the same size. |
|
@yumorishita , There are more than 1000 folders, how can I do this more easily? Also, if there is a corrupt file, what should I do? Should I go back to the beginning? |
|
Remove corrupted files and restart from step11. |
|
@yumorishita , I checked for corrupt files, but all files were the same size and as they should be. I don't know what to do now? |
|
I have no idea, maybe some other files are corrupted. What I can suggest is removing all the files and rerunning from the start. |
|
thank you... |
|
@yumorishita , Dear professor, I have a different technical question for you apart from this topic. Using LICSBAS, I produced cumulative deformation los maps in ascending and descending orbits (2016-2024). How technically correct is it to separate each image pair as east-west and up-down using the cumulative los data produced for the ascending and descending orbits as of 2016? Because after a certain year (failure of one of the Sentinel-1 satellite constellations), the ascending and descending image dates do not match. I need your opinion on this matter.. |
|
haii @oguzhannysr |
What do you mean by "as of 2016"? |
@yumorishita, I meant to say starting from 2016 and until 2024, so I did my work within this date range. |
|
How did you treat the date difference between ascending and descending in the decomposition? |
|
@yumorishita , as it can be seen in the image, after the date 20211218, the dates of the couples start not to match with each other. Therefore, I made ud-ew separation based on two pairs in 6-day periods. For example, I matched the date 20211224 in the ascending orbit with the date 20211230 in the descending orbit and made the separation as ud-ew. How technically correct is this? Does it provide me with the correct trend of the deformation?
|
|
If the deformation is slow and we can ignore the 6 day difference, I think your approach makes sense. |
|
@yumorishita , Thank you sir, but is the reason why the data dates do not match after a certain time (after 2021) due to the failure of the Sentinel-1 satellite or due to incomplete processing of data in the COMET system? |
|
I don't know. You should check it yourself by searching for data, e.g., on ASF. |
|
dear @yumorishita , Is there an anomaly in n_loop_err in my results here? Do you think I should set p15_n_loop_err_thre=0 and run it again? |
|
The result looks normal. |
|
@yumorishita , I got an error like the following. I couldn't understand why. My other files are below. What do you think is the reason? 202409190909batch_LiCSBAS_01_16.log |
This comment was marked as resolved.
This comment was marked as resolved.
|
@oguzhannysr I am not sure but cc files may be corrupted. Please check the contents. |
|
|
These messages are just warnings, not errors, and can be ignored. The processing was successfully finished with no error. |
@yumorishita ,Hello sir, the problem still persists. I want to process the entire tile at once, but I stay in the same step. I can't understand whether my computer's RAM is not enough. |
|
@oguzhannysr What is your RAM size? |
|
@as1234554321 I have no idea from this limited information. |
@yumorishita, Yes, I run LICSBAS in WSL in Windows. |
|
@as1234554321 Now I see your point. You should set the reference point in the south area. |
|
@oguzhannysr I have never used WSL but it seems that the stuck tends to happen in WSL according to the reported issues. I suggest using the VirtualBox as I do. |
|
hi sir @yumorishita |
|
step05 does not set any reference point but just clips the area. |
|
Ohh I see, thankyou for your answer and suggestion
|
|
|
|
The pixel corresponding to the GPS CORS can be a ref point if it exists. |
|
thankyou sir, I will try it Thank you |
|
licsbascum2vel.py does not affect licsbasplot.py at all because the output of licsbascum2vel.py is not used in licsbasplot.py. |
so what tools do i use to change the ref point and how do i know if the velocity has changed? |
|
You should specify the reference for each command. |
yes I know I have to change the ref on every command. but I'm confused about is what commands should be used? Can you provide step by step tools that should be used. I've read the issue related to the ref area but I still miss understanding. |
|
It depends on what output you want. Please carefully read the usage for each command. All the required information is there. |
This comment was marked as resolved.
This comment was marked as resolved.
|
How about -r 190:200/100:110? |
This comment was marked as resolved.
This comment was marked as resolved.
|
For example, |
|
Hi sir, I want to ask you again about this, |
|
I cannot see a significant difference between them. |
|
licsbas result range uplift 0-30 mm but STA MPS just 0 (stable) |
|
If you set the reference there, the displacement will become 0. |
|
Hi sir |
|
Change the value for --ref_geo option. |
sorry i dont understand about this, can you give an example please? |
sorry I follow up about this, I process this using a batch script with default parameter >change ref area with cum2vel> decompose |
|
I see. Use |
how about this sir? |
|
I cannot understand your situation. |
Hello @yumorishita, the computer gets stuck at this step. What is the reason for this? I do it without cropping the area.
202409050828batch_LiCSBAS_01_16.log
The text was updated successfully, but these errors were encountered: