Difference between revisions of "The HPS Run Wiki"

From hps run
Jump to navigation Jump to search
Line 123: Line 123:
 
* SVT HV will trip off automatically  
 
* SVT HV will trip off automatically  
 
# Check the FSD GUI to see if high rates in the HPS halo counters generated the trip
 
# Check the FSD GUI to see if high rates in the HPS halo counters generated the trip
−
# If it's not an HPS halo counter trip, MCC will restore the beam as usual (follow to their own instructions). As soon beam is back and stable restore SVT HV.
+
# If it was not an HPS halo counter trip, MCC will restore the beam as usual (following their own instructions). As soon beam is back and stable, restore SVT HV.
−
# If it is an HPS halo counter trip, MCC will not restore the beam. Inform MCC that we will get back to them when we are ready for beam.
+
# If it was an HPS halo counter trip, MCC will not restore the beam. Inform MCC that we will get back to them when we are ready for beam.
 
#* Retract the SVT to its 1.5 mm stations, both top and bottom.  
 
#* Retract the SVT to its 1.5 mm stations, both top and bottom.  
 
#* Tell MCC we are ready for beam.
 
#* Tell MCC we are ready for beam.
−
#* Once beam is restored, confirm that 2H02 beam positions x and y are as desired; and confirm that halo counter rates are as expected.
+
#* Once beam is restored, confirm that both 2H02 beam positions x and y are as desired and halo counter rates are as expected.
−
#* Once beam is stable for ~ 1 minute, restore SVT HV, and the SVT to its nominal position.
+
#* Once beam is stable for ~1 minute, restore SVT HV and the SVT to its nominal position.
 
# Resume data taking.
 
# Resume data taking.
  
Line 134: Line 134:
  
 
# Follow run plan as outlined by RC
 
# Follow run plan as outlined by RC
−
# Ask MCC if orbit locks are on, they should be.
+
# Ask MCC if orbit locks are on (they should be).
−
# Keep shift summary up-to-date in HBLOG. Record all that happens.
+
# Keep shift summary up to date in HBLOG. Record all that happens.
 
#* Check on white board all scalers, strip charts and monitoring plots that need to be logged regularly
 
#* Check on white board all scalers, strip charts and monitoring plots that need to be logged regularly
 
#* Document any beam condition change and send scaler GUIs to HBLOG
 
#* Document any beam condition change and send scaler GUIs to HBLOG
−
#* Fill the shift check list for every shifts [https://logbooks.jlab.org/checklists/151]
+
#* Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
−
# Update the run table on [https://docs.google.com/spreadsheets/d/1l1NurPpsmpgZKgr1qoQpLQBBLz1sszLz4xZF-So4xs8/edit#gid=43855609 Google Docs].
 
 
# Perform 2H02A harp scan once per shift or when beam conditions have changed, based on beam monitors (BPMs, halo rates, beam-viewer)
 
# Perform 2H02A harp scan once per shift or when beam conditions have changed, based on beam monitors (BPMs, halo rates, beam-viewer)
−
# With any issue contact On-Call Experts or RC.
+
# '''With any issue contact On-Call Experts or RC'''
  
 
===Every Run:===
 
===Every Run:===
 
# '''After''' "Prestart" but '''before''' "Go", [https://logbooks.jlab.org/entry/3337933 Check ECal Latency]
 
# '''After''' "Prestart" but '''before''' "Go", [https://logbooks.jlab.org/entry/3337933 Check ECal Latency]
 
# After "Go":  [https://logbooks.jlab.org/entry/3337784 Check SVT Occupancy]
 
# After "Go":  [https://logbooks.jlab.org/entry/3337784 Check SVT Occupancy]
−
# Update the run spreadsheet.
+
# Update the run spreadsheet on [https://docs.google.com/spreadsheets/d/1l1NurPpsmpgZKgr1qoQpLQBBLz1sszLz4xZF-So4xs8/edit#gid=43855609 Google Docs].
 
<!--# Do NOT do this:  <s>After end of a Non-Junk run, [https://logbooks.jlab.org/entry/3337942 Copy the Run To Tape]</s>-->
 
<!--# Do NOT do this:  <s>After end of a Non-Junk run, [https://logbooks.jlab.org/entry/3337942 Copy the Run To Tape]</s>-->
 
