SNAP2StaMPS version 2: new features and new sensors supported

Hi,
I am stuck at another step. While running “mt_prep_snap” I am getting the following error. I have checked all the dependencies and the files as well. Everything seems to be okay but the error is persistent.
Can you please guide how solve this?

I would say that most probably you compiled the src folder of StaMPS using a newer C compiler. it should be around in the forum already the solution.

One of those : Segmentation Fault (core dumped) error during mt_prep_snap - #17 by ABraun

Let me know.

Best

Perfect.
The problem was GCC compiler. I have ubuntu22.04 and gcc7 is not compatible with this version. So I created distrobox, created an image of ubuntu18 in that box, and compiled the StaMPS in that box. I ran “mt_prep_snap” in the box. After that all the other steps are performed in the Ubuntu22.
For distrobox creation i followed the steps mentioned below:
sudo add-apt-repository universe

  • sudo apt update

  • curl -s https://raw.githubusercontent.com/89luca89/distrobox/main/install | sudo sh

  • sudo apt update

  • sudo apt install podman -y

  • distrobox create -n stamps-env --image ubuntu:18.04

  • distrobox enter stamps-env

  • sudo apt update

  • sudo apt install build-essential gawk tcsh -y

  • Final Recompile (In the distrobox):

    • cd /home/ehtasham/StaMPS/src (directory where the Stamps src present)

    • Open the Makefile and ensure CC = g++. (can be done in text editor)

    • make clean

    • Make

    • sudo make install

For me the StaMPS is working now.

Hi Jose Manuel (@mdelgadoblasco),

I am encountering a major is sue with the quality of the interferograms generated by the snap2stamps workflow. As seen in the attached images, the raw interferogram (fist) is completely decorrelated, and even after Goldstein filtering (second), the characteristic fringes are missing.

Due to this extreme noise, the mt_prep_snap step results in empty output files because no PS candidates can be identified. I suspect the issue stems from a coregistration or Back-Geocoding failure during the SNAP processing stage.

Do you have any suggestions on how to troubleshoot this loss of coherence in the automated workflow?

Best regards