ISCE_INSAR/contrib/stack
CunrenLiang 1eaa62a459
ionospheric phase estimation module for topsStack (#326)
* ionosphere correction for topsStack

* Update README.md

* Update Alos2ProcPublic.py

* Update Stack.py

Currently the script writes the `invertIon.py` command pointing to 'ion' and writing to 'ion_dates'. However we need the absolute paths in order to find the 'ion' directory from within the run_files directory (similar to how the `computeIon.py` function is written at l.1488)

* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

* Add files via upload

Co-authored-by: Oliver Stephenson <ollie.stephenson@outlook.com>
2022-02-14 11:13:23 -08:00
..
alosStack Replaced logger.warn to logger.warning, changed *.hgt* to *.hgt and updated RelaxIV download link (#332) 2021-09-09 11:05:12 -07:00
stripmapStack UAVSAR_Stack: bugfix for line/sample num and dopplerFile path (#431) 2022-02-01 13:50:40 -08:00
topsStack ionospheric phase estimation module for topsStack (#326) 2022-02-14 11:13:23 -08:00
README.md new alosStack application 2020-11-07 16:06:02 -08:00

README.md

Stack Processors

Read the document for each stack processor for details.

Installation

To use a stack processor you need to:

  1. Install ISCE as usual

  2. Depending on which stack processor you need to try, add the path of the folder containing the python scripts to your $PATH environment variable as follows:

    • add the full path of your contrib/stack/topsStack to $PATH to use the topsStack for processing a stack of Sentinel-1 TOPS data
    • add the full path of your contrib/stack/stripmapStack to $PATH to use the stripmapStack for processing a stack of StripMap data
    • set environment variable $PATH_ALOSSTACK by doing: export PATH_ALOSSTACK=CODE_DIR/contrib/stack/alosStack to use the alosStack for processing a stack of ALOS-2 data

Note: The stack processors do not show up in the install directory of your isce software. They can be found in the isce source directory.

Important Note:

There might be conflicts between topsStack and stripmapStack scripts (due to comman names of different scripts). Therefore users MUST only have the path of one stack processor in their $PATH environment at a time, to avoid conflicts between the two stack processors.

References

Users who use the stack processors may refer to the following literatures:

For StripMap stack processor and ionospheric phase estimation:

  • H. Fattahi, M. Simons, and P. Agram, "InSAR Time-Series Estimation of the Ionospheric Phase Delay: An Extension of the Split Range-Spectrum Technique", IEEE Trans. Geosci. Remote Sens., vol. 55, no. 10, 5984-5996, 2017. (https://ieeexplore.ieee.org/abstract/document/7987747/)

For TOPS stack processing: