Template:ShortTermSchedule-RGD

Run Coordinator: Susan Schadmand (757) 575-7540

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

RG/Analysis Coordinator (AC): Lamiaa El Fassi (630) 605-4259

Daily RC/OA Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1611984219; Passcode: RGD-RC23), except on Wednesdays, which is on ZOOM ONLY @ 15:30 due to the conflict with the 13:30 MCC Scheduling/Planning meeting.

Important Notes

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.
• If you have symptoms or a positive COVID test, do NOT come to your shift - instead, inform the PDL and the RC and JLab medical services immediately to arrange replacements.
• 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 "Worker Shift" Tab - you need some lead time to set up!

• Note to shift takers, please:

◊ Read the logbook, be aware of previous 24 hours

◊ Arrive at least 10 minutes early for shift change

◊ Refresh the run wiki pages; look over them every shift

- Follow the expert/worker shift instructions.

◊ For advice, do not hesitate to call the RC first and foremost, day or night.

Current Issues

• Do not spend more than 15-20 min trying to fix a problem. With any issue, contact On-Call Experts or RC.

• NOTE, the beam position on BPM 2C21A is not important, the beam orbit lock is on BPM 2H01.

• New RICH recovery protocol: see tab expert "Shift Expert" for new information. Avoid unnecessary recoveries.

• BMT/FMT/SVT: If new hot channels appear, call the MVT/SVT/MM expert Yuri Gotra (757-541-7539). These channels need to be addressed by the expert.

• Tagger magnet procedure: If the tagger magnet needs to be turned off, tell the operator to use only the script for degaussing, NEVER do "by hand"!

• Change of target in the hall: In case of questions from MCC about the necessary controlled access, refer to the logbook entry #: 4196113 for the access requirements.

Run Plan for Mon., Oct. 30th - Sat., Nov. 11th, 2023 Continue production on CuSn - Target: CuSn - Beam Blocker: IN - Beam current: 90 nA +/- 3nA on 2C21A - Run duration: 100 M events - DAQ configuration: PROD67 - Trigger file: rgd_out_v2.1_Q2_1.2.trg P.S.: If the beam is widely fluctuating above 90 nA, please ask MCC to narrow down the fluctuation margin and give us the required 90 nA +/- 3nA based on 2C21A reading. They could put the beam current lock on 2C21A in case that may help with the wide fluctuation as it's currently done. We will keep the beam blocker IN while using this target combination! Tuesday, Oct. 31st, Day Shift: • Please call the engineering on-call to change the target position in the hall to the liquid target position around 8:30 AM, depending on the progress of the run. Please keep the run ongoing until the engineer arrives, even if it exceeds 100 M. In parallel with rapid (controlled) access, change the solid flag assembly to "Empty" from the drop menu in the cryo-target GUI and start filling the LD2 cell. For more details, please refer to the cryo-target and flag assembly: manual. Also, retract the beam blocker Once the access is done and the cell is filled, ask for the beam and continue LD2 production as follows: - Beam current: 60 nA - Run duration: 100 M events - Beam Blocker: OUT - DAQ configuration: PROD67 - Trigger file: rgd_out_v2.1_Q2_1.2.trg Wednesday, Nov. 1st, Day Shift: • MCC Beam Studies! The hall will be in Controlled Access. even if it exceeds 100 M. • Please call the engineering on-call to change the target position in the hall to the solid target position. • Once the target work is done, change the solid flag assembly to "Empty" from the drop menu in the cryo-target GUI and start emptying the LD2 cell. For more details, please refer to the cryo-target and flag assembly: manual. Wednesday, Nov. 1st, Swing Shift: • Please follow the steps to establish the beam to tagger dump in the "Establishing Beam for Physics manual". A few points to note: energize the tagger magnet, then move the collimator to Blank position to not get an alarm, mask beam halos, ask for 5 nA beam current, check the 2C21A and 2C24A beam positions (x, y) recorded at the bottom of this page, and take a harp scan in 2C21 and 2C24 (tagger Harp) if they are fine. Please log your results after comparing them with the reference ones at the bottom of this page. Then, take a Møller run with a 1/2-wave plate OUT and the new Wien Angle. • Next, the collimator needs to be moved to a 20 mm position, unmask beam halos, then ask for a 5 nA beam to FCup, check the 2C24A and 2H01 beam positions (x, y) recorded at the bottom of this page, take a harp scan in 2H01, and compare their results with the reference one at the bottom of this page. Please log these results, too. • If everything is fine, please insert CuSn back in the beamline from the same drop-menu mentioned above along with the beam blocker and resume CuSn data-taking as follows: - Target: CuSn - Beam Blocker: IN - Beam current: 90 nA +/- 3nA on 2C21A - Run duration: 100 M events - DAQ configuration: PROD67 - Trigger file: rgd_out_v2.1_Q2_1.2.trg DAQ Operation STANDARD end of run and start of new run: - "End run" - "Prestart" - "Go" Restart from scratch when changing configuration or trigger files, or when the run did not end correctly, or when ROC(s) is(are) rebooted, or when RICH is FAST/Fully recovered, as follows: - "Cancel", "Reset" - "Configure" - "Download" - "Prestart" - "Go" Reference Values FSD Thresholds from RG-D Upstream: 2 kHz Midstream: 2 kHz Downstream: 100 kHz BOM: 50 kHz 5 ms dwell time Harp Scan References from RG-D 2H01 [1]; x= -1.4 mm; y= 0.0 mm Tagger (2C24A) [2]: x= -2.0 mm; y= +0.6 mm 2C21A [3]: x= -0.4 mm; y= +0.6 mm (less important; values form RG-C) IA for Q Asymmetry HWP IN: https://logbooks.jlab.org/entry/4194811 and https://logbooks.jlab.org/entry/4195453 HWP OUT: https://logbooks.jlab.org/entry/4195738 and https://logbooks.jlab.org/entry/4195733

General Instructions Data Acquisition: • Configuration is PROD66 (or PROD66_PIN for fast reconstruction of some calibration/reference runs from the cache disk); • In case of DAQ Disk space alarm, call the DAQ expert. • Trigger files: - Inbending production: rgd_inb_v1.0.trg - Outbending production: rgd_out_v2.1_Q2_1.2.trg with low-Q2 suppression • If a ROC has crashed, find which one it is, end the current run, issue a roc_reboot command ON JUST THAT ROC, and RESTART DAQ. • Unless a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run for a RICH recovery. Instead, do this in between runs. • The shift MUST check and reset monitoring histograms at least once every 30-60 minutes to ensure no major detector problems. Sometimes, it is the only way to know that a specific roc needs to be rebooted. • Pop-up window: Enter the beam current and the type of runs (e.g., Production) in the "Comment" field. • After each step of a DAQ RESTART, ensure it is completed in the Run Control message window. • Contact the DAQ expert if there are any questions. 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 (especially, ECAL sec 2 and 3). If these lights are switched on during an access, they should be switched off when leaving the Hall. • Refer to these photos: ON: [4], OFF: [5] • We have a new dome light switch outside of the hall in the labyrinth. The lights can be turned off without entering the hall. See https://logbooks.jlab.org/entry/4204460 • Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cool down. Beamline: • Do not run over 30 minutes above 90 nA with a 5-pass beam without the beam blocker IN . The beam blocker must be IN for long-running at high currents for 5-pass operations. • 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: ◊ Please check with the beamline expert whether the SLM and FCUP charge asymmetry (Q-Asym (%)) readings are set properly as they will be out of range in case Eugene's script is not run by the experts after the HWP change. At the start and end of every run, check that the data filled in the Run Condition Data Base (RCDB) is correct, especially the fields filled manually. For beam tuning and Møller runs • Make sure the SVT/MVT are set as follows: SVT: LV ON; HV OFF, and MVT: LV ON; HV ON in SAFE Mode. - When turning MVT OFF, do not press "BMT HV OFF" from HV->Overview->Actions, but instead select BMT HV ON - Safe Voltage. The same applies to FMT select FMT HV ON - Safe Voltage. - When turning MVT ON: go to HV->Overview->Actions, and select BMT (/FMT) "HV ON - Full Voltage". - DO NOT start runs in SAFE Mode for Production/Calibration/Various-Studies. • Turn DC HV off only for beam tuning; if no beam is available or when the beam is stable, keep them on even if you are not taking data. 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 (757-575-7540). • Check in with the shift personnel before entering the hall.