Run Group L

[edit]

• General
• Phone Numbers
• Short Term Schedule
• General Information
• Recent Issues
• Shift Expert
• Shift Worker
• ALERT Expert
• Run Coordinator
• Monitoring
• Important Links

General Logbook Shift Schedule Run Coordinator/ALERT Expert Schedule Shift Checklist Beam Time Accounting Beam Time Accounting User Guide. Hot Checkout ESAD, COO, RSAD, ERG

Manuals Systems Beamline Torus Solenoid DAQ Slow Controls Software CED MON12 Detectors ALERT: AHDC and ATOF AHDC Gas System Target Gas System Gas System Drawings DC FTOF ECAL LTCC HTCC RICH: Expert Shift CTOF CND FT BAND

Procedures Beam Restoration Step-By-Step Playbook Establishing Physics-Quality Beam (2021) Performing Møller Runs Performing Harp Scans Accessing the Tunnel/Hall Logbooks MCC Hall-A Hall-B Hall-C Hall-D Studies Analysis of DC Occupancy and FT Dose for ALERT CTOF/CND Calibration Plans for ALERT

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) 630-7050 (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 (757) 897-9060 Engineering On-Call (primary) Denny Insley (secondary) Slow Controls (757) 748-6922 Nathan Baltzell Beamline (757) 303-3996 Eugene Pasyuk DC (757) 218-4372 (757) 748-5048 Florian Hauenstein (primary) Engineering On-Call (secondary) SVT/MVT/MM (757) 541-7539 (757) 753-7769 Yuri Gotra (primary) Rafo Paremuzyan (secondary) ECAL (757) 810-1489 Cole Smith FTOF/CTOF/CND (757) 344-7204 Daniel Carman ALERT (757) 329-4844 Felix Touchte Codjo HTCC/LTCC (757) 344-7174 Youri Sharabian FT (757) 344-1848 Raffaella De Vita BAND (757) 310-7198 Florian Hauenstein RICH (757) 344-3235 (757) 748-6922 Christopher Dilks (primary) Nathan Baltzell (secondary) DAQ (757) 232-6221 Sergey Boiarinov HYDRA (317) 550-9226 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 to Edit solely this tab. P.S.: You must click on the top Edit, next to Read, followed by "Save changes" to force the current page to refresh.

Run Coordinator (RC): Lamiaa El Fassi (757) 575-7540

PDL: Daniel Carman (757) 876-1789

Important Reminders

• If any issue takes more than 15-20 min to solve, call an expert!
  • If you are unsure of who is the expert, check this wiki. If you still can't find it, check the ESAD.
• Check the monitoring plots and hydra frequently so we can spot issues early!
• When longer beam down time is predicted (~30 min up), call the Target Expert (Felix) to purge the target (once per shift).
• Switch off the AHDC HV when beam is down for 30 minutes or longer.
• Do NOT under ANY circumstances change FSD settings or beam halo thresholds without approval from RC or beamline expert!

General Notes

DAQ config: PROD67

Trigger file: rgl_inb_v4.2_200MeV.trg for 325 nA runs

See General Information's Nominal Beam Positions

Commissioning Run List

• Worker: Upload the screenshots (See shift workers tab.) when beam on. Make sure that all the trigger bits from 0 to 31 are in the CLAS12 Trigger window when submitting the screenshot. Restart the clas12online at the beginning of the shift, by "./bin/start_hipo_et.sh" and "./bin/run-jshell runOnine.java".

• Raffaella checked the mon12 version in the counting house and it should be fine. If there's an issue with submitting the histograms to the server, let the RC know so that we can communicate with Raffaella and Nathan about that.

• Expert: Please remember to Configure and download for every run.

Short Term Run Plan

Updated: 5/15 @ 6:50 a.m.
PLEASE REFRESH THE BROWSER TO SEE LATEST UPDATES!

• Wed 5/15 OWL - Thu 5/15 DAY
  • Execute the General Information's Full Beam Restoration Procedure once beam is back (No Moller this week)
  • When good quality beam is established, run production on He-4 @325nA. 100M event per run.
  • Target Expert or RC should purge target once very 24 hours

• Thu 5/15 SWING - Wed 5/21 OWL:
  • Keep running production on He-4 @ 325nA. 100M event per run.
  • Perform Hall A bleed-through test (~5 minutes, post scalers to logbook) if Hall A is running stably at 20uA.
    1. Ask MCC to switch off the Hall B laser but keep the slit open.
    2. Take screenshots of the scaler displays (beamline/FTCal/ATOF/AHDC) while Hall A is receiving stable beam and post to the logbook.
    3. Take screenshots of beam strip chart showing BOM rate and Hall A current and post to the logbook.
  • Target Expert or RC should purge target once every 24 hours

• Wed 5/22 SWING - Wed 5/28 OWL:
  • Execute the General Information's Full Beam Restoration Procedure INCLUDING Moller measurements (previous run was on Fri 5/9)
  • When good quality beam is established, run production on TARGET TBD @325nA. 100M event per run.
  • Target Expert or RC should purge target once every 24 hours

This tab contains information on

• Important Shift takers instructions
• DAQ Operation
• Reference Values
  • FSD Threshold Settings
  • Nominal Beam Positions
  • Latest Harp Scan References
• Beam Restoration and Møller
  • Restoring Beam after Short Downtime
  • Full Beam Restoration
    • STEP 1: Beam Tuning to Tagger Yoke Dump
    • STEP 1b (optional): Møller Measurements
    • STEP 2: Beam Tuning to Faraday Cup
    • STEP 3: Prepare for Physics Running

Important Shift takers instructions

Do NOT change FSD settings without approval from RC or beamline expert!

In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House and inform the Crew Chief and RC.

In case of evacuation of the Counting Room (e.g., due to a fire alarm), grab the shift expert phone and leave the room through the "EXIT" door leading to the parking lot. Do not leave through the hallway! Call the RC once outside so the latter will call MCC to turn the beam OFF to Hall B and inform other Hall B staff members.

Remote shift: If needed, worker shifts can be taken from off-site. Inform the PDL and RC. Also, make sure that you follow the instructions under the "Shift Worker" tab, as you need some lead time to set up!

Note to Shift Takers:

• Read the ESAD, COO, RSAD, and ERG documents found on the "Current RG-L Run Info" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.
• There is a new detector for this run: ALERT. Read the manual before your first shift.
• Read at least the previous 24 hours logbook entries to be aware of recent run details and changes
• Arrive at least 10 minutes early for shift change
  • If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.

• Refresh the run wiki page/tabs; look over it/them every shift
• Follow the Shift Expert/Worker tab's instructions
• Do not spend more than 15-20 min trying to fix a problem. In case of any issue, contact the On-call Experts or the RC.
• Refer to the Beam Restoration and Møller for beam restoration procedures and Møller runs.

General Overview

Beam Information

• Orbit locks are on BPMs 2C24A and 2H01 and the locks should generally be on "RUNNING" in the top left of the beamline overview GUI.
  • Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the Nominal Beam Positions.
  • The beam position at 2C21A is part of the orbit lock but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.
  • The beam position at 2C21A is important for initial beam tuning (on tagger dump).

• If the half-wave plate (HWP) is changed, start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.

• Beam tuning and Møller runs
  • Generally, Detector HV OFF
  • Turn DC HV off only for beam tuning

Access to the Hall

• If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).
• Check in with the shift personnel before entering the hall.
• The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF during run time.

