SARPROZ ©

Problems can be solved by doing things step by step from the beginning.

Step 0: read this https://www.sarproz.com/groups/sarproz-group/forum/topic/forum-general-rules/
In particular for what concerns files to include when one encounters errors

best

correct.
if you are using matlab, you can type “fast” at the command prompt, this will load all important variables and file names. the you can use “leggi” to read the data, with Type=1. here the help:
Data=leggi(FileName,S,L)
Data=leggi(FileName,S,L,[Svet,Lvet])
Data=leggi(FileName,S,L,[Sin,Sfin,Lin,Lfin])…[Read more]

Thank you for the suggestion.

But how can I’ve never used the compiled version yet. Could you please tell me how to open the compiled version, and how to luanch the co-registration in more detail ?

Best regards

sorry, no idea. since it’s the most recent version of Matlab, then the suggestion is to write to Mathworks reporting the error.
to temporarily solve the problem, you can use the Sarproz compiled version. you just need to launch the co-registration in the compiled version, then you can switch back to Matlab for doing the rest. The Sarproz license…[Read more]

yes, this file exist. And the output of “license(‘test’,’Image_Toolbox’)” is 1

is this possibly a compatibility problem ?

Sorry, it seems we overlooked your post…
It sounded a system/permissions problem anyway…
But, never mind, now it works…

This problem is not present anymore with upload version from 31-May, I have successfully uploaded version by manage version module.
Thanks anyway…

does this file C:Program FilesMATLABR2018atoolboximagesimagesprivateresampsep.mexw64 exist?

what is the output of “license(‘test’,’Image_Toolbox’)” at the matlab command prompt?

Please find the attached lasterror.mat

you need to include a lasterror.mat file

Hi,

I have problem updating to the newest version of SarProz (29. May),
whenever I try to update it via Manage Vesrsion model, I alwasy get the same error
“Unable to write file “C:SarProZarchivetmpmain.exe”.
The entry may be password-protected or encrypted.”

I always start SarProz with Run As Administrator. But, since today I have noticed
that…[Read more]

Hello Steffan,

Could you send the log of this new one to me as well? I will start to investigate from there. I will probably ask for more files but I will check see the log first for signs.

Thanks!

yuxiao

Dear friends,

I have good news and bad news…

Good news – Using “orbits only” coregistration parameter not only made coregistration much faster but also corrected the failed interferograms from before, excelent!

Bad news: There is still ramping, mostly in azimuth, and strange results.

A – First the ramping pairs:

B – Now the…[Read more]

Dear Yuxiao,

I have sent you the site log file to the provided email address.

In the meantime I will check out “orbits only” coregistration.

Thanks!

Hello Steffan,

Thanks for the post.

The first few azimuth ramps seem very likely to be caused by the initial coregistration accuracy not good enough. In the next paragraph, I will explain how to tackle this problem.

I am not sure about the ramps on the range direction, though. It might be orbital errors, but we need to check the logs.

The…[Read more]

So I re-cogistered the dataset (I know I didn’t have to, oh well) and increased the number of reference points to 500K. Didn’t notice any errors except S1_Stitching like before. Using Max Area for AOI selection.

Then I changed to MST graph I processed Interferograms. There still seems to be a lot of problems…

Ramping in numerous images, here…[Read more]

It still show the stop running message like I told yesterday.

open a terminal (command prompt), cd to the folder where main.exe is, launch the application from the terminal by typing “main.exe” and pressing enter, then tell us what messages you get