How to run MC_exam

Updated :April 2003  Major cleaning and added chapter H in complement of Chapter G for MC testing
This file can be found on /dist/packages/mc_exam/devel/doc/mc_exam.html
This is a description on how to run the histogram/Ntuple/Root-tuple maker.
 In case of problems/suggestions contact: Laurent Duflot and Armand Zylberstejn and Sarah Eno

A-Introduction
B-Description of the packages
C-Building a working directory and getting the files
D-Important warning using mc_exam
E-Running the executable
F-Description of rcp files
G-Using the code: a few examples
H-More examples: how to run the code to test MC production
I-Liste of macros to run the jobs and analyze the root-tuples
J-Use the macros to run the jobs and analyze the root-tuples
K-Brief instructions to run and analyze a sim type file (written by Sarah- July 2003)
 

A-Introduction

    MC_exam , an histogram, ntuple or root-tuple maker was written  before most analyse packages were written. It was first designed to analyse and/or reconstruct data coming from D0gstar.
     Informations about HITS, DIGI and clusters for most subdetectors:SMT, CFT, CAL (DIGI only), CPS, FPS and MUON as well as informations on the generated particles were written in the histograms or Ntuple/Rootuple.
    Later on, blocks corresponding to reconstructed quantities (clusters in all the detectors, tracks) were added. In addition, the MCexam_x executable was compiled with em_analyze, jet_analyze, MuoIdAnalyze, VertexAnalysis_data allowing to get in the same Ntuples the blocks defined in these  packages.
    Since the d0reco package has somewhat stabilized since the early times when MC_exam was written,  the reco part of MC_exam is deprecated, although still doable.
    As of release t01.22.00 the old package MC_exam has been split in 3 different packages: Sim_exam, Reco_exam and MC_exam. Later on, the part for generated particles was put in a separate package: gene_exam.
     Since January 2003 (release p13.04.00) MC_exam as well as Sim_Exam and Reco_exam are not part of the releases and the devel versions have to be used.

B-Description of the packages

  What can be done in each of the package is driven by its own  two rcp files: framework.rcp and XX_exam.rcp
  In each package the quantities entering in the plots may be re-built using the appropriate keys in framework.rcp

•  Sim_exam:

Plots/Ntuple for quantities defined at the simulation  (MC ) and/or digi level (MC and data) for all detectors. Some relevant quantities can be rebuilt

• Plotted quantities:

    Hits : x,y,z,px,py,pz,dE/dx 
    Digits : channel address, ADC
    Generated particles and vertices (plot in package gene_exam)

• Functionnalities

    Hits cannot be rebuilt
    Digits can be rebuilt after dropping the relevant chunks before being plotted
    No reconstructed quantities (clusters, objects) can be plotted or rebuilt

• Reco_exam:

• Plotted quantities:   

    Clusters
    Jets (using jet_analyze)
    Tracks
    Generated particles and vertices
    EM- object (using em_analyze)

• Functionnalitie:

    Hits or digi cannot be rebuilt nor plotted;
   Clusters, jets, em objects can be rebuilt after dropping the relevant chunks prior to be plotted.

 

• MC_exam:

• Plotted quantities:   

            Hits
            Digits
            Generated particles and vertices
            Clusters
            Jets (obsolete, replaced by call to jet_analyze)
            Tracks

• Functionnalities

Hits cannot be rebuilt;
Digits can be rebuilt after dropping the relevant chunks before being plotted;
clusters, jets, em objects can be rebuilt after dropping the relevant chunks prior to be plotted

 C-Building a working directory and getting the files

What a package does is controlled by the list of packages given in its own framework.rcp. The list of packages called is described below and may be modified by the user at execution time
Reco_exam and MC_exam are linked with d0reco and included are the Ntuples made by some analysis packages: em_analyze, jet_analyze, MuoIdAnalyze, VertexAnalysis_data
As these packages rely on most of the offline packages to compile and run smoothly, it sometimes happens (as for d0reco) that the xx_exam version on a given release is broken. Please have a look at the mc_exam news page for indications on which versions of xx_exam work with which release and for new features of the packages