DAQ Operation & Related Information

NEW STANDARD end and start of the run: - "End run" - "Abort" - "Configure" - "Download" - "Prestart" - "Go" This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery. Restart DAQ -- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery: - "Cancel" - "Reset" - "Configure" - "Download" - "Prestart" - "Go"

Restart DAQ: ensure that each step is completed in the Run Control message window. During "Configure", look for error messages in the ROC terminals Some ROCs keep printing error messages while functioning properly, see logbook entry # 4215299 If a ROC is disconnected, the message will appear in the run control message window If a ROC has crashed Find out which one (look for busy ROCs) End the current run Issue a roc_reboot command on just that ROC (for rich4 perform "Full RICH Recovery", that includes rebooting rich4. See "Current Issues") ssh to the ROC to check that it is back (some take longer than others). After ssh-ing successfully type "exit" Restart DAQ Pop-up window: Enter the beam current and the type of run in the "Comment" field At the start and end of a run, check that the data in the Run Condition Data Base (RCDB) is correct, especially the manually filled fields Check and reset monitoring histograms every hour. Sometimes, it is the only way to know that a specific ROC needs to be rebooted In case of DAQ Disk space alarm, call the DAQ expert. Contact the DAQ expert if you have any questions or doubts about how to proceed

Reference Values

FSD Thresholds

Fast Shutdown (FSD) Parameters

Counter	Rate	dwell time
Upstream	2 kHz	5 ms
Midstream	2 kHz	5 ms
Downstream	100 kHz	5 ms
BOM	1.6 kHz	5 ms

Nominal Beam Positions

Position	x [mm]	y [mm]	Date	Note
2C21A	$-0.4$	$+0.8$	May 12, 2025	NOT part of orbit lock
2C24A	$-2.0$	$+1.0$	May 12, 2025
2H01	$-1.6$	$+0.8$	May 12, 2025

