($ Version 0.09 December 29th, 2009 Author : Jitendra Kodilkar$ )

   Detail information about the package and SOP to use it, is as follows :

   (i) Introduction : The GDP (GTAC data diagnostic package) is a set of  diagnostic programs to 
      check the basic health of regular GMRT data. It works on any LTA/B file (right now, only for Indian polar
       mode), taken during a regular GTAC observation.  The package takes a gtaclog  number/ltafile-name, and
       finds out status on flux calibrators (3C)  by using the 'mkmatmon' program.  After knowing the bad/non- 
       working  antennas from this, and the names of the phase-calibrators, it runs 'rantsol' to detect delay jumps\
       and bad-baselines by using the scripts  '' and '', respectively.  At the end it
        generates  a summary of the analysis, giving the problems encountered.

        In side the gdp package, three mains scripts are being run :
        (a) matxmon (Author : Santaji Katore)
            This shows fringe amplitude counts on flux calibrator (3C147|3C286|3C48) for all baselines in a matrix
             format, upper triangle shows LL (175 MHz) polarization and lower triangle shows RR (130 MHz)
        (b) Delay Jump (Author : Sandeep Sirothia)  
            '' script run rantsol and shows delay jump output in pdf format for each antenna with two
             polarization information (RR and LL).

        (c) Bad base-lines (Author : Jitendra/Ishwar)
            '' script run rantsol on flux-calibrator data, check the residual  amplitude gain for baselines.
            The baselines are declared as a bad if residual amplitude gain (ratio of true visibility/model visibility) for
             given baseline is either less than 0.3 or greater than 2.

   (ii) Standard Operating Procedure

       login : gtaclog,  Path : /home/gtaclog/ANALYSIS/gdp
       Usage : ./gdp [ -o <GTACLOG number> | -f <file-name> ]
             Other available options are :
          -r <Reference Antenna >
          -s <Scan No for MATMON and Badbaselines>
          -c <chan No>
          -i <Integration for phase plots>
          -g <Threshold Gain value for Bad-Baselines>

    > gdp -o <3508>
       # This will generate matrix-montor like display using flux 
       # calibrator data. It will then query for bad antenna names.
     Give Bad antennas names in capital letters XXX [] : E03,W04

       # Then it will display the lta header and ask for the names of the  calibrators.
     Specify calibrators list [3C147|3C48|3C286]: 3C|1120

       # User will get a phase vs time display for the specified calibrators, which can be used to infer the presence
       #  of phase / delay jumps. If the phase for both channels is jumping or changing, then it is   a constant step /
       # jump. Then user can write a comment for delay jumps. 
         Enter comment about delay jumps [] : No delay jumps

       # Then it checks for bad baselines using script. finding bad baselines....
     Update Summary log [y/n]? y     # Final query about updating gtac summary log.

     Output :
     (i) For example, 'gdp -o 3508' should create following resultant directories 
          and log files:
         /home/gtaclog/ANALYSIS/3508  # Directory
         /home/gtaclog/ANALYSIS/3508/3508.obslog  # Gtac observing log
         /home/gtaclog/ANALYSIS/3508/13efa01_22dec2007.lta.MTX # Gtac observing log
         /home/gtaclog/ANALYSIS/3508/13efa01_22dec2007.lta.PS  # phase plots on 
          calibrators for delay jumps.
         /home/gtaclog/ANALYSIS/3508/13efa01_22dec2007.lta.BBS # bad-baselines on 
          flux calibrators.
     (ii) It automatically updates the log file /home/gtaclog/ANALYSIS/GTACSUMMARY.HTML 
          This file can be browsed from

          *  This diagnostic package analysis all ltafiles mentioned in the gtac  observing log; the user
             doesn't need to give any program/ltafile name  manually.
          *  This is a beta version which works only for "Indian Polar Mode".