Run Group F

[edit]

• Shift Documentation
• Phone Numbers
• Short Term Schedule
• Monitoring
• Useful Links

Shift Schedule Shift Checklist Hot Checkout Beam Time Accounting See guidance for BTA in Beam Time Accounting User Guide.

Manuals Target BONuS12-RTPC BAND Beamline CND CTOF DAQ DC ECAL FT FTOF HTCC LTCC MVT MVT turn on procedure RICH: expert novice Slow Controls Solenoid Power-Up and Power-Down Procedure SVTTo switch on SVT see SVT short Torus Power-Up and Power-Down Procedure

Procedures Establishing Physics-Quality Beam Performing Møller Runs Performing Harp Scans Tunnel/Hall Access

JLab Logbooks MCC Hall-A Hall-B Hall-C Hall-D

RC schedule Weekly form Feb 12 - Feb 18: Mohammad Hattawy Feb 19 - Feb 25: Florian Hauenstein Feb 26 - Mar 3: Eric Christy Mar 4 - Mar 17: Sebastian Kuhn Mar 18 - Mar 24: Mohammad Hattawy Mar 25 - Mar 31: Raphael Dupre Apr 1 - Apr 7 : Narbe Kalantarians Apr 8 - Apr 14: Carlos Ayerbe Apr 15 - Apr 21: Mohammad Hattawy Apr 22 - May 6 : Stephen Bultmann

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]

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 this page to force a refresh.

CLAS12 Run Group F, Spring 2020
Beam energy 10.38 GeV (5 pass)
Important: Document all your work in the logbook!

RC: Florian Hauenstein (Full list of RG-F RCs)

• 757-575-7540
• 9 757-575-7540 from Counting Room

PDL: Stepan Stepanyan

• (757) 876-1789
• 9 876-1789 from Counting Room

Run Plan, 2020 (Last updated: Feb 24th, 2020 @ 11:00 ) Requests Overall Program: Establish beam on FC, 2H01 harp scan; re-establish orbit with locks Take production data on full H2 target (see below) until 22:00, then empty target (done by RTPC expert, 1 purge) Take data with "empty" H2 target: 1 run for about 2 hours Around 1a.m. Tuesday->Wednesday, call Eugene and ask for the torus and solenoid to be ramped down. Take data (trigger file rgf_elec_2secrs_ftof_ctof_zero_field.trg) with low current 5nA! on empty H2 target and both solenoid and torus OFF. trigger deadtime should be around or below 10%. If FMT trips repeatedly, inform Yuri. Beam will likely be taken away around 7-8 on Wednesday for Accelerator/Engineering Stand Down (9 - 12). Afterwards, reestablish normal running conditions (including trigger file rgf_inbending_v3_2, full H2 target, 240 nA beam) and take enough data so we have at least 50 M events on H2 (including the Tuesday ones). Then switch back to standard D2 production running. Further down the line: EC only trigger run, lumi scan, about 10 days of outbending torus Production: Electron-inbending Configuration, D2/H2/4He target @ 10.4 GeV beam DAQ config:PROD66; Trigger file:rgf_inbending_v3_2.trg Put beam blocker in in front of Faraday Cup Ask MCC for 240 nA beam current (NOTE that 2C21A BPM will show 260nA. This is a known issue.) Start a run and check that live time is above 85%. If not decrease current and log it. Restart a new run every 2h During the run (at least every 2h) submit screenshots for the DAQvnc, Trigger GUI, Beamline overview, beam strip charts, RTPC overview from clascss. Run clas12mon over 100000 events and submit the occupancy plots. Make sure to reset monitoring plots regularly. Screenshot for DAQ/Trigger GUIs to logbook when beam is only ON. NEW: To do for FMT: Regularly post the FMT current strip-charts (available on the expert computer) Once per shift post the FMT HV control overview screen when the beam is OFF . Access it via CVT -> FMT overview to get the overview screen. Then click on the grey button next to "High Voltage" and choose ``Channel controls" in the opening menu If FMT trips let Yuri Gotra know. NEW: For trigger alarms check Note 14 first! Beam Restauration (last updated Feb 19) Updated Manual is at [1] IF YOU GO DIRECTLY TO FARADAY CUP!!!: Quick beam recovery procedure including Harp Scan All HV are off (including FTOF) Check that 20 mm collimator is in Call MCC to unmask U/M/D counters but keep BOM masked or get it masked in case it isn't Call MCC to put 5nA to the FC. Compare the 2c21, 2c24, 2H01 positions and beam overview screen to the reference below Put thresholds on U/M/D as 1M/1M/1M and dwell time 50 ms. follow the procedures for the harp scans at 2H01 [2] (optionally at 2C21 and 2C24) Compare the results with the references scans below (be aware to use the correct analysis counter) if what you get is similar to the references, call MCC and tell them the the beam is acceptable and set FSD thresholds and dwelltimes as written below and continue with production running (see above) if what you get isn't similar to the references, do the other harp scans. If you are not sure if a tune of the beam is needed, consult beam line expert and/or RC. At the end of each run, follow the standard DAQ restart sequence (Note, this might be different from the instructions coming up on RunControl.) "end run", "cancel", "reset" 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" References and Standards: (last update Feb 18, 2020 @ 19:00 PM.) Restoration of Beam to Hall B Default solenoid current and B field 1933 A (~4.06 T) Nominal Beam Positions 2H01, X: -0.6 mm, Y: -0.6 mm 2C24, X: +0.1 mm, Y: -0.4 mm 2C21, X: +0.1 mm, Y: 0.0 mm the acceptable trajectory for the beam before entering the hall must be established while on the tagger dump. The relation between the 2C24 BPM positrons and the X,Y values measured with the tagger harp are: X_harp=36.68-X_2C24 Y_harp=20.97-Y_2C24 FSD Thresholds Upstream: 2000 Hz Midstream: 2000 Hz Downstream: 500000 Hz BOM: 100000 FSD Dwell time Upstream: 5 ms Midstream: 5 ms Downstream: 5 ms BOM: 5 ms BONuS HV setting https://logbooks.jlab.org/entry/3784096 Reference Harp Scans for Beam on Tagger Dump: 2C21 [3], 2C24 [4] Reference Harp Scans for Beam on Faraday Cup: 2H01 [5], [6], 2C21 [7], 2C24 [8] Reference Monitoring Histograms 5 nA production trigger [9] Reference Scalers and Halo-Counter Rates: Well-tuned CW beam on FC, Full LD2 and 4He target, CLAS12 ON: 5 nA [10], 50 nA [11], 240nA [12] Well-tuned CW beam on FC, Empty Target, CLAS12 OFF: 5 nA [13] Well-tuned beam during Moller run [14] Well-tuned beam on Tagger Dump at 5 nA during harp scans: [15]

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 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. Get familiar with the shift crew responsibilities for the RTPC (see manual [16]). Especially on how to switch on the HV after a trip. Do not run more than 30 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. Once Per Day (At 13:00): Call RTPC expert to purge the target and fill it with the appropriate target gas. Complete RICH recovery procedure - see Note: 11 below 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. 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. Upload spectra from clas12mon at begin and end of shift and cross-check with reference spectra Reset clas12mon every ~2 hours and inspect spectra Fill and submit the shift checklist in the logbook Every Run: Log screenshots of: main scaler GUI display Trigger rate gui Beam strip charts 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. Same holds for FT.

