Introduction

This page is mean to collect info on our efforts to study the performance of the Tile Calorimeter with Cosmic rays.

Using cosmic muons to cross check the uniformity of the cells equalization and the absolute energy scale is a rather difficult task. Though the muon energy deposition is a very well understood phenomena the Calorimeter response to muons is rather complicated by the highly periodic inhomogeneous structure of absorber and active material. Sampled with the gauge of hadronic interactions the Tile is a remarkable homogeneous and uniform detector but using muon we can clearly underline the fine details in the structure of scintillator and iron absorber slabs.

The variation in the muon response due to different impinging points can be enormous for particular angles, resulting in having a well measured signal or nothing at all moving across distances of about one millimiter.

To control at the best the effects of the geometry we decide to use well defined tracks reconstructed in the Inner Detector and extrapolate them to the different calorimeter layers so that we can compute and control the impinging point position, the track path length, etc.

Tracks are required to have hits in the SCT detector. Tracks reconstructed exclusively by the TRT cannot be extrapolated with large precision, unless we use the combined reconstruction with the Muon Spectrometer. This latest option can be investigated in future.

A set of Ntuples with minimal contents to perform these studies has been produced, Info on the contents and location are included below.

The data used here represent a small fraction of the ATLAS cosmic data, one other approach that is less constrained is also studied in Tile (TileMuonFitter).

Preliminary list of possible topics to investigate and people interested

  • uniformity in the intercalibration of Calorimeter layers a/o cells (Giulio,Claudio).

  • Studies on particular regions of the detector where the intercalibration deserve special attention:

    • generally all the ITC modules (Carlos,Shima?)
      • modules with small D4 attached to D5: EBA15 EBC18
      • modules with small D4: EBA14, EBA18, EBA19, EBC14, EBC15, EBC18
      • modules without C10 (only one scintillator slab is present due to interference with supports): EBA,EBC 39,40,41,42 55,56,57,58

    • modules with asymmetric cells (support of cryostat) A12,A13,A16: EBA,EBC 36,37,60,61
    • modules with damaged Cs tube (the first tile row cannot be scanned by Cs capsule): EBA 39,40,57,58

    • Scintillator slabs (E1-E4) (Shima)

  • comparison of cosmic response with TB results (Valerio?).
  • comparison with cosmics MC simulations
  • comparison with computed muon energy deposition
  • cross check of Intercalibration LArg-Tile?
  • Study of the alignement

Collection of Material

Presentations

TileCalWeek July08 plans updates

useful links

Atlas Cosmics Analysis Twiki

Data Preparation Reprocessing Twiki

list of processed Data Sets

2008 data, Spring-08 reprocessing, runs 90XXX and 91XXX, Magnetic field on (S+T), runs 92XXX have Toroid field off

data08_cosmag.00090262.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090264.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090270.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090272.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090275.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090345.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090413.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090525.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090731.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090732.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090733.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090749.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090755.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090757.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090758.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090784.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090786.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090792.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090793.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00090801.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091338.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091361.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091387.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091389.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091391.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091400.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091464.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091591.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091613.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091627.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091636.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091639.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091800.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091801.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091808.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091860.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091861.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091862.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091870.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091885.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091888.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091890.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091891.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091897.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00091898.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00092065.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00092069.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00092072.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00092074.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00092077.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00092078.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00092081.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00092082.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00092112.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00092160.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26
data08_cosmag.00092226.physics_IDCosmic.merge.DPD_SCTCOMM.o4_r653_p26

Cosmics MC simulation

valid2.108867.CosSimIDVolSolOnTorOn.recon.ESD.s540_d167_r676

Ntuple location

All the Ntuples are registered in dq2, please look for the latest version, for the data the output DS name is

user09.GiulioUsai.CosmicsAnalysis.data08_cosmag.XXXXXX.physics_IDCosmic.merge.
DPD_SCTCOMM.o4_r653_p26.version.6
With XXXXXX run number. A copy of the ntuples on my castor area is accessible from cern machines, this are about 200 files with 655K events, ~8GB:
nsls /castor/cern.ch/user/g/gusai/cosmics08

Some changes are expected and a newer version will be produced at some point. Please send comment/suggestions to me.

Also Ntuples with MC simulation were produced, you can access it with dq2, the dataset name is

user09.GiulioUsai.CosmicsAnalysis.valid2.108867.CosSimidvolsolontoron.recon.esd.s540_d167_r676.version.2
Problems finding this dataset were reported, it seems not available anymore. A copy of the ntuples on my castor area is accesible from cern machine, this are about 59 GB in 759 files.
nsls /castor/cern.ch/user/g/gusai/cosmics08MC

Description of Ntuple contents The Ntuples contain a limited set of info splited in few blocks:

  • track parameters of common use (defined at the point of closest approach)
  • track impact points on the different calorimeter layers; * the track is extrapolated in both direction, though a bug in the track extrapolation tools (under fixing) jeopardize at the moment the use of tracks in the upper part of the detector.
  • a road of cells within a distance dR <0.3 from the impact point above are saved on the ntuple;
    • cells in the LArg barrel are saved to study the intercalibration LArg-Tile.

