IFAEAtlasAnalysisEV

Introduction

Collection of useful information abour EV for IFAE members. So far mainly oriented towards application. Please add info general about EV philosophy if you like.

• Abbreviations for the paths
  • EV means here the current EV path, e.g. /afs/cern.ch/atlas/groups/PAT/Tutorial/Atlas.EventViewGroupArea/EVTags-11.0.5.16/PhysicsAnalysis/Atlas.EventViewBuilder/
    • ..most of the interesting stuff is in ./Atlas.EventViewAtlas.UserData/
  • SusyView means your current Susyview path, e.g /11.0.5/PhysicsAnalysis/SUSYPhys/SUSYView/SUSYView-00-00-13-06/
    • Configuration of individual EV modules from Susyview is done via python scripts in SusyView /python directory
  • TopView means your current Topview release

General Event View philosophy

• This chapter has to be extended. So far we refer to the general introduction into the

Atlas analysis model

Extracting detailed variables from AODs:

• The source code for the module is in EV ./Atlas.EventViewAtlas.UserData/ . It can configured from SusyView python scripts like DetailBlaBlaInfo.py
  • Example Muon:
    • The source code for the module is in EV ./Atlas.EventViewAtlas.UserData/Atlas.EventViewAtlas.UserData...../src/EVUDMuonAll.cxx
    • It is configured in SusyView via DetailMuonInfo.py
• Levels of detail: Susy View uses LevelOfDetailMu, LevelOfDetailEl etc from SimpleUserDataDump by default in the nearly-top job-options file SUSYViewRecoAOD_jobOptions.py ).
  • SusyView example:
    • Level Of Detail==0 : kinematic quantities
    • Level Of Detail==1 : Full dump of AOD variables
      • for information look into AOD keys page or into the pages of the physics groups
      • Examples:
        • Eletron class reference
        • Combined Muon in the ESD
    • Level Of Detail==2 : additional connections to other objects, e.g. association with Cal clusters

Inserting variables into the AAN

• Source code in EV ./EventViewInserters/EventViewInserters-00-00-01-11/
  • Example Muons: ./EventViewInserters/EventViewInserters-00-00-01-11/src/EVMuonInserter.cxx
• Can be configured directly from the top job Options
  • Susyview Example (configurables, new style): see also SusyView
    • from EVToolLoopers import *
    • defaultEVLooper = EVMultipleOutputToolLooper("defaultEVLooper")
    • theJob + = defaultEVLooper
    • toInsert = ["Electron", "Photon", "Muon", "ParticleJet", "MissingEt", "EventInfo"]
    • defaultEVLooper + = EventView("Inserters", toDo = toInsert)
    • defaultEVLooper.Inserters.ElectronInserter.etCut=30*GeV

Truth-to-reco match

• Simple default match in Susy View: Class ElectronTruthToRecMatch etc.
  • Configured in SusyView:
    • Example electrons: ElectronTruthToRecMatch.py (What is ElectronTruthToRecInfo.py doing ?)

Tips

• Do not use full paths for athena aware ntuples. Somehow, during the production of the ntuple, its path is written with its content, so that if this file changes its address in the future you will get crashes when reading it via root.
  Therefore, try to specify always local paths, when writing and reading athena aware ntuples.

---

Major updates:
-- UllaBlumenschein - 11 Jan 2007

%RESPONSIBLE% Main.unknown
%REVIEW% Never reviewed