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 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 meeting.

Important Notes

• 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 and night.

Run Plan for Oct. 7th to Oct. 8th, 2023 Saturday, Oct. 7th, Swing Shift: • Solid-target, CuSn Configuration, Luminosity Scan: ‡P.S.: Before starting each luminosity scan run, please call in advance the SVT/MVT experts, Yuri and Rafo at least 45 min and 30 min, respectively, to check the HV setting of MVT. ‡ The luminosity scan will be performed with the specified trigger files but with the same DAQ configuration: - DAQ Config.: PROD66_PIN. Follow the DAQ instructions below to change its configurations. ‡ We will scan three beam currents in this 5 M triggers run. Ask MCC for 110 nA, and take roughly 1.5 M events, monitor the DC occupancy in mon12 and log them, then increase the current to 120 nA, take another 1.5 M events, refresh mon12 and monitor the DC occupancy, and then increase the current to 130 nA for the last 2 M events while monitoring and logging the DC occupancy in mon12, but with the following trigger file: - Trigger file: rgd_v1.0_no_DC_100nA.trg. Follow the DAQ instructions below to load a new trigger file. ‡ Next, we will scan much higher beam currents in the last 5 M triggers run with this target. Ask MCC for 150 nA, take roughly 1.5 M events, monitor the DC occupancy in mon12, then increase the current to 175 nA for another 1.5 M events, refresh mon12 and monitor the DC occupancy, and then increase the current to 200 nA for the last 2 M events while monitoring the DC occupancy in mon12.. Depending on the detector's performance (HV trips?) during this run, the beam current can be reduced until the level at which the trips cease. If approaching the current of the previously taken run, check with the RC or AC whether the luminosity scan should stop or whether this last scan should be taken at a specific current value. • Once done, ask for 130 nA (check with RC/AC after Lumi. scan is done), keep the beam blocker in front of the Faraday cup, and take 100 M electron triggers runs of CuSn until the end of the Swing shift with the following configuration: - DAQ Config.: PROD66. Follow the DAQ instructions below to change its configurations. - Trigger file: rgd_v1.0_no_DC.trg.---If everything goes well, that should bring us to the Owl shift--- Sunday, Oct. 7th, Owl Shift: • It depends on the status of the run from the previous shift; please continue the run until it reaches 100 M with CuSn target, then switch to Carbon. The previous shift leader will instruct the Owl shift expert on how to move the solid target from CuSn to CxC. For more details, please refer to the cryo-target and flag assembly manual. • Since the beam was off for hours, continue data taking with CuSn whenever the beam is back until the end of the shift with the following configuration: - DAQ Config.: PROD66. Follow the DAQ instructions below to change its configurations. - Trigger file: rgd_v1.0_no_DC.trg.---If everything goes well, that should bring us to the Day shift--- Sunday, Oct. 8th, Day Shift: • It depends on the status of the beam: In case the beam is back and a run started, please continue the run until you reach 100 M. Otherwise, once the beam is back, please check the 2H01 and 2C21 beam positions, if reasonable, start a production run. If not, do a harp scan by following the procedure described for the case of the beam to FC, compare it to the reference one, and log your results • Solid-target, CuSn Configuration, Luminosity Scan (cont'd): ‡P.S.: Please call in advance the SVT/MVT experts, Yuri and Rafo, to let them know that we plan to take two high beam currents runs on CuSn that we postponed yesterday due to the instability of beam! ‡ Continue the luminosity scan with the specified trigger files and the following DAQ configuration: - DAQ Config.: PROD66_PIN. Follow the DAQ instructions below to change its configurations. ‡ Ask MCC for 150 nA and take a 25 M triggers run with the following trigger file: - Trigger file: rgd_v1.0_no_DC_100nA.trg. Follow the DAQ instructions below to load a new trigger file. ‡ Take a 25 M run @ 180 nA with the same DAQ and trigger configurations. • Once done, please call MCC to take the beam away, remove the beam blocker, and then ask for 50 nA to take 100 M triggers with CxC target until the end of the Day shift with the same DAQ and trigger configurations: - DAQ Config.: PROD66. Follow the DAQ instructions below to change its configurations. - Trigger file: rgd_v1.0_no_DC.trg.---If everything goes well, that should bring us to the Day shift--- Sunday, Oct. 8th, Swing Shift: • To be continued and confirmed during the Day shift! • In case 500 M triggers are already collected for each CuSn and CxC Target, we will flip the torus magnet polarity and change the target back to the LD2 position. • Please call Eugene to change the torus polarity to the outbending configuration. In parallel, Engineering-on-call/Xiangdong Wei should be called so the engineer will perform a controlled access to move the target back to the LD2 position while the RC/Xiaodong will fill the LD2 cell. • Once the torus is ramped up to the outbending setting, take another 50 M triggers run @ 35 nA with LD2 for the trigger validation and ECAL calibration run requested by Valery and Cole, respectively: - DAQ Config.: PROD66_PIN. Follow the DAQ instructions below to change its configurations. - Trigger file: rgd_v1.0_no_DC.trg. • Once done, we will switch to production mode with outbending configuration: - DAQ Config.: PROD66. Follow the DAQ instructions below to change its configurations and load new trigger files. - Trigger file: rgd_out_v1.0.trg. • To-be-continued.... . DAQ configuration Configuration is PROD66 or PROD66_PIN for fast reconstruction of some commissioning/reference runs from the cache disk. Trigger file: rgd_inb_v1.0.trg and rgd_out_v1.0.trg for inbending and outbending production. 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. 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: - Quit ALL running instances of mon12 - "Cancel", "reset" - "configure", "download", "prestart", "go" - restart mon12 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 2C21A [2]; Not done yet for RG-D, but from RG-C: x= -0.4 mm; y= +0.6 mm Tagger (2C24A [3]; x= -2.0 mm; y= +0.6 mm

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. If these lights are switched on during an access, they should be switched off when leaving the Hall. Note that the dome lights, when switched off, cannot be turned back on immediately because they require 10-15 min to cool down. Now we have a new dome light switch outside of the hall in the labyrinth. The lights can be turned off without entering the hall. 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. 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. ◊ When turning MVT ON: go to HV->Overview->Actions, and select BMT 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 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 go down into 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.