Best viewed with Firefox

ROI_PAC processing for Modern Geodetic Methods (Page 4 of 6)

Getting Data Table of Contents Figures

Preparing RAW data for ROI_PAC:

  • If you download a .zip file that contains a .DAT file and no .raw file, you will need to run the following script to make the raw format.
    Note that depending on the satellite data you are using, a different program is needed to make the raw files. However, after this point all files should work similarly with the rest of the programs (but you still cannot combine data from satellites with different frequency-bands or orbits).

  • To convert a DAT file into a RAW file for ROI_PAC processing we need to run the following in each of the directories that contain radar image files.
    1. Unzip the files:
           % cd ~/MGM/HectorMine/990915  # get into image directory
           % unzip ERS2_127_2907_23027.zip 
      Repeat for other directory.

    2. Rename a couple of files (I use links) to the YYMMDD format that you are using for your current directory.
           % ln -s LEA_01.001 990915.ldr
           % ln -s DAT_01.001 IMAGERY.dat
      Repeat for other directory.

    3. Run make_raw.pl on the data. Typing the command with no arguments gives the basic usage.
       make_raw.pl 'ORBIT' 'YYMMDD'.ldr 'YYMMDD'  # this can take a couple of minutes 
               ORBIT  = ODR  Delft Orbit Determination for ERS satellites
               YYMMDD = date of the image 
           % make_raw.pl ODR 990915.ldr 990915
      Repeat for other directory.

    4. Check the file 990915.raw.rsc to see if DOPPLER_RANGE0 is between +-0.5. If it is not, add or subtract 1 to it and replace the field. Sometimes the doppler ambiguity is not correctly calculated, particularly for later ERS2 data (after the gyroscopes died), thus it needs to be updated manually.

Prepare Running Directory

In order to allow us all to process with efficiency, we will run the actual InSAR processing on tohoku.

On Tohoku: (be sure to switch to group MGM)
  • In the HectorMine directory, create process file (990915_991020.proc) that the program process_2pass.pl reads. The contents of the file are as listed below.
    SarDir1=990915                
    SarDir2=991020
    IntDir=int_990915_991020
    DEM=/home/anewman/MGM/HectorMine/DEM/HM.dem
    flattening=topo 
    OrbitType=ODR  
    
    
    # location of SAR data
    
    # directory to create interferograms in
    # location of your DEM 
    # remove topographic fringes
    # Use Delft satellite orbit determinations 
    

Process data to create interferograms

    Here we will run the perl script 'process_2pass.pl' to do the complete processing from start to finish. While, for some datasets (including the class example) it is possible to run from start to end with no problems, this is not always the case. Thus, below are examples of processing either in its entirety or piece-wise. You can always look at the perl script to see precisely what it is doing.

  • Perform processing from start to finish (good luck!)
     % time process_2pass.pl 990915_991020.proc &> 990915_991020.log& # this will take about 30 minutes 
     % tail -f 990915_991020.log # to watch the progress

    You may see several "** ERROR **" and warning messages scroll across the log file. Unless the program unexpectedly stops, or the resulting image outputs do not look right, it has been our experience that many of these can be 'safely' ignored.

    If your processing stops at a point where it gives the message "That's all folks.", you were likely successful!

    :Or

  • Run piece-wise
    By including additional variables after the .proc file, you can start and stop the processing at numerous places. Even if you have started from the fully automatic processing, it is possible to restart the processing from an intermediate point if it had unexpectedly crashed.

    Note: If you misspell a start/stop point the program may sit there perfectly happy doing nothing. Thus, it is a good idea to check that you are getting output either to screen or a log file. Some steps, however, may still go 15 or more minutes without any screen output, so you may also want to check what your processes is doing through a program like 'top'. More information about processing in stages can be found here.

    Options for DoItFrom and EndItAt are:
    1. raw
    2. roi_prep
    3. orbbase
    4. slcs
    5. offsets
    6. resamp
    7. flatorb
    8. full_res
    1. seismic
    2. begin_filt
    3. filtered
    4. make_mask
    5. unwrapped
    6. done_sim_off
    7. done_sim_removal
    8. redo_base
    1. use_sim_base
    2. synth_offset
    3. sim_removal
    4. sim_removal_bsim
    5. unwrapped_bsim
    6. done

    Example shown without sending to a log file:
    1. Go from raw data to make single look complexes:
       % process_2pass.pl 990915_991020.proc raw slcs # this will take a few seconds to minutes  
    2. Make flattened inteferogram (remove simulated topographic effects from image):
       % process_2pass.pl 990915_991020.proc slcs flatorb  &> 990915_991020.log&  # takes ~10 minutes
       % tail -f 990915_991020.log # to watch the progress
    3. Unwrap inteferogram to get LOS displacements:
       % process_2pass.pl 990915_991020.proc flatorb unwrapped          # takes ~15 minutes
    4. Geocode the unwrapped interferogram to get LOS displacements relative to geographic coordinates (instead of satellite coords):
       % process_2pass.pl 990915_991020.proc unwrapped done             # takes ~5 minutes

Getting Data Figures

Course Home | anewmangatech.edu | Updated: Thu Apr 5 11:00:50 EDT 2012