The PATCH folders are not in an ideal directory. Running StaMPS will export files in its bin folder along with script files. It is recommended you rerun mt_prep_gamma and export in the master InSAR directory (where diff0, geo, dem, rslc are located).
I have renamed my ps_initial_…(changed) file to the ps_initial file and removed the older “initial” file.
I have also done what some may have suggested as change the gamma in the getparm/setparm.
@ABraun I am using Linux Ubuntu but I also received the same error as you. Any new findings?
I am looking to view PS in highly urban area but there are a few nature reserves around, hence there should be obvious non PS areas in my project if it does succeed.
It is a late response but maybe it is still helpful for you, and maybe it will be helpful for others. I just got the same error index out of bounds because size(ij)=[0,0]. I recognized that one scene was not processed properly. I noticed it during the mt_prep_gamma_snap step before entering matlab:
The scene of 2017 Nov 08 seems to have zero mean (see the WARNING message in terminal), which is highly suspicious. I had a look at the stack in SNAP and all bands of this date were empty. I think the error occurred during ApplyOrbitFileOP but I was not able to redo it. After processing a new split, apply orbit file, stack, deburst, subset and export, the warning during mt_prep_gamma_snap disappeared and I was able to run stamps(1,1) without a single problem!
It is good to see you could handle some of error. I wonder after you changed the scripts ps_load_initial_gamma and mt_prep_gamma_snap, did you do mt_prep_gamma_snap step again and then just typed stamps??? I see stamps(4,5) so you need to do same steps with new scripts. Also is pscands.1.ij file empty or not?
After you do same steps again you will see psver.mat file, the program could not find this file right now.
Hi @gabrielaquintana77 your screenshots and errors are very similar to those @hchong005 posted here. Please have a look in this thread, and follow the described steps, they may solve your problems.
Hello everybody.
I’m trying to do InSAR from two Sentinel-1A images.
Based on @bayzidul steps, i’m wondering about two steps inside:[quote=“bayzidul, post:252, topic:4981”]
Apply TOPS split and then Apply orbit file.
Add scenes (Master+Slave1 and Master+Slave2 and so on ) to do the Backgeocoding separately for each Master-Slave pair.
Create Stack of Backgeocoded images (master_Stack1, master_stack2 and so on).
[/quote]
I’ve done with the first step.
Now I’m trying to do the back-geocoding for only two images. When I was performing Radar > Corregistration > S1 TOPS Corregistration > S1 Back-Geocoding and click Run, the warning “Not able to write product” shown, so the process failed.
But when I did the back-geocoding for each image, it worked well.
The problem arised when I tried to stack those both images through Radar > Corregistration > Stack Tools > Create Stack. The error message “[NodeId: 2-CreateStack] S1 TOPS SLC products should use TOPS Coregistration” appeared, so I have no result of S1 TOPS Coregistration.
Please read the previous comments and then you will find some limitations and recommendations of PS processing with Sentinel-1 data using the combination of SNAP and StaMPS.
If you are using the current version of SNAP-6 then there are some changes in the steps that we had written here in previous discussions.
From my experience, you need at least 16GB memory and it is way more better to work in Linux. From you snapshots, my comment is to change the PC configuration first and even you have to choose the correct Geocoding method.
Thank you for your fast reply!
Maybe because I’m using SNAP-6, the steps I following had been changed
I will try to use another computer with greater RAM size to do the back-geocoding correctly.
Yes but you changed the name of script to mt_prep_gamma or did you just copied and pasted new script into matlab folder. Because your command should be start mt_prep_gamma_snap not just mt_prep_gamma if you did not replaced with new one.