Other useful function during calibration

Creating a mapping file

In order to translate the different channels in one (or multiple) CAEN readout unit(s) into physical space i.e. layer, column, row and module within our detector, we need to define a mapping file. For the 2024 TB each assembly was connected to an 8 layer connector board, which was then connected to either a CAEN DT5202 or one HGCROC on the KCU.

Connector board for 2024 test beam campaign to connect 8 assembles to one readout unit

Ribbon cables to connect connector board (for 8 assemblies) and 1 readout unit (i.e. CAEN DT5202).

A picture of the mapping of one CAEN unit to 8 physical layers can be seen below and the full picture of the mapping for the TB is displayed below as well.

Mapping of individual channels within the assemblies (black text) to the corresponding channels within one CAEN DT5202 readout unit (blue text) using the ribbon cables and 8 layer connector boards.

Mapping of all layers and channels to the 8 CAEN DT5202 readout unit used in the August 2024 PS TB.

To ease the generation of the necessary mapping text file (i.e 2024TB-file) you can use the CreateMapping.C macro, as follows:

root -b -x -q -l 'CreateMapping.C+("../configs/mappingSingleCAENUnit_simple.txt","../configs/layersCAEN_PSTB_2024.txt","Mapping_output.txt")'

Where the first input is the mapping within the one CAEN module and the second the layer to CAEN RU assignment.

In order to analyse any data you need to know which channel in the respective read out unit belongs to which specific channel in the physical space. As an example below the association of a single CAEN unit with the ribbon cable and the full TB using the CAEN units.

Mapping of the individual channels within one assembly (black text) to one CAEN DT5202 (blue text) unit using the ribbon cables and the 8 layer connector boards from the TB in 2024.

Skimming local muon triggers only

./DataPrep -f -d 1 -M -i rawPedAndMuon_$RUNNR.root -o raw_muononly_$RUNNR.root 

Skimming local noise triggers only

./DataPrep -f -d 1 -N -i rawPedAndMuonNoise_$RUNNR.root -o raw_pedonly_$RUNNR.root 

Restricting the number of events to be analyzed

For some functions of ./DataPrep an option to limit the running only over a fraction of the events is implemented use -L $NEVTSANA if need be.