search

geodesymiami / MiNoPy

MIami NOn linear phase linking in PYthon
Other
19 stars 5 forks source link

Phase_to_range issue #44

Closed stoormgeo closed 3 years ago

stoormgeo commented 3 years ago

Hi, I got strange results after phase_to_range step. At the same time ifgramStack.h5 looks good. Is it possible Dask related issue? Thx tsview.py timeseries.h5

timeseries h5

view.py tempCoherence.h5

tempCoherence h5

view.py ifgramStack.h5

ifgramStack h5

view.py avgPhaseVelocity.h5

avgPhaseVelocity h5

info.py --compact timeseries.h5 `**** HDF5 File Structure **** Attributes in / level: ALOOKS 1 ANTENNA_SIDE -1 AZIMUTH_PIXEL_SIZE 15.591820178293727 BANDS 2 CENTER_INCIDENCE_ANGLE 41.1599 CENTER_LINE_UTC 9857.0 DATA_TYPE float32 DATE12 190904-170610 EARTH_RADIUS 6390163.33041499 END_DATE 20210929 FILE_LENGTH 4994 FILE_PATH /home/insar/1/Massive/Har/proc/merged/minopy/inverted/interferograms_single_reference/20190904_20170610/filt_fine.unw FILE_TYPE timeseries HEADING -157.8703454714286 HEIGHT 706322.8153330042 INTERLEAVE BIL ISCE_VERSION Release: 2.5.3, svn-, 20210823. Current: svn-. LAT_REF1 67.58788771342218 LAT_REF2 67.894505829158 LAT_REF3 66.7535060747611 ...

HDF5 dataset "/bperp ": shape (45,) , dtype HDF5 dataset "/date ": shape (45,) , dtype <|S8> HDF5 dataset "/timeseries ": shape (45, 4994, 10993) , dtype info.py --compact ifgramStack.h5 *** HDF5 File Structure **** Attributes in / level: ALOOKS 1 ANTENNA_SIDE -1 AZIMUTH_PIXEL_SIZE 15.591820178293727 BANDS 2 CENTER_INCIDENCE_ANGLE 41.1599 CENTER_LINE_UTC 9857.0 DATA_TYPE float32 DATE12 190904-170610 EARTH_RADIUS 6390163.33041499 FILE_LENGTH 4994 FILE_PATH /home/insar/1/Massive/Har/proc/merged/minopy/inverted/interferograms_single_reference/20190904_20170610/filt_fine.unw FILE_TYPE ifgramStack HEADING -157.8703454714286 HEIGHT 706322.8153330042 INTERLEAVE BIL ISCE_VERSION Release: 2.5.3, svn-, 20210823. Current: svn-. LAT_REF1 67.58788771342218 LAT_REF2 67.894505829158 LAT_REF3 66.7535060747611 LAT_REF4 67.05412557536643 ... HDF5 dataset "/bperp ": shape (44,) , dtype HDF5 dataset "/coherence ": shape (44, 4994, 10993) , dtype MODIFICATION_TIME 1634462833.1958241

HDF5 dataset "/connectComponent ": shape (44, 4994, 10993) , dtype MODIFICATION_TIME 1634462863.1388915

HDF5 dataset "/date ": shape (44, 2) , dtype <|S8> HDF5 dataset "/dropIfgram ": shape (44,) , dtype HDF5 dataset "/unwrapPhase ": shape (44, 4994, 10993) , dtype MODIFICATION_TIME 1634462758.8277864

HDF5 dataset "/unwrapPhase_bridging ": shape (44, 4994, 10993) , dtype MODIFICATION_TIME 1634468110.4036858

HDF5 dataset "/wrapPhase ": shape (44, 4994, 10993) , dtype MODIFICATION_TIME 1634463061.0120227 `

mirzaees commented 3 years ago

Hi @stoormgeo! These figures do not show the goodness of interferograms, first check the quality in inverted folder. view.py inverted/quality

If it is the same as temporal coherence, then your data probably is not read correctly from the beginning. Have you generated the SLCs with ISCE?

stoormgeo commented 3 years ago

Hi @stoormgeo! These figures do not show the goodness of interferograms, first check the quality in inverted folder. view.py inverted/quality

If it is the same as temporal coherence, then your data probably is not read correctly from the beginning. Have you generated the SLCs with ISCE?

Hi, @mirzaees thanks for help! I checked the quality file and it was the only one corrupted. Probably when I was transferring the data to another workstation (with more CPU) for inversion it got corrupted. Although originally it was fine.

I encountered another one strange error on mintpy_corrections step (correct_LOD) that I can not avoid. But I'm using a Sentinel data not Envisat. Which way should I dig? Thx

Miami InSAR Time-series software in Python ______/ 

      MintPy v1.3.1-43, 2021-10-09

--RUN-at-2021-10-18 00:32:22.740681--

Current directory: /home/ya_insar/Proc/har21/minopy

Run routine processing with smallbaselineApp.py on steps: ['correct_LOD', 'correct_SET', 'correct_troposphere', 'deramp', 'correct_topography', 'residual_RMS', 'reference_date', 'velocity', 'geocode', 'google_earth', 'hdfeos5']

Remaining steps: ['correct_SET', 'correct_troposphere', 'deramp', 'correct_topography', 'residual_RMS', 'reference_date', 'velocity', 'geocode', 'google_earth', 'hdfeos5']

Go to work directory: /home/ya_insar/Proc/har21/minopy

read default template file: /home/ya_insar/Proc/har21/minopy/smallbaselineApp.cfg

**** step - correct_LOD ****

Traceback (most recent call last):

File "/insar/MintPy/mintpy/smallbaselineApp.py", line 1281, in 

main(sys.argv[1:])

File "/insar/MintPy/mintpy/smallbaselineApp.py", line 1263, in main

app.run(steps=inps.runSteps)

File "/insar/MintPy/mintpy/smallbaselineApp.py", line 1048, in run

self.run_local_oscillator_drift_correction(sname)

File "/insar/MintPy/mintpy/smallbaselineApp.py", line 716, in run_local_oscillator_drift_correction

fnames = self.get_timeseries_filename(self.template, self.workDir)[step_name]

File "/insar/MintPy/mintpy/smallbaselineApp.py", line 641, in get_timeseries_filename

if atr['PLATFORM'].lower().startswith('env'):

KeyError: 'PLATFORM'

mirzaees commented 3 years ago

Hi @stoormgeo, yes that might have happened If your data is Sentinel, you don't need to run correct_LOD and you may start from correct_SET. The PLATFORM might not be in the attributes but you can add it and it will be fine: add_attribute.py timeseries.h5 PLATFORM=Sen

stoormgeo commented 3 years ago

Hi @stoormgeo, yes that might have happened If your data is Sentinel, you don't need to run correct_LOD and you may start from correct_SET. The PLATFORM might not be in the attributes but you can add it and it will be fine: add_attribute.py timeseries.h5 PLATFORM=Sen

Hi, @mirzaees Many thanks. I'll try.