Difference between revisions of "The HPS Run Wiki"

From hps run
Jump to navigation Jump to search
Line 88: Line 88:
 
*9 575 7540 from Counting Room
 
*9 575 7540 from Counting Room
 
== PDL: Stepan Stepanyan ==
 
== PDL: Stepan Stepanyan ==
−
 
  
−
==<font color=red>Every Shift:</font>==
+
== <font color=blue><b> Run Plan: April 23-30, 2015 </b></font>==
−
<font color=blue><b>
 
−
# Follow run plan as outlined by RC
 
−
# Ask MCC if orbit locks are on, they should be.
 
−
# Keep shift summary up-to-date in HBLOG. Record all that happens. </b>
 
−
#* 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 the shift check list for every shifts [https://logbooks.jlab.org/checklists/151]<b>
 
−
# 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)
 
−
# With any issue contact On-Call Experts or RC.
 
−
</b></font>
 
−
 
 
−
==<font color=red size=+2>SVT Instructions</font>==
 
−
<font color=blue>
 
−
<b>Before sending beam to Faraday cup, verify (and page SVT expert if otherwise):</b>
 
−
* 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
 
−
 
 
−
'''The first time sending beam to the Faraday cup after the hall is closed, page the SVT expert.'''
 
−
</font>
 
−
 
 
−
 
 
−
==<font color=red size=+2>Acceptable Beam Conditions:</font>==
 
−
<font color=blue>
 
−
<b> To establish good beam conditions first send beam to the tagger dump (ask MCC to turn ON the tagger).</b>
 
−
# Check position, it should corresponds to previous good settings [https://logbooks.jlab.org/entry/3334787]
 
−
# Check profile using 2C21 and tagger harp scans, it should correspond to previous settings ([https://logbooks.jlab.org/entry/3334749],[https://logbooks.jlab.org/entry/3334751])
 
−
# Beam can be accepted at this level if it is within 20% of previous standards
 
−
# Halo counters TAG-L/T/T2 should be ~10Hz/nA [https://logbooks.jlab.org/entry/3326723],
 
−
<b>While MCC degausses the tagger magnet, turn the chicane ON</b>
 
−
# Strictly follow the procedure in the beam line manual!
 
−
<b>Before sending beam to the Faraday cup</b>
 
−
# Check 3mm collimator is IN
 
−
# Check HPS target is OUT
 
−
# Check SVT is out (position 0 mm)
 
−
<b>Beam to the Faraday cup</b>
 
−
# Tune beam profile with 2H02A harp scan to be wide in X-direction and narrow in Y (see ref [https://logbooks.jlab.org/entry/3334783])
 
−
# Check the beam spot on chromax viewer
 
−
# The halo counter rates before HPS must be low:
 
−
#* UPS-L and UPS-R few Hz/nA,
 
−
#* The tagger counters and downstream counters should count  <<1 Hz/nA
 
−
#* 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 [https://logbooks.jlab.org/entry/3328991]
 
−
# Positions on BPMs must be close to what where before [https://logbooks.jlab.org/entry/3334787]
 
−
# Contact SVT expert to do SVT Wire Scan
 
−
# Ask MCC to establish HPS orbit locks
 
−
# Ask beam to be turned OFF to insert the 4um W target
 
−
<b>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. </b>
 
−
</font>
 
−
 
 
−
==<font color=red size=+2>Every Run:</font>==
 
−
# <b>ECal logs</b>
 
−
#* Pdf output from the ECal monitoring App
 
−
#* FADC & DISC Scalers
 
−
# <b>SVT logs</b>
 
−
#* Occupancies
 
−
#* Timing plots (Max Sample)
 
−
#* Track momenta
 
−
# <b> DAQ logs </b>
 
−
#* Trigger rate GUI
 
−
 
 
−
==<font color=red size=+2>Miscellaneous:</font>==
 
−
'''[http://opweb.acc.jlab.org/CSUEApps/bta03/pd_shiftplan_history.php MCC Daily Meetings]'''
 
−
 
 
−
 
 
−
| valign=top |
 
−
 
 
−
 
 
−
== Run Plan: April 23-30, 2015 (day/swing/owl) ==
 
  
 
During week days, Mon-Thursday, there will be no Day shifts due to work in the hall.
 
During week days, Mon-Thursday, there will be no Day shifts due to work in the hall.
Line 183: Line 114:
 
* If orbit locks are on, call Rafayel for beam trip study. Take 4 hours of beam trip data with wire up; take 4 hours of beam trip data with wire down.
 
* If orbit locks are on, call Rafayel for beam trip study. Take 4 hours of beam trip data with wire up; take 4 hours of beam trip data with wire down.
 
* Absent other requests, take data at 50 nA. Be sure to block Faraday cup if higher current.
 
* Absent other requests, take data at 50 nA. Be sure to block Faraday cup if higher current.
 +
 +
 +
| valign=top |
 +
 +
==<font color=blue><b>General Instructions:</b></font>==
 +
===Every Shift:===
 +
 +