Latest Harp Scan References

Mode	Harp	Width			Reference	Date
Beam to Tagger Dump	2C21A	$\sigma _{x}\sim 150\mu {\text{m}}$	$\sigma _{y}\sim 150\mu {\text{m}}$	N/A	4371796	May 9, 2025
	2C24A (Tagger)	$\sigma _{45}\sim 500\mu {\text{m}}$	$\sigma _{y}\sim 300\mu {\text{m}}$	$\sigma _{x}\sim 500\mu {\text{m}}$	4371790	May 9, 2025
Beam to Faraday Cup	2C24A (Tagger)	$\sigma _{45}\sim 500\mu {\text{m}}$	$\sigma _{y}\sim 300\mu {\text{m}}$	$\sigma _{x}\sim 500\mu {\text{m}}$	4371849	May 9, 2025
	2H01	$\sigma _{x}\sim 330\mu {\text{m}}$	$\sigma _{y}\sim 100\mu {\text{m}}-200\mu {\text{m}}$	$\sigma _{45}\sim 250\mu {\text{m}}$	4371838	May 9, 2025

Beam Restoration and Møller

Before starting the beam restoration procedure, make sure to read the manual: Establishing Physics-Quality Beam. Note that while the values in this manual are outdated (from 2023), the overall procedure is the same. For up-to-date values and step-by-step instructions, please use this wiki page. If you do not feel confident doing this alone, contact the Beamline Expert!

Make sure to cross check the reference values against the latest reference values on the CH whiteboard.

Restoring Beam after Short Downtime

Use this procedure after shorter interruptions in the beam, when there is no reason to expect the optics to have changed. Ask the RC if you are not sure if this applies. Examples are after a target change, or after a change in beam steering or beam orbit. We systematically go from 5nA, to 10% of production current, to full production current while ensuring everything is OK

1. Procedure to ensure good running conditions for data taking
   1. Ask MCC to send beam with the desired current (first with 5nA and then following the steps below)
   2. Ensure orbit locks are enabled
      • It may take 30 seconds for the orbit locks to turn green in the beamline display and for the beam positions to stabilize
   3. Check 2C24A and 2H01 beam (x, y) positions against the reference values
      • If BPM 2C24A and/or 2H01 positions are off (not within $\pm$0.1 mm), ask MCC to bring them to the reference values
   4. Post the scaler displays (beamline, FTCal, ATOF scalers) while beam is on to the logbook
   5. Ensure halo rates, FTCal, and ATOF rates are nominal compared to the previous beam restoration (in the logbook). Contact the Beamline Expert or RC if you are unsure.
   6. If conditions are good, continue to the next step. If conditions are NOT good, contact the Beamline Expert or RC for guidance.
2. Steps to gradually go from 5nA to production current:
   1. Follow the procedure to ensure good running conditions for 5nA
   2. Follow the procedure to ensure good running conditions for 10% of production current (e.g. 30nA for 325nA production running)
   3. Follow the procedure to ensure good running conditions with full production current (e.g. 325nA on He-4)
   4. Start the DAQ and take data!

Full Beam Restoration

Before starting the beam restoration procedure, make sure to read the manual: Establishing Physics-Quality Beam. Note that while the values in this manual are outdated (from 2023), the overall procedure is the same. For up-to-date values and step-by-step instructions, please use this wiki page. If you do not feel confident doing this alone, contact the Beamline Expert

STEP 2 (Beam Tuning to the Faraday Cup) usually requires the target to be emptied. It is recommended to contact the Target Expert by the beginning of STEP 2 while the tagger magnet is being degaused to empty the target

STEP 1: Beam Tuning to Tagger Yoke Dump

1. All CLAS12 detectors (including ALERT) HV off
2. Ask MCC to energize the tagger magnet
3. Set blank collimator (In CS-Studio CLAS12 Menu: Subsystems -> Motors -> Collimators, Viewers, ... -> Collimator. Click "Blank (0 mm)")
4. Set beam type to "Photon"
   • In CS-Studio (CLAS12 Menu): Subsystems -> Beamline -> BTA Config. Click "PHOTON"
