• AHCALSpiroc2dTestBeam2015

AHCAL Spiroc2d Testbeam at DESY (November 2015)

Contents

Setup

Detailed information can be found in:

http://flcweb02.desy.de/flcwiki/2015?action=AttachFile&do=view&target=20151027_AI.pdf

and

https://agenda.linearcollider.org/event/6741/session/5/contribution/41

Spiroc2d

One small module is equipped, with several tiles in all of the chips, except in chip Spiroc2_3.

• SP2D1, channels 1, 2, 3, 4, 5, 10, 16 are equipped with 12k KETET soldered two times tiles. Channels 11, 17, 30, 34 are equipped with "newer" KETEK tiles.
  • Modifications: rstb_delay and the start_acq tied → we can use all 16 memory cells in External Trigger

  • Pin 48 lifted --> preamplifier filter

  • The tiles are connected to HV1=30.04V. Switch the inDACs to 2.5V mode and setting "0" to come to the aimed 27.5V.
  • Preamplifier value 200fF
  • T0 at channel 29
• SP2D2, channels 5, 6, 21, 31 are equipped with the 12k "newer" KETEK tiles.

  • Triger configuration not modified --> don't use memory cells 10 and 14 in ET mode

  • No preamplifier filter
  • The tiles are connected to HV1=30.04V. Switch the inDACs to 2.5V mode and setting "0" to come to the aimed 27.5V.
  • Preamplifier value 200fF
• SP2D3
  • T0 channel 7
• SP2D4, channels 3, 11, 18, 21 and 23 are quipped with SENSL tiles.

  • Triger configuration not modified --> don't use memory cells 10 and 14 in ET mode

  • No preamplifier filter
  • The tiles are connected to HV1=30.04V. Switch the inDACs to 2.5V mode and setting "0" to come to the aimed 27.5V.
  • Channel 20 seems to be dead and does not react on preamplifier settings (simply ignore it).

Channel map:

Spiroc2D map

T0 channels

Since run 40XXX, two t0 channels are operative in the module:

• channel 29 in chip 129
• channel 7 in chip 131

EUDAQ

We are running the data taking using the eudaq program, as in previous testbeams. For more detailed information, read the following link

http://flcweb02.desy.de/flcwiki/AHCALTestBeamCERN2015/#Common_DAQ:_EUDAQ

The output format is slightly different since two more integers have been added to the lcio object in order to have the gain_bit/hit_bit duplicated (one decoded from the ADC data stream from the spiroc and other decoded from the TDC data stream from the spiroc)

Electronics setup

The setup is very similar to the one used in previous testbeams. 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, for first time, 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 to...

The coincidence signal is also fed into the two t0 channels.

Beam InFormation module (BIF)

The BIF is a modified AIDA mini-TLU, which is running in the slave mode and is connected to the LDA via HDMI cable. It receives clock, fast commands and trigger. The picture of the cable connection is shown here:(TODO). For the spiroc2D tests there was only 1 input: coincidence of the trigger scintillator.

The communication protocol and BIF data format is described in AHCAL_BIF.

The BIF readout cycles need to be correlated. For the time being the method is a guess based on the delay between readout cycles.

Data

Data are stored in the dCache Grid /grid/calice/tb-desy/native/desyAhcal2015/AHCAL_Testbeam_Raw_November_2015/

for more information, visit: http://flcweb02.desy.de/flcwiki/AHCALTestBeamCERN2015/#Data_access

As usual all the information about the runs is detailed in the elog https://ttfinfo.desy.de/CALICEelog-sec/show.jsp?dir=/2015/46/10.11&pos=2015-11-10T14:12:09 (10, 11 and 12 of november)

MIP scans

A summary of the most interesting runs are shown in the following table. Only the MIP scans using AT threshold of 150 DAC are shown, for more information check the elog.

Threshold scans

Operation

The basics of the operation are the same than in last testbeam at CERN http://flcweb02.desy.de/flcwiki/AHCALTestBeamCERN2015

Some pecualiarities appear since we are using a new version of the Spiroc (Spiroc2d):

Labview operation

http://flcweb02.desy.de/flcwiki/AHCALTestBeamCERN2015/#Labview_operation

• rdesktop calice@131.169.184.84

• Slow control changes may need to be handled manually.
• The initial configuration of the module (powering up and down, choice of the Slow control files) is done using the "old" USB-labview.
  • Labview program: ahcal_newDAQ_versProto12.vi
  • First: System/USB init tab:

    • If left side of the tab not all is green: first stop (blue button) and restart the labview program (white arrow). If still is not green, click "Write" and "Set" in the left part of the tab. If still is not green, repower the system (the LV and HV power supplies, first disconnect HV and then LV, consequently connect the LV and then the HV).

    • If left side of the tab not all is green: power up the system using the following sequence
      • HBU2 ON, 3.3 V ON, Power Pulsing ON
      • Power Pulsing OFF, 3.3 V OFF, HBU2 OFF
      • Wait 15 s
      • HBU2 ON, 3.3 V ON, Power Pulsing ON
• Go to the Slow Control Slab
  • Correct path C:\temp\HBU_SP2D\AT\ or \ET\
  • Click Define, Write, Reset, Load
• Stop the program (Blue button)

USBLab2.png, USBLab1.png

• The specific settings for the run (ET or AT mode, delay times, etc) and the data taking are done using the multilayer Labview.
  • Main_commandlessFork.vi in the project AHCAL_DAQ_xLDA.lvproj

  • Go to Calibration tab and set it in the following way: MultilayerLabview1.png, MultilayerLabview1.png

  • Go to take data tab and set the LabMode (AT) with no LED, with valdiation signal and zero dummy triggers.

  • Go back to the Calibration tab and check that the external trigger are off (they are automatically set when you set the Lab mode). Unclick them and click set.

  • Put the Labview in autolisten, listen and autopath modes (check the paths) MultilayerLabview2.png, MultilayerLabview2.png

EUDAQ operation

http://flcweb02.desy.de/flcwiki/AHCALTestBeamCERN2015/#EUDAQ_operation

• The data taking is done with the EUDAQ in the usual way.

  • ssh -X calice@131.169.184.85

  • cd /home/calice/eudaq-1.5-dev/calice_eudaq
  • ./TESTBEAM_2015
  • select the conf file and run