WInSAR will be distributing the InSAR SCE (InSAR Scientific Computing Environment) software for SAR processing from this page. In order to download the software, institutional representatives of WInSAR Member institutions must sign and return this license agreement. Please print out and sign the cover sheet, and then either scan and email to email@example.com or fax to 303-381-7501. Once the agreement is received, users from your institution will have access to the software with their normal WInSAR archive credentials.
|2014 Jul 30||isce-2.0.0.bz2||This release, isce-2.0.0, is the first Python3 version of ISCE.
Users should switch to the version. We plan to release a final Python2 version soon that will
include much, but not all, of the functionality of this version, but future developments and bug
fixes will be to the Python3 version. We plan more frequent formal releases in the future and
will also release monthly snapshots of the development version of the code.
The README.txt file and the example input files in the examples/input_files directory are the most up to date sources of information on installing and running ISCE. The ISCE.pdf file is useful but may be dated in parts. It will be updated in an upcoming release.
If you want to use ISCE to process RadarSAT1 data, then you will need to download files to the components/isceobj/Orbit/db directory. Instructions on where to get the files are given in the file kernels.list file in that directory.
|2013 Oct 28||isce.1.5.01.tgz||Minor bug-fix release: fixes a memory leak in ampcor|
|2013 Oct 22||isce.1.5.0.tgz||Many new products created, new configurable parameters exposed, and greater flexibility in the format of the input files|
|2012 Aug 14||iscepack_svn_r_739.bz2|
|2012 July 12||iscepack_svn_r_727.bz2||Pre-release version|
|April 2016||isce-2.0.0_201604||RELEASE NOTES|
|December 2015||isce-2.0.0_201512.bz2||Included in this release are a number of bug fixes and a few new features:
|November 2015||isce-2.0.0_201511.bz2||Included in this release are a number of bug fixes and a few new features:
|June 2015||isce-2.0.0_201506.bz2||Several bug fixes. Sensor objects - ALOS–2, UAVSAR stacks. Added support for ERS and ALOS-1 SLCs. isce2geotiff.py utility to generate geotiffs from ISCE products. New modules for dem assisted coregistration in zero and native doppler geometries.|
|May 2015||isce-2.0.0_201505.bz2||Many general improvements and bug fixes. Application isceApp.py functional for UAVSAR stack post-processing and for polarimetric data in general; see examples/input_files for example input files.|
|October 2014||isce-2.0.0_201410.bz2||General improvements and bug fixes. Automatic DEM download now uses SRTM3. Added improved DEM interpolation default/options. Preliminary additions for UAVSAR stack post-processing---not yet fully functional: coming soon in the next monthly snapshot.|
|September 2014||isce-2.0.0_201409.bz2||This version has a number of bug fixes and adds new sensor handling for: ALOS2, RISAT1 (experimental), UAVSAR_RPI (experimental).|
You can now download the testing data set which includes Envisat, ALOS and ERS data with some documentation. Use your normal WInSAR archive username and password.
We are presently distributing the MDX plotting package from JPL under the ISCE software license agreement described above. For more information on MDX, please see the ROI_pac Wiki. Support images and tables used by MDX are provided in the MDX Data tar file.
To build mdx, you will need both a C and FORTRAN compiler. You will also need a version of the Motif library. All three should be available online. Included in the tar file is a sample Makefile that is used to build the code on an Intel Macintosh running OS X10.6. You will probably need to modify the Makefile to work on your system. There are also a couple sample images you can display to test if the code is working. Running the code without any command line parameters will generate a list of the most common options.
©2001. California Institute of Technology. ALL RIGHTS RESERVED. U.S. Government sponsorship acknowledged. Any commercial use must be negotiated with the Office of Technology Transfer at the California Institute of Technology. The technical data in this document is controlled under the U.S. Export Regulations, release to foreign persons may require an export authorization.
Last modified Tuesday, 26-Apr-2016 17:52:10 UTC
Sponsors of WInSAR activities: