Skip to Content.
Sympa Menu

sphenix-software-l - [Sphenix-software-l] Thoughts about new CaloTower object to store Calorimeter Tower Information

sphenix-software-l AT lists.bnl.gov

Subject: sPHENIX discussion of software

List archive

Chronological Thread  
  • From: Nils Feege <nils.feege AT stonybrook.edu>
  • To: sphenix-software-l AT lists.bnl.gov, "phenix-ephenix-l AT lists.bnl.gov" <phenix-ephenix-l AT lists.bnl.gov>, EIC <eic AT stonybrook.edu>, PHENIX Forward Upgrades Next Decade <phenix-nextfor-l AT lists.bnl.gov>
  • Subject: [Sphenix-software-l] Thoughts about new CaloTower object to store Calorimeter Tower Information
  • Date: Wed, 29 Jul 2015 18:20:21 -0400

Dear all,

Chris, Jin and I had some discussion about common calorimeter tower objects in the software for all calorimeters, i.e. sPhenix barrel HCAL, Spacal, and the forward calorimeters for fsPhenix / EIC.

We'll have two slides and an opportunity for plenary discussion tomorrow 10 am at the sPhenix workfest:

https://indico.bnl.gov/conferenceDisplay.py?confId=1237

Here's what we came up with so far: Each sub-detector would keep its own implementation up to the tower builder code. The output of these individual tower builders will be generic tower objects (CaloTower, see below). This would allow downstream code (clustering etc) to run on towers independent from the calorimeter they came from. In other words, these tower nodes are junctions where the independent simulation / reconstruction for all calorimeters can converge.

We plan to test this with the forward calorimeters first (and SPACAL and HCAL later if it works smoothly). Here's a list of the classes we plan to implement:

- CaloTower: A new base tower class which will represent a tower and have parameters like TowerID, Energy, Time(?) and respective Get functions (it will replace the RawTower class).

- CaloTowerv1: Inherits from CaloTowerv1. This is how tower information will be stored on the node tree. The idea is to keep this tower information general so it would have the same information and functionality for Simulation and Data.

- CaloSimTowerv1: Inherits from CaloTowerv1 and adds additional information that would only be available for simulated events.

- CaloTowerContainer and CaloTowerContainerv1: Store multiple CaloTower and retrieve them by TowerID or iterator.

- CaloGeometry: Provides center position x,y,z and size for each TowerID. Will be created on the fly (either from mapping files or later from TGeo object) and is therefore NOT stored in the output file.

I'll work on implementing and testing this in the next couple of days.

Best,
Nils

--
Dr. Nils Feege
Research Associate

SUNY at Stony Brook
Department of Physics & Astronomy
Stony Brook, NY 11794-3800

skype nils1920
phone +1-631-632-8112



Archive powered by MHonArc 2.6.24.

Top of Page