AHCAL and BIF Test Beam at DESY (July/August 2016)

We had 2 weeks of beamtime at DESY, TB24, from 25/07 to 07/08. Elog is available here : https://ttfinfo.desy.de/CALICEelog-sec/show.jsp?dir=/2016/30/26.07&pos=2016-07-26T21:09:48

Contents

Hardware under test

HBUs

HBU commissioning

interfaces

20 sets of interfaces expected on July 5 or 6

Data taking programme:

Schematic view of the modules as they are seen by the beam.

layout.jpg

MIP calibration in airstack

IMG_1607.jpeg IMG_1611.jpeg IMG_1614.jpeg

Default setup

We perform MIP calibration in the airstack using a default setup of 15 single modules, as summarized in the table. As the MIP signal is degradad for the latest modules, we have repeated the measurement three time, each of them, removing a set of the first 5-4 modules from the airstack.

map1.png

Phys.
order

DIF_ID#

power
cable

MPOD

HV values

LDA
port#

name

1.

1

1

u0,u100,u400

67

0

SM_100 (Mainz HBU4)

2.

2

2

u207,u307,u507

67

1

SM1

3.

3

3

u2, u102, 402

67

2

SM2

4.

4

4

u3, u103, 403

67

3

SM4

5

5

5

u4, u104, 404

67

4

SM5

6

6

6

u5, u105, 405

67

5

SM7

7

7

7

u6, u106, 406

78 (increaded during MIP calib. https://ttfinfo.desy.de/CALICEelog-sec/show.jsp?dir=/2016/30/29.07&pos=2016-07-29T11:05:16)

6

Mainz HBU3

8

8

8

u7, u107, 407

40

7

HBU3_1

9

9

9

u200, u300, u500

40

8

HBU3_2

10

10

10

u201, u301, u501

40

9

HBU3_3

11

11

11

u202, u303, u502

40

10

HBU3_4

12

12

12

u203, u303, u503

40

changed to 18

HBU3_5

13

13

13

u204, u304, u504

40

12

HBU3_6

14

14

14

u205, u305, u505

40

13

HBU3_7

15

15

15

u206, u306, u506

40

15 (14 is bad port)

HBU3_12

The map with all modules in the setup can be found here: http://desy.de/~ebrianne/Mapping/MapChipChan2IJK_July2016_Airstack.txt

During the first round of MIP calibrations runs, the layer 12 had to be removed of the runs. https://ttfinfo.desy.de/CALICEelog-sec/show.jsp?dir=/2016/30/28.07&pos=2016-07-28T13:42:47

Second setup

We removed the first 5 layers and also the layer 12th since had failed during previous runs, so we can perform the calibration of the following 5. see https://ttfinfo.desy.de/CALICEelog-sec/show.jsp?dir=/2016/30/28.07&pos=2016-07-28T13:42:47

Therefore, the setup is the following:

Phys.
order

DIF_ID#

power
cable

MPOD

HV values

LDA
port#

name

2

6

6

u5, u105, 405

67

5

SM7

3

7

7

u6, u106, 406

78 (increaded during MIP calib. https://ttfinfo.desy.de/CALICEelog-sec/show.jsp?dir=/2016/30/29.07&pos=2016-07-29T11:05:16)

6

Mainz HBU3

4

8

8

u7, u107, 407

40

7

HBU3_1

5

9

9

u200, u300, u500

40

8

HBU3_2

6

10

10

u201, u301, u501

40

9

HBU3_3

7

11

11

u202, u303, u502

40

10

HBU3_4

8

13

13

u204, u304, u504

40

12

HBU3_6

9

14

14

u205, u305, u505

40

13

HBU3_7

10

15

15

u206, u306, u506

40

15 (14 is bad port)

HBU3_12

The map with all modules in the setup can be found here:

Last setup

We removed again the first 5 layers and moved the Mainz HBU3 (previous layer 7) at the end.

Therefore, the setup is the following:

Phys.
order

DIF_ID#

power
cable

MPOD

HV

LDA
port#

name

1

11

11

u202, u302, u503

40

10

HBU3_4

2

12

12

u203, u303, u503

40

11

HBU3_5

3

13

13

u204, u304, u503

40

12

HBU3_6

4

14

14

u205, u305, u503

40

13

HBU3_7

5

15

15

u206, u306, u503

40

15

HBU3_12

6

7

7

u6, u106, 406

80

changed to 18

Mainz HBU3

The map with all modules in the setup can be found here:

EM showers in the Steel Absorber stack

We order the HBUs in the same than in the default airstack setup.

IMG_1622.jpeg IMG_1627.jpeg IMG_1639.jpeg

The map with all modules in the setup can be found here: http://desy.de/~ebrianne/Mapping/MapChipChan2IJK_July2016_Airstack.txt

Setup (basics):

DAQ software

A wiki for the new monitoring system is up here : http://flcwiki.desy.de/AHCALMonitoring_DQM4HEP, general instructions can be found in the operation section of this wiki.

Here you can find a wiki about the EUDAQ for AHCAL and BIF

Visit http://flcwiki.desy.de/tb2016 for more information.

Signals & Logics (electronics)

The setup is very similar to the one used in previous testbeams.

/!\ Electronics picture.

For previous setups, see for example http://flcweb02.desy.de/flcwiki/AHCALTestBeamCERN2015/#Electronic_setup_and_cabling:_diagrams_and_pictures .

I the present case, we only use two scintillators (placed in front of the detector) and we also used the BIF.

We are using two scintillators placed between the beam and the detector as validation signal. Both scintillators are thin sticks of about 1cm width and 15 cm lenght and both are crossed in order to set horizontal and vertical position with high precision. The coincidence signal is fed into the CCC to be used as validation signal.

The two signals from the scintillators and from the coincidence is conducted to the BIF also.

Operation instructions

Monitoring instructions:

http://flcwiki.desy.de/AHCALMonitoring_DQM4HEP#instructions_for_July.2FAugust_Testbeam

monitoring.png

LED runs with EUDAQ

0)

Prepare Labview:

  1. load ET_IC slow control files
  2. go to Calib tab and click
    1. SET (Delay Lines)
    2. SET (DACs VCALIB)
    3. Enable TCALIB (5) and click SET
  3. Go to Take Data tab and click SET Setup Lab Mode.
  4. Choose the paths and click autopath, autolisten and listen.

For a more extens explanation, visit the old wiki http://flcwiki.desy.de/AHCALTestBeamCERN2015/LabviewOperation

Long LED runs

1)