5. Ask MCC to mask the beam halo counters FSDs (i.e. the Upstream, Midstream, Downstream and BOM FSDs)
6. When tagger magnet is energized, ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
7. If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the reference values (should be within $\pm$0.1 mm).
8. Take harp scans
   • In CS-Studio (CLAS12 Menu): Subsystems -> Motors -> Harp Scans" (see also the harp scan manual
     1. At Harp 2C21A (Upstream Right Counter) (Click "SCAN")
        • Fit the results and post the results to the logbook
        • Post a picture of the beam line overview to the logbook (this is important to document the corrector magnet settings, etc.)
     2. At Tagger Harp 2C24A (Upstream Right Counter) (Click "SCAN")
        • Fit the results and post the results to the logbook
        • Post a picture of the beam line overview to the logbook
     3. Validate the results with the harp scan references (make sure to look at the references for beam to the tagger dump).
        • Compare positions against the nominal beam positions (cross check with the white board!). Position offsets should be well under $\delta _{x,y}<200\mu {\text{m}}$
        • Compare widths ($\sigma$ values of the fit) against the harp scan reference. The widths should be near the reference width. Smaller values are typically OK, and a bit larger values are also tolerable within reason - the references are not hard limits
     4. If NOT good (either width too large or position off), ask MCC to address the issue and repeat
        • If you have taken four or more iterations of harp scans, please contact the Beam Line Expert for advice on how to proceed
   • If the beam trips, abort the scan and restart. The beam must be on during the scan; otherwise, the fit to the beam profile will not work!
   • The fit ranges, in particular for 2C24A, may need to be adjusted manually for the fit to work. Use the ranges in the reference figures

STEP 1b (optional): Møller Measurements

While not part of the full beam restoration procedure, Møller measurements are often paired with the beam restoration as the tagger is already energized. Møller Measurements should be done once every week. In case of doubt if Møller measurements are needed, ask the RC or Beam Line Expert

1. Follow the standard procedure as described in the manual Performing Møller Runs
2. Request 20 nA and Orbit Locks OFF.
   • Orbit locks should be off as the BPM positions may drift out of range after the Møller configuration. This is normal!
3. Keep running until the polarization uncertainty is < 1.5%

STEP 2: Beam Tuning to Faraday Cup

Beam tuning to the Farady Cup is typically done after tuning to the tagger dump (and possibly taking a Moller run). It can also be done to assess beam quality when needed.

1. All CLAS12 detectors (including ALERT) HV OFF
2. Ask MCC to de-energize the tagger magnet
   • In parallel, call the target expert to empty the target (in some cases under direction of the RC or Beamline Expert, emptying the target may not be needed)
3. Set collimator to 20 mm
   • In CS-Studio (CLAS12 Menu): Subsystems -> Motors -> Collimators, Viewers, ... -> Collimator. Click "20 mm"
4. Set beam type to "electron"
   • In CS-Studio (CLAS12 Menu): Subsystems -> Beamline -> BTA Config. Click "ELECTRON"
5. Set BEAM BLOCKER to OUT
   • In CS-Studio (CLAS12 Menu): Subsystems -> Motors -> Collimators, Viewers, ... -> Blocker. Click "Go Home"
6. Ask MCC to unmask beam halos
7. Ask MCC to set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds
8. Insert the Downstream Viewer, Chromax, in the beamline
   • In CS-Studio (CLAS12 Menu): Subsystems -> Motors -> Collimators, Viewers, ... -> Viewer. Click "Chromax"
9. Ask MCC for 5 nA beam current and make sure the orbit locks are ON
   • It may take 30 seconds for the orbit locks to turn green in the beamline display and for the beam positions to stabilize
10. If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the reference values (should be within $\pm$0.1 mm).
11. Take harp scans:
    • In CS-Studio (CLAS12 Menu): Subsystems -> Motors -> Harp Scans" (see also the harp scan manual).
      1. Do harp scans at 2C24A (Upstream Right Counter) then 2H01 (Midstream Left)
         • Fit the results and post the results to the logbook
         • Post a picture of the beam line overview to the logbook together with each of the harp scans.
      2. Validate the results with the harp scan references (make sure to look at the references for beam to the Faraday Cup).
         • Compare positions against the nominal beam positions (cross check with the white board!). Position offsets should be well under $\delta _{x,y}<200\mu {\text{m}}$.
         • Compare widths ($\sigma$ values of the fit) against the harp scan reference. The widths should be near the reference width. Smaller values are typically OK, and a bit larger values are also tolerable within reason - the references are not hard limits.
      3. If NOT good (either width too large or position off), ask MCC to address the issue and repeat.
         • If you have taken four or more iterations of the same harp scans, please contact the Beam Line Expert for advice on how to proceed.
    • If the beam trips, abort and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.

STEP 3: Prepare for Physics Running

Slowly move into Physics running after the checkout procedure:

1. Ask MCC to:
   1. stop the beam
   2. re-enable the orbit locks
   3. put the halo FSD thresholds and integration times to their reference values
