Difference between revisions of "Run Group B"

From clas12-run
Jump to: navigation, search
(Short Term Schedule)
(Short Term Schedule)
Line 178: Line 178:
 
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 4: FTOF HVs: The goal is to minimize the number of power cycles of the dividers.
+
* '''Note 3: FTOF HVs: The goal is to minimize the number of power cycles of the dividers.
 
** should be turned off during the initial beam tuning down to the Faraday Cup after CLAS12 has been off for a long shutdown, when doing a Moller run, when doing harp scans, or if there is tuned/pulsed beam in the upstream beamline.'''
 
** should be turned off during the initial beam tuning down to the Faraday Cup after CLAS12 has been off for a long shutdown, when doing a Moller run, when doing harp scans, or if there is tuned/pulsed beam in the upstream beamline.'''
 
** should be left on after an initial beam tune has been established and if there are only minor steering adjustments and “tweaks” being made.
 
** should be left on after an initial beam tune has been established and if there are only minor steering adjustments and “tweaks” being made.
 
** if shift workers have doubts what to do with the HVs, they can always contact the TOF on-call expert for advice.
 
** if shift workers have doubts what to do with the HVs, they can always contact the TOF on-call expert for advice.
  
* '''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 190: Line 190:
 
*# Turn off all detectors'''
 
*# Turn off all detectors'''
  
*'''Note 6: When beam is being delivered to the Faraday Cup:'''
+
*'''Note 5: When 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 7: Any request for a special run or change of configuration has to be approved by the RC & documented'''
+
*'''Note 6: Any request for a special run or change of configuration has to be approved by the RC & documented'''
  
*'''Note 8: 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 7: 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 9: Reset CLAS12MON frequently to avoid histogram saturation.'''
+
*'''Note 8: Reset CLAS12MON frequently to avoid histogram saturation.'''
  
*'''Note 10: Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/?reference=3650729]'''
+
*'''Note 9: Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/?reference=3650729]'''
 
<!--[https://clas12mon.jlab.org/mon12/histograms/?reference=3621580]'''-->
 
<!--[https://clas12mon.jlab.org/mon12/histograms/?reference=3621580]'''-->
  
*'''Note 11 Do not Turn OFF MVT HV: Instead go to 'Restore settings' from the MVT overview screen:
+
*'''Note 10 Do not Turn OFF MVT HV: Instead go to 'Restore settings' from the MVT overview screen:
 
*# SafeMode.snp for beam tuning and Moeller runs
 
*# SafeMode.snp for beam tuning and Moeller runs
 
*# MV_HV_FullField.snp for full solenoid field
 
*# MV_HV_FullField.snp for full solenoid field
 
*# MV_HV_MidField.snp wgeb solenoid < 4T
 
*# MV_HV_MidField.snp wgeb solenoid < 4T
 
'''
 
'''
*'''NOTE 12 Check the vacuum periodically, make sure vacuum id not higher than 5e-5 '''
+
*'''NOTE 11 Check the vacuum periodically, make sure vacuum id not higher than 5e-5 '''
  
*''' NOTE 13 Always reset the CFD threshold after all power off/on on the CND CAMAC crate'''  
+
*''' NOTE 12 Always reset the CFD threshold after all power off/on on the CND CAMAC crate'''  
 
After the CAMAC crate (camac1) holding the CND CFD boards is switched off for any reason, it is mandatory to reset the associated thresholds typing the
 
After the CAMAC crate (camac1) holding the CND CFD boards is switched off for any reason, it is mandatory to reset the associated thresholds typing the
 
following command from any clon machine terminal: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0
 
following command from any clon machine terminal: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0
Line 217: Line 216:
 
If this command is failing and the crate is not responding, reboot it as follows: roc_reboot camac1
 
If this command is failing and the crate is not responding, reboot it as follows: roc_reboot camac1
  
*'''NOTE 14 ''' Shift workers should anyway check routinely scalers to verify they update correctly and make a logbook entry if anomalies are observed after starting a new run.
+
*'''NOTE 13 ''' Shift workers should anyway check routinely scalers to verify they update correctly and make a logbook entry if anomalies are observed after starting a new run.
  
*'''NOTE 15: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766'''
+
*'''NOTE 14: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766'''
  
*'''NOTE 16: After any reboot of crate 'adcband1', reboot tdcband1 crate''' to avoid sync problems of TDCs.'''
+
*'''NOTE 15: After any reboot of crate 'adcband1', reboot tdcband1 crate''' to avoid sync problems of TDCs.'''
  
*'''NOTE 17:''' 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. <u>Please, note </u> that missing tiles typically occur due to lost communication. Keep in mind that the recovery procedure will kill DAQ. If DAQ is running for other purpose, rather than data taking (for which the RICH acceptance would be important) do not initiate the recovery procedure.  
+
*'''NOTE 16:''' 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. <u>Please, note </u> that missing tiles typically occur due to lost communication. Keep in mind that the recovery procedure will kill DAQ. If DAQ is running for other purpose, rather than data taking (for which the RICH acceptance would be important) do not initiate the recovery procedure.  
 
** The most critical parameter for RICH is the temperature of the photosensors. If the temperature rises above limits, an interlock will automatically turn the RICH HV and LV. If this happens, notify the expert on call and keep taking data without RICH.
 
** The most critical parameter for RICH is the temperature of the photosensors. If the temperature rises above limits, an interlock will automatically turn the RICH HV and LV. If this happens, notify the expert on call and keep taking data without RICH.
  
*'''NOTE 18:''' Asymmetry on FTCal ADC Scalers: If the beam current is 5 - 10 nA, and the observed asymmetry is out of specs, i.e. > +-2.5%, check (1) that the beam position is according to specs, (2) the response of the rest of CLAS (compare the scalers of FTOF, CTOF, ECAL, etc. from the Scalers GUI to the reference for that current, as posted above). If positions and other detectors do not show any anomalies, keep running. The ADC scalers require at least ~15 nA for a reliable response.
+
*'''NOTE 17:''' Asymmetry on FTCal ADC Scalers: If the beam current is 5 - 10 nA, and the observed asymmetry is out of specs, i.e. > +-2.5%, check (1) that the beam position is according to specs, (2) the response of the rest of CLAS (compare the scalers of FTOF, CTOF, ECAL, etc. from the Scalers GUI to the reference for that current, as posted above). If positions and other detectors do not show any anomalies, keep running. The ADC scalers require at least ~15 nA for a reliable response.
  
 
= Monitoring =
 
= Monitoring =

Revision as of 17:58, 13 February 2019

[edit]

Shift Schedule

Shift Checklist

Hot Checkout

Beam Time Accounting

Manuals

Procedures

JLab Logbooks

RC schedule

  • Jan 26 - Feb 6: S. Niccolai
  • Feb 6 - Feb 13: Y. Ilieva
  • Feb 13 - Feb 20: S. Stepanyan
  • Feb 20 - Feb 27: F. Hauenstein
  • Feb 27 - Mar 6: S. Niccolai
  • Mar 6 to Mar 12: J. Gilfoyle
  • Mar 12 to Mar 19: V. Kubarowsky

Person Phone Number
Run Coordinator 9-757 575-7540 (cell)
Physics Division Liaison 9-757 876-1789 (cell)
Shift Expert 5244 or 9-757 329-4846 (cell)
Shift Worker 5126
MCC-OPS 7048
Crew Chief 7045
Crew Chief 9-757 876-3367 (cell)
Program Deputy 9-757 876-7997 (cell)
Engineering on-call 9-757 748-5048 (cell)
Engineering on-call secondary 9-757 897-9060 (cell)
Radcon (needed for target cell swaps) 9-757 876-1743 (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) Yuri 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) Jose Carvajal
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
Pol. Target On-Call (850) 443 6517 (cell) Zulkaida Akbar
Polarized Target (757) 746-9277 (cell) Chris Keith
Polarized Target (757) 897-1415 (cell) James Maxwell
Polarized Target (757) 871-5374 (cell) James Brock
Target (not used) (757) 822-9586 (cell) Bob Miller Primary
Target (not used) (757) 897-9060 (cell) Denny Insley Secondary
Counting House C x6000
Counting House D x5504

In case of a problem with superconducting magnets call Engineering on-call first, particularly if it is related to cryo.
For all other superconducting magnet problems call magnet group.
Their schedule and phone numbers are posted on the wall next to the Saclay target computer.




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


CLAS12 Run Group B, spring 2019
Beam energy 10.6 GeV (5 pass)
Important: Document all your work in the logbook!
Remember to fill in the run list at the beginning and end of each run (clas12run@gmail.com can fill the run list)

RC: Stepan Stepanyan

PDL: Maurizio Ungaro


Run Plan: Feb. 13-14

Production-run DAQ configuration PROD66, trigger file rgb_v3.trg.

After random trigger run, take 2-hrs long runs with PROD66 and rgb_v3.trg .

References and Standards:

(last update 2/10/2019- 12:00 PM)

Restoration of Beam to Hall B

Nominal Beam Positions

  • 2H01, X: +3.0 mm, Y: -1.0 mm
  • 2C24, X: +0.16 mm, Y: 0.26 mm

FSD Thresholds

  • Upstream: 2000 Hz
  • Midstream: 2000 Hz
  • Downstream: 500000 Hz
  • BOM: 35000

Reference Harp Scans for Beam on Tagger Dump: 2C21 [1], 2C24 [2]

Reference Harp Scans for Beam on Faraday Cup: 2C21 [3], 2C24 [4], 2H01 [5]

Reference Monitoring Histograms (20 nA, production trigger) [6]

Reference Monitoring Histograms (35 nA, production trigger) [7]

Reference Scalers and Halo-Counter Rates:

  • Well-tuned CW beam on FC, Full LD2 target, CLAS12 ON: 5 nA [8], 10 nA [9], 20 nA [10], 30 nA [11], 40 nA [12], 50 nA [13], 60 nA [14], 75 nA [15]
  • Well-tuned CW beam on FC, Empty Target, CLAS12 OFF: 5 nA [16]
  • Well-tuned beam during Moller run [17]
  • Well-tuned beam on Tagger Dump at 5 nA during harp scans: [18]

SVT acceptable currents: <10 nA (typically < 1 nA) with no beam and no HV; ~< 400 nA (HV ON, no beam); 10 nA [19], 20 nA [20], 30 nA [21], 40 nA [22], 50 nA [23], 60 nA [24], 75 nA [25]


General Instructions:

  • For a given beam current, compute the FSD thresholds according to the Establish Physics Quality Beam document. Call MCC to update the values. Contact the beamline expert if there are questions about setting the FSD thresholds.
  • 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.
  • Check for and read any comments to log-book entries made during your shift.

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
  • Fill out BTA hourly. Click "Load from EPICS" to automatically fill the left side.
  • Fill and submit the shift checklist in the logbook
  • Monitor the SVT Slow Controls status, post plot of current stability in the HBSVT elog once per shift.
  • As of 9th of February, once per shift stop and start the gas flow of the FTT (see logbook entry [26] for more details. Check the FTT HV after the procedure. If it is Off, check the status of all gas interlocks, reset the one that is at "Fault" and turn the FTT HV back ON.

Every Run:

  • Log screenshots of:
    • main scaler GUI display (both at the begining and at the end of run)
    • Detector occupancy plots from clas12mon
    • Trigger rate gui
    • Beam strip charts
  • Fill out the run info in run list at the beginning and at the end of each run.
  • Compare the monitoring histograms from clas12mon to the reference and troubleshoot as needed. When checking the ECAL response, make sure to look at the histograms for each sector by using the sector buttons at the bottom of the clas12mon window - if adcecal* or/and adcpcal* ROC crashes, there will be no alarm and the histograms are the way to notice this issue.


  • 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.

  • 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", "go". If the run did not end correctly or if any ROCs had to be rebooted, "configure", "download", "prestart", "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.

  • Note 3: FTOF HVs: The goal is to minimize the number of power cycles of the dividers.
    • should be turned off during the initial beam tuning down to the Faraday Cup after CLAS12 has been off for a long shutdown, when doing a Moller run, when doing harp scans, or if there is tuned/pulsed beam in the upstream beamline.
    • should be left on after an initial beam tune has been established and if there are only minor steering adjustments and “tweaks” being made.
    • if shift workers have doubts what to do with the HVs, they can always contact the TOF on-call expert for advice.
  • Note 4: In case of a Torus and/or Solenoid Fast Dump do the following:
    1. Notify MCC to request beam OFF and to drop Hall B status to Power Permit
    2. Call Engineering on-call
    3. 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
    4. Notify Run Coordinator
    5. Turn off all detectors
  • Note 5: When beam is being delivered to the Faraday Cup:
    1. the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state UNMASKED
    2. No changes to the FSD threshold should be made without RC or beamline expert approval
  • Note 6: Any request for a special run or change of configuration has to be approved by the RC & documented
  • Note 7: Carefully check the BTA every hour and run the script btaGet.py to print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.
  • Note 8: Reset CLAS12MON frequently to avoid histogram saturation.
  • Note 9: Shift workers must check the occupancies! Use this tool to compare to previous runs: [27]
  • Note 10 Do not Turn OFF MVT HV: Instead go to 'Restore settings' from the MVT overview screen:
    1. SafeMode.snp for beam tuning and Moeller runs
    2. MV_HV_FullField.snp for full solenoid field
    3. MV_HV_MidField.snp wgeb solenoid < 4T

  • NOTE 11 Check the vacuum periodically, make sure vacuum id not higher than 5e-5
  • NOTE 12 Always reset the CFD threshold after all power off/on on the CND CAMAC crate

After the CAMAC crate (camac1) holding the CND CFD boards is switched off for any reason, it is mandatory to reset the associated thresholds typing the following command from any clon machine terminal: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0

If this command is failing and the crate is not responding, reboot it as follows: roc_reboot camac1

  • NOTE 13 Shift workers should anyway check routinely scalers to verify they update correctly and make a logbook entry if anomalies are observed after starting a new run.
  • NOTE 15: After any reboot of crate 'adcband1', reboot tdcband1 crate to avoid sync problems of TDCs.
  • NOTE 16: 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. Please, note that missing tiles typically occur due to lost communication. Keep in mind that the recovery procedure will kill DAQ. If DAQ is running for other purpose, rather than data taking (for which the RICH acceptance would be important) do not initiate the recovery procedure.
    • The most critical parameter for RICH is the temperature of the photosensors. If the temperature rises above limits, an interlock will automatically turn the RICH HV and LV. If this happens, notify the expert on call and keep taking data without RICH.
  • NOTE 17: Asymmetry on FTCal ADC Scalers: If the beam current is 5 - 10 nA, and the observed asymmetry is out of specs, i.e. > +-2.5%, check (1) that the beam position is according to specs, (2) the response of the rest of CLAS (compare the scalers of FTOF, CTOF, ECAL, etc. from the Scalers GUI to the reference for that current, as posted above). If positions and other detectors do not show any anomalies, keep running. The ADC scalers require at least ~15 nA for a reliable response.


Clas12design.png