cd /home/calice/Desktop/eudaq-configuration/calice_ahcal/conf_longLED_July

source create_from1file.sh

The script generates the configuration files in the eudaq pc, the labview configuration files in the eudaq pc also and sends the copy to the labview pc. It also creates the eudaq folders if needed.

(see header of the script)

echo "Script to generate the EUDAQ configuration files for long LED runs"
echo "usage: source create_from1file.sh -l(--labviewConffolder) LabviewPCConfigurationFolder -v(--v0) V0 -n(--nvoltages) NVoltages -s(--step) dmv_step -r(--readoutcycles) CYCLES -e(--eudaqfolder) EUDAQdatafolder -c(--createDatafolder) y/n"
echo "requires the existence of:"
echo "                    a)       the xxLED.conf file, see the end of the script to see how it should look"
echo "                    b)       the longLED_wind/LED_00.ini file, see the end of the script to see how it should look"



LABVFolder="longLED_July2016"
NV="91"
V0="3500"
dmV="50"
CYCLES="3000"
EUDAQ_FOLDER="20160729_long"
MAKE_DIR="y"

2)

cd /home/calice/Desktop/EUDAQ1.6/producers/calice/scripts

./LED_2016

3) choose the /home/calice/Desktop/eudaq-configuration/calice_ahcal/conf_longLED_July/LED_00.conf file

4) START.

Short daily LED runs

1)

cd /home/calice/Desktop/eudaq-configuration/calice_ahcal/conf_dailyLED_July

source create_from1file.sh

The script generates the configuration files in the eudaq pc. It also creates the eudaq folders if needed.The labview files should be already generated by the experts.

2)

cd /home/calice/Desktop/EUDAQ1.6/producers/calice/scripts

