Instructions for 
1. Running the bmad based tacking program 'g2_tracking' to determine depencies of correlations in stored distribution on 
    - Twiss parameters at T0 (the T0 detector is immediately upstream of the hole into the backleg iron of the g-2 magnet)
    - Correlations in the initial distribution
    - Injection trajectory
    -
2. Compilation and preliminary analysis of the program output

1. Running the program
   a. Create a working directory. We will call it 'working'. (The program generates a lot of output so before proceeding 
      be sure that there is sufficient disck space available) 
   b. co to the working directory
   c. Copy the following files to working
        cp /nfs/gm2/data2/dlr10/g-2/mytest/ydelta_correlation/example/bmad_esquad_grid_split_dfree.  working/.         
	   											     		       !This is the lattice file that defines the system layout
        cp /nfs/gm2/data2/dlr10/g-2/mytest/ydelta_correlation/example/ref_input.dat  working/.    !The input file with parameters specific to the run
        cp /nfs/gm2/data2/dlr10/g-2/mytest/ydelta_correlation/example/quad_input.dat  working/.    !Quadrupole voltages
        cp /nfs/gm2/data2/dlr10/g-2/mytest/ydelta_correlation/example/submit_20.sh  working/.    !Batch submission control file
        cp /nfs/gm2/data2/dlr10/g-2/mytest/ydelta_correlation/example/g2.sh  working/.    !Basic batch submission comand file
    d. Additional files common to all runs are accessed via soft links. To create the soft links type
           /home/dlr/development9_linux/g-2/softlink_lnx        (and then carriage return) on the command line

    Parameter input file
      There are many parameters defineable via the input file.
      For the moment we restrict ourselves to
          nturns = 150               !The number of turns around the ring.
          nmuons = 100000       ! The numbe of muons to propagate through the injection channel and into the ring
          muon_first = 0            !The muons are pulled from a file generated by an upstream simulation. There are about 1.4 million
                                                  particles in the file. It is convenient to run jobs with 'nmuons = 100000'. Then in order to sample all
                                                  of the particles in the file, we start successive runs  with muon_first = 0, then muon_first=100000, etc.
          muon_file =  'EndofM5_Valetov_withInit.dat'   !This is the file with 1.4 million muons

! <twiss> :12-real - betax, betay, alphax, alphay, etax, etapx, etay, etapy, phix, phiy, gammax, gammay at reference point
          twiss     = 25.0, 4.0, 7., 3.0, 0.0, 0., 0., 0., 0.7, 0.7, 0., 0.  ! We will be varying betay (here equal to 4.0) and alpha_y (here equal to 3.0)                                                   

 - Test run
       In order to be sure that all relevant files are in place and that the input file is properly formatted it is good to run a test before submitting jobs to the compute grid
       The prorgam  (g2_tracking) reads the file
              'input.dat'    - (This is where you set nturns, nmuons, muon_first, etc.)
       To run the program type
           /home/dlr/development9_linux/production/bin/g2_tracking          - followed by a carriage return

      Note that each time the program is initiated, a subdirectory is created named 'data_time'. All of the output files are written to this subdirectory.
      Also, the input.dat file and the lattice files are written to the subdirectory for future reference.
       
3. Batch submission
      To submit a single job to the compute grid use the command
           qsub 
       To check on the status of the submission use the command
           qstat
        And to kill a job that you have submitted
           qdel   <job number>    (which you get with the qstat command)

      To get through all the 1.4 million particles in the 'muon_file' it is convenient to take advantage of the CLASSE compute grid.
      There are a couple of hundred nodes in the grid. There is a quota of ~60 nodes per user at any one time.
      We might submit 19 jobs with 'nmuons' and 'muon_first' so designated
        1.         nmuons = 75000
                    muon_first = 0       

         2.        nmuons = 75000
                    muon_first = 75000       

         3.        nmuons = 75000
                    muon_first = 150000       

         4.        nmuons = 75000
                    muon_first = 225000
              .......

         19.      nmuons = 75000
                    muon_first = 1350000