[espiritocz]

Hi,

try to draw the angle to the piece of paper. You will realize that the value -129.6 deg is not the heading of the satellite track, while the value from SARPROZ is really heading angle of the satellite from the North (azimuth angle).

best,

M.

[espiritocz]

ok,

so, I have tried this – i used the same master and put only 4 wrong slaves in a “test” project.
Two of them were extracted (normally?):

4 Slave images have not been extracted!!

Extracting Slave Images

SLC data extraction

Your S1A imgfile: /media/TEMP_90DAYS/processing/test/SLC/S1A_IW_SLC__1SDV_20150825T163428_20150825T163455_007422_00A376_7C99.SAFE/measurement/s1a-iw2-slc-vv-20150825t163430-20150825t163455-007422-00a376-005.tiff seems to be corrupted and NO HEADER INFO can be read!!! Further Process with this image may lead to error!!!

Your S1A imgfile: /media/TEMP_90DAYS/processing/test/SLC/S1A_IW_SLC__1SDV_20150825T163428_20150825T163455_007422_00A376_7C99.SAFE/measurement/s1a-iw2-slc-vv-20150825t163430-20150825t163455-007422-00a376-005.tiff seems to be corrupted and NO HEADER INFO can be read!!! Further Process with this image may lead to error!!!

Your S1A imgfile: /media/TEMP_90DAYS/processing/test/SLC/S1A_IW_SLC__1SDV_20150825T163428_20150825T163455_007422_00A376_7C99.SAFE/measurement/s1a-iw2-slc-vv-20150825t163430-20150825t163455-007422-00a376-005.tiff seems to be corrupted and NO HEADER INFO can be read!!! Further Process with this image may lead to error!!!

Your S1A imgfile: /media/TEMP_90DAYS/processing/test/SLC/S1A_IW_SLC__1SDV_20150918T163429_20150918T163455_007772_00ACE7_BE0B.SAFE/measurement/s1a-iw2-slc-vv-20150918t163430-20150918t163455-007772-00ace7-005.tiff seems to be corrupted and NO HEADER INFO can be read!!! Further Process with this image may lead to error!!!

Your S1A imgfile: /media/TEMP_90DAYS/processing/test/SLC/S1A_IW_SLC__1SDV_20150918T163429_20150918T163455_007772_00ACE7_BE0B.SAFE/measurement/s1a-iw2-slc-vv-20150918t163430-20150918t163455-007772-00ace7-005.tiff seems to be corrupted and NO HEADER INFO can be read!!! Further Process with this image may lead to error!!!

Your S1A imgfile: /media/TEMP_90DAYS/processing/test/SLC/S1A_IW_SLC__1SDV_20150918T163429_20150918T163455_007772_00ACE7_BE0B.SAFE/measurement/s1a-iw2-slc-vv-20150918t163430-20150918t163455-007772-00ace7-005.tiff seems to be corrupted and NO HEADER INFO can be read!!! Further Process with this image may lead to error!!!

An error occurred and was saved in the file lasterror.mat, directory /home/insarist/SARPROZ

If you need assistance, please include the file lasterror.mat

You may include also file 23_Aug_2016_21_11_20_sarproz.log

Here a glimpse:

Too many input arguments.

2 Slave images have not been extracted!!

I tried to look at them, but by pressing “View Ex. Sl.”:

File /media/TEMP_90DAYS/processing/test/EXT/20150825_VV.slc.jpg not found!!!

File /media/TEMP_90DAYS/processing/test/EXT/20150918_VV.slc.jpg not found!!!

File 20150930_VV.slc not found

File 20151024_VV.slc not found

So, I used my script to generate jpg from the extracted slcs (20150825 and 20150918) and checked them – but it seems bad, only a grey area. Probably really corrupted.

Okay, I just created a script to check corrupted tiff files – it is possible to use gdal for it, for example.. and indeed, those files are corrupted.

