Template:ShortTermSchedule-RGE

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

PDL: Nathan Baltzell (757) 876-1789, Office: x5902

Daily RC Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1605705819), except on Wednesdays, which is @ 15:00 in CH Room 200C and at the same ZOOM link.

Important Notes

• In case of medical or fire emergency, call 911 or 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 can call MCC to turn the beam OFF for Hall B and inform other Hall B staff members.
• If you have symptoms or a positive COVID test, do NOT come to your shift. Instead, inform the PDL, the RC, and JLab medical services immediately to arrange replacements.
• In case of a problem with the HV Slow Controls, EPICS in general, please call the primary expert on-call: Nathan Baltzell, before reaching out to anyone else.

Please put all essential information on the main hall B log HBLOG. Some important alarms have been documented on HBRUN. Use the pulldown menu to choose where an error is reported.

Current Run Plan: May 8th to May 15th Take production data! Don't break anything! Keep an eye on the backgrounds, such as in the halo counters and the 2C24 and 2H01 BPM positions. Both of these give confidence that the beam remains centered on the RGE target. See the General Information tab for specific issues with the detector subsystems. Production data taking: LD2+Al runs • Target: LD2 + Al • Beam Blocker: IN • Configuration: PROD67 (w/o. PIN option) • Trigger: rge_inb_v1.0_200MeV.trg • Beam Current: 70 nA • 3-hour runs If you need to manipulate the whole target system - cryotarget or solids - please contact the target experts. For information on triggers, please see here: https://logbooks.jlab.org/entry/4267187 Long-term run plan can be found in this link: [1], which will be updated based on the following May 8th RC meeting discussion: • Luminosity scan for LD2+Al: Take runs at various beam currents spanning the range from 5 nA to 70 nA with a 15 nA step. • Take more runs at low current for LD2+Pb, if the time allows, once the LD2+Al production runs are completed! • Take one Empty+Empty run for the dual-target configuration to display all Al windows, cryo-cell, heat shield, etc., some of which are not resolved yet in the current reconstructed vertices. • Perform the Streaming Readout Test, which could be done in parallel with reversing the torus magnet polarity. The latter will be considered if the LD2+Al production runs are completed. • Take data with the outbending configuration with the to-be-determined dual-target configuration if the LD2+Al inbending production runs are completed. Previous Dual-target Configuration Plans - DC firmware test plan (LD2 + Pb) 1) Take one run each with 1M events with the trigger files and beam current at 70 nA rge_inb_v1.0_200MeV_dcrb17_1.trg : DCRB Threshold (30, 45, 45 nA) rge_inb_v1.0_200MeV_dcrb17_4.trg : DCRB Threshold (30, 60, 45 nA) rge_inb_v1.0_200MeV_dcrb17_3.trg : DCRB Threshold (45, 60, 60 nA) rge_inb_v1.0_200MeV_dcrb17_2.trg : DCRB Threshold (30, 30, 30 nA) 2) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_2.trg 3) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_4.trg • Before the last run, call DC expert Florian so that he can change the firmware after the last run is finished. *** Notes *** • In every step, follow DAQ procedure (End run, Cancel, Reset, Configure, Download, Prestart, Go) • For every run please log clas12mon plots from the special version at /usr/clas12/offline/clas12mon/dcrb/bin/mon12 LD2+Pb runs Trigger: rge_inb_v1.0_200MeV.trg Beam Current: 70 nA Use PROD67 configuration (this will not PIN data) 3-hour runs LD2+Sn runs Trigger: rge_inb_v1.0_200MeV.trg Beam Current: 65 nA Use PROD67 configuration (this will not PIN data) 3-hour runs

References - BPM Positions The most important BPMs to monitor are 2C24A and 2H01, from the point of view of assuring the beam remains centered on the RG-E target. Other steering/focusing beamline elements can influence the values of the others. BPM X (mm) Y (mm) 2C21A -0.4 +0.7 2C24A -1.7 +0.5 2H01 -1.0 +0.25 - Harp Scans 2C21A 2C24A/Tagger 2H01 - FSD Thresholds Do NOT change FSD settings without approval from RC or beamline expert! • Upstream: 2 kHz • Midstream: 3 kHz • Downstream: 150 kHz • BOM: 50 kHz • 5 ms dwell time - Charge Asymmetry HWP IN: 4194811 and 4195453 HWP OUT: 4195738 and 4195733 - Upstream Halo counters If the reading on the upstream halo counters exceeds 10, please contact MCC.

General Reminders The main lights in the Hall and the Forward Carriage lights must be kept off during data taking. • Refer to these reference photos, ON and OFF • The main, dome lights can be turned off without entering the Hall. Beamline • Do not run over 30 minutes above 90 nA with a 5-pass beam without the beam blocker IN. • If there is any concern about beam stability, ask MCC if orbit locks are on (they should be). • Document any beam condition change and send scaler GUIs to HBLOG. • If HWP is changed, start a new run. During beam tuning and Møller runs • DC: HV OFF • SVT: LV ON, HV OFF • MVT: LV ON, HV ON in SAFE Mode • All CLAS12 detectors should be OFF; aforementioned tracking detectors are the most critical. To access the Hall • If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator. • Check in with the shift personnel before entering the hall.

DAQ Operation Standard end and start of a run End run Abort Download Prestart "Go" Restart DAQ from scratch • E.g., when changing configuration or trigger files, when the run did not end correctly, or after ROCs are rebooted Cancel Reset Configure Download Prestart Go DAQ instructions • Please make a log entry (logbook RICH, notify vpk@jlab.org) with RICH temp and scalers screenshots when you have RICH problems. • You do not need to stop the run each time you get 1-2 dead tiles if DAQ is still working. Continue data taking. When you start a new run, the dead tiles will recover without your intervention during DAQ Prestart with a high probability. If you still have problems, make a full RICH recovery and call Valery #5647.