2. Ensure the BEAM BLOCKER is IN on the beamline display
   • If the Beam Blocker is OUT, put in the Beam Blocker (Click "Go Beam")
3. Turn all detector HV ON
4. Procedure to ensure good running conditions for data taking
   1. Call MCC to send beam with the desired current (starting with 10% of production current on an empty target, and then following the steps below)
   2. Ensure orbit locks are enabled
      • It may take 30 seconds for the orbit locks to turn green in the beamline display and for the beam positions to stabilize.
   3. Check 2C24A and 2H01 beam (x, y) positions against the reference values
      • If BPM 2C24A and/or 2H01 positions are off (not within +/-0.1 mm), ask MCC to bring them to the reference values.
   4. Post the scaler displays (beamline, FTCal, ATOF scalers) while beam is on to the logbook
   5. Ensure halo rates, FTCal, and ATOF rates are nominal compared to the previous beam restoration (in the logbook). Contact the Beamline Expert or RC if you are unsure.
   6. If conditions are good, continue to the next step. If conditions are NOT good, contact the Beamline Expert or RC for guidance.
5. Steps to gradually go from empty target running at 10% current to production running:
   1. Follow the procedure to ensure good running conditions with 10% of production current on an empty target (e.g. 30nA for 325nA production running).
   2. Have the target expert bring the target the desired pressure and gas (e.g. production He-4 target)
   3. Follow the procedure to ensure good running conditions for 10% of production current with the filled target (e.g. 30nA for 325nA production running)
   4. Have MCC stop the beam
   5. Retract the Downstream Viewer from the beamline (Click "Retract")
   6. Follow the procedure to ensure good running conditions with full production current (e.g. 325nA on He-4)
   7. Start the DAQ and take data!

AHDC

• The HV on the ALERT AHDC needs to be turned OFF when the magnet is OFF and during longer downtimes (over 30 minutes).
• There might be an issue with the plots in "AHDC_Occupancy" section of monitoring plots: See here: https://logbooks.jlab.org/entry/4369218. If you observe this, make a logbook entry in HBRUN and HBALERT. Include information on whether the livetime was reduced during the run in the posted logbook entry (in most cases, this is not the case).

ATOF

• If the ATOF HV trips and it is not related to transient beam steering issues follow this procedure:
  1. run /home/clasrun/alert/scripts/cycle_atof_power.sh
  2. Start new run
  3. If HV continues to trip, contact expert.

Note: Currently ATOF is running without Channel M7_B (Module 7 Bar) until repairs will be done. Do not expect the HV and LV on these channels to be at nominal values.

DAQ

• clondaq11 takes a bit of time to reboot. Give it a minute or two. You can test that it is fully rebooted if you can ssh to it (without password prompt). If problem persists, reboot it then call DAQ on-call before starting the run. Sergey need to make a manipulation on it.

RICH

• Please log details about the RICH alarms, along with screenshots of the RICH temperature monitors, scaler rates, and specific alarm messages. (HBRUN, HBLOG, RICH elogs)
• The RICH fibers alarm leads to web guidance, aka logbook entry 3562273 - RICH recovery procedure - scroll to the bottom. Please perform "Full RICH Recovery".
• If the rich4 roc is 100% busy perform "Full RICH Recovery" (not only roc_reboot rich4).

• Known problematic PMTs and tile:

- You don't need to report about it.

- Problematic tiles and PMTs:

• Sector 1 Tile 21 dead (PMT 55,56,57)

• Sector 1 Tile 1 PMT 2

• Sector 4 Tile 34 PMT 92

- PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.

Rapid/Controlled Access to the Hall

• Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.
• After a higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.

24/7 ZOOM connection for Counting House

• Click on https://jlab-org.zoomgov.com/j/1618614939, which is included in "Remote Shifts" in the "Shift Worker" tab.
• choose the option to "join from browser" (Chrome is recommended) and ignore all other messages to update the ZOOM APP in the pop-up windows.
• Enter the passcode from the logbook entry in "Shift Worker" tab.

Lights in the Hall

• The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF because of light leaks from some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall.
• Refer to these photos: ON: [1], OFF: [2]
• We have a new dome light switch outside the hall in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460
• When the dome lights are switched off, they cannot be turned back on immediately; they require 10-15 min to cool down.

Beamline

