##############################################################################
# $Id $
# $Name $
# $Revision $
# $Log $
##############################################################################
+-----------------------------------------------------------------------------+
|                                                                             |
|                   UVES Pipeline Installation Disclaimer                     |
|                           Andrea Modigliani (ESO-DMD)                       |
|                               amodigli@eso.org                              |
|                                                                             |
+-----------------------------------------------------------------06/09/2001--+

The UVES pipeline is a project under continuous development. Here we would like
to list all the known problems and limitations.

Problems:
========

o Known eventual installation problems:

- To allow proper installation of the pipeline:
  
  1- Check that you have a MIDAS release 01SEPpl1.3 or higher

  2- Check that the 01SEPpl1.3/local/default.mk defines
     MIDASHOME as the directory where 01SEPpl1.3 is located.


- Check that the binary ar (to create, modify, and extract from archives) is included
  in your local path (on Solaris this should be under /usr/ccs/bin)
  


Limitations:
============
o Physical Model  (command PREDICT/UVES): In case of macro Earthquake events the instrument
  may have significant shifts which induce spectral format shift which may be not tolerated
  by the physical model. This is reflected from a characteristic final plots which in the XDIF vs X
  and YDIF vs Y plots loose the characteristic aggregation to show instead random points.
  In this case it is necessary to apply offset on the relevant parameters,
  as described in the high level documentation. 
  
  In case of observation taken in not standard configuration, with X shift greater than 5 pixels
  the physical model can still be failing. Again in this case one should apply appropriate
  offset to the parameters, in particular, in this case appropriately set the 
 X component of the XYtrans
  parameter (P4).
  
  In case of aborted calibration exposure, which can be noticed by the characteristic
  look-up of the frame without the trace of the orders, this step may file as obviously
  no line is identified if no order trace is present.
  
  
o The order position data reduction step may fail if it is not found an appropriate
  DRS setup table. This may be typical at run time of the pipeline in online mode
  using as reference solutions the ones stored in a calibDB due to the fact that
  the calibDB contains DRS setup tables covering only the standard settings.  
  In this case one should generate a complete set of calibration solution from
  an  complete set of raw calibration frames all taken with the same
  instrument setting and (having the ThAr line table, for example 
  thargood_2.tfits) 
  use the script uves_popul.sh to build a complete set of reference solutions
  in which will be comprised also the proper DRS setup table.
  

o The wavelength calibration step may fail in case of aborted observation and so
  no signal present on the frame. This is usually sign of an aborted calibration
  exposure.
  
o The master flat field creation step may fail in automatic pipeline processing
  (online) if the Reduction Block  contains in the input raw frame part two files
  with incoherent DO_CLASSIFICATION, like FLAT_RED and FLAT_BLUE, ARC_LAMP_BLUE
  and FLAT_BLUE, ARC_LAMP_BLUE and FLAT_RED etc.. This problem is usually due to
  a wrong creation of the RB from the Data Organizer which can verify in case
  an observation is aborted.
  
o The standard star data reduction to get the instrument efficiency (recipe uves_cal_response)
  may fail in case the observed standard star is not contained in the reference list table
  of standard stars for which known is their flux. In this case obviously being missing
  important information the recipe is going to fail.
      
  
  
o Optimal extraction (command REDUCE/UVES): Despite from version 1.0.6 a significant
  improvement of extraction quality occurred, extraction quality is still limited,
  in particular in case of high S/N data (S/N ratio grater than 50).
  We also suggest to always check extraction quality using the dedicated commands
  MPLOT/CHUN and PLOT/CHUN checking in particular how well the fit corresponding to 
  the blue trace matches the dark (raw data) and magenta (after k-sigma clipping) 
  points.


  In the optimal extraction the maximum allowed input raw file name is 54 chars (which
  anyway should be enough!). This due to the use some buffer with size limited to
  96 chars to display informations on the data reduction.
  It is anyway a good idea to not use too long filenames.

o Background extraction (occurring during master flat preparation, science extraction,
  efficiency determination) should be checked using the dedicated command MPLOT/BKGR.

  


  
 
