The problem at mergeBursts step while processing with topsStack.

[vardareg]

Hello,
In mergeBursts step, I got an error message like this:

['Function-1']
Running: mergeBursts
['--stack', '/mnt/hdd4tb-2/stack/Elazig/stack', '--inp_reference', '/mnt/hdd4tb-2/stack/Elazig/coreg_secondarys/20190403', '--dirname', '/mnt/hdd4tb-2/stack/Elazig/coreg_secondarys/20190403', '--name_pattern', 'burst*slc', '--outfile', '/mnt/hdd4tb-2/stack/Elazig/merged/SLC/20190403/20190403.slc', '--method', 'top', '--aligned', '--valid_only', '--use_virtual_files', '--range_looks', '9', '--azimuth_looks', '3']
Using default ISCE Path: /home/egehan/miniconda3/envs/isce2/lib/python3.8/site-packages/isce
This is the Open Source version of ISCE.
Some of the workflows depend on a separate licensed package.
To obtain the licensed package, please make a request for ISCE
through the website: https://download.jpl.nasa.gov/ops/request/index.cfm.
Alternatively, if you are a member, or can become a member of WinSAR
you may be able to obtain access to a version of the licensed sofware at
https://winsar.unavco.org/software/isce
Traceback (most recent call last):
File "/home/egehan/tools/src/isce2/contrib/stack/topsStack/SentinelWrapper.py", line 251, in
main(args.start,args.end)
File "/home/egehan/tools/src/isce2/contrib/stack/topsStack/SentinelWrapper.py", line 242, in main
cfgParser.runCmd()
File "/home/egehan/tools/src/isce2/contrib/stack/topsStack/SentinelWrapper.py", line 54, in runCmd
func_modules.main(self.funcParams[section])
File "/home/egehan/tools/src/isce2/contrib/stack/topsStack/mergeBursts.py", line 366, in main
stack = ut.loadProduct(os.path.join(inps.stack , 'IW{0}.xml'.format(swath)))
File "/home/egehan/tools/src/isce2/contrib/stack/topsStack/s1a_isce_utils.py", line 26, in loadProduct
obj = pm.loadProduct(xmlname)
File "/home/egehan/miniconda3/envs/isce2/lib/python3.8/site-packages/isce/components/iscesys/Component/ProductManager.py", line 25, in loadProduct
self.load(filename)
File "/home/egehan/miniconda3/envs/isce2/lib/python3.8/site-packages/isce/components/iscesys/Component/Configurable.py", line 1407, in load
tmpProp, tmpFact, tmpMisc = FP.parse(filename)
File "/home/egehan/miniconda3/envs/isce2/lib/python3.8/site-packages/isce/components/iscesys/Parsers/XmlParser.py", line 41, in parse
root = ET.parse(filename)
File "/home/egehan/miniconda3/envs/isce2/lib/python3.8/xml/etree/ElementTree.py", line 1202, in parse
tree.parse(source, parser)
File "/home/egehan/miniconda3/envs/isce2/lib/python3.8/xml/etree/ElementTree.py", line 584, in parse
source = open(source, "rb")
FileNotFoundError: [Errno 2] No such file or directory: '/mnt/hdd4tb-2/stack/Elazig/stack/IW1.xml'

Maybe my problem in setting environment variables, so I am adding the commands which I used. Therefore, I am adding the commands:
export ISCE_STACK=$HOME/tools/src/isce2/contrib/stack export
PYTHONPATH=/home/egehan/miniconda3/bin/python:${ISCE_STACK}
export PATH=${PATH}:${ISCE_STACK}/topsStack

and my commands for stackSentinel are:
stackSentinel.py -s /mnt/hdd4tb-1/Elazıg/data/slcs/ -d /mnt/hdd4tb-1/Elazıg/data/DEM/demLat_N35_N39_Lon_E036_E041.dem.wgs84 -a /mnt/hdd4tb-1/Elazıg/data/Aux/ -o /mnt/hdd4tb-1/Elazıg/data/orbits -b '38.2 39.43 38.68 41.08' -W interferogram -C geometry -c 5

My slc, orbit, DEM, and AUX files are in my first HDD, while I set the output source to my second HDD. After I got the error message, topsStack processes some data, but in the output files, such as stack and merged interferogram directories, are not created. I installed isce2 from the source using Cmake. I got no error message when I typed topsApp.py -h or stackSentinel.py -h. It works as expected and prints the help text. If anyone can help with my problem, I would be very pleased.

[vardareg]

It is just a syntax error while writing run commands.

[tdl255]

@vardareg I am getting a similar error, but for the geocoding step in stripmapApp.py. Can you explain how you fixed this problem in more detail? Thanks.

[vardareg]

You need to check your log carefully my log does not include actual error. You can check the "error" keyword in your log to identify the problem. In my case, the problem was I did a syntax error. For example, I wrote runtx_06* instead of run_06* in my bash script. It can be hard to catch these types of mistakes sometimes. I hope this can solve your problem.