• When are dealing with bad quality beam, Please pay extra attention to beam quality alarms. Observe Fast Shut Down scaler rates (on Beamline Overview and Strip Charts, scaler_cS3b Upstream Left, scaler cS4b Upstream Right, ISD2H001HALORATE04 BOM), FT rates (on FTC FADC Scalers plot). Alarms has been set on non-acceptable values for those, and if the beam quality is bad and we see those keep alarming, please call MCC and ask to work on the beam quality. Keep detectors off when beam is unstable and MCC is trying to do touch ups. Make the log entry.
• Orbit locks are on BPMs 2C24A and 2H01, which should generally be on ("Running").

- Beam positions at 2C24A and 2H01 must be kept within ±0.1 mm at the nominal beam positions listed under "References" at the Short Term Schedule tab.

• The beam position at 2C21A is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.
  • The beam position at 2C21A is important for initial beam tuning (on tagger dump).
• After the HWP change

• The absolute values of the SLM and FCUP charge asymmetry (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.

• Start a new run

• Tagger Magnet Procedure: If the tagger magnet needs to be turned off, tell the operator to ONLY use the script for degaussing, NEVER do it "by hand"! The latter method might/will trip the circuit breaker for the power supply in the Hall.

CND

• CAMAC crate alarm:

• CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, which can be done via the alarm handler.

• After reboot, the CFD thresholds need to be set by running a script; see page 12 in the CND manual at the "General" tab: https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf

DAQ

• Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # 4215299 to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected!
• NEW STANDARD end and start of the run: End run, Cancel, Reset, Download, Prestart, Go. This will ensure proper compression of the FADCs and, therefore, a smaller data rate.
• ROC reboot instructions:

• To reboot, i.e., adcecal1, or any noted ROC that became busy, type on a clasrun terminal: clasrun> roc_reboot adcecal1

• To check that the roc is back alive, type:clasrun> ssh adcecal1

• If you can ssh it means that it is back. Type exit.

DC

• Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.

ECAL/PCAL

• "ECAL_SEC6_UO26 Noisy" https://logbooks.jlab.org/entry/4241957
• "PCAL_HV_SEC2_U25 turned off" https://logbooks.jlab.org/entry/4247187, https://logbooks.jlab.org/entry/4247400

FTOF

• Arrive at your shift in time for the shift change, 15 minutes before the start of your shift.

• If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.

• Follow the Short Term Schedule;

• The RC must be notified before changing run conditions.

• Operate the Data Acquisition.

• Take action on and log alarms.

• Communicate with your co-shift person:

• Remind them to read the tab 'Shift Worker'.

• The shift worker should discuss an issue with the shift expert before making extra logbook entries.

• During production, not in extended downtime, the shift expert should ensure the shift worker is filling their end-of-shift Checklist when the beam is ON, not in the period of beam trips.

• Use the CS-Studio Logbook entry tool for all screenshots (but the strip charts)!

• Note that the Logbook Entry tool defaults the entry in the HBRUN logbook. Other logbooks can be added or selected from the drop-down menu.

• Check for and read any comments made to log-book entries during your shift.

• Keep your shift summary up to date in HBLOG. Record all shift activities, issues, if any, and related communications with experts with details and/or reference to any associated logbook entries:

- Refer to relevant logbook entries in the shift summary.

- Include a list of runs taken during the shift with relevant run information;

• See, for instance, this shift summary where all relevant run info, links, and shift activities are cited.

• Ensure that all MON12 monitoring plots are logged and checked against the reference plots for every single run; see the links under Monitoring tab;

• Both, you and the shift worker should run MON12 and reset & check spectra frequently.

• If the worker shift is remote, maintain communication over Zoom.

• If you have any other questions or uncertainties about what to do, call the RC.

• At the end of the shift, submit the strip charts to the logbook:

- If they are not up already: (CS-Studio → Tools → Strip Charts → livePlot)

- Right-click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"

- Choose a time-span width of 10 hours (right-click below x-axis)

- To make a logbook entry:

• Right-click within the grid of one of the charts, choose "Make Logbook Entry"

• The title of the logbook entry can be changed, eg to Strip charts

• Un-click ELOG, select HBLOG and click "Make Entry" to submit.

• Fill out BTA hourly;
• Accelerator beam time (Verify that these look correct. Make changes if needed and explain changes in the expert shift log):

• ABU: acceptable beam used

• BANU: beam acceptable but not used (should be reflected in our PCC and UED)

• BNA: beam not acceptable (e.g., tuning, drifting, not focused)

• ACC: Accelerator Configuration Change (e.g., pass change)

• OFF: Accelerator is down

• Experiment beam time (Allocate time into the appropriate category):

• ER: Experiment ready (should be 60 minutes - PCC - UED)

• PCC: Planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, etc.)

• UED: Unplanned experiment down (hardware failure, DAQ crashes, our problems, ...)

