Bunch Numbering P. Baudrenghien AB/RF for the LHC/RF team

March 11, 2007 LHCCWG meeting 2 Numerology For each ring: Convention 1: The 400 MHz RF defines buckets, spaced by one RF period, and numbered from 1 to Convention 2: Bucket 1 is the first bucket after the 3  s long abort gap (defined from bucket to 35640) For 25 ns operation the bunches will occupy buckets 1, 11, 21 etc. with gaps occurring every PS or SPS kicker gap. For 43 bunch operation the bunches will occupy buckets 1, 811, 1621, etc. (see LHC-OP-ES-0003 rev 1.0 for the different schemes).

March 11, 2007 LHCCWG meeting 3 For 25ns operation the bunches will occupy buckets 1, 11, 21 etc. with gaps occurring every PS or SPS kicker gap. (see Figure 1 above reproduced from LHC-OP-ES-0003 rev 1.0).

March 11, 2007 LHCCWG meeting 4 For 43 bunch operation the bunches will occupy buckets 1, 811, 1621, etc. (see Figure 3 above reproduced from LHC- OP-ES-0003 rev 1.0).

March 11, 2007 LHCCWG meeting 5 Revolution Frequency or Orbit For each ring: The revolution frequency (F rev or orbit) is a train of pulses, with one 5 ns long pulse per turn. This pulse “points” to bucket 1. The revolution frequency is obtained by dividing the RF by At a given place in the machine, and at a given beam energy (that is fixed RF frequency) the delay between the pulse and the passage of a bunch in bucket 1 will be fixed from run to run Drift during the ramp: Signals remain in phase with the corresponding beam in IP4 (RF cavities). During the acceleration, the revolution frequency increases by 2.2 ppm for protons ( MHz) and 14 ppm for Pb ( MHz). [See LHC Radio-Frequency Swing, P. Baudrenghien, 14 th Leade meeting, Dec 15 th, 2003]. At a given place, but varying energy (frequency) the F rev -bunch delay will drift during the acceleration ramp due to the difference between signal transmission delay and the beam time of flight. For protons we have 6.5 ps/km, for ions ps/km. Not a problem.

March 11, 2007 LHCCWG meeting 6 Bunch Clock For each ring: The Bunch Clock is a square wave obtained by dividing the RF by 10. The divider is synchronized on the Revolution Frequency (see page 8) At a given place in the machine, and at a given beam energy (RF frequency) the delay between the edge of the Bunch Clock and the passage of a bunch will be fixed from run to run Drift during the ramp: During the proton ramp the Bunch Clock frequency increases by 86.8 Hz (protons) and 550 Hz (Pb). At a given place, but varying energy (frequency) the edge will drift with respect to the bunch. (Same figures as for the Revolution Frequency pulses.)

March 11, 2007 LHCCWG meeting 7 Collision Pattern Ring 1 w.r.t. ring 2: While for each ring bucket 1 and its revolution frequency are locked together, the two bunch patterns can be “rotated” with respect to each other so as to move or set the collision points This is usually done before the injection process with collision (and crossing) points defined before filling. This is the preferred method as it keeps crossing points fixed from injection to physics It can also be done after injection by changing the phase of one RF system (and thereby the corresponding beam) with respect to the other (Machine Development) Convention 3: bunches in bucket 1 of the two rings collide in IP1 (or any other IP. To be agreed now…)

March 11, 2007 LHCCWG meeting 8 Clock Generation All signals are generated in SR4 They are transmitted to CMS (point 5) and BT (dumps) directly And they are transmitted to the other experiments and BI via CCR (optical splitter 1:4) Injection pulses are sent directly to the kickers (not shown above)

March 11, 2007 LHCCWG meeting 9 Reference Clock Generation The Ref Bunch Clock is a stable, constant frequency square wave at MHz (7 TeV proton) obtained by asynchronous division (1:10) of a 400 MHz Reference ( MHz). This 400 MHz Reference is generated by a commercial Low Noise Frequency Synthesizer On the flat top (7 TeV), but before physics starts, the 400 MHz RF1 and RF2 (and the corresponding beams) are rephased onto this 400 MHz Reference. The Bunch Clocks 1 and 2 follow automatically But the Ref Bunch Clock can still be off by 1 to MHz. To fix that the Ref Bunch Clock will be slowly phase shifted by the proper number of 400 MHz periods to bring it in phase with the bunch When physics starts, the delay between the edge of the Ref Bunch Clock and the passage of a bunch will be thus fixed from run to run

