Difference between revisions of "Run Group M"

From clas12-run
Jump to navigation Jump to search
 
(518 intermediate revisions by 13 users not shown)
Line 6: Line 6:
 
<!--==={{#switchtablink:Phone Numbers|'''Phone Numbers'''}}===-->
 
<!--==={{#switchtablink:Phone Numbers|'''Phone Numbers'''}}===-->
 
===[http://www.jlab.org/Hall-B/shifts Shift Schedule]===
 
===[http://www.jlab.org/Hall-B/shifts Shift Schedule]===
 +
===[https://logbooks.jlab.org/book/hallb Hall B Logbook]===
 
===[https://logbooks.jlab.org/checklists/151 Shift Checklist] ===
 
===[https://logbooks.jlab.org/checklists/151 Shift Checklist] ===
 
===[https://accweb.acc.jlab.org/hco/readiness Hot Checkout]===
 
===[https://accweb.acc.jlab.org/hco/readiness Hot Checkout]===
 
===[https://bta Beam Time Accounting]===
 
===[https://bta Beam Time Accounting]===
−
* See guidance for BTA in '''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf Beam Time Accounting User Guide]'''.
+
* See guidance at '''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf BTA 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/rgm/ESAD_HallB-CLAS12_rgM.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rgm/COO_HallB-CLAS12_RGM.pdf COO], [https://www.jlab.org/Hall-B/run-web/rgm/RSAD_HallB-CLAS12_rgM.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] ===
  
 
| valign=top |
 
| valign=top |
 
===Manuals===
 
===Manuals===
−
* [https://clasweb.jlab.org/wiki/images/b/b2/Drift-chamber-operating-procedure.pdf DC]
+
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/dc/Drift-chamber-operating-procedure.pdf DC]
−
* [https://clasweb.jlab.org/wiki/images/b/b0/Ftof_manual.pdf  FTOF]
+
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/ftof/ftof_manual.pdf  FTOF]
 
* [https://clasweb.jlab.org/wiki/images/a/a2/Ec_manual.pdf ECAL]
 
* [https://clasweb.jlab.org/wiki/images/a/a2/Ec_manual.pdf ECAL]
−
* [https://wiki.jlab.org/clas12-run/images/d/d2/Ltcc_manual.pdf LTCC]
+
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/ltcc/manual/ltcc_manual.pdf LTCC]
 
* [https://clasweb.jlab.org/wiki/images/f/f1/HTCC_MANUAL.pdf HTCC]
 
* [https://clasweb.jlab.org/wiki/images/f/f1/HTCC_MANUAL.pdf HTCC]
−
* RICH: [https://clasweb.jlab.org/wiki/images/e/ea/RICH_Manual.pdf expert] [https://wiki.jlab.org/clas12-run/images/d/d9/RICH_Controls_mc.pdf novice]
+
* RICH: [https://github.com/JeffersonLab/clas12-manuals/raw/master/rich/RICH_Manual.pdf Expert] [https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf Shift]
−
* [https://clasweb.jlab.org/wiki/images/0/0f/Ctof_manual.pdf CTOF]
+
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/ctof/ctof_manual.pdf CTOF]
 
* [https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf CND]
 
* [https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf CND]
−
* [https://clasweb.jlab.org/wiki/images/6/60/Svt_operation_manual.pdf  SVT]
+
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/svt/svt_operation_manual.pdf  SVT]
−
* [https://clasweb.jlab.org/wiki/images/a/ad/Documentation_Shifters_MVT.pdf MVT]
+
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/mm/Documentation_Shifters_MVT.pdf MVT]
 
** [https://wiki.jlab.org/clas12-run/images/b/bf/MVT_for_Dummies.pdf MVT turn on procedure]
 
** [https://wiki.jlab.org/clas12-run/images/b/bf/MVT_for_Dummies.pdf MVT turn on procedure]
−
* [https://clasweb.jlab.org/wiki/images/3/3b/FT-Manual.pdf FT]
+
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/ft/FT-Manual.pdf FT]
−
* [https://clasweb.jlab.org/wiki/images/4/4d/Beamline_manual.pdf Beamline]
+
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beamline_manual.pdf Beamline]
−
* [https://clasweb.jlab.org/wiki/images/d/d6/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus Power-Up and Power-Down Procedure]
+
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus Power-Up/Down Procedure]
−
* [https://clasweb.jlab.org/wiki/images/d/dc/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid Power-Up and Power-Down Procedure]
+
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid Power-Up/Down Procedure]
−
* [https://clasweb.jlab.org/wiki/images/c/c1/Shift_Worker_Manual_January_2018.pdf Cryo Target Operation manual]
+
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/target/Target_Shift_Worker_RGM_2021.pdf Target Operation manual]
−
* [https://clasweb.jlab.org/wiki/images/a/ab/Opman_master.pdf DAQ]
+
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/daq/opman_master.pdf DAQ]
 
* [[Media:clas12controls_shift.pdf|Slow Controls]]
 
* [[Media:clas12controls_shift.pdf|Slow Controls]]
 +
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/band/band_om.pdf BAND]
  
 
| valign=top |
 
| valign=top |
 
===Procedures===
 
===Procedures===
−
* [[Media:estab_beam.pdf|Establishing Physics-Quality Beam]]
+
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beam_estab_rgm.pdf Physics-Quality Beam]
 
* [[Media:moller.pdf|Performing M&oslash;ller Runs]]
 
* [[Media:moller.pdf|Performing M&oslash;ller Runs]]
 
* [[Media:HarpScanManual.pdf|Performing Harp Scans]]
 
* [[Media:HarpScanManual.pdf|Performing Harp Scans]]
 
* [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Tunnel/Hall Access]
 
* [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Tunnel/Hall Access]
 +
* [https://www.jlab.org/Hall-B/run-web/index_rgm.html  ESAD, COO, RSAD]
 
<!--* [https://clonwiki0.jlab.org/wiki/index.php/DAQ/Online_Quick_Reference <span style="color:red;"><b>DAQ Quick Reference/Recovery</b></span>] -->
 
<!--* [https://clonwiki0.jlab.org/wiki/index.php/DAQ/Online_Quick_Reference <span style="color:red;"><b>DAQ Quick Reference/Recovery</b></span>] -->
  
Line 55: Line 59:
 
= Phone Numbers =
 
= Phone Numbers =
  
−
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]'''
+
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+[ten digit number]'''
  
 
<!--#######################################  PHONE NUMBERS  #############################################-->
 
<!--#######################################  PHONE NUMBERS  #############################################-->
 
{{PhoneNumbers}}
 
{{PhoneNumbers}}
−
[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=Run_Group_A&action=edit&section=11 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 edit the current page to force a refresh.
  
−
<!-- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATEs-->
+
<!-- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE -->
  
 +
 +
<!--#######################################  Short Term Schedule  #############################################-->
 
= Short Term Schedule =
 
= Short Term Schedule =
−
<center><font color=blue size=4>
 
−
''' CLAS12 Run Group M, Fall 20XX </font> '''<br>
 
−
''' Beam energy 20.6 GeV (10 pass) '''<br>
 
−
''' Important: Document all your work in the logbook! '''<br>
 
  
−
<!--
+
=== <font color=blue size=4> ''' CLAS12 Run Group M, Fall 2021 </font> ''' ===
−
*'''<font color=red size=6> Shifts are cancelled until 08:00 Saturday September 22, 20XX </font>'''<br>
+
''' Beam energies: 2.1, 4.0, 6.0 GeV (1.96 GeV/pass) '''<br>
−
-->
 
−
</center>
 
  
−
== RC: Holly ==
+
=== RC: Susan Schadmand ===
−
* (757) 575-7540
+
* (757) 575-7540, [mailto:susansch@jlab.org susansch@jlab.org]
−
* 9 575 7540 from Counting Room
+
* 9 575 7540 from Counting Room 
−
* [mailto:latifa@jlab.org rafopar@jlab.org]
 
  
−
== PDL: Bob ==
+
=== PDL: Valery Kubarovsky ===
 
*  (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:vpk@jlab.org vpk@jlab.org]
  
−
<br>
+
== <font color=blue>''' Run Plan: Friday, Feb 7-8, 2022 '''</font> ==
  
−
* '''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.'''
+
Production runs use <b> PROD67_noVTPread </b> and the trigger <b> rgm_6GeV_inb_v1_0.trg </b>.<br/>
−
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.
+
Run duration 100M events or 4 hours, whichever comes first.
  
−
* ''' Note 2: At the end of each run, follow the standard DAQ restart sequence '''
+
* run 6GeV 80 nA on Ca48 target (240 mg/cm2), beam blocker IN, until SAD
−
"end run", "cancel", "reset", then if the run ended correctly, "download", "prestart", "iocjscalerRestartAll.sh", "go". If the run did not end correctly or if any ROCs had to be rebooted, "configure", "download", "prestart", "iocjscalerRestartAll.sh", "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.
+
* low luminosity runs:(ca 3pm - 9pm on Feb 7)
 +
** 2 hrs 5nA
 +
** 2 hrs 10 nA
 +
** 2 hrs 40 nA
  
−
* '''Note 3: Nominal beam positions:''' ''' 2C24A (X=0.5 mm, Y=0.5 mm) ''', '''2H01 (X=.6 mm, Y=.2 mm)'''
+
* the run on Ca48 until 6am, Feb 8
  
−
* '''Note 4: Do not turn OFF FTOF HVs, even during the beam tune with CW beam (turn off if tuned/pulsed beam in the upstream beamline)'''
+
* 6am Feb 8: Investigate BLA tune beam trips with tune beam to Hall B, https://devweb.acc.jlab.org/CSUEApps/atlis/task/24015
  
−
* '''Note 5: In case of a Torus and/or Solenoid Fast Dump do the following:
+
* RC will be there at 6 am and follow Eugene's instruction
−
*# Notify MCC to request beam OFF and to drop Hall B status to Power Permit
+
** put the blank collimator in
−
*# Call Engineering on-call
+
** turn HV off for all tracking detectors, just in case if the tagger magnet trips during the test
−
*# 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
+
** MCC may mask upstream halo FSD if necessary but keep all other FSD unmasked
−
*# Notify Run Coordinator
 
−
*# Turn off all detectors'''
 
  
−
*'''Note 6: When beam is being delivered to the Faraday Cup:'''
+
== <font color=blue> DAQ configuration </font> ==
−
*# the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state <font color=red>UNMASKED</font>
 
−
*# No changes to the FSD threshold should be made without RC or beamline expert approval
 
  
−
*'''Note 7: Do not turn on the SVT or MM - only the SVT or MM expert can do that'''
+
<b> PROD67_noVTPread </b>, production trigger <b> rgm_6GeV_inb_v1_0.trg </b>. <br/>
  
−
*'''Note 8: Any request for a special run or change of configuration has to be approved by the RC & documented'''
+
<font color=blue><b> NOTE: UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to do a RICH recovery - instead do this in between runs.  </b></font>
 +
<br/>
  
−
*'''Note 9: Carefully check the BTA every hour and run the script <font color=red>btaGet.py</font> to print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.'''
+
<font color=blue><b> NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems. </b></font>
 +
<br/>
  
−
*'''Note 10: Reset CLAS12MON frequently to avoid histogram saturation.'''
+
<b> At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font> </b>'''<br>
 +
*  "end run", if the run ended correctly then: "prestart", "go"
 +
<!-- This needs to be followed at the end of every run. Note: this might be different from the instructions coming up on RunControl. -->
 +
<b><font color=red>
 +
* if the run did not end correctly or if any ROCs had to be rebooted:
 +
* "cancel", "reset"
 +
** "configure", "download", "prestart", "go"
 +
* After each step, make sure it is completed in the Run Control message window.</font></b> If a ROC has crashed, find which one it is, issue a roc_reboot command ON JUST THAT ROC and try again. Contact the DAQ expert if there are any questions.
  
−
*'''Note 11: Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/ https://clas12mon.jlab.org/mon12/histograms/]'''
+
== <font color=blue> References and Standards </font>==
 +
''(last update 01/18/2022- 23:30)''
  
−
{| {{TableStyle1}}
+
<b> Nominal Beam Positions </b>
 +
*2H01, X: -0.6 mm, Y: 0.8 mm
 +
*2C24, X: -2.0 mm, Y: +0.6 mm
  
−
| valign=top width=50% |
+
<b> FSD Thresholds </b>
 +
* Upstream: 2000 Hz
 +
* Midstream: 2000 Hz
 +
* Downstream: 500000 Hz
 +
* BOM: 10000
 +
* 5 ms dwell time
  
−
== <font color=blue>''' Run Plan:'''</font>==
+
<b> Reference Harp Scans for Beam on Faraday Cup: </b> 2H01  [https://logbooks.jlab.org/entry/3963256]
−
<i>(Updated: Oct. 3 2018 at 14:30)</i>
 
  
−
* <font color=red> ''' Make sure that the FSD thresholds are set correctly and they are unmask when ready to receive beam to the FC'''</font>
+
<b> Reference Harp Scans for Beam on Tagger dump: </b> 2C21 [https://logbooks.jlab.org/entry/3963244], tagger harp [https://logbooks.jlab.org/entry/3963250]
  
−
* As soon 2 nA run is finished notify Ben and Sergei that they can go to th hall
+
<b> Reference Monitoring Histograms:</b>
−
* When they finish the work in the hall continue to take data with 60 nA and 75 nA beams, 5M each
+
* [https://logbooks.jlab.org/entry/3982817 6 GeV 80 nA on Ca48]
−
** The DAQ configuration for these runs is PROD66_PIN
+
* [https://logbooks.jlab.org/entry/3980929 6 GeV 90 nA on Sn]
−
** For each of runs, in addition to standard Beamline overview and monitoring plots, send to the logbook the DC HV, SVT currents.
+
* [https://logbooks.jlab.org/entry/3973807 6 nA, production C]
−
* When Luminosity scan runs are finished, go to the production and take data with 45 nA beam.
+
* [https://logbooks.jlab.org/entry/3943458 50 nA, production LD2]
−
** NOTE for this please use PROD66 configuration for DAQ.
 
−
** For every run please submit to the logbook all the screens listed in the "Every Run" section
 
−
* Andrea should call in between 8:00 - 8:30 in order to take special trigger runs for hadron trigger validation.
 
−
** The beam current should be 45 nA, and He will take care of the DAQ.
 
−
** With good beam it will take approximately 4-6 hours.
 
  
 +
<b> Counter rates </b>
 +
* Upstream counters integrated rates: 0-15 Hz (acceptable up to 100 Hz are acceptable) @50 nA.
 +
* Midstream counters: 10-20 Hz (acceptable up to 50 Hz) @50 nA.
 +
* Counting rates of ~ hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.
  
−
* Any questions call system expert, RC or PDL.
+
<b> Beamline vacuum: </b> should be not higher than 5e-5.
  
−
<!--* Sunday 9:00 a.m. will perform
+
= Notes/Known Issues =
−
* With all detectors on, perform current scan
+
<!--#######################################  Notes/Known Issues  ################################################-->
−
** before starting, notify experts for SVT/MM, ECAL, FTOF/CTOF so they can monitor scan
 
−
** check rates vs. beam current to 150 nA (use 5 nA, 20 nA, 50 nA, 75 nA, 100 nA, 150 nA)
 
−
** record detector rates (FTOF, ECAL, CTOF) and tracking detector currents (DC, CVT) in logbook and record currents on CTOF, FTOF, and PCAL ammeters (see links on-->
 
  
 +
'''NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms (mon12) at least once every 30-60 minutes to make sure there are no major detector problems.'''
  
 +
== <font color=blue> Notes </font> ==
  
 +
#'''LTCC''' is NOT used in this experiment. HV should be kept OFF.
 +
# '''FMT''' only using 3 FMT layers, not 6.
 +
# 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 access, they should be switched off when leaving the Hall. Refer to these photos:
 +
#* ON: [https://logbooks.jlab.org/entry/3825712]
 +
#* OFF: [https://logbooks.jlab.org/entry/3825731]
 +
#* Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cool down.
 +
# In case of a '''Torus and/or Solenoid Fast Dump''' do the following:
 +
#* Notify MCC to request beam OFF and to drop Hall B status to Power Permit
 +
#* Call Engineering on-call
 +
#* Make a separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Probir Goshal, Dave Kashy, and esr-users@jlab.org
 +
#* Notify Run Coordinator
 +
#* Turn off all detectors
 +
# Observe the guidance of the alarm handler.
  
−
<!--* Complete empty target run at 80 nA
 
−
* Continue data taking with empty target at 100 nA
 
−
* At 7:00 a.m. give the DAQ to Andrea and Nick to perform gain matching for the FT Hodoscope
 
−
* At 9:00 a.m. there will be pass change for Hall A so no beam for couple of hours during the day shift
 
−
* Run plan will be update after 8:00 a.m. MCC meeting for the day shift
 
−
* When beam is off for pass change ask MCC to energize the tagger
 
−
* During this time test target filling
 
−
1) Before the start of beam delivery:
 
−
* When Hall B goes into Restricted Access and before beam comes into the hall, make sure all CLAS12 detectors are turned off
 
−
* Check that torus field is -100% (negatives inbending) and solenoid field is -100% (contact PDL to change fields)
 
  
−
1) Complete beam tuning studies - <font color="red">This effort will be carried out under the direction of the beamline expert</font>
 
−
* Complete beam tuning to the tagger yoke beam dump following the procedures in the beam tuning document
 
−
* Take a Moller run
 
−
* Complete beam tuning to Faraday Cup with empty target following procedures in the beam tuning document
 
−
* Perform beam centering using BOM and FT-Cal along with beamline halo monitors
 
−
* Make sure harp scans results for 2C21, 2C24, and 2H01 are posted in the logbook (these will represent our baseline results for the fall 2018 run)
 
−
* Record nominal beam positions at BPMs in the logbook (these will represent our nominal values for the fall 2018 run)
 
−
* Ensure FSD settings are proper
 
  
−
2) With empty target:
+
== <font color=blue> Known Issues </font> ==
−
* With 5 nA beam, turn on CLAS12 detectors from least sensitive to most sensitive (call SVT and MM experts to turn their systems on).
 
−
* Check DAQ rates and trigger performance with May 2018 setup. The current trigger configuration : trigger_v20_1.trg.  This work will be completed under the direction of the DAQ expert.
 
  
−
4) Once all everything is checked:
+
* '''Beamline overview''' No Data from Faraday cup viewer camera, network switch died
  
−
a) Fill the target (call Bob Miller for this step; number on whiteboard)
+
* '''DAQ''' when starting a run, the live time alarm goes off, while status of the ROCs all ok, then the alarm can just be acknowledged
 +
* '''DAQ''' The error messages " ERR: event# ..." e.g. for crates tdcband1, tdcecal1 and tdcecal6 are NOT a problem. Can go along with relatively higher roc rates.
  
−
b) Turn beam back on at 5 nA - ensure FSD settings are proper
+
* '''PCAL''' transient: mu strip occupancy hole in U view TDC, https://logbooks.jlab.org/entry/3978499, https://logbooks.jlab.org/entry/3978736
 +
* '''ECAL''' one strip of TDC ECout W strip sector4 is hot, https://logbooks.jlab.org/entry/3979286
 +
* '''ECAL''' HV SEC2_WI_E36 is known to be problematic. Channel stays off for now.
  
−
c) Complete DC HV setting scan
+
* '''BMT''' off: histogram occupancy Z, layer 3, sector 1, detetcor 7, S1L3 strip HV is off due to high leakage, https://logbooks.jlab.org/entry/3970886
−
* See log entry [https://logbooks.jlab.org/entry/3590854 3590854] for settings. Take data for 15 min with 10 nA for each setting. Be sure to reset to the fault HV settings at the end of the test plan R1/R2/R3 #8/#9/#9.-->
+
* '''BMT''' off: histogram occupancy Z, layer 5, sector 2, detetcor 14
 +
* '''BMT''' SEC1 L1 STRIP: reduced HV. (This tile will have almost 0 efficiency), https://logbooks.jlab.org/entry/3982425
  
−
<!--
+
* '''RICH''' recovery only between runs. also when you see problems like a missing tile
−
* Complete MM setting optimization. This work will be completed under the direction of the MM experts.
+
* '''RICH''' FPGA temperatures can show yellow tiles. Yellow tiles in the RICH temperature map are normal. It is done just to pay attention to the tiles with temp>70 degrees. The alarm is set to 75 degrees https://logbooks.jlab.org/entry/3975547
−
* Take empty target run (8 hrs at 20 nA)
 
−
* With all detectors on, perform current scan
 
−
** before starting, notify experts for SVT/MM, ECAL, FTOF/CTOF so they can monitor scan
 
−
** check rates vs. beam current to 150 nA (use 5 nA, 20 nA, 50 nA, 75 nA, 100 nA, 150 nA)
 
−
** record detector rates (FTOF, ECAL, CTOF) and tracking detector currents (DC, CVT) in logbook and record currents on CTOF, FTOF, and PCAL ammeters (see links on monitoring tab to access cameras; username/password on whiteboard)
 
−
* Take empty target run (4 hrs at 150 nA)
 
−
* Check DAQ rates and trigger performance with August 2018 setup. This work will be completed under the direction of the DAQ expert.
 
−
* Perform initial trigger test plans (trigger checks and optimization, study of DC tracking trigger, FTOF/PCAL matching). This work will be completed under the direction of the trigger experts.
 
−
* At end of run, have MCC turn the beam off.
 
  
−
<font color="red"> Call RC before proceeding with the following tasks:</font>
+
= Shift Expert =
 +
<!--#######################################  Shift Expert  ################################################-->
 +
{| {{TableStyle1}}
 +
| valign=top |
  
−
4a) Fill the target (call Bob Miller for this step; number on whiteboard)
+
'''NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms at least once every 30 - 60 minutes to make sure there are no major detector problems.'''
  
−
5a) Turn beam back on at 5 nA - ensure FSD settings are proper
+
* Follow the '''[[https://wiki.jlab.org/clas12-run/index.php/Run_Group_M#Short_Term_Schedule Short Term Schedule]]''' as outlined by RC
 +
** includes Run Plan, DAQ configuration, and References and Standards
 +
* Keep '''shift summary''' up to date in HBLOG. Record all that happens.
  
−
6a) Complete DC HV setting scan
+
* '''Cycle the FMT gas once per shift''', in-between runs. Pease log in shift summary.
−
* See log entry [https://logbooks.jlab.org/entry/3590854 3590854] for settings. Take data for 15 min with 10 nA for each setting. Be sure to reset to the fault HV settings at the end of the test plan R1/R2/R3 #8/#9/#9.
+
** If it is not reset, the interlock may drop and disable the HV.
 +
** Turning off and on the  gas flow without pausing to avoid HV trips.  
 +
** If the HV tripped, make sure that once gas flow is restarted and the flow differential is down to reasonable values, to turn the FMT HV back on and let it ramp all the way up.
 +
** Remember that this experiment is only using 3 FMT layers, not 6.
  
−
7a). Complete any remaining MM setting optimizations. This work will be completed under the direction of the MM experts.
+
* Do a '''RICH recovery''' (press the RICH Recovery button on the GUI) once daily during day shift, between runs. Please log in shift summary.
 +
** Note the automated "RICH Recovery" sequence already confirms RICH4 is up and accepting ssh connections before claiming success. And it also prints out that you have to "Cancel->Reset->Configure->Download->Prestart" before starting the next run.
  
−
8a) Perform current scan
+
* '''[https://bta.acc.jlab.org Fill out BTA]''' hourly.  Click "Load from EPICS" to automatically fill the left side then correct as needed.
−
* before starting, notify experts for SVT/MM, ECAL, FTOF/CTOF so they can monitor scan
+
** Accelerator beam time:
−
* check rates vs. beam current to 75 nA (use 2 nA, 10 nA, 30 nA, 50 nA, 75 nA)
+
*** ABU: acceptable beam used (eg harp scans, calibrations, trigger settings, running)
−
* record detector rates (FTOF, ECAL, CTOF) and tracking detector currents (DC, CVT) in logbook and record currents on CTOF, FTOF, and PCAL ammeters (see links on monitoring tab to access cameras; username/password on whiteboard)
+
*** BANU: beam acceptable but not used (eg radiator change or our problems)
−
* DC experts should use this period to finalize their HV and discriminator thresholds
+
*** BNA: beam not acceptable (eg tuning, drifting, not focused)
−
* CVT experts should use this period to study currents and stability
+
** Experiment beam time
−
* After studies call for Hall B access to recover FTOF, ECAL, and CTOF channels plugged into ammeters (call FTOF/CTOF and ECAL experts for this work). Use rapid-access protocol.
+
*** ER: experiment ready
 +
*** PCC: planned configuration change (when beam is masked while radiators are moved, DAQ (roc rebooting,  restarting runs)), if more than 5 minutes, put a short comment, eg harp scans or DAQ.
 +
*** UED: unplanned experiment down (hardware failure)
  
−
9a) Optimize the FT settings (FT group will take over DAQ control remotely and complete task). This should be done (preferably) during the owl shift.
 
  
−
10a) Check DAQ rates and performance (including initial studies of FADC bit packing)
+
'''In case of other questions or uncertainties of what to do, call the RC or PDL'''
  
−
11a) Perform trigger test plans (trigger checks and optimization, study of DC tracking trigger, FTOF/PCAL matching). This work will be completed under the direction of the trigger experts
+
(remote) shift worker: see dedicated [https://wiki.jlab.org/clas12-run/index.php/Run_Group_M#tab=Remote_Shifts Remote Shifts] tab above.
  
−
12a) Complete a luminosity scan and record data in the following sequence with the standard RG-A trigger:
+
|}
−
* 2 nA - 6 hrs
 
−
* 10 nA - 2 hrs
 
−
* 30 nA - 30 min
 
−
* 50 nA - 30 min
 
−
* 75 nA - 30 min
 
  
−
13a) Take data with the standard RG-A trigger at 20 nA for 4 hrs to collect data for baseline subsystem calibrations
+
= Remote Worker Shift =
  
−
14a) Take production data with the standard RG-A trigger at 40 nA (3 hr runs)
+
{| {{TableStyle1}}
  
−
<font color="red"> target is  functional:  These tasks will be scheduled for later dates</font>
+
| valign=top |
  
−
4b) Ramp torus to 0% field (call Engineering for this step)
 
  
−
5b) Take data at 2 nA for DC alignment studies for 1 hr
+
* '''Zoom for 24-7 communication with counting house:'''  https://jlab-org.zoomgov.com/j/1619881100
 +
** Passcode REQUIRED: 927417
 +
* Remind the expert in the counting house to restart their zoom, if necessary
  
−
6b) Have MCC turn the beam off
+
* Remote VNC connection instructions:  https://logbooks.jlab.org/entry/3906039
 +
** All necessary applications should be avaible from the desktop menu (left/right click on the desktop)
 +
* EPICS GUIs should be accessed '''ONLY''' via the desktop menu or by running <tt>clascss-remote</tt>.
 +
* [https://userweb.jlab.org/~baltzell/clas12/shift/remote-demo.mp4 Remote Demonstration Video (150 MB)]
  
−
7b) Ramp solenoid to 0% field (call Engineering for this step)
 
  
−
8b) Take data at 2 nA with both magnets for DC and CVT alignment studies off for 8 hrs
+
=== Tasks ===
  
−
9b) Take Moller run - work with MCC to maximize electron beam polarization (should be >86%)-->
 
  
−
== <font color=blue>''' Shift Worker Notes:'''</font>==
+
'''Every Run:'''
  
−
* 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.
+
* WITH BEAM, log screen shots of
 +
** Beamline Overview, in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser]
 +
** CLAS12 Trigger rates and DAQ status
  
−
* If the machine is down for few hours 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 40 nA and continue data for production. If there are issues with the beam call the RC. Sometimes MCC operator might ask to deliver tuned 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.
+
* upload monitoring plots (mon12) to logook
 +
** '''look at the spectra''': Reference, current, and 5 most recent runs, choose a reference run (the reference numbers refer to logbook entries):
 +
*** 6 GeV 80 nA on Ca48 [https://clas12mon.jlab.org/mon12/histograms/?reference=3982817 https://clas12mon.jlab.org/mon12/histograms/?reference=3982817]
 +
*** 6 GeV 90 nA on Sn [https://clas12mon.jlab.org/mon12/histograms/?reference=3980929 https://clas12mon.jlab.org/mon12/histograms/?reference=3980929]
 +
*** ref 6 nA, production C, [https://clas12mon.jlab.org/mon12/histograms/?reference=3973807 https://clas12mon.jlab.org/mon12/histograms/?reference=3973807]
 +
*** ref 50 nA, production LD2, [https://clas12mon.jlab.org/mon12/histograms/?reference=3943458 https://clas12mon.jlab.org/mon12/histograms/?reference=3943458]
  
−
* Sometimes, a couple RICH channel scalers go to 0 and there is no alarm, even though the "# of fibers connected" would be shown to be the correct 138. Shift takers therefore should periodically, especially at the end of run, check the RICH scalers GUI. If there is an issue:
+
'''Every Shift:'''
−
** For RICH recovery procedures, please see Log entry https://logbooks.jlab.org/entry/3562273.  This would apply in the cases of  1. DAQ crash: rich4 is not responding or 2. RICH alarms (LV,missing tile, temperature etc). If it does not work or you are uncertain about what to do, contact the RICH expert on call.
 
  
−
'''In case of other questions or uncertainties of what to do, call the RC'''
+
* Fill the [https://logbooks.jlab.org/checklists/151 shift checklist]
  
−
<!--
+
* Log screen shots of RICH temperature and scaler maps. Log in HBLOG and RICH logbook.
−
'''[[Every Shift:]]'''
+
 
−
*Follow run plan as outlined by RC
+
'''Regularly''':
−
* 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.
+
* <font color=red>'''reset & check spectra frequently (every 30 - 60 minutes)'''</font>
−
* Check on white board all scalers, strip charts and monitoring plots that need to be logged regularly
+
** Some plots in '''mon12''' have a '''choice of histogram sets per sector''', select buttons at the bottom of the plot. Only the currently selected set ends up in the logbook entry.
−
* Document any beam condition change and send scaler GUIs to HBLOG
+
** that means you have to '''look at all sectors for these histograms'''
−
* [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side.
 
−
*Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
 
  
−
'''[[Every Run:]]'''
+
* Log the '''strip charts''' in time intervals '''according to the x-axis time span''', using the liveplot configuration '''Beamline4Logbook''', see https://logbooks.jlab.org/entry/3978837 .
−
''Log screenshots of:''
+
** in VNC: use CS-Studio, Tools, Strip Charts, livePlot
−
* main scaler GUI display
+
*** right-click on the livePlot screen and select "Load a Configuration"
−
* Detector occupancy plots
+
*** the configuration "Beamline4Logbook" provides the beam current and position information
−
* Trigger rate GUI
+
*** right-click on the screen and select "Make Elog Entry", make sure to log to HBLOG and not ELOG
−
* Beam strip charts
 
−
* FT-Cal FADC scalers
 
  
−
-->
+
* in Web Browser: [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Upstream+and+Midstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scaler_cS3b&pv=scaler_cS4b&pv=scaler_cS6b&pv=scaler_cS12b&pv=scaler_cS13b&pv=scaler_cS14b&pv=scaler_cS15b&scaler_cS3blabel=scaler_cS3b&scaler_cS3bcolor=%23a6cee3&scaler_cS3byAxisLabel=Rate++%28Hz%29&scaler_cS3byAxisMin=&scaler_cS3byAxisMax=&scaler_cS3byAxisLog&scaler_cS3bscaler=&start=2020-08-08+09%3A02%3A36&end=2020-08-08+09%3A07%3A36&scaler_cS4blabel=scaler_cS4b&scaler_cS4bcolor=%231f78b4&scaler_cS4byAxisLabel=&scaler_cS4byAxisMin=&scaler_cS4byAxisMax=&scaler_cS4byAxisLog=&scaler_cS4bscaler=&scaler_cS5byAxisLabel=&scaler_cS5byAxisMin=&scaler_cS5byAxisMax=&scaler_cS5byAxisLog=&scaler_cS5bscaler=&scaler_cS6blabel=scaler_cS6b&scaler_cS6bcolor=%2333a02c&scaler_cS6byAxisLabel=&scaler_cS6byAxisMin=&scaler_cS6byAxisMax=&scaler_cS6byAxisLog=&scaler_cS6bscaler=&scaler_cS7byAxisLabel=&scaler_cS7byAxisMin=&scaler_cS7byAxisMax=&scaler_cS7byAxisLog=&scaler_cS7bscaler=&scaler_cS12blabel=scaler_cS12b&scaler_cS12bcolor=%23e31a1c&scaler_cS12byAxisLabel=&scaler_cS12byAxisMin=&scaler_cS12byAxisMax=&scaler_cS12byAxisLog=&scaler_cS12bscaler=&scaler_cS13blabel=scaler_cS13b&scaler_cS13bcolor=%23fdbf6f&scaler_cS13byAxisLabel=&scaler_cS13byAxisMin=&scaler_cS13byAxisMax=&scaler_cS13byAxisLog=&scaler_cS13bscaler=&scaler_cS14blabel=scaler_cS14b&scaler_cS14bcolor=%23ff7f00&scaler_cS14byAxisLabel=&scaler_cS14byAxisMin=&scaler_cS14byAxisMax=&scaler_cS14byAxisLog=&scaler_cS14bscaler=&scaler_cS15blabel=scaler_cS15b&scaler_cS15bcolor=%23cab2d6&scaler_cS15byAxisLabel=&scaler_cS15byAxisMin=&scaler_cS15byAxisMax=&scaler_cS15byAxisLog=&scaler_cS15bscaler= Upstream/Midstream Halo Counters], [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Downstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scalerS8b&pv=scalerS9b&scalerS8blabel=scalerS8b&scalerS8bcolor=%23a6cee3&scalerS8byAxisLabel=Rate++%28Hz%29&scalerS8byAxisMin=&scalerS8byAxisMax=&scalerS8byAxisLog&scalerS8bscaler=&pv=scalerS10b&pv=scalerS11b&scalerS9blabel=scalerS9b&scalerS9bcolor=%231f78b4&scalerS9byAxisLabel=&scalerS9byAxisMin=&scalerS9byAxisMax=&scalerS9byAxisLog=&scalerS9bscaler=&scalerS10blabel=scalerS10b&scalerS10bcolor=%23b2df8a&scalerS10byAxisLabel=&scalerS10byAxisMin=&scalerS10byAxisMax=&scalerS10byAxisLog=&scalerS10bscaler=&scalerS11blabel=scalerS11b&scalerS11bcolor=%2333a02c&scalerS11byAxisLabel=&scalerS11byAxisMin=&scalerS11byAxisMax=&scalerS11byAxisLog=&scalerS11bscaler= Downstream Halo Counters], [https://epicsweb.jlab.org/wave/?start=2020-07-08+16%3A50%3A02&end=2020-07-08+16%3A55%3A02&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Beam+Currents&fullscreen=false&layoutMode=2&viewerMode=2&pv=IPM2C21A&pv=IPM2C24A&pv=scaler_calc1b&IPM2C21Alabel=IPM2C21A&IPM2C21Acolor=%23a6cee3&IPM2C21AyAxisLabel=Beam+Current+%28nA%29&IPM2C21AyAxisMin=0&IPM2C21AyAxisMax=300&IPM2C21AyAxisLog&IPM2C21Ascaler=&scaler_calc1blabel=Faraday+Cup&scaler_calc1bcolor=%23b2df8a&scaler_calc1byAxisLabel=&scaler_calc1byAxisMin=&scaler_calc1byAxisMax=&scaler_calc1byAxisLog&scaler_calc1bscaler= Beam Currents], [https://epicsweb.jlab.org/wave/?start=2020-08-03+12%3A30%3A57&end=2020-08-03+12%3A35%3A57&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=BPM+Positions+%28Y-Axis+is+mean+%2B%2F-+0.5+mm%29&fullscreen=false&layoutMode=3&viewerMode=2&pv=IPM2C24A.XPOS&pv=IPM2C24A.YPOS&pv=IPM2H01.XPOS&pv=IPM2H01.YPOS&IPM2C24A.XPOSlabel=IPM2C24A.XPOS&IPM2C24A.XPOScolor=%23e31a1c&IPM2C24A.XPOSyAxisLabel=&IPM2C24A.XPOSyAxisMin=-2.0&IPM2C24A.XPOSyAxisMax=+1.0&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=pink&IPM2C24A.YPOSyAxisLabel=&IPM2C24A.YPOSyAxisMin=-2.0&IPM2C24A.YPOSyAxisMax=1.0&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=darkgreen&IPM2H01.XPOSyAxisLabel=&IPM2H01.XPOSyAxisMin=-2.0&IPM2H01.XPOSyAxisMax=1.0&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=lightgreen&IPM2H01.YPOSyAxisLabel=&IPM2H01.YPOSyAxisMin=-2.0&IPM2H01.YPOSyAxisMax=1.0&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler=#a6cee3&IPM2C24A.XPOSyAxisLabel=2C24+X+(mm)&IPM2C24A.XPOSyAxisMin=-1.5&IPM2C24A.XPOSyAxisMax=-0.5&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=%231f78b4&IPM2C24A.YPOSyAxisLabel=2C24+Y+(mm)&IPM2C24A.YPOSyAxisMin=0.3&IPM2C24A.YPOSyAxisMax=1.3&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=pink&IPM2H01.XPOSyAxisLabel=2H01+X+(mm)&IPM2H01.XPOSyAxisMin=-0.6&IPM2H01.XPOSyAxisMax=0.4&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=darkred&IPM2H01.YPOSyAxisLabel=2H01+Y+(mm)&IPM2H01.YPOSyAxisMin=0.4&IPM2H01.YPOSyAxisMax=1.4&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler= BPM Positions]
−
| valign=top |
 
  
−
==<font color=blue>''' General Instructions''':</font>==
 
  
−
* For a given beam current, compute the FSD thresholds according to the [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf Establish Physics Quality Beam] document. Call MCC to update the values. Contact the beamline expert if there are questions about setting the FSD thresholds.
+
| valign=top |
−
* 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.
 
−
* 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.
 
−
* Reference harp scans: [https://logbooks.jlab.org/entry/3571664 2C21], [https://logbooks.jlab.org/entry/3571676 2C24], [https://logbooks.jlab.org/entry/3571859 2H01]
 
  
−
'''Every Shift:'''
+
<!--
−
*Follow run plan as outlined by RC
+
== Shift Worker Backup Table ==
−
* If any concern about beam stability, ask MCC if orbit locks are on (they should be).
+
{| class=wikitable
−
* Keep shift summary up to date in HBLOG. Record all that happens.
+
!width=600 colspan=4 style="background:#ffdead;"| '''Worker Shift Backup'''
−
* 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
+
| style="background:#ffdead;"|  '''Date''' || style="background:#ffdead;"|  '''Day''' || style="background:#ffdead;"| '''Swing''' || style="background:#ffdead;"| '''Owl'''  
−
* [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side.
+
|-
−
* Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
+
| Fri, Oct 15 ||  John Doe || Jane Doe || Domenico D'Urso
 +
|-
 +
| Sat, Oct 16 ||  Jane Doe || Bob Cat || Alber Einstein
 +
|}
 +
-->
  
−
'''Every Run:'''
+
{| class=wikitable
 +
!width=600 colspan=3 style="background:#deffad;"| '''Backup shifter contact info'''
 +
|-
 +
| style="background:#deffad;"|  '''Name''' || style="background:#deffad;"|  '''Email''' || style="background:#deffad;"| '''Cell phone'''
 +
|-
 +
| Justin Estee || esteejus@mit.edu ||
 +
|-
 +
| Andrew Denniston || awild@mit.edu ||
 +
|-
 +
| Sara Ratliff || ratliff_sara@gwmail.gwu.edu ||
 +
|-
 +
| Erin Seroka || erinseroka@gwmail.gwu.edu ||
  
−
'' Log screenshots of:''
+
|}
−
* main scaler GUI display
 
−
* Detector occupancy plots
 
−
* Trigger rate gui
 
−
* Beam strip charts
 
−
* FTCalo FADC scalers
 
  
 
|}
 
|}
Line 315: Line 323:
 
| valign=top |
 
| valign=top |
 
===Webcams===
 
===Webcams===
−
* [http://hallbcam06.jlab.org/ Faraday Cup Beam Viewer]
 
 
* [http://cctv1.jlab.org Tagger Beam Dump Viewer]
 
* [http://cctv1.jlab.org Tagger Beam Dump Viewer]
 
* [http://cctv12.jlab.org CND/CTOF Ammeter]
 
* [http://cctv12.jlab.org CND/CTOF Ammeter]
Line 321: Line 328:
 
* [http://hallbcam02.jlab.org Hall Fisheye]
 
* [http://hallbcam02.jlab.org Hall Fisheye]
 
* [http://cctv11.jlab.org Saclay Cryotarget]
 
* [http://cctv11.jlab.org Saclay Cryotarget]
 +
* Faraday Cup Beam Viewer
 +
** To reboot it, run <tt>beam-viewer-reboot</tt> on a clonpc.
  
 
| valign=top |
 
| valign=top |
Line 327: Line 336:
 
*[https://wiki.jlab.org/clas12-run/images/f/fd/CLAS12Mon_documentation.pdf MON12 Manual]
 
*[https://wiki.jlab.org/clas12-run/images/f/fd/CLAS12Mon_documentation.pdf MON12 Manual]
 
*[https://wiki.jlab.org/clas12-run/images/a/ae/Online_shifts.pdf  off-line Manual]
 
*[https://wiki.jlab.org/clas12-run/images/a/ae/Online_shifts.pdf  off-line Manual]
 +
 +
| valign=top |
 +
===Hall Webcams===
 +
* [https://hallach-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall A]
 +
* [https://hallbch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall B]
 +
* [https://hallcch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall C]
 +
* [https://halldch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall D]
  
 
| valign=top |
 
| valign=top |
Line 332: Line 348:
 
* [https://hallbopi.jlab.org/webopi3.3/w Hall B WebOPI] (CUE Login)
 
* [https://hallbopi.jlab.org/webopi3.3/w Hall B WebOPI] (CUE Login)
 
* [https://epicsweb.jlab.org Accelerator] (CUE Login)
 
* [https://epicsweb.jlab.org Accelerator] (CUE Login)
 +
 +
 +
| valign=top |
 +
===Live Monitoring Links===
 +
*[https://clas12mon.jlab.org/rgm/pass0_online_qa/tlsummary/ CLAS12 Monitoring Timelines]
 +
*[https://clasweb.jlab.org/clas12online/timelines/rg-m/RGM2022_progress_charge.html Live Charge Collected Plots]
 +
*[https://clasweb.jlab.org/clas12online/timelines/rg-m/RGM2022_progress.html Live Luminosity Collected Plots]
 +
  
 
|}
 
|}
 +
 +
  
 
{| {{TableStyle1}}
 
{| {{TableStyle1}}
−
| valign=top |
+
| valign=center |
−
[[Image:chart.jpeg|chart.jpeg|700px]]
+
[[File:RGM_monitoring_dec_21_charge.png|1100px]]
 +
 
  
−
| valign=top |
 
−
[[Image:moller_measurement_rg-a.jpg|500px]]
 
 
|}
 
|}
 +
 +
  
 
= Useful Links =
 
= Useful Links =
Line 353: Line 380:
 
* [https://clas12mon.jlab.org/ CLAS12 mon page]
 
* [https://clas12mon.jlab.org/ CLAS12 mon page]
 
* [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/charge/ Accumulated Charge]
 
* [https://clas12mon.jlab.org/datasize/ Accumulated datasize]
 
* [https://clas12mon.jlab.org/datasize/ Accumulated datasize]
 +
* [https://docs.google.com/spreadsheets/d/1KazAyOTyajKfq6xMqFSQJBYTAEPN80TlgtkLOytvFUA/edit?usp=sharing Run Coordinator Schedule]
 +
* [https://docs.google.com/spreadsheets/d/1WOXy15v5imrpeAVoLV9D-qU4dyjqf2VRKmhkqVtGBM4/edit?usp=sharing Target and Run Plan Summary]
 +
* [https://docs.google.com/spreadsheets/d/1xKeXvBn_euvj17BU_hW6Zvrfq9bOgUILlinU_CR2YXQ/edit?usp=sharing Full Run Plan]
 +
 
===Run lists===
 
===Run lists===
  
Line 359: Line 391:
 
===Accelerator===
 
===Accelerator===
 
* [http://accboard.acc.jlab.org Accelerator Whiteboard]
 
* [http://accboard.acc.jlab.org Accelerator Whiteboard]
−
* [http://opweb.acc.jlab.org/CSUEApps/bta03/pd_shiftplan_history.php Program Deputy Shift Plans]
+
* [https://accweb.acc.jlab.org/apps/pd/shift-plans Program Deputy Shift Plans]
−
* [http://opweb.acc.jlab.org/internal/ops/ops_webpage/run_coord/runcoord_form.php?action=main Run Coordinator Reports]
+
* [https://cebaf.jlab.org/pd/run-coordinator-reports Run Coordinator Reports]
 +
** [https://accweb.acc.jlab.org/btm/reports/physics-summary Beam Time Accounting Reports]
 +
 
 +
===References===
 +
* [https://www.jlab.org/exp_prog/proposals/18/PR12-18-003.pdf Proposal]
 +
 
 
| valign=top |
 
| valign=top |
−
===Bluejean meetings===
 
  
−
* [https://bluejeans.com/7572697303] RGM RC and analysis meetings XXXXXXXX
+
===ZOOM meetings===
 +
 
 +
* 07:45 [https://jlab-org.zoomgov.com/j/1611843361?pwd=YU55WVVwVS9ZVDEvT1I5M1VIbnJyQT09 RC/PD Morning Meeting]
 +
* 08:00 [https://jlab-org.zoomgov.com/j/1601304841?pwd=Z1RIOVVUdkdXL2R2LzREZUNOUlh1dz09 MCC/OPS Morning Meeting]
 +
*15:30 Daily RC Meeting
 +
** [https://jlab-org.zoomgov.com/j/1612697153?pwd=d3ZRdWgxMEJoTlZmWC9GTFZxb2dUZz09 Zoom Link]
 +
** Meeting ID: 161 269 7153
 +
** Passcode: 474207
 +
** Daily Analysis Meeting to follow directly after
 +
** [[RGM_RC_Meetings | Meeting Agendas]]
 +
 
 
|}
 
|}
  

Latest revision as of 13:53, 25 July 2024

[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+[ten digit number]

Role Phone Number
Hall B Run Coordinator (757) 575-7540 (cell)
Hall B Physics Division Liaison (757) 876-1789 (cell)
MCC 7048
Crew Chief 7045
Crew Chief (757) 876-3367 (cell)
Program Deputy (757) 876-7997 (cell)
RadCon (757) 876-1743 (cell)
Gate House Guard 5822
Location Phone Number
Hall B Floor 5165
Hall B Space Frame 5170 and 5171
Hall B Forward Carriage 5371
Hall B Gas Shed 7115
Hall B Counting House 5244 (Shift Expert)
Hall B Counting House (757) 329-4846 (Shift Expert cell)
Hall B Counting House 5245 or 5126 (Shift Worker)
Hall A Counting House 5501
Hall C Counting House 6000
Hall D Counting House 5504
Hall B System Phone Number On-Call Person
Engineering (757) 748-5048 (cell)
(757) 897-9060 (cell)		 Engineering On-Call (primary)
Denny Insley (secondary)
Slow Controls (757) 748-6922 (cell) Nathan Baltzell
Beamline (757) 303-3996 (cell) Eugene Pasyuk
DC (757) 218-4372 (cell)
(757) 748-5048 (cell)		 Florian Hauenstein (primary)
Engineering On-Call (secondary)
SVT/MVT/MM (757) 541-7539 (cell)
(757) 753-7769 (cell)		 Yuri Gotra (primary)
Rafo Paremuzyan (secondary)
ECAL (757) 810-1489 (cell) Cole Smith
FTOF/CTOF/CND (757) 344-7204 (cell) Daniel Carman
ALERT (757) 329-4844 (cell) Raphael Dupré
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)
(757) 748-6922 (cell)		 Christopher Dilks (primary)
Nathan Baltzell (secondary)
DAQ (757) 232-6221 (cell) Sergey Boiarinov
HYDRA (317) 550-9226 (cell) Torri Jeske
Authorized Hall B Solenoid/Torus Operators
Hall B Denny Insley, Morgan Cook, Eugene Pasyuk
Magnet Group Probir Ghosha, Renuka Rajput-Ghoshal
Detector Support Group Brian Eng, Pablo Campero, Tyler Lemon
DC Power Onish Kumar, Sarin Philip
  • Note, all non-JLab numbers must be dialed with an area code. When calling from a counting-house landline, dial "9" first.
  • To call JLab phones from outside the lab, all 4-digit numbers must be preceded by 757-269
  • Click Here to edit Phone Numbers. Note, you then also have to edit the current page to force a refresh.

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


CLAS12 Run Group M, Fall 2021

Beam energies: 2.1, 4.0, 6.0 GeV (1.96 GeV/pass)

RC: Susan Schadmand

PDL: Valery Kubarovsky

Run Plan: Friday, Feb 7-8, 2022

Production runs use PROD67_noVTPread and the trigger rgm_6GeV_inb_v1_0.trg .
Run duration 100M events or 4 hours, whichever comes first.

  • run 6GeV 80 nA on Ca48 target (240 mg/cm2), beam blocker IN, until SAD
  • low luminosity runs:(ca 3pm - 9pm on Feb 7)
    • 2 hrs 5nA
    • 2 hrs 10 nA
    • 2 hrs 40 nA
  • the run on Ca48 until 6am, Feb 8
  • RC will be there at 6 am and follow Eugene's instruction
    • put the blank collimator in
    • turn HV off for all tracking detectors, just in case if the tagger magnet trips during the test
    • MCC may mask upstream halo FSD if necessary but keep all other FSD unmasked

DAQ configuration

PROD67_noVTPread , production trigger rgm_6GeV_inb_v1_0.trg .

NOTE: UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to do a RICH recovery - instead do this in between runs.

NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems.

At the end of each run, follow the STANDARD DAQ RESTART SEQUENCE

  • "end run", if the run ended correctly then: "prestart", "go"

  • if the run did not end correctly or if any ROCs had to be rebooted:
  • "cancel", "reset"
    • "configure", "download", "prestart", "go"
  • After each step, make sure it is completed in the Run Control message window. If a ROC has crashed, find which one it is, issue a roc_reboot command ON JUST THAT ROC and try again. Contact the DAQ expert if there are any questions.

References and Standards

(last update 01/18/2022- 23:30)

Nominal Beam Positions

  • 2H01, X: -0.6 mm, Y: 0.8 mm
  • 2C24, X: -2.0 mm, Y: +0.6 mm

FSD Thresholds

  • Upstream: 2000 Hz
  • Midstream: 2000 Hz
  • Downstream: 500000 Hz
  • BOM: 10000
  • 5 ms dwell time

Reference Harp Scans for Beam on Faraday Cup: 2H01 [1]

Reference Harp Scans for Beam on Tagger dump: 2C21 [2], tagger harp [3]

Reference Monitoring Histograms:

Counter rates

  • Upstream counters integrated rates: 0-15 Hz (acceptable up to 100 Hz are acceptable) @50 nA.
  • Midstream counters: 10-20 Hz (acceptable up to 50 Hz) @50 nA.
  • Counting rates of ~ hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.

Beamline vacuum: should be not higher than 5e-5.

NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms (mon12) at least once every 30-60 minutes to make sure there are no major detector problems.

Notes

  1. LTCC is NOT used in this experiment. HV should be kept OFF.
  2. FMT only using 3 FMT layers, not 6.
  3. 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 access, they should be switched off when leaving the Hall. Refer to these photos:
    • ON: [4]
    • OFF: [5]
    • Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cool down.
  4. In case of a Torus and/or Solenoid Fast Dump do the following:
    • Notify MCC to request beam OFF and to drop Hall B status to Power Permit
    • Call Engineering on-call
    • Make a separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Probir Goshal, Dave Kashy, and esr-users@jlab.org
    • Notify Run Coordinator
    • Turn off all detectors
  5. Observe the guidance of the alarm handler.


Known Issues

  • Beamline overview No Data from Faraday cup viewer camera, network switch died
  • DAQ when starting a run, the live time alarm goes off, while status of the ROCs all ok, then the alarm can just be acknowledged
  • DAQ The error messages " ERR: event# ..." e.g. for crates tdcband1, tdcecal1 and tdcecal6 are NOT a problem. Can go along with relatively higher roc rates.
  • RICH recovery only between runs. also when you see problems like a missing tile
  • RICH FPGA temperatures can show yellow tiles. Yellow tiles in the RICH temperature map are normal. It is done just to pay attention to the tiles with temp>70 degrees. The alarm is set to 75 degrees https://logbooks.jlab.org/entry/3975547

NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms at least once every 30 - 60 minutes to make sure there are no major detector problems.

  • Follow the [Short Term Schedule] as outlined by RC
    • includes Run Plan, DAQ configuration, and References and Standards
  • Keep shift summary up to date in HBLOG. Record all that happens.
  • Cycle the FMT gas once per shift, in-between runs. Pease log in shift summary.
    • If it is not reset, the interlock may drop and disable the HV.
    • Turning off and on the gas flow without pausing to avoid HV trips.
    • If the HV tripped, make sure that once gas flow is restarted and the flow differential is down to reasonable values, to turn the FMT HV back on and let it ramp all the way up.
    • Remember that this experiment is only using 3 FMT layers, not 6.
  • Do a RICH recovery (press the RICH Recovery button on the GUI) once daily during day shift, between runs. Please log in shift summary.
    • Note the automated "RICH Recovery" sequence already confirms RICH4 is up and accepting ssh connections before claiming success. And it also prints out that you have to "Cancel->Reset->Configure->Download->Prestart" before starting the next run.
  • Fill out BTA hourly. Click "Load from EPICS" to automatically fill the left side then correct as needed.
    • Accelerator beam time:
      • ABU: acceptable beam used (eg harp scans, calibrations, trigger settings, running)
      • BANU: beam acceptable but not used (eg radiator change or our problems)
      • BNA: beam not acceptable (eg tuning, drifting, not focused)
    • Experiment beam time
      • ER: experiment ready
      • PCC: planned configuration change (when beam is masked while radiators are moved, DAQ (roc rebooting, restarting runs)), if more than 5 minutes, put a short comment, eg harp scans or DAQ.
      • UED: unplanned experiment down (hardware failure)


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

(remote) shift worker: see dedicated Remote Shifts tab above.



Tasks

Every Run:

  • WITH BEAM, log screen shots of
    • Beamline Overview, in VNC or Web Browser
    • CLAS12 Trigger rates and DAQ status

Every Shift:

  • Log screen shots of RICH temperature and scaler maps. Log in HBLOG and RICH logbook.

Regularly:

  • reset & check spectra frequently (every 30 - 60 minutes)
    • Some plots in mon12 have a choice of histogram sets per sector, select buttons at the bottom of the plot. Only the currently selected set ends up in the logbook entry.
    • that means you have to look at all sectors for these histograms
  • Log the strip charts in time intervals according to the x-axis time span, using the liveplot configuration Beamline4Logbook, see https://logbooks.jlab.org/entry/3978837 .
    • in VNC: use CS-Studio, Tools, Strip Charts, livePlot
      • right-click on the livePlot screen and select "Load a Configuration"
      • the configuration "Beamline4Logbook" provides the beam current and position information
      • right-click on the screen and select "Make Elog Entry", make sure to log to HBLOG and not ELOG


Backup shifter contact info
Name Email Cell phone
Justin Estee esteejus@mit.edu
Andrew Denniston awild@mit.edu
Sara Ratliff ratliff_sara@gwmail.gwu.edu
Erin Seroka erinseroka@gwmail.gwu.edu

Webcams

Manuals

Hall Webcams

Epics on the web

Live Monitoring Links



RGM monitoring dec 21 charge.png




Clas12design.png

Retrieved from "https://wiki.jlab.org/clas12-run/index.php?title=Run_Group_M&oldid=7778"