Snap2stamps error

Ferrett · January 16, 2023, 7:17pm

Hi,
I am getting the following error in my 5 images, what should I do?

SNAP STDOUT:INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: GDAL 2.2.3 found on system. JNI driver will be used.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Installed GDAL 2.2.3 set to be used by SNAP.
INFO: org.esa.snap.core.util.EngineVersionCheckActivator: Please check regularly for new updates for the best SNAP experience.
INFO: org.esa.s2tbx.dataio.gdal.GDALVersion: Installed GDAL 2.2.3 set to be used by SNAP.
Executing processing graph
INFO: org.hsqldb.persist.Logger: dataFileCache open start
…10%…20%…INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Shifts written to file: /home/gndz/.snap/var/log/IW2_range_shifts.json
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 1/8
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 2/8
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 3/8
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 4/8
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 5/8
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 6/8
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 7/8
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Estimating azimuth offset for blocks in overlap: 8/8
WARNING: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: NetworkESD (azimuth shift): arc = IW2_VV_mst_02Sep2019_IW2_VV_slv1_16Jul2019 overlap area = 0, weight for this overlap is 0.0
WARNING: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: NetworkESD (azimuth shift): arc = IW2_VV_mst_02Sep2019_IW2_VV_slv1_16Jul2019 overlap area = 1, weight for this overlap is 0.0
WARNING: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: NetworkESD (azimuth shift): arc = IW2_VV_mst_02Sep2019_IW2_VV_slv1_16Jul2019 overlap area = 2, weight for this overlap is 0.0
WARNING: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: NetworkESD (azimuth shift): arc = IW2_VV_mst_02Sep2019_IW2_VV_slv1_16Jul2019 overlap area = 3, weight for this overlap is 0.0
INFO: org.esa.s1tbx.sentinel1.gpf.SpectralDiversityOp: Shifts written to file: /home/gndz/.snap/var/log/IW2_azimuth_shifts.json
…30%…40%…50%…60%…70%…80%…90% done.
– org.jblas INFO Deleting /tmp/jblas5290024103253089492/libquadmath-0.so
– org.jblas INFO Deleting /tmp/jblas5290024103253089492/libjblas.so
– org.jblas INFO Deleting /tmp/jblas5290024103253089492/libgfortran-4.so
– org.jblas INFO Deleting /tmp/jblas5290024103253089492/libjblas_arch_flavor.so
– org.jblas INFO Deleting /tmp/jblas5290024103253089492

suribabu · January 17, 2023, 5:08am

I think the processing went well. There is no error

Shadi1 · January 30, 2023, 1:22pm

I have a question if you wouldn’t mind.
As you can see here, in line number 69, the topographic phase removal option is disabled,

I have used this graph file during the automated processing step “Master-slave coregistration and interferogram generation” and yet topographic phase bands were created. How is that possible ?
and the tutorial never mentioned editing this line during for the pre-Stamps-processing chain.

mdelgado · January 30, 2023, 2:02pm

Just scroll down and you will find the operator TopoPhase Removal (line 106)

You have just needed to go a bit down to get it clear.
Obviously, no need to rise an unexisting alarm to everybody.

Best,

Shadi1 · January 30, 2023, 2:22pm

This is embarrassing, I thought it was the reason why all the interferograms and velocity maps of my study area still contain persistent topographic pattern even after StaMPS processing. I apologize for such disturbance I have caused

mdelgado · January 30, 2023, 3:43pm

No problem!
It can happen to everybody.

The main reasons for topography alike signal could be: 1) not too accurate DEM, 2) atmospheric signal link to the topography

Enjoy the processing

masoodhp · March 28, 2024, 11:39am

Hi dear @mdelgado sorry to ask but I am trying to use the PSI method and I got this error:
python2.7 slaves_prep.py project.conf
Traceback (most recent call last):
File “slaves_prep.py”, line 16, in
from pathlib import Path
ImportError: No module named pathlib
I have used this before but it is not working now any suggestion?

suribabu · March 28, 2024, 11:45am

mdelgado · March 28, 2024, 12:22pm

That was specified on the user manual for the version 1

masoodhp · April 3, 2024, 10:47am

I used that but for some reasons it is not working. I think the problem is with ubuntu 22. so i think i should downgrade it.

mdelgado · April 5, 2024, 8:48am

I invite you to see the version 2 then, which includes a yaml file with all the dependencies which you can directly use to create your conda environment with the python dependencies.

erkdiwakar · July 6, 2024, 3:52am

@Shadi1 : I am using GitHub - mdelgadoblasco/snap2stamps: Using SNAP as InSAR processor for StaMPS for snap2stamps. I am also facing same problem as you have faced previously, the error is in the computation of coregistration & interferogram generation. Please see my configuration file.
project_topsar.doc (1.7 KB)
I would also like to share the work i have done before executing coregistration & interferogram generation.
snap2stamps workflow-Error.docx (200.5 KB)
Please see why there is error message as below while executing this coregistration & interferogram generation. F:\SNAP2StaMPS>python topsar_step_3_coreg_ifg_topsar_smart.py -F F:\SNAP2StaMPS\project_topsar.conf
BBOX
POLYGON ((85.68 27.63,86.06 27.63,86.06 28.22,85.68 28.22,85.68 27.63))

#####################################################################

Coregistration and Interferogram computation started:

#####################################################################

