Snap2stamps error

Hello, everyone,

I am trying to use the snap7.0 as the pre-processor for StaMPS.
when I issue “python coreg_ifg_topsar.py project.conf”, I received this error message,
Operator ‘SpectralDiversityOp’: Unknown element 'useSuppliedShifts’
I dont know how to correct it.
So I want some help from you!
Thank you very much!

Yours,
Dingfeng Duan

1 Like

Please provide more information… such project.conf
and also please provide a graph with the SpectralDiversityOp, because what you are telling sounds to me that the new SNAP version modified tags with respect to version 6.

Hello everyone,

I have a problem to export the results of coregistartion and interferogram to StaMPS with stamps_export.py. The problem is:
[NodeId: StampsExport] The Product ‘20170301_20150628_IW1’ already contains a band with the name ‘i_20170301.rslc’.\n"
Previous steps are done successfully. I unistalled the SNAP and reinstalled the SNAP6. the “project.conf” is:

Could you please help me. I did not find the problem.
Thank you so much

Hi,mdelgado,i have a problem when i run snap script ‘python coreg_ifg_topsar.py project.conf’, aftering running it, it seems locked in the first salve and didn’t show progress. i have let it run more than 12 hours. this is my project.conf, and i have three bursts.
######### CONFIGURATION FILE ######
###################################

PROJECT DEFINITION

PROJECTFOLDER=/media/mzf/0A9AD66165F33762/work/PROC
GRAPHSFOLDER=/media/mzf/0A9AD66165F33762/work/GRAPH
##################################

PROCESSING PARAMETERS

IW1=IW1
MASTER=/media/mzf/0A9AD66165F33762/work/PROC/MASTR/20190820/S1A_IW_SLC__1SDV_20190820T230320_20190820T230347_028659_033E4A_AFB6_Orb.dim
##################################

AOI BBOX DEFINITION

LONMIN=105
LATMIN=34.78
LONMAX=105.5
LATMAX=35.39
##################################

SNAP GPT

GPTBIN_PATH=/media/mzf/0A9AD66165F33762/snap/bin/gpt
##################################

COMPUTING RESOURCES TO EMPLOY

CPU=6
CACHE=12
##################################
Is there any solution?
Thank you!

I believe your issue is SNAP configuration or system memory. How big is the data? How many bursts?

I need more information to find the problem…
Please provide
My first question would be… how you modified any graph?
And second: as you said you uninstall SNAP and reinstalled v6… had you processed the previous steps with higher SNAP version?

Thank you for you reply!
i have only three bursts, you say my issue may be SNAP configuration, it has been mentioned in the sanp2stamps_user_manual that $HOME/snap/bin/gpt.vmoptions and modify the param
o –Xmx 12G (according to your computer set up; i.e –Xmx 512M ), if i should change the parameter 512MB to 12G. Or is there any other solutions?

There are more parameters to change… maybe not in that manual.
Please check the file named snap.properties (check also here in the forum)

mzf@mzf:/media/mzf/0A9AD66165F33762/work/snap2stamps-1.0.1/mdelgadoblasco-snap2stamps-c2362a6/bin$ python coreg_ifg_topsar.py project.conf
/media/mzf/0A9AD66165F33762/work/PROC
/media/mzf/0A9AD66165F33762/work/GRAPH
IW1
/media/mzf/0A9AD66165F33762/work/PROC/MASTR/20190820/S1A_IW_SLC__1SDV_20190820T230320_20190820T230347_028659_033E4A_AFB6_Orb.dim
/media/mzf/0A9AD66165F33762/snap/bin/gpt
/media/mzf/0A9AD66165F33762/work/GRAPH/coreg_ifg_computation_subset.xml

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

Coregistration and Interferogram computation started:

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

/media/mzf/0A9AD66165F33762/work/PROC/split/20180930/20180930_IW1.dim
[1] Processing slave file :20180930_IW1.dim

SNAP STDOUT:INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters
SEVERE: org.esa.s2tbx.dataio.gdal.activator.GDALDistributionInstaller: The environment variable LD_LIBRARY_PATH is not set. It must contain the current folder ‘.’.
Executing processing graph
INFO: org.hsqldb.persist.Logger: dataFileCache open start

Master: 20Aug2019
Slave: 20Aug2019 prep baseline: 0.0 temp baseline: 0.0
Slave: 30Sep2018 prep baseline: -79.38123 temp baseline: 324.00006

======
Master: 30Sep2018
Slave: 20Aug2019 prep baseline: 79.388794 temp baseline: -324.00006
Slave: 30Sep2018 prep baseline: 0.0 temp baseline: 0.0

IFG: isTOPSARBurstProduct = true
…INFO: org.hsqldb.persist.Logger: Database closed
…10%…20%…30%…40%…51%…61%…71%…81%… done.
– org.jblas INFO Deleting /tmp/jblas8859000957964385564/libjblas.so
– org.jblas INFO Deleting /tmp/jblas8859000957964385564/libjblas_arch_flavor.so
– org.jblas INFO Deleting /tmp/jblas8859000957964385564

