Status report for LVL2 e/  ESD/AOD

1. Status report for LVL2 e/ ESD/AOD Aims and constraints Tracking status Calorimetry status (Monika) Monika Wielers Ricardo Gonçalo

2. Aims and Constraints (shown at PESA mtg Dec.04) • LVL2 e/ variables currently available in the CBNT • The aim is to store this information at the AOD/ESD level: need persistified objects • AOD level: • Should be only minimal info about trigger menus satisfied (EF only or L2+EF?) • AOD should be obtainable from ESD • Worry about it later • ESD level is the top priority: • LVL2 e/ information would allow trigger studies using large data samples produced for Rome • How to do it? • First approximation is to use available offline objects: TrackParticle, EMShowerMinimal, CalCluster (linked from EMShowerMinimal) • Tracks can be converted by existing TrigToTrkTrackTool switched on through job option; must check it out (thanks to John Baines) • Real data is a separate matter due to space/bandwidth: need L2/EF fragments of ~1kByte for real data (i.e. ~1MByte/s for 1kHz accept rate) ATLAS UK HLT e/gamma meeting

3. The story so far… • Christmas and brain reset… • Trying to use existing offline objects as much as possible • Concentrating on ESD level for now • TrackParticle class: machinery should “all” be there • EMShowerMinimal: needs persistification • Other issues: • Level 1: work done by Tadashi Maeno so far: RoI builder result and CTP decision, no info on ET, , , isolation (should be there for release 10) • Perhaps workaround for filling missing classes directly instead of going through bytestream, but classes should be “final” • Discussion on LVL1 has started with Alan Watson • CBNT production for trigger tuning • Dependencies on Trigger and Offline code ATLAS UK HLT e/gamma meeting

4. Tracking • TrackParticles can in principle be persistified with no extra machinery • Built from vector of Trk::Tracks plus extra bits • Existing ParticleCreatorTool creates TrackParticle from Trk::Track ATLAS UK HLT e/gamma meeting

5. Tracking • Trk::Track: vectors of TrackStateOnSurface and RIO_OnTrack plus extra bits • Existing TrigToTrkTrackTool (Dimitry) can be used to convert L2 tracks to Trk::Track ATLAS UK HLT e/gamma meeting

6. Status of LVL2 track persistification • So far: • Painful process of getting things to work and understanding what is/isn’t working, also because documentation is scarce (to find what tools exist) • Checked that Trk::Track’s are being created • Had to remove SiTrack from HLTsequence.xml • About to check the TrackParticle creation • Then: • Store TrackParticles in ESD (“should work”…must check) • How should the code be packaged? • Dependencies? ATLAS UK HLT e/gamma meeting

7. Status of LVL2 Cluster Persistification • Need to persistify cluster and shower shape quantities • Stored in EMShowerMinimalContainer and CaloClusterContainer • link to CaloCluster from EMShowerMinimal object • To write it into ESD one needs to do the following • Add EMShowerMinimalContainer to list of objects to be stored in ESD • CaloClusterContainer stored automatically due to link from EMShowerMinimal • Some code changes in EMShowerMinimal needed for navigation • Add EMShowerMinimal to pool dictionary • Create pool converter for EMShowerMinimal • done automatically when pool dictionary is created ATLAS UK HLT e/gamma meeting

8. Status of LVL2 Cluster Persistification • All this is done • Was very painful • due to missing documentation • Working blindly without really knowing how all this works • Every iteration (compile and run) takes at least 10min • Constant interaction with Ketevi who’s at BNL • Now I can read back EMShowerMinimal and CaloClusters correctly • However, the direct link from EMShowerMinimal to CaloClusters does not work yet properly, problem due to change to Elementlinks • Caveat: to get it running new dependencies on trigger code had to be done to allow navigation ATLAS UK HLT e/gamma meeting

9. Next steps • Continue work on persistifying TrackParticles • Continue discussions on needs for LVL1: if needed, implement classes, to get going • Worry about technical issues like additional dependencies in trigger code • Add algorithm to fill CBNT ntuple as done right now • Has to cover LVL1/LVL2/offline/Truth • Everything has to be ready for release 10 (Feb. 23) ATLAS UK HLT e/gamma meeting