Template:ShortTermSchedule-RGD

Run Coordinator: Susan Schadmand (757) 575-7540 (or 757-223-6213)

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.

◊ For the required controlled access to change the LD2 and solid targets position down in the hall, please refer to this logbook entry #: 419613 for its requirement.

◊ Do NOT change FSD settings without approval from RC or beamline expert!

Run Plan for Oct. 11th to Oct. 13th, 2023 Thursday, Oct. 12th, Day/Swing Shift: • As soon as the MCC is ready to send the beam, please call Eugene. Please follow the steps to establish the beam to tagger dump, energize the tagger magnet, and take a harp scan in 2C21 and 2C24 using 5 nA beam current, then Eugene will take a Møller run with a 1/2-wave plate out. • Next, the collimator needs to be moved to a 20 mm position, mask beam halos, and send the beam to FC, then take a harp scan in 2H01 and compare their results with the reference one at the bottom of this page. • If everything is fine, we will fill LD2 with beam OFF, then proceed with the trigger validation and ECAL calibration run for this outbending configuration. Ask MCC for 35 nA and take 50 M triggers run 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. • Once done, we will switch to the outbending production mode for LD2 @ 50 nA by taking 100 M runs with the following configuration: - DAQ Config.: PROD66. Follow the DAQ instructions below to change its configurations and load new trigger files. - Trigger file: rgd_v1.0_no_DC.trg. -----If everything goes well, that should bring us to the Swing/Owl shift---- Friday, Oct. 13th, Owl Shift: • Continue the LD2 outbending production with 50 nA and 100 M runs by using the following configuration: - DAQ Config.: PROD66. Follow the DAQ instructions below to change its configurations and load new trigger files. - Trigger file: rgd_v1.0_no_DC.trg. -----If everything goes well, that should bring us to the Owl shift---- Friday, Oct. 13th, Day Shift: • Depending on the status of the run during the shift changeover, please end the run once it reaches 100 M, then start the RICH threshold scans. • Please ask MCC for 35 nA and take three 1h 30min runs with BEAM-ON and the following DAQ configuration and trigger files : - DAQ Config.: PROD66_PIN. Follow the DAQ instructions below to change its configurations and load new trigger files. - Load the trigger file: rgd_v1.0_no_DC_RICH_50.trg for the first 1h 30min BEAM-ON run, - Load the trigger file: rgd_v1.0_no_DC_RICH_100.trgfor the second 1h 30min BEAM-ON run, - Load the trigger file: rgd_v1.0_no_DC_RICH_200.trgfor the third 1h 30min BEAM-ON run. • P.S.: While approaching the end of the 3rd run (at least 1/2h before its end), please contact the SVT/MVT experts, Yuri and Rafo, to keep an eye on MVT during the next Lumi. scans runs. Also, please watch the DC occupancy on mon12 and refresh it frequently during the Lumi. scans. ‡ Ask MCC for 20 nA and take a 10 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 55 nA and take a 25 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. ‡ Ask MCC for 75 nA and take a 25 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. • Once done, continue the LD2 outbending production with 50 nA and 100 M runs by using the following configuration: - DAQ Config.: PROD66. Follow the DAQ instructions below to change its configurations and load new trigger files. - Trigger file: rgd_v1.0_no_DC.trg. -----If everything goes well, that should bring us to the Swing shift---- Friday, Oct. 13th, Swing Shift: • Continue the LD2 outbending production with 50 nA and 100 M runs by using the following configuration: - DAQ Config.: PROD66. Follow the DAQ instructions below to change its configurations and load new trigger files. - Trigger file: rgd_v1.0_no_DC.trg. -----If everything goes well, that should bring us to the Owl shift---- Saturday, Oct. 14th, Owl Shift: • Continue LD2 outbending production with 50 nA by taking 100 M runs with the following configuration: - DAQ Config.: PROD66. Follow the DAQ instructions below to load new trigger file. - Trigger file: rgd_out_v1.0.trg. -----If everything goes well, that should bring us to the Day shift---- P.S.: At 7:30 AM, please call the engineering-on-call to inform him that we want to change the target position downstairs to the solid target position by the end of this run, and thus, we need him to come for controlled access. Don't end the run even if it exceeds 100 M until the engineer arrives. -----If everything goes well, that should bring us to the Day shift---- Saturday, Oct. 14th, Day Shift: • In parallel with controlled access, empty the cryo-target cell and insert CxC solid target in the beamline from the drop menu in the cryo-target GUI. For more details, please refer to the cryo-target and flag assembly: manual. • Ask MCC for 50 nA and start CxC outbending production of 100 M runs with the following configuration: - DAQ Config.: PROD66. Follow the DAQ instructions below to change its configurations. - Trigger file: rgd_out_v1.0.trg • Continue CxC production for the next couple of days as mentioned above until otherwise instructed! • 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 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. 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.