Difference between revisions of "Run Group F"

From clas12-run
Jump to navigation Jump to search
 
(75 intermediate revisions by 4 users not shown)
Line 12: Line 12:
 
'''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf Beam Time Accounting User Guide]'''.
 
'''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf Beam Time Accounting User Guide]'''.
 
<!-- ===[https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc#CLAS12_Operations_Documentation Operations Documentation]=== -->
 
<!-- ===[https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc#CLAS12_Operations_Documentation Operations Documentation]=== -->
 +
===[https://www.jlab.org/Hall-B/run-web/rgf/ESAD_HallB-CLAS12_rgF.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rgf/COO_HallB-CLAS12_rgF.pdf COO], [https://www.jlab.org/Hall-B/run-web/rgf/RSAD_HallB-CLAS12_rgF.pdf RSAD], [https://www.jlab.org/div_dept/train/SAF111/Hall%20B%20worker%20Safety%20Training%20%28SAF111%29%20%2008%2001-12-1.pdf ERG] ===
 +
===[https://www.jlab.org/Hall-B/run-web/rgf/RTPC_OSP.pdf OSP for Radial Time Projection Chamber]===
 +
===[https://www.jlab.org/Hall-B/run-web/rgf/bonus12_gas_target_osp_97803.pdf OSP for BONUS12 gas target system]===
  
 
| valign=top |
 
| valign=top |
Line 126: Line 129:
 
* 9 757-575-7540 from Counting Room.
 
* 9 757-575-7540 from Counting Room.
 
* If you can't reach the RC on the RC phone, use the personal phone numbers (Mohammad: (423) 596-8352, Sebastian: (757) 639-6640)
 
* If you can't reach the RC on the RC phone, use the personal phone numbers (Mohammad: (423) 596-8352, Sebastian: (757) 639-6640)
 
 
 
* RC meeting held at 12 pm online.  Bluejeans 757 683 5804
 
* RC meeting held at 12 pm online.  Bluejeans 757 683 5804
 
+
* Get the number of events from SQL --> [http://clasweb.jlab.org/rcdb RCDB]
* [https://docs.google.com/spreadsheets/d/1zqU05gixdQuRD9ldJGwF245HBw5vnWfPIbLZ72E22ow/edit?usp=sharing Number of Events Spreadsheet] RIght now manually, until somebody with the knowledge and the time write an script to get the number of events from SQL --> [http://clasweb.jlab.org/rcdb RCDB]
 
  
 
   
 
   
Line 138: Line 138:
  
 
== NEW SHIFT INFORMATION - PLEASE READ ==
 
== NEW SHIFT INFORMATION - PLEASE READ ==
Due to travel restrictions, only local people will be able to come to Jefferson Lab for their shifts. To deal with this situation, Jefferson Lab leadership has developed a new [https://userweb.jlab.org/~kuhn/BONuS12/Documents/shift-policy_20200317.docx POLICY] that requires only an expert shift taker during Day and Swing shifts (Owl shifts will still be covered by 2 people). There will be remote backup, at least partial presence by the Run Coordinators, and all counting houses have been equipped with a direct camera feed so that shift takers for ANY hall can monitor the counting houses of Hall B and Hall D when only 1 person is present. Shift Experts will carry a cell phone that can be used to call in help. IF YOU ARE ALONE ON SHIFT, you may not go into the Hall - call the relevant experts instead. Shift experts during Day and Swing are expected, in addition to their regular duties, to also check monitoring histograms and CED and log them (as well as standard screen shots) to the logbook, and to respond to any alarms, as well as fill out shift checklists. These new rules take effect on Tuesday, March 24.  
+
Due to travel restrictions, only local people will be able to come to Jefferson Lab for their shifts. To deal with this situation, Jefferson Lab leadership has developed a new [https://userweb.jlab.org/~kuhn/BONuS12/Documents/shift-policy_20200317.docx POLICY] that requires only an expert shift taker during Day and Swing shifts (Owl shifts will still be covered by 2 people). There will be remote backup ("Ghost Shifts") for some of the worker shifts during Day/Swing - '''please read the instructions under the "Remote Shifts" tab and make sure that Bluejeans is properly connected (Screen share and audio)'''. All counting houses have been equipped with a direct camera feed so that shift takers for ANY hall can monitor the counting houses of Hall B and Hall D when only 1 person is present. Shift Experts will carry a cell phone that can be used to call in help. IF YOU ARE ALONE ON SHIFT, you may not go into the Hall - call the relevant experts instead. Shift experts during Day and Swing are expected, in addition to their regular duties, to also check monitoring histograms and CED and log them (as well as standard screen shots) to the logbook, and to respond to any alarms, as well as fill out shift checklists. These new rules take effect on Tuesday, March 24.  
  
 
Starting immediately, please follow these rules: Keep a distance of 6 ft from all other people AT ALL TIMES. In particular, expert and worker (when both present) should sit 6 feet apart, facing in different directions. In addition, only the RC OR an RTPC expert  should be inside the counting house B at any time - a maximum room occupancy of THREE has to be obeyed at all times. The RC, PDL and shift expert have the authority to ask non-essential people to leave if overcrowding occurs. Any work that requires 2 people to work in closer proximity than 6' must be first approved.
 
Starting immediately, please follow these rules: Keep a distance of 6 ft from all other people AT ALL TIMES. In particular, expert and worker (when both present) should sit 6 feet apart, facing in different directions. In addition, only the RC OR an RTPC expert  should be inside the counting house B at any time - a maximum room occupancy of THREE has to be obeyed at all times. The RC, PDL and shift expert have the authority to ask non-essential people to leave if overcrowding occurs. Any work that requires 2 people to work in closer proximity than 6' must be first approved.
  
At present, we expect the experimental run to continue until '''September 21, 2020'''. Obviously, this puts extra burden on many people, and we are grateful especially for those local volunteers who have signed up for shifts. ('''It's still not too late to sign up for some empty slots!!!''') Please also read the relevant information on COVID-19 and MEDCON5 operations at Jefferson Lab: [https://jlab.servicenowservices.com/cv19?id=cv19_index]
+
At present, we expect the experimental run to continue until '''September 21, 2020'''. Obviously, this puts extra burden on many people, and we are grateful especially for those local volunteers who have signed up for shifts.Please also read the relevant information on COVID-19 and MEDCON5 operations at Jefferson Lab: [https://jlab.servicenowservices.com/cv19?id=cv19_index]
  
 
==================================================================================================================================
 
==================================================================================================================================
Line 153: Line 153:
 
===<font color=black>There will be an audible Beamline alarm when the half-wave plate (HWP) state changes. Please end the ongoing run and start a new run.</font>===
 
===<font color=black>There will be an audible Beamline alarm when the half-wave plate (HWP) state changes. Please end the ongoing run and start a new run.</font>===
  
===<font color=blue>'' 2. For every run (~2 hours)''</font>===
+
===<font color=blue>'' 2. For every run (~15-20 M events)''</font>===
 
# In the '''begin run dialog''', enter the requested '''beam current''', the '''state of the half-wave plate (IN or OUT)''' and any conditions changed since the last run (target, B-fields, HVs, DAQ config, trigger, ...). In the end run dialog, check boxes ("junk" etc.) and add to the dialog any significant changes during the run.
 
# In the '''begin run dialog''', enter the requested '''beam current''', the '''state of the half-wave plate (IN or OUT)''' and any conditions changed since the last run (target, B-fields, HVs, DAQ config, trigger, ...). In the end run dialog, check boxes ("junk" etc.) and add to the dialog any significant changes during the run.
 
# *) Near the beginning of the run, submit  the following screenshots (can be all in one elog entry) '''while beam is on'''. Sample plots for reference:
 
# *) Near the beginning of the run, submit  the following screenshots (can be all in one elog entry) '''while beam is on'''. Sample plots for reference:
Line 162: Line 162:
 
## RTPC overview [https://logbooks.jlab.org/files/2020/08/3819288/clonpc15_20200802_065636.gif],  
 
## RTPC overview [https://logbooks.jlab.org/files/2020/08/3819288/clonpc15_20200802_065636.gif],  
 
## BONuS HV [https://logbooks.jlab.org/files/2020/08/3819288/clonpc15_20200802_065643.gif].
 
## BONuS HV [https://logbooks.jlab.org/files/2020/08/3819288/clonpc15_20200802_065643.gif].
# Run clas12mon over '''at most''' 10-20 min '''with good beam(!)''' (reset first) and submit the occupancy plots (at least '''once''' per run, '''early in the run'''). Whenever you restart clas12mon (and if you haven't checked it yet), '''go to the TriggerBits menu and select "ElectronOr"'''. Compare with previous monitoring plots and the '''[https://clas12mon.jlab.org/mon12/histograms/?reference=3826198 reference WITHOUT FT]''' and make a log entry about any changes you observe. Make sure to reset monitoring plots regularly.
+
# Run clas12mon over '''at most''' 10-20 min '''with good beam(!)''' (reset first) and submit the occupancy plots (at least '''once''' per run, '''early in the run'''). Whenever you restart clas12mon (and if you haven't checked it yet), '''go to the TriggerBits menu and select "ElectronOr"'''. Compare with previous monitoring plots and the '''[https://clas12mon.jlab.org/mon12/histograms/?reference=3826198 reference WITHOUT FT]''' and make a log entry about any changes you observe. '''Do NOT worry about trigger bits 22 and 31''' - those will be missing. Make sure to reset monitoring plots regularly.
 
# Take at least one screen shot of RTPC CED with beam per run and post in logbook. De-select "Auto-event" and use Cntrl-N to browse for an event with tracks in it.
 
# Take at least one screen shot of RTPC CED with beam per run and post in logbook. De-select "Auto-event" and use Cntrl-N to browse for an event with tracks in it.
  
Line 184: Line 184:
  
 
===<font color=blue>''4. PLEASE <font color=red> ''DO NOT IGNORE ANY ALARM ''</font> and follow the guidance for each alarm notification. ''</font>===
 
===<font color=blue>''4. PLEASE <font color=red> ''DO NOT IGNORE ANY ALARM ''</font> and follow the guidance for each alarm notification. ''</font>===
 +
'''Exception: Alarms on trigger bits > 14 can be ignored (or the alarm threshold set lower)'''
  
 
============================================================================================================================================================
 
============================================================================================================================================================
 
== <font color=blue>'''B. Run Plan'''</font> (see also [https://userweb.jlab.org/~kuhn/BONuS12/Documents/RunPlan.pdf initial run plan]) ==
 
== <font color=blue>'''B. Run Plan'''</font> (see also [https://userweb.jlab.org/~kuhn/BONuS12/Documents/RunPlan.pdf initial run plan]) ==
(Last updated: August 26, 2020)
 
  
General plan: Follow a sequence of 6 Days D2 (200 nA), 2 shifts H2 (250 nA), 1 2-hour run empty (350 nA) and 10M events on 4He (200 nA).
 
  
=== Continue taking data on D2 ===
+
* Collect 30M on H2
 +
* Call Mohammad to set the target to empty
 +
* continue taking data on empty target setting till 7:00AM on Monday, Sep 21st.
  
 
<b>DAQ config:  PROD66 </b>,   
 
<b>DAQ config:  PROD66 </b>,   
<b>Trigger file: rgf_inbending_v4_1.trg (.cnf)</b>
+
<b>Trigger file: rgf_inbending_v4_2.trg (.cnf)</b>
# The RC will purge the target every day at 8:30 Am and take an empty target run. Then,
+
# Continue taking data with 270 nA beam current (@2C24). '''NOTE:''' This is 280 nA on the SLM, which means we have to ask MCC for 270 nA on 2C24 (which is what they see).
# Continue taking data on Full D2 target (~ 67 psig) and 180 nA beam current.  
 
 
# <font color=red> Please write the target pressure and comments in the dialogue box when starting/stopping a run </font>
 
# <font color=red> Please write the target pressure and comments in the dialogue box when starting/stopping a run </font>
 
# Start a run and check that live time is above 85%. If not decrease current and log it.
 
# Start a run and check that live time is above 85%. If not decrease current and log it.
# Restart a new run every <font color=red> 2h </font> OR 10M events. '''END A RUN''' if beam will be off > 15 min, RTPC HV trip, or '''whenever half-wave plate is changed'''!
+
# Restart a new run every (15-20)M events (wait till beam trips). '''END A RUN''' if beam will be off > 20 min, RTPC HV trip, or '''whenever half-wave plate is changed'''!
# Submit the list of screenshots at the beginning and at the end of every run.  
+
# Submit the list of screenshots + clas12mon +ced at the beginning and at after the first 10M events in every run.  
#<b><font color=red> At the end of each run, follow the standard DAQ restart sequence: <br></font></b>
 
## -> "end run", "cancel", "reset" <br>
 
## a. if the run ended correctly: ->  '''"download", "prestart", "go"'''<br>
 
## b. if the run did not end correctly or if any ROCs had to be rebooted:-> "configure", "download", "prestart", "go"<br>
 
 
# Keep BTA (beam time accounting) up to date, including reasons for any entries with experiment not ready.
 
# Keep BTA (beam time accounting) up to date, including reasons for any entries with experiment not ready.
 
# <b> When checking the ECAL response, make sure to look at the histograms for each sector by using the sector buttons at the bottom of the clas12mon window - if adcecal* or/and adcpcal* ROC crashes, there will be no alarm and the histograms are the way to notice this issue.  
 
# <b> When checking the ECAL response, make sure to look at the histograms for each sector by using the sector buttons at the bottom of the clas12mon window - if adcecal* or/and adcpcal* ROC crashes, there will be no alarm and the histograms are the way to notice this issue.  
 
#<font color=blue> For trigger alarms check Note 14 first! </font></b>
 
#<font color=blue> For trigger alarms check Note 14 first! </font></b>
  
 +
=== <b><font color=red>* At the end of each run, follow the standard DAQ restart sequence: <br></font></b>===
 +
# -> "end run", "cancel", "reset" <br>
 +
# a. if the run ended correctly: ->  '''"download", "prestart", "go"'''<br>
 +
# b. if the run did not end correctly or if any ROCs had to be rebooted:-> "configure", "download", "prestart", "go"<br>
  
 +
=== Plan for Monday Morning, Sep 21st ===
 +
# 07:00 : The beam will be taken away for some MCC studies. Gagik, will confirm with MCC that the Hall goes to Controlled Access.
 +
# 07:00 to 8:00: Gagik will call Eugene to ramp down the torus and ramp the solenoid to 1.5T.
 +
# 07:00- 08:00: Gagik can turn off HV on the following detectors ONLY (LTCC, HTCC, DC, RICH, FMT, FTC, FTH)
 +
# 08:00: Gagik leaves the counting house and the BONuS team (Jiwan and Sebastian) will join to do final cosmic tests.
 +
# Before 12:00: the solenoid be totally ramped down. the bonus team will be in contact with Eugene.
 +
# 12:00: The bonus team will turn off HV on ECAL, PCAL, and CND.
 +
# FTOF and CTOF must be left turned ON.
 
==================================================================================================================================
 
==================================================================================================================================
  
Line 215: Line 223:
 
== <font color=blue>'''C. References and Standards:'''</font>==
 
== <font color=blue>'''C. References and Standards:'''</font>==
  
=== Checking the beam profiles and positions ===
+
===* Establish beam in the Hall ( CALL RC )===
# Doing harp scans on FC:
+
# ALL the detectors must be off. Don't forget the FT and RTPC HV (separate GUIs).
## All HV are off (including FTOF)
+
# Ask MCC to energize the tagger magnet.
## Check that 20 mm collimator is in
+
# Ask MCC for 5-9 nA and check the beam quality using harp scans 2C21 and 2C24, following the procedures described in [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]
## Call MCC to unmask U/M/D counters but keep BOM masked or get it masked in case it isn't
+
# When the beam quality is acceptable, Call MCC and ask for a low-intensity (~5-9 nA) beam to FC, complete harp scans. Procedures described in [https://wiki.jlab.org/clas12-run/images/9/9f/HarpScanManual.pdf]. We require less than 0.3 mm (1σ) beam widths in x and y (As measured by 2H01A harp) and halo below 10^−4 (As measured by 2H01A harp). See references below.
## Put thresholds on U/M/D as 1M/1M/1M and dwell time 50 ms.
+
# ONLY if instructed by RC: -> Center beam on target, using rates in BOM and downstream beam monitors. Establish range where beam starts directly interacting with target walls and take middle.
## Call MCC to put 5nA to the FC.
+
# Engage orbit locks and ascertain that they are stable.
## Compare the 2c21, 2c24, 2H01 positions and beam overview screen to the reference below
+
# Set alarms and interlocks.
## follow the procedures for the harp scans at 2H01 [https://wiki.jlab.org/clas12-run/images/9/9f/HarpScanManual.pdf] (also do harp scans on 2C24)
+
# Call the MCC and tell them that the beam is good and must keep the beam current at 5 nA.
## Compare the results with the references scans below (be aware to use the correct analysis counter)
+
 
## if what you get is similar to the references, call MCC and tell them the the beam is acceptable and set FSD thresholds and dwelltimes as written below and continue with production running
 
## if what you get isn't similar to the references or If you are not sure if a tune of the beam is needed, consult beamline expert and/or RC.
 
  
 
<b> Default solenoid current and B field </b> 1800 A (~3.78 T)
 
<b> Default solenoid current and B field </b> 1800 A (~3.78 T)
  
 
<b> Nominal Beam Positions </b>
 
<b> Nominal Beam Positions </b>
''(last update Aug 22nd, 2020 @ 06:20 AM)''
+
''(last update Sep 10th, 2020 @ 23:50 PM)''
*2H01, X: -0.2 mm, Y: -1.4 mm
+
*2H01, X: +0.7 mm, Y: -1.6 mm
*2C24, X: -0.8 mm, Y: -1.7 mm
+
*2C24, X: -2.0 mm, Y: -1.0 mm
*2C21, X: -0.2 mm, Y: 0.4 mm
+
*2C21, X: -0.4 mm, Y: 0.3 mm
  
  
 
<b> FSD Thresholds </b>
 
<b> FSD Thresholds </b>
* Upstream: 2,000 Hz
+
* Upstream: 2,600 Hz
 
* Midstream: 2,000 Hz
 
* Midstream: 2,000 Hz
 
* Downstream: 500,000 Hz
 
* Downstream: 500,000 Hz
* BOM: 2,600 Hz
+
* BOM: 7,000 Hz
  
 
<b> FSD Dwell (Integration) Time </b>
 
<b> FSD Dwell (Integration) Time </b>
Line 251: Line 257:
 
<b> BONuS HV setting</b>
 
<b> BONuS HV setting</b>
 
* [https://logbooks.jlab.org/entry/3807043 Reference RTPC currents without beam]
 
* [https://logbooks.jlab.org/entry/3807043 Reference RTPC currents without beam]
* [https://logbooks.jlab.org/files/2020/08/3826925/clonpc19_20200813_230432.gif Final reference RTPC HV and currents with beam]
+
* [https://logbooks.jlab.org/files/2020/08/3838353/clonpc15_20200831_082242.gif Final reference RTPC HV and currents with beam (240 nA)]
  
<b> Reference Harp Scans for Beam on Tagger Dump: </b> 2C21 [https://logbooks.jlab.org/entry/3825429], 2C24 [https://logbooks.jlab.org/entry/3825443]
+
*<b> Reference Harp Scans for Beam on Tagger Dump: </b> 2C21 [https://logbooks.jlab.org/entry/3825429], 2C24 [https://logbooks.jlab.org/entry/3838463]
 
+
*<b> Reference Harp Scans for Beam on Faraday Cup: </b>  2C21 [https://logbooks.jlab.org/entry/3825493], 2C24 [https://logbooks.jlab.org/entry/3837237][https://logbooks.jlab.org/entry/3837238], 2H01 [https://logbooks.jlab.org/entry/3837231].
<b> Reference Harp Scans for Beam on Faraday Cup: </b>  2C21 [https://logbooks.jlab.org/entry/3825493], 2C24 [https://logbooks.jlab.org/entry/3825485], 2H01 [https://logbooks.jlab.org/entry/3825489].
 
  
 
<b> Reference Monitoring Histograms</b> 5 nA production trigger [https://logbooks.jlab.org/entry/3783929]
 
<b> Reference Monitoring Histograms</b> 5 nA production trigger [https://logbooks.jlab.org/entry/3783929]
Line 407: Line 412:
 
* [http://clasweb.jlab.org/rcdb RCDB]
 
* [http://clasweb.jlab.org/rcdb RCDB]
  
===Run lists===
 
 
| valign=top |
 
| valign=top |
 
===Accelerator===
 
===Accelerator===
Line 415: Line 419:
 
* [https://www.evernote.com/pub/maureeungaro/pdldaily Accelerator daily meetings notes (by Mauri)]
 
* [https://www.evernote.com/pub/maureeungaro/pdldaily Accelerator daily meetings notes (by Mauri)]
 
| valign=top |
 
| valign=top |
===Bluejeans meetings===
+
 
* [https://bluejeans.com/7576835804 Daily Run meetings] 10:00 a.m. Upstairs Counting House / Bluejeans 757 683 5804
 
 
|}
 
|}
  
Line 449: Line 452:
 
* Audio for the bluejeans session goes through the phone, 269-5247. This is the phone attached on the second row of tables (former RC station), behind the shift expert station.  
 
* Audio for the bluejeans session goes through the phone, 269-5247. This is the phone attached on the second row of tables (former RC station), behind the shift expert station.  
 
** DO NOT HANG UP or MUTE the phone, if you have to mute then do not forget to unmute.   
 
** DO NOT HANG UP or MUTE the phone, if you have to mute then do not forget to unmute.   
** About every 6 hours the bluejeans will disconnect the phone if this happens, use the microphone tab in the bluejeans window and choose "Switch to phone audio" then select "Call me" and give the phone number, 757 269 5247.  
+
** CHECK AT THE BEGINNING OF EACH SHIFT: About every 6 hours the bluejeans will disconnect the phone if this happens, use the microphone tab in the bluejeans window and choose "Switch to phone audio" then select "Call me" and give the phone number, 757 269 5247. Once you are connected, you have to press "'''*4'''" on the phone to unmute yourself.
  
 
<headertabs/>
 
<headertabs/>

Latest revision as of 13:49, 25 July 2024

[edit]

Shift Schedule

Shift Checklist

Hot Checkout

Beam Time Accounting

  • See guidance for BTA in

Beam Time Accounting User Guide.

ESAD, COO, RSAD, ERG

OSP for Radial Time Projection Chamber

OSP for BONUS12 gas target system

Manuals

Procedures

JLab Logbooks


RC schedule Weekly form

  • Feb 12 - Feb 18: Mohammad Hattawy
  • Feb 19 - Feb 25: Florian Hauenstein
  • Feb 26 - Mar 3: Eric Christy
  • Mar 4 - Mar 19: Sebastian Kuhn
  • Mar 18 - Mar 23: Carlos Ayerbe

  • RC & RTPC expert list [1]
  • 07/31 - 08/04 : Narbe Kalantarian
  • 08/05 - 08/11 : Stephen Bueltmann
  • 08/12 - 08/18 : Carlos Ayerbe Gayoso
  • 08/20 - 08/21 : Mohammad Hattawy
  • 08/22 - 08/25 : Sebastian Kuhn
  • 08/26 - 09/01 : Mohammad Hattawy
  • 09/02 - 09/08 : Sebastian Kuhn
  • 09/09 - 09/15 : Mohammad Hattawy
  • 09/16 - 09/21 : (Mohammad Hattawy)


Daily Run Group F Coordination Meetings Daily at 12:00 pm. Bluejeans = 757 683 5804


Daily Ops Meeting (working days 7:45):
BlueJeans = 569 476 853


Clas12design.png