SARPROZ ©

Dear Yuxiao,

I have sent you the site log file to the provided email address.

In the meantime I will check out “orbits only” coregistration.

Thanks!

Hello Steffan,

Thanks for the post.

The first few azimuth ramps seem very likely to be caused by the initial coregistration accuracy not good enough. In the next paragraph, I will explain how to tackle this problem.

I am not sure about the ramps on the range direction, though. It might be orbital errors, but we need to check the logs.

The…[Read more]

So I re-cogistered the dataset (I know I didn’t have to, oh well) and increased the number of reference points to 500K. Didn’t notice any errors except S1_Stitching like before. Using Max Area for AOI selection.

Then I changed to MST graph I processed Interferograms. There still seems to be a lot of problems…

Ramping in numerous images, here…[Read more]

It still show the stop running message like I told yesterday.

open a terminal (command prompt), cd to the folder where main.exe is, launch the application from the terminal by typing “main.exe” and pressing enter, then tell us what messages you get

Hi , I have re-installed MCR V83 and added to the system path. The former message didn’t show again but the main.exe always stops running when I open it. I have changed to the win7 or vista settings but it still didn’t work…LOL

this means that the installation of the mcr was not successful
try again
and check if the directory where you installed it is in the system path. if not, add it manually to the system path

Thanks for your reply, Professor.

I was able to write the value of Max Matrix Size according to your suggession, equal to 50.000.000, in the advanced parameters. However, i still notice something weird in the result. The result of displacement and height are still similiar. The height isn’t similiar with the DEM.

Is my statement correct ? Or…[Read more]

Hi Rajabun,
this is indeed a visualization bug. What is visualized is the content of the jpeg images which is written in a 0-255 scale. While we work to fix it, you can circumvent the bug by temporarily change the Max Matrix Size value in the advanced parameters https://sarproz.com/manual/adv_param.html In your case, you should write a value equal…[Read more]

when you have an error, post the log and lasterror.mat

Check the website manual for managing versions:
https://sarproz.com/manual/manage_version.html

Check the following tutorials for importing, coregistration and other steps:
https://www.sarproz.com/yuxiaos-tutorials/

If you are working with the LA_small sample data you don’t need to coregister; otherwise, if you are downloading SLCs of your own…[Read more]

hello,
even I am experiencing the same error with the data import. please, help me with this error
thankyou in advance

we are now uploading a fix.
to temporarily solve the issue, you could switch back to a previous sw version.
The APIDelay was first introduced on March 24 and then modified on April 19

We are seeing the same error message. Data is set up following the same procedure that we usually use, although we are on a new machine.

hi
the error you report is in fact a small bug, an updated version will soon be uploaded online.
however, in normal conditions you should not get such error. it is not clear to me what you are trying to do.
check well please the instructions in the tutorial. make sure data are in the proper folders and try again.
best

Hi Carolina,
you should reduce the size of your attachments (pictures), the maximum allowed should be 2MB.
There are many ways to export results to google, you do not say how you did it.
In your case, you should use the “GeoOut” function in the “filter/matrix visualization” frame in the “scatter plots” module:…[Read more]