Difference between revisions of "Run Group K"

From clas12-run
Jump to: navigation, search
(Short Term Schedule)
(Short Term Schedule)
 
(97 intermediate revisions by 5 users not shown)
Line 73: Line 73:
 
</center>
 
</center>
  
== RC: Annalisa D'Angelo ==
+
== RC: Volker Burkert ==
 
* (757) 575-7540   
 
* (757) 575-7540   
 
* 9 575 7540 from Counting Room
 
* 9 575 7540 from Counting Room
* [mailto:annalisa@jlab.org annalisa@jlab.org]
+
* [mailto:burkert@jlab.org burkert@jlab.org]
  
== PDL: Eugene Pasyuk ==
+
== PDL: Daniel S. Carman ==
 
*  (757) 876-1789  
 
*  (757) 876-1789  
 
* 9 876-1789 from Counting Room
 
* 9 876-1789 from Counting Room
* [mailto:pasyuk@jlab.org pasyuk@jlab.org]
+
* [mailto:carman@jlab.org carman@jlab.org]
  
 
<br>
 
<br>
  
 
* '''Note 1: Be very mindful of the background rates in the halo counters, rates in the detectors, and currents in the SVT for all settings to ensure that they are at safe levels.'''
 
* '''Note 1: Be very mindful of the background rates in the halo counters, rates in the detectors, and currents in the SVT for all settings to ensure that they are at safe levels.'''
The integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and the rates on the midstream counters have to be in the range 10-20 Hz (acceptable up to 50 Hz) @50 nA. Counting rates in the range of hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.
+
** The integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and the rates on the midstream counters have to be in the range 10-20 Hz (acceptable up to 50 Hz) @50 nA. Counting rates in the range of hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.
  
* ''' Note 2: At the end of each run, follow the standard DAQ restart sequence '''
+
* ''' Note 2: At the end of each run, follow the standard DAQ restart sequence ''':
"end run", "cancel", "reset", then if the run ended correctly, '''"download", "prestart", "go"'''. If the run did not end correctly or if any ROCs had to be rebooted, "configure", "download", "prestart", "go".
+
** "end run", "cancel", "reset", then if the run ended correctly, '''"download", "prestart", "go"'''. If the run did not end correctly or if any ROCs had to be rebooted, "configure", "download", "prestart", "go".
 
+
** After each step, make sure it is complete in the Run Control message window. If a ROC has crashed, find which one it is and issue a roc_reboot command and try again. Contact the DAQ expert if there are any questions.
After each step, make sure it is complete in the Run Control message window. If a ROC has crashed, find which one it is and issue a roc_reboot command and try again. Contact the DAQ expert if there are any questions.
+
  
 
* '''Note 3: Nominal beam positions: <font color=red>''' ''' 2C21A (X= - 0.37 mm, Y=0.33 mm) ''',''' 2C24A (X=0.2 mm, Y=0.3 mm) ''', '''2H01 (X=1.1 mm, Y=-2.0 mm)''' </font>  
 
* '''Note 3: Nominal beam positions: <font color=red>''' ''' 2C21A (X= - 0.37 mm, Y=0.33 mm) ''',''' 2C24A (X=0.2 mm, Y=0.3 mm) ''', '''2H01 (X=1.1 mm, Y=-2.0 mm)''' </font>  
Line 115: Line 114:
 
*'''Note 9: Reset CLAS12MON frequently to avoid histogram saturation.'''
 
*'''Note 9: Reset CLAS12MON frequently to avoid histogram saturation.'''
  
*'''Note 10: Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/?reference=3634145 https://clas12mon.jlab.org/mon12/histograms/]'''
+
*'''Note 10: Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/?reference=3634894 https://clas12mon.jlab.org/mon12/histograms/]'''
  
*'''Note 11 Do not Turn OFF MVT HV: Instead go to 'Restore settings' from the MVT overview screen:
+
*'''Note 11: Do not Turn OFF MVT HV: Instead go to 'Restore settings' from the MVT overview screen:
 
*# SafeMode.snp for beam tuning and Moeller runs
 
*# SafeMode.snp for beam tuning and Moeller runs
 
*# MV_HV_FullField.snp for full solenoid field
 
