***********************************************************************
*** cmkin->cmsim->orca->analysis stuff for Ooty ***********************

in   ~anikiten/public/html/ooty_orca6/
                                     cmkin/
                                     cmsim/  
                                     orca/
                                         todo_federation/
                                         todo_ooHits/
                                         todo_Digi/
                                         jet_analysis/

it uses cms125 and ORCA_6_1_0_pre1
=============================

I call below as $SCRATCH the area where federation DB will be created,
ORCA project will be running and where cmsim fz & rz files will be
placed.
***********************************************************************
***********************************************************************

                            DO STEPS BELOW

*** Run cmkin to create 100 jets of Et = 40-50 GeV; eta < 0.8

0. use all files in ~anikiten/public/html/ooty_orca6/cmkin/
	 
1. type cmsim cms125

2. kine_make_ntpl_pyt.com                     create executable on 
                                              $SCRATCH area

3. kine_make_ntpl_pyt.run                     run cmkin/pythia
 
4. file qcd_40_50.ntpl will be created in ~ 1 min real time

5. mv qcd_40_50.ntpl to the area where cmsim will be run

*** run interactive cmsim to process 100 jets generated in previous step ***

0. use all files in ~anikiten/public/html/ooty_orca6/cmsim and qcd_40_50.ntpl;
   type cmsim cms125   

1. cmsbuild -i -S *.F

2. change path in cms125.titles to save qcd_40_50.fz on $SCRATCH
   line :
       'EVTO' '/afs/cern.ch/user/a/anikiten/scratch0/qcd_40_50.fz '    


2. cms125i.run  
   GEANT > trig 100   it takes ~ 10 min real time to process 100 jets at 
                      cern lxplus cluster with interactive cmsim 

3. file cms_geom.rz will be created , copy it to the $SCRATCH area
   file qcd_40_50.fz will be created on $SCRATCH area.

*** create and initialize your own federation *************************

0. go to $SCRATCH area                        to have in this area your
                                              federation and work with
                                              ORCA 
1. project ORCA                                           


2. scram project ORCA ORCA_6_1_0_pre1         create ORCA area for version 
                                                  ORCA_6_1_0_pre1 

3. cd ORCA_6_1_0_pre1
   eval `scram runtime -csh`                  set runtime variables in
                                              config/Runtime.
                                              You can provide similar files 
                                              (Runtime) wherever you want
   cd ..	
 

4. makefd.local                               It will create a subdirectory
                                              myoofd. If you are using bash, 
                                              ksh or zsh, you should give 
                                              ``-sh'' as argument. 

5. cd myoofd                                   look at what is in you 
                                               federation at the moment

6. source fdinit.csh                           to set OO_FD_BOOT environment
                                               variable

*** store in an ORCA database the simulated GEANT hits from the FZ files ***

0. from ORCA_6_1_0_pre1/src do :
     cvs co -r current Workspace

1. cd Workspace
   rm *.*

2. cp ~anikiten/public/html/ooty_orca6/orca/todo_ooHits/BuildFile .
   cp ~anikiten/public/html/ooty_orca6/orca/todo_ooHits/writeHits.csh .
   cp ~anikiten/public/html/ooty_orca6/orca/todo_ooHits/writeHits.cpp .
   
3. scram b

4. source writeHits.csh

5. eval `scram runtime -csh`
   writeHits       it takes ~ 3 min real time

*** Digitization  ***********************************************************

0. do it in Workspace :
   cp ~anikiten/public/html/ooty_orca6/orca/todo_Digi/BuildFile .
   cp ~anikiten/public/html/ooty_orca6/orca/todo_Digi/writeDigis.cpp .
   cp ~anikiten/public/html/ooty_orca6/orca/todo_Digi/writeDigis.csh .

1. scram b

2. source writeDigis.csh

3. eval `scram runtime -csh`
   writeDigis     it takes ~ 5 min real time

*** Analysis     ************************************************************

0. cp ~anikiten/public/html/ooty_orca6/orca/jet_analysis/BuildFile .
   cp ~anikiten/public/html/ooty_orca6/orca/jet_analysis/jet_analysis.cpp .
   cp ~anikiten/public/html/ooty_orca6/orca/jet_analysis/jet_analysis.csh .
   cp ~anikiten/public/html/ooty_orca6/orca/jet_analysis/My_Jet.h .
   cp ~anikiten/public/html/ooty_orca6/orca/jet_analysis/My_Jet.cc .


1. scram b
   read at the top of jet_analysis.cpp file what it is doing

2. eval `scram runtime -csh`
   source jet_analysis.csh
   jet_analysis                it takes ~ 30 sec real time to process 100 jets

3. look at qcd_jj.hbook with PAW

4. what to do with code in jet_analysis.cpp :
     
     a. try to supress false jets with change of seed initiator threshold
        and see finding efficiency for real jets. 
     b. optimize jet resolution v.s. cone size
     c. add more information to ntpl : 
                          em. and had. part of jet et 
                          missing Et



CC : commands to start ams and lockmanager : oostartams, oolockserver