Presentation is loading. Please wait.

Presentation is loading. Please wait.

ECAL Digitization in CMSSW: Philosophy  Try to reuse code as much as possible between systems  ECAL, HCAL, Preshower? CASTOR?  Keep things as simple.

Similar presentations


Presentation on theme: "ECAL Digitization in CMSSW: Philosophy  Try to reuse code as much as possible between systems  ECAL, HCAL, Preshower? CASTOR?  Keep things as simple."— Presentation transcript:

1 ECAL Digitization in CMSSW: Philosophy  Try to reuse code as much as possible between systems  ECAL, HCAL, Preshower? CASTOR?  Keep things as simple as possible  Avoid big inheritance trees  Don’t get carried away with templates!  Tempting: DataFrames & DetIds are specialized now  EBDataFrame, EEDataFrame  HBHEDataFrame, HODataFrame, HFDataFrame  EBDetId, EEDetId, HcalDetId  Interface for changing conditions  Geometry  Pedestals & gains

2 ECAL Digitization in CMSSW EcalSimProducer CaloTDigitizer CaloHitResponse EcalCoder EcalPedestals EcalSimParameterMap Geometry Conditions Hits Digis

3 CaloHitResponse Adds up analog signals from Hits Same code for all subsystems è è Input: r r Calo Sim Hits r r List of Active DetIds è è Subdetector-specific parameters: r r Shaping function r r Hit correction, to do attenuation or delay r r Some parameters (see next slide) è è Output: r r Analog signals (CaloSamples)

4 Sim Parameter Maps Readout-cell-specific parameters, accessed by DetId (although in practice constant for all cells now) è è Photomultiplier gain: r r converts SimHit energy to avg. # of photolectrons è è Amp gain: r r from photoelectrons to units of analog signal è è Sampling factor r r Fraction of incoming energy absorbed u u 1 for ECAL, only relevant for HCAL è è Timing phase adjustment è è Readout frame size è è Time bin of signal maximum è è Whether or not to do Poisson photostatistics è è Nominal calibration constant r r Sampling factor / Photomultiplier gain / amp gain

5 ECAL Coder u Needs to know pedestals to use: è Producer can read them from conditions DB, if requested è Can use Shahram’s Conditions DB interface now u Why should simulation use real gains & pedestals? è Other experiments do è Makes for realism r Hot channels are hot r Noisy channels are noisy u Try to keep things simple è Producer fetches conditions, and passes to algorithms è Avoid software dependence on databases.

6 Status: u WORKING: è Running from files of CMSSW hits è Running combined G4 + digitization jobs u To do: (along with experts) è Trigger Simulation è Selective Readout è Integrate with Shahram’s reconstruction


Download ppt "ECAL Digitization in CMSSW: Philosophy  Try to reuse code as much as possible between systems  ECAL, HCAL, Preshower? CASTOR?  Keep things as simple."

Similar presentations


Ads by Google