f09213eb33
* add Dockerfile and SConfigISCE to build cuda-enabled modules
* add Dockerfile and SConfigISCE to build cuda-enabled modules
* set correct name
* update for centos7 and cuda-dev image
* restore
* disable GPUampcor
* update
* save
* sync up Dockerfile updates
* fix base image
* change docker image names
* create gpu vs. cpu specific tags
* update with nodata WBD Stitcher
* fix segmentation fault when running sciflo workflows
- remove dependencies that downgrade the `geos` conda package
* sync fix for segmentation fault to cuda builds
* ping ffi to version 1.12.2
Latest version of ffi, 1.13.0, breaks installation of fpm:
```
$ sudo gem install --no-ri --no-rdoc fpm
Fetching: cabin-0.9.0.gem (100%)
Successfully installed cabin-0.9.0
Fetching: backports-3.17.2.gem (100%)
Successfully installed backports-3.17.2
Fetching: arr-pm-0.0.10.gem (100%)
Successfully installed arr-pm-0.0.10
Fetching: clamp-1.0.1.gem (100%)
Successfully installed clamp-1.0.1
Fetching: ffi-1.13.0.gem (100%)
ERROR: Error installing fpm:
ffi requires Ruby version >= 2.3.
```
TODO: remove pin when ffi's backwards compatiblity is restored.
* comment out unused import
* add build circleci job to PR tests
* pin ffi in cuda build
* revert logging hackery
* fix "target_include_directories called with non-compilable target type" errors
* Keep source directory for topsStack
Co-authored-by: dustinlo <dustin.k.lo@jpl.nasa.gov>
Co-authored-by: shitong01 <stchin@ntu.edu.sg>
Co-authored-by: Ryan Burns <47790121+rtburns-jpl@users.noreply.github.com>
|
||
|---|---|---|
| .. | ||
| stripmapStack | ||
| topsStack | ||
| README.md | ||
README.md
Stack Processors
Read the document for each stack processor for details.
Installation
To use the TOPS or Stripmap stack processors you need to:
-
Install ISCE as usual
-
Depending on which stack processor you need to try, add the path of the folder containing the python scripts to your
$PATHenvironment variable as follows:- add the full path of your contrib/stack/topsStack to
$PATHto use the topsStack for processing a stack of Sentinel-1 TOPS data - add the full path of your contrib/stack/stripmapStack to
$PATHto use the stripmapStack for processing a stack of StripMap data
- add the full path of your contrib/stack/topsStack to
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:
- H. Fattahi, P. Agram, and M. Simons, “A network-based enhanced spectral diversity approach for TOPS time-series analysis,” IEEE Trans. Geosci. Remote Sens., vol. 55, no. 2, pp. 777–786, Feb. 2017. (https://ieeexplore.ieee.org/abstract/document/7637021/)