Difference between revisions of "Run Group M"

From clas12-run
Jump to navigation Jump to search
 
(165 intermediate revisions by 2 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://www.jlab.org/Hall-B/run-web/index_rgm.html ESAD, COO, RSAD]===
+
===[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]===
Line 12: Line 12:
 
* See guidance at '''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf BTA 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 |
Line 73: Line 74:
 
''' Beam energies: 2.1, 4.0, 6.0 GeV (1.96 GeV/pass) '''<br>
 
''' Beam energies: 2.1, 4.0, 6.0 GeV (1.96 GeV/pass) '''<br>
  
−
 
+
=== RC: Susan Schadmand ===
−
=== RC: Susan Schadmand (phone below) and Sebastian Kuhn (kuhn@jlab.org, 757-639-6640) ===
+
* (757) 575-7540, [mailto:susansch@jlab.org susansch@jlab.org]
−
* (757) 575-7540
+
* 9 575 7540 from Counting Room 
−
* 9 575 7540 from Counting Room
 
−
* [mailto:susansch@jlab.org susansch@jlab.org]
 
  
 
=== PDL: Valery Kubarovsky ===
 
=== PDL: Valery Kubarovsky ===
Line 84: Line 83:
 
* [mailto:vpk@jlab.org vpk@jlab.org]
 
* [mailto:vpk@jlab.org vpk@jlab.org]
  
−
 
+
== <font color=blue>''' Run Plan: Friday, Feb 7-8, 2022 '''</font> ==  
−
== <font color=blue>''' Run Plan: Jan 26 - Jan 30 2022 '''</font> ==  
 
  
 
Production runs use <b> PROD67_noVTPread </b> and the trigger <b> rgm_6GeV_inb_v1_0.trg </b>.<br/>  
 
Production runs use <b> PROD67_noVTPread </b> and the trigger <b> rgm_6GeV_inb_v1_0.trg </b>.<br/>  
 
Run duration 100M events or 4 hours, whichever comes first.
 
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
  
−
* Presently running on Ar
+
* low luminosity runs:(ca 3pm - 9pm on Feb 7)
−
** beam blocker calibration (during day)
+
** 2 hrs 5nA
−
** run on Ar target (at least until Saturday)
+
** 2 hrs 10 nA
−
** Take at least one run each (4 hours) with 5 nA and 10 nA.
+
** 2 hrs 40 nA
  
−
* switch to C target (for about 2 shifts)
+
* the run on Ca48 until 6am, Feb 8
−
** Check with Bob Miller if we can take data while target is being purged from Ar ->
 
−
** take C data while purging ? Or "empty" target run?
 
  
 +
* 6am Feb 8: Investigate BLA tune beam trips with tune beam to Hall B, https://devweb.acc.jlab.org/CSUEApps/atlis/task/24015
  
−
* Sunday afternoon switch to LH2
+
* RC will be there at 6 am and follow Eugene's instruction
−
** 1 shift LH2
+
** put the blank collimator in
−
** beam blocker calibration
+
** turn HV off for all tracking detectors, just in case if the tagger magnet trips during the test
−
** During Monday owl: 4 hours empty target
+
** MCC may mask upstream halo FSD if necessary but keep all other FSD unmasked
−
 
 
−
* Monday pass change (6GeV beam)
 
−
** OUTLOOK: Run on Ar, Sn and C with 6 GeV beam
 
  
 
== <font color=blue> DAQ configuration </font> ==  
 
== <font color=blue> DAQ configuration </font> ==  
  
 
<b> PROD67_noVTPread </b>, production trigger <b> rgm_6GeV_inb_v1_0.trg </b>. <br/>
 
<b> PROD67_noVTPread </b>, production trigger <b> rgm_6GeV_inb_v1_0.trg </b>. <br/>
 +
 +
<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/>
 +
 +
<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/>
  
 
<b> At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font> </b>'''<br>
 
<b> At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font> </b>'''<br>
Line 121: Line 122:
 
** "configure", "download", "prestart", "go"
 
** "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.
 
* 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.
−
 
  
 
== <font color=blue> References and Standards </font>==
 
== <font color=blue> References and Standards </font>==
Line 141: Line 141:
 
<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]
 
<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]
  
−
<b> Reference Monitoring Histograms (6 nA, production C) </b> [https://logbooks.jlab.org/entry/3973807]
+
<b> Reference Monitoring Histograms:</b>  
−
<b> Old reference Monitoring Histograms (50 nA, production LD2) </b> [https://logbooks.jlab.org/entry/3943458]
+
* [https://logbooks.jlab.org/entry/3982817 6 GeV 80 nA on Ca48]
 +
* [https://logbooks.jlab.org/entry/3980929 6 GeV 90 nA on Sn]
 +
* [https://logbooks.jlab.org/entry/3973807 6 nA, production C]
 +
* [https://logbooks.jlab.org/entry/3943458 50 nA, production LD2]
  
 
<b> Counter rates </b>
 
<b> Counter rates </b>
Line 153: Line 156:
 
= Notes/Known Issues =
 
= Notes/Known Issues =
 
<!--#######################################  Notes/Known Issues  ################################################-->
 
<!--#######################################  Notes/Known Issues  ################################################-->
−
{| {{TableStyle1}}
 
  
−
| valign=top, width=50%|
+
'''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> ==
 
== <font color=blue> Notes </font> ==
  
−
*Note 1: 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:
+
#'''LTCC''' is NOT used in this experiment. HV should be kept OFF.
−
** ON: [https://logbooks.jlab.org/entry/3825712]
+
# '''FMT''' only using 3 FMT layers, not 6.
−
** OFF: [https://logbooks.jlab.org/entry/3825731]
+
# 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:
−
** Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cool down.
+
#* ON: [https://logbooks.jlab.org/entry/3825712]
−
 
+
#* OFF: [https://logbooks.jlab.org/entry/3825731]
−
*Note 2: 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 that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cool down.
−
** The integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up to 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 a bad beam tune or bleed-through from other Halls.
+
# 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
−
*Note 3: When the '''beam is being delivered to the Faraday Cup''':
+
#* Call Engineering on-call
−
*# the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state <font color=red>UNMASKED</font>
+
#* 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  
−
*# No changes to the FSD threshold should be made without RC or beamline expert approval
+
#* Notify Run Coordinator
−
 
+
#* Turn off all detectors
−
*Note 4: Do not run more than 30 minutes with >150 W beam to Faraday cup without the beam blocker.
+
# Observe the guidance of the alarm handler.
−
 
 
−
*Note 5: Any request for a '''special run or change of configuration''' has to be approved by the RC & documented
 
−
 
 
−
*Note 6: Do not turn OFF FTOF HVs, even during the beam tune with CW beam (turn off if tuned/pulsed beam in the upstream beamline)
 
−
*Note 7: 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.
 
−
 
 
−
*Note 10: '''Reset CLAS12MON''' frequently to avoid histogram saturation.
 
−
 
 
−
*Note 11: 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
 
−
 
 
−
*Note 12: '''LTCC is NOT used''' in this experiment. HV should be kept OFF.
 
−
 
 
−
*Note 13: If responding to '''RICH or Trigger alarms''' please post screens also to RICH or HBTRIGGER logbook, respectively.
 
−
 
 
−
 
 
−
<!--
 
−
*Note : 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/]
 
−
-->
 
−
<!--
 
−
* Note : At the end of each run, follow the standard DAQ restart sequence
 
−
"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.
 
−
-->
 
  
  
−
| valign=top |
 
  
 
== <font color=blue> Known Issues </font> ==
 
== <font color=blue> Known Issues </font> ==
  
−
* ECAL HV SEC2_WI_E36 is known to be problematic. Channel stays off for now.
+
* '''Beamline overview''' No Data from Faraday cup viewer camera, network switch died
  
−
* If any weird stripes appear in the DC occupancy plots, call Sergey. This is a known problem.
+
* '''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.
  
−
* In case of loss of communication with IOCBTARG, follow instructions at https://logbooks.jlab.org/entry/3502218
+
* '''PCAL''' transient: mu strip occupancy hole in U view TDC, https://logbooks.jlab.org/entry/3978499, https://logbooks.jlab.org/entry/3978736
−
** 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.
+
* '''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.
  
−
* The error messages " ERR: Event ..." for crates tdcband1, tdcecal1 and tdcecal6 are NOT a problem
+
* '''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
 +
* '''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
  
−
<!-- * With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem.  
+
* '''RICH''' recovery only between runs. also when you see problems like a missing tile
−
* 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
+
* '''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
−
-->
 
−
 
 
−
 
 
−
|}
 
  
 
= Shift Expert =
 
= Shift Expert =
Line 227: Line 200:
 
| valign=top |
 
| valign=top |
  
−
* Follow the [[https://wiki.jlab.org/clas12-run/index.php/Run_Group_M#Short_Term_Schedule Short Term Schedule]] as outlined by RC  
+
'''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 '''[[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
 
** includes Run Plan, DAQ configuration, and References and Standards
−
* 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.
 
* Keep '''shift summary''' up to date in HBLOG. Record all that happens.
−
* Document any beam condition change and send scaler GUIs to HBLOG
+
 
−
* '''Cycle the FMT gas once per shift''', in-between runs.  If it is not reset, the interlock may drop and disable the HV.
+
* '''Cycle the FMT gas once per shift''', in-between runs. Pease log in shift summary.   
−
** 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.
+
** If it is not reset, the interlock may drop and disable the HV.
−
* Do a '''RICH recovery''' (press the RICH Recovery button on the GUI) once daily during the day shift between runs.
+
** Turning off and on the  gas flow without pausing to avoid HV trips.  
−
* [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side then correct as needed.
+
** 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.
 +
 
 +
* '''[https://bta.acc.jlab.org 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'''
 
'''In case of other questions or uncertainties of what to do, call the RC or PDL'''
Line 242: Line 231:
  
 
|}
 
|}
−
 
−
<!--#######################################  REMOTE SHIFTS  ##############################################-->
 
−
<!--#######################################  REMOTE SHIFTS  ##############################################-->
 
−
<!--#######################################  REMOTE SHIFTS  ##############################################-->
 
  
 
= Remote Worker Shift =
 
= Remote Worker Shift =
Line 270: Line 255:
  
 
* WITH BEAM, log screen shots of  
 
* WITH BEAM, log screen shots of  
−
** Beamline Overview
+
** Beamline Overview, in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser]
−
*** In VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser]
 
 
** CLAS12 Trigger rates and DAQ status
 
