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.

Sign up for GitHub

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

Jump to bottom

InSAR fails with "no points available for determining average intensity" error #216

Open

asjohnston-asf opened this issue Mar 5, 2021 · 0 comments

Labels

bug

Member

asjohnston-asf commented Mar 5, 2021 •

edited

Loading

Impacted ~1 in 1,000 pairs out of ~20,000 insar jobs we ran for SARVIEWS.

Example pairs:

S1A_IW_SLC__1SDV_20200126T112153_20200126T112221_030971_038E72_7909,S1B_IW_SLC__1SDV_20200201T112118_20200201T112141_020075_025FEA_7523
S1A_IW_SLC__1SDV_20191115T112156_20191115T112224_029921_036A01_6C79,S1B_IW_SLC__1SDV_20191121T112120_20191121T112144_019025_023E71_1AD0

This is related to code in https://github.com/ASFHyP3/hyp3-gamma/blob/master/hyp3_gamma/insar/ifm_sentinel.py#L48 , related to the burst times for each scene not being within 0.2 seconds of each other.

03/05/2021 01:39:59 AM - INFO - total_bursts1, time1 10 [6201.7603385546, 6204.5188951092, 6207.2774516638, 6210.0339526621, 6212.792509216701, 6215.549010215001, 6218.305511213301, 6221.0661233242, 6223.8246798788, 6226.5811808771]
03/05/2021 01:39:59 AM - INFO - total_bursts2, time2 7 [285.4837895546, 288.2444016655, 291.0029582201, 293.7594592184, 296.5200713293, 299.2786

The text was updated successfully, but these errors were encountered:

asjohnston-asf added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment