Calorimetry DetUnits for HCAL

1
CommonDet For Calorimetry

• CommonDet infrastructure classes common to
  Tracker and Muon packages
• Geometry navigation
• Handling SimHits, Digis, RecHits
• Why should Calorimetry use CommonDet?
• To allow navigation and track propagation
• To gain new functionality
• DAQ readout grouping
• Misalignment
• Track propagation
• To give ORCA a more coherent overall design

2
Mapping CommonDet to Calo

• Master Readout Unit for digis
• First try
• One for ECAL, one for HCAL, one for preshower
• Eventually
• Mimic the DAQ readout front ends
• DetUnit (implies one Slave Readout for digis)
• First try one per
• ECAL crystal
• HCAL tower
• Preshower plane
• Eventually
• one per 5x5 ECAL tower
• crystals would be channels within the readout

3
SimHits and RecHits

• PROBLEM Calo SimHits and RecHits are different
  than the ones used in Tracker and Muon.
• We cannot use CommonDets SimDet class, or the
  RecHit handling in DetUnit
• Maybe these need to be rewritten to be generic,
  templated on the SimHit or RecHit?
• We can use Calos old methods for now.

4
Digitization

• Old code digitizes entire subsystems at once
• Reasonable, because ECAL selective readout needs
  to know nearby crystals before deciding which
  ones to keep
• Reusing the old code wasnt hard
• Just had to factor some code out of the PRecDet
  class, because we get PRecDet from the Slave
  Readout
• Maybe HCAL towers (at least) should be digitized
  one-by-one, rather than all at once?
• Unrolling all those nested loops into reusable
  methods would be a good thing to do, anyway.

5
Current Status

• Done
• DetUnits and digitization infrastructure written
  (Rick)
• Implemented for HCAL (Rick) preshower
  (Vladimir)
• Doesnt get detector Bounds right yet, but not
  needed yet
• Old structure still works, too.
• Not CVS-committed yet, just sharing tarballs
• Near-term to do list
• ECAL
• Make DetLayer structures for navigation
• Make CaloItr use new readouts, so users wont
  notice the change
• Release into ORCA