# Follow run plan as outlined by RC
 +
# Ask MCC if orbit locks are on, they should be.
 +
# 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 the shift check list for every shifts [https://logbooks.jlab.org/checklists/151]
 +
# 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)
 +
# With any issue contact On-Call Experts or RC.
 +
 +
 +
===SVT Instructions===
 +
 +
#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
 +
#The first time sending beam to the Faraday cup after the hall is closed, page the SVT expert.
 +
 +
 +
===Acceptable Beam Conditions:===
 +
 +
# <b> To establish good beam conditions first send beam to the tagger dump (ask MCC to turn ON the tagger).</b>
 +
## Check position, it should corresponds to previous good settings [https://logbooks.jlab.org/entry/3334787]
 +
## Check profile using 2C21 and tagger harp scans, it should correspond to previous settings ([https://logbooks.jlab.org/entry/3334749],[https://logbooks.jlab.org/entry/3334751])
 +
## Beam can be accepted at this level if it is within 20% of previous standards
 +
## Halo counters TAG-L/T/T2 should be ~10Hz/nA [https://logbooks.jlab.org/entry/3326723],
 +
# <b> While MCC degausses the tagger magnet, turn the chicane ON</b>
 +
#* Strictly follow the procedure in the beam line manual!
 +
# <b> Before sending beam to the Faraday cup</b>
 +
#* Check 3mm collimator is IN
 +
#* Check HPS target is OUT
 +
#* Check SVT is out (position 0 mm)
 +
# <b> Send beam to the Faraday cup</b>
 +
#* Tune beam profile with 2H02A harp scan to be wide in X-direction and narrow in Y (see ref [https://logbooks.jlab.org/entry/3334783])
 +
#* Check the beam spot on chromax viewer
 +
#* The halo counter rates before HPS must be low:
 +
#*# UPS-L and UPS-R few Hz/nA,
 +
#*# The tagger counters and downstream counters should count  <<1 Hz/nA
 +
#*# 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 [https://logbooks.jlab.org/entry/3328991]
 +
#* Positions on BPMs must be close to what they were before [https://logbooks.jlab.org/entry/3334787]
 +
#* Contact SVT expert to do SVT Wire Scan
 +
#* Ask MCC to establish HPS orbit locks
 +
#* Ask beam to be turned OFF to insert the 4um W target
 +
#<b>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. </b>
  
 
|}
 
|}

Revision as of 15:07, 25 April 2015


[edit]

RC: Raphael Dupre

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

PDL: Stepan Stepanyan

Run Plan: April 23-30, 2015

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

Short Term Schedule: Study Trigger and SVT running conditions.

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

  1. Document all your work in the logbook! Please!
  2. Turn ON the ECal and check for normal scalers (ref: [1])
  3. Call SVT expert. Expert will check conditions and turn on SVT. Only SVT expert moves the SVT!
  4. Take data. Check if DAQ runs properly and if all monitors look reasonable on both SVT and ECal(call experts if needed)

Then, proceed with program

Notes: If you change beam current current, turn orbit locks off first, there is a current - position dependence on the stripline BPMs 2H00 and 2H02. Do NOT change magnet currents when beam is on.

DO NOT RUN MORE THAN 30 MINUTES ABOVE 50 nA WITHOUT THE BEAM BLOCKER
PUT BEAM BLOCKER IN FOR LONG RUNNING AT HIGH CURRENT

  • Make sure DAQ is OK for data taking
  • More Trigger commissioning data runs. See Valery's note on the run Wiki under commissioning trigger.
  • If orbit locks are on, call Rafayel for beam trip study. Take 4 hours of beam trip data with wire up; take 4 hours of beam trip data with wire down.
  • Absent other requests, take data at 50 nA. Be sure to block Faraday cup if higher current.

General Instructions:

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 the shift check list for every shifts [2]
  4. Update the run table on Google Docs.
  5. Perform 2H02A harp scan once per shift or when beam conditions have changed, based on beam monitors (BPMs, halo rates, beam-viewer)
  6. With any issue contact On-Call Experts or RC.


SVT Instructions

  1. 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
  2. The first time sending beam to the Faraday cup after the hall is closed, page the SVT expert.


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 position, it should corresponds to previous good settings [3]
    2. Check profile using 2C21 and tagger harp scans, it should correspond to previous settings ([4],[5])
    3. Beam can be accepted at this level if it is within 20% of previous standards
    4. Halo counters TAG-L/T/T2 should be ~10Hz/nA [6],
  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
    • Tune beam profile with 2H02A harp scan to be wide in X-direction and narrow in Y (see ref [7])
    • 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 and downstream counters should count <<1 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 [8]
    • Positions on BPMs must be close to what they were before [9]
    • Contact SVT expert to do SVT Wire Scan
    • Ask MCC to establish HPS orbit locks
    • Ask beam to be turned OFF to insert the 4um W target
  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.
Long Term Schedule Proposal PowerPoint

AccumulatedCharge.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
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
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
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 4 Sho Uemura
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




Svtpic.png

Ecalpic.png

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