** CLAS12 Trigger rates and DAQ status
  
−
* Data Quality Monitoring
+
* upload monitoring plots (mon12) to logook
−
** reset & check spectra frequently
+
** '''look at the spectra''': Reference, current, and 5 most recent runs, choose a reference run (the reference numbers refer to logbook entries):
−
** upload monitoring plots (mon12)  
+
*** 6 GeV 80 nA on Ca48 [https://clas12mon.jlab.org/mon12/histograms/?reference=3982817 https://clas12mon.jlab.org/mon12/histograms/?reference=3982817]
−
** Reference, current, and 5 most recent runs, choose a reference run, here are some choices (the reference numbers refer to logbook entries):
+
*** 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 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]
 
*** ref 50 nA, production LD2, [https://clas12mon.jlab.org/mon12/histograms/?reference=3943458 https://clas12mon.jlab.org/mon12/histograms/?reference=3943458]
−
 
  
 
'''Every Shift:'''
 
'''Every Shift:'''
Line 286: Line 269:
 
* Fill the [https://logbooks.jlab.org/checklists/151 shift checklist]
 
* Fill the [https://logbooks.jlab.org/checklists/151 shift checklist]
  
−
* log screen shots of RICH temperature and scaler maps
+
* Log screen shots of RICH temperature and scaler maps. Log in HBLOG and RICH logbook.
 +
 
 +
'''Regularly''':
 +
 
 +
* <font color=red>'''reset & check spectra frequently (every 30 - 60 minutes)'''</font>
 +
** 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'''
  
−
* Strip charts
+
* 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 or 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]
+
** 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
  
−
* Alarms
+
* 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]
−
** If responding to RICH or Trigger alarms please post screens also to RICH or HBTRIGGER logbook, respectively
 
  
  
Line 417: Line 408:
 
** Meeting ID: 161 269 7153
 
** Meeting ID: 161 269 7153
 
** Passcode: 474207
 
** Passcode: 474207
−
** On site - CEBAF Center F324-325 conference room
 
 
** Daily Analysis Meeting to follow directly after
 
** Daily Analysis Meeting to follow directly after
 
** [[RGM_RC_Meetings | Meeting Agendas]]
 
** [[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"