*# MV_HV_FullField.snp for full solenoid field
 
*# MV_HV_MidField.snp wgeb solenoid < 4T
 
*# MV_HV_MidField.snp wgeb solenoid < 4T
 
'''
 
'''
*'''NOTE 12 Check the vacuum periodically, make sure vacuum id not higher than 5e-5 '''
+
*'''NOTE 12: Check the vacuum periodically, make sure vacuum is not higher than 5e-5 '''
  
*''' NOTE 13 Always reset the CFD threshold after all power off/on on the CND CAMAC crate'''  
+
*'''NOTE 13: Always reset the CFD threshold after all power off/on on the CND CAMAC crate'''  
After the CAMAC crate (camac1) holding the CND CFD boards is switched off for any reason, it is mandatory to reset the associated thresholds typing the
+
** If the CND CAMAC CFD crate (camac1) is switched off for any reason, it is mandatory to reset the thresholds via the command: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0
following command from any clon machine terminal: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0
+
** If this command fails and the crate is not responding, reboot it as follows: roc_reboot camac1
  
If this command is failing and the crate is not responding, reboot it as follows: roc_reboot camac1
+
*'''NOTE 14: To solve common SVT issues see [https://logbooks.jlab.org/files/2018/10/3615766/svt_problem_solving_0.pdf SVT problem solving]'''
  
*'''NOTE 14: As of 10/25, the issue of detector scalers being frozen and starting a new run has been resolved.''' Shift workers should anyway check routinely scalers to verify they update correctly and make a logbook entry if anomalies are observed after starting a new run.
+
*'''NOTE 15: To solve common RICH issues (missing tiles, DAQ crash due to rich4 crate etc) follow https://logbooks.jlab.org/entry/3562273'''
  
