##############################################################################
# $Id: ReadMe,v 1.11 2001/09/10 15:19:51 amodigli Exp $
# $Name:  $
# $Revision: 1.11 $
# $Log: ReadMe,v $
# Revision 1.11  2001/09/10 15:19:51  amodigli
# Updated for CDROM release 1.2.0
#
# Revision 1.10  2001/03/10 08:18:24  amodigli
# Simplified
#
# Revision 1.9  2001/03/05 15:28:08  amodigli
# Included reference to ipip
#
# Revision 1.8  2001/02/19 09:25:39  amodigli
# Updated to reflect new pipeline directory
# structure and installation procedure
#
# Revision 1.7  2001/01/04 13:07:20  amodigli
# Added Id, Name, Revision, Log conf. control info
#
##############################################################################
+-----------------------------------------------------------------------------+
|                                                                             |
|                   UVES Pipeline Installation Instruction                    |
|                           Andrea Modigliani (ESO-DMD)                       |
|                               amodigli@eso.org                              |
|                                                                             |
+-----------------------------------------------------------------09/03/2001--+

(0) Be sure to have defined and existing two basic environment variables:
    MIDASHOME and MIDVERS, for example:
    
    
        setenv MIDASHOME /midas
        setenv MIDVERS 01SEPpl1.3

(1) System installation usually takes place at (Paranal):
    In this case the Paranal user is supposed to use the DFS delivery script
     "ipip". For more information consult the following URL:
     http://www.eso.org/projects/dfs/dfs-shared/web/seg/seg-ipip.html
     
    In this case an instrument pipeline delivery will consist of two tarfiles:
     o <instrument>-<rel>.tar.gz
     o <instrument>-<calibdb-<rel>.tar.gz
    were <instrument> in our case will be uves and rel is the release number,
    for example 1.2.0
      
    ipip will be called as:
     
           ipip <instrument>-<rel>.tar.gz [ offline ]
     
    were the optional keyword offline will be used to flag a pipeline delivery
    to be used by the Quality Group at ESO Garching HQ.

    The script will install the pipeline in the directory:
    
		$MIDASHOME/$MIDVERS/pipeline
    
    were it will appear  a directory

        <instrument>-<rel>
        and a link to it:
        <instrument>   -> <instrument>-<rel>
        
   Below <instrument>-<rel> will be present the directories context/ exec/ proc/
   and a few other files: this ReadMe file with installation notes, 
   the ReleaseNotes file, the setup installation script, and in case of 
   uves also the complete pipeline tree under uves/.
   
(2) For normal user we have a simplified installation procedure:

        mkdir $PIPE_HOME
        cd $PIPE_HOME
        gunzip uves-<rel>.tar.gz
        tar xvf uves-<rel>.tar
        cd uves-<rel>
        ./setup user
		
    The installation is terminated. In this case under $PIPE_HOME will 
    be created a link
        uves -> uves-<rel>
        
(3) The installation can occur also somewere else and the user could 
    specify the deployment directory. Lets suppose that it is $PIPE_HOME.
    It must exist:
   
     mkdir $PIPE_HOME

    Under such directory you need to have the subdirectory <instrument>-<rel>.
    
     mkdir -p $PIPE_HOME/uves-<rel>
    
    Copy your archive file (assume uves-<rel>.tar.gz) to a temporary
    directory (suppose for example named tmp_dir)
        cd tmp_dir
        gunzip uves-<rel>.tar.gz
        tar xvf uves-<rel>.tar
		cd uves-<rel>
		./setup $PIPE_HOME/uves-<rel>
		cd $PIPE_HOME
		ln -s uves-<rel> uves
		
    your installation is finished now. you can also remove tmp_dir
  

(4) To upgrade the pipeline in case of having changed just a few modules
    under $PIPE_HOME/uves/uves/ tree
    cd $PIPE_HOME/uves
    make update

