Difference between revisions of "Run Group M"

From clas12-run
Jump to navigation Jump to search
Line 89: Line 89:
 
<br>
 
<br>
  
<!--
+
 
 
* '''Note 1: Be very mindful of the background rates in the halo counters, rates in the detectors, and currents in the SVT for all settings to ensure that they are at safe levels.'''
 
* '''Note 1: Be very mindful of the background rates in the halo counters, rates in the detectors, and currents in the SVT for all settings to ensure that they are at safe levels.'''
 
The integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and the rates on the midstream counters have to be in the range 10-20 Hz (acceptable up to 50 Hz) @50 nA. Counting rates in the range of hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.
 
The integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and the rates on the midstream counters have to be in the range 10-20 Hz (acceptable up to 50 Hz) @50 nA. Counting rates in the range of hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.
 
+
<!--
 
* ''' Note 2: At the end of each run, follow the standard DAQ restart sequence '''
 
* ''' Note 2: At the end of each run, follow the standard DAQ restart sequence '''
 
"end run", "cancel", "reset", then if the run ended correctly, "download", "prestart", "iocjscalerRestartAll.sh", "go". If the run did not end correctly or if any ROCs had to be rebooted, "configure", "download", "prestart", "iocjscalerRestartAll.sh", "go".
 
"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.
 
After each step, make sure it is complete in the Run Control message window. If a ROC has crashed, find which one it is and issue a roc_reboot command and try again. Contact the DAQ expert if there are any questions.
 +
-->
 +
* '''Note 2: Nominal beam positions:''' ''' 2C24A (X=xx mm, Y=yy mm) ''', '''2H01 (X=xx mm, Y=yy mm)'''
  
* '''Note 3: Nominal beam positions:''' ''' 2C24A (X=0.5 mm, Y=0.5 mm) ''', '''2H01 (X=.6 mm, Y=.2 mm)'''
+
* '''Note 3: 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 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)'''
 
  
* '''Note 5: In case of a Torus and/or Solenoid Fast Dump do the following:
+
* ''' Note 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
 
*# Notify MCC to request beam OFF and to drop Hall B status to Power Permit
 
*# Call Engineering on-call
 
*# Call Engineering on-call
Line 109: Line 109:
 
*# Turn off all detectors'''
 
*# Turn off all detectors'''
  
*'''Note 6: When beam is being delivered to the Faraday Cup:'''
+
*'''Note 5: When the beam is being delivered to the Faraday Cup:'''
 
*# the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state <font color=red>UNMASKED</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
 
*# 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''
 +
-->
 +
*'''Note 6: Any request for a special run or change of configuration has to be approved by the RC & documented'''
  
*'''Note 7: Do not turn on the SVT or MM - only the SVT or MM expert can do that'''
+
*'''Note 7: * [https://bta.acc.jlab.org Fill out BTA] hourly. Click "Load from EPICS" to automatically fill the left side then correct as needed.'''
 
 
*'''Note 8: Any request for a special run or change of configuration has to be approved by the RC & documented'''
 
 
 
*'''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.'''
 
 
 
*'''Note 10: Reset CLAS12MON frequently to avoid histogram saturation.'''
 
  
 +
*'''Note 8: Reset CLAS12MON frequently to avoid histogram saturation.'''
 +
<!--
 
*'''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/]'''
 
*'''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/]'''
  
Line 199: Line 199:
 
* 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
 
* 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 then correct as needed.
 
 
* Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
 
* Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
  

Revision as of 10:17, 9 November 2021

[edit]


Clas12design.png