SARPROZ ©

Hi Dear Ivana,

The bak file is a backup file so that when the fine-coregistration failed for one of the slave images, the code can “roll back” to this previous not-fine-coregistered version.

Apparently in this case the code failed to “roll-back”. A simple manual solution would be to change yyyymmdd.b.back to yyyymmdd. This is the not-fin…[Read more]

Hi Yasser,

Sorry for the late reply. I forgot to submit the code last weekend. I’ve just submitted the correct code to the developer yesterday and you should be bug-free in the next update of sarproz. Sorry again.

A description of tops post processing can be find in chapter 4.3 of this conference paper:…[Read more]

Tomorrow by latest. Meanwhile, I would suggest to increase your area step by step until you reach maximum area. If you get these warnings, it would mean that it will be very difficult to obtain reliable results in your later on processing.

yuxiao

Hi Yasser,

The bug is fixed and the next version in sarproz update should see the solving of this bug.

Meanwhile, please take a look at your log. There are a number of warnings like this:

WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!! WARNING!!!
Your area is TOO SMALL for an accurate subpixel coregistration!!!
A linear azimuth ramp…[Read more]

Sorry, it seems to me that you’re using the compiled version.

I’ve updated the code and we will update the compile version soon. Meanwhile (if you can) please switch back to the previous version (that should not have this error).

Sorry for the inconvenience..

Yuxiao

Please use this patch for fixing this error,

thanks for testing out the code!

yuxiao

Yes. SLC images need to have the same relative orbit track number.

absolute orbit number can be read from the file name of your downloaded S1A, and

relative_orbit = mod (absolute_orbit – 73, 175) + 1;

yuxiao

Hi,

An updated code was submitted.

The reason you get this error is because yesterday both of the server for downloading orbit files were shut down and (not start running yet but will be). (And also because there’s a bug in the code not considering fully this situation.)

One more word about S1A orbit file: In case there’s a connection error…[Read more]

Hi Milan,

I am sorry but I’ve missed your previous posts regarding updating S1A images.

The code is not yet optimized for updating SLC images, but I am working on it right now: I am taking a look at the errors and I will get back to you as soon as possible.

Yours,
Yuxiao

Hi Milan,

I am sorry but apparently I’ve missed your previous posts regarding updating S1A images.

The code is not yet optimized for updating SLC images, but I am working on it right now: I am taking a look at the errors and I will get back to you as soon as possible.

Yours,
Yuxiao

Hi Benl,

If you are selecting maximum area, you are not having the same error as Yasser. It would be great if you could post your lasterror.mat and log file so that I can know where the error occurs.

For this particular issue, I have located another bug in the code that sometimes will result in an error. I have fixed it and will update sarproz…[Read more]

Hi,

It seems to me that you’ve had your firewall on and blocked the outgoing connections to download precise orbit files from an external ftp site. Can you confirm that? If you do have a firewall on please try to close it and try again.

If it is still not working I will add a line in the code so that when returning such an error when connecting…[Read more]

Hi Yasser,

I indeed find where the problem is, I will try to fix it and let you know.

Meanwhile, to skip this error, I suggest you select a bigger area (in both samples and lines). This is not only for avoiding the bug, but also is a general suggestion for processing TOPS image. A reference can be found here:…[Read more]

Hi Yasser,

you will need to zip the lasterror.mat together with the log file and upload the zip file so that I can take a look.

Thanks!

Yuxiao

Hi Yasser,

you will need to zip the lasterror.mat together with the log file and upload the zip file so that I can take a look.

Thanks!

Yuxiao

Hi Ivana,

For your second question: since the software is querying one webpage for each date of your image, there are chances that one or more of all the querying are not getting response within the setted time limitation (which is 10 seconds, I think). The reason we set the time limitation for each query is because there is a known bug in Matlab…[Read more]

I want to add one point that:

In small area processing the resolution of your background Google Earth Image goes with your area. If your area is really small then SARPROZ downloads the highest resolution possible. If your area is very large then SARPROZ will download the image with a much coarse resolution. The size of the Google Earth image…[Read more]

your interferograms. screenshot them.