so…. what was the aim of this investigation?
should i use also one good image?
yes..

okay, trying to include also one good image. again pressing SLC import (now there are 5 slaves – 4 corrupted and 1 good). the result is:
the good one was extracted normally.
So, I could not reconstruct this error – it seems it was caused by something else but I have no idea what caused it.

So, I am sorry Yuxiao, I did not help in debugging….

Thank you for your time.

Milan

[espiritocz]

Thank you Yuxiao, in the meantime I tried something else:

I have removed the corrupted files and removed also these wrongly cropped images, re-extracted slaves and – it is working normally now..

I would like to recommend some test for corrupted files. Also, I don’t understand why the presence of one corrupted file caused that another file was cropped in different area..seems like this is what happened here.

Anyway, it is indeed up to user to double check his files J

So, thanks so far, I continue working. Cheers!

[espiritocz]

Hi Yuxiao,

thank you.
So, I have realized that the coreg-erroneous slave images are cropped from totally different area!
(it is strange, even the jpg previews were not generated, i had to do it manually and saw that they are after Slave Extraction from totally different location.. please note that I use precise orbits normally here…)

Let’s try it only for one track (i choose track 51 where 27 images were coregistered well)
I attach the footprints and screenshot.
I know exactly which ones are not coregistered – there are 11 images:
20151121
20151203
20151215
20160108
20160120
20160201
20160225
20160320
20160413
20160425
20160519

I know which ones were not extracted. It seems that really some of them were corrupted. I am checking them one by one now..so, let’s say the problem is reduced only to this coregistration error, caused by wrong cropping of these 11 images.

Thank you.

Attachments:

You must be logged in to view attached files.

[espiritocz]

only adding a comment – the coregistration errors are accompanied by following message:
Error in amp_corr(): Match parameters missing!

do you have any clues?
thank you

[espiritocz]

hi Dan,

thank you very much. I have recreated the Image.conf using the command you wrote me. Everything works well now.
I will perform the same processing steps in another area to see if i can recreate the error. Anyway, it can be also again caused by the permissions due to my VM system, maybe due to accessing the structure from matlabpool?..

anyway, probably the problem is on my side.

thank you,

milan

[espiritocz]

hi,
I have tried once more (with another S-1 dataset) the SLC update process.
Unfortunately, it again failed – can you give me some advice about what can be the cause of these problems?
This time I had in my SLC folder all the previous data and only provided new 5 images..

Thank you very much – I attach both log and lasterror.mat files..

Thank you,

Milan

Attachments:

You must be logged in to view attached files.

[espiritocz]

hi,

i am sorry, now i have zipped the lasterror.mat file properly. Unfortunately I cannot give the .log file since it will contain much more processing now. Is the log file necessary?

Thank you,

Milan

Attachments:

You must be logged in to view attached files.

[espiritocz]

seems working – thank you very much! m.

[espiritocz]

ok, i see now about the attachment – thank you.
ok, i will try pcodes

[espiritocz]

ok, again the extension was blocked – what filetype should i send you? .zip?

[espiritocz]

well, it seems i cannot send .mat files, sorry (security reasons?)

[espiritocz]

Dear Ana,

Indeed the area should be larger – don’t worry to extend it. To check the small area (after you prepare project using bigger area), there is special Toolbox in Sarproz called Small Area Processing. It works very well!

Milan

[espiritocz]

Dear Daniele,

thank you for fast response!
I will test it now (Manage Version shows the last to be from 27-Apr, is it the new one?).
The topic of AOI is subsidence of buildings – three weeks ago a dangerous movement was (accidentally) detected over one building. With this dataset we may detect this movement in similar way you did for Hong-Kong, we’ll see.

Milan

[espiritocz]

Hi, thank you.
indeed, the orbits have huge errors, showing also strong phase ramps.
I will send you one image for reference using ftp (in private message). thank you!

Milan

[Author]

Posts