# Presentation: 408841

## Monte-Carlo data quality control based on package MC_EXAM

**Introduction: what is MC_exam and what it does**
**History**
**Brief description of variables and Functionalities**
**Some representative plots (simulation and digit)**

**A. ****Zylberstejn**** **
**ADM: April/04/03**

## Why revive mc_exam?

**After some catastrophe having occurred in  M.C. production, we were asked if MC_exam could ****have ****be****en**** used to check MC production at different level**
** ****This talk to try to convince D0**** that the answer is  « yes »**

## Introduction : MC_exam history  I

**MC_EXAM: an histogram, ntuple or root-tuple maker written at  very early stages of D0 II before most analyze packages were written to check Monte-Carlo production. **
**Main contributors: L. Duflot, A.Zylberstejn**
**Designed to analyze and/or reconstruct data coming from D0gstar. Intended to be equivalent of EXAMINE for M.C.. **
**Information about HITS, DIGI for most sub detectors:SMT, CFT, CAL (DIGI only), CPS, FPS and MUON as well as information on the generated particles were written in the histograms or Ntuple/Rootuple. **
**Several bugs found both in GEANT (ex:polycone was wrong) and D0GSTAR (ex:CFT digitization)**
**Later on, blocks corresponding to reconstructed quantities (clusters in all the detectors, tracks) were added. In addition, the MCexam_x executable was compiled with some analyze packages  allowing to get physics objects variables in the same ntuple.**

## Introduction : MC_exam history  II

**Linked with D0gstar but never used (?)**
**Then more and more detector specialized analysis packages becoming available(and less and less users)  ******** abandoned and removed from the release.**

## Brief description of MC_Exam 

**Framework Package****:**** ****MC_exam****  split in 3 main packages: ****Sim_exam, Reco_exam and MC_exam****.**
**   ****And 2 “satellites”: ****gene_exam and trig_exam**
**Each package  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”  **

## Variables being histogrammed in sim_exam

**Generator**
**GEANT hits: x, y, z, de/dx , range, p,... in all the « sensitive » detectors (except calo)**
**E, ieta, iphi of all hit calo cells ****or**** E, ieta, iphi of EM and Hadr. towers**
**px,py,pz,pid,vertex... for KINE**
**Simulation:**
**Channel number (strip , layer,... ADC)  **
**No analyze of  muon detector**

## Slide 7

## Plots for Zee digitization: nb of hits

**CPS**

**Calo cells**

**Calo towers**
**EM**

**Calo towers**
**HADR**

**Calo towers**
**ICD and MSG**

**FPS**

**CFT**

**SMT barrels**

**SMT disks**

## Cells

**Cells**

## Towers

- , unweighted

- , weighted

**Towers**

## Plots for Zee digitization

**FPS**

**CFT**

**Nb of strips North**

**Nb of strips South**

## Works on DST’s (or raw data). Not (yet) adapted to Thumbnails
Plots/Ntuple for quantities defined at the reconstruction level Plotted quantities:
Clusters (x, y, z, E, extension...) 
Physics objects (tracks, jets, electron, muons, vertex) using the appropriate analyze package (not rewritten except for tracks)

**Plots/Ntuple for quantities defined at the reconstruction level Plotted quantities:**
**Clusters (x, y, z, E, extension...) **
**Physics objects (tracks, jets, electron, muons, vertex) using the appropriate analyze package (not rewritten except for tracks)**

**Reco_exam**

## Zee-p1308 reconstruction:nb of clusters

**cft**

**cps**

**FPS North**

**FPS South**

**SMT barrel**

## Zee-p1308 reconstruction

**Nb of******

**Nb of jets**

**Nb of tracks**

**Nb of elec**

## Example of quantities plotted at reco level: CFT

**CFTC : block for clusters**
**Ncftc: nb. of information **
**lay_cftc:layer number (0 to 15 )**
**nst_cftc:width of the cluster (in nb. of strips) **
**str_cftc: center of the cluster (in nb. of strips) **

## MC_exam== sim_exam and reco_exam linked together.
    Plotted quantities (chosen by turning on/off rcp keys):
Hits 
Digits
Generated particles and vertices
Clusters 
Jets
Tracks 
Physics objects

**    ****Plotted quantities**** (****chosen by turning on/off rcp keys****)****:**
**Hits **
**Digits**
**Generated particles and vertices**
**Clusters **
**Jets**
**Tracks **
**Physics objects**

** ****MC_exam**

## Example of quantities plotted at digi and reco level: CPS

**CPSD :  block for CPS digi **
**ncpsd: nb. of information**
**e_cpsd: energy **
**lay_cpsd: layer **
**str_cpsd: strip number **
**CPSC :  block for CPS clusters**
**ncpsc: nb. of information **
**e_cpsc(ncpsc) energy **
**x_cpsc: X in general system**
**y_cpsc: Y **
** ****z_cpsc: Z**

## SMTD: block for SMT barrel digits 
nsmtd nb. of information 
e_smtd:
iba_smtd: barrel number 
ild_smtd: ladder number 
ily_smtd: layer number 
ist_smtd: strip number 
iv_smtd: View (n or p side) 

**nsmtd nb. of information **
**e_smtd:**
**iba_smtd: barrel number **
**ild_smtd: ladder number **
**ily_smtd: layer number **
**ist_smtd: strip number **
**iv_smtd: View (n or p side) **

**Another example of quantities plotted at digi level: SMT barrel**

## Slide 19

## SMTB: block for SMT barrel clusters
nsmtb: nb. of information 
bar_smtb: barrel number
ex1_smtb: de/dx "n" side 
ex2_smtb: de/dx "p" side 
lay_smtb: layer nb. 
phi_smtb: 
st1_smtb: nb. of strips "n" side 
st2_smtb(nsmtb) nb. of strips "p" side
xg_smtb, yg_smtb, zg_smtb

**nsmtb: nb. of information **
**bar_smtb: barrel number**
**ex1_smtb: de/dx "n" side **
**ex2_smtb: de/dx "p" side **
**lay_smtb: layer nb. **
**phi_smtb: **
**st1_smtb: nb. of strips "n" side **
**st2_smtb(nsmtb) nb. of strips "p" side**
**xg_smtb, yg_smtb, zg_smtb**

**Another example of quantities plotted reco level: SMT barrel**

## Recent development

**Until recently emphasis put on ntuples and histos.**
**	****	****Major draw-backs:**
**Histos: predefined histos. Have to modify the code and re-run the program if binning not adequate or more histos**
**Ntuples: limited nb. of information can be written; Incompatibly with many analysis programs( names too long)**
**Decided to go to root_tuples**
******  ****Macros are being written**
**	****	****(AZ and D. Vilanova)**

## Strategy ? 

**Should we link ****sim_exam and gene_exam ****together ****with D0gstar****? Or run mc_exam on the ouput of d0gstar/d0sim?**
**Should we run reco_exam on DST (and/or thumbnails)?**
**Should we produce histos or root-tuples?**
**Detector groups/id groups/physics groups to define relevant set of variables to be histogrammed**

## Didier Vilanova

**Didier Vilanov****a**

## Slide 24

## Slide 25

## Slide 26

## Slide 28

## Slide 29

## Slide 30

## Slide 31

## Slide 32

## Slide 33

## Slide 34