• Exception: BANU, due to time spent on beam tuning and BPM checks after beam down, should be counted as ER on our side.

• Enter fields at the "Shift Information" tab.
• To send information to MCC, you must save at 7:00, 15:00, and 23:00. To see the save button, click 'edit all' or 'Edit CC Hours.'
• Acknowledge the popup error message about the last hour not being completed by clicking OK.
• Sign, viz log completed 8-hour sheet.
• Note: we can change the time sheet up to 48 hours after completion.

• Come to your shift in time for the shift change, 15 minutes before the start of your shift;

• If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.

• Discuss any issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary.

• Use the CS-Studio Logbook entry tool for all screen shots, except the strip charts!

• Make sure the RICH temperature and scaler GUIs are up. In case of RICH issues, check the RICH manual for the current guidance: https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf

• Make sure the FT trigger GUI is up.

Frequently

• Reset and check MON12 histograms frequently, preferably each 1 h, during a run;

• Note that some plots have radio buttons at the bottom to choose the sector. Remember to cycle through and check all sectors.

• Monitor the trigger rates and if some trigger bits are zero, please discuss this with the shift expert and make a log entry to tag the related detector expert.

Once per run

• Note that the CS-Studio Logbook Entry tool puts the entry in the HBRUN logbook by default. Other logbooks can be added or selected from the drop-down menu.

• Using the Logbook Entry tool, submit EPICS screenshots to the HBRUN logbook (one logbook entry) with beam ON:

1. Beamline overview (remote shift: in VNC or Web Browser)
2. DAQ status
3. CLAS12 trigger rates

• Upload mon12 monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see Monitoring tab). Notify shift expert about your observations!

• At the end of the run:

- Submit the strip charts to the logbook:

• If they are not up already: (CS-Studio → Tools → Strip Charts → livePlot)

• Right-click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters" and "AHDC_Overview"

• Choose a time-span width of 4 hours, compatible with the run duration (right-click below x-axis)

• To make a logbook entry:

• Right-click within the grid of one of the charts, choose "Make Logbook Entry"

• The title of the logbook entry can be changed, eg to Strip charts

• Un-click ELOG, select HBLOG, and click on "Make Entry" to submit

- Upload the clas12online plots to the logbook.

• The program can continue through a standard end/start of a run. However, after a DAQ restart, you must back out and restart clas12online.

• If the DAQ has to be restarted, you can still make the upload before backing out.

Once per shift

• At the beginning of the shift take screenshot of ALERT ATOF HV overview and add to HBLOG and HBALERT.
• At the beginning of the shift restart clas12online .
• Fill the shift checklist;

• During production, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status and CLAS12 Trigger;

• During extended downtime, get relevant values from the latest EPICS screenshots that you made during production

For Remote Shifts

• Please inform the PDL that your shifts will be remote. . Remote shifts are listed here
• You must test your setup, including ZOOM and VNC connections, at least 24 hours before your first shift!

♦ ZOOM for 24-7 communication with Counting House:

• In a Web-browser: https://jlab-org.zoomgov.com/j/1618614939; Or in the ZOOM APP: Enter the meeting #: 1618614939, then

- The required passcode can be obtained from this log entry

• Remind the expert in the counting house to restart their ZOOM, if necessary
• Remote VNC connection instructions: https://logbooks.jlab.org/entry/3906039:

• If you mistyped (username, pincode, passcode,...) a string of numbers will appear with text asking you to respond to this challenge. Back out with Ctrl_c, and you get another try! After N+1 mistypes, you will be locked out. For several hours after that, you will not even be able to get to the public JLab web pages.

• All necessary applications should be available from the desktop menu (left/right click on the desktop)

• EPICS GUIs should be accessed ONLY via the desktop menu or by running clascss-remote.

• Some charts are also accessible via web browser: Upstream/Midstream Halo Counters, Downstream Halo Counters, Beam Currents, BPM Positions

Safety instructions

• All RG-L RCs and ALERT AHDC/ATOF experts must have a pre-job briefing BEFORE they begin their terms. This briefing will be given by myself and/or Florian. This is part of the ALERT ePAS operations requirement. You must also sign the ePAS document that will be in the Safety Documentation Binder in the Counting House.
• Before making any entry into Hall B related to the ALERT system once the run officially starts, you are required to make an entry in the HBLOG detailing your work plans. A follow-up log entry should be made after returning from the hall. This is very important and will be monitored by the JLab Division Safety Officer to be sure that we are in compliance.
• Before you begin your terms on-site at JLab, you are required to take ladder safety training (SAF307). It will take about 15 minutes. See [3] This is in addition to all of your other required training courses (RW-I, ODH, ESC001).

