Differences between revisions 3 and 4
Revision 3 as of 2017-05-30 15:16:57
Size: 12855
Revision 4 as of 2017-05-30 15:17:30
Size: 12853
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
=== DQM4HEP Monitoring ===

== Shifter instructions ==
== DQM4HEP Monitoring ==

=== Shifter instructions ===
Line 30: Line 30:
=== Testbeam Monitoring === == Testbeam Monitoring ==

Online Monitoring and reconstruction for AHCAL Test Beam Campaign at CERN2017

This page is a branch of the main AHCALTestBeamCERN2017 page.


DQM4HEP Monitoring

Shifter instructions

1) In /home/calice/TB2017/scripts, load all the dqm4hep elements:

source manual_start.sh

This is only needed once, but eventually an element will crash. In this case kill them, for that:

source manual_kill.sh

2) In the Run Control, click Start run click on okay, no password is needed. This is only required once at the beginning.

3) in /home/calice/TB2017/DQM4HEP/build start the streamer with the name of the file to look into (and the full path if you are not in the right path), e.g.

dqm4hep_start_lcio_file_service -c ahcal_event_collector -t 1 -f /home/calice/mounted_data_directory/path_to_file/ROCEvents051081_tp.slcio

4) if you want to clear the histograms before you look at a new run, you need to stop the run in the run control, wait a bit, and then start the run again. After clicking on update in the DQM Monitoring Window, the histograms should be empty

Testbeam Monitoring

copy from 2015, to be checked!!! Katja

The programs are in


We reconstruct and apply the available calibrations to the raw events:

QtReco (reconstruction):

1. Run it by doing


2. Edit the steering file in the folder /home/calice/Desktop/AHCAL-Reconstruction/xml (steering.xml)

Run number

(need to be edited for each new Run)

3. Then Press Configure -> Check if the lcio file is found.

4. Then Press Start, it will run the reco and the analysis.

5. Wait until it finishes. It should show Analysis Module : destroyed

Now we are ready to show the plots or event displays.

Online monitor for events after reconstruction


It is in:


1. Run it by doing


/!\ QtReco-interface must be opened!

2. Click on connect then enter the Run number. /!\ Check that it says connected.

3. Then choose what plots you want to look at. /!\ Careful when analysing the plots! Mis-calibrations!

Important (and implemented) distributions

Several distributions are available after analysis :

  • T0 correlations
  • Hit multiplicity
  • Energy sum and spectra per layer
  • Shower profile, beam profile
  • HitMap

  • Temperature (only for raw txt!)


In this section, T0 Plots are shown. 3 differents types of plots : Correlation within a layer, Difference of T0s within a layer and Correlation of a T0 channel to the others. If everything is fine, a linear (more or less as TDC is not calibrated) correlation should be visible as shown on the plots below.

Hit Multiplicity


Shower profile, beam profile

Muons +120 GeV, tungsten absorber

Pions +50 GeV, tungsten absorber

Electrons +20 GeV, tungsten absorber


You can see some reference hitmaps from August 2015 data taking period.

For Muons, +120 GeV, tungsten absorber.

For Pions +50 GeV, tungsten absorber.

For Electrons +20 GeV, tungsten absorber.

Calibration procedure

The QtReco program make use of the Marlin framework and the calice processors in order to reconstruct the raw data (hardware information) to physics data. The reconstruction is done in several steps and need to have access to the database containing mapping of the detector and calibration constants for each channel (gain, Pedestal, MIP).

/!\ The calice database is not accessible from outside the DESY network, so for CERN, a local database needs to be setup or slcio made.

The latter option is chosen and also the database slcio file are in  ~/Desktop/TB_Soft/Local_db/ . The database setup and making of slcio file is rather difficult so it is reserved for experts (contact Eldwan ( eldwan.brianne@NOSPAMdesy.de ) or Lan ( huong.lan.tran@NOSPAMdesy.de )).

The reconstruction is done in 4 steps :

  • Event Building from raw txt or raw slcio eudaq files
  • Geometry mapping of the detector
  • Get Calibration constant from database/files
  • Apply Calibration

This is done for each hits in each events.

Database constants (Local)

If you are at DESY, you can directly connect to the database no need to have local files. (Same steering part of GeoCondition Processor as offline reconstruction)

