AOD Data in Atlantis Event Display Qiang Lu, Juergen Thomas, Peter Watkins (Birmingham) Hans Drevermann (CERN) Andrew Haas (Columbia) Eric Jansen, Pieter Klok, Charles Timmermans (Nijmegen, NIKHEF) Simon Dean, Nikos Konstantinidis, Zdenek Maxa (UCL) Physics Analysis Tools Group Meeting ATLAS Software Week, CERN, 5 Apr 2006

Atlantis with AOD data, 5 Apr Outline Display of AOD data:  Data types  Data in GUI: Properties and cuts  Projections: XY, eta/phi and Legoplot Trigger data (preparing for AOD) More news from Atlantis Appendix: Wiki link, Producing xml output from AOD files within Analysis tools: AnalysisSkeleton, UserAnalysis, EventView NOTE: Shown features are in Atlantis versions from AtlantisJava

Atlantis with AOD data, 5 Apr AOD Data in GUI (1): Types and Switches AOD data which was already in Atlantis:  Missing-ET is selected in Data -> ATLAS from drop-down menu (uses new ‘multiple collections’ infrastructure) ETMis (MET_Final) CaloETMis (MET_Calib) MuonETMis (MET_Muon)  Tracks (TrackParticle) (Note that AOD tracks have reduced data) Truth:  Read from McEventCollection GEN_AOD Separated in neutral and charged truth: SNP: Neutral Truth STr: Simulated Tracks (incl all charged particles !) Switched in Data -> InDet and Data -> Calo Note: pT-Cut taken from Cuts -> InDet applies to –all- Truth objects  In projections: Red ‘V’ in eta/phi projections, and red lines in XY projection

Atlantis with AOD data, 5 Apr AOD Data in GUI (2): Types and Switches In addition, the following AOD data are now displayed:  Electron (ElectronCollection)  Muon (MuidMuonCollection)  BJet (BJetCollection)  ParticleJet (Cone4TowerParticleJets)  Photon (PhotonCollection)  TauJet (TauJetCollection) All Storegate keys can be switched in jobOptions if wanted (e.g. to get KtTower jets. See Wiki page) Switch on/off in ‘Data’ panel

Atlantis with AOD data, 5 Apr AOD Data in GUI (3): Colour and Widths AOD data colours and line widths can be changed in ‘AOD’ panel. Default colours are:  BJet: dark blue  Electron: green  Muon: red  ParticleJet: (slim) grey  Photon: yellow  TauJet: light blue

Atlantis with AOD data, 5 Apr AOD Data in GUI (4): Cuts A ‘reasonable’ set of default cuts is applied, freely adjustable by the user:  All: pT > 5 GeV  BJet: lhSig > 0.9  Electron: isEM=0 (note: we fix 2048 bug inside, set to 0)  Muon: chi2 < 0 (this is ‘matchChi2OverDoF’)  TauJet: isolationFraction > 0.3, logLhRatio > -2

Atlantis with AOD data, 5 Apr XY Projection (1) AOD objects are displayed outside of the detector as small towers (1 degree width) Zoom and Pick to inspect objects Height has a cut- off value at pT/ET = 100 GeV (maximal height) All Events shown are semileptonic ttbar (mc11 T1 sample)

Atlantis with AOD data, 5 Apr XY projection (2) Muon ParticleJet (also a BJet ! Note slim dark blue frame)

Atlantis with AOD data, 5 Apr XY Projection (3) Fisheye used: ‘visual track matching’ possible PICK output: InDet: Track = 15 storegate key: xKalTrack d0 =.002 cm z0 = cm phi0 = η =.040 tL =.040 pT = p = GeV AOD: Electron = 1 Pt = GeV E = GeV isEM = 0 eOverp = η =.040 Φ = ° Truth: STr barcode = 118 Type = e- d0 = cm z0 = cm phi0 = η =.041 tL =.041 pT = p =

Atlantis with AOD data, 5 Apr AOD display: eta/phi Projection AOD objects are circles:  An ‘x’ marks the centre position  scaled with their pT (resp. ET for Jets)  Note: Circle is not jet cone ! Circles are a first implementation, this may change. ‘Pick' on any AOD object to print-out parameters A ParticleJet which is also a tagged BJet will be a dark blue circle with slim grey circle on top.

Atlantis with AOD data, 5 Apr Missing ET in eta/phi Projection ETMis: storegate key: ETMis Sum-ET = GeV ET-Mis = GeV ETx-Mis = GeV ETy-Mis = GeV Φ = ° ETMis: storegate key: CaloETMis Sum-ET = GeV ET-Mis = GeV ETx-Mis = GeV ETy-Mis = GeV Φ = ° ETMis: storegate key: MuonETMis Sum-ET = GeV ET-Mis = GeV ETx-Mis =.002 GeV ETy-Mis = GeV Φ = ° Select Missing-ET type from ‘ATLAS’ -> ‘ETMis’ -> ‘ETMis Collections’ (Multiple Collection). Default is ETMis (MET_Final)

Atlantis with AOD data, 5 Apr SynchroCursor (SC): eta/phi matching

