SARPROZ ©

Hi Matus,

if you are running 2 instances of Matlab together, one instance may have opened a pool of workers exhausting your resources.
So, if the second instance opens a spmd process, it will return an error because no resources are available.
You can solve this issue by halving the number of workers for both instances.
Say that you have totally…[Read more]

https://www.dropbox.com/s/1c16o7ozj6a3447/lasterror.mat?dl=0

https://www.dropbox.com/s/g1yloq5hrxxyiz9/14_Jul_2015_11_36_19_sarproz.log?dl=0

If you are processing PS-like targets, use the star graph.
If you are dealing with distributed targets, it’s better to use a multi-master graph.
The MST is theoretically interesting, but practically it’s better to use more connections to stabilize the inversion.
If you use the (spatial) coherence as weight, it’s strongly suggested to use a…[Read more]

Hi Ivana
at this moment this calculation is not published.
The std dev in the paper mentioned by you is a statistical quantity.
The one listed in the sarproz output is a value calculated for that single time series.
The point is: the solution of the estimation is found as the peak of the periodogram.
How sharp is the peak? If the movement is…[Read more]

Hello Daniele,

I am getting slowly into it.

I understand there are two standard deviations – one evaluated from the coherence, using e.g. Colesanti 2003, and the other one evaluated here (can you recommend a paper where to read more?)

I understand it is a measure by which the variable (velocity, height) could change with no (significant) change…[Read more]

Hi Ivana,
some comments:
a. the standard deviation of the velocity is a measure of the peak width of the periodogram. It’s not a global parameter as the temporal coherence, it’s local (giving a view around the estimated parameter).
b. if it would simply be correlated to the coherence, it would not be useful. By already having the coherence, you…[Read more]

ok, as the csv could not be attached, i am putting some lines from the file:

VEL SIGMA VEL KTEMP CUM…[Read more]

sorry, you are right.
The cumulative displacement is calculated using the model you chose for the time series analysis.
This reduces possible noise.

Then, the cumulative displacement shouldn’t be equal to the displacement for the last acquisition?

I give you a concrete example:

20120803 (First Acquisition): 0.00
20120819: 0.43
.
.
.
20150112 (Last Acquisition): -14.53 —-> This is the displacement of 20151212 respect to 20120803??
CUMULDISP: -15.54

The time series in the site processing are referred to the first acquisition.
In the small area processing you can choose whether to refer them to the first acquisition or to the Master one.
However the Master acquisition may be noisy, so, the sw estimates an error and it removes it (so, the value at the master may be not zero).
The cumulative…[Read more]

Hello Daniele,

I have a doubt regarding the fields YYYYMMDD (created with the time series option) which seem to be showing displacement values. These values refer to a cumulative displacement (i.e. the cumulative displacement at date 20010721) or to the single displacement registered for that acquisition (in that case, respec to to whom or when?…[Read more]

yes, that is something to be tided up.
Initially, the Cum Disp tool was generated to calculate it based on the estimated coefficients of a polynomial.
Later on, I invented the smart tool, which is a non-parametric time series analysis.
So, the Cum Disp tool is consistent with the rest of the results (and it calculates the proper things) only if…[Read more]

The small area processing has been designed as a process independent from the full site analysis. Even if they can interact (see b).
So, my suggestion is:
(a) if you want to carry out different processing sessions with different parameters, you should save every time a different small area dataset. You do this using the “save” button in the small…[Read more]

Hello Daniele,

I’ve tried to generate Cumulative Displacement files covering different periods of time, entering different dates in the Cumulative Displacement tool. However, when exporting to KML/KMZ I think I’m always getting the same file,as the initially generated for the complete temporal length. covered by mi images. Looking at the logfile…[Read more]

Hello Daniele,

Thanks you, now it is clear for me

Cheers,
S