<processor name="GeoConditions" type="ConditionsProcessor">
<parameter name="DBInit" type="string" value="flccaldb02.desy.de:calice:caliceon:Delice.1:3306"/>
<parameter name="DBCondHandler" type="StringVec">
        Ahc2ModuleDescription        /cd_calice_cernSPS2015/TestbeamJuly2015/ModuleDescription               HEAD
        Ahc2ModuleConnection         /cd_calice_cernSPS2015/TestbeamJuly2015/ModuleConnection                HEAD
        Ahc2ModuleLocationReference  /cd_calice_cernSPS2015/TestbeamJuly2015/ModuleLocationReference         HEAD
        Ahc2DetectorTransformation   /cd_calice_cernSPS2015/TestbeamJuly2015/DetectorTransformation          HEAD
        Ahc2HardwareConnection       /cd_calice_cernSPS2015/TestbeamJuly2015/Ahc2HardwareConnection          HEAD
        E4DPedestal                  /cd_calice_cernSPS2015/TestbeamJuly2015/Pedestal                        ahc2_pedestal_007
        E4DGainConstants             /cd_calice_cernSPS2015/TestbeamJuly2015/gain_constants                  ahc2_gain_constants_004
        E4DGainSlopes                /cd_calice_cernSPS2015/TestbeamJuly2015/gain_slopes                     ahc2_gain_slopes_003
        E4DMipConstants              /cd_calice_cernSPS2015/TestbeamJuly2015/mip_constants                   ahc2_mip_constants_005
        E4DMipSlopes                 /cd_calice_cernSPS2015/TestbeamJuly2015/mip_slopes                      ahc2_mip_slopes_003
        E4DDeadCellMap               /cd_calice_cernSPS2015/TestbeamJuly2015/DeadCellMap                     ahc2_DeadCells_008
        E4DSaturationParameters      /cd_calice_cernSPS2015/TestbeamJuly2015/SaturationParameters            ahc2_Sat_001
        E4DIntercalibration          /cd_calice_cernSPS2015/TestbeamJuly2015/Intercalibration                ahc2_IC_001

In case you are outside DESY, the connection is restricted to specific IP addresses. To avoid this problem, local database files can be specified instead. First to create a database file, you need the package lccd (http://ilcsoft.desy.de/portal/software_packages/lccd/index_eng.html). Inside the lccd folder, create a folder build. Then go inside and type :

cmake $ILCSOFT/ILCSoft.cmake ..
make install

It will compile the package.

To create a local file, you have to do :

export LCCD_DB_INIT=flccaldb02.desy.de:calice:caliceon:Delice.1:3306
./build/bin/createdbfile <dbfolder> <tag>

This will then create a slcio file condDB_<Collection>_<tag>_<querytime>.slcio

To make use of theses file locally then you need to specify in the reconstruction steering file : This specify the name of the output collection, the path of the slcio file and the name of the collection inside the file.

<processor name="GeoConditions" type="ConditionsProcessor">
<parameter name="DBFileHandler" type="StringVec">
        Ahc2ModuleDescription       <filepath> ModuleDescription
        Ahc2ModuleConnection        <filepath> ModuleConnection
        Ahc2ModuleLocationReference <filepath> ModuleLocationReference
        Ahc2DetectorTransformation  <filepath> DetectorTransformation
        Ahc2HardwareConnection      <filepath> Ahc2HardwareConnection    
        E4DPedestal                 <filepath> Pedestal                        
        E4DGainConstants            <filepath> gain_constants                  
        E4DGainSlopes               <filepath> gain_slopes                    
        E4DMipConstants             <filepath> mip_constants                   
        E4DMipSlopes                <filepath> mip_slopes                      
        E4DDeadCellMap              <filepath> DeadCellMap                     
        E4DSaturationParameters     <filepath> SaturationParameters            
        E4DIntercalibration         <filepath> Intercalibration                

Event display

After applying the reconstruction and the corrections, we also can have a look on the aspect of the events in our detector. Actually, we can do it in parallel to the reconstruction, since it reads the events in the slcio file created by the QtReco program. For that we use a schematic 3D view of our detector that allows us to nicely and very intuitively discern the structure of the beam (content of pions, muons, electrons, etc), the position of the tracks, etc.

To execute the event display go in :

./start_Event Run_XXXXXX.slcio

The program has a tool to make screenshots. This is found in the "tools" tab and do screenshots in tga format.

Some standard event display are shown in the following pictures.

Electron (-) candidates (10 GeV, steel absorber)

Muon (-) candidate ( steel absorber)

Pion (-) candidate (50 GeV, steel absorber)

Pion (+) candidates (50 GeV, tungsten absorber)

Electron (+) candidates (20 GeV, tungsten absorber)

To make these nice sets of eventdisplays, we can use a few set of "Jiri's" commands:

1) Convert to png, since the saved pictures in the eventdisplay use the tga format

ls *.tga|parallel convert {} ~

2) Create the set, by appending individual pictures:

convert \( glced-1.png glced-2.png +append \) \( glced-3.png glced-4.png +append \) -append test.png

(for 2x2)

convert \( glced-1.png glced-2.png glced-3.png +append +append \) \( glced-4.png glced-5.png glced-6.png +append +append \) \( glced-7.png glced-8.png glced-9.png \) -append -append r30079_pick_of_9events.png

(for 3x3)



AHCALTestBeamCERN2017/Monitoring (last edited 2017-05-31 12:31:07 by EldwanBrianne)