Template:ShortTermSchedule-RGD

Run Coordinator: Lamiaa El Fassi (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 on CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1611984219; Passcode: RGD-RC23), except on Wednesdays, which is in 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

Run Plan for Sept. 29th to Oct. 2nd, 2023 All shifts are canceled until Friday, Sept. 29th, due to the target work delay. Thursday, Sept. 28th: The tentative plan if everything progresses well with the target work 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. 29th: If the beam is successfully tuned overnight to the tagger dump, take a 1.5-hour Moller run with a new quadrupole power supply and tagger ramping/degaussing. Eugene plans to be present as the beamline expert. 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 at the viewer. Eugene plans to be present as the beamline expert. Trigger validation: The trigger experts, Valery and Rafo, need to be notified before starting this run. Then, call MCC, ask for 35 nA, and take 4 hours (read the N.B. below) LD2 target run with a 30 kHz random trigger to validate the electron trigger. Please note that a 4-h-long run is needed while the BEAM is ON; thus, adjust the end-of-run accordingly to account for any beam trips and hiccups: DAQ Config.: PROD66_PIN Trigger file: rgd_v1.0_30kHz.trg. Follow the DAQ instructions below to load a new trigger file. N.B.: We need to test during this run a different BMT config; thus, after taking beam-on-data for 3h45min, the SVT/MVT experts will load a new BMT configuration with 16 samples, then start a new random trigger run to complete the remaining 15-min-BEAM-ON-data with such a configuration. The SVT/MVT experts, Yuri or Rafo, need to be called while approaching the 3h45min end-of-run to be ready to reconfigure their BMTs. P.S.: Before the random trigger run ends, please call the SVT/MVT experts, Yuri or Rafo, to prepare for their MVT bias and SVT ADC threshold studies during the next 1-hour-long LD2 run.-------- If everything goes well, that should bring us to the Swing shift ------- The trigger experts, Valery and Rafo, need to be notified before starting this run. Take a one-hour-BEAM-ON LD2 run with no-DC-roads e- trigger @ 35 nA to validate the trigger roads. DAQ Config.: PROD66_PIN Trigger file: rgd_v1.0_no_DC.trg. 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. DC HV Scan, TOF Gain and ECAL Calibrations: All runs will be taken with the e- trigger with no-DC-roads until the trigger roads are validated by the trigger team.. DAQ Config.: PROD66_PIN Trigger file: rgd_v1.0_no_DC.trg. Follow the DAQ instructions below to load a new trigger file. Ask MCC for 45 nA beam current and take (approximately 5 hours?) LD2 runs with 4 DC HV settings. A total of 120 M electron triggers is needed for this study: two HV settings with 50 M each and the other two with 10 M each. More information can be found at [1] Florian needs to be called to change the DC HV and confirm the statistics needed. P.S.: During the DC HV scan runs, please call the SVT/MVT experts, Yuri or Rafo, to perform their CVT bias scans. Parasitically, 50 M electron triggers are needed for the TOF gain calibration. Parasitically, the same data can be used to conduct a linearity study for the new ECAL PMTs. Take a 1.5-hour run with just EPICS, no DAQ. Florian needs to be notified to be present in the CR during this run (This could be done whenever it's convenient for Florian, even in-between LD2 Lumi. scans).-------- If everything goes well, that should bring us to the Owl shift ------- Saturday, Sept. 30th: LD2 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 and the same electron trigger without DC roads: DAQ Config.: PROD66_PIN Trigger file: rgd_v1.0_no_DC.trg. P.S.: Before starting each luminosity scan run, please call the SVT/MVT experts, Yuri or Rafo, to check the HV setting of MVT. Also, keep an eye on the DC occupancy on mon12 and refresh it frequently during the Lumi. scan runs. Ask MCC for 5 nA and take a 5 M triggers run. Ask MCC for 20 nA and take a 5 M triggers run. Ask MCC for 35 nA and take a 15 M triggers run. Ask MCC for 50 nA and take a 15 M triggers run.-------- If everything goes well, that should bring us to the Day shift------- Two high-current runs for AI training purposes: Ask MCC for 75 nA and take a 50 M triggers run. Ask MCC for 100 nA and take a 50 M triggers run. 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! Once done, continue LD2 data-taking with 35 nA (check with RC/AC after Lumi. scan is done), and 100 M triggers runs until the end of the Day shift, but change the DAQ configuration to: 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 Swing shift ----- Continue LD2 data-taking with 35 nA and 100 M triggers runs until the end of the Swing shift with the PROD66 DAQ configuration and rgd_v1.0_no_DC.trg trigger file. Parasitically, a scan of the RICH threshold should be performed based on Valery/Marco M.'s instructions. Once done, the RICH setting can be reverted to the nominal setting.-----If everything goes well, that should bring us to the Owl shift ----- Sunday, Oct. 1st: Continue LD2 data-taking with 35 nA and 100 M triggers runs until the end of the Owl shift with the PROD66 DAQ configuration and rgd_v1.0_no_DC.trg trigger file. Target Changeover: Denny/Xiaodong 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.---If everything goes well, that should bring us to the Day shift --- Once the access is done, put the flag assembly in the CxC target configuration, then ask MCC for 30 nA and take a 1/2h-BEAM-ON run as follows: DAQ Config.: PROD66_PIN. Follow the DAQ instructions below to change its configurations. Trigger file: rgd_v1.0_no_DC.trg. Solid-target, CxC Configuration, Luminosity Scan: P.S.: Before starting each luminosity scan run, please call the SVT/MVT experts, Yuri or Rafo, to check the HV setting of MVT. Also, keep an eye on the DC occupancy on mon12 and refresh it frequently during the Lumi. scan runs. Ask MCC for 10 nA and take a 5 M triggers run. We will scan three beam currents in this 5 M triggers run. Ask MCC for 20 nA, take roughly 1.5 M events, monitor the DC occupancy in mon12, then increase the current to 35 nA for another 1.5 or 2 M events, refresh mon12 and monitor the DC occupancy, and then increase the current to 45 nA for the last 1.5 M events while monitoring the DC occupancy in mon12. Next, we will scan much higher beam currents in the last 5 M triggers run with this target. Ask MCC for 50 nA, take roughly 1.5 M events, monitor the DC occupancy in mon12, then increase the current to 75 nA for another 1.5 or 2 M events, refresh mon12 and monitor the DC occupancy, and then increase the current to 90 nA for another 1.5 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 30 nA (check with RC/AC after Lumi. scan is done) and take 100 M electron triggers runs with CxC target until the end of the Day shift, but change the DAQ configuration as follows: 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 Swing shift----- Continue CxC data-taking with 35 nA and 100 M triggers runs until the end of the Swing shift with the same PROD66 DAQ configuration and rgd_v1.0_no_DC.trg trigger file.---If everything goes well, that should bring us to the Owl shift--- Monday, Oct. 2nd: Continue CxC data-taking with 35 nA and 100 M triggers runs until the end of the Owl shift with the same PROD66 DAQ configuration and rgd_v1.0_no_DC.trg trigger file.---If everything goes well, that should bring us to the Day shift--- Solid-target, CuSn Configuration, Luminosity Scan: P.S.: Before starting each luminosity scan run, please call the SVT/MVT experts, Yuri or Rafo, to check the HV setting of MVT. Change the flag assembly setup to the CuSn target configuration and perform its luminosity scan with the following configuration: DAQ Config.: PROD66_PIN. Follow the DAQ instructions below to change its configurations. Trigger file: rgd_v1.0_no_DC.trg. Ask MCC for 90 nA and take a 5 M triggers run. We will scan three beam currents in this 5 M triggers run. Ask MCC for 110 nA, take roughly 1.5 M events, monitor the DC occupancy in mon12, 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 the DC occupancy in mon12. 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) and take 100 M electron triggers runs of CuSn until the end of the Day 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 Swing shift--- Continue CuSn data-taking with 130 nA and 100 M triggers runs until the end of the Swing shift.-----If everything goes well, that should bring us to the Owl shift---- Plans may change but assuming the MCC MD will be on Tuesday, Oct. 3rd, Denny/Xiaodong should be called ahead of time to ensure that the controlled access to change the target back to the LD2 position will be done within 1/2h while the target is being filled with LD2. P.S.: Please check with Eugene when he could come to ramp down the torus and solenoid magnets as a preparation for the alignment run. Tuesday, Oct. 3rd: Once the access is done, please ask MCC for 35 nA and take 100 M triggers runs with LD2 for a couple of hours with the same PROD66 DAQ configuration and rgd_v1.0_no_DC.trg trigger file until the time of the alignment run. Once ready for the alignment run, call Xiaodong or follow instructions to boil off LD2. Ask MCC for 1 nA, and take 10 M electron triggers run with zero-field, empty target, and the following electron trigger file based on CTOFxCND coincidence with no-DC-roads: DAQ Config.: PROD66_PIN. Follow the DAQ instructions below to change its configurations and load new trigger files. Trigger file: rgd_v1.0_zero.trg.-----If everything goes well, that should bring us to the Day shift ----- MCC maintenance/beam studies during the day shift (TBC)! After establishing the beam in the swing shift on the outbending configuration, take first a Moller run. Take another 50 M triggers run with LD2 for the ECAL calibration upon Cole's request: 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: TBD. 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_v1.0_no_DC.trg with no-DC-roads for the first commissioning studies while e- trigger is being validated. 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 (to-be-changed for RG-D) Upstream: 5 Hz Midstream: 2 kHz Downstream: 10 kHz BOM: 1 MHz 5 ms dwell time Harp Scan References from RG-C (to-be-changed for RG-D) 2H01 [2] 2C21 [3] Tagger [4]

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