------------------------------------------------------------------- ========================================================= Geant4 - an Object-Oriented Toolkit for Simulation in HEP ========================================================= Example HGCal_testbeam ---------------------- This example is based on the Geant4 standalone application developed by Thorben Quast for the CMS HGCal studies: https://github.com/ThorbenQuast/HGCal_TB_Geant4. The goal of this example is to demonstrate a test beam setup used in HEP experiments, and as a base for the validation studies and comparison with experiment data. It presents a test beam setup used in the HGCal studies in October 2018. It can be easily extended to other configurations. Details on the High Granularity Calorimeter (HGCal) can be found i.a. in the Technical Design Report: https://cds.cern.ch/record/2293646/files/CMS-TDR-019.pdf 1. Detector description ----------------------- Detector construction in this example assumes that the setup is constructed with different elements placed one behind another along z axis (beam axis). There are 3 configurations user can choose from, and could be set with UI command: /HGCalTestbeam/setup/configuration where by default is equal to 0, which means the HGCal testbeam setup used in October 2018. 1 builds the same calorimeter setup, but places in front of it several beamline elements. 2 builds a very simplistic test configuration. Whenever a silicon wafer or SiPM is placed in the detector, a sensitive volume is attached to it, and will be used to collect signal. Silicon wafer is divided into cells (pixels), and each individual pixel can collect signal. In order to change the maximum step size allowed in silicon pixels: /HGCalTestbeam/setup/stepSilicon where is value of the max step size in micrometres. By default is equal to 30 um. 2. Signal --------- Energy deposited within silicon pixels and SiPMs is registered in the sensitive detectors. Each deposit is added individually to the vector of hits, in order to allow the digitisation. Digitisation is performed at the end of the event. It accumulates the energy deposits within pixels, taking into account the time cut on the arrival of signal (global time of energy deposit). By default no time cut is applied which means all the deposits are counted. It can be set using UI command: /HGCalTestbeam/hits/timeCut