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

Clarification on Reference Point Usage for Decomposing LOS Results in LiCSBAS #332

Closed
BahruzAhadov opened this issue Feb 26, 2024 · 7 comments

Comments

@BahruzAhadov
Copy link

Hello LiCSBAS Team,

I am currently utilizing the LiCSBAS software for an InSAR time series analysis project and have encountered a conceptual challenge that I hope you could help clarify.
How does LiCSBAS determine or utilize this reference point (or area) when decomposing LOS results into horizontal and vertical displacements? Is there a default setting, or does it require user input to specify this reference point? Where can see that used reference point during decomposition?

@yumorishita
Copy link
Owner

yumorishita commented Feb 26, 2024

Please see: #102
#266

@as1234554321
Copy link

hi sir,
I have decomposed the 2017-2023 data. How do I get the decomposition value for each year?
Do I have to repeat running batch (01-16) every year?

@yumorishita
Copy link
Owner

You can output the velocity for each year by LiCSBAS_cum2vel.py.

@as1234554321
Copy link

as1234554321 commented Oct 12, 2024

Hi sir, I want ask again
1.Can the decomposed file (2017-2024) be used on cum2vel py? to get points for each year (eg 2017-2020)?

@yumorishita
Copy link
Owner

No.

@as1234554321
Copy link

ohh I see,
So I do cum2vel.py ascending and descending according to the desired year (ex: 2016-2018) then decompose again?

@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

3 participants