I’m relatively new to the InSAR world and SNAP. I’ve been trying to use snaphu via the MacOS terminal to unwrap interferograms created using S1 SLC imagery. To start (and to keep file sizes down), I’ve used one swath (IW1) and two bursts from a trial image pair.
I believe that snaphu has been configured properly on my machine.
I’ve used snaphu export with the following settings:
Col and row overlap: 0
Number of processors: 4
Number of tiles cols: 10
Number of tiles rows: 10
Cost mode: DEFO
Initialisation method: MCF (although have also tried changing this to MST)
Cost threshold: 500
When I copy the command prompt from the created snaphu.conf file and try to run, the process appears to start, but then aborts (see below):
After searching the Step Forum and resulting advice for similar issues, I tried adding the full file paths for all files within the snaphu.conf file. This didn’t make any difference to the resulting error.
Thinking that this may be a tile issue, I played around with changing the number of tiles and overlap. The unwrapping is only successful if I use one tile only. For such a small image (i.e., two bursts of one swath) this doesn’t take very long to run. However, I’ll need to upscale the analysis which will require increasing the number of tiles used for unwrapping.
Has anyone come across this unwrapping situation / error before? Or have any insight into why the unwrapping works using one tile, but not when using an increased number of tiles?
Cannot think of a reason why such data leads to an error. MST and MCS produce the same problem?
The only thing I can then suggest is to test if SMOOTH runs differently than TOPO or DEFO.
Since snaphu version 2 there is an option to exclude low coherence areas or to mask out certain areas, but I see no reason why this is necessary in your case, nor does it simplify the workflow for multiply products.
I’ve just doubled checked that MST and MCF produce the same resulting error messages (i.e., abnormal exit in terminal and log file showing inability to write to tmp file).
Using SMOOTH or TOPO also result in the same error as using DEFO. I’ve tried SMOOTH and TOPO in varying combinations with MCF and MST, but have left the other export parameters defaults (as in original post above).
I’m looking at an area in the highlands of Scotland, which is mostly vegetated hills and peatlands. The coherence is likely to be low in the vegetated areas. Although my image pair is only 13 days apart, so I wouldn’t expect any dramatic changes in land cover / movement.
For windows, the exe files have to be compiled first using cygwin, but that’s not so complicated. Let me know if you want to give it a try and I’ll send you a document with instructions.
great, happy to hear that this solved the issue!
Raises hopes that this error will be gone in the future (was reported quite frequently, but I never understood its actual cause).
I had this warning during the unwrapping then I had an error “A java.nio.file.InvalidPathException exception has occurred” while selecting the .hdr file while importing.
What could be causing this warning? I have selected 200 Row Overlap and 200 Column Overlap during snaphu export
I am sorry I don’t know how to check the raster’s (column/rows), well, if the s1tbx products are readable by other software, I can check but it’s not possible.
the number of rows is the number at the end of the snaphu command. But the first screenshot indicates that the unwrapping is completed (two UnwPhase_ifg files).
The error message indicates that there is something wrong with your path. Is the data located on a network drive?
Please try to move the exported folder to a simple path (C:\temp\ for example) and try to import the unwrapped phase again.
Mr. Andreas you are great, I have created a simpler path and the import was accomplished successfully, Although I made several imports through very long paths in the hard drive and never had this problem, perhaps there’s unwanted " " space in the path address I couldn’t see. but thanks again