Fermilab

Machine Operations Guidance

Unless otherwise noted in the AD Elog by the Machine Coordinator or Run Coordinator, the following is how each machine would like their machine ran. This guidance is meant for normal operations, startup or new installation commissioning periods do not apply.

Beam Priority

  1. g-2
  2. NuMI
  3. Switchyard
  4. BNB

Proton Source
  • Pre-Acc
    • TBD
  • Linac
    • Losses
      • L:TK1RAD < 20 mR/h
      • L:TUNRAD < 200 mR/h
      • L:D7LMSM < 15
    • Efficiency
      • G:LINEFF >= 90%
    • Intensity
      • L:ATOR/L:BTOR ~ 60 mA
      • L:TO1IN > 25 mA
      • L:D7TOR > 22 mA
  • Booster
    • Losses
      • Maintain losses under 0.75 on the B88 normalized loss plot. BLM sum alarms should be active during normal operations, except when tuning
    • Efficiency
      • Efficiency should be 92% minimum

Main Injector
  • MI8
    • Collimator Proton Loss Sum
      • We would like to keep the total proton loss sum on the MI8 collimators to at or below 1% of beam intensity on I:TOR806. The $15s are currently running at this level, the $1Ds are higher but we are working to lower their loss and they may run at their current loss for the time being
      • Naming conventions for the collimator proton loss sum averages are I:MI8PA{Booster Event} (i.e. I:MI8PA5 is the average proton loss sum for the $15s). These devices divided by I:TOR806 gives the percentage. I am working on creating percentage devices.
      • An IRM monitors the total loss and will pull the MI/RR/BNB permits if it’s limit is reached. However, the current hard-coded limit is much higher than we would like to run operationally, I will discuss with controls to modify this.
  • Main Injector/Recycler
    • Event Loss Sum Averages
      • Each MI/RR machine reset event has their own loss sum average device. Each device has its own alarm limits that is calculated based on “best” running. We would like to keep these devices out of alarm, if tuning fails to keep these devices out of alarm please reduce intensity.
      • Naming conventions for these devices are {R|I}:LXSUM{Event}, (i.e. R:LXSUME3 is the loss sum average on the $E3 events)
    • Event Location Loss Averages
      • Each BLM in MI/RR has event specific loss average devices. Each device has it’s own alarm limit that is calculated on “best” running. We would like to keep these devices out of alarm, if tuning fails to keep these devices out of alarm please reduce intensity.
      • Naming conventions for these devices are {R|I}:LX{Location}{Event}, (i.e. R:LX102AE3 is the loss average for R:LI102A on the $E3 events)
    • Event Efficiencies
      • Each operational machine reset event for Recycler and Main Injector have an efficiency device. We would like to keep these devices out of alarm, if tuning fails to keep these devices out of alarm please reduce intensity.
      • Naming conventions for these devices are {R|I}:EFF{Event}, (i.e. R:EFFE3 is the efficiency on the $E3 events)

Of course, if at any time the Operators feel they are getting any of the above alarms in error or that the limits are unreasonable they may contact the MI machine coordinator and he/she may choose to adjust the limits or bypass them.

Muon
  • When beam is available and requested, maintain normal g-2 running conditions, of 16 pulses per combined Muon cycle ($93 & $94)
  • Maintain D:POTAVE > 1.00 E12 protons per pulse on the AP-0 target
  • Maintain D:ICABT close to recent levels of performance, scaled to the present beam intensity
  • A live plot of D:POTAVE, D:ICABT, E:G2T0B, and E:G2DCAY should be running and periodically checked to verify performance
  • Performance issues upstream of the target should be addressed as they are discovered
  • Performance issues downstream of the target should be discussed with the g-2 shifter before addressing and before inserting any additional instrumentation
  • When beam is not requested, immediately remove Muon cycles from the timeline
  • Please contact the Muon Machine Coordinator if further operational guidance is required

External Beamlines
  • BNB
    • Intensity is set by what Booster/MI8 can stably send
    • Repetition rate is set by free slots in timeline, not to exceed 5 Hz (average)
    • If AutoTune gets “stuck”, call the machine coordinator
    • When in doubt, call the machine coordinator
  • NuMI
    • TBD
  • Switchyard
    • TBD