1 Luminosity monitor and LHC operation H. Burkhardt AB/ABP, TAN integration workshop, 10/3/2006 Thanks for discussions and input from Enrico Bravin, Ralph Assmann, Jörg Wenninger, Werner Herr, Roger Bailey and others. Apologies for any omissions (prepared on rather short notice)

2 Outline Importance of luminosity monitoring in operation and commissioning Operational use in (early) operation

3 Introduction Luminosity and background signals are the main figures of merit in operation. Fast, robust, relative luminosity is important to help to bring beams into collision, for tuning and optimisation LHC luminometer spec. : beam lumi every sec, bunch-by- bunch lumi every 10 sec, backgrounds every sec. Absolute lumi and vertex position every minute from experiments. (see LHC-B-ES-0007, Table 5) Some redundancy, particularly in commissioning is essential to understand what we measure and to distinguish signal, background, geometry etc. Needs good communication and signal exchange with experiments

4 LEP status page

5 Luminosity and beam parameters For head-on collisions of round beams and N particles / bunch n b bunches (n b = 1 for bunch Lumi) Reduction factor due to the crossing angle  c is the full crossing angle of ~ 300  rad only really significant (~ 20%) at 7 TeV squeezed  z is the rms bunch length 7.55 cm at 7 TeV

6 Luminosity and collision rates per bunch crossing Simple estimate, using  pp = 100 mbarn According to lum. spec : dynamic range x10 34 cm -2 s -1 What about 450 GeV - pilot beams ? Checks with first collisions at injection energy and optics (450 GeV,  *=18 m) at very moderate intensity (2x10 10, L = cm -2 s -1 ) should be ~ easy and are within the specified dynamic range. Generally : rates in machine luminometer high, statistics no problem. ( pile-up )

7 Coincidences, Pile - up. Nominal conditions : many collisions at each crossing, and only few, ~ O ( ) beam-gas interactions / crossing. Left / right coincidences will be of little use in this case. For commissioning, early running ( + special conditions high-  ) : Pile-up ok up to some L = cm -2 s -1 / bunch Beam-gas background instead maybe much higher than nominal in commissioning and early operation. Coincidences (or some other robust reliable method) needed to allow for reliable, background subtracted luminosity determination.

8 Staged commissioning plan for protons Hardware commissioning Machine checkout Beam commissioning 43 bunch operation ? 75ns ops 25ns ops I Install Phase II and MKB 25ns ops II Stage I IIIII No beamBeam IV I.Pilot physics run First collisions First collisions 43 bunches, no crossing angle, no squeeze, moderate intensities 43 bunches, no crossing angle, no squeeze, moderate intensities Push performance (156 bunches, partial squeeze in 1 and 5, push intensity) Push performance (156 bunches, partial squeeze in 1 and 5, push intensity) Performance limit cm -2 s -1 (limited by event pileup) Performance limit cm -2 s -1 (limited by event pileup) II.75ns operation Establish multi-bunch operation, moderate intensities Establish multi-bunch operation, moderate intensities Relaxed machine parameters (squeeze and crossing angle) Relaxed machine parameters (squeeze and crossing angle) Push squeeze and crossing angle Push squeeze and crossing angle Performance limit cm -2 s -1 (limited by event pileup and  * ) Performance limit cm -2 s -1 (limited by event pileup and  * ) III.25ns operation I Nominal crossing angle Nominal crossing angle Push squeeze Push squeeze Increase intensity to 50% nominal Increase intensity to 50% nominal Performance limit cm -2 s -1 (limited by  *) Performance limit cm -2 s -1 (limited by  *) IV.25ns operation II Push towards nominal performance Push towards nominal performance Beam Strategy needed for ion runs Strategy needed for TOTEM runs Need to revisit 75ns operation

9 Operational use in (early) operation Bring beams into collision Centre collisions in x and y Luminosity / tuning Monitoring of Lumi / Background

10 Bringing beams into collision Initial beam finding and overlap optimization BPM’s at IP: BPM resolution  y(IP)in sigma  * 200  m283  m18  0.5 m 200  m283  m3  18.0 m 50  m70  m4.4  0.5 m 50  m70  m0.7  18 m (S. Fartoukh) From R.A. LCC 11/6/2003 Roughly: 0. 3 mm resolution anticipated from BPMs. Beam sizes ~ 0.4 mm at 450 GeV, 0.1 mm at 7 TeV at  * = 18m BPM resolution should be sufficient to get beams sufficiently close to already see some beam-beam effects (collisions, modified tune signal. )

11 Centre collisions Separation scans in two dimensions ( for LEP only needed in y ) This can be done manually with a set of steering knobs and when safe and reliable enough using a semi - automatic procedure.

12 Continued tuning Continuous lumi / background monitoring needed for optimisation (orbit, tune, waste, …) Monitor and optimise the bunch-by-bunch specific luminosity (divided by I x I ) In the LHC, the two beams may drift apart and require further separation scans.

13 Interference with LHCf To my knowledge so far : Running with LHCf instead of the converter in front of the machine luminometer may significantly interfere with the luminosity / vertex / background measurements. To be clarified ! Angular acceptance rather small : 80 mm / 143 m = 0.56 mrad Concern : sensitivity on beam angles and positions at IP !

14 My preliminary conclusions Continuous, robust luminosity and background monitoring will be essential for operations. We have to be able to clearly distinguish between luminosity, background, and acceptance effects. Some redundancy and robust background subtraction (including coincidences) will be required, particularly at commissioning.