ISCE2 stackSentinel ESD error: Coherence threshold too strict + missing IW2.xml #1020
-
|
Hi everyone, I tried the NESD & the geometry method of co-registration method. On NESD method
['Function-1', 'Function-2', 'Function-3', 'Function-4'] followed by the strange occurance, says "secondarys//IW2.xml" not found for almost all the secondarys, but it exists when i search "ls $ /secondarys//IW2.xm/" it found in the directory. File "/home/incois/karthi/miniconda3/envs/isce2/lib/python3.10/xml/etree/ElementTree.py", line 569, in parse and it follows to the 'coreg_secondarys' folder, here the 'coreg_secondarys/20200202/overlap/IW2_top.xml'isn't really found there File "/home/incois/karthi/miniconda3/envs/isce2/lib/python3.10/xml/etree/ElementTree.py", line 1222, in parse and followed by File "/home/incois/karthi/miniconda3/envs/isce2/share/isce2/topsStack/SentinelWrapper.py", line 54, in runCmd I have also ran ISCE2 in -C geometry mode, yet it still shows the same error like above.
in -C geometry mode also i got the same error like the secondarys/IW*.xml not found error File "/home/incois/karthi/miniconda3/envs/isce2/lib/python3.10/xml/etree/ElementTree.py", line 1222, in parse Kindly help me solve this |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 5 replies
-
|
Use full paths instead of relative paths as clearly laid out in the instructions and the README. It is probably related to that |
Beta Was this translation helpful? Give feedback.
-
|
Actually I have used the full path, Regards. |
Beta Was this translation helpful? Give feedback.
-
|
I would recommend running it step-by-step and getting familiar with what happens at each processing stage. Messages like these
|
Beta Was this translation helpful? Give feedback.
-
|
The other most likely cause is that you are mixing images from different tracks and its not able to match bursts with the reference date. |
Beta Was this translation helpful? Give feedback.
-
|
Dear @piyushrpt Thank you so much.
|
Beta Was this translation helpful? Give feedback.
-
|
Following that
This is the total log files of 'run_01_unpack_topo_reference.sh & run_02_unpack_secondary_slc.sh' |
Beta Was this translation helpful? Give feedback.
-
|
There is still no matching up of bursts at this stage. It is when you use |
Beta Was this translation helpful? Give feedback.
-
|
You are also running 64 processes in parallel. For debugging, maybe try fewer or single process. Your outputs from different are interleaved and so you should not interpret output as sequential in your attached file. Each of the processing modules is multithreaded. Maybe you are just overloading your system. Try with 1 process. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @piyushrpt It worked actually.
I have already run like this in one specific area; there was no problem. Now I ran for 5 months but have to run entire 9 years So I'm planning to use more cores and executing all run files at once in a .pbs script. Will it be a problem if I do in this way? |
Beta Was this translation helpful? Give feedback.
-
|
Your problem is that you are asking for 64 processes and each of the processes can take up 8-16 or more threads (depending on what hardware you have). You were encountering missing files because it was executing next steps before the previous steps were completed due to the large number of processes being requested. numproc has nothing to do with threads - they are parallel processes. Threads are controlled by OMP_NUM_THREADS. Depending on what hardware you have - you need to figure out how many threads vs processes to use. There may be other users on your machine too. I think you have to understand your resource constraints and adapt accordingly |
Beta Was this translation helpful? Give feedback.
-
|
Step-by-step will guarantee that it wont try to run a future step before the previous one is completed - so that maybe the way to go. |
Beta Was this translation helpful? Give feedback.
You are also running 64 processes in parallel. For debugging, maybe try fewer or single process. Your outputs from different are interleaved and so you should not interpret output as sequential in your attached file. Each of the processing modules is multithreaded. Maybe you are just overloading your system. Try with 1 process.