# See the '''whiteboard''' for everything else that should be done on a per-run basis.
 
# See the '''whiteboard''' for everything else that should be done on a per-run basis.

Revision as of 18:12, 13 May 2015


[edit]
Daily Run Meeting at 15:00
First rule of HPS: Document all your work in the logbook!

RC: Nathan Baltzell

  • (757) 575-7540
  • 9 575 7540 from Counting Room

PDL: Stepan Stepanyan

Run Plan for May 10 - 18, 2015:

During week days, Mon-Thursday, there will be no Day shifts due to work in the hall.

We will be running with 1.05GeV beam. This beam needs to be carefully restored, first to the tagger dump, then to the alcove and Faraday cup screen. See detailed instructions in the right pannel.

Short term schedule:

  1. Turn ON the ECal and check for normal scalers ([1])
  2. Call SVT expert. Expert will check conditions and turn ON the SVT Only SVT expert should move the SVT!
  3. Take data at 50 nA
    • Check if DAQ runs properly and if all monitors look reasonable on both SVT and ECal (call experts)
    • Log errors for each DAQ crash
    • Use v7TurboBurst.trg trigger file
  4. Keep an eye on beam current, and beam positions at 2H02 BPM: x = -1.78 mm , y = -0.70 mm.

Miscellaneous Notes:

  1. If you change beam current current, turn orbit locks off first, there is a current - position dependence on the stripline BPMs 2H00 and 2H02
  2. Do NOT change magnet currents when beam is on
  3. Do not run more than 30 minutes above 50 nA without the beam blocker put beam blocker in for long running at high current

General Instructions:

Recovering from beam trips when running SVT at 0.5 mm

  • SVT HV will trip off automatically
  1. Check the FSD GUI to see if high rates in the HPS halo counters generated the trip
  2. If it was not an HPS halo counter trip, MCC will restore the beam as usual (following their own instructions). As soon beam is back and stable, restore SVT HV.
  3. If it was an HPS halo counter trip, MCC will not restore the beam. Inform MCC that we will get back to them when we are ready for beam.
    • Retract the SVT to its 1.5 mm stations, both top and bottom.
    • Tell MCC we are ready for beam.
    • Once beam is restored, confirm that both 2H02 beam positions x and y are as desired and halo counter rates are as expected.
    • Once beam is stable for ~1 minute, restore SVT HV and the SVT to its nominal position.
  4. Resume data taking.

Every Shift:

  1. Follow run plan as outlined by RC
  2. Ask MCC if orbit locks are on (they should be).
  3. Keep shift summary up to date in HBLOG. Record all that happens.
    • Check on white board all scalers, strip charts and monitoring plots that need to be logged regularly
    • Document any beam condition change and send scaler GUIs to HBLOG
    • Fill and submit the shift checklist in the logbook
  4. Perform 2H02A harp scan once per shift or when beam conditions have changed, based on beam monitors (BPMs, halo rates, beam-viewer)
  5. With any issue contact On-Call Experts or RC

Every Run:

  1. After "Prestart" but before "Go", Check ECal Latency
  2. After "Go": Check SVT Occupancy
  3. Update the run spreadsheet on Google Docs.
  4. See the whiteboard for everything else that should be done on a per-run basis.

Setting up chicane for E=1.056 GeV

Note: This requires only Beam Permit and NO beam to HPS / Faraday Cup. This CAN be done before or during tuning beam on the Tagger Dump.

  1. Turn on chicane power supplies following provided instructions on the documentation page on "Turning Chicane ON/OFF"
  2. When supplies are ready - set the analyzing magnet power supply (Hall-B PS power supply) to I=369.6A
  3. Set the frascati magnet power supply (Hall-B mini-T power supply) to i=707A

SVT Instructions:

  1. Turn SVT completely OFF (Bias, FEB, Flange) when entering Beam Permit.
  2. Before sending beam to Faraday cup, verify (and page SVT expert if otherwise):
    • SVT should be open: "Position" at 0.000 mm in the main scaler_hps GUI
    • SVT HV is off: all red/green indicators RED in SVT bias GUI
  3. The first time sending beam to the Faraday cup after the hall is closed, page the SVT expert.