N masters:1
Checking N bursts in file F:/SNAP2StaMPS\MasterSplit\20211001_IW3.dim
Line 4918 :
5
graph :F:/SNAP2StaMPS/graphs\topsar_coreg_ifg_computation_subset_extDEM.xml
F:/SNAP2StaMPS\MasterSplit\20211001_IW3.dim
IW3
F:/SNAP2StaMPS\split\20210110_IW3.dim
[1] Processing secondaries file :20210110_IW3.dim

20211001_20210110_IW3
Executing processing graph

done.

[1] Finished process in 5.038559913635254 seconds.
Returncode :1
Error computing with coregistration and interferogram generation of splitted secondaries F:/SNAP2StaMPS\split\20210110_IW3.dim

#####################################################################

F:/SNAP2StaMPS\split\20210122_IW3.dim
[2] Processing secondaries file :20210122_IW3.dim

20211001_20210122_IW3
Executing processing graph

done.

[2] Finished process in 5.250585079193115 seconds.
Returncode :1
Error computing with coregistration and interferogram generation of splitted secondaries F:/SNAP2StaMPS\split\20210122_IW3.dim
The error repeats for all split secondaries image. I am looking for yours kind suggestion. —Diwakar

erkdiwakar · July 6, 2024, 7:07am

@mirza.waqar, @mdelgado, @suribabu, @ABraun : I am using (GitHub - mdelgadoblasco/snap2stamps: Using SNAP as InSAR processor for StaMPS)for snap2stamps. I am also facing same problem as you have faced previously, the error is in the computation of coregistration & interferogram generation. Please see my configuration file. Please see my configuration file.
project_topsar.doc (1.7 KB)
I would also like to share the work i have done before executing coregistration & interferogram generation.
snap2stamps workflow-Error.docx (200.6 KB)
Please see why there is error message as below while executing this coregistration & interferogram generation. F:\SNAP2StaMPS>python topsar_step_3_coreg_ifg_topsar_smart.py -F F:\SNAP2StaMPS\project_topsar.conf
BBOX
POLYGON ((85.68 27.63,86.06 27.63,86.06 28.22,85.68 28.22,85.68 27.63))

#####################################################################

Coregistration and Interferogram computation started:
#####################################################################

N masters:1
Checking N bursts in file F:/SNAP2StaMPS\MasterSplit\20211001_IW3.dim
Line 4918 :
5
graph :F:/SNAP2StaMPS/graphs\topsar_coreg_ifg_computation_subset_extDEM.xml
F:/SNAP2StaMPS\MasterSplit\20211001_IW3.dim
IW3
F:/SNAP2StaMPS\split\20210110_IW3.dim
[1] Processing secondaries file :20210110_IW3.dim

20211001_20210110_IW3
Executing processing graph

done.

[1] Finished process in 5.038559913635254 seconds.
Returncode :1
Error computing with coregistration and interferogram generation of splitted secondaries F:/SNAP2StaMPS\split\20210110_IW3.dim

#####################################################################

F:/SNAP2StaMPS\split\20210122_IW3.dim
[2] Processing secondaries file :20210122_IW3.dim

20211001_20210122_IW3
Executing processing graph

done.

[2] Finished process in 5.250585079193115 seconds.
Returncode :1
Error computing with coregistration and interferogram generation of splitted secondaries F:/SNAP2StaMPS\split\20210122_IW3.dim The error repeats for all split secondaries image. I am looking for yours kind suggestion.-Diwakar

mdelgado · July 11, 2024, 7:33pm

can you provide me the coreg2run.xml file that can be found on the graphs folder of the project?
Best,

erkdiwakar · July 12, 2024, 7:54am

@mdelgado: Thank you for your response sir. I found coreg_ifg2run.xml rather than coreg2run.xml. I am not sure why coreg2run.xml file is not seen in my computer location.

Here is my coreg_ifg2run.xml
coreg_ifg2run.xml (7.1 KB)

erkdiwakar · July 13, 2024, 4:59am

@mdelgado : Since, I failed to peform coregistration and interferogram generation using python script. I tried to peform it manually using master image and single slave image using SNAP 10.0.0. But, Still i failed to perform ‘coreg’ & ‘ifg’. I would like to share the work i have done in the following attachment. I am hoping for yours kind suggestion.
snap2stamps-workflow-mdelgardo.docx (1.8 MB)
Also, Please find my project_topsar.conf file too.
project_topsar.doc (28.5 KB)

erkdiwakar · July 19, 2024, 6:29am

@mdelgado : Hello Sir, Is there any suggestion on the problem i am facing since few weeks. It would be highly apprecialbe to receive yours suggestion.

Diwakar

mdelgado · July 19, 2024, 12:39pm

Sorry for the silence but summer has intrinsic delays due to holiday time.
Could you please verify that your master image has been correctly splitted? Can you open it using SNAP for example and visualise it?

Same for slave images… as I do not see anything weird on the graph xml (maybe the / and \ on the external DEM path. but I am not sure of it)

Best,

erkdiwakar · July 19, 2024, 1:45pm

@mdelgado : Hello Sir, As per your suggestion, I checked the master and slave image and i think it worked perfectly.

I checked the path of External DEM. I think the path of external DEM is also correct.Please check the image for External DEM path.
DEM_AOR

Thank You
Diwakar

mdelgado · July 20, 2024, 9:53pm

When I mentioned the external DEM, I meant the path that appears inside the coreg_ifg2run.xml .

I am not sure you want to share it and tell me 2 files so I can try locally…
Best