Home CMS Production Clean room MedAustron HEPHY testbeams old
testbeam-RD50-DESY-Jul2023 testbeam-RD50-CERN-Oct2022 testbeam-DESY-Oct2017 testbeam-DESY-April2017 testbeam-SPS2015 testbeam-SPS2014 testbeam-DESY14 testbeam-SPS12 testbeam-SPS11 testbeam-SPS10 testbeam-SPS09 testbeam-SPS08 LP-TPC
  Belle testbeam at SPS in June 2015, Page 6 of 6  Not logged in ELOG logo
ID Date Author Project Subject Run Numberdown Events XYPosition Cooling Data
  36   Sun Jun 7 14:44:29 2015 Thomas BergauerSVD3 (H6B)XY Stage and DUT Positions    Unknown

Coordinate system:

pos x-Direction = Jura side

pos y-Direction = Down

Zero-point is in the top right corner in Beam direction

 

absolute Position of PI Stages:

Pos 1: x=100 mm, y=79 mm (Hits in APV 3 und 8-9 in p-Seite und 14 und 17 in n-Seite )

Pos 2: x=69.3 mm, y=79 mm (Hits in APV 3-4 und 8-9 in p-Seite und 13 und 18 in n-Seite) 

Pos 3: x=38.6 mm, y=84 mm

Pos 4: x=130.7 mm, y=84 mm

Pos 5: x=30.5 mm, y= 99.74 mm (wide side top)

Pos 6: x=136.08 mm, y= 91.49 mm (narrow side top)

Pos 7: x= 30.5 mm, y= 79 mm (wide side center)

Pos 8: x=136.08 mm, y= 79 mm (narrow side center)

Pos 9: x=30.5 mm, y= 60.67 mm (wide side down)

Pos 10: x= 136.08mm, y=68.9 mm (narrow side down)

  39   Sun Jun 7 20:02:40 2015 Hao YinBelle II FADC (H6A)Cooling Box Emergency break    Unknown

Something triggered a emergency break. HWRun012 only last 1-10k event has to be discarded.

  50   Mon Jun 8 11:33:24 2015 Thomas Bergauercommonbeam profile    Unknown

120GeV hadrons, beam config H6A.BELLE.003

  56   Mon Jun 8 16:53:13 2015 Benedikt WürknerSVD3 (H6B)EUTelescope Fitter not working investigation    Unknown

Apparently every problem can be attributed to a misalignment problem. The telescope has troubles with heavily misaligned DUTs. Was resolved by creating different gear-files for each run with pretty precise coordinates of the DUT position calculated for the telescope coordinate system. 

Additionally one has to watch out for misaligned planes of the telescope itself. It was required to allow for more than 2mm offset for the telescope planes behind the DUTs. This can be easily checked by looking at the PreAligner plots in the -hitmaker-histo.root file.

It look something like this:

and not like this:

 

Run number offset value Comment
49 -1  
50 -1 Expected default value. EORE=49401
51 -1 Expected default value. EORE=49400
52 -1 Checked -1 EORE= 49401
53 -1 Checked -1 EORE= 49401
54 -1 Checked -1 EORE= 119401, 
55 -1 Checked -1 EORE= 409388
56 -1 Checked -1 EORE= 49392
57 -1 Checked -1 EORE= 49377
58 -1 Checked -1 EORE= 49397

 

Run Position x-Table x-telescope FW x-telescope BW
49 1 100 -13,7 -16,7
50 2 69,3 17 14
51 3 38,6 47,7 44,7
52 4 130,7 -44,4 -47,4
53 5 30,5 55,8 52,8
54 6 136,8 -50,5 -53,5
55 7 30,5 55,8 52,8
56 8 136,8 -50,5 -53,5
57 9 30,5 55,8 52,8
58 10 136,8 -50,5 -53,5
  58   Mon Jun 8 18:08:49 2015 Thomas BergauerSVD3 (H6B)Telescope online monitor    Unknown

a working version of the EUDET online monitor (which works also with the FE-I4) is at the following location

~/BELLETEST/eudaq-neu/build/monitors/onlinemon$ ./OnlineMon.exe -sc 0 -f /home/telescope/eudaq/data/run000060.raw

  66   Tue Jun 9 10:01:03 2015 Lukas BullaSVD3 (H6B)TLU setup info    Unknown

Channels:

  • Upstream vertical -> channel 0; (bitmask 1)
  • Upstream horizontal -> channel 1; (bitmask 2)
  • Downstream vertical -> channel 2; (bitmask 4)
  • Downstream horizontal ->channel 3; (bitmask 8)

 

TLU DuT interface:

DUT Interface Bitmask DAQ
1 1 Mimosa (EUDET Telescope)
2 2 leer
3 4 SVD3
4 8 FE-I4

 

  80   Wed Jun 10 18:05:03 2015 Benedikt WürknerSVD3 (H6B)FEI4 configuration   NoUnknown

There are two planes, one fixed upstream and one fixed downstream. 

CIS3WII_6 upstream and CIS2WI_IBL2 downstream.

They are configured using the pc in H6B which can be accessed via microsoft remote desktop from the network 192.168.5.x using the ip 192.168.5.6. 

The configuration files can be found in the folder "E:\ConfigurationCMS\" on the server and are named after the modules. 

Only one of the FEI4 detectors can be used at a time since they are of different generations (FEI4A and FEI4B) which can't be used at the same time with the available USB board. vnc

The configuration for EUDAQ needs to be adapted for the used module by changing the name of the configuration file. 

[Producer.USBpixI4]
SRAM_READOUT_AT = 5
SkipConfiguration = no
UseSingleBoardConfig = no
boards = 230
modules[230] = 1
#upstream
config_file = E:\ConfigurationCMS\CIS3_W11_06_thr1600_7to21ke_modified.cfg.root
#downstream:
#config_file = E:\ConfigurationCMS\CIS2_W02_IBL1_thr1600_7to14_modified.cfg.root
fpga_firmware = E:\icwiki_svn\USBPixI4\host\tags\release-5.3\config\usbpixi4.bit
lvl1_delay = 16
tlu_trigger_data_delay = 10

In my experience switching between the planes also requires a restart of the USBPix DAQ because apparently something is not working with the reload of a different config file afterwards. I had the phenomenon that the DAQ responded like it was working but the datastream was empty. Therefore always check the online monitor for hitmaps. 

ELOG V3.1.5-fc6679b