Yes, some steps are quite fast, I also wondered.
The AOI is roughly 10x10 km but some of it is covered by water and might not be usable at all.
Thank you for the offer! I think I might first just test another area to see if turns out different. Could be that the area I selected is not suitable for PSI. But I’ll let you know, of course.
Thank you again for your support!
Maybe the weeding thresholds you used are strong.
Or as you said, that area is not the best one to get PS points.
you were right. Increasing the standard_deviation to 1.4 resulted in 4000 PS and the plots look reasonable. I’ll investigate this some more.
Cool! I am glad that my advices are still useful! 
It would be nice if you could share some plots with us.
Just to have shared a sample of the first PSI results obtained with the snap2stamps scripts by the first time*! 
Looking forward to it
*first time without counting myself
I will, of course!
I keep getting an error now with slaves_split
Error: [NodeId: TOPSAR-Split] -1
I looked at splitgraph2run.xml and found that the output raster was defined as
D:\S1_Mexico/split/20150802/20150802_D:\S1_Mexico\split\20141006\20141006_IW1.dim.dim
What format does the
PROJECTFOLDER= in project.conf need if I am running Windows? I can’t remember what I inserted the first time when it worked.
Hi @ABraun!
The PROJECTFOLDER should contain a full path where can be found the slaves folder.
My guess is that if the step 1 on the slave preparation worked, it might not be because of the PROJECTFOLDER.
Could you provide more info about this? Had you run step 1, right?
Was your first try also run in Windows OS? I have tested only in several linux distros.
Let me know if this helps.
it was the same machine and as far as I know I entered a full project folder in both cases. Step 1 was successful, all data was sorted according to the acquisition date. I am currently repeating it from scratch, now it works again…
Strange, but as long as it runs - fine 
So now it works? Cool !!
Let me know. Thanks
how is the MASTER to be defined in project.conf?
I added the full path to the split product but nothing happens and the command shell returns to enter mode.
If I enter anything else I get the message “split product is expected”.
I really wonder why everything worked like charm with my first dataset and now there is this strange behaviour…
Indeed I am still wondering what you have changed from one processing to the other as the software that you are using is always the same.
the MASTER variable in the project.conf must be the full path to the splitted and orbit corrected master (processed with SNAP) in BEAM-DIMAP format.
In case you might need it, you can give me more info about the dataset and parameters so I can try to reproduce your problem. Or we can see it together
Let me know
thank you. So this is simply the outcome of splitting_slaves.py, right?
Not really! For the MASTER… as written in the SNAP2StaMPS_User_Manual.pdf I suggest to do it in GUI, ensuring that the selected burst cover the entire AOI (as with the splitting_slaves.py you get entire subswath (that could be also used, but then the processing time needed is much higher than selecting few burst only for the MASTER)
I hope this helps.
Keep me updated
I see, thank you. This didn’t become clear to me when reading the manual, to be honest. What could be helpful would be a flow chart of the order of all included steps so the reader has an idea of what is to come.
However, simply applying all scripts technically worked the first time I used it. Probably because it was only one burst.
I will try it as you suggested.
Thanks for the feedback!
In fact it is good to get real users’ feedback so I can improve the manual for next release.
You are right and there is nothing wrong with just applying the scripts, but full swath interferograms takes much more time if the AOI can fit in smaller area to process.
Full swath should work as well…there is no limitation for that, maybe memory allocation should be better consider while configuring SNAP I guess.
Let me know
so the extent of the master image defines how much of the slaves will be used for the coregistration and interferogram formation process?
Not exactly, but the time and space needed for processing increases with the size. Let’s say that 2 burst MASTER takes on my 8vCPUs and 32GB RAM only between 2-3 mins. Full swath can take about/over 1 hour.
Internally I do not know if SNAP is able to get directly only the slave burst(s) matching the master extent. Maybe somebody can reply to this question (@marpet)???
now I get it, thank you!
I don’t know much about SAR processing. I hardly know what bursts are
So, I can’t answer if this is possible. Maybe @lveci or @jun_lu can answer this.
is it a problem when the bursts are shifted along-track?
I get the message at step three, coregistration:
Error: [NodeId: Back-Geocoding] Same sub-swath is expected.
