Run Coordination News 19 th November 2018 Sudan

Run Coordination News 19 th November 2018 Sudan Paramesvaran (University of Bristol & CERN) Lucia Silvestris (INFN Bari) Gaelle Boudoul (IN 2 P 3 Lyon) Slides for MB

Brief summary of Run 2 and 2018 pp running

2015: 4. 22 fb-1 2016: 40. 82 fb-1 Run 2 Data-taking efficiency 92. 3% 2017: 50. 25 fb-1 2018: 66. 89 fb-1 19 NOVEMBER 2018 COORDINATION ~ 162 fb-1 delivered to CMS in Run 2 ~ 150 fb-1 collected by CMS in Run 2 RUN Run 2 summary: pp @ 13 Te. V 3

Collected ~94% of delivered LHC luminosity. Record for CMS! 19 NOVEMBER 2018 COORDINATION RUN 2018 pp summary 4

Deadtime ~ 3. 4%, in-line with expectations and essentially irreducible 19 NOVEMBER 2018 COORDINATION Lost ~4 fb-1 this year: ~1. 8 fb-1 lost due to downtime, 2. 2 fb-1 lost due to deadtime RUN 2018 pp summary 5

19 NOVEMBER 2018 COORDINATION Downtime contributions > 100 pb-1 RUN 2018 pp summary Tracker DAQ: One large contribution due to cooling issues, and regular occurrences of FEDs getting stuck ECAL DAQ: Large contribution due to HW issue with 2 FEDs, regular occurrences of FED issues (out-of -sync, sync-loss etc) HCAL DAQ: Several instances of stop/start runs to clear alarms, various event counter mismatches, FED errors. GEM DAQ: Mainly during first introduction to Global running - FED blocking run, recording debug info etc. CTPPS DAQ: FED issues, sending out-of-sequence data, had to spend time to isolate where the problem exactly was. A few one-off hardware incidents coupled with minor but regular incidents which led to downtime. Frequency of these reduced through the year thanks to action of subsystems. Downtime is at a reasonable level, but still continue to debug problems and look for improvements. 6

Current situation, HI Run progress

• 2 weeks of HI run to go, including 1 MD day • Had a slightly rocky start to the program, 2 -3 days delay due to problem with Ion source, and time spent trying to understand losses seen at start of run • Vd. M Scans in all experiments have been performed, CMS scan had to be re-done due to fill being dumped, second attempt all data taken well. • 19 NOVEMBER 2018 COORDINATION RUN LHC Schedule Currently running with 100 ns bunch spacing, aim to go to 75 ns later this week… 8

• 19 NOVEMBER 2018 COORDINATION RUN Run progress Collected 93% of the data so far, most of the losses came in the ramp-up fills where significant tuning of trigger menus and configurations was performed. • Now on to much smoother operation, since we started with the nominal production fills ~600 bunches. • Monitoring closely the rate through to Lustre, and the Lustre occupancy. In case we see rises close to threshold values, procedures are in place to cope. • DPG co-ordination meeting organised for Friday 23 rd November to discuss the first part of the HI data taking 9

19 NOVEMBER 2018 COORDINATION RUN Nominal production fills so far 1

• Due to a problem in that the ‘waist’ of the Beta* at ALICE seems to have shifted away from the RUN Levelling strategy from LPC IP, they currently see a reduced luminosity. They effectively see twice the Beta* that they • To compensate - LPC did an analysis on how best to share this “loss”. From their nominal production scenario they compared levelling IP 1 and 5 at 3 e 27 and lower values. Their analysis showed that levelling IP 1 and 5 at 3 e 27 costs ATLAS/CMS 2% compared to their nominal scheme, but ALICE lose 11%. • With the current 100 ns filling scheme, levelling ATLAS/CMS to 2. 2 e 27 costs us 8% (compared to the LPC nominal), and also costs ALICE 8%. This value was chosen as the levelled value for 100 ns scheme, when we move to the 75 ns scheme this value moves up to 2. 8 e 27. • HI group in CMS are evaluating the current proposal • Table is in back-up showing the different levelling scenarios for the 100 ns filling schemes 19 NOVEMBER 2018 COORDINATION should have. 1

Plan after run Magnet ramp down on Dec 3 rd at 14: 00 • Dec 3 rd • ◦ Beams dumped by 6 am ◦ ECAL and HCAL activities that needs Magnet at 3. 8 T Dec 4 th -5 th -6 th ◦ • All the other activities that can be done with no Magnet. 19 NOVEMBER 2018 COORDINATION RUN • Some contingency until Dec 10 th in the morning. 1

• Call for Shift Leaders and Technical shifter will go out soon RUN • Being discussed now and plan being drawn up with TC Shifts in 2019 • Planning also MWGRs throughout this year, dates will also be posted soon. 19 NOVEMBER 2018 COORDINATION (next week) - just for first block of January 7 th to March 3 rd 1

Back-Up