• Note 1: 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 2: 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 3: 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 4: Any request for a special run or change of configuration has to be approved by the RC & documented

• Note 5: 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 6: Reset CLAS12MON frequently to avoid histogram saturation. If CLAS12MON is restarted change MAX scale to 10 (default is 5) for DC normalized occupncy histograms. This would prevent them from saturation. See log entry [17]

• Note 7: Shift workers must check the occupancies! Use this tool to compare to previous runs: [18]

• Note 8: Check the vacuum periodically, make sure vacuum is not higher than 5e-5

• Note 9: 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 10: 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 11:

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 12: Ignore
• Note 13: If ROC mmft1 is 100% busy: power cycle FTT LV (FT->FTT Overview, HV stays ON), roc_reboot mmft1, wait until it reboots (ssh mmft1 to verify). If the first LV recycle/mmft1 reboot doesn’t work call FT expert

• Note 14: Trigger Troubleshooting: If you get trigger alarms check first if the trigger bit of a sector alarms both, for the DC roads and non DC roads, in the trigger expert screen (DAQ --> CLAS1 Trigger --> Menu --> Table - Expert). If this is the case (i.e. sector 3 and bits 3 and 10), there might be a problem with HTCC, PCAL or ECAL rocs and you should check the rocs in the runcontrol. If the non DC trigger bit is working and only the one with DC alarms, you would need to check the DC trigger rocs (possibly the one from the alarming sector). If you are not sure, call RC or trigger expert.

Webcams Faraday Cup Beam Viewer Tagger Beam Dump Viewer Hall Fisheye Saclay Cryotarget

Manuals CED Manual MON12 Manual off-line Manual

Epics on the web Hall B WebOPI (CUE Login) Accelerator (CUE Login)

Fall 2018 Run

Spring 2018 Run

Hall-B Operation Safety Procedures RCDB Run lists

Accelerator Accelerator Whiteboard Program Deputy Shift Plans Run Coordinator Reports Accelerator daily meetings notes (by Mauri)

Bluejeans meetings Daily Run meetings 10:00 a.m. Upstairs Counting House / Bluejeans 757 683 5804