Atlantis with AOD data, 5 Apr SynchroCursor PICK output: Muon = 0 Pt = GeV E = GeV chi2 = η = Φ = ° BJet = 1 Pt = GeV E = GeV lhSig = weight = η = Φ = ° STr barcode = 75 Type = μ- d0 = cm z0 =.140 cm phi0 = η = tL = pT = p = GeV ETMis: storegate key: CaloETMis Sum-ET = GeV ET-Mis = GeV ETx-Mis = GeV ETy-Mis = GeV Φ = °

Atlantis with AOD data, 5 Apr Legoplot: AOD Colour coding, cuts and data selection as explained above. All Jets are circles on the base plane of the legoplot (size adjustable), the others data are narrow towers Missing-ET is a narrow tower at the border On picture: High-pT muon Event is a semileptonic ttbar (mc11 T1 sample)

Atlantis with AOD data, 5 Apr Legoplot: Calo data from Digi/ESD (1) Note: This plot is from Digi (!) AOD in have no calo cells AOD objects described before are not produced by default when using doJiveXML=True currently. But can be switched on. Picture shows calo data by calo type: electromagnetic: green, hadronic: red Grey disks on base are ESD Jets

Atlantis with AOD data, 5 Apr Trigger data: Level1-Trigger Towers Produced using doTrigger=True Geometry (Grid) as in real system (Barrel: 0.1x0.1, much larger in FCAL) Trigger data from Digi/ESD (1)

Atlantis with AOD data, 5 Apr Level-1 Jet Elements Added up over em and had (neutral colour: yellow) Geometry (Grid) as in real system (Barrel: 0.4x0.4) Visible also: red rectangle on Legoplot base: This is an RoI. Atlantis shows JetRoI, EmTauRoI Next: Add more trigger data, also HLT (CTP_Decision, TriggerDecision) Trigger data from Digi/ESD (2)

Atlantis with AOD data, 5 Apr More news from Atlantis Many improvements made in view of usage of Atlantis for InDet commissioning:  Geometry now taken from Athena (Muon, Calo)  Multiple Collections for Tracks  Interactive Running (Vertexing) New XML Parser JiveXML: Various adjustments to changes in Offline software

Atlantis with AOD data, 5 Apr Summary Most AOD objects can now be viewed in Atlantis. Instructions for running in the most popular analysis tools are available on Wiki Cuts and switches can be applied to the user’s preference AOD data is displayed in eta/phi, XY and Legoplot projections. Soon also in rho/Z. Tried and tested with mc11 (CSC) pre-production in Atlantis section in PAT tutorial this Thursday Please send comments, questions and suggestions to

Atlantis with AOD data, 5 Apr Appendix: Technical details and instructions

Atlantis with AOD data, 5 Apr Producing output in (1) Instructions collected on Wiki page: JiveXML version in is not producing XML output for most AOD data, therefore you need to update that package. To run with , do: cmt co -r JiveXML graphics/JiveXML (config and gmake as usual) is fine, contains JiveXML already. Add this to your analysis package’s ‘cmt/requirements’ (probably not needed ?) use JiveXML JiveXML-* graphics

Atlantis with AOD data, 5 Apr Producing output in (2) To produce xml output in analysis based on AnalysisExamples, to your jobOptions, e.g.after 'EvtMax' within AnalysisExamples/ZtautauExample_jobOptions.py add: add those lines to call and adjust JiveXML: include( "JiveXML/JiveXML_jobOptionBase.py" ) include( "JiveXML/DataTypes_AOD.py" ) ToolSvc.EventData2XML.Muonkey = "MuidMuonCollection" include( "JiveXML/DataTypes_Reco.py" ) In case your analysis is based on UserAnalysis, do the the same within UserAnalysis/AnalysisSkeleton_jobOptions.py Run job options as normal, output in xml format will be dumped

Atlantis with AOD data, 5 Apr Interface calling JiveXML is available from TopView package (Akira): PhysicsAnalysis/TopPhys/TopView/python/ EventViewToJiveXML.py JiveXML is called in TopView/share/ttBarAnalysis_jobOptions.py by XMLSaver=EventViewToJiveXML(ttbarEVLooper, "XMLSaver") XMLSaver.setParameters({"EV2XML":{"CutName":"tt_TightCut"}}) Producing output in (3): EventView

Atlantis with AOD data, 5 Apr Up-to-date Atlantis Website has plenty of documentation & tutorials: The latest Atlantis version is now available from the Offline releases (package graphics/AtlantisJava): cmt co –r AtlantisJava graphics/AtlantisJava cd AtlantisJava-*/cmt cmt config source setup.sh gmake cd.. java –jar atlantis Don’t use alias ‘atlantis’, this will start old version in release. If you have a. Atlantis-config.xml, you may need to rename it. Running under Windows / Mac as a java application works (may require installing Java 1.5 SDK) Copy directory ‘AtlantisJava-*’ from release, start atlantis.jar Note: Although Atlantis is inside the release, it has no dependency on other packages. It is a Java standalone application. Inclusion into release only to simplify distribution and code management.