SARPROZ ©

I used latest version, 15th June.

I am trying to add new S1 SLC image in the processed data. when try to run the set orbit after selecting the update option its giving some error. Please see the attached.

Thank you very much! I use oldthe er sarproz version solve the problem.
otherwise, I use QPS method to process these 14 ALOS data, when I select QPS point which strategy will be used? Amp.stable.Index 1-sigma or Amp.stab.Ind plus Sp. coher or Amp.stable.Mu/sigma??
thank you very much

probably your updates-license has expired.
one suggestion for the moment: the error you get derives from new polarimetric features (introduced in march 2016) that where not contained in the old gamma-like format. if you kept older sarproz versions (before march 2016) you can switch back to an old version without the new full polarimetric support…[Read more]

it’s just a screenshot.

when I check online to update the SARPROZ,it saied that No new uodates for your license.

sorry, for some reasons the file was not correctly uploaded…
please try again!

I update it and it saied it is latest version

Hi,
I use the latest version 17-MAY-2016. I use linux version.
Thank you!

you should update the code with the last version
then let us know

HI,

I import ALOS data after co-Registration by GAMMA software，but there always has an error.

I don’t know why?

Thank you very much!

Hi Ben,
first of all, when you get an error, please zip log and lasterror.mat files and attach the zip archive here.
Secondly, there exist no “SBAS” processing in sarproz. However, you can choose processing options that can make something similar.
You do not need to process a FULL graph, you may want to process only a subset of…[Read more]

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?