AHDC

• Max HV for production (no sparks): no field 1300V in field 1325V
• File for pedestal runs: alert1_base.cnf

• Check the upcoming shifts, and if necessary, coordinate with the PDL to contact shift takers about their training and site access status.

• Remote shifts are listed here.

• Backup shift personnel is listed here.

• Meeting ZOOM connections: see Important Links or Short Term Schedule tab

Daily

• Report at the PD/RC and attend the MCC/OPS meetings (weekdays 7:45 AM and 8 AM Daily, MCC building). The PD will communicate when and how meetings happen on the weekend: You should expect a 9am remote zoom meeting on the weekends. Find the zoom link here: https://logbooks.jlab.org/entry/4280766 (same link as the 7:45/8 meeting)

• Update the run plan in the Short Term Schedule tab, as well as the whiteboard in CH, in coordination with the RG-L experiment Run Coordinators and communicate it to the shift crew.

• RC Daily summary in HBLOG.

• BTA time sheet: Make sure the "Beam Available Not Used" (BANU) time is accounted for as explained at the Shift Expert tab. The BTA information can be modified post-signature.

• NOTE: "After 48 hours, you cannot modify a User signed timesheet unless you are the signer, Hall Manager, or Admin".

• Run daily RC meetings in CH Room 200C and on ZOOM

• URL Link (including Passcode)

• Mo-Fr at 11:30 ET in the Counting House Conference Room

• Weekends upon agreement

• Send a daily invitation for the RC meeting to mailing lists clas12_alert, clas_members.

• Connect to Zoom in CH Room 200C: 757-269-7846

• Turn on the projector with the white remote control, then log into your CUE account. If not listed yet, click "Not listed?" in the bottom left to add your account.

• Once logged in, use the recommended Google Chrome to join the ZOOM meeting on the browser or use the ZOOM application.

• Since the room doesn't have audio, don't connect with the computer audio, but Call the 1-833-xxx-xxxx number shown in the ZOOM session on the small Cisco answering device. Once prompted, enter the meeting ID followed by the participant ID displayed in the ZOOM session to join the meeting.

• The room has a camera, which can be turned on via ZOOM.

• Purge the target once a day. Coordinate the schedule with AHDC/ Target expert.

Weekly

For RC summary, calculate data collected using ABU.

• MCC/OPS planning meeting, on Wednesdays at 13:30, MCC building.

• Submit (save) the online form Run Coordinator Weekly Summary beforehand and present its contents at the meeting.

♦ The summary covers the data-taking status from 7 a.m. on the previous Wednesday to 7 a.m. on the current Wednesday;

♦ Info about Scheduled Program, Acceptable Beam in Use (ABU), and CW (ABU+BANU) can be retrieved from the Beam Time Accounting interface: Beam Time Manager; Physics Time Accounting;

♦ The total experiment data collected to date could be retrieved from the up-to-date Accumulated "Charge" or "Luminosity" depicted on the "RG-L 2025 Progress" plot; see the Monitoring tab, or, for better accuracy, use the total reported ABUs in Beam Time Manager; Physics Time Accounting from the beginning of the run (Apr. 2^th 2025).

• Hall B meeting is on Mondays at 9 AM. Present your summary slides, which should be sent beforehand to the Hall B leader, Patrick Achenbach.
  • You can present the progress of the experiment with the RG-L progress figure
  • The long term run plan is available here

Webcams Hall-B Tagger Beam Dump Viewer Hall-B Fisheye Hall-B Spaceframe Level-1 Beamline Faraday Cup beam viewer • To reboot it, run beam-viewer-reboot Counting House Cameras: 2x2, Hall A, Hall B, Hall C, Hall D

EPICS Hall B (CUE Login) epicsweb • Accelerator Status • Strip Charts

Data Quality mon12 histograms: reference (run 21735) Hydra (CUE Login) clas12online: real-time reconstructed vertices & various event topologies Data CHARGE accumulation timeline [4]; LUMINOSITY accumulation timeline [5].

Hall-B Run Group L Wikipage Commissioning RCDB CCDB

Accelerator Accelerator Whiteboard Program Deputy Shift Plans Run Coordinator Reports Beam Time Accounting Reports PSS Elog Operational Restrictions

ZOOM Meetings 07:45 RC/PD Morning Meeting, passcode is 933173 08:00 MCC/OPS 8:00 M thru F and 13:30 Wednesday Meeting See also this logbook entry Daily Hall B Run Coordinator Meeting: • URL Link (including Passcode) • Meeting ID: 160 570 5819 • Passcode: see emails Hall B Remote Shifts & Counting House