The geometry consists of the vertex detector (VD), the electromagnetic calorimeter (EM), and the muon identifier (MU). Detector layout along the Z axis.
VD consisted of 3 layers of Si with pads structured along the X axis. Between VD and EM there are 2 active absorbers (scintillators). EM is the matrix 5x5 of heavy crystals. MU consist of 2 active absorbers (scintillators) and the iron plate between.
2 regions additional to the World are defined: VertexDetector and MuonDetector. For testing purposes first absorber of MU is included in the region of VD.
Material of calorimeter and absorber can be choosen:
Air Water lAr Al Fe BGO PbWO4 Pb.
Eg:
/testem/det/CalMat PbWO4 /testem/det/AbsMat Al
The size of the detector can be changed also.
Eg:
/testem/det/EcalLength 20 cm /testem/det/EcalWidth 5 cm /testem/det/update ---> rebuild the geometry
Physics Lists are based on modular design. Several modules are instantiated:
The following options for EM physics using builders from physics_lists sub-package are available:
A local builder, PhysListEmStandard "local" (similar to opt0) is also available.
Optional components can be added:
The primary kinematic consists of a single particle which hits the cylinder perpendicular to the input face. The type of the particle and its energy are set in the PrimaryGeneratorAction class, and can changed via the G4 build-in commands of G4ParticleGun class.
The batch regime of simulation can be started
$G4WORKDIR/bin/$G4SYSTEM/TestEm9 TestEm9.in
where TestEm9.in is the example of macro file for batch job.
As a result of simulation the number of secondaries produced in different regions are averaged. The average energy depositions in active absorbers and EM as well as RMS of these values are shown. The number of hits in pads of VD is printed out.
To use visualisation the environment variable G4_VIS_USE should be defined. An interactive session starts if no macro file is specified in the command line:
$G4WORKDIR/bin/$G4SYSTEM/TestEm9
To start visualisation one can issur
>/control/execute vis.mac >/run/beamOn 1
Number of histograms are built inside the example using internal analysis sub-package. Histograms are saved in a root file. Histogram booking and saving is done only if any of histogram
/testem/histo/fileName myname /testem/histo/setHisto id nbins xmin xmax unit