@@ -7,7 +7,7 @@ description: "Simulation of the DESY testbeam setup with a EUDET telescope and R
This example is similar to the EUDET-type telescope example but with extra DUTs added to match the DESY testbeam setup with RD53a modules.
The setup consists of six telescope planes of MIMOSA26-type (EUDET beam telescope) and two RD53a modules centered in between the telescope arms:
DUT0 defined with 50×50um^2 pitch and DUT1 defined with 20×100um^2 pitch.
DUT0 defined with 50x50um^2 pitch and DUT1 defined with 20x100um^2 pitch.
Furthermore, one FEI4 reference plane is added as the last plane as in real testbeam setup.
The goal of this setup is to simulate the performance of RD53a modules with testbeam setup and to study multiple scattering effects with passive and extra material.
@@ -48,7 +48,7 @@ The cross-coupling matrix, to be parsed via the matrix file or via the configura
```
The matrix center element, `cross_coupling_11` in this example, is the coupling to the closest pixel and should be always 1.
The matrix can have any size, although square 3×3 matrices are recommended as the coupling decreases significantly after the first neighbors and the simulation will scale with N×M, where N and M are the respective sizes of the matrix.
The matrix can have any size, although square 3x3 matrices are recommended as the coupling decreases significantly after the first neighbors and the simulation will scale with NxM, where N and M are the respective sizes of the matrix.
## Usage
This module accepts only one coupling model (`coupling_scan_file`, coupling_file or `coupling_matrix`) at each time. If more then one option is provided, the simulation will not run.
where `<N>` is the current event number, `<PID>` is the PDG particle ID \[[@pdg]\], `<T>` the time of deposition, calculated from the beginning of the event, `<E>` is the deposited energy, `<[X-Z]>` is the position of the energy deposit in global coordinates of the setup, and `<V>` the detector name (volume) the energy deposit should be assigned to.
The resulting induced charge is summed for all propagated charge carriers and returned as a `PixelCharge` object. The number of neighboring pixels taken into account can be configured using the `induction_matrix` parameter.
## Parameters
*`induction_matrix`: Size of the pixel sub-matrix for which the induced charge is calculated, provided as number of pixels in x and y. The numbers have to be odd and default to `3, 3`. Usually, a 3×3 grid (9 pixels) should suffice since the weighting potential at a distance of more than one pixel pitch normally is small enough to be neglected.
*`induction_matrix`: Size of the pixel sub-matrix for which the induced charge is calculated, provided as number of pixels in x and y. The numbers have to be odd and default to `3, 3`. Usually, a 3x3 grid (9 pixels) should suffice since the weighting potential at a distance of more than one pixel pitch normally is small enough to be neglected.
