search

isce-framework / isce2

InSAR Scientific Computing Environment version 2
Other
513 stars 252 forks source link

stripmapStack geom_reference/los.rdr incorrect scheme #277

Closed EJFielding closed 2 years ago

EJFielding commented 3 years ago

When running stripmapStack on UAVSAR data, the multilooked geom_reference/los.rdr is created in BSQ file scheme, but the los.rdr.xml file is set to scheme BIP. This is run setup I used:

stackStripMap.py -s SLC/ -d /u/sar-r0/fielding/Calif/SF_Bay/topo/USGS/1_3asec/BayArea_USGS_13.dem.wgs84 -a 8 -r 2 -W interferogram --filter_strength 0.2 --nofocus -S uavsar_stack -t 350

 My version of ISCE2 is compiled with: GDAL 3.1.4, released 2020/10/20

geniusinaction commented 3 years ago

I see the same thing, running stripmapStack on Envisat data. There is a 'tiled' pattern to the angle values in los.rdr which obviously messes up my troposphere corrections and the like when I import the data into MintPy. See 3 and 4 here:

Screenshot 2021-06-17 14 06 27

I cloned the repo a few days ago, so this is a 'current' issue.

Processing an individual pair with the same reference image in stripmapApp does not have this problem, so is there a code snippet I can copy from one to the other that fixes this?

EJFielding commented 3 years ago

I forget exactly what I did, but I think you can hand-edit the los.rdr.xml file and change the scheme to BSQ so that MintPy reads it correctly. You have to remove the MintPy .rsc files and .h5 files to get it to re-read everything.

I looked at the ISCE2 code to try to find where the problem was, but I did not find it.

geniusinaction commented 3 years ago

Can confirm that changing 'BIP' to 'BSQ' in los.rdr.xml seems to mitigate the problem, even if it doesn't fix it at source.

Can also confirm that grepping for 'BIP' in the contrib/stack/stripmapStack directory doesn't turn up anything that looks like it might be to blame...