You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[ITS3] Update default parameters and adapt code to work with fourth layer (#11227)
* Change default parameters
* Avoid to get GRPECS from CCDB
* Fix simulation and digitisation with 4th later
* Adapt clusterer to work with 4th layer
* Adapt ITS3 tracker to work with 4th layer
* Update README
* Fix typo
* Please consider the following formatting changes
* Move modifications to ITS code in dedicated PR
* Remove leftover
* Fix conflicts
* Fix conflicts
---------
Co-authored-by: ALICE Action Bot <alibuild@cern.ch>
-`-n` is used to set the number of events to simulate;
24
24
-`-g` is used to set the event generator, in this case `pythia8hi`. To simulate pp collisions one can use `pythia8pp`.
25
-
-`--configKeyValues` is needed to set internal parameters of the workflow. Among these parameters, the geometry of the ITS3 inner barrel can be set.
25
+
-`--configKeyValues` is needed to set internal parameters of the workflow. Among these parameters, the geometry of the ITS3 inner barrel can be set:
26
+
-`DescriptorInnerBarrel.mVersion` is the geometry version of the ITS3 inner barrel (`ThreeLayersNoDeadZones`, `ThreeLayers`, or `FourLayers`)
27
+
-`DescriptorInnerBarrel.mRadii` is a 4-element vector with the radii of the ITS3 layers
28
+
-`DescriptorInnerBarrel.mLength` is the length of the ITS3 in the Z direction
29
+
-`DescriptorInnerBarrel.mGapY` is a 4-element vector with the values of gap between the two hemicylinders, described by a translation of the hemicylinders in the vertical direction
30
+
-`DescriptorInnerBarrel.mGapPhi` is a 4-element vector with the values of gap of azimuthal angle between the two hemicylinders, described by the maximum distance between the two hemicylinders. Differently from `mGapY`, in this case there no shift in the vertical direction, but a smaller coverage in the azimuthal angle of the half layers.
31
+
-`DescriptorInnerBarrel.mGapXDirection4thLayer` is the gap in the horizontal direction for the fourth layer, analogous to the `mGapY`.
32
+
-`SuperAlpideParams.mDetectorThickness` is the thickness of the chip
26
33
-`--run` is needed to set the run number.
27
34
28
-
Currently, three different geometries of the ITS3 inner barrel are available:
29
-
-`ThreeLayersNoDeadZones`
30
-
-`ThreeLayers`
31
-
-`FourLayers`
32
-
33
35
The run number is needed to retrieve objects from the CCDB. There are specific ranges of run-numbers, according to the collision system and to the selected geometry if the ITS3 inner barrel:
34
36
35
37
-**pp** collisions:
@@ -42,7 +44,6 @@ The run number is needed to retrieve objects from the CCDB. There are specific r
42
44
- 311934—311966 (`ThreeLayers`)
43
45
- 311967—311999 (`FourLayers`)
44
46
45
-
46
47
### Using external generators based on AliRoot
47
48
It is also possible to simulate heavy-ion collision using external generators based on AliRoot. In this case, it is necessary to load both O2 and AliROOT (the order is important):
As above, it is important to set the correct interaction rate and run number.
79
80
81
+
In addition, some parameters related to the segmentation of the chips can be set with the `--configKeyValues` argument:
82
+
- `SuperAlpideParams.mPitchCol` is the pitch of the column (Z direction)
83
+
- `SuperAlpideParams.mPitchRow` is the pitch of the row (r$\phi$ direction)
84
+
- `SuperAlpideParams.mDetectorThickness` is the thickness of the chip
85
+
86
+
If some parameters of the geometry changed in the simulation, they should be set similarly for the digitisation. In particular, the `mVersion`, `mRadii`, and `mLength` must be setif different from the default ones.
87
+
80
88
# Reconstruction
81
89
82
90
In this step, clustering, vertexing and tracking are performed. This is obtained with the `o2-its3-reco-workflow`:
As above, it is important to provide the correct run number using `-—configKeyValues`, to retrieve the correct files from the CCDB. The other internal parameters provided `-—configKeyValues` via are specific to the cased here considered (Pb-Pb) and are inherited from ITS2.
98
+
As above, it is important to provide the correct run number using `-—configKeyValues`, to retrieve the correct files from the CCDB. The other internal parameters for the vertexer and the tracker are provided `-—configKeyValues` via are specific to the cased here considered (Pb-Pb) and are inherited from ITS2.
99
+
100
+
If the `FourLayers` geometry was used in the simulation, it should be set also forthe reconstruction to set properly the tracker to work with the additional layer. If something else of the geometry was set differently (`mRadii`, `mLength`, `mGapY`, `mGapPhi`, `mGapXDirection4thLayer`, or `mDetectorThickness`), it is necessary to remap the file with the geometry to replace the one on the CCDB, which would be different. This can be done by copying the `o2sim_geometry-aligned.root` file created during the simulation to a directory called `GLO/Config/GeometryAligned`, with the name `snapshot.root`in a local path of choice. Then, the following argument has to be added to the reco workflow: `--condition-remap "file://local_path=GLO/Config/GeometryAligned"`.
92
101
93
-
>**_NOTE:_** reconstruction for the `FourLayers` geometry is not implemented yet.
102
+
>**_NOTE:_**in order to make the reconstruction forthe `FourLayers` geometry work, the following line has to be added to the CMake optionsin the [o2.sh](https://github.com/alisw/alidist/blob/master/o2.sh) recipe in alidist:
0 commit comments