SARPROZ ©

Yes, you found the answer. I was wondering whether you were saving your results after processing.
Please notice 2 things:
a. in your descriptions you’ve never given all the needed details to understand you case. Even more, you descriptions were wrong (you were speaking about the APS module)
b. if you would keep reading the messages from the…[Read more]

I know the reason, it seems SARproz does not calculate the deformation velocity if you use non-linear estimation mode(as smart 5). I rerun the APS step and the SPP step using linear estimation, now the result is obtained.

If you are right, then why the velocity was not generated after the step of SPP processing was done? I rerun the SPP step, still not result.

first comment:
Sarproz was designed in a way that you never need to repeat steps. even if your computer suddenly crashes in most cases sarproz can recover the job avoiding to start over again.
second comment:
the APS module is aimed at estimating the APS (Atmospheric Phase Screen), not at estimating/saving results as velocity and DEM.
For that,…[Read more]

I rerun every single step since co-registration, though time consuming, still no result. It seems the vel.mat is not generated in the APS step. Why does it happen?

Sorry forgot to compress the file

Hi Yuxiao,

the interferograms (resp. their coherence) is striped again with the new version.

Regards, Ivana

Hello Yuxiao,

I reprocessed the dataset with the new version. One black strip is again present in (coregistered) 20150504 and 20150516, as these are the two images with earlier timing, so the area of interest is not completely covered. The extracted slaves look ok, but they are thinner (less lines). This is probably the source of the problem.

I…[Read more]

Dear Ivana,

1. Update to the newest sarproz version and all the problems with bad interferogram should be gone. You might need to start from the very beginning..

2. I failed to replicate your scene where the black strips happened in image intensity, especially in slave image 20150504. Can you tell me your specific parameters in ‘SLC data…[Read more]

Dear Ivana,

1. Update to the newest sarproz version and all the problems with bad interferogram should be gone. As I mentioned above, the failure in tops-post-processing is the reason why those interferograms fails. Now please try with the updated sarproz again. You might need to start from the very beginning…

2. I failed to replicate your…[Read more]

Hi Yuxiao,

one more note:

I have now reprocessed the area once again with more images, and again: the first two (different days) look OK, the others are striped (with the same version of sarproz).

Regards, Ivana

Hi Yuxiao,

one more fact (do not know if it is caused by the stupid error you mentioned or with the problems with topography as mentioned by Daniele earlier):

having now more interferograms, there are more of them “reasonable” (i.e. not striped coherence), but many of them contain phase fringes in the azimuth direction and their frequency is not…[Read more]

You are quite right, I did not discern the host address is changed due to the wireless internet reconstruction in our department, now I changed to the wire internet, it works smoothly. Thoroughly thanks!

Hello Yuxiao,

yes, the reasonably-looking interferograms are 20150305-20150703 and 20150317-20150703. I am now processing more interferograms (full graph) to see whether more interferograms are reasonable.

Ivana

As I said, it’s a network problem.
Did you resart Matlab?
Check hostname and IP address. There is a conflict somewhere. The workers try to send signals to the main Matlab instance, but it’s addressed in a wrong way and so the parallel job freezes.

As I said, it’s a network problem.
Did you resart Matlab?
Check hostname and IP address. There is a conflict somewhere. Matlab tries to send signals to the workers, but they are addressed in a wrong way and so it freezes.

I forgot to mention, the PS numbers and connection is in the screenshot below

I crop the area smaller, which up to 5000 * 6000 pixel, but it still frozen there, since I set the DL=0, the top command shows only one eternal occupied process is by MATLAB, though somehow parallel MATLAB workers show sometime.

The graph processing has been running for up to 50000 seconds, I am playing on 4 core 16 GB RAM machine, is that…[Read more]