Template:ShortTermSchedule-RGK

Experiment Coordinator: Annalisa D'Angelo

Run Coordinator: Axel Schmidt (757) 575-7540

PDL: Daniel Carman (757) 876-1789; Office: x5586

Daily RC/OA Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link

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

◊ 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;

◊ Refresh the runwiki 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.

◊ Review these important links:

- Recent Changes and Current Issues

- General How-to for beam restoration procedures and Møller runs.

Run Plan, Thursday, Jan. 11 - Saturday, Jan. 13, 2024 Thursday, Jan. 11: 12:00 – 15:00 - Beam tuning + Moller run - Tune beam to tagger dump yoke with necessary harp scans (Eugene Pasyuk) - Take Moller run at 20 nA (default settings; polarity positive, left target) (Nathan Baltzell) - Prepare for beam transport to Faraday cup; Note both torus and solenoid should be off. - Tune 5 nA beam to Faraday cup with warm/empty target with necessary harp scans (Eugene Pasyuk) - Perform a horizontal and vertical scan of the beam on the target to determine the nominal BPM settings - When tuning is complete have MCC turn off beam 15:00 – 24:00 – Alignment runs - Turn all detectors on; use nominal DC HV setting (11, 12, 12); torus and solenoid should be off - Take alignment run with warm/empty target - 3-5 nA beam (increase beam until R1 DC occupancies < 2-2.5%) - RC will dictate final beam current for all alignment runs - Use rgk_v1.0_zero_150MeV.trg, PROD67_PIN configuration - Normalize the DAQ trigger alarms once final beam current is chosen - Take data for 6-8 hours (2.5 M FD trigger events) - Take alignment run as target system cools - Begin target system cooldown (James Brock) - While target system cools (should take about 8 hours) take data (3-5 nA beam as previous step) - Use rgk_v1.0_zero_150MeV.trg, PROD67_PIN configuration - Take data for 6-8 hours (2.5 M FD trigger events) Friday, Jan. 12: 00:00 – 15:00 - Alignment runs (continued) - Take alignment run with cold/empty target - 3-5 nA beam (increase beam until R1 DC occupancies < 2-2.5%) - Use rgk_v1.0_zero_150MeV.trg, PROD67_PIN configuration - Take data for 6-8 hours (2.5 M FD trigger events) 15:00 – 18:00 - Prepare for production running - Ramp up the torus (-100%) and the solenoid (100% POSITIVE polarity) (Eugene Pasyuk) - Fill the target (James Brock) 18:00 – 21:00 - Production running - Take first production data run - rgk_noDC_v1.0_300MeV.trg, PROD67_PIN configuration - Data run should use 75 nA beam; collect 100M events - RC will dictate final beam current (R1 DC occupancies < 5% and DAQ livetime ~90%) - Normalize the DAQ trigger alarms once final beam current is chosen - Review all mon12 and Hydra plots throughout the run - Monitor the DAQ rate via strip chart throughout the run and notify the RC if there are any DAQ trigger alarms not due to beam excursions/trips - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook 21:00 – 24:00 - Production running (continued) - Take production data - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration - Data run should use 75 nA beam; collect 100M events per run - Review all mon12 and Hydra plots throughout the run - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook Saturday, Jan. 13: 00:00 – 24:00 – Production running (continued) - Take production data - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration - Data run should use 75 nA beam; collect 100M events per run - Review all mon12 and Hydra plots throughout the run - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook

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 (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: [1], OFF: [2] • 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 logbook entry: https://logbooks.jlab.org/entry/4204460 • Note that when the dome lights are switched off, they 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 . • 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. The absolute values should be less than 0.1%. 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.

DAQ Operation & Related General Instructions

(New) STANDARD end and start of the run: - "End run" - "Cancel" - "Reset" - "Configure" - "Download" - "Prestart" - "Go" RESTART DAQ 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"

Configuration is PROD67 (or PROD67_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: - XXX.trg During "Configure", observe the ROC terminals to see whether any ROC has error messages. Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # 4215299 to avoid unnecessary reboot since the printout in the ROC terminal won't change. If any of them get disconnected, the message will appear in the run control itself! If a ROC has crashed, find which one is (look for busy ROCs), end the current run, issue a roc_reboot command ON JUST THAT ROC, and test with SSH or PING to check whether the ROC is back up (some take longer than others). Then, RESTART DAQ from scratch. 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 shifter 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. Also, during "Configure", look for error messages in the ROC terminals. • Contact the DAQ expert if you have any questions or doubts about how to proceed. At the start and end of every run, check that the data filled in the Run Condition Data Base (RCDB) is correct, especially the manually filled fields.

Reference Values

FSD Thresholds from RG-K

• Upstream: 2 kHz
• Midstream: 2 kHz
• Downstream: 100 kHz
• BOM: 50 kHz
• 5 ms dwell time

Harp Scan References from RG-K

• 2C21A [3]: x= -0.4 mm; y= +0.6 mm
• Tagger (2C24A) [4]: x= -2.0 mm; y= +0.6 mm
• 2H01 [5]; x= -1.4 mm; y= 0.0 mm

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