1. ORCA Calorimetry Software Status and Plans ORCA Core Calo group: Rick Wilkinson Andre Holzner Homer Neal Oct. 21, 2004 Robert asks, “As an example, are you planning on an interface that allows users to quickly access specific towers (CaloRecHits or EcalPlusHcalTowers) based on their location in the calorimeter (in eta and phi) and efficiently find their nearest neighbors?”

2. The way the geometry is currently organized: CaloBase CellProperties Represents a subsystem Indexed by integer HcalBaseEcalBarrelBaseEcalEndcapBasePreshBase 1 ~10,000

3. The way the geometry will soon be organized: CaloBase CellProperties Represents a subsystem Indexed by integer HcalBaseEcalBarrelBaseEcalEndcapBasePreshBase CaloDetType CaloDetUnit Info common to all cells in this subdetector 1 ~10,000

4. How the data is stored and accessed now CaloBase CellProperties PRecDet of CaloDataFrames CaloDataFrame … CellProperties User needs to loop over all data frames, find the cell index inside the data frame, And match it to the index of the cell in the CaloBase. CaloHits, CaloDataFrames, & CaloRecHits all do this.

5. How the data will be stored and accessed CaloBase Master Readout Each slave has a data cache, which means each CaloDetUnit holds its own data Master Readout handles persistency: stores the data in one big container fills the slaves when it reads data in. For CaloHits, the class is called “CaloSimDet” (implemented, not released) For CaloDataFrames, the class is called “CaloReadout” (implemented, not released) For CaloRecHits, “MasterRecDet” (implementing now) Should solve Robert’s problem to speed up jet finding. Slave ReadoutCaloDetUnit Slave Readout

6. Master Readouts CaloBase Master Readout We’re free to associate the SlaveReadouts with any MasterReadout we choose We might as well make a realistic DAQ configuration Currently, for HCAL, we’re using one readout = 20 o sectors in  plus one for each HF easy to change. Please send me mail telling what we should use! Slave ReadoutCaloDetUnit Slave Readout Master Readout

7. Status:

8. What the Customers Want: EcalPlusHcalTowers (Fermilab LPC): –Even simple tasks like finding a neighboring tower are slow and cumbersome: –No easy way to find the HCAL tower associated with the EcalPlusHcalTower. –Then need to find the neighboring HCAL tower, and then loop over every Tower in the RecCollection to find the one they want. –Navigation –They don’t like the north-south-east-west syntax –They