Documentation for HGCAL + AHCAL TestBeam at CERN SPS in 2017

Contents

Setup

July 2017

In May, we have take data in the H2@SPS line at CERN, during the period between the 12/07/2017 to the 19/07/2017.

Our setup consisted of a thick small steel absorber structure with 11 plates (thickness 74 mm) and thin front and back plates, equipped with 12 active layers of 1 HBU each. The HGCAL EE and FH prototypes were placed in front. All layers have individually wrapped tiles. The detector was read out with the Wing-LDA.

The layers were ordered as follows (first is the closest to beam):

Phys.
order

Module#

power
cable

HDMI
cable

MPOD

LDA#

LDA
port#

name

1.

1

01

01

u0,u100,u400

0

01

SM_100

2.

2

02

02

u1,u101,u401

0

02

SM_1

3.

3

03

03

u2,u102,u402

0

03

SM_2

4.

4

04

04

u3,u103,u403

0

04

SM_4

5.

5

05

05

u4,u104,u404

0

05

SM_5

6.

6

06

06

u5,u105,u405

0

06

SM_7

7.

7

07

07

u6,u106,u406

0

07

HBU3_1

8.

8

08

08

u7,u107,u407

0

08

HBU3_2

9.

9

09

09

u200,u300,u500

0

09

HBU3_3

10.

10

10

10

u201,u301,u501

0

10

HBU3_4

11.

11

11

11

u202,u302,u502

0

11

HBU3_5

12.

12

12

12

u203,u303,u503

0

12

HBU3_6

Network setup

Network_setup_testbeam_2017_July.png

The data from physics data taking is stored in on svhgcal01 (192.168.222.1) and the proper directories (data and logs) have to be mounted via sshfs:

On EUDAQ pc (flchcallab4):

sshfs daq@192.168.222.1:/home/daq/eudaq/data /home/calice/Desktop/EUDAQ1.6-testbeam2017July/data/mounted_svhgcal01_data/ -o ro,Ciphers=arcfour,compression=yes,auto_cache,reconnect

sshfs daq@192.168.222.1:/home/daq/eudaq/data_ahcal/ /home/calice/Desktop/EUDAQ1.6-testbeam2017July/data/mounted_svhgcal01_data_ahcal/ -o ro,Ciphers=arcfour,compression=yes,auto_cache,reconnect

where the directory on svhgcal directory has to be updated. For safety, it is mounted as read-only

On DQM pc (flchcallab6):

All mounts can be mounted via a script: /home/calice/TB2017/mount.sh

sshfs 192.168.1.11:/ /home/calice/TB2017/mount_frankenstein/ -o reconnect

sshfs 192.168.1.10:/home/calice/ /home/calice/TB2017/mount_flchcallab4/ -o Ciphers=arcfour,compression=no,auto_cache,reconnect

sshfs daq@svhgcal01:/home/daq/eudaq/data/ /home/calice/TB2017/mount_svhgcal01_data -o ro,Ciphers=arcfour,compression=yes,auto_cache,reconnect

sshfs daq@svhgcal01:/home/daq/eudaq/logs/ /home/calice/TB2017/mount_svhgcal01_logs -o ro,reconnect

On Reconstruction & Dcache PC (flchcallab5):

sshfs daq@svhgcal01:/home/daq/eudaq/data/ /home/calice/TB2017/mount_svhgcal01_data -o ro,allow_other,reconnect

sshfs daq@svhgcal01:/home/daq/eudaq/data_ahcal/ /home/calice/TB2017/mount_svhgcal01_data_ahcal -o ro,allow_other,reconnect

sshfs 192.168.1.10:/home/calice/ /home/calice/Desktop/EUDAQ_PC/ -o reconnect,allow_other

sshfs 192.168.1.11:/ /home/calice/Desktop/DAQ_PC/ -o reconnect,allow_other

DAQ Setup

The used DAQ hierarchy is as follows:

ASIC (SPIROC 2b, Omega group)

all layers were operating with SPIROC2b

Interfaces

All layers were operating with the new generation of interface boards (CIB, POWER, DIF, CALIB) without magnetic components. For layers 1, 8 and 9 (SM100, HBU3_2, HBU3_1) pre-series boards were used (accidentally), where as many magnetic components as possible were removed (see logbook entries of 23 May 2017)

Link Data Agregator (LDA)

The Wing-LDAs were used.

Clock and Control Card (CCC)

The CCC provides the master clock of the DAQ and starts and stops the acquisition according to the spill level and readiness of all ASICs.

It receives the trigger validation signal from the HGCAL SYNC board. No spill signal was used. For the CCC the HGCAL veto+stop settings were used, veto+stop+wait leads to a significant fraction of missed events on our side (HGCAL readout very slow, so we run into a timeout)

Beam Interface (BIF)

no beam interface was used.

Labview

Labview operation is described in the shifter's instructions. It is running on a dedicated PC in the beam area ("Frankenstein PC") via remote desktop from the beam hut (PC with the large screen). The labview project is located in f:\CERN_2017_July\test\LabviewTestbeam2017July_TempComp_12\ . Always open the project first! In the project, open main.vi

EUDAQ

For beam data, the EUDAQ installation (version 1.6) on HGCAL server svhgcal01) was used. The communication between EUDAQ and detector goes through the labview, therefore the Labview has to be running and in a listening state. No further steps from AHCAL side are needed for operation. Just configurate once (after EUDAQ start, it is not necessary to configure between runs), then go with start and stop in EUDAQ. Further configuration does not harm AHCAL.

For LED calibration, a special branch for EUDAQ1.6 supporting parameter scans is used on the EUDAQ PC. Details in shifter's tasks

Trigger and spill signal

Trigger

For the validation a coincidence of two CMS owned trigger scintillators of 4*4 cm2 and 10*10 cm2 directly in front of the detector was used. This goes to the HGCAL electronics and is provided to the AHCAL by the HGCAL SYNC board. This is recorded by the LDA.

Spill

no spill signal was used

Others

nothing

Materials in front of AHCAL

beam area

lots: trigger scintillators, wire chambers, the HGCAL, ...

Run Information

to come common runs: google doc

AHCAL specific information is collected in theCALICE AHCAL E-log

CMS-HGCAL documentation and instructions are in this CMS twiki page

Monitoring

Both quasi-online and DQM monitorings require slcio files. For EUDAQ1.6, there is a prepared script, that converts every finished run, except for the last run (which is not converted to avoid converting unfinished eudaq file). Keep this terminal running in the background. To convert the last run, there is a dedicated script.

ssh 192.168.1.10 #to connect to the EUDAQ PC from flchcallab6
cd /home/calice/Desktop/EUDAQ1.6-testbeam2017July/data
./lcio_convert.sh #all new files will be converted automatically
./lcio_convert_last.sh #to force convert also the last stored eudaq raw file

Quasi-Online monitoring and event display is described in a separate wiki page: http://flcwiki.desy.de/AHCALandHGCALTestBeamCERN2017/Monitoring

Data Quality monitoring within DQM4HEP framework is described in a wiki page http://flcwiki.desy.de/AHCALandHGCALTestBeamCERN2017/DQM4HEP

In addition, the EUDAQ onlinemonitor was used for HGCAL and AHCAL. The AHCAL part only contains a hitmap.

The temperature can be obtained from the labview text files. The summary of the temperatures can be plotted on the pc flchcallab6:

cd ~/TB2017/Temperature
./plot_temperature.sh 

Shift Instruction

are on a separate wiki page: http://flcwiki.desy.de/AHCALTestBeamCERN2017/July2017shifts

AHCALandHGCALTestBeamCERN2017 (last edited 2017-09-30 07:16:26 by JiriKvasnicka)