1. Piquet report Pascal, Yuri, Valentin, Tengiz, Miriam Calorimeter meeting 16 March 2011

2. Outlook First 2011 stable beams last Sunday (13 March). – Successful data taking. – Calo timing scan performed. Main problems before that: – PS/SPD C-side Maraton. – One turbine of HCAL C-side. Other small issues. xCAL HV project modification. Access requests for next technical stop. 2

3. Calo Activity during first 2011 stable beams Timing scans performed for CALO on A and C sides. Detailed analysis is in progress… 3

4. 4 12x~500kevts Fill 1613, 2 colliding bunches during ~6h Activity : COLLISION|TAE Mu 1.2 L0 rate 16 KHz Fill 1615, 2 colliding bunches Activity : COLLISION|TAE

5. PS/SPD C-side Maraton 4 March, 1:30. Maraton LV VFE power supply for C-side stopped working. Fixed by changing the rectifier, which was dead. (Yuri). 9 March. Access to check the Maraton and its cooling. – The temperature map side C in the area of VFE MARATON is similar to that at the side A side: A sideC side Water temperature on input, C 0 15.015.1 Water temperature on output, C 0 21.0 Box temperature, C 0 34.434.3 5

6. Turbine of HCAL C-side 5 March. One (out of two) turbine of HCAL C-side seemed to be dead (L3A03). 9 March. Access to check. The turbine (presumably dead) is working. Probably problem in the control card or bad connectors. Should be checked during next technical stop. 6 Currently we have this:

7. Other problems/issues 25 February (Yuri). Last days several network glitches happened. The consequences for CALO were the following: – HCAL and PRS MV in NOT_READY (Agilent servers lost connection to their Agilents), the remedy was to restart corresponding services via service+ on cadcs01w. – Both control boards in the PRS C side crate 2 went into ERROR at configuring. Cured by Daniel by refreshing their subscriptions via HwTool. 2->15 March. One PRS regulator board in SM1 Top which is slightly above 31 degree. But it was the same last year. 4 March. Current too high on SPD_PS1_CB5_RB1_LVR CH 28 (3.3 0.85 V). Threshold for the alarm increased (Francesc). 5-7 March: PS/SPD HV C side, power status reads very low voltage values. The nominal +6V reads +3.7 V. Also the nominal +150 reads only 68 V. The problem was fixed by Yuri by setting the HV state to STANDBY and then back to OFF. 7

8. 14 March. PS2 FEB11 doesn’t send data. – It already happened 29 October 2010. – This means all delay chips are getting stuck (Stephane). – Not cured by power cycling the crate (L3B02 U)?! First action : open the PVSS of the board, go to the settings page and read/write/read the delay chips. If it does not cure the problem (usually it does but not always) a reset of the Glue which can be accessed from the very same panel must be done. Then a reconfiguration of the board is needed. If all that fails, then power cycling the crate is the way to go. 8 No related alarm published yet, first need some checks The steps to follow are…

9. 15 March. HCAL cell unmasked. The HCAL cell O_02_20 (crate 22 FEB 6 input 11) was found to be masked in the DEFAULT recipe but not masked in PHYSICS. The cell looks OK in the recent LED runs, so it has been unmasked now in the DEFAULT recipe also (Yuri). 9

10. From last night, 16 March HCAL channel unmasked looks fine Some PS hot channels?

11. Orwell v2r4 is ready for the new monitoring service. It is installed at pit. It was back to v2r3 because of the presenter was linked to the old Online release (Olivier). Some Presenter and Calibration Farm monitoring problems. 11 14 March 2011

12. Slight modification in xCAL HV projects 8 March (Yuri): Now in case of burning of a +-6V fuse or opening a MV relay the xCAL HV state will not go to ERROR. Instead, an alarm of type W[arning] (yellow) or E[rror] (orange) will appear at the alarm screen. Piquet should come to mask the faulty lines manually. … and not to forget what is masked 12

13. In the new version of HV project the xCAL LV/MV problems appear only at the Alarm Screen, and stay there until solved 13

14. Access requests for next technical stop Fix problematic PRS trigger cables/boards (ID 74). Try to fix the synchronization problems for the sampling of ECAL trigger data by PRS4FEB01 and PRS4FEB02. Possible solutions might be, replugin cables, changing cables for one with same or different lengths, and changing the PS board if neither of the previous options worked. ECAL Integrator readout board side C (ID 77). Try to fix the ECAL C Integrator readout by tuning the SPECS timing. Turbine in L3A03 HCAL side C (ID 79). Repair the monitoring system. 14

15. BACKUP 15

16. 16 Run #PS/SPDECALHCAL 87092222/2222/42/6 87093202/2222/42/6 87094182/2202/422/6 870952/32/5222/5 8709622/32/5222/5 87097162/22/5222/5 A-side CROC fine/coarse delays Default values: Ecal 102/5 Hcal 122/6 PS 102/3 13 March scans Run #PS/SPDECALHCAL 87100222/2222/42/6 87101202/2202/422/6 87102182/32/5222/5 871032/32/5222/5 8710422/22/5222/5 C-side CROC fine/coarse delays 14 March scans Run #ECALHCAL 87158102/5122/6 8716092/5112/6 8716182/5102/6 8716272/592/6 87163112/5132/6 87164132/5152/6 Fill 1613 Fill 1615

17. Other 2 Mar (Valentin): – Maybe a higher TELL1 desync rate in the HCAL (?) 4 Mar: – PRS LED channels on A side in error (have status -1 whatever switched on or off). The problem disappeared with a status refresh. 17

18. 18