Difference between revisions of "KPP Run"

From clas12-run
Jump to: navigation, search
(Short Term Schedule)
(Procedures)
 
(55 intermediate revisions by 4 users not shown)
Line 11: Line 11:
  
 
<br><br>
 
<br><br>
===[https://wiki.jlab.org/clas12-run/images/7/74/HallB_KPP_Demo.pdf Draft CLAS12 KPP Demo Slides]===
+
===[https://wiki.jlab.org/clas12-run/images/e/e2/Offline_-shift-schedule.pdf Off-line shift schedule]===
 +
 
 +
<br><br>
 +
===[https://wiki.jlab.org/clas12-run/images/8/80/HallB_KPP_Demo_data-3.pdf CLAS12 KPP Demonstration Slides]===
  
 
| valign=top |
 
| valign=top |
Line 40: Line 43:
  
 
| valign=top |
 
| valign=top |
 +
 
===JLab Logbooks===
 
===JLab Logbooks===
 
<font size=3>
 
<font size=3>
Line 56: Line 60:
 
[https://wiki.jlab.org/clas12-run/index.php?title=Template:PhoneNumbers&action=edit Click Here]  to edit Phone Numbers.  Note, you then also have to [https://wiki.jlab.org/clas12-run/index.php?title=KPP_Run&action=edit&section=9 edit this page] to force a refresh.
 
[https://wiki.jlab.org/clas12-run/index.php?title=Template:PhoneNumbers&action=edit Click Here]  to edit Phone Numbers.  Note, you then also have to [https://wiki.jlab.org/clas12-run/index.php?title=KPP_Run&action=edit&section=9 edit this page] to force a refresh.
  
<!-- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE-->
+
<!-- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATEs-->
  
 
= Short Term Schedule =
 
= Short Term Schedule =
Line 64: Line 68:
 
''' Beam energy 6.4 GeV (3 pass) '''<br>
 
''' Beam energy 6.4 GeV (3 pass) '''<br>
 
''' Important: Document all your work in the logbook! '''<br>
 
''' Important: Document all your work in the logbook! '''<br>
 +
== <font color=red>''' Very Successfull Run '''</font>==
 
<!--<font size=3>[https://bluejeans.com/573852742 Bluejeans for Run Meetings on Thursdays and Fridays at 2pm]</font></center>-->
 
<!--<font size=3>[https://bluejeans.com/573852742 Bluejeans for Run Meetings on Thursdays and Fridays at 2pm]</font></center>-->
 
</center>
 
</center>
Line 78: Line 83:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
 +
== <font color=blue>''' Run Plan for February 4-5, 2017 : '''</font>==
 +
 +
*Target position <b> 10.505 </b> (2H01 harp, can be moved using button on the main scaler GUI or using the expert GUI)
 +
*Beam current <b> 5 nA </b> (use Faraday Cup)
 +
*Beam positons on 2H01 nA BPM <b> x=0.38, y=0.905 </b>
 +
*CODA configuration - <b> SECTOR2_SVT (sector2 trigger with SVT) <del>SECTOR2 (sector2 only trigger), FC_DC (6-sectors)</del></b>
 +
*Triger file - <b> trigger/kpp1.trg </b>
 +
*Take data, 2 hours a run
 +
*Keep track of runs, run#, torus seting, target position, # of triggers, start/end time, trigger rate
  
== <font color=blue>''' Run Plan for February 2 - 3, 2017 : '''</font>==
+
=== Plan: ===
 +
# <del>Complete data taking with Sector-2 only, EC-inner high threshold (5000 fADC units)</del>
 +
#<del> Reverse torus polarity, <b> Set point = -1900 A </b>. First ramp down torus to zero, by setting 0 in the set point, then ramp up to -1900 A.</del>
 +
# <del>Take data with reverse field, Sector-2 only, high EC-inner threshold</del>
 +
# <del>Study tracking efficiency: four HV setings: 8, 9, 10, 11, 12, for each HV four threshold settings: 30, 45, 60, 75. 10 min runs each.</del>
 +
# <del>Continue with data taking torus at -1900 A, target at 13.125, DC HV setting #11, thresholds 45 mV </del>
 +
# <del> Switch target (call RC) and continue data taking till Sunday morning </del>
 +
# <del>Change torus polarity. While torus current is changing, perform harp scans and FSD studies (see below)</del>
 +
# <del>(Sunday morning while torus setting gets changed) Perform beam studies (call RC and beamline, <b> Turn off DC HV </b>):</del> done
 +
#*<del>Do harp scans - 2C21, "tagger", and 2H01 </del>
 +
#*<del>Test FSD system, run Struck scaler with 300um dwel time, ask MCC to set FSD trip time integration times for FSD channels (1 old and 3 new) to 1 ms. Un-mask one FSD channel, run collimator with slmall steps to left or right untill it will intercept beam tails. It will raise rates on halo counters.  </del>
 +
# <del>Take one 30 min run with torus at zero </del> done
 +
# Set torus +1900 A, continue data taking, trigger Sector-2 only, high threshold in EC-in (5000 fADC counts)
 +
#* <del>take one run for 3 hours at low luminosity. Move beam in vertical direction up (or down does not matter) with 0.1 mm steps untill rates on downstream counters will be ~5kHz</del>done. x10 lower rates on downstream halo couters (luminosity monitor)
 +
# <del> Take short ~1 hour, random trigger data (Sergei should be in to set  it up). Should happen before goimg to 6-sector trigger ~9 pm </del>
 +
# Switch to 6-sector trigger (some time ~11pm), take data till Monday morning.
 +
# <b> Run ends 6:45 am on Monday. Following has to be done:
 +
#* End the run, turn OFF HVs for all detectors, Start Ramping torus down to zero
 +
#* Retract the target using 2H01 expert GUI, just put -10 in the left "MoveAbs" and hit the return. Motor will go towards 0, and will hit "Lo Limit" limit switch
 +
#* Ask MCC to change beam current to 50nA with small steps, this is to calibrate SLM (data goes to MYA, but you can record beam current and the SLM reading if you want)
 +
#* When finished, got to 50nA, ask MCC to terminate the beam and take the Hall to restricted access.
 +
#* When torus reaches to 0 turn the PS OFF.</b>
 +
<!--
 +
== The Hall was closed and brought to controlled access at 8pm on Thursday, February 2 ==
  
== Start close-up of the Hall at 5pm on Thursday, February 2 ==
+
<b> While no beam, cosmic calibration run is in progress with all CLAS12 detectors ON.
=== Locking up the hall on Fridays ===
+
 
* At 2pm check the status of the activities in the hall and notify RC if there are potential delays for the lockup at 3pm.
+
When ready to get beam, Turn all beamline devices ON, turn all CLAS12 detectors OFF (including SVT)</b>
* Work with the hall work coordinator (Doug Tilles or his designee) to make sure hall is ready for sweep at around 3pm:
+
** Vacuum is good, magnet power supplies (Tagger and Torus) are turned ON and in remote mode, LCW is on.
+
* Make sure experts, beamline, ECal, DC, HTCC, FTOF, and slow controls, checked their systems before the lockup.
+
* When ready notify MCC to start sweep and lockup of the hall.
+
* Make sure all necessary monitoring GUIs are up and running.
+
* Make sure beam viewer screens are up.
+
* When hall reaches "Beam Permit":
+
**  Ramp torus to 10% of max current (380A)
+
** Turn all beamline devices ON, turn all CLAS12 detectors OFF  
+
  
  
Line 100: Line 128:
 
# Log every harp scan
 
# Log every harp scan
 
# Log Main scaler GUI every time conditions change
 
# Log Main scaler GUI every time conditions change
# Follow beam position and current strip charts for 2C21 and 2C24 nA BPMs, make log entry of strip chartes
+
# Follow the beam position and current strip charts for 2C21 and 2C24 nA BPMs, make log entry of strip chartes
 
== Bring beam to FC: ==
 
== Bring beam to FC: ==
 
# Establish beam to the Faraday cup following the Beamline Commissioning Plans, execute 2(g) to 2(k). Note, at some point part of CLAS12 calorimeters must be turned on  
 
# Establish beam to the Faraday cup following the Beamline Commissioning Plans, execute 2(g) to 2(k). Note, at some point part of CLAS12 calorimeters must be turned on  
 
# Log every harp scan
 
# Log every harp scan
 
# Log Main scaler GUI every time conditions change
 
# Log Main scaler GUI every time conditions change
# Follow beam position and current strip charts for 2C21 and 2C24 nA BPMs, make log entry of strip charts
+
# Follow the beam position and current strip charts for 2C21 and 2C24 nA BPMs, make log entry of strip charts
 
# Setup FSD if it is day time and beamline expert is present, 2(l) and 2(m), otherwise skip them
 
# Setup FSD if it is day time and beamline expert is present, 2(l) and 2(m), otherwise skip them
 
# Start bringing the CLAS12 detectors ON and do rate studies , 2(n) and 2(o). When moving target in, consult [[Media:Harp_TargetStick.pdf| 2H01 harp stick drawing]] and 2H01 harp scans performed on step 2(k) to define how far you should move the motor to get carbon target on the beam, first bullet of 2(o).
 
# Start bringing the CLAS12 detectors ON and do rate studies , 2(n) and 2(o). When moving target in, consult [[Media:Harp_TargetStick.pdf| 2H01 harp stick drawing]] and 2H01 harp scans performed on step 2(k) to define how far you should move the motor to get carbon target on the beam, first bullet of 2(o).
 
<b> At this point call DAQ, EC, DC, and FTOF experts, notify them that beam is ready for data taking</b>
 
<b> At this point call DAQ, EC, DC, and FTOF experts, notify them that beam is ready for data taking</b>
 
+
-->
  
 
=== Important Notes: ===
 
=== Important Notes: ===
 +
# '''During beam tune and harp scans Hall-B halo FSD must be masked.'''
 
# '''Do not run more than 60 minutes above 30 nA without the beam blocker in front of Faraday cup. Put beam blocker in for long running at high currents.'''
 
# '''Do not run more than 60 minutes above 30 nA without the beam blocker in front of Faraday cup. Put beam blocker in for long running at high currents.'''
 +
# '''If DAQ crashed/broken: Follow instruction on Documentation tab. If cannot resolved in 20-30 min call DAQ on-call cell phone.'''
 +
# '''With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem.'''
 +
  
 
| valign=top |
 
| valign=top |
  
 
==<font color=blue><b>General Instructions:</b></font>==
 
==<font color=blue><b>General Instructions:</b></font>==
 +
 +
 
<!--
 
<!--
===<font color=magenta><b>DAQ RECOVERY</b></font>===
 
If DAQ crashed/broken:
 
 
# For every daq crash login into clondaq3 as a clasrun then run the following command  
 
# For every daq crash login into clondaq3 as a clasrun then run the following command  
 
#* clasrun@clondaq3:clasrun> <font color='blue'> save_DAQ_logs.pl</font> (See [https://logbooks.jlab.org/files/2016/04/3397123/DAQ_DPM_Crash_0.png])
 
#* clasrun@clondaq3:clasrun> <font color='blue'> save_DAQ_logs.pl</font> (See [https://logbooks.jlab.org/files/2016/04/3397123/DAQ_DPM_Crash_0.png])
Line 125: Line 157:
 
# If the procedure fails to restore DAQ, call Sergey (DAQ on call) without any further disturbing the DAQ status.
 
# If the procedure fails to restore DAQ, call Sergey (DAQ on call) without any further disturbing the DAQ status.
 
-->
 
-->
 +
=== Locking up the hall  ===
 +
* Work with the hall work coordinator (Doug Tilles or his designee) to make sure hall is ready for sweep at around 3pm:
 +
** Vacuum is good, magnet power supplies (Tagger and Torus) are turned ON and in remote mode, LCW is on.
 +
* Make sure experts, beamline, ECal, DC, HTCC, FTOF, and slow controls, checked their systems before the lockup.
 +
* When ready notify MCC to start sweep and lockup of the hall.
 +
* Make sure all necessary monitoring GUIs are up and running.
 +
* Make sure beam viewer screens are up.
 +
* When hall is in "Beam Permit"
 +
**  Ramp torus to 10% of max current (380A)
 +
** Turn tagger magnet ON if beam tune on the tagger dump or tagger yoke dump will be needed (it will be needed if beam comes back after several hours of down)
 +
** Turn all beamline devices ON, turn all CLAS12 detectors OFF
  
 
===Establishing Acceptable Beam Conditions:===
 
===Establishing Acceptable Beam Conditions:===
Line 135: Line 178:
 
#** Positions on both harps should be within 1mm
 
#** Positions on both harps should be within 1mm
 
#** Width on 2C21 should be <~0.1+/-0.05 mm
 
#** Width on 2C21 should be <~0.1+/-0.05 mm
#** Width on tagger harp (2C24) <~0.35 +/- 0.1mm
+
#** Width on tagger harp (2C24) <~0.5 +/- 0.1mm
#* Halo counters UPS-L/R and TAG-L/T/T2 should be ~few Hz/nA [https://logbooks.jlab.org/entry/3376736]
+
<!--#* Halo counters UPS-L/R and TAG-L/T/T2 should be ~few Hz/nA [https://logbooks.jlab.org/entry/3376736]-->
 
<!-- # <b> While MCC degausses the tagger magnet, verify that chicane is ON</b>  
 
<!-- # <b> While MCC degausses the tagger magnet, verify that chicane is ON</b>  
 
#* If not, turn it on.  Strictly follow the procedure in the beam line manual!-->
 
#* If not, turn it on.  Strictly follow the procedure in the beam line manual!-->
Line 143: Line 186:
 
#* If you don't see it immediately, and rates on halo counters are more than 100 Khz, then ask MCC, to change to pulsed (tune mode) beam, and ask to put corrector values. At this point don't accept any CW beam, until beam spot is visible on Downstream Viewer.
 
#* If you don't see it immediately, and rates on halo counters are more than 100 Khz, then ask MCC, to change to pulsed (tune mode) beam, and ask to put corrector values. At this point don't accept any CW beam, until beam spot is visible on Downstream Viewer.
 
#* If MCC operator is not able to tune the beam more than 30 minutes, then please notify RC
 
#* If MCC operator is not able to tune the beam more than 30 minutes, then please notify RC
#* Tune beam profile at CLAS12 target using 2H01A harp. The required beam profile at 2H01A harp is: X-width <~0.25 mm, Y-width <~ 0.25 mm  
+
#* Tune beam profile at CLAS12 target using 2H01A harp. The required beam profile at 2H01A harp is: X-width <~0.3 mm, Y-width <~ 0.3 mm  
 
#* Check and log the beam spot on chromax viewer
 
#* Check and log the beam spot on chromax viewer
 
#* Check rates on halo counters
 
#* Check rates on halo counters
 
#*# UPS-L and UPS-R few Hz/nA,  
 
#*# UPS-L and UPS-R few Hz/nA,  
#*# The tagger counters should count less than Hz/nA and downstream counters should count ~Hz/nA
+
#*# The tagger counters should count less than Hz/nA and downstream counters should count ~Hz/nA,
#* Once all the above is achieved, turn first CLAS12 ECal HV '''ON''' and monitor and log ECal rates
+
#*# Midstream counters few Hz/nA  
 +
#* Once all the above is achieved, turn first CLAS12 ECal HV '''ON''' and monitor and log ECal rates before bringing rest of the detector UP
  
 
=== Setting up the FSD threshold ===
 
=== Setting up the FSD threshold ===
Line 171: Line 215:
 
#* Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
 
#* Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
 
# Perform 2H01A harp scan once per shift or when beam conditions have changed, based on beam monitors (BPMs, halo rates, beam-viewer). During harp scans the HV for DC and HTCC should be OFF.
 
# Perform 2H01A harp scan once per shift or when beam conditions have changed, based on beam monitors (BPMs, halo rates, beam-viewer). During harp scans the HV for DC and HTCC should be OFF.
# '''With any issue contact On-Call Experts or RC''' - do not spend more than 15-20 min trying to fix the problem
 
  
 
| valign=top style="background:#eeeeee;"|
 
| valign=top style="background:#eeeeee;"|
Line 177: Line 220:
 
==Every Run:==
 
==Every Run:==
 
# Log screenshots of:
 
# Log screenshots of:
#* main scaler_hps display
+
#* main scaler GUI display
 
#* Detector occupancy plots
 
#* Detector occupancy plots
 
#* Trigger rate gui
 
#* Trigger rate gui
 +
#* Beam strip charts
  
 
|}
 
|}
Line 200: Line 244:
 
*[https://wiki.jlab.org/clas12-run/images/c/c9/CedManual.pdf CED Manual]
 
*[https://wiki.jlab.org/clas12-run/images/c/c9/CedManual.pdf CED Manual]
 
*[https://wiki.jlab.org/clas12-run/images/7/7e/MON12.pdf MON12 Manual]
 
*[https://wiki.jlab.org/clas12-run/images/7/7e/MON12.pdf MON12 Manual]
 +
*[https://wiki.jlab.org/clas12-run/images/5/5a/OfflineKPPmanual2.pdf KPP off-line Manual]
 +
 +
| valign=top |
 +
===Epics on the web===
 +
*[https://hallbopi.jlab.org/webopi3.3/w WebOPI] (CUE Login)
  
 
|}
 
|}

Latest revision as of 08:18, 21 June 2017

[edit]
Person Phone Number
Run Coordinator 9-757 575-7540 (cell)
Physics Division Liaison 9-757 876-1789 (cell)
Run Group C coordinator 9-757 639-6640 (cell)
Shift Expert 5244 or 9-757 329-4846 (cell)
Shift Worker 5126
MCC-OPS 7048
Crew Chief 7045
Crew Chief 9-757 876-3367 (cell)
Program Deputy 9-757 876-7997 (cell)
Engineering on-call 9-757 748-5048 (cell)
Engineering on-call secondary 9-757 897-9060 (cell)
Radcon (needed for target cell swaps) 9-757 876-1743 (cell)
Gate House Guard 5822
Location Phone Number
Hall-B Floor 5165
Hall-B Space Frame 5170, 5171
Hall-B Forward Carriage 5371
Hall-B Counting Room 5245 (Shift1), 5126 (Shift2)
Hall-B Counting Room 5244 (Expert)
Hall-B Gas Shed 7115
System Phone Number On-Call Person
DC (757) 748-5048 (cell) Engineering On-Call
SVT + MM (757) 541-7539 (cell) Yuri Gotra Primary
SVT + MM (757) 753-7769 (cell) Rafo Paremuzyan (secondary)
ECAL (757) 810-1489 (cell) Cole Smith
FTOF/CTOF (757) 344-7204 (cell) Jose Carvajal
CND (757) 344-7204 (cell) Jose Carvajal
HTCC-LTCC (757) 344-7174 (cell) Youri Sharabian
FT (757) 344-1848 (cell) Raffaella De Vita
BAND (757) 310-7198 (cell) Florian Hauenstein
RICH (757) 344-3235 (cell) Valery Kubarovsky
DAQ (757) 232-6221 (cell) Sergey Boiarinov
Slow Controls (757) 748-6922 (cell) Nathan Baltzell
Beamline (757) 303-3996 (cell) Eugene Pasyuk
Pol. Target On-Call (757)-218-2266 (cell) See schedule or call RC
Polarized Target (757) 746-9277 (cell) Chris Keith
Polarized Target (757) 897-1415 (cell) James Maxwell
Polarized Target (757) 871-5374 (cell) James Brock
Target (not used) (757) 822-9586 (cell) Bob Miller Primary
Target (not used) (757) 897-9060 (cell) Denny Insley Secondary
Counting House C x6000
Counting House D x5504

In case of a problem with superconducting magnets call Engineering on-call first, particularly if it is related to cryo.
For all other superconducting magnet problems call magnet group.
Their schedule and phone numbers are posted on the wall next to the Saclay target computer.




Click Here to edit Phone Numbers. Note, you then also have to edit this page to force a refresh.


CLAS12 KPP run, February 3 to March 3
Beam energy 6.4 GeV (3 pass)
Important: Document all your work in the logbook!

Very Successfull Run

RC: Stepan Stepanyan

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

PDL: Eugene Pasyuk

  • (757) 876-1789
  • 9 876-1789 from Counting Room

Run Plan for February 4-5, 2017 :

  • Target position 10.505 (2H01 harp, can be moved using button on the main scaler GUI or using the expert GUI)
  • Beam current 5 nA (use Faraday Cup)
  • Beam positons on 2H01 nA BPM x=0.38, y=0.905
  • CODA configuration - SECTOR2_SVT (sector2 trigger with SVT) SECTOR2 (sector2 only trigger), FC_DC (6-sectors)
  • Triger file - trigger/kpp1.trg
  • Take data, 2 hours a run
  • Keep track of runs, run#, torus seting, target position, # of triggers, start/end time, trigger rate

Plan:

  1. Complete data taking with Sector-2 only, EC-inner high threshold (5000 fADC units)
  2. Reverse torus polarity, Set point = -1900 A . First ramp down torus to zero, by setting 0 in the set point, then ramp up to -1900 A.
  3. Take data with reverse field, Sector-2 only, high EC-inner threshold
  4. Study tracking efficiency: four HV setings: 8, 9, 10, 11, 12, for each HV four threshold settings: 30, 45, 60, 75. 10 min runs each.
  5. Continue with data taking torus at -1900 A, target at 13.125, DC HV setting #11, thresholds 45 mV
  6. Switch target (call RC) and continue data taking till Sunday morning
  7. Change torus polarity. While torus current is changing, perform harp scans and FSD studies (see below)
  8. (Sunday morning while torus setting gets changed) Perform beam studies (call RC and beamline, Turn off DC HV ): done
    • Do harp scans - 2C21, "tagger", and 2H01
    • Test FSD system, run Struck scaler with 300um dwel time, ask MCC to set FSD trip time integration times for FSD channels (1 old and 3 new) to 1 ms. Un-mask one FSD channel, run collimator with slmall steps to left or right untill it will intercept beam tails. It will raise rates on halo counters.
  9. Take one 30 min run with torus at zero done
  10. Set torus +1900 A, continue data taking, trigger Sector-2 only, high threshold in EC-in (5000 fADC counts)
    • take one run for 3 hours at low luminosity. Move beam in vertical direction up (or down does not matter) with 0.1 mm steps untill rates on downstream counters will be ~5kHzdone. x10 lower rates on downstream halo couters (luminosity monitor)
  11. Take short ~1 hour, random trigger data (Sergei should be in to set it up). Should happen before goimg to 6-sector trigger ~9 pm
  12. Switch to 6-sector trigger (some time ~11pm), take data till Monday morning.
  13. Run ends 6:45 am on Monday. Following has to be done:
    • End the run, turn OFF HVs for all detectors, Start Ramping torus down to zero
    • Retract the target using 2H01 expert GUI, just put -10 in the left "MoveAbs" and hit the return. Motor will go towards 0, and will hit "Lo Limit" limit switch
    • Ask MCC to change beam current to 50nA with small steps, this is to calibrate SLM (data goes to MYA, but you can record beam current and the SLM reading if you want)
    • When finished, got to 50nA, ask MCC to terminate the beam and take the Hall to restricted access.
    • When torus reaches to 0 turn the PS OFF.

Important Notes:

  1. During beam tune and harp scans Hall-B halo FSD must be masked.
  2. Do not run more than 60 minutes above 30 nA without the beam blocker in front of Faraday cup. Put beam blocker in for long running at high currents.
  3. If DAQ crashed/broken: Follow instruction on Documentation tab. If cannot resolved in 20-30 min call DAQ on-call cell phone.
  4. With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem.


General Instructions:

Locking up the hall

  • Work with the hall work coordinator (Doug Tilles or his designee) to make sure hall is ready for sweep at around 3pm:
    • Vacuum is good, magnet power supplies (Tagger and Torus) are turned ON and in remote mode, LCW is on.
  • Make sure experts, beamline, ECal, DC, HTCC, FTOF, and slow controls, checked their systems before the lockup.
  • When ready notify MCC to start sweep and lockup of the hall.
  • Make sure all necessary monitoring GUIs are up and running.
  • Make sure beam viewer screens are up.
  • When hall is in "Beam Permit"
    • Ramp torus to 10% of max current (380A)
    • Turn tagger magnet ON if beam tune on the tagger dump or tagger yoke dump will be needed (it will be needed if beam comes back after several hours of down)
    • Turn all beamline devices ON, turn all CLAS12 detectors OFF

Establishing Acceptable Beam Conditions:

  1. Make sure CLAS12 is OFF When Beam is Turned For the First Time After long Down.
  2. First send beam to the tagger yoke dump:
    • Check that beam type is set to "Photon" (HPS_EPICS->Beam->BTA).
    • Ask MCC to turn ON the tagger magnet and then deliver <10 nA beam.
    • Follow instructions under "Procedures" on the documentation tab for Beamline Commissioning Plans. To tune the beam on tagger yoke dump and perform harp scans, beam current should be <10 nA.
    • Check profile using 2C21 and tagger harp scans, and compare the positions and widths with previous scans ([1],[2])
      • Positions on both harps should be within 1mm
      • Width on 2C21 should be <~0.1+/-0.05 mm
      • Width on tagger harp (2C24) <~0.5 +/- 0.1mm
  3. Send beam to the Faraday cup
    • If the beam optics is correct, then you should immediately see the beam spot on the Downstream Viewer
    • If you don't see it immediately, and rates on halo counters are more than 100 Khz, then ask MCC, to change to pulsed (tune mode) beam, and ask to put corrector values. At this point don't accept any CW beam, until beam spot is visible on Downstream Viewer.
    • If MCC operator is not able to tune the beam more than 30 minutes, then please notify RC
    • Tune beam profile at CLAS12 target using 2H01A harp. The required beam profile at 2H01A harp is: X-width <~0.3 mm, Y-width <~ 0.3 mm
    • Check and log the beam spot on chromax viewer
    • Check rates on halo counters
      1. UPS-L and UPS-R few Hz/nA,
      2. The tagger counters should count less than Hz/nA and downstream counters should count ~Hz/nA,
      3. Midstream counters few Hz/nA
    • Once all the above is achieved, turn first CLAS12 ECal HV ON and monitor and log ECal rates before bringing rest of the detector UP

Setting up the FSD threshold

  • When you are about to calculate FSD limit, it means the beam is already established, and the target is in.
  • To calculate the FSD threshold run the folloing executable
hpsrun@clonpc11> /home/hpsrun/scripts/FSD/Calc_FSD_Threshold.exe
  • Note we use 1 ms integration time, and want 5.5 sigma away from the average rates
  • Allowed tolerable rate increase default is 15%, if that causes many trips, then contact RC, he might suggest to increase that number
  • Make sure if MCC operator set the FSD limit and integration time correctly


Every Shift:

  1. Follow run plan as outlined by RC
  2. If any concern about beam stability, 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 out BTA hourly. Click "Load from EPICS" to automatically fill the left side.
    • Fill and submit the shift checklist in the logbook
  4. Perform 2H01A harp scan once per shift or when beam conditions have changed, based on beam monitors (BPMs, halo rates, beam-viewer). During harp scans the HV for DC and HTCC should be OFF.

Every Run:

  1. Log screenshots of:
    • main scaler GUI display
    • Detector occupancy plots
    • Trigger rate gui
    • Beam strip charts


Clas12design.png