Presentation is loading. Please wait.

Presentation is loading. Please wait.

Calorimeter Cosmics Patrick Robbe, LAL Orsay & CERN, 20 Feb 2008 Olivier, Stephane, Regis, Herve, Anatoly, Stephane, Valentin, Eric, Patrick.

Similar presentations


Presentation on theme: "Calorimeter Cosmics Patrick Robbe, LAL Orsay & CERN, 20 Feb 2008 Olivier, Stephane, Regis, Herve, Anatoly, Stephane, Valentin, Eric, Patrick."— Presentation transcript:

1 Calorimeter Cosmics Patrick Robbe, LAL Orsay & CERN, 20 Feb 2008 Olivier, Stephane, Regis, Herve, Anatoly, Stephane, Valentin, Eric, Patrick

2 2 Setup for cosmic run Night of 13-14 February Full C-side ECAL and C-side HCAL Uniform high gain: 3.10 5 (ECAL) and 2.10 5 (HCAL)‏ Calibration constants of 128 (not really sure...)‏ Trigger rate of 1 kHz, due to hot channels in inner ECAL, data are recorded with these conditions to detect these channels. Then remove Inner ECAL (13 & 14) from L0 path (but not from DAQ path) : 30 Hz. Then set calibration constant in HCAL to 127: 15 Hz.

3 3 Configuration Selection Boards, L0DU, TELL1, CROC, LEDTSB were configured easily using PVSS (one click to get ready, using shortcuts)‏ More difficult to configure ECAL Front-End boards with PVSS HV were set also using PVSS, by Anatoli PRS crate 0 and associated TELL1s were also included (but no cosmics seen)‏ Trigger Validation Boards configured with CAT L0DU algorithm (Et(electron)>20 and Et(hadron)>3) is applied automatically using the default PHYSICS recipe. Optical channels were aligned automatically and latency was setup correctly using the default recipes:  This could be checked rapidly using the online presenter which showed clear cosmics, also seen live from Clermont-Ferrand.

4 4 Consecutive triggers We took first data with only one trigger, than time alignment events with 5 consecutive triggers:  We first thought that these events were not correct  But looking into more details, it seems that only the ODIN bank is corrupted during the first events, all other banks are correct (checked with L0DU bank which contains BCIds)‏  Richard found yesterday where it could come from  But this means that these events could be used and really contain the main trigger, plus 2 clock cycles before and after: not yet analyzed.

5 5 ECAL Hot Channels Readout channel [0-31] FEB-ID (16*crate + FEB) ‏ ECAL Crate #14: FEB 6: channels 28 FEB 7: channels 7, 15, 23, 31 FEB 8: channels 13, 21

6 6 ECAL ADC (1)‏ No more peaks at 256 and -256: CROCs are all configured correctly. Online presenter allows to check presence of 256 and -256 ADC. Zoom

7 7 ECAL ADC (2)‏ ECAL11, FEB7ECAL13, FEB12

8 8 ECAL ADC (3)‏ Problem also visible looking at L0 ADC for the same boards: not a DAQ problem. ECAL11, FEB7ECAL13, FEB12

9 9 ECAL ADC (4)‏ Only 2 channels affected: ECAL11, FEB7: Channel 12 ECAL13, FEB12: Channel 9

10 10 ECAL ADC (5)‏ After Removing the 2 bad channels:

11 11 ECAL 2D-View: Feb vs Channel in feb ECAL 8ECAL 9 ECAL 10ECAL 11ECAL 12ECAL 13ECAL 14 Hot Channels Pb with HV ?

12 12 HV Problem ? ADC Distribution for channels in the grey zone with channels 3 in crate ECAL12 ADC Distribution for « normal » channels

13 13 L0ADC vs ADC Relation between 12 bit ADC and 8 bit L0ADC was not correct in previous attempts: fixed in TELL1 firmware. ADC – 8*L0ADC in the range 0<ADC<2048, in ECAL8 where the calibration constant is 128: all problems disappear ADC>2048, in ECAL8: Saturation at 255 of L0ADC: OK ADC<0: L0ADC=0: OK

14 14 L0ADC vs ADC in ECAL8

15 15 L0ADC in different crates ECAL 8 ECAL 9 ECAL 10ECAL 11ECAL 12ECAL 13ECAL 14 Calib constant = 127: configuration problem One strange event Calib constant = 0: my attempts to mask hot channels ? ECTell07 problem: see Stephane's talk

16 16 Configuration problems ? To configure ECAL for Cosmics:  First launch CAT which configures all FEB with calibration constant equal to 127  Then configure all ECAL crates using PVSS (usually takes several times to clear the errors): all FEB should have the calibration constant equal to 128  Then configure only the Trigger Validation Boards with the correct settings, with CAT.  We see boards still with 127 as calibration constants: were the recipes for these boards really applied ?

17 17 HCAL ADC No Problem in DAQ

18 18 HCAL 2D Map (ADC vs FEB)‏ HCAL 22HCAL 23 Half BoardsBeam pipe hole 3 Dead Channels ? 3 Hot Channels ?

19 19 HCAL L0ADC

20 20 HCAL ADC vs L0ADC Difference between expected and read L0ADC for 127 and 128, as a function of the FEB number 2 FEB with calibration constant of 128, all others with 127: no problem at all for both sets of boards. Default configuration with PVSS is 128. For cosmics run, we changed 128 to 127 for HCAL, for all boards, using PVSS panels: painful process during which I certainly forgot 2 HCAL boards. A cosmics PVSS recipe setting all constants to 127 will be very useful.

21 21 L0Calo Raw banks: electron max First look at the L0Calo DAQ path ! Trigger Cut Do not expect a perfect match because we read more crates that are used for trigger, and one half-crate is not read correctly. L0CaloL0Calo recomputed from CALO DAQ

22 22 L0Calo Raw Bank: hadron max Trigger Cut L0CaloL0Calo recomputed from CALO DAQ Strange events below the cut: can be due to a lot of things to be checked further (bad transmission between Selection Boards and L0DU, bug in decoding software of L0Calo banks, in firmware of Selection Board, etc...)‏

23 23 Conclusions Main problems observed so far (+/-128, L0ADC vs ADC) disappeared:  last cosmics data allow now to see real hardware problems. Setting up calorimeters for cosmics is now rather easy and fast, apart from ECAL Front- End boards and Trigger Validation Boards in PVSS. Still a lot to study (consecutive triggers,...) and probably also other less frequent problems to discover.

24 24 Gallery (ECAL in black, HCAL in red)‏

25 25

26 26

27 27

28 28

29 29

30 30

31 31

32 32

33 33

34 34

35 35

36 36

37 37

38 38


Download ppt "Calorimeter Cosmics Patrick Robbe, LAL Orsay & CERN, 20 Feb 2008 Olivier, Stephane, Regis, Herve, Anatoly, Stephane, Valentin, Eric, Patrick."

Similar presentations


Ads by Google