Difference between revisions of "Run Group M"

From clas12-run
Jump to: navigation, search
(Short Term Schedule)
(Short Term Schedule)
Line 140: Line 140:
 
* Production data taking with <b> rgm_6GeV_inb_v1_0.trg </b> 2 hour runs
 
* Production data taking with <b> rgm_6GeV_inb_v1_0.trg </b> 2 hour runs
  
 +
===Hall Access Items (Wednesday, November 3rd):===
  
 
+
== DAQ configuration ==
<!--
+
<b> PROD66 </b>, production trigger <b> rgm_6GeV_inb_v1_0.trg </b>
<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>
+
 
+
* As soon 2 nA run is finished notify Ben and Sergei that they can go to th hall
+
* When they finish the work in the hall continue to take data with 60 nA and 75 nA beams, 5M each
+
** The DAQ configuration for these runs is PROD66_PIN
+
** For each of runs, in addition to standard Beamline overview and monitoring plots, send to the logbook the DC HV, SVT currents.
+
* When Luminosity scan runs are finished, go to the production and take data with 45 nA beam.
+
** 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.
+
-->
+
  
  
 
== <font color=blue>''' Shift Worker Notes:'''</font>==
 
== <font color=blue>''' Shift Worker Notes:'''</font>==
<!--
+
'''In case of other questions or uncertainties of what to do, call the RC or PDL'''
* 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 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.
 
  
* 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:
 
** 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 or PDL'''
 
 
<!--
 
'''[[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
 
* [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:]]'''
 
'''[[Every Run:]]'''
  ''Log screenshots of:'' (this is for the remote shifter, see dedicated tab above.)
+
  ''Log screenshots of:'' (this is for the remote shifter)
 
* Main beamline GUI overview
 
* Main beamline GUI overview
 
* clas12mon Detector occupancy plots
 
* clas12mon Detector occupancy plots
 
* Trigger rate GUI
 
* Trigger rate GUI
* FT-Cal FADC scalers
 
  
-->
+
 
 
| valign=top |
 
| valign=top |
  

Revision as of 09:05, 9 November 2021

[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 (757) 575-7540 (cell)
Physics Division Liaison (757) 876-1789 (cell)
Shift Expert (757) 329-4846 (cell)
Remote Shifter (757) 310-7198 (cell)
MCC-OPS 7048
Crew Chief 7045
Crew Chief 9-876-3367 (cell)
Program Deputy 9-876-7997 (cell)
Engineering on-call 757 748-5048 (cell)
Engineering on-call secondary 757 897-9060 (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) Yori 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) Silvia Niccolai
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
Target (757) 822-9586 (cell) Bob Miller Primary
Target secondary (757) 897-9060 (cell) Denny Insley

Paging system in case the on-call
phone is unanswered

PageExpertScreenshot.png

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


CLAS12 Run Group M, Fall 2021
Beam energies: 2.1, 4.0, 6.0 GeV (1.96 GeV/pass)
Important: Document all your work in the logbook!

RC: Stepan Stepanyan

PDL: Valery Kubarovsky




Run Plan: Nov 10 - 12 2021

  • Restore physics quality beam for the production running at 3-pass, start from the tagger dump (see instructions [1])
  • After physics quality beam is established to the Faraday cup dump, proceed with the following:
    • Establish produciton current for LH2 target (limit 80 nA), run DAQ with the produciton trigger Config. PROD66 , trigger rgm_6GeV_inb_v1_0.trg )
    • Trigger Validation Runs with the established conditions:
  1. Random trigger @30 kHz 4 hours with the trigger rgm_6GeV_inb_RNDM_30kHz_v1_0.trg
  2. Trigger without DC roads: 1 hour with the trigger rgm_6GeV_inb_No_Dc_Roads_v1_0.trg
  • Production data taking with rgm_6GeV_inb_v1_0.trg 2 hour runs

Hall Access Items (Wednesday, November 3rd):

DAQ configuration

PROD66 , production trigger rgm_6GeV_inb_v1_0.trg


Shift Worker Notes:

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


Every Run:

Log screenshots of: (this is for the remote shifter)
  • Main beamline GUI overview
  • clas12mon Detector occupancy plots
  • Trigger rate GUI


General Instructions:

  • 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. Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cool down.
  • Do not run more than 30 minutes with >150 W beam to Faraday cup without the beam blocker.
  • Turn DC HV off only for beam tuning; if no beam is available or when the 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
  • 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 the 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.
  • 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 then correct as needed.
  • Fill and submit the shift checklist in the logbook

Every Run:

Log screenshots of: (this is for the remote shifter, see dedicated tab above.)

  • Main beamline GUI overview
  • clas12mon Detector occupancy plots
  • Trigger rate GUI
  • FT-Cal FADC scalers

Overview

Tasks


Shift Worker Backup Table

Worker Shift Backup
Date Day Swing Owl
Fri, Oct 15 John Doe Jane Doe Domenico D'Urso
Sat, Oct 16 Jane Doe Bob Cat Alber Einstein
Backup shifter contact info
Name Email Cell phone
Justin Estee esteejus@mit.edu 517 896 5905
Andrew Denniston awild@mit.edu + 987654321
Sara Ratliff ratliff_sara@gwmail.gwu.edu 774 266 6758
Erin Seroka erinseroka@gwmail.gwu.edu> + 987654321


Clas12design.png