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
• 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

◊ Communicate with your co-shift person

- The shift expert should know about and refer to logbook entries in their shift summary

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

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

Current Issues

• BMT/FMT/SVT:

◊ If new hot channels appear, please call the MVT/SVT/MM expert Yuri Gotra (757-541-7539) to address them.

• 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 the LD2 and solid targets positions in the hall: In case of questions from MCC about the necessary controlled access, please refer to the logbook entry #: 4196113 for the access requirements.
• Please ensure the ZOOM session is ALWAYS running in the counting house, as it gets automatically disconnected after being idle with one end user for a while. See its remote connection under the Shift Worker tab.

Run Plan for Wedn., Oct. 25th - Tue., Oct. 31st, 2023 Wednesday, Oct. 25th, Swing Shift: • Please follow the steps to establish the beam to tagger dump, energize the tagger magnet, move the collimator to Blank position, 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 2C24A (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 IN. • Next, the collimator needs to be moved to a 20 mm position, unmask beam halos, and change the target to "Empty" from the drop menu in the cryo-target GUI. For more details, please refer to the cryo-target and flag assembly: manual. 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 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 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: • Switch back to LD2 around 8:30 AM. DAQ configuration 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, notify the DAQ expert and switch to Configuration PROD67. Trigger files: ◊ Inbending production: rgd_inb_v1.0.trg ◊ Outbending production: rgd_out_v1.1.trg, or rgd_out_v2.1_Q2_1.2.trg with low-Q2 suppression NOTE: UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to make a RICH recovery - instead, do this in between runs. Review its new recovery procedures in HBLOG entry #: 4201728. Note that you have to start new run with CANCEL-RESET after any RICH recovery. NOTE: BOTH the shift expert AND the shift worker MUST check and reset monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems. Sometimes, it is the only way to know that a roc needs to be rebooted. At the end of each run, follow the STANDARD DAQ RESTART SEQUENCE: ◊ "end run." ◊ If the run ended correctly and you will run with the same configuration and trigger file, then: "prestart", "go" ◊ If you are changing configuration (between PROD6X and PROD6X_PIN) or trigger file: "Cancel", "reset", "configure", "download", "prestart", "go". ◊ If the run did not end correctly or if any ROCs had to be rebooted: - "Cancel", "reset" - "configure", "download", "prestart", "go" Pop-up window: Enter the beam current and the type of runs (e.g., Production) in the as "Comment" field. After each step, make sure it is completed in the Run Control message window. If a ROC has crashed, find which one it is, issue a roc_reboot command ON JUST THAT ROC, and try again. Contact the DAQ expert if there are any questions. 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 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. Do not run more than 30 minutes above 90 nA with a 5-pass beam without the beam blocker in front of the 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 the beam is stable, keep them on even if you are not taking data. RICH issues: put screen shots of scalers and temperatures in the RICH logbook. For beam tuning and Møller runs, please 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 thing 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 Production/Calibration/Various-Studies runs in the SAFE Mode. With any issue, contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem. If the phone is not answered, try the "Page Experts" button on top of CLASCSS. Check for and read any comments to log-book entries made during your shift. Every Shift: Follow the run plan as outlined by RC (/AC). If there is 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. If HWP is changed, start a new run. Upload spectra from clas12mon at the beginning and end of the shift and cross-check with reference spectra (make sure you select the SAME SECTOR for the reference plots on tabs with multiple sectors); ◊ Reset clas12mon every ~2 hours and inspect spectra (some detectors have buttons at the bottom to toggle between the sectors -- please check all of them). Fill and submit the shift checklist in the logbook. Every Run: Check values at the start of every run and log screenshots of: ◊ Main scaler GUI display ◊ Trigger rate GUI ◊ Beam strip charts ◊ FTC scalers At the start and end of every run, check that the data filled in the database run list is correct (especially fields that are filled in manually, like beam current and comments). This replaces the previously used spreadsheet. To access the Hall: If you need to enter Hall B, alert Engineering On-Call (757) 748-5048 and the Run Coordinator (757-575-7540). Check in with the shift personnel before entering the hall.