[1] Finished process in 70335.1374719 seconds.
Coregistration and Interferogram computation for data 20180930_IW1.dim successfully completed.

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

Hello,mdelgado,this is my processing procedure,it works without error,but it takes too long time. Does it seem to be any problem from this process? Thank you!

I am glad that it works.
Regarding the timing… probably you should configure SNAP to optimize the computing resources. There are some parameters you can modify, but at the end the performance will entirely depend of your computer and the amount of bursts you want to process from the same product.

In the sense… if you work with 2 burst it takes 2-4 mins depending on your computer. If you use 4-5 bursts it takes much longer, not following linear relationship.

You should find the proper combination. For tuning the parameters please look in the forum for the right thread. I remember that are 2 files snap.properties and snap.conf

1 Like

Hi,mdelgado, i have a new problem when coregistration and interferogram, before i process this step, i have prepared corresponding DEM in the ‘’.snap/auxdata/dem’’, but when i process this step, it always reloads the corresponding DEM automatically. I’ve never had this problem before. Is there any solutions?Thank you!

Not sure what you are trying… if you include an external DEM, you may need to tune the corresponding graphs to get it directly, as there is no option from the project.conf in the current release.

Thank you for you reply, i solve it!

1 Like

Hi,

I encounter the same problem as you, how did you solve it?

Thanks,

I have this error while processing, i recently formatted my computer and tried to install snap, stamps, snapp2stamps for processing the data. But i am not sure they are installed properly or not. Can someone please help me in checking the installations?

I can provide access to my computer to check the installations.

Thank you all

Try to change

<useSuppliedShifts>false</useSuppliedShifts>

to

<useSuppliedRangeShift>false</useSuppliedRangeShift>
<useSuppliedAzimuthShift>false</useSuppliedAzimuthShift>

in coreg_ifg_computation.xml file

This option is changed to two attributes in range and azimute for snap V.7

1 Like

Thanks!
Next release will be compatible with v7

1 Like

in case this is still an issue, just found out that snap7.0 had changed or replaced the parameter " useSuppliedShifts" in operator " SpectralDiversityOp" into two new parameters: “useSuppliedAzimuthShift” and “useSuppliedRangeShift”.

  1. <version>1.0</version>
    
  2. <node id="someNodeId">
    
  3.   <operator>Enhanced-Spectral-Diversity</operator>
    
  4.   <sources>
    
  5.     <source>${source}</source>
    
  6.   </sources>
    
  7.   <parameters>
    
  8.     <fineWinWidthStr>string</fineWinWidthStr>
    
  9.     <fineWinHeightStr>string</fineWinHeightStr>
    
  10.     <fineWinAccAzimuth>string</fineWinAccAzimuth>
    
  11.     <fineWinAccRange>string</fineWinAccRange>
    
  12.     <fineWinOversampling>string</fineWinOversampling>
    
  13.     <xCorrThreshold>double</xCorrThreshold>
    
  14.     <cohThreshold>double</cohThreshold>
    
  15.     <numBlocksPerOverlap>int</numBlocksPerOverlap>
    
  16.     <**useSuppliedRangeShift**>boolean</useSuppliedRangeShift>
    
  17.     <overallRangeShift>double</overallRangeShift>
    
  18.     <**useSuppliedAzimuthShift**>boolean</useSuppliedAzimuthShift>
    
  19.     <overallAzimuthShift>double</overallAzimuthShift>
    
  20.   </parameters>
    
  21. </node>
    

so, if you use snap2stamps scrips in snap7, you have to change the parameter names in graph “coreg_ifg_computation_subset.xml” in section:

  1. <operator>Enhanced-Spectral-Diversity</operator>
    
  2. <sources>
    
  3.   <sourceProduct refid="Back-Geocoding"/>
    
  4. </sources>
    
  5. <parameters class="com.bc.ceres.binding.dom.XppDomElement">
    
  6.   <fineWinWidthStr>512</fineWinWidthStr>
    
  7.   <fineWinHeightStr>512</fineWinHeightStr>
    
  8.   <fineWinAccAzimuth>16</fineWinAccAzimuth>
    
  9.   <fineWinAccRange>16</fineWinAccRange>
    
  10.   <fineWinOversampling>128</fineWinOversampling>
    
  11.   <xCorrThreshold>0.1</xCorrThreshold>
    
  12.   <cohThreshold>0.15</cohThreshold>
    
  13.   <numBlocksPerOverlap>10</numBlocksPerOverlap>
    
  14.   <**useSuppliedRangeShift**>false</useSuppliedRangeShift>
    
  15.   <**useSuppliedAzimuthShift**>false</useSuppliedAzimuthShift>
    
  16.   <overallAzimuthShift>0.0</overallAzimuthShift>
    
  17.   <overallRangeShift>0.0</overallRangeShift>
    
  18. </parameters>
    

then the gpt in the script works. well, for me for now.


just saw the same answer by @ Abdel above. sigh, took me one afternoon to figure it out.

I believe these answers are already several times in the forum.

It is sometimes worth to use the search engine to get problems solve easily and avoid duplicated issues and questions.
Still, good that you managed to solve it

Hello, How could you solve the error ?, because I present the same error.
Thank you very much.