March 11, 2007 LHCCWG meeting 10 Availability of clocks during runs see also edms v1, TTC System Upgrade, S. Baron, Sept 29, /35640 and 1/10 dividers are resynchronized at each filling, once, before the first SPS-LHC transfer During resynchronization the output signal disappears for ~1 ms Signal presence and validity is then guaranteed, from shortly before filling until beam dump After beam dump it is not excluded that the RF manipulate its equipment (switch a crate off/on) and signal may disappear. Experiments should make sure that no manual reset is needed in that case Presence of signals is not guaranteed outside physics run due to maintenance needed on the RF equipment, or if basic control facilities are lacking. That applies in particular to shutdown periods The AB/RF group is responsible for the transmission up to the Fiber Optic receivers installed in the experiments (including on-call service). In return the experiments will make for an easy access to this equipment and help implement remote acquisition of the status of the Fiber Optic RX (optical power, presence and frequency of detected RF signal) so that AB/OP and AB/RF can quickly diagnose the transmission

March 11, 2007 LHCCWG meeting 11 Installation planning RF Synchronization equipment being installed/commissioned in SR4 Expect all running by mid-April

March 11, 2007 LHCCWG meeting 12 RF Synchro: Functionalities Synchronization of the SPS-LHC bunch into bucket transfer A train of pulses at the Fiducial Frequency F c (= F revLHC /7 = F revSPS /27 = 1.6 kHz) is sent to the SPS for synchronization By displacing this train by x RF periods the transfer will end-up in bucket+x -> Mechanism to select the injection bucket. Transparent to the SPS We have only one “hardware” bucket selector for both rings It is re-synchronized on two different F rev for the 2 rings -> Mechanism to rotate one ring with respect to the other (before injection) Generation of beam synchronous signals: 40 MHz bunch clocks, revolution frequencies, injection pulses

March 11, 2007 LHCCWG meeting 13 This divider will adjust the relative position of ring 2 vs ring 1. It must be adjusted only once at start-up This sets the RF frequencies before and at injection By changing the programmable delay in the bucket selector one chooses the LHC bucket for transfer. It will be adjusted continuously by OP to change the collision point or for multiple-batch injections. This module generates the pulses sent to the injection kickers LHC LLRF RF Synchronization

March 11, 2007 LHCCWG meeting 14 Commisioning Procedure Label Bucket 1 Beam 1 RF sets all its dividers (VTUs) to offset 0 (ring 1) Inject a single bunch pilot from SPS in ring 1 By definition: This pilot is in bucket 1 Get the pilot to make a few turns (OP) Adjust delay in the F rev sent to the beam dump. Observe our signal at the beam dump location. Compare to bunch position. Adjust. (BT). The abort gap ends just before the passage of pilot (Convention 2) Adjust delay in the 40 MHz/F rev clock received by the experiments (EXP). Best done by various EXP as RF has only 1 signal for all EXP but CMS

March 11, 2007 LHCCWG meeting 15 Commissioning Procedure Label Bucket 1 Beam 2 RF sets all its dividers (VTUs) to offset 0 (ring 2) Inject a single bunch pilot from SPS in ring 2 By definition: This pilot is in bucket 1 Get the pilot to make a few turns (OP) Adjust delay in the F rev sent to the beam dump. Observe our signal at the beam dump location. Compare to bunch position. Adjust. (BT). The abort gap ends just before the passage of pilot (Convention 2) Adjust delay in the 40 MHz/F rev clock received by the experiments (EXP).

March 11, 2007 LHCCWG meeting 16 Problem: Convention 3 is NOT respected. Bunches in bucket 1 must collide in IP1 -> we must rotate ring 2 with respect to ring 1 BI or EXP measures the time difference of passages of the 2 pilots (ring 1 vs ring 2) In IP1 (or another IP) The RF adjusts the VTU ring 2 thereby changing the collision point of the 2 pilots on next injection -> repeat until collision in IP (within ns). This adjustment does not change the position of the bunch ring 2 with respect to the F rev (orbit). (When triggering on F rev the bunch does not move). Conclusion: The RF will adjust the relative positions of the 2 rings but we need a measurement from BI or EXP. This measurement must come from a PU that sees both beams.

March 11, 2007 LHCCWG meeting 17 FAQ Q: Bunches in bucket 1 of both rings meet in IP1 and IP5. Can this be changed ? A: No…but if we want to have single bunch collisions in another IP we should inject in a different bucket of ring 2 (for example) using the bucket selector (page 13). For example for collision in IP2: Inject pilot in bucket 1 ring 1, and pilot in bucket /4 = 8911 ring 2. Reminder: For its Phase Loop to work properly the RF must be told in what bucket the bunch is injected via the Bunch Mask Pattern. By delaying the ring 2 injection bucket by ¼ turn we displace the collision point by 1 octant

March 11, 2007 LHCCWG meeting 18 Q: Should we count in 400 MHz bucket or in 40 MHz bunch clock? A: The RF Bucket Selector counts in RF periods but most hardware is designed for a minimum 25 ns spacing between bunches. So we can use both indexing: bucket 1 -> bunch clock period 1 bucket 11 -> bunch clock period 2 bucket 21 -> bunch clock period 3 …. bucket > bunch clock period 3564 or Q: How about the 43 bunch scheme. Will bunches be numbered 1 to 43? A: They should best be numbered in buckets (1, 811, 1621,…) or in bunch clocks (1, 82, 163, …)