SARPROZ ©

Hi Dan,

this effect was caused by the fact that the weather download (update) was performed between the small area processing and the display (geocoding), probably after save/load. So, it helped to reprocess it and display again and the lines are already straight.

I am sorry, still getting into the system…

Ivana

Thank you for the explanation.

However, in this case (see the log or the report I attached last time) the coregistration “concluded successfully”. I encountered this problem two times for different masters (there are not many possibilities for master selection due to weather and perp baselines) – and I never encountered it before… So, should I…[Read more]

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 Yuxiao,

I am sorry for this error, it is my mistake. I really mixed one ascending image into the descending set. However, the date reported is significantly different from the one it really was: while the ascending image is 20160224, the reported one was 20150329, and then 20150410.

Very sorry for that,

Ivana

normally… attached

how is the plot of the temperature as a function of the acquisition time looking like?

Thank you, it works for my first AOI (I checked only if the model line is fractional or not).

However, in my second AOI, the model line is a straight line for most of the time, however at the end, it gets fractional again.

The weather data is complete here so that I do not understand it. However, as you answered me recently in a different topic,…[Read more]

If the comparison is between data exported after processing them with different options, this is the answer:
lat and lon coordinates are estimated using SAR coordinates + the height estimated from phase time series
if you process phase time series using different options for the movement, the height (which is jointly estimated together with the…[Read more]

Hi Ivana,
sorry for the late answer, your matter highlighted a bug that needed some attention.
A new version is going to be uploaded in the next hours and the model mov/temper stuff should be fixed.
However, I do not understand what you mean when you say that there is a small change in lat and lon coordinates: what are you comparing to see the change?

Thank you very much. I changed the non-linear weights and it worked.

this may happen when your graph is broken (not connected) either because of a bad graph topology or because low coherence isolate a portion of the graph.
In the first case you have to re-generate the graph making sure it is connected.
In the second case, you have to change the non-linear weights in order not to isolate any areas. In this second…[Read more]

Hello,

thank you for the new version.

I still encounter an error with multiple imaging modes detected. For this one set, on my computer (did not try yet this dataset on the supercomputer, and did not try other datasets on my computer). I already reported this problem in the beginning of April.

The problem emerges in the “get contents” step.

I…[Read more]

Hi Ivana,
a new linux version is now available!
d

Hello,

please, if the new S1 (coregistration) scripts were already updated, can you also please upload the linux-compiled version? The last version available is still 12-May.

Thank you very much, Ivana

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]