1. Calorimeter global commissioning: progress and plans Patrick Robbe, LAL Orsay & CERN, 25 jun 2008

2. 2 Summary Full DAQ chain tested:  cosmics are seen in ECAL, HCAL, PRS and SPD Cosmics are triggered with ECAL and HCAL in coincidence ECAL/HCAL are time-aligned with Muon both in DAQ and Trigger.

3. 3 Operations (1)‏ Data are recorded either:  from the main console  or from the CA1 calorimeter global project: this now works « fine » (ie after 1 or 2 or N days of struggle we have data on disk)‏ One try was made to take cosmics interleaved with LED in the same run. My interpretation was that it was not 100% successful but it has to be redone. Databases:  For the Selection Boards, we now use the ConfigurationDB: the configuration recipes are taken from the Database.  Then we know when we analyse the data what was the configuration applied to the boards.

4. 4 Operations (2)‏ Databases:  The plan is to use for the Selection Boards also: the archive database, to store and retrieve later the values of key registers, such as the masks to know later what was the real configuration when we took cosmics the « condition » database, to be able to tell automatically to the monitoring software what boards are masked in order not to detect fake errors.  The same thing would also be useful (at least): For the TVB to know the masks applied For the Maraton power supplies to follow the current in each crate (maybe useful to locate problems with M24 serializers): I will provide Vincent with a list of quantities we would like in the archive database

5. 5 Operations (3)‏ HV:  phone call to Anatoly to setup the high voltage on Calorimeters, now put it at Cosmics gain also on Inner ECAL parts to collect useful data for Yasmine's analysis.  HV is decreased by Anatoly to nominal HV (or to 0) when cosmics runs are finished. Timings:  One cosmics run has been taken with fine tunings for timing settings for HCAL, but not with ECAL yet.  ECAL fine tunings to be used at the next occasion.

6. 6 Last Cosmics Run: HCAL (1)‏ Position of triggers in HCAL One problematic Front-End Board, removed from the Trigger: has been replaced successfully yesterday One hot channel

7. 7 Last Cosmics Run: HCAL (2)‏ Comparison DAQ/Trigger The masked board (solved)‏ Some border effect when choosing the candidate address in the software (solved)‏ The HCAL path alone is OK !

8. 8 Last Cosmics Run: HCAL (3)‏ Since an empty plot is not convincing... Introducing artificial bug in neighbour treatment:

9. 9 Last Cosmics Run: HCAL (4)‏ SumEt (difference between seen and expected, all errors are due to the missing board)‏

10. 10 Last Cosmics Run: ECAL (1)‏ 5 masked boards (see later): replaced last week Hot Cells

11. 11 Last Cosmics Run: ECAL (2)‏ Comparison DAQ/Trigger Problems are seen only in the ½ crates with the missing boards: everything else is fine

12. 12 Problems with EHCAL FEB 6 boards (5 ECAL + 1 HCAL) showed problems for the trigger, 4 problems were related to the M24 serializer known to have problems. We think the boards developed this problem when changes where made to the CROC configuration sequence: during ~1 day random values, varying at high frequency. 4 of the boards have been repaired and changed This may happen again... (boards will be permanently repaired beginning 2009)‏

13. 13 Masking Channels Hot channels (or bad boards) may appear, and have to be masked. Several levels:  Mask in L0DU: mask all calorimeter  Mask in Selection Board: mask one HCAL board or one ½ ECAL crate - > has to be propagated offline  Mask in TVB: mask one full ECAL board -> has to be propagated offline  Mask in Trigger PGA of FEB: mask one cell, but if it is a neighbour cell, this must be done in different boards -> has to be propagated offline  Set Calibration constant in FE PGA to 0: one place and info is contained in CALO banks  Set PM HV to 0 ? What is the best solution ? Should we define now recipes for cosmics masking known hot cells ?

14. 14 Trigger with SPD/PRS SPD multiplicity trigger has been tested with RAM patterns, with simple algorithm in L0DU: trigger part is working correctly, has to be time aligned with the other triggers. PRS information arrives much later than expected with respect to ECAL information (see Eric's talk): we need to delay a lot ECAL in the trigger path, and then increase the computation time of the L0Calo path (which is limited !)‏ Understanding is needed: this problem affects the TVB firmware which may to be changed, but also time alignment constraints from all other detectors have to be taken into account. But we need to complete detailed tests before knowing exactly the situation.

15. 15 Conclusions (trigger oriented)‏ HCAL trigger alone is well tested and debugged: with last corrections, it works as expected (SumEt and EtHadron): it is the L0 trigger which will mainly be used for the first beams. ECAL addition to HCAL is under test (but will probably not be used at the beginning)‏ ECAL alone works also correctly:  Need to test validation by PRS to be in the realistic conditions

16. 16 Plans Additional cosmics runs would be useful to check:  Precise time alignment, with timings corrections,  ECAL+HCAL addition in trigger path,  Trigger with SPD and PRS,  Time-alignment with Muon detector,... In parallel, it would be useful to prepare for beam particles conditions:  HV settings, calibration constants,  Noise trigger rates as a function of threshold,  Calibration + real triggers at the same time (we should see only one trigger, we seem to see several ones)‏