ProcessingChains/Sar_MultiSlc_Chain.md

@@ -2,14 +2,15 @@
 
 # SAR_MultiSlc.py
 
-This workflow works on S1 StripMap and Cosmo data.
-
 ## Description
 
-This file is an interferometry chain between multitemporal SAR images. 
-One master image is fixed by users and other images are processed as slave image.
+This workflow works on S1 StripMap and Cosmo data. It spreads the main processing with multitemporal SAR images. 
+One reference image is fixed by users and other images are processed as secondary image. This chain deals with DEM differently by creating the corresponding DEM from a folder filled with SRTM files and a shapefile. 
+
+![image](../Art/chains_description/diapOTB_SARMultiSlc.png)
+
 
-For each couple (master/slave), the processing is divided into four parts descrided below :
+For each couple (reference/secondary), the processing is divided into four parts descrided below :
 
 * Pre-Processing Chain
 
@@ -39,7 +40,7 @@ Five sections compose the configuration file :
     * **SRTM_Shapefile :** Path to the SRTM shapefile
 
 
-    * **SRTM_Path :** Path to the SRTM Datalake folder
+    * **SRTM_Path :** Path to the SRTM folder
 
 
     * **Geoid :** Path to Geoid file
@@ -148,3 +149,7 @@ Five sections compose the configuration file :
 	
 	
 	* **Filtered_parameter_alpha :** alpha parameter for Goldstein filtering
+	
+	
+
+The processing chain needs metadata to launch the applications. Thus, input images must be into the native directory for each kind of products (i.e SAFE directory for Sentinel-1 products).