1. CALORIMETRY SOFTWARE: Rick Wilkinson April 2005

2. Release Of Calo + CommonDet ● Trying to get it into ORCA_8_9_0 ● Will have: – Master/Slave readouts – Full backwards-compatibilty, both code and data – Cell-by-cell digitization – Support for HCAL calibration – Lots of cleanup/refactoring/bug fixes ● Will not have: – Testbeam support (important) – Cell-by-cell RecHit building (important) – Supercrystals (needed?) – Tracker-style navigation (needed?)

3. BUGS: CRYSTALS IN ECALPLUSHCALTOWERS ● Robert Harris found a serious bug: EcalPlusHcalTowers don't always get 25 crystals! – Crystals get assigned to the nearest HCAL tower, based on position ● How can we fix? – Smarter algorithm? – Explicit mapping ● XML mappings discussed later Tower Max Num Crystals 1 25 2 25 3 25 4 25 5 25 6 20 * 7 25 8 30 * 9 25 10 20 * 11 25 12 30 * 13 25 14 20 *

4. BUGS: TRIGPRIMS ● Philippe found that TrigPrims always run after digis, so after digi zero-suppression! ● Fixed in DetUnits HEAD, and a big motivation to get this version released. ● Not totally dummy-proof, though. – Nothing stopping you from making zero- suppressed digis, then running TrigPrims.

5. BUGS: SELECTIVE READOUT SETUP ● Setup dependencies are too fragile! SelectiveReadout needs EcalBarrel, EcalEndcap, and EcalTower to be there before it's built. – Doesn't work otherwise, maybe because EcalBarrel/EcalEndcap depend on EcalTower, too? Not sure. ● Works if you wait as long as you can before building the SelectiveReadoutTowerMap. Wait for events to start coming in. – Singleton, so overhead should be negligible – Fixed in release, HEAD. ● Vincenzo says the right way to do it is to make everything a LazyObserver, with check()s in every public method! – Should we bother, or just limp along until the EDM rewrite?

6. NEW FEATURES: INDIVIDUAL DIGITIZATION ● Implemented a mechanism to digitize cells one-by-one – Performance 50% slower than CaloBulkDigitizer. Not sure why. – Refactored CaloFrontEndResponse, so will break some test programs. ● Some complications in HCAL Because of ganged channels, some active volumes don't have readouts. Those channels are no longer DetUnits CaloHitLoader moves hits to correct active volume Not done yet for CaloRecHits, where it would be really useful

7. NEW FEATURE: Decoupling ECAL & HCAL ● ECAL Geometry loading is slow, so we need a way to run HCAL jobs without ECAL & vice versa. ● Coupling comes in two places: – Setting up SelectiveReadout for DataFrames & RecHits ● Solved for DataFrames by moving setup into EcalSelectiveReadout library ● Not solved for RecHits, because it might make sense to redo RecHits in CommonDet style first – CaloTrigRec library, which sets up EcalTrigPrim & HcalTrigPrim ● Solved by eliminating CaloTrigRec library, and moving setup into EcalTrigPrim & HcalTrigPrim

8. CALIBRATION – First of all, ORCA code needs an interface to accept and use the appropriate constants – HCAL required rewrite of the whole digitization procedure! ● Can this be done for ECAL? – HCAL Solution inappropriate for ECAL ● HCAL has only two constants, ECAL has six ● Requires me to make some code changes – Trying to get an actual test case, using testbeam data, has been hard. ● Need to fix testbeam reading in DetUnit-based Calorimetry ● Need to define CMS's interface to databases! – CERN/POOL people like generic objects, POOL:AttributeList – Fermilab people like strongly-typed objects, with automatic code generation. – Vincenzo has an EDM design, which everyone seems to like.

9. HCAL GEOMETRY ● Sunanda made some realism fixes to newest prerelease: – Needed for testbeam – Made depth segmentation more realistic – Fixed incorrect eta boundaries – Seems like this will break old datasets! ● I'm moving HCAL DDD parsing out of ORCA, into common routines he provided in Profound. ● Also, I'm trying to reorganize the HCAL geometry into some regular structures. – Requires rewriting HCAL navigation – Complications at overlap of HE & HF HcalTowerType etaMin etaMax nDepthSegments depths nPhiSegments

10. EcalPlusHcalTowers and HO ● JetMET people find that the outer HCAL layer shouldn't be used on most towers, because it just adds noise. It should only be used as a tail-catcher for high energy deposits – Same electronics as other channels, but amplified by the lower sampling factor of the detector itself ● This requires adding a field for HO energy in the EcalPlusHcalTower class. – Modifies schema! – Vincenzo says ROOT/POOL can handle schema change ● I need to test this – Tony says no re-running production, though.

11. ECAL Endcap Trigger Tower Mapping ● Currently in flat file ● ECAL experts (Seez, Baffioni, Berthon) point out that it really should go in DDD/XML ● Vladimir has a prototype already! ● Good to have an example for our other mapping problems – EcalPlusHcalTowers – Electronics (see next slide)

12. Electronics Mapping ● How do testbeams define which cell goes with which readout in the electronics? ● This information needs to go in ORCA – Would be used immediately for mapping CommonDet's MasterReadouts cells ● How should we implement? – Eventually will be in the configuration database – Michael Case says it would be easy to put this information into an SQL Lite DB, and used in all ORCA jobs. – Or should we go with flat file? XML? – Volunteers?

13. EDM ● Jeremy Mans has come up with a design for how Calo data will be stored/handled in new EDM. ● Pretty urgent. Slice test coming up! ● Document being written