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

[Help]: large time processing to plot unwrapped phase #151

Open
mateosanchezospina opened this issue Jul 19, 2024 · 12 comments
Open

[Help]: large time processing to plot unwrapped phase #151

mateosanchezospina opened this issue Jul 19, 2024 · 12 comments

Comments

@mateosanchezospina
Copy link

mateosanchezospina commented Jul 19, 2024

Describe the problem you encountered
"bas.plot_phases(unwrap_sbas.phase[:8], caption='SBAS Phase, [rad]')" , more than 45 mintues and still loading.

OS and software version
Please specify your operating system and the version of PyGMTSAR you are using, if applicable.

  • OS:
  • PyGMTSAR version:

Steps to reproduce the problem
2D Unwrapping - sbas phase
sbas.plot_phases(unwrap_sbas.phase[:8], caption='SBAS Phase, [rad]')

Note

  • If you have a general question not directly related to PyGMTSAR, consider using the discussions page.

[For additional support, consider using the ChatGPT4-based InSAR AI Assistant at https://insar.dev/ai. It can provide guidance and help with understanding PyGMTSAR's capabilities and troubleshooting issues.]

@mateosanchezospina mateosanchezospina changed the title [Help]: large time processing to plot unwrapped phase "bas.plot_phases(unwrap_sbas.phase[:8], caption='SBAS Phase, [rad]')" , more than 45 mintues and still loading. [Help]: large time processing to plot unwrapped phase Jul 19, 2024
@AlexeyPechnikov
Copy link
Owner

In the case of large rasters, SNAPHU unwrapping can require a lot of time, depending on your hardware. Have you materialized the dataset unwrap_sbas before plotting? While this does not speed up the process, it provides a progress indicator to help estimate the remaining time.

@mateosanchezospina
Copy link
Author

Alexey thankyou very much. Probably is it, I didn´t the last step, materialized the dataset. I´ll try again.

@AlexeyPechnikov
Copy link
Owner

It seems you have large rasters because the first 8 cannot be completed in 45 minutes. What are the dimensions of your interferogram stack? Typically, SBAS resolution is 60 meters, and you do not need to unwrap overly large interferograms. Of course, you can use a more precise resolution, but it can be slow and is often not necessary since we can enhance lower-resolution SBAS results with higher-resolution PSI.

@mateosanchezospina
Copy link
Author

I dont think so. The resolution rasters that I used is by default 60 m, and the stack numbers of interferoframs is 27. So probably shouldn't be delayed. I think the reason is that I did not execute the las step "materialized the dataset unwrap_sbas", because there was an "optional" notice in the text. So I´ll try again, in few momements, and I update the issue thread. Again, thank you for your help.

@mateosanchezospina
Copy link
Author

Hello again. After trying several times, the line "unwrap_sbas = sbas.sync_cube(unwrap_sbas, 'unwrap_sbas')" still does not execute. Is loading for more than 30 minutes and the bar does not exceed 36%. I attach a screenshot, I hope there is some solution. Thank you.
screen

@AlexeyPechnikov
Copy link
Owner

Your data resolution is 15 meters (see your y and x spacing, 1 unit per y means about 15 meters and 4 units per x mean the same). As I’ve mentioned above, 60-meter resolution processing might be much faster.

@mateosanchezospina
Copy link
Author

Ok I have it. But how can I change this resolution to 60 m? Update: I chose an AOI with a smaller dimension size, and it worked correctly. However, in LOS displacement decompose, there appears to be noise in the trends.
SBAS_LOS_Dispkacement_Decompose_2022_2023
What you can appreciate?

@mateosanchezospina
Copy link
Author

How could I read a document where you learn to interpret these results? (Notebook: Golden Valley)

@AlexeyPechnikov
Copy link
Owner

Check the ‘resolution’ parameter for the function compute_interferogram_multilook(). Ensure that your interferograms are clean from atmospheric noise, and use the function plot_baseline_displacement_los_mm() to check changes in single pixels.

I share some explanations of the results on Patreon: https://www.patreon.com/pechnikov

@Aragon-yggdrasill
Copy link

Aragon-yggdrasill commented Jul 23, 2024

检查函数 compute_interferogram_multilook() 的“resolution”参数。确保干涉图没有大气噪声,并使用函数 plot_baseline_displacement_los_mm() 检查单个像素的变化。

我在 Patreon 上分享了一些对结果的解释: https://www.patreon.com/pechnikov

QQ截图20240723134808
QQ截图20240723134821
I also tried adjusting other parameters, but either there was no change or they were all zero. The example used was LakeSarez_Landslides_2017.ipynb. @AlexeyPechnikov

@AlexeyPechnikov
Copy link
Owner

Your variable ‘landmask_sbas’ is defined on a different grid and needs to be adjusted here.

@Aragon-yggdrasill
Copy link

Thank you for your reply, the problem has been solved

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