150 GEV Transfers

Jerry Annala, Peter Bagley
3/24/99

This is a list of the 150 GEV transfers necessary to run Fixed Target and Collider operations.  Shown are the MI ramp wave form, the machine resets and transfer beam synch events and an approximate timing diagram.  Comments about each scenario appear under the picture.

At the bottom of this page is a list of  outstanding issues with the 150 GEV transfer scenarios.
 


 

$C1 is issued once at the beginning of shot set up (multiple times when Tevatron is in a ramping mode).  It is not needed again for injection unless event $C2 has occurred.  $2B and $4D are TLG sourced events.  The number of $13 events for this transfer depends on the success of multi-batch coalescing.  All transfers in this scenario use the P1 line at 150 GEV.  Transfer line load switching is not necessary for this scenario.
 
 
 


 

This scenario occurs while Protons are already stored in the Tevatron (150 GEV store).  Multiple Proton bunches may be stored in the Tevatron when this scenario occurs, or a single bunch.  The time necessary to switch beam lines power supply loads and move Lambertsons (as well as ramp rates of separators) will determine whether we use multiple stored Proton bunches or individual stored Proton bunches.  The transfer from the TEV to the MI uses the A1 beam line. Even if the switch of the beam line takes the maximum 6 seconds, there is plenty of time to do this during MI acceleration.  The impact of the switch would be noticed after this cycle.  There could be several seconds of dead time while the power supplies switch back to the P1 configuration.  The MI waveform in this picture assumes that we are taking shots out of the RR.  If we need to take shots out of the Accumulator, we would want to use a shorter MI cycle (the same that would be used for Pbar transfers).  If we use the shorter $2A ramp, there would possibly be a wait for the A1 line to switch in before transfering from the Tev to the MI.
$2A and $5D are sourced by the TLG.
 


 

Event $ED is issued during Tevatron deceleration (by the sequencer) to prepare the RR for transfers.  Transfer from the TEV to MI is timed off of event $54.  Transfer from the MI to the RR is timed off of event $E0 which is referenced to $D2 (end of MI deceleration) which is referenced to $20.  All transfers in this scenario use the P1 line at 150 GEV.  Transfer line load switching is not necessary for this scenario.  The controls group documentation shows event $A0 being on the RRBS clock and not the MIBS clock.  The other problem with this scenario is that there are no RR events sourced from the TLG.  It would be better if the $E0 would be TLG sourced so the TLG would have knowledge of the RR activity.

It is possible that we will want to tune up this scenario with Protons.  We may be able to use the normal $2B, $4D scenario (if the $2B and $20 up ramps are identical), but it is possible that we will need to transfer Protons from MI to Tev on an event $20.  Using event $20 to transfer Protons to the Tevator could cause complications.  The BSSB does not look at the Tevatron beam permit when allowing beam on $20 cycles.

Events $20 and $54 are sourced by the TLG.
 

The RR stack is prepared for extraction by $EE prior to $E4.  Events $E4, $2A, and $40 are sourced from the TLG.  The $E4 triggers the preparation of the Pbars for transfer from the RR to the MI.  The transfer to the MI is timed off the $2A.  The transfer from the MI to the TEV is timed off the $40.  The transfer to the TEV uses the A1 beam line. Even if the switch of the beam line takes the maximum 6 seconds, there is plenty of time to do this during MI acceleration.  The impact of the switch would be noticed at the end of  this cycle, after the transfer to the Tevatron.  There could be several seconds of dead time while the power supplies switch back to the P1 configuration.

It is possible that we will decide that this is a scenario when we want to break the rule about leaving the beam lines in the Proton line mode after every transfer.  If we need to do many transfers to fill the Tevatron, it may waste valuable time to switch back to the P1 mode each time.  We may have to set up in a dedicated inject Pbar mode where no use of the P1 line is allowed.
 

This is the scenario that we should not have to use.  It is the scenario used in Run I.   Event $9A begins the unstacking process in the Accumulator.  The transfer to the MI is timed off event $2A.  The transfer to the TEV is timed off the $40.  This scenario would be impacted the most by the delays needed to switch power supply loads in the beam line.  Pbars are injected into the MI using the P1 line (at 8 GEV).  The switch to the A1 line (and 150 GEV mode) must take place while Pbars are in the MI.  This may be of concern if the switch takes the full 6 seconds, and the Pbar lifetime is not long.  The transfer to the Tevatron uses the A1 line, and after the cycle is finished the switch back to the P1 line would cause further delays.

Events $2A and $40 are sourced from the TLG.  In this scenario, there are no Accumulator resets sourced from the TLG.  This means that the TLG is unaware that the Accumulator is busy during this time period.  It is worth considering moving the $9A to the TLG.

Outstanding Issues:

Fixed Target Injection:  Without hardware modification, only the first injection cycle will have a $49.  Will this be a problem?

Pbar Ejection from Tev to MI:  Controls group documentation show BS event $A0 as being on RRBS while the Mike Church documentation show it being on MIBS.  Also, there are no RR events source by the TLG in this scenario.  This leaves the TLG with no knowledge of the RR activity.  Tuning up this scenario with Protons will need to be done either using the $2B, $4D scenario, or by transfering Protons to the Tev on $20 cycles.  Using the $20 to tune up this scenario may add substantial complications.  Will the $2B and the $20 be similar enough that we can use the $2B to tune up?

Pbar Injection from RR:  To be efficient with time, we may want to leave the P1/A1 swithc in the A1 line mode while we inject Pbars.  We probably won't be able to decide if this is the right thing to do until we are running the Collider.

Pbar Injection from the Accumulator:  There are no Accumulator events for this scenario sourced by the TLG.  Should event $9A be a TLG reset so the TLG would have knowledge of the Accumulators activity?