ECAL Instructions:

  • For additional info on beam quality, HV can be ON when Tagger Magnet is on and tuning beam to the Tagger Dump.
    • To be useful, this requires DAQ Prestarted and ECAL Scaler GUIs running and monitored.
  • HV must be OFF during FIRST delivery of beam to the Faraday Cup after tuning to the Tagger Dump.
    • Only after stable beam established to Faraday Cup can HV can be turned ON.
  • HV should be OFF when running beam studies with Struck scalers with 1 mm wire or tuning collimator position.

Acceptable Beam Conditions:

  1. To establish good beam conditions first send beam to the tagger dump (ask MCC to turn ON the tagger).
    1. Check the beam position on the tagger viewer, it should be approximately in the center of the screen
    2. Check profile using 2C21 and tagger harp scans, and compare the positions and widths with previous scans ([2],[3]). Positions on both harps should be with +/- 1mm, widths on 2C21 shoud be ~0.05 within 0.05 mm, and on the tagger harp ~0.35mm within 0.1mm.
    3. Halo counters TAG-L/T/T2 should be ~10Hz/nA [4],
  2. While MCC degausses the tagger magnet, turn the chicane ON
    • Strictly follow the procedure in the beam line manual!
  3. Before sending beam to the Faraday cup
    • Check 3mm collimator is IN
    • Check HPS target is OUT
    • Check SVT is out (position 0 mm)
  4. Send beam to the Faraday cup
    • Ask MCC to establish ~25 nA beam with HPS orbit locks on (We need HallBHPSOrb not HallBOrb configuration)
    • Tune beam profile with 2H02A harp scan to be wide in X-direction and narrow in Y (see ref [5])
    • Check the beam spot on chromax viewer
    • The halo counter rates before HPS must be low:
      1. UPS-L and UPS-R few Hz/nA,
      2. The tagger counters should count <Hz/na and downstream counters should count ~Hz/nA
      3. The halo counter rates on HPS, HPS-L/R/T/SC, depends on the collimator and HPS chicane settings, but should not be more than 100 Hz/nA [6]
    • Positions on BPMs must be close to what they were before [7]
    • Insert the 4um W target without turning off the beam.
  5. Before accepting beam, make sure all the previous conditions are met. Always read previous log entries, compare settings of BPMs and correctors with previous settings using scaler_hps GUI.


Charge.png

Run Coordinator
March 1 - March 11 Stepan Stepanyan
March 12 - March 18 Francios-Xavier Girod
March 19 - April 1 John Jaros
April 2 - April 8 Nathan Baltzell
April 9 - April 15 Takashi Maruyama
April 16 - April 22 Maurik Holtrop
April 23 - April 29 Raphael Dupre
April 30 - May 6 Takashi Maruyama
May 6 - May 11 Nathan Baltzell
May 12 - May 19 Stepan Stepanyan
Physics Division Liaison
Stepan Stepanyan


Beamline On-Call
Takashi Maruyama
May 5 - May 11 Francios-Xavier Girod
May 12 - May 19 Stepan Stepanyan
DAQ On-Call
NOW Sergey Boyarinov
SlowControls On-Call
March 1 - March 18 Hovanes Egiyan
March 19 - April 1 Stepan Stepanyan
April 22 - April 29 Bryan McKinnon
April 30 - May 4 Sho Uemura
May 5 - May 19 Nerses Gevorgyan
ECAL On-Call
March 1 - March 9 Andrea Celentano
March 9 - March 23 Nathan Baltzell
March 23 - March 30 Holly Vance
March 30 - April 13 Gabriel Charles
April 13 - April 20 Raphael Dupre
April 20 - April 27 Michel Garcon
April 27 - May 4 Holly Vance
May 5 - May 14 Nathan Baltzell
May 14 - May 18 Holly Vance
SVT On-Call
March 8 - March 14 Sho Uemura
March 15 - March 28 Omar Moreno
March 29 - April 4 Pelle Hansson
April 5 - April 8 Omar Moreno
April 9 - April 19 Matt Graham
April 20 - April 26 Tim Nelson
April 27 - May 18 Sho Uemura




Svtpic.png

Ecalpic.png

Retrieved from "https://wiki.jlab.org/hps-run/index.php?title=The_HPS_Run_Wiki&oldid=859"