30 likes | 114 Views
MC of CalDet. G.Choudalakis,P.Stamoulis,G.Tzanakos,M.Zois University of Athens. GOAL: Interaction Discrimination In order to discriminate neutrino interaction types (with any method), we have to “get a feeling” of how the different interactions and particles look like in our detectors.
E N D
MC of CalDet G.Choudalakis,P.Stamoulis,G.Tzanakos,M.Zois University of Athens • GOAL: Interaction Discrimination • In order to discriminate neutrino interaction types (with any method), we have to “get a feeling” of how the different interactions and particles look like in our detectors. • Especially for ANN techniques,we must have good MC representations of particle interactions in the detectors to use in training. • We tried to reproduce the CalDet data with the MC provided • We followed the instructions and code found at • http://www.hep.utexas.edu/~kordosky/mc.html • (Thanks to Mike, Tricia and Robert for continuous help and interaction). • Working on flxi03 machine GCC 3.2, ROOT 3.05.07 • Using stable versions of gnumi and analysis software packages:(The following lines appear on .cshrc): source/afs/fnal.gov/files/code/e875/sim/labyrinth_sandbox/setup_labyrinth.csh source/afs/fnal.gov/files/code/e875/general/minossoft/setup/setup_minossoft_FNALU.csh -r R1.2 • constructed ~200 events of each “single particle beam”:electrons,muons,pions,protons • Not getting any error messages when building the software, running gnumi (as modified by Mike), rerooting or ‘looning’ the reroot files, BUT:
ELECTRONS MUON(S) PROTONS mind the gap! It appears on ~2/3 of electron events ALL muons are as ‘hit-poor’ as the one shown No hits in one view! PION(S) More than half of the pions seem to “start late” a.Minor disturbance: all snarls have snarl no ~ 4.9x107 (more likely,they are never filled?) b.More important:The electrons,muons,pions and protons(?) do not look as expected*...[see below] *how do we know what we are expecting-->CalDet Data with cerenkov and TOF information Pictures:electrons,muons,pions and protons 2.4GeV/c,MC.Separate x and y views. Color coded according to pulseheight
First Reaction:What are we doing wrong? Help needed from the experts... All logfiles and details about the procedures are available on request OR Is something wrong with the MC? Conjecture: Something is hard-coded into the MC that creates particles with equal probabilities anywhere inside the detector...This obviously must be turned off for CalDet AGAIN, Help needed from the experts...