Tile Calorimeter: Reconstruction Status

1. Tile Calorimeter:Reconstruction Status Frank Merritt University of Chicago May 13, 2002

2. TileCal Reconstruction Status, Dec ‘01 • TileRec package (A. Gupta, E. Frank, F. Merritt, A. Solodkov) • TileCell, -Tower, and -Cluster Classes created from G3 digits • TileCell (like LArCell) inherits from CaloCell. • JetRec package (A. Gupta, E. Frank) • Jets are made from ProtoJets • Protojets are made from CaloCells, -Towers, or -Clusters. • Three different jet-finding algorithms: • Seedless cone algorithm • Kt algorithm • Sliding window algorithm

3. TileCal Reconstruction Status, Jan ‘02 • New Navigation package(Ed Frank) • First proposed summer 2001, presented at SW workshop in September 2001 (see talk by E. Frank in that workshop) • designed to allow decomposition of Jet into constituent cells, towers, clusters. Separates navigable structure (representational domain) from behavior (OO domain). • used by A. Gupta to develop Jet reweighting algorithm, and by F. Paige in studies of H1 reweighting in taujet. • User feedback welcome (especially from other applications and other systems).

7. Recent changes • Bug fixed in TileID for Gap cells (A. Solodkov) • TileID and TileRange classes improved (AS) • Define TileHWID and map (AS) • Port to Solaris (Zhifang Wu) • Persistency(ADL) of TileCell class (T. LeCompte)

8. New Projects Underway: April 2002 • Preparing for Conditions DataBase (EF, TLC, and FSM). • Defining what conditions data will be needed, and how it will be represented as objects in Transient Detector Store (EF, TLC). • New class TileInfo has been written (preliminary version by FSM) to provide access to information such as number of time slices, calibration constants, etc. This provides a single interface for this kind of information. • Ed Frank is working on improving structure and providing initialization. • Defining and constructing new classes and algorithms corresponding to the steps of the detector and electronics evolution of data processing. • Consistent with LAr structure, although the details of implementation and classes are different:

9. Tile Data Objects Tile Algorithms TileDeposits (local energy dep in scint) TileOpticalSimAlg TileHit (signal seen by PMT) TileElectronicSimAlg TileDigits (with time struct. and noise) TileOptimalFilter TileRawChannel (after optimal filtering) TileCellMaker TileCell (calibrated cell energy)

10. Work in Progress: April 2002 • Move to new D.Q. package structure. • This separates algorithms from data objects. • transition has been completed for version 3.1.0. (May 2, 2002). • Write new classes for Digits, RawChannel, etc. • This has been completed for TileHit, TileRawChannel; work on TileDigits is under way. • Use ADL to make classes? This will make conversion process (for new persistency mechanism) automatic. Will add this over the summer.

11. Work in Progress: April-May 2002 • Modify algorithms for conversions. • This has been completed for • G3 -> TileHit, • TileHit -> TileRawChannel, and • TileRawChannel -> TileCell. • Work on TileHit -> TileDigits is in progress, to be completed this week. • Interesting note on normalization: • In transforming from TileHits to TileRawChannels, found that many of the cells we have been “reading out” from MC files give an amplitude of less than 1 ADC count in high gain (!). • Should have a working version this week (May 15). • Shaping and noise to be worked on after than. • Then move optimal filtering algorithms from test-beam work, further development offline.

12. ROD output and optimal filtering • In normal ATLAS running, how much analysis on the time samples should be done in the ROD and how much offline? • Doing this in ROD reduces required bandwidth (?) out of ROD but limits what one can study offline. • It may be that reading out all of the the digits (8 time slices) takes no more space than energy/time/quality. • Can we keep all digit information ONLY for those channels that show non-trivial time-structure? Probably so. This is (?) under discussion within TileCal.

13. What Still Needs to be Done? • A lot! • Tile work plan and milestones are given on TileCal software web pages http://tilecal.web.cern.ch/tilecal/documents/General/swplans.txt • Greater involvement in software is needed by Tile, and needed by ATLAS in general. Physicist involvement is important for maintaining the push needed to meet decision, make milestones, use DC data, etc. • Reading out testbeam data within Athena seems like an important milestone. Currently, target date is Dec 2002. Should this be moved up? Who is interested in working on this, or on using it? Work could begin next month.

14. What Still Needs to be Done? • Tile software biweekly telephone conferences: • Wednesday 10:00 am CST, next meeting May 15. • There is significant Tile involvement in JetEtMiss group, biweekly telephone conferences (with minutes): • Wednesday 10:00 am CST, next meeting May 22. • This is a good time to get involved in Tile sw, in Combined Performance Groups, or in Physics Groups. • There is a lot of progress in software, and an emphasis on meeting the Data Challenge goals now underway.

15. What is the best way to get started? • Get help! (Me, Ed, Ambreesh, Tom, Sasha, etc.) • Documentation is not great, but there are some useful links: • Getting started (setting up software environment):http://atlas.web.cern.ch/Atlas/GROUPS/SOFTWARE/OO/tools/cmt/primer/index.html • Tutorials (I will try to add others here): • http://hep.uchicago.edu/atlas/software/reference/ • Web pages for TileCal (software), JetEtMiss (see links from ATLAS home web page.