*'''NOTE 15: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766'''
+
*'''NOTE 16: Every DAY shift do the RICH recovery procedure (between runs or better when accelerator is dead) described in  https://logbooks.jlab.org/entry/3633487''
  
*'''NOTE 16: To solve common RICH issues (missing tiles, DAQ crash due to rich4 crate etc) follow https://logbooks.jlab.org/entry/3562273'''
+
*'''NOTE 17: CLAS12 is configured with FT-Off - Do not turn on LV or HV for any of the FT components (Cal, Hodo, Trk)
 
+
*'''NOTE 17: Every DAY shift do the RICH recovery procedure (between runs or better when accelerator is dead) described in  https://logbooks.jlab.org/entry/3633487'''
+
  
 
{| {{TableStyle1}}  
 
{| {{TableStyle1}}  
Line 143: Line 140:
  
 
== <font color=blue>''' Run Plan:'''</font>==
 
== <font color=blue>''' Run Plan:'''</font>==
<i>(Updated: Nov. 28, 2018 at 9:43 a.m.)</i>
+
<i>(Updated: Dec. 16, 2018 at 14:50hrs)</i>
<!--* Before beam delivery ramp torus to -3770 A (100% field - negatives outbending) and solenoid to 2416 A (100% field); empty target and turn all detectors off except Micro Megas
+
 
* When MCC tells that beam is going to be available call RC at (757)575-7540
+
* Update the reference harp scan links on the run wikipage (the RC should do this)
* Tune beam in upstream beamline following nominal procedures [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf Establish Physics Quality Beam]
+
''' Turn on all CLAS12 detectors (note that FT components should be left off as they are not used in this part of the run)'''
* Take Moller run [[Media:clas12moller.pdf|Performing M&oslash;ller Runs]]
+
*'''In the following use the BPM positions: 2C21A: x=-0.14, y=0.460; 2C24A: x = 0.290, y=0.290 ; 2H00: x=1.3, y=1.0; 2H01: x=1.13, y=-1.91'''
* Turn HV of FTCal onto monitor Beam position. Tune 5 nA beam to Faraday Cup following nominal procedures (updated by Stepan) [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf Establish Physics Quality Beam]
+
 
* Ensure the beam position at the target is optimized at 5 nA and record the new nominal beam positions.
+
'''Plan until Thursday morning 6:00:'''
* Turn beam off and fill target
+
 
* Turn beam on and ask for 5 nA beam current - turn all detectors on - check detectors and halo counter rates
+
* Trigger file: rgk_v6_200MeV.trg, HWP IN. Beam current at 35nA. Run until 1,000M events are collected.
* Start DAQ to perform Trigger Studies. Trigger file: '''rgk_v2.trg ''' – check rates, prescaling and beam current
+
* Trigger file: rgk_v6_150MeV.trg, HWP IN. Beam current at 5nA. Take data until Wednesday 8:00am.
* Ask for 20 nA beam current take a short run enough to accumulate monitor plots and take a screenshot of the trigger rates, DAQ window with statistics GUI and monitoring histograms
+
* Trigger file: rgk_v6_300MeV_random_30KHz.trg, HWP IN. Beam currents at 10nA, 35nA, 60nA, 75nA. Collect 200M events at each current (~2hrs per current)
* Ask for 30 nA beam current take a short run enough to accumulate monitor plots and take a screenshot of the trigger rates, DAQ window with statistics GUI and monitoring histograms
+
* Empty target. rgk_v6_150MeV.trg, Beam current: ~150nA. Take data for 4 hours. 
* Ask for 40 nA beam current take a short run enough to accumulate monitor plots and take a screenshot of the trigger rates, DAQ window with statistics GUI and monitoring histograms
+
* Ramp Torus current down to 1885A (ask Daniel Carman, PDL). At the same time fill target with lH2. Trigger file: rgk_v6_150MeV.trg, Beam current at 35nA. Take data until Thursday 6am.
* Ask for 50 nA beam current take a short run enough to accumulate monitor plots and take a screenshot of the trigger rates, DAQ window with statistics GUI and monitoring histograms
+
'''End of RGK run!'''  
Set the beam for final current (~35nA ?) and take production runs-->
+
<br><hr><br>
* When beam is available ask for 5 nA beam current - check detectors and halo counter rates
+
 
* Production runs using '''rgk_v2.trg''' at '''35n nA '''
+
Notes:
*'''Once per day shift''' apply the RICH recovery procedure described in https://logbooks.jlab.org/entry/3633487
+
* '''Once per day shift''' apply the RICH recovery procedure described in https://logbooks.jlab.org/entry/3633487
 
* If '''beam is expected to be off for more than 1 hr''' turn DC HV off, wait 5 minutes, turn DC HV on again.  
 
* If '''beam is expected to be off for more than 1 hr''' turn DC HV off, wait 5 minutes, turn DC HV on again.  
 
* Any questions or uncertainty about what to do please call RC  
 
* Any questions or uncertainty about what to do please call RC  
<!--
+
* Make sure to save ROC Rates (MB/s) GUI to logbook for each run together with beam screens and trigger GUI
* Luminosity scan: take 2hr run @ 10 nA + 1 hr run @ 20 nA + 40 min. run @ 30 nA - (call Florian - post CND camera screenshot)
+
* Make sure that the FSD thresholds are set correctly and they are unmask when ready to receive beam to the FC @40-50 nA
* Production runs using '''rgk_v2.trg''' at '''45 nA'''
+
* When trigger group is ready take 1h special trigger run-->
+
 
+
 
+
'''<font color=red> Make sure to save ROC Rates (MB/s) GUI to logbook for each run together with beam screens and trigger GUI </font>'''
+
+
* <font color=blue> ''' Make sure that the FSD thresholds are set correctly and they are unmask when ready to receive beam to the FC @40-50 nA
+
 
** Upstream 2000
 
** Upstream 2000
 
** Midstream 1000
 
** Midstream 1000
 
** Downstream 1000000
 
** Downstream 1000000
 
** BOM 30000
 
** BOM 30000
<!--** Downstream 900000 (previous values)
 
** BOM 15000 (previous values)-->
 
 
** Dwell time 5 ms
 
** Dwell time 5 ms
'''</font>
 
  
 
== <font color=blue>''' Shift Worker Notes:'''</font>==
 
== <font color=blue>''' Shift Worker Notes:'''</font>==
  
<!-- * From time to time, we might experience trigger bit issues (FT bits: 24, 25, 26, 27). Bit 26 might not trigger the alarm but when this issue happens it will count abnormally high. For the time being, shift leaders can try to do the sequence of End->Cancel->Reset, roc_reboot adcft1 (and adcft2, adcft3), make sure the ROCs are connected, then Download->Prestart->Go. If this does not work, repeat the sequence and add "Configure" in front of "Download". If the trig issue persists, continue to take production data without fixing it -- please make sure you log this infor in the RCDB "Comment" field. -->
+
* If the machine is down for more than 30 min ask for low current first 5 nA ,make sure that the beam is stable both in position and current, check that the rates are OK on all the detectors and halo counters. Then ask for the nominal production beam current and continue data taking for production. If there are issues with the beam call RC. Sometimes MCC operator may ask to deliver tuned mode beam --- do not accept it. We need CW beam sent to the Faraday cup. If there is indeed a need for tuned beam, it should be sent to the tagger dump with the tagger magnet on. If you are uncertain, please call RC/PDL.
 
+
* If the machine is down for more than 30 min ask for low current first 5 nA ,make sure that the beam is stable both in position and current, check that the rates are OK on all the detectors and halo counters. Then ask for 35 nA and continue data for production. If there are issues with the beam call RC. Sometimes MCC operator may ask to deliver tuned mode beam --- do not accept it. We need CW beam sent to the Faraday cup. If there is indeed a need for tuned beam, it should be sent to the tagger dump with the tagger magnet on. If you are uncertain, please call RC/PDL.
+
  
 
'''In case of other questions or uncertainties of what to do, call the RC'''
 
'''In case of other questions or uncertainties of what to do, call the RC'''
Line 205: Line 190:
 
* Statistics DAQ rates GUI
 
* Statistics DAQ rates GUI
 
* Beam strip charts
 
* Beam strip charts
* FT-Cal FADC scalers
 
 
-->
 
-->
  
Line 220: Line 204:
 
<!--* All jscaler iocs (iocjscalerX) on the health screen (under DAQ tab) must be restarted after every DAQ prestart is completed. Follow this link for detailed instructions https://userweb.jlab.org/~baltzell/CLAS12/SC/jlabScalersOps.txt-->
 
<!--* All jscaler iocs (iocjscalerX) on the health screen (under DAQ tab) must be restarted after every DAQ prestart is completed. Follow this link for detailed instructions https://userweb.jlab.org/~baltzell/CLAS12/SC/jlabScalersOps.txt-->
 
* Check that no unnecessary beamline-related screens are open.  This includes particularly the big beamline overview screen, but also and any motor/harp/collimator screens, and ioc health screens.
 
* Check that no unnecessary beamline-related screens are open.  This includes particularly the big beamline overview screen, but also and any motor/harp/collimator screens, and ioc health screens.
* Reference harp scans: [https://logbooks.jlab.org/entry/3571664 2C21], [https://logbooks.jlab.org/entry/3571676 2C24], [https://logbooks.jlab.org/entry/3571859 2H01]
+
* Reference harp scans: [https://logbooks.jlab.org/entry/3638081 2C21], [https://logbooks.jlab.org/entry/3638086 2C24], [https://logbooks.jlab.org/entry/3638088 2H01]
  
 
'''Every Shift:'''
 
'''Every Shift:'''
Line 249: Line 233:
 
* Statistics DAQ rates GUI
 
* Statistics DAQ rates GUI
 
* Beam strip charts
 
* Beam strip charts
* FT-Cal FADC scalers
 
  
 
|}
 
|}
Line 299: Line 282:
 
* [https://clas12mon.jlab.org/mon12/histograms/ Comparison between mon12 histograms (last 5 runs)]  
 
* [https://clas12mon.jlab.org/mon12/histograms/ Comparison between mon12 histograms (last 5 runs)]  
 
* [https://clas12mon.jlab.org/datasize/ Accumulated datasize]
 
* [https://clas12mon.jlab.org/datasize/ Accumulated datasize]
 +
* [https://clas12mon.jlab.org/charge/ Accumulated charge]
 
===Run lists===
 
===Run lists===
 
* [https://docs.google.com/spreadsheets/d/1M8KGMPd7sXdyNHu3q4V-qzIHdJCXalGWITx2_0MRP4k/edit#gid=0 RGK run list]
 
* [https://docs.google.com/spreadsheets/d/1M8KGMPd7sXdyNHu3q4V-qzIHdJCXalGWITx2_0MRP4k/edit#gid=0 RGK run list]
Line 311: Line 295:
 
| valign=top |
 
| valign=top |
 
===Bluejean meetings===
 
===Bluejean meetings===
 +
* [https://bluejeans.com/383362476] RGK RC meeting - no moderator passcode needed
  
* [https://bluejeans.com/7572697303] RGA RC and analysis meetings 7572697303
+
<!--* [https://bluejeans.com/7572697303] RGA RC and analysis meetings 7572697303 -->
 
|}
 
|}
 
  
 
<headertabs/>
 
<headertabs/>

Latest revision as of 20:14, 18 December 2018

[edit]

If calling local numbers (with area code prefix 757) from the counting room dial 9+[last 7 digits]. To call other area codes dial 91+[10 digit number]

Person Phone Number
Run Coordinator 9-757 575-7540 (cell)
Physics Division Liaison 9-757 876-1789 (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) Tsuneo Kageya
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 Run Group K, Fall 2018
Beam energy 7.5/6.5 GeV (4 pass)
Important: Document all your work in the logbook!
Remember to fill in the run list at the beginning and end of each run (clas12run@gmail.com can fill the run list)

RC: Volker Burkert

PDL: Daniel S. Carman


  • Note 1: Be very mindful of the background rates in the halo counters, rates in the detectors, and currents in the SVT for all settings to ensure that they are at safe levels.
    • The integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and the rates on the midstream counters have to be in the range 10-20 Hz (acceptable up to 50 Hz) @50 nA. Counting rates in the range of hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.
  • Note 2: At the end of each run, follow the standard DAQ restart sequence :
    • "end run", "cancel", "reset", then if the run ended correctly, "download", "prestart", "go". If the run did not end correctly or if any ROCs had to be rebooted, "configure", "download", "prestart", "go".
    • After each step, make sure it is complete in the Run Control message window. If a ROC has crashed, find which one it is and issue a roc_reboot command and try again. Contact the DAQ expert if there are any questions.
  • Note 3: Nominal beam positions: 2C21A (X= - 0.37 mm, Y=0.33 mm) , 2C24A (X=0.2 mm, Y=0.3 mm) , 2H01 (X=1.1 mm, Y=-2.0 mm)
  • Note 4: Do not turn OFF FTOF HVs, even during the beam tune with CW beam (turn off when doing a Moller run or if there is tuned/pulsed beam in the upstream beamline)
  • Note 5: In case of a Torus and/or Solenoid Fast Dump do the following:
    1. Notify MCC to request beam OFF and to drop Hall B status to Power Permit
    2. Call Engineering on-call
    3. Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org
    4. Notify Run Coordinator
    5. Turn off all detectors
  • Note 6: When beam is being delivered to the Faraday Cup:
    1. the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state UNMASKED
    2. No changes to the FSD threshold should be made without RC or beamline expert approval
  • Note 7: Any request for a special run or change of configuration has to be approved by the RC & documented
  • Note 8: Carefully check the BTA every hour and run the script btaGet.py to print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.
  • Note 9: Reset CLAS12MON frequently to avoid histogram saturation.
  • Note 11: Do not Turn OFF MVT HV: Instead go to 'Restore settings' from the MVT overview screen:
    1. SafeMode.snp for beam tuning and Moeller runs
    2. MV_HV_FullField.snp for full solenoid field
    3. MV_HV_MidField.snp wgeb solenoid < 4T

  • NOTE 12: Check the vacuum periodically, make sure vacuum is not higher than 5e-5
  • NOTE 13: Always reset the CFD threshold after all power off/on on the CND CAMAC crate
    • If the CND CAMAC CFD crate (camac1) is switched off for any reason, it is mandatory to reset the thresholds via the command: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0
    • If this command fails and the crate is not responding, reboot it as follows: roc_reboot camac1
  • NOTE 17: CLAS12 is configured with FT-Off - Do not turn on LV or HV for any of the FT components (Cal, Hodo, Trk)

Run Plan:

(Updated: Dec. 16, 2018 at 14:50hrs)

  • Update the reference harp scan links on the run wikipage (the RC should do this)

Turn on all CLAS12 detectors (note that FT components should be left off as they are not used in this part of the run)

  • In the following use the BPM positions: 2C21A: x=-0.14, y=0.460; 2C24A: x = 0.290, y=0.290 ; 2H00: x=1.3, y=1.0; 2H01: x=1.13, y=-1.91

Plan until Thursday morning 6:00:

  • Trigger file: rgk_v6_200MeV.trg, HWP IN. Beam current at 35nA. Run until 1,000M events are collected.
  • Trigger file: rgk_v6_150MeV.trg, HWP IN. Beam current at 5nA. Take data until Wednesday 8:00am.
  • Trigger file: rgk_v6_300MeV_random_30KHz.trg, HWP IN. Beam currents at 10nA, 35nA, 60nA, 75nA. Collect 200M events at each current (~2hrs per current).
  • Empty target. rgk_v6_150MeV.trg, Beam current: ~150nA. Take data for 4 hours.
  • Ramp Torus current down to 1885A (ask Daniel Carman, PDL). At the same time fill target with lH2. Trigger file: rgk_v6_150MeV.trg, Beam current at 35nA. Take data until Thursday 6am.

End of RGK run!




Notes:

  • Once per day shift apply the RICH recovery procedure described in https://logbooks.jlab.org/entry/3633487
  • If beam is expected to be off for more than 1 hr turn DC HV off, wait 5 minutes, turn DC HV on again.
  • Any questions or uncertainty about what to do please call RC
  • Make sure to save ROC Rates (MB/s) GUI to logbook for each run together with beam screens and trigger GUI
  • Make sure that the FSD thresholds are set correctly and they are unmask when ready to receive beam to the FC @40-50 nA
    • Upstream 2000
    • Midstream 1000
    • Downstream 1000000
    • BOM 30000
    • Dwell time 5 ms

Shift Worker Notes:

  • If the machine is down for more than 30 min ask for low current first 5 nA ,make sure that the beam is stable both in position and current, check that the rates are OK on all the detectors and halo counters. Then ask for the nominal production beam current and continue data taking for production. If there are issues with the beam call RC. Sometimes MCC operator may ask to deliver tuned mode beam --- do not accept it. We need CW beam sent to the Faraday cup. If there is indeed a need for tuned beam, it should be sent to the tagger dump with the tagger magnet on. If you are uncertain, please call RC/PDL.

In case of other questions or uncertainties of what to do, call the RC


General Instructions:

  • For a given beam current, compute the FSD thresholds according to the Establish Physics Quality Beam document. Call MCC to update the values. Contact the beamline expert if there are questions about setting the FSD thresholds.
  • The main lights in the Hall (dome lights) and the Forward Carriage lights are being kept off because of light leaks affecting some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall. Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cooldown.
  • Do not run more than 60 minutes above 30 nA with 5-pass beam without the beam blocker in front of Faraday cup. Put beam blocker in for long running at high currents for 5 pass operations.
  • Turn DC HV off only for beam tuning; if no beam is available or when beam is stable, keep them on even if you are not taking data.
  • In case of loss of communication with IOCBTARG, follow instructions at https://logbooks.jlab.org/entry/3502218
  • With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem.
  • Check that no unnecessary beamline-related screens are open. This includes particularly the big beamline overview screen, but also and any motor/harp/collimator screens, and ioc health screens.
  • Reference harp scans: 2C21, 2C24, 2H01

Every Shift:

  • Follow run plan as outlined by RC
  • If any concern about beam stability, 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 out BTA hourly. Click "Load from EPICS" to automatically fill the left side.
  • When you do BTA keep track of of BANU. Include at the end of shift summary log details of BANU: the reason and duration.
  • Fill and submit the shift checklist in the logbook

Every Run:

Log screenshots of the following screens, and make sure at the moment you capture the screen the beam is ON

  • main scaler GUI display
  • Detector occupancy plots
  • Trigger rate GUI
  • Roc Rates (MB/s) GUI
  • Statistics DAQ rates GUI
  • Beam strip charts


Clas12design.png