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

Run Plan for Oct. 4th to Oct. 8th, 2023 Wednesday, Oct. 4th: • Trigger validation: Ongoing in the Day Shift ‡ The trigger experts, Valery and Rafo, need to be notified before starting this run. Then, call MCC, ask for 35 nA, and take a 4-hour-long (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 and Rafo, need to be called (at least 30 min in advance) while approaching the 3h45min end-of-run to be ready to reconfigure their BMTs. ‡ P.S.: Before the random trigger run ends, please call (at least 30 min in advance) the SVT/MVT experts, Yuri and Rafo, to prepare for their MVT bias, and SVT ADC threshold studies during the next one-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_35nA.trg. Follow the DAQ instructions below to load a new trigger file. • 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_35nA.trg. Follow the DAQ instructions below to load a new trigger file.If everything goes well, that should bring us to the Owl shift ------- ‡ Ask MCC for 35 nA beam current and take a few LD2 runs with 4 DC HV settings. A total of 180 M electron triggers is needed for this study: two HV settings with 75 M each and the other two with 15 M each. More information can be found at DC HV scan. Florian needs to be called to change the DC HV after the first 75 M run with the default current setting (R1/R2/R3: 10/10/10 V; see the first table for HV study setting in DC HV scan). ‡ P.S.: During the DC HV scan runs, please call (at least 30 min in advance) the SVT/MVT experts, Yuri and Rafo, to perform their CVT bias scans. ‡ Parasitically, 75 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.--------If everything goes well, that should bring us to the Owl shift ----- • Since the MCC Beam Studies is planned for Thus., Oct. 5th, please call Eugene to ramp down the torus and solenoid magnets as a preparation for the alignment run. In parallel, the LD2 target needs to be emptied with a beam OFF. Also, there is a plan for Yuri and Rafo to perform controlled access for SVT and FMT crates power-cycling during this process. • Once ready for the alignment run, ask MCC for 1 nA, and take 10 M electron triggers run (keep an eye on the FD trigger rates to ensure that) 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! Thursday Swing Shift, Oct. 5th: • LD2 Luminosity Scan: ◊ After establishing the beam in the swing shift on the inbending configuration, take first a Møller run. ◊ Next, perform a series of runs for TOF/ECAL linearity and AI training with the following beam currents and the specified trigger files but with the same DAQ configuration: - DAQ Config.: PROD66_PIN - Trigger file: rgd_v1.0_no_DC_5nA.trg. Follow the DAQ instructions below to load a new trigger file. ‡ P.S.: Before starting each luminosity scan run, please call (at least 30 min in advance) the SVT/MVT experts, Yuri and 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 with the following trigger file: - Trigger file: rgd_v1.0_no_DC_20nA.trg. Follow the DAQ instructions below to load a new trigger file. ‡ Ask MCC for 35 nA and take a 15 M triggers run with the following trigger file: - Trigger file: rgd_v1.0_no_DC_35nA.trg. Follow the DAQ instructions below to load a new trigger file. ‡ Ask MCC for 50 nA and take a 15 M triggers run with the following trigger file: - Trigger file: rgd_v1.0_no_DC_50nA.trg. Follow the DAQ instructions below to load a new trigger file. -------- If everything goes well, that should bring us to the Owl shift------- Friday, Oct. 6th: ◊ Two high-current runs for AI training purposes: ‡ Ask MCC for 75 nA and take a 50 M triggers run with the following trigger file: - Trigger file: rgd_v1.0_no_DC_90nA.trg. Follow the DAQ instructions below to load a new trigger file. ‡ Ask MCC for 100 nA and take a 50 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. 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! ◊ Parasitically, a 1.5-hour run with just EPICS, no DAQ, can be taken in blocks in between the luminosity runs. List of points at Overview Table. Florian needs to be notified to be present in the CR during this run. ◊ Parasitically to the EPICS run, 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. The process should take 5 to 7 min at max. ◊ 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 Owl shift, but start performing the RICH Threshold scan as follows, assuming all other detectors are at their nominal settings, please check with the RC/AC: - Load the trigger file: rgd_v1.0_no_DC_RICH_50.trg; Follow the DAQ instructions below to load a new trigger file, and take a 100 M run; - Load the trigger file: rgd_v1.0_no_DC_RICH_100.trg; Follow the DAQ instructions below to load a new trigger file, and take a 100 M run; - Load the trigger file: rgd_v1.0_no_DC_RICH_200.trg; Follow the DAQ instructions below to load a new trigger file, and take a 100 M run;-----If everything goes well, the Day shift should start somewhere in-between the RICH scan runs! ----- ◊ Whenever the RICH scan is done, continue LD2 data-taking with 35 nA and 100 M triggers runs until the end of the Day shift but change the DAQ/trigger 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 ----- P.S.: Both Denny and Xiaodong must be notified ahead of time (at least 1/2h) to inform them about performing access to change the target position to the solid-foil position as well as emptying the target in parallel! • Solid-target, CxC Configuration, Luminosity Scan: ◊ P.S.: Before starting each luminosity scan run, please call (at least 30 min in advance) the SVT/MVT experts, Yuri and 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 with the following trigger file: - Trigger file: rgd_v1.0_no_DC_10nA.trg. Follow the DAQ instructions below to load a new trigger file. ‡ 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 30 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, but with the following trigger file: - Trigger file: rgd_v1.0_no_DC_30nA.trg. Follow the DAQ instructions below to load a new trigger file. ‡ Once done, take a 15 M run @ 30 nA with the same trigger file and DAQ configuration. ‡ 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, but with the following trigger file: - Trigger file: rgd_v1.0_no_DC_50nA.trg. Follow the DAQ instructions below to load a new trigger file. 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. ‡ Depending on the stability of detectors in the last higher beam currents run, we can take a 25 M run @ 50 nA. • 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 Swing shift, but change the DAQ/trigger 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 Owl shift----- Saturday, Oct. 7th: • Continue CxC data-taking with 30 nA (TBD after Lumi. scan) 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 (at least 30 min in advance) the SVT/MVT experts, Yuri and 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 specified trigger files but with the same DAQ configuration: - DAQ Config.: PROD66_PIN. Follow the DAQ instructions below to change its configurations. ‡ Ask MCC for 90 nA and take a 5 M triggers run with the following trigger file: - Trigger file: rgd_v1.0_no_DC_90nA.trg. ‡ 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, 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. ‡ Once done, take a 25 M run @ 130 nA with the same trigger file and DAQ configuration. ‡ 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. ‡ Depending on the stability of detectors in the last higher beam currents run, we can take a 25 M run @ 150 nA. • Once done, ask for 125 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 125 nA (TBD after Lumi. scan is done) and 100 M triggers runs until the end of the Swing shift.-----If everything goes well, that should bring us to the Owl shift---- Sunday, Oct. 8th: • Continue CuSn data-taking with 125 nA (TBD after Lumi. scan is done) and 100 M triggers runs until the end of the Owl shift. -----If everything goes well, that should bring us to the Day shift ----- • Please call Eugene to change the torus polarity to the outbending configuration. In parallel, Denny/Xiaodong should be called so Denny 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 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: 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: 100 kHz 5 ms dwell time Harp Scan References from RG-D 2H01 [1]; x= -1.4 mm; y= +1.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.