Setting up a working directory (assuming one does not exist already)

cd working_dir (your working directory)
setup D0RunII <release version> (for now on and for clarity we will use t01.30.0 as example)
newrel -t t01.30.00 mcexm (mcexm is an arbitrary name) cd mcexm
d0setwa


Access the package and define the rcp files and files for constants


    There are 2 cases: either you want to change anything in the code or not. After release p13.04 these packages are not part of the releases and you must go to part 2
 
No change in the code is required: access directly the executable which was built in the release

We describe how to use mc_exam packages so that the user can cut and paste the needed lines.
We assume that the user is in  mcexm
mkdir -p sim_exam/rcp
mkdir -p sim_exam/bin
cd sim_exam/rcp
cp $D0RUNII_DIR/sim_exam/rcp/*.rcp .
cd ../bin
$D0RUNII_DIR/sim_exam/bin/only_once.csh
$D0RUNII_DIR/sim_exam/bin/make_link.csh
rm Analyze.x
ln -sf $D0RUNII_DIR/bin/$SRT_SUBDIR/Simexam_x Analyze.x
 cp $D0RUNII_DIR/sim_exam/bin/*.list .

or

mkdir -p reco_exam/rcp
mkdir -p reco_exam/bin
cd reco_exam/rcp
cp $D0RUNII_DIR/reco_exam/rcp/*.rcp .
cd ../bin
$D0RUNII_DIR/reco_exam/bin/only_once.csh
$D0RUNII_DIR/reco_exam/bin/make_link.csh
rm Analyze.x
ln -sf $D0RUNII_DIR/bin/$SRT_SUBDIR/Recoexam_x Analyze.x
cp $D0RUNII_DIR/reco_exam/bin/*.list .

mkdir -p mc_exam/rcp mc_exam/bin
cd mc_exam/rcp

cp $D0RUNII_DIR/mc_exam/rcp/*.rcp .
cd ../bin
$D0RUNII_DIR/mc_exam/bin/only_once.csh
$D0RUNII_DIR/mc_exam/bin/make_link.csh
rm Analyze.x
ln -sf $D0RUNII_DIR/bin/$SRT_SUBDIR/MCexam_x Analyze.x
cp $D0RUNII_DIR/mc_exam/bin/*.list .

Now we have made a working directory to be used by the D0 framework, setup the rcp database. Then links to the XXexam_x executable has been made as well as other links needed to run mc_exam on sim files (i.e. calling the reco packages). We have created a local/rcp directory to hold the rcp script that we may modify. The framework control rcp has been copied to the working
directory.
 
Some changes are required in the code (or release nb. >p13.04)


          We assume that the user is in mcexm
          In the following, xx stands for reco, sim or mc

           setup d0cvs

   For releases containing mc_exam you can run the packages individually; you type: addpkg [-h] xx_exam
[    -h]  is optional for release < p14.01 (Jan 2003) and compulsory above, not using it makes you retrieve the version associated with the release <release version>  if it exists
cd xx_exam/bin
only_once.csh
make_link.csh
For releases  not containing mc_exam you must "addpkg" all the packages:

            addpkg -h gene_exam
            addpkg -h sim_exam
            addpkg -h reco_exam
            addpkg -h mc_exam
            addpkg -h trig_exam

Then you have to link some files in the packages this is done using the 2 script files:  only_once.csh  and    make_link.csh that are found in the directories   xx_exam/bin   


cd sim_exam/bin
only_once.csh
make_link.csh
cd reco_exam/bin
only_once.csh
make_link.csh
cd mc_exam/bin
only_once.csh
make_link.csh


if you want to change anything in the histograms or ntuple for dectector DET , yyy (Where DET is a detector name and yyy is hit, clus or dig)..
edit the files mcexm /sim_exam/Exam_DET_yyy.hpp and mcexm/sim_exam/src/Exam_DET_yyy.cpp mcexm/Reco_exam/Exam_DET_yyy.hpp and mcexm/reco_exam/src/Exam_DET_yyy.cp

gmake : build the executable the first time, this may take up to 30 mn.  After the first time when all the dependencies ahev been built, you may wa    nt to us use gmake xx_exam.lib and gmake xx_exam.bin. The experts do not recommend these 2 last procedures but it saves a lot of waiting time.

D-Important warning using mc_exam:

      MC_exam.rcp is there for compatibility with the framework. The control parameters for the package are actually Sim_exam.rcp and Reco_exam.rcp. We highly recommend, if  you want to have the control of  what exactly goes on the Ntuple, to change in ../rcp/framework.rcp RCP sim_exam  = <sim_exam Sim_exam>  to      RCP sim_exam  = <mc_exam Sim_exam>
RCP reco_exam  = <reco_exam Reco_exam> RCP reco_exam  = <mc_exam Reco_exam>

E-Running the executable

 MC_exam and sam

xx_exam are already linked with sam_manager. Call sam_manager in the framework rcp ("sam"). You can use the provided  xxx_exam/bin/run_sam.sh script file to run xx_exam with sam. The variables you would have to modify are:

• SAM_PROJECT_NAME: the name of you sam project.
SNAP_VERSION: your snapshot version or "last" or "new".
• EXEC: the name of the executable.
• SAM_LOCAL_BUFFER: a directory where sam will stage the files.

Tracking and jets

The default option for tracking is reconstruction in full eta
 The default options for jets is reconstruction using all the known algorithms
 

Warning

 By default, the ntuple is written with HBOOK, to switch to ROOT, copy NtupleMgr.rcp to local/rcp and change it.
For people using COMIS routine to analyze the NTUPLE: if a detector is not selected in XX_exam.rcp then the corresponding block is not written on the NTUPLE. Therefore the common block /PAWCR4/ created using uwfunc changes according to the detectors which are selected. To avoid this problem we suggest that you use in "INCLUDE ?" in your comis routine. See file nvert_prim.f in mc_exam/bin for an example.

F-Description of rcp files

Sim_exam.rcp

// rcp for sim_exam
int Nprint =0 // set the number of evts to be printed
 int debug =1 //minimum print output: Enter and exit of "routines"
//------------------------------
// parameters for subdetectors selection if 0 -> not selected
// switch on (=1)/off (=0) hits, dig for all detectors
 //------------------------------
int Do_hit =1  //analyse the hits
int Do_dig =1 //analyze the digi
//------------------------------
//switch off/on total detector
//------------------------------
int Do_SMT =1 // turn on(=1)/off(=0) the SMT
int Do_CFT =1 // turn on /off the CFT
int Do_CPS =1 // turn on /off the CPS
int Do_Calo =1 // turn on /off the calo
int Do_FPS =1 // turn on /off the FPS
int Do_Muon =1 // turn on /off the Muon system
//------------------------------
//turn off/on plot/ntuple for SMT
//------------------------------
int Xsmt_dig =1 // digi off/on
float Emin_SMT_dig = 0.0005 //energy threshold to be written on Ntuple
int Nmax_SMT_hit =100 //Max number of set of elements in the Ntuple block
int Xsmt_hit =1 // turn SMT hit off/on
float Emin_SMT_hit = 0.0 //Threshold value for de/dx for the block being written on the Ntuple
int Nmax_SMT_dig =100
//------------------------------
//turn off/on plot/ntuple for SFT (see definition of variable above)
//------------------------------
int Xsft_dig =1
float Emin_SFT_dig = 0.0005
int Nmax_SFT_dig =100
int Xsft_hit =1
float Emin_SFT_hit = 0.0
int Nmax_SFT_hit =100
//------------------------------
// CPS (see definition of variable above)
//------------------------------
int Xcps_dig =1
float Emin_CPS_dig = 0.0005
int Nmax_CPS_hit =100
int Xcps_hit =1
float Emin_CPS_hit = 0.0
int Nmax_CPS_dig =100
//------------------------------
// FPS (see definition of variable above)
//------------------------------
int Xfps_dig =1
float Emin_FPS_dig = 0.0005
int Nmax_FPS_dig =100
int Xfps_hit =1
float Emin_FPS_hit = 0.0
int Nmax_FPS_hit =100
//------------------------------
// Calo
//------------------------------
int Xcal_dig =0 //Calo digitization
float Emin_Cal_dig= 0.001
int Nmax_Cal_dig =100
float ECAEP = 0.01
float ECAL = 0.050
int Xcaep =0 //do not turn on
//------------------------------
// muons
//------------------------------
int Xmuon_dig =0 // muon digi
float Emin_muond =0.00
int Nmax_muon_dig =100
int Xmuon =1 //muon hits
float Emin_muonh =0.00
int Nmax_muon =10
int Xmuon_segm =0 //not implemented
int Xmuon_hitr =0 //not implemented
//------------------------------
// generated part. (obsolete: replaced by call to gene_exam in framework.rcp)
//------------------------------
int Xkine =1 // turn off/on histos/ ntuple for generated tracks
float Etmin_Kine = 3. // Pt threshold to be written on Ntuple
int Nmax_track_gen=500
int Nmax_vert_gen =200
int Only_Stab =1 // select only stable(=1) or all- including initial partons- (=0) part. to write on Ntuple
//------------------------------
 int Do_Histo =0 //turn histo off(=0)/on(=1)
int Do_Ntuple =1 //turn ntuple (root) off/on
int Do_NtupleDig =0 //do not turn on
int Effic =0 // do not turn on : for experts
int Flavor_Sel_Part =-350 // select B (350 is a Bs);
int Flavor_Sel_Apart =0 //

Reco_exam.rcp

string Use_TIM = "auto" //choices are "auto","no","yes"
  //auto is NO-tim for DCA and CFTV4, TIM for CPS and CRYO
   //"no" impose no_tim everywhere,"yes" impose TIM everywhere
string Last_Plane ="CRYO" //choices are: CFTV4, CPS, CRYO
float ECAEP = 0.01
float ECAL = 0.050
int Flavor_Sel_Part =-350 // select B (350 is a Bs);
int Flavor_Sel_Apart =0 //
int Nprint =0 // set the number of evts to be printed
 int debug =1 //minimum print out


//------------------------------
// SMT
//------------------------------
int Xsmt_clus =1
float Emin_SMT_clus = 0.0
int Nmax_SMT_Barrel_clus =100
int Nmax_SMT_Disk_clus =100

//------------------------------
// SFT
//------------------------------
int Xsft_clus =1
float Emin_SFT_clus = 0.0
int Nmax_SFT_clus =100


//------------------------------
// CPS
//------------------------------
int Xcps_clus =1
float Emin_CPS_clus = 0.0
int Nmax_CPS_clus =100
//------------------------------
// FPS
//------------------------------
int Xfps_clus =1
float Emin_FPS_clus = 0.0
int Nmax_FPS_clus =100
//------------------------------
//turn off/on plot/ntuple for jets (obsolete: replaced by call to jet_analyze in framework.rcp)
//------------------------------
int Xcal_clus =1 //allows turning on/off of calo clusters
int Xcal_clusNN =0 //nearest neighbor algorithm
int Xcal_clusC =1 //cone algorithm
int Xcal_clusSC =0 //simple cone algorithm
int Xcal_clusKT =0 //kt algorithm
int Xcal_clusKTKINE =0
int Xcal_clusGX =0//cellnn
int Nmax_calo_jets =10
int Nmax_jets =20
//------------------------------
// muons
//------------------------------
int Xmuon_segm =0 //not implemented
int Xmuon_hitr =0 //not implemented
float Emin_muonh = 0.00
float Emin_muond = 0.00
int Nmax_muon_dig=100
int Nmax_muon=100


//-------------------------------------------------
// reconstructed vertices
//-------------------------------------------------
int Xvertex =0
int Nmax_vert_reco=200

//------------------------------------------------
// reconstructed tracks
//-------------------------------------------------
int Tracking =1
int Nmax_tra =200 //maximum nb. of recontructed track
float Track_min_Pt=1.
//select type of reconstructed tracks (0 = all)
//reconstructed track ID
// ID = 101 CFT only (central and overlap)
// ID = 111 central CFT only -no SMT
// ID = 121 is overlap CFT only- no SMT
// ID = 201 is for central and overlap CFT tracks extended into the SMT.
// ID = 301 SMT only
// ID = 401 tracks in all eta SFT+SMT
int Track_Type = 401
int Errors =0 //write error matrix in block TRACK, kept for back
compatibility
string error_dca ="none"// error on the track at the DCA
//choices are "diag" "full ,"none"
string error_last ="none"// errors on the track at last chosen plane
// choices are "diag" "full ,"none"


//---------------------------------
// etmiss
//---------------------------------
int Xetmiss =1
int Nmax_Etmiss =1
float Emin_Etmiss=1.

//---------------------------------
float EFPS = 0.0005
 
int Do_Histo =0 //turn histo off/on
int Do_Ntuple =1 //turn ntuple (root) off/on
int Effic =0 // do not turn on : for experts
 

framework.rcp:

The main keys are:

geo read ->standard: do not touch
drop chunks (check DropEvent.rcp to check if it corresponds to what you want)
smt1b smt1d smt2b smt2d smt3b smt3d smt4b smt4d -> perform SMT clusters reconstruction
cft1 cps1 fps1 -> CFT,  CPS and FPS: perform digitization
cft2  cps2 fps2-> CFT, CPS and FPS: perform clusterization
gtr-> perform reconstruction of tracks .
 vtxpv1 vtxsv1 vtxpv2 vtxsv2 -> primary and secondary vertex reconstruction and filtering
cal0 scone EMnn cone kt ktkine -> different jet algorithms
em ->emreco
met -> missing Et
ntplmgr -> use global Ntuple (recommended)
sim_exam, reco_exam -> build histos and/or root/ntuples using sim_exam, reco_exam
em_ana ->put in Ntuple blocks for em-id
ntplmgr: allows to put in the same Ntuple, blocks coming from various packages (recommended) .
Do not use if histo option is chosen in XX_exam.rcp (int Do_Histo =1) //turn histo off/on)

G-Using the code: a few examples

Sim_exam:

cd /mcexm/sim_exam/rcp
Edit Sim_exam.rcp: to choose the type of data you want to histogram:
      Set to 1 (0) the key associated the detector you do (not) want to examine,
For instance:
 
digi, no geant hits:

int Do_hit =0
int Do_dig =1
int Do_SMT =1; // turn on the SMT
int Do_CFT =1 // turn on the CFT
int Do_CPS =1 // turn on the CPS
int Do_Calo =1 // turn on the calo
int Do_FPS =1 // turn on the FPS
int Do_Muon =0 // turn off the Muon system
int Xsmt_hit =1 // allow turn on of all hits on
int Xsft_dig =0 // turn off all digi
int Xsft_hit =1//turn on hits for cft
and the same for the other detectors

           no digi except for calo geant hits:
int Do_hit =1
int Do_dig =1
int Do_SMT =1 // turn on the SMT
int Do_CFT =1 // turn on /off the CFT
int Do_CPS =1 // turn on the CPS
int Do_Calo =1 // turn on the calo
int Do_FPS =1// turn on the FPS
int Do_Muon =1 // turn on the Muon system
int Xcal_dig =1
int Xsmt_dig =0 // digi SMT off
int Xsmt_hit =1  // hit SMT on
int Xsft_dig =0  // digi CFT off
int Xsft_hit =1 //allow hit to be turned on
int Xcps_dig =0 // all digi off int Xcps_hit =1 //hit CPS on
and the same for the other detectors

  geant hits and digi
 
int Do_hit =1
int Do_dig =1
int Xcal_dig =1
int Xsmt_dig =1 // allow digi to be turned on
int Xsmt_hit =1 // allow hit turned on
int Xsft_dig =1 // digi off/on
int Xsft_hit =1 //SFT hit on
int Xcps_dig =1// CPS digi on
int cps_hit =1 //CPS hit on
and the same for the other detectors

cd /mcexm/sim_exam/bin
Edit framework.rcp: to write generated tracks on the Ntuple:
                     on the line  string Packages= add  gene_exam 
                    add the line  (if not there already)     RCP gene_exam= <gene_exam Gene_exam>
Choose histo or ntuple
 
cd /mcexm/sim_exam/rcp
Edit Sim_exam.rcp
  
•   To build histograms
     int Do_Histo =1 //turn histo off/on)
    int Do_Ntuple =0 //turn ntuple (root) off/on   
  
• To build ntuples
  
  int Do_Histo =0 //turn histo off/on)
  int Do_Ntuple =1 //turn ntuple (root)
Edit framework.rcp

• on the line  "string Packages="   add  ntplmgr (Do not use this option if histo option is chosen in Sim_exam.rcp)
  
• add the line (if not there already)
  
RCP ntplmgr= <sim_exam NtupleMgr>

Edit NtupleMgr.rcp
  bool useHBOOK = false // if false use ROOT, if true  use PAW


Remark:

To look at digit's for data  is more complicated since we need to unpack the raw data chunk
The way to do it is not described in this document.

Reco_exam:

cd /mcexm/reco_exam/rcp
edit Reco_exam.rcp

As above set to 1 (0) the key associated the detector you do (not) want to examine,
for Ntuple/Roottuple: modify threshold values, modify max. number of objects in each block
For instance, let's assume that we no not want the clusters information of the SMT and FPS on the Ntuple:
 
int Xsmt_clus =0
int Xsft_clus =0

Edit framework.rcp .

string Packages = "geo read mcsetlinks reco_exam".
Do not use ntplmgr if histo option is chosen in Reco_exam.rcp

    Don't forget to change the references to Reco_exam.rcp and ReadEvent.rcp to :local Reco_exam and ReadEvent

Edit DropChunks.rcp (which you have copied in directory local)

string DropChunks = "GTrackChunk "

Edit framework.rcp .

string Packages = "geo read mcsetlinks gtr reco_exam".

MC_exam

You can mix at  will all the options you have in the previous 2 packages simulation
and reconstruction: you can plot and/or rebuild any chunk you want (except KINE and digi).
You have to adjust local/framework.rcp (or mc_exam/rcp/framework.rcp) and/or local/Reco_exam.rcp
(or mc_exam/rcp/Reco_exam.rcp) and/or local/Sim_exam.rcp
(or mc_exam/rcp/Sim_exam.rcp).You may add jetreco,emreco,em_analyze,?

H-More examples: how to run the code to test MC production

create_proj.csh: create sam project
run_job.csh      : create script to run with no sam
run_sam.csh     : create script to run with sam   
run_sam_all.csh   will submit anal-sim,anal-dig and anal-rec for a given project (that the macro will ask for)

global submission: must be done in working directory( mcexm in our case)
you need to define in your working directory a file containing the names of the project you want to analyze without its extension (sim, rec or dig)
   for instance you define file "single_p14_03-input"

single_mu_50_p140301
single_mu_10_p140301
single_e_10_p140301
single_e_100_p1403

sub_sam_dig will analyze the projects xxx_dig xxx_dig
sub_sam_fullwill analyze the projects xxx_dig, xxx_sim and xxx_rec
sub_sam_rec xxx_rec
sub_sam_sim xxx_sim
Exemple of global submission :
sub_sam_dig
   you are asked : define input file ?
  answer single_p14_03-input this will produce root-tuples for projects:
   single_mu_50_p140301_dig
   single_mu_10_p140301_dig
   single_e_10_p140301_dig
   single_e_100_p1403_dig

templ_ReadEvent 
templ_create_proj   
templ_rootMgr        
templ_run_sam      

•   Preliminary steps:
The first time you have to get the packages, make the executables and get some files for constants.
       If you do not have a working directory follow the procedures in chapter C

addpkg -h mc_exam
cd mc_exam/macros
Util.csh : this will addpkg the packages you need, make the libraries, make the executables (this may take some time) and get the appropriate files for constants
d0setwa,

and then run the job in the appropriate directory: sim_exam/bin for generated files ("d0g" type) and/or simulated file ("sim" type)

• Subsequent times:
  
  d0setwa,
  
• Running the job using SAM
  
  if project does not exist  check for request ID in certification samples in:
    http://www-d0.fnal.gov/computing/mcprod/mcc.html
and use this number to create the project using: create_proj.csh
            cd xxx_exam/bin (assuming you are in directory mcexm)
    to run on d0g data and/or sim: cd sim_exam/bin
    to run on dst:

cd reco_exam/bin
run_sam.csh and answer the questions
• Running the job with no SAM
(file(s) on disk (or on sam cache disk))
    to run on d0g data and/or sim:

cd sim_exam/bin

   to run on dst:

cd reco_exam/bin run_job.csh and answer the questions

I-Liste of macros

d0dist-d0dist-d0dist-dist-packages-mc_exam-devel-macros;

Util.csh               
anal_dig.C            
anal_dig.h            
anal_rec.C          
anal_rec.h               
anal_sim.C         
anal_sim.h          
create_proj.csh      
run_job.csh         
run_sam.csh           
templ_ReadEvent        
templ_run              
templ_run_sam

 Makefile_alpha_dig     
 Makefile_alpha_rec    
 Makefile_alpha_sim     
 Makefile_linux_sim     
 Makefile_sgi_rec       
 histo_dig.h            
 histo_rec.h      
 histo_sim.h          
 main_dig.C             
 main_rec.C            
 main_sim.C             
 make_ps.csh           
templ_create_proj      
templ_histo_dig.h     
templ_main_dig.C       
templ_main_rec         
templ_main_sim        
templ_rootMgr

J-Use the macros to run the jobs and analyze the root-tuples

K-Brief instructions to run and analyze a sim type file

setup D0RunII p14.03.01
setup d0cvs
newrel -t p14.03.01 lala
cd lala <
d0setwa
setup mc_runjob
addpkg -h mc_exam
cd mc_exam/macros
./Util.csh (ignore all the error messages)
wait a long time until the following exe's appear in ../../bin/Linux2.4-KCC_4_0/
    MCexam_x, Recoexam_x, Simexam_x
cd ../../sim_exam/bin
ln -s ../../d0g-dest/d0gstar/d0g(hit tab key) inputfile
edit run_job.csh and comment out the "set echo" lines and the last two lines
source run_job.csh
it will ask for inputs. give it the current directory (which it echos for you)
inputfile
sim
0
./Analyze.x -rcp frame_sim.rcp
source make_cl.csh
it will ask for inputs. give it
inputfile_sim.root
sim
source make_ps.csh
ignore errors
for P14 and below.. not for p15 and above
   edit Makefile
     make active: //ARCH =linuxkcc removing the //)
     delete: ARCH=Linux
gmake   This creates the executable anal_sim.x
anal_sim.x "path" "root_tuple_file" this creates 2 files :
"root_tuple_file".ps which is the old visualization of the histos and hist_"root_tuple_file".root which is a root-tuple file that contains the histos.