./LED_2016

3) choose the /home/calice/Desktop/eudaq-configuration/calice_ahcal/conf_longLED_July/LED_00.conf file

4) START.

Data location (dCache)

The data is uploaded on the dCache at the usual space, the raw data (binary as well as slcio and txt files) :

BIF Offset

noPP

68054

TB_PP

93654

ILC_PP

141153

Run Information

runinfo_JulyAUG2016.txt

run_summary.txt

Database

Pedestal

Folder

DB Tag

Comments

/cd_calice_Ahc2/TestbeamJuly2016/Pedestal

ahc2_pedestal_001

Pedestal value from AT data from July data (Muons)

Gain

Folder

DB Tag

Comments

/cd_calice_Ahc2/TestbeamJuly2016/gain_constants

ahc2_gain_constants_001

Gain calibration values from 20160801_long LED run

/cd_calice_Ahc2/TestbeamJuly2016/gain_constants

ahc2_gain_constants_003

Gain calibration values (Anna Rosmanitz)

MIP Calibration

Folder

DB Tag

Comments

/cd_calice_Ahc2/TestbeamJuly2016/mip_constants

ahc2_mip_constants_001

MIP Calibration from DESY July 2016 (mpv is not pedestal subtracted!)

/cd_calice_Ahc2/TestbeamJuly2016/mip_constants

ahc2_mip_constants_002

MIP Calibration from DESY July 2016 (using ahc2_pedestal_001), channel 0 on chip 0 on module 1 missing

/cd_calice_Ahc2/TestbeamJuly2016/mip_constants

ahc2_mip_constants_003

MIP Calibration from DESY July 2016 (using ahc2_pedestal_001), 8 default values. The default value is obtained computing the mean of the mpv per chip

/cd_calice_Ahc2/TestbeamJuly2016/mip_constants

ahc2_mip_constants_004

MIP constants for events after Run43293, MIP Calibration from DESY July 2016 (using ahc2_pedestal_001), HV on MPOD for Module7 (Mainz_HBU3) changed

/cd_calice_Ahc2/TestbeamJuly2016/mip_constants

ahc2_mip_constants_005

MIP constants (Anna Rosmanitz)

/cd_calice_Ahc2/TestbeamJuly2016/mip_constants

ahc2_mip_constants_007

MIP constants 2 (Anna Rosmanitz)

Dead Cells

Folder

DB Tag

Comments

/cd_calice_Ahc2/TestbeamJuly2016/DeadCellMap

ahc2_DeadCells_001

Dead cells for the data until Run 43127

/cd_calice_Ahc2/TestbeamJuly2016/DeadCellMap

ahc2_DeadCells_002

Dead cells

Others

/cd_calice_Ahc2/TestbeamJuly2016/Intercalibration

ahc2_IC_001

HG/LG Intercalibration one value per chn. LED data in ET mode from DESY TB 2016 are used (module 15 the chip number is wrong! use the ahc2_IC_002)

/cd_calice_Ahc2/TestbeamJuly2016/Intercalibration

ahc2_IC_002

HG/LG Intercalibration one value per chn. LED data in ET mode from DESY TB 2016 are used (module 2 has wrong chip number!)

/cd_calice_Ahc2/TestbeamJuly2016/Intercalibration

ahc2_IC_003

HG/LG Intercalibration one value per chn. LED data in ET mode from DESY TB 2016 are used (error on module 2 corrected!)

/cd_calice_Ahc2/TestbeamJuly2016/Intercalibration

ahc2_IC_005

HG/LG Intercalibration one value per chn. LED data in ET mode and Beam data in AT mode from DESY TB 2016 are used (error on module 2 corrected!)

Theme

Following the tradition started in May2016, to feed the shifters urges of artistic beautiness and compensate the lack of natural light in the hut, a set of wallpapers was prepared and loaded in the PC's.

This time Sara Herranz, Paula Bonet, Conrad Roset and Laura Agustí illustrations accompanied us during the testbeam installation, debugging and data taking phases.


CategoryHCAL

AHCALandBIF_TestBeamDESYJuly2016 (last edited 2017-09-01 16:55:55 by yujisudo)