Run Plan for Oct. 8th to Oct. 9th, 2023
- Sunday, Oct. 8th, Swing Shift:
- • If the controlled access is done and the beam is back, please ask MCC for 130 nA and take one 100 M production run of the CuSn target with the following configuration:
- - DAQ Config.: PROD66. Follow the DAQ instructions below to change its configurations.
- - Trigger file: rgd_v1.0_no_DC.trg.
- • Since the beam is OFF for RF recovery, the two high beam current runs are postponed until tomorrow morning; thus, we will continue CuSn data-taking with 100 M production runs @ 130 nA and the following DAQ and trigger configurations until the end of the Swing shift:
- - 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---
- Monday, Oct. 9th, 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 the CxC target with beam OFF by changing the solid target 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, then take 100 M production runs with CxC until the end of the Owl 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---
- Monday, Oct. 9th, Day Shift:
- • It depends on the run status at the shift changeover, but in case it's not ended, please continue the run until it reaches 100 M with CxC target, then switch to the CuSn target with beam OFF by changing the solid target from the drop-menu in the cryo-target GUI. For more details, please refer to the cryo-target and flag assembly: manual.
- • 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 @ 175 nA with the same DAQ and trigger configurations.
- • Once done, continue CuSn data-taking of 100 M production runs with 130 nA and the following DAQ and trigger configurations until the end of the Day shift:
- - 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---
- Monday, Oct. 9th, Swing Shift:
- • 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:
- Tagger (2C24A [3]; x= -2.0 mm; y= +0.6 mm
IA for Q Asymmetry
|
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).
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.
|