-
Notifications
You must be signed in to change notification settings - Fork 110
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
GACOS not working #155
Comments
I guess one or more unw data contain no data (though it is weird). Please try skipping step03, running step11, seeing TS_GEOCml1/info/11ifg_stats.txt, identifying unw with no data, removing the unw data from GEOCml1, then rerun step03. |
Got it, thanks Morishita, I will have a try with the steps that you suggested. -Daisy |
Hi Morishita, I have tried your suggested steps, still got error. Please see attached log file |
I have processed the frame and found that the data below are corrupted: |
I have done your suggested step, still error. Please see attached log |
Please remove GEOCml1GACOS as well and try again. |
Thanks Morishita. Good and bad news. Finally I have got the batch file running successfully, please see attached log file. Bad news is when I plot the data, is empty result, please see attached screen capture. |
Strange. Can you show me TS_GEOCml1GACOSclip/mask_ts.png? |
I found that the following data are also corrupted:
(You can see the corrupted data images GEOCml1GACOSclip//.png) Please remove them from GEOCml1GACOSclip (or other GEOC* directories for earlier steps) and rerun from step11. Then clear subsidence signals would appear! |
It is not an issue. The color range is automatically set to 99% of the data to exclude outliers by default (see here). If you want to set the color range to min/max of the data, add an option I firstly ran with |
Got it, thanks, it works! |
Hi, I am a Post-doc from the University of Edinburgh. I have tried the GACOS atmospheric correction in the batch file, however, I got an error, please see attached log file.
202205102327batch_LiCSBAS_01_16.log
The text was updated successfully, but these errors were encountered: