Template:ShortTermSchedule-RGD

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

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

Daily RC Meetings at 15:30: CH Room 200C, and on Zoom: Link, Meeting ID: 1611984219, Passcode: RGD-RC23

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

LE: Please don't change: Work in progress

Short-Term Schedule for the Week from Sept 13th to Sept. 20th, 2023 Wednesday, Sept. 13th: shifts are canceled due to the target work and/or MCC beam/maintenance studies. Thursday, Sept. 14th: The current plan is to lock up the hall in the day shift and start tunning the beam to the tagger dump in the swing/owl shift. Friday, Sept. 15th: If the beam is successfully tuned overnight to the tagger dump, take a 1.5-hour Moller run with new quadrupole power supply and tagger ramping/degaussing; Does Eugene (or another beamline expert?) need to be consulted for this? Start tuning beam to Faraday cup. It may take 2.5 hours to ramp up the solenoid and torus to full current. The solenoid will be gradually ramped up to half field intensity, then full, then the torus will be turned on and ramped up to full inbending current. During this process, keep an eye on the deflection on the viewer; Does Eugene (or another expert?) need to be called for this? Trigger validation: Call MCC and ask for 35 nA and take 4 hours LD2 target run with a random trigger to validate electron trigger; Trigger file: TBD. Follow the DAQ instructions below to load a new trigger file. Take one hour LD2 run with the inbending e- trigger with no-DC-roads to validate the trigger roads. Trigger file: TBD. Follow the DAQ instructions below to load a new trigger file. Parasitic studies: When it's convenient, perform a slow beam current ramps up for scaler linearity. That can be done over the phone with the MCC ops using a 5 nA beam current increase steps until reaching 35 nA while starting the random trigger run. The process should take 5 to 7 min at max. The SVT/MVT expert could perform any SVT/MVT studies that fit within ongoing activities prior to production. (Comments and suggestions to be notified or add to this run plan are welcome) -------- If everything goes well, that should bring us to the Swing shift ------- DC HV Scan, TOF Gain and ECAL Calibrations: All runs will be taken with the TBD inbending e- trigger without DC-roads until the trigger roads are validated by the trigger team. Ask MCC for 45 nA beam current and take 5 hours runs with different DC HV settings. A total of 120 M electron triggers is needed for this study. Florian needs to be consulted. (I can't access Florian's table in Nathan's shared RG-D Special Runs document. Please, Florian, advise what needs to be specified here!) Take 1.5-hour run with just EPICS, no DAQ. Florian needs to be consulted. (I can't access Florian's document due to some expired access error??? ) Parasitically, 50 M electron triggers are needed for the TOF gain calibration Please, Daniel, advise whether you need to be contacted for any specific setup for this run!) Parasitically, the same data can be used to conduct a linearity study for the new ECAL sector 5 PMTs. Cole needs to be consulted. ( Please, Cole, advise what needs to be specified here!) Coarse Luminosity Scan: This first study is needed for TOF/ECAL linearity and AI training. A series of runs will be taken with the following beam currents: Ask MCC for 5 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. The random prescale factor needs to be decreased. Who should be notified about that, and for which beam current it should increase back? -------- If everything goes well, that should bring us to the Owl shift ------- Saturday, Sept. 16th: Luminosity Scan: Continue the study for the following beam currents: Whenever the 5 nA run is done, ask MCC for 10 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Ask MCC for 25 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Ask MCC for 35 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. -------- If everything goes well, the Day shift should start somewhere in between these runs! ------- Ask MCC for 50 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Once done, we could perform a high-current luminosity scan (to-be-revised based on the feedback). If so, ask MCC for: 75 nA and take a 50 M run with the TBD inbending e- trigger with no-DC-roads. 100 nA and take a 50 M run with the TBD inbending e- trigger with no-DC-roads. Depending on the detector's performance (HV trips?), the beam current can be reduced to 90 nA or until the level that the trips cease. Would that work? Once done, Valery should be called to change the RICH to a high threshold setting, then take a 100 M electron trigger run with 35 nA (~ 4h run). Please, Valery, advise whether you want to take this run now with no-DC-roads, assuming all other subsystems will be at their nominal settings!) Once done, the RICH setting can be reverted. Valery may need to be contacted again. Continue LD2 data-taking with 35 nA and 100 M runs until the end of the shift.---If everything goes well, that should bring us to the Swing shift --- Target Changeover: Denny/the target group (TBD) needs to be called ahead of time to ensure that the controlled access to change the target in the hall and boiling off LD2 will be done within 1/2h. Put the flag assembly in the C+C target configuration, then ask MCC for 30 nA and take 1/2h run with the TBD inbending e- trigger with no-DC-roads. Solid-target Luminosity Scans: C+C target configuration: Ask MCC for 10 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Ask MCC for 20 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Ask MCC for 30 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Ask MCC for 40 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Ask MCC for 50 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Cu+Sn target configuration: Ask MCC for 90 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Ask MCC for 100 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Ask MCC for 110 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Ask MCC for 120 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Ask MCC for 130 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. Ask MCC for 150 nA and take a 5 M run with the TBD inbending e- trigger with no-DC-roads. ---If everything goes well, the Owl shift should start somewhere in between the listed Cu+Sn luminosity scan runs! --- Sunday, Sept. 17th: If the Owl shift starts with an ongoing luminosity scan for Cu+Sn, please continue the study to complete the listed beam current runs. Once done, ask for 130 nA and take 100 M runs of Cu+Sn until the end of the shift. By the beginning of the day shift, change the target to C+C Assuming the MD If HWP is changed, start a new run DAQ configuration Configuration is currently PROD66/TBD for RG-D, trigger file TBD for RG-D 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-C Upstream: 5 Hz Midstream: 2 kHz Downstream: 10 kHz BOM: 1 MHz 5 ms dwell time Harp Scan References from RG-C 2H01 [1] 2C21 [2] Tagger [3]

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. Do not run more than 30 minutes above 30 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. ( Is this still relevant?) 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. 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 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.