A detailed list of variable follows, most of the name are self explanatory, the more important variable are explained in details, if you don't understand something please ask and then help improving the documentation...

  • Block with general info: run/event numbers, luminosity block, trigger type, etc.

    Int_t           RunNumber; 
    Int_t           EventNumber; 
    Char_t          StreamESD_ref[153]; 
    Char_t          Stream1_ref; 
    Char_t          Token[153]; 
    Int_t           Run; 
    Int_t           Event; 
    Int_t           Time; 
    Int_t           LumiBlock; 
    Int_t           BCID; 
    Int_t           LVL1ID; 
    Double_t        Weight; 
    Int_t           IEvent; 
    Int_t           StatusElement; 
    Int_t           LVL1TriggerType;
    vector<unsigned int> *LVL1TriggerInfo; 
    vector<unsigned int> *LVL2TriggerInfo; 
    vector<unsigned int> *EventFilterInfo; 
    vector<string>  *StreamTagName; 
    vector<string>  *StreamTagType;

LVL1TriggerType can be used to select only events in one particular trigger chain, here is the decoding (hex and dec): most of the events (~90%) in this DPD are from RPC and TGC Triggers.

       0x81 RNDM                          129 Random triggers 
       0x82 BPTX                          130  BPTX triggers 
       0x90 RPCwBeam                  144 any RPC trigger 
       0x88 TGCwBeam                  136 any TGC trigger 
       0x84 L1Calo                         132 any L1Calo trigger (EM,  
JET, TAU, XE etc.) 
       0xa0 MBTS_BCM_LUCID    160  MBTS, BCM and LUCID triggers 
       0xc0 CosmicMuons              192 Cosmic triggers 

  • Track parameters and other info defined at the point of closest approach
    UInt_t          NTracks; 
    vector<float>   *TrackPt; 
    vector<float>   *TrackP; 
    vector<float>   *TrackCharge; 
    vector<float>   *TrackEta; 
    vector<float>   *TrackPhi; 
    vector<float>   *TrackD0; 
    vector<float>   *TrackZ0; 
    vector<float>   *TrackPhi0; 
    vector<float>   *TrackTheta; 
    vector<float>   *TrackPIXELHits;    // number of hits in the pixels 
    vector<float>   *TrackSCTHits;      // number of hits in the SCT

    UInt_t          NCaloCells; 
    vector<float>   *CaloCellEnergy; 
    vector<float>   *CaloCellTime; 
    vector<float>   *CaloCellQuality; 
    vector<float>   *CaloCellEta; 
    vector<float>   *CaloCellPhi; 
    vector<float>   *CaloCellR; 
    vector<float>   *CaloCellX; 
    vector<float>   *CaloCellY; 
    vector<float>   *CaloCellZ; 
    vector<float>   *CaloCellDR;     // Cell length   R direction  
    vector<float>   *CaloCellDX;     //  empty 
    vector<float>   *CaloCellDY;     // empty    (not filled in our detector description since could  be inferred from the module extension in phi direction)   
    vector<float>   *CaloCellDZ;    //  Cell length Z direction 
    vector<float>   *CaloCellV;    // volume 
    vector<float>   *CaloCellCaloSample;  // samples 
  • CaloCellCaloSample: Calorimeter samples enumeration as defined in the Calocells, values saved on the ntuple are:
EMB1, EMB2, EMB3,     LAr   barrel               1 2 3 
TileBar0, TileBar1,  TileBar2,                //  Tile barrel                  12 13 14 
TileGap1, TileGap2, TileGap3,           // Tile gap (ITC &  scint)       15 16 17 
 TileExt0, TileExt1, TileExt2,           // Tile extended  barrel         18 19 20 
                                                
   vector<float>   *CaloCellSubCalo;     // (0==LARG-EM,3==TIle) 
   vector<float>   *CaloCellDirection;     // (+1,-1,-2) 

   * The  cell is associated  at  the extrapolation of track  along momentum(1)  the cell is associated in the  extrapolation opposite  to the 
momentum:-1, the extrapolation  on opposite momentum  fails: -2. (do not use) 


    UInt_t          NtrParamLayers;         //   Parameters of the  track at a given calorimeter layer  
    vector<float>   *TrackParamlayerEta;  // eta of the impact point  at a given layer.. etc... 
    vector<float>   *TrackParamlayerPhi; 
    vector<float>   *TrackParamlayerX; 
    vector<float>   *TrackParamlayerY; 
    vector<float>   *TrackParamlayerNumber;     // layer number == calo  sample as defined above 
    vector<float>   *TrackParamlayerDirection;   //  direction as defined above 
    vector<float>   *TrackParamlayerZ;

-- GiulioUsai - 28 Jul 2009

Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r9 - 2010-10-19 - GiulioUsai
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback