you can check his dissertation where he explains some more details: https://web.stanford.edu/group/radar/people/Hooper_Thesis.pdf
Otherwise - Hanssen 2001 is always a great source: Radar Interferometry: Data Interpretation and Error Analysis | SpringerLink (not open access)
anyone knows the meaning of "master_master_flag = ‘0’ " in stamps(1,1)
Good evening. Please tell me, I’m trying to export to PS. But my workflow has been going on for several days and it shows 8% all the time.
My computer has 32gb of ram and I’m running on an SSD. I tried to run it again, but again 8% and it’s been like this for a week and it doesn’t show any errors. I would be very grateful for your advice.
close snap and restart it ,and rerun export
Hello, i meet the same problem, have you solve it? looking forward to your advice.
Hello ABaun,
I tried to make Psinsar using the snap2Stemp workflow. Following the steps mentioned in the manual, I got to the StaMPS export step, and as a result, a project folder contains the final output structure in four folders: rslc, diff0, geo, and dem.
Later, I installed Stamps, in order to run mt_prep_snap.
I know that I have to make some modifications to the configuration.
My question is: which lines should I modify within StaMPS.CONFIG.bash?
Thanks in advance.
Best regards
Hello,
I seem to have the same issue. How did you end up resolving the Window’s matlab issue to get past the permission denied error here?
Thanks for the help!
Hey guys.
I am new to using StaMPS for the PSInSAR technique. And I would like to know which StaMPS setparm corresponds to spatial coherence?
Thanks in advance for everyone’s attention.
Hello, I have 12 interferograms from February 14, 2020 until July 31, 2020. I applied all the steps in stamps and got the results, but I want your help in evaluating the results of the processing in. Do I have any errors? Do the results look logical because I want to export the results to gis and calculate the vertical displacements in my area? Please help me. Evaluate my results before continuing to analyze them in gis
Hello, does anyone can help how to select or count pixel density at a specific area by using stamps?
Thank you.
I have successfully resolved a similar problem. I followed the instructions on blog csdn net website
The main point is that because an image is not perfect, we just need to delete it from the list that we want to process or replace it with a new image.
How to check it at the terminal prompt after running mt_prep_snap, type in the search tab “warning”. Check the image date and you can change or replace it. Then repeat the process of backgeocoding, deburst, interferogram formation, export StamPS after replacing the imperfect image.
Good luck
@ABraun @mdelgado: Dear Sir, I have been working on some research project using PS-InSAR for few months now. When i started working on one of my research work and followed all the steps for Data Preparation using SNAP2StaMPS and started to proceed with StaMPS using MATLAB. For the first time i find some error which is unique to me. I tried to find the solution of this problem for one week now but its just killing my time. I have worked with PS-InSAR in some other research work as well and i have some results before. But, i am stuck in stamps(1,1). The error is as follow. Please can one help me to get rid of this problem. It would be so greatful to receive your feedback and suggestion on the error below.
logit function :
The logit function is a function included in the StaMPS matlab folder, so it makes me think that you may need to add the stamps path in matlab PATH environment
please try :
addpath(‘<PATH_TO_STAMPS_FOLDER>/matlab’,path)
changing the PATH_TO_STAMPS_FOLDER with the correct path of StaMPS package on your PC
I hope this helps.
Best,
Does anyone have experience using the latest SNAP 10.0 version in the Snap2STaMPS processing? The results are fine until the mt_prep_snap command, which fails. The reason is @badly formed number.
I noticed that when using the commands splitting_slaves.py, coreg_ifg_topsar.py and stamps_export.py the same message is received which reads: "SNAP STDOUT:b’WARNING: An illegal reflective access operation has occurred\r\nWARNING: Illegal reflective access by org. esa.snap.runtime.Engine (file:/C:/Program%20Files/snap/snap/modules/ext/org.esa.snap.snap-core/org-esa-snap/snap-runtime.jar) to method java.lang.ClassLoader.initializePath(java.lang.String)\r\nWARNING: Please consider reporting this to the maintainers of org.esa.snap.runtime.Engine\r\nWARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations\r\nWARNING: All illegal access operations will be denied in a future release\r\nWARNING: org.esa.snap.core.util.ServiceLoader: org.esa.snap.core.gpf .OperatorSpi: Provider eu.esa.opt.meris.sdr.aerosol.AerosolMergerOp$Spi not found\r\nWARNING: org.esa.snap.core.util.ServiceLoader: org.esa.snap.core.gpf.OperatorSpi: Provider eu.esa.opt.meris.sdr.aerosol.ModisAerosolOp$Spi not found\r\nINFO: org.esa.snap.core.gpf.operators.tooladapter.ToolAdapterIO: Initializing external tool adapters\r\nINFO: org. esa.snap.core.util.EngineVersionCheckActivator: Please check regularly for new updates for the best SNAP experience.\r\nExecuting processing graph\r\n…10%…20%…30% …40%…50%…60%…70%…80%…90% done.\r\n’
I tried with SNAP 9.0, and there are no problems.
Does anyone know how to overcome this issue?
snap2stamps has not been tested yet against SNAP10. If SNAP 9 does the work, please use it instead for now.
For what I see you got warnings but no error messages from SNAP 10, so I am not sure what the issue is.
@mdelgado, thank you for your comment.
Indeed, interferograms are successfully created using SNAP 10. The issue arises with the mt_prep_snap function, displaying the error message: “Badly formed number.” I don’t have coding expertise, but I suspect the problem lies with the interferograms, as there are no issues when using SNAP 9.
However, the SNAP 9 version usually does not display the third sub - swath (IW3) on the newer images from October 2023 onwards, and my AOI is located precisely in that band.
But since SNAP 10 is not fully operational yet, I will wait for its testing to be completed.
what you can do to allow SNAP9 recognise the IW3 is to unzip the S1 image and zip it again…or to unzip it and let snap2stamps find the SAFE folder instead of the zip file.
@mdelgado thanks for the useful advice, it works. I unzipped and rezipped the problematic SLCs and now they are fine.
have you found the reason for this error?
