GAMMA Questions

This is a multi-part message in MIME format.
--------------uUFpqeZkIATSQQ3sSus8NMK8
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello Igor,

The error comes about because you using SLC_deramp, that is only meant for strip
map data.
For Sentinel-1 data you need to use the scripts

ScanSAR_deramp.py and ScanSAR_deramp_2nd.py

Also, for Scansar data, there is very little if any benefit to azimuth
oversampling, and it complicates the processing significantly.
Se the az_ovr factor to 1 when using SLC_ovr.

Best regards,

Charles

On 14.01.2026 19:31, Igor Babayants wrote:

GAMMA Questions - Sentinel-1: Horisontal "stripes" on amplitude part of data
after coregister <https://dep1doc.gfz.de/boards/32/topics/683>

/Igor Babayants/

Hi everyone!
Try to process some S1C data (15 files). Need to calculate IPTA for possible
horizontal subsidences.
1) extract iw3, 2 bursts, OPOD data +- 1 day from sensing data.
2) geocode (no visible problems).
3) coregister, deramp, oversampling in range and azimuth (factor 2).

But after vizualise coregister images, some images have noticeable horizontal
stripes. Deramping does not affect the result.
Is it a problem for further calculations? How I can check result and find a
mistake?

Thanks for help.

Some commands:

1. Extract
run_all.pl dates 'S1_import_SLC_from_zipfiles $1.ziplist
$1.ziplist.burst_number_table vv 0 3 'OPOD' >> log2.txt'
run_all.pl dates 'SLC_mosaic_ScanSAR $1.vv.SLC_tab $1.slc $1.slc.par 10 2

log.txt'

run_all.pl dates 'multi_look $1.slc $1.slc.par $1.mli $1.mli.par 10 2'
run_all.pl dates 'raspwr $1.mli 2391 1 0 1 1'

1. Geocode
gc_map2 20250805c.mli.par ../DEM/perm.dem_par ../DEM/perm.dem
20250805.dem_par 20250805.dem 20250805.lt 1 1 20250805.ls_map -
20250805.inc >> log.txt
pixel_area 20250805c.mli.par 20250805.dem_par 20250805.dem 20250805.lt
20250805.ls_map 20250805.inc 20250805.sigma0 20250805.gamma0 >> log.txt
create_diff_par 20250805c.mli.par - 20250805.diff_par 1 0 >> log.txt
offset_pwrm 20250805.gamma0 20250805c.mli 20250805.diff_par 20250805.offs
20250805.snr 128 128 - 1 32 32 0.15 >> log.txt
offset_fitm 20250805.offs 20250805.snr 20250805.diff_par 20250805.coffs -
0.15 1 >> log.txt
gc_map_fine 20250805.lt 2391 20250805.diff_par 20250805.lt_fine 1 >> log.txt
pixel_area ../input/20250805c.mli.par 20250805.dem_par 20250805.dem
20250805.lt_fine 20250805.ls_map 20250805.inc 20250805.sigma0
20250805.gamma0 >> log.txt
geocode 20250805.lt_fine 20250805.dem 2391 20250805.hgt 1000 1000 2 0
rasdt_pwr 20250805.hgt ../input/20250805c.mli 1000 1 0 1 1 0 500 0
terrain.cm 20250805.hgt.bmp 1 0.35 8

1. Coregister
run_all.pl dates1 'SLC_coreg.py ../input/$1c.slc ../input/$1c.slc.par
$1c.s1.rslc $1c.s1.rslc.par $1.rmli $1.rmli.par 20250805c.rslc
20250805c.rslc.par ../DEM_pre/20250805.hgt 10 2'

1. Deramp
run_all.pl dates 'SLC_deramp $1c.s1.rslc $1c.s1.rslc.par $1c.s1.der.rslc
$1c.s1.der.rslc.par 0'

1. Oversampling
run_all.pl dates 'SLC_ovr $1c.s1.rslc $1c.s1.rslc.par $1.rslc.ovr
$1.rslc.ovr.par 2.0 2.0 1 9'

1. Raster for create Average image
run_all.pl dates 'multi_look ../rslc/$1.rslc.ovr ../rslc/$1.rslc.ovr.par
$1.rmli $1.rmli.par 20 4'
run_all.pl dates 'raspwr $1.rmli 1000'

Files 20250606.rmli.jpg
<https://dep1doc.gfz.de/attachments/download/1013/20250606.rmli.jpg> (932 KB)
20250606c.mli.jpg
<https://dep1doc.gfz.de/attachments/download/1014/20250606c.mli.jpg> (958 KB)
20250805.hgt.jpg
<https://dep1doc.gfz.de/attachments/download/1015/20250805.hgt.jpg> (1.13 MB)

