Snap2stamps package: a free tool to automate the SNAP-StaMPS Workflow

Hello dear mdelgado
my cache is 12G, it took more than 6 hours, I only processed a snap2stamps and only 3bursts has been selected.

What about the computer resources?
Could you monitor the processing?

For me similar processing 3 burst with 16G cache on a 8vCPUs and 32GB RAM computer that process took 3min per interferogram pair.

So I can only suggest to check the snap (snap.conf and snap.properties) and system parameters

Hello All
I had a problem when i ran the stamps_export.py like this one… is there any solutions for this problem? thanks…

Where is the problem?
it seems successfully completed to me

i have problem when i ran python stamps_export.py project.conf, aftering running it, it seems locked in the first master-slave pair and didn’t show progress. is there any solution. this is my project.conf.

PROJECT DEFINITION

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

PROCESSING PARAMETERS

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

AOI BBOX DEFINITION

LONMIN=104.95
LATMIN=34.85
LONMAX=105.25
LATMAX=35.15
##################################

SNAP GPT

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

COMPUTING RESOURCES TO EMPLOY

CPU=6
CACHE=16G

I see your master product ends with “_Orb.dim”. I think you should apply TOPS Split to your master as well, because the naming convention as @mdelgado described here:

If you need all bursts, I still recommend adding “_Split” to the product name just to go sure, because the script expects this structure to correctly extract the date from the master image’s file name.

1 Like

I am sorry for disturbing again,i applied TOPS Split to my master before, and i added “_Split” to the product name just now, and try it again, but it also doesn’t work. Is there any other solution?

How many bursts did you use?
Coregistering is a quite computationally intensive task, it is usually taking several minutes to hours, depending on the size of the data.

Or do you get a different error message now?

Hi mdelgado ,
I check this error when using the command “python coreg_ifg.py project.conf”

WARNING: org.esa.snap.core.gpf.common.SubsetOp: No intersection with source product boundary S1A_IW_SLC__1SDV_20180724T060252_20180724T060319_022932_027CF4_3860_split_Orb_Stack_Deb
IFG: isTOPSARBurstProduct = true
WARNING: org.esa.snap.core.gpf.common.SubsetOp: No intersection with source product boundary S1A_IW_SLC__1SDV_20180724T060252_20180724T060319_022932_027CF4_3860_split_Orb_Stack_Ifg_Deb_DInSAR

is there any solution to resolve it ???
cheers.

Well… my first guess when seeing the error you pointed: SubsetOp: No intersection with source product boundary is that you have not correctly defined the LATMIN, LATMAX, LONMIN and LONMAX coordinates in the project.conf file.

Please check it out and let us know

Good Morning ,
i think the problem in Splitting , what do you think too ??
[6] Folder: 20190929
/home/miloudi/software/chlef/slaves/20190929
[’/home/miloudi/software/chlef/slaves/20190929/S1A_IW_SLC__1SDV_20190929T060301_20190929T060328_029232_03521C_8885.zip’]
FILE(s) : /home/miloudi/software/chlef/slaves/20190929/S1A_IW_SLC__1SDV_20190929T060301_20190929T060328_029232_03521C_8885.zip
[’/usr/local/snap/bin/gpt’, ‘/home/miloudi/software/chlef/graphs/splitgraph2run.xml’, ‘-c’, ‘6G’, ‘-q’, ‘4’]
SNAP STDOUT:SEVERE: org.esa.s2tbx.dataio.gdal.activator.GDALDistributionInstaller: The environment variable LD_LIBRARY_PATH is not set. It must contain the current folder ‘.’.
INFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters
Executing processing graph
INFO: org.hsqldb.persist.Logger: dataFileCache open start
…10%…20%…30%…40%…50%…60%…70%…80%…90% done.

[6] Finished process in 95.3614559174 seconds.
Split slave [’/home/miloudi/software/chlef/slaves/20190929/S1A_IW_SLC__1SDV_20190929T060301_20190929T060328_029232_03521C_8885.zip’] successfully completed.

thanks in advance

It seems to me that this had not any issues.

it seems that the problem is here ??? what do you think??
SNAP STDOUT:SEVERE: org.esa.s2tbx.dataio.gdal.activator.GDALDistributionInstaller: The environment variable LD_LIBRARY_PATH is not set. It must contain the current folder ‘.’

This is not causing a problem at all…
please not that is a WARNING and related to sentinel-2 toolbox, which is not used on S1 processing.

If you wish, add the LD_LIBRARY_PATH to the current environment to avoid this WARNING message, and you could check that the output is exactly the same.

Your problem, as said some posts before, is due to the SubsetOp that is used only in the coregistration/interferogram step, and not before. Probably you defined the LAT/LON coordinates wrong in the project.conf (PLEASE CHECK THIS)

Maybe you splitted the wrong IW… this is my last guess… (but this is not related to the severe warning you are pointing out)

I hope this helps.
Good luck!

Hi mdelgado ,
you were right it was the problem of coordinates
now i have this warning when i process “coreg” :

IFG: isTOPSARBurstProduct = true
INFO: org.esa.snap.core.dataop.dem.ElevationFile: http retrieving http://step.esa.int/auxdata/dem/SRTMGL1/N37E001.SRTMGL1.hgt.zip
WARNING: org.esa.snap.core.dataop.dem.ElevationFile: http error:http://step.esa.int/auxdata/dem/SRTMGL1/N37E001.SRTMGL1.hgt.zip on http://step.esa.int/auxdata/dem/SRTMGL1/N37E001.SRTMGL1.hgt.zip
INFO: org.esa.snap.core.dataop.dem.ElevationFile: http retrieving http://step.esa.int/auxdata/dem/SRTMGL1/N37E000.SRTMGL1.hgt.zip
WARNING: org.esa.snap.core.dataop.dem.ElevationFile: http error:http://step.esa.int/auxdata/dem/SRTMGL1/N37E000.SRTMGL1.hgt.zip on http://step.esa.int/auxdata/dem/SRTMGL1/N37E000.SRTMGL1.hgt.zip

is that will cause a problem???

Thanks a lot

Mmmm, in this case please check.

Is your area in the middle of the Mediterranean Sea?
It is normal that there is no DEM over water… and looking at the coordinates that gives the warning… this seems to be the reason (from my understanding)

Without DEM they will not be any topographic phase removal.
Please check if your area contains also other piece of DEM and not only the one giving the error.

I hope this helps

Hi Mdelgado ,

my area of interest include (IW3 and IW2) . my first work was the splitting of all my data with IW2, and i have done the process snap2stamps .
my question is how to combine the IW3 and IW2 to have my area of interest ???

cheers

Well…Using my scripts you may run the steps 2 and 3 for each of the IWs and then you may need to include also the merging in a latter step. This is not in the current snap2stamps version but it is quite easy to implement it and include it in a second release

Hi @mdelgado,

I just tried to use snap2stamps code to process images with SNAP v7.0.2.

My study is area just in one burst, so I have already deleted the ESD operator in coreg_ifg_computation.xml and coreg_ifg_computation_subset.xml.

But there still have the same error message as followed:
Error: [NodeId: Enhanced-Spectral-Diversity] Operator ‘SpestralDiversityOp’: Unknown element ‘useSuppliedShifts’

Could you help me to deal with this problem?
Thank you very much!

Let me try.

Which file had you modified? It seems that SNAP is still getting the one containing the ESD operator.

Secondly, SNAP 7 modified the ESD operator changing the parameters contained in the xml, but if you do not need it, you should not care about updating them.

I hope this helps