---

You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
https://dep1doc.gfz.de <https://dep1doc.gfz.de>

This is a multi-part message in MIME format.
--------------5G2wtWTgjxUvvFjfj0Ondc21
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello Igor,

One more thing"

To coregister Sentinel-1 data use the
script ScanSAR_coreg.py or ScanSAR_coreg_stack.py and NOT SLC_coreg.py

Best regards,

Charles

On 14.01.2026 19:31, Igor Babayants wrote:

GAMMA Questions - Sentinel-1: Horisontal "stripes" on amplitude part of data
after coregister <https://dep1doc.gfz.de/boards/32/topics/683>

/Igor Babayants/

Hi everyone!
Try to process some S1C data (15 files). Need to calculate IPTA for possible
horizontal subsidences.
1) extract iw3, 2 bursts, OPOD data +- 1 day from sensing data.
2) geocode (no visible problems).
3) coregister, deramp, oversampling in range and azimuth (factor 2).

But after vizualise coregister images, some images have noticeable horizontal
stripes. Deramping does not affect the result.
Is it a problem for further calculations? How I can check result and find a
mistake?

Thanks for help.

Some commands:

1. Extract
run_all.pl dates 'S1_import_SLC_from_zipfiles $1.ziplist
$1.ziplist.burst_number_table vv 0 3 'OPOD' >> log2.txt'
run_all.pl dates 'SLC_mosaic_ScanSAR $1.vv.SLC_tab $1.slc $1.slc.par 10 2

log.txt'

run_all.pl dates 'multi_look $1.slc $1.slc.par $1.mli $1.mli.par 10 2'
run_all.pl dates 'raspwr $1.mli 2391 1 0 1 1'

1. Geocode
gc_map2 20250805c.mli.par ../DEM/perm.dem_par ../DEM/perm.dem
20250805.dem_par 20250805.dem 20250805.lt 1 1 20250805.ls_map -
20250805.inc >> log.txt
pixel_area 20250805c.mli.par 20250805.dem_par 20250805.dem 20250805.lt
20250805.ls_map 20250805.inc 20250805.sigma0 20250805.gamma0 >> log.txt
create_diff_par 20250805c.mli.par - 20250805.diff_par 1 0 >> log.txt
offset_pwrm 20250805.gamma0 20250805c.mli 20250805.diff_par 20250805.offs
20250805.snr 128 128 - 1 32 32 0.15 >> log.txt
offset_fitm 20250805.offs 20250805.snr 20250805.diff_par 20250805.coffs -
0.15 1 >> log.txt
gc_map_fine 20250805.lt 2391 20250805.diff_par 20250805.lt_fine 1 >> log.txt
pixel_area ../input/20250805c.mli.par 20250805.dem_par 20250805.dem
20250805.lt_fine 20250805.ls_map 20250805.inc 20250805.sigma0
20250805.gamma0 >> log.txt
geocode 20250805.lt_fine 20250805.dem 2391 20250805.hgt 1000 1000 2 0
rasdt_pwr 20250805.hgt ../input/20250805c.mli 1000 1 0 1 1 0 500 0
terrain.cm 20250805.hgt.bmp 1 0.35 8

1. Coregister
run_all.pl dates1 'SLC_coreg.py ../input/$1c.slc ../input/$1c.slc.par
$1c.s1.rslc $1c.s1.rslc.par $1.rmli $1.rmli.par 20250805c.rslc
20250805c.rslc.par ../DEM_pre/20250805.hgt 10 2'

1. Deramp
run_all.pl dates 'SLC_deramp $1c.s1.rslc $1c.s1.rslc.par $1c.s1.der.rslc
$1c.s1.der.rslc.par 0'

1. Oversampling
run_all.pl dates 'SLC_ovr $1c.s1.rslc $1c.s1.rslc.par $1.rslc.ovr
$1.rslc.ovr.par 2.0 2.0 1 9'

1. Raster for create Average image
run_all.pl dates 'multi_look ../rslc/$1.rslc.ovr ../rslc/$1.rslc.ovr.par
$1.rmli $1.rmli.par 20 4'
run_all.pl dates 'raspwr $1.rmli 1000'

Files 20250606.rmli.jpg
<https://dep1doc.gfz.de/attachments/download/1013/20250606.rmli.jpg> (932 KB)
20250606c.mli.jpg
<https://dep1doc.gfz.de/attachments/download/1014/20250606c.mli.jpg> (958 KB)
20250805.hgt.jpg
<https://dep1doc.gfz.de/attachments/download/1015/20250805.hgt.jpg> (1.13 MB)

---

You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
https://dep1doc.gfz.de <https://dep1doc.gfz.de>

Hello, Charles!

Yes, I completely modify processing, it's ok!
I use ScanSAR_coreg.py (based on rslc_tab) for coregister, then deramp data (S1_deramp_TOPS_slave) and oversampling only in range direction.
I calculate pair interferogram, and see, that 48 and 60 days between passes gives an acceptable result.
For IPTA methods, how I can define delta_T_max for processing (S1C sensor, sensing period 12 days)?

Thanks for your help!

This is a multi-part message in MIME format.
--------------6Nx2KQzWOyJL4zg0fq7sZIjy
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello,
I assume you are referring to the script base_calc:

• /Users/cw/gamma_software/DIFF/scripts/base_calc
• Copyright 2025, Gamma Remote Sensing, v4.9 24-Dec-2025 clw/uw/cm ***
• Generate baseline plot and output file with perpendicular baselines and
  delta_T values ***
• Generate interferogram table (itab) file specifying SLCs for each
  interferogram ***

usage: /Users/cw/gamma_software/DIFF/scripts/base_calc <SLC_tab> <SLC_par>
<bperp_file> <itab> <itab_type> [plt_flg] [bperp_min] [bperp_max] [delta_T_min]
[delta_T_max] [delta_n_max] [date_format] [log]

    SLC_tab      (input) two column list of SLC filenames and SLC parameter
filenames (including paths) (text)
                   1. SLC filename  (includes path)
                   2. SLC parameter filename (includes path)
    SLC_par      (input) reference SLC parameter filename (includes path)
    bperp_file   (output) list of dates, bperp and delta_T for interferogram
pairs in the itab (text)
    itab         (output) interferogram table with 4 column format:
                   1. row number in SLC_tab of the reference SLC
                   2. row number in SLC_tab of SLC2 of the interferogram
                   3. line number in the itab
                   4. flag used to indicate if this interferogram is used in
IPTA processing (0: not used, 1: used)
    itab_type    itab type (enter - for default):
                   0: single reference pairs with constraints (default)
                   1: all possible pairs with constraints
                   2: all possible pairs with constraints + all
single-reference pairs
    plt_flg      bperp plotting flag (enter - for default)
                   0: none (default)
                   1: output plot in PNG format
                   2: screen output
    bperp_min    minimum magnitude of bperp (m) (enter - for none)
    bperp_max    maximum magnitude of bperp (m) (enter - for none)
    delta_T_min  minimum number of days between passes (enter - for none)
    delta_T_max  maximum number of days between passes (enter - for none)
    delta_n_max  maximum scene number difference between passes (enter - for none)
    date_format  date format in bperp_file (enter - for default)
                   0: legacy format YYYYMMDD
                   1: ISO 8601 format YYYYMMDDTHHMMSS (default)
    log          (output) log file name (enter - for none)

often I have mount it more useful to use the delta_n_max that defines the
network in terms of the number of connections rather than
the time interval. Though you can also use delta_T_min (set to a number > 0 to
ensure you do not include auto-interferograms, and then delta_T_max
to define the maximum time interval for an interferogram. If some of the
interferograms are unusable (e.g. very low correlation or extreme atmosphere)
then you can edit the itab in a text editor. Sometimes I define limits and add
additional interferograms to the list to increase the
the number of corrections and redundancy in the network. Redundancy helps
greatly with correction of phase unwrapping errors and reduction
of errors from noise and phase closure phase differences.  The solution of mb
aims to reduce phase closure error and other errors through
redundancy in the least-squares solution.

Best regards,
Charles

On 21.01.2026 12:01, Igor Babayants wrote:

GAMMA Questions - Sentinel-1: RE: Horisontal "stripes" on amplitude part of
data after coregister
<https://dep1doc.gfz.de/boards/32/topics/683?r=686#message-686>

/Igor Babayants/

Hello, Charles!

Yes, I completely modify processing, it's ok!
I use ScanSAR_coreg.py (based on rslc_tab) for coregister, then deramp data
(S1_deramp_TOPS_slave) and oversampling only in range direction.
I calculate pair interferogram, and see, that 48 and 60 days between passes
gives an acceptable result.
For IPTA methods, how I can define delta_T_max for processing (S1C sensor,
sensing period 12 days)?

Thanks for your help!

Files 0805_1004.diff.filt.unw.jpg
<https://dep1doc.gfz.de/attachments/download/1019/0805_1004.diff.filt.unw.jpg>
(2.14 MB)

---

You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
https://dep1doc.gfz.de <https://dep1doc.gfz.de>