Template:ShortTermSchedule-RGK

From clas12-run
Jump to navigation Jump to search

Experiment Coordinator: Annalisa D'Angelo

Run Coordinator: Susan Schadmand (757) 575-7540

PDL: Daniel Carman (757) 876-1789; Office: x5586

Daily RC Meetings

Important Notes

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

In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House and inform the Crew Chief and RC.

In case of evacuation of the Counting Room (e.g., due to a fire alarm), grab the shift expert phone and leave the room through the "EXIT" door leading to the parking lot. Do not leave through the hallway! Call the RC once outside so the latter will call MCC to turn the beam OFF to Hall B and inform other Hall B staff members.

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 "Shift Worker" tab, as you need some lead time to set up!

Note to Shift Takers:

  • Read the ESAD, COO, RSAD, and ERG documents found on the "Current RG-K Run Info" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.
  • Read at least the previous 24 hours logbook entries to be aware of recent run details and changes
  • Arrive at least 10 minutes early for shift change
    • If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.
  • Refresh the run wiki page/tabs; look over it/them every shift
  • Follow the Shift Expert/Worker tab's instructions
  • Do not spend more than 15-20 min trying to fix a problem. In case of any issue, contact the On-call Experts or the RC.

See tab GENERAL INFORMATION for

  • Recent Changes
  • Current Issues
  • Beam Restoration (for beam restoration procedures and Møller runs)

Short Term Plan Feb. 7 - 8, 2024

Beam Restoration

  • Tune beam to tagger yoke dump at 5 nA
  • Take Moller run at 20 nA
  • Tune 5 nA beam to Faraday cup

Empty Target Run

  • Ramp beam up to 150 nA and check halo monitors (screen shots of Beamline overview) at 50 nA, 100 nA, 150 nA
  • If beam is good, turn off beam, insert beam blocker, ramp beam up to 200 nA
- DAQ configuration: PROD67
- Trigger: rgk_noDC_empty_v1.1_300MeV.trg
  • Take 10 M triggers
  • post online reconstruction plots in logbook
  • Turn off beam, remove beam blocker
  • Fill LH2 target

Luminosity scan

  • DAQ configuration: PROD67
  • Beam current requests and Trigger files
    • 5 nA and rgk_5nA_noDC_v1.1_300MeV.trg
    • 15 nA and rgk_15nA_noDC_v1.1_300MeV.trg
    • 30 nA and rgk_30nA_noDC_v1.1_300MeV.trg
    • 45 nA and rgk_45nA_noDC_v1.1_300MeV.trg
  • Run duration: 10M triggers for each beam current
  • Continue production running for the rest of the night, if possible. See below for Production running conditions


Feb 8, 2024 / daytime Trigger run

  • Take data without HTCC in the trigger
- DAQ configuration: PROD67
- Trigger: rgk_noHTCC_noDC_v1.1_300MeV.trg
  • Beam current request: TBD
    • adjust beam current to give bit #0 trigger rate = 25 kHz) - call Valery to check trigger setup and beam current choice
  • Run duration: 2 hrs
Production running conditions
- DAQ configuration: PROD67
- Trigger: rgk_noDC_v1.1_300MeV.trg
- Beam current request: 65 nA
- Run duration: 3 hrs
- DAQ livetime ~90%
- R1 DC occupancy <5%


Related Information

Find detailed information at tab "GENERAL INFORMATION".

  • The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF during run time.
  • Orbit locks are on BPMs 2C24A and 2H01 and the locks should generally be on ("Running").
    • Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
  • The beam position at 2C21A is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.
    • The beam position at 2C21A is important for initial beam tuning (on tagger dump).
  • If HWP is changed, start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.
  • Beam tuning and Møller runs
    • Generally, Detector HV OFF but
    • SVT: LV ON; HV OFF, and MVT: LV ON; HV ON - Safe Voltage
    • Turn DC HV off only for beam tuning

Access to the Hall

  • If you need to enter 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.

DAQ Operation & Related Information

NEW STANDARD end and start of the run:

- "End run"
- "Cancel"
- "Reset"
- "Download"
- "Prestart"
- "Go"

This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.

Restart DAQ

-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:
- "Cancel"
- "Reset"
- "Configure"
- "Download"
- "Prestart"
- "Go"
  • Restart DAQ: ensure that each step is completed in the Run Control message window. During "Configure", look for error messages in the ROC terminals.
  • Some ROCs keep printing error messages while functioning properly, see logbook entry # 4215299 .
  • If a ROC is disconnected, the message will appear in the run control message window.
  • If a ROC has crashed.
    • Find out which one (look for busy ROCs)
    • End the current run
    • Issue a roc_reboot command ON JUST THAT ROC
    • PING the ROC to check that it is back up (some take longer than others)
    • Restart DAQ
  • Pop-up window: Enter the beam current and the type of run in the "Comment" field.
  • At the start and end of a run, check that the data in the Run Condition Data Base (RCDB) is correct, especially the manually filled fields.
  • Check and reset monitoring histograms every hour. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.
  • In case of DAQ Disk space alarm, call the DAQ expert.
  • Contact the DAQ expert if you have any questions or doubts about how to proceed.

Triggers files

rgk_noDC_v1.0_300MeV.trg DC roads are not in the trigger. Hold off time is 3 us.
rgk_noDC_v1.1_300MeV.trg DC roads are not in the trigger. Hold off time is 2 us.
rgk_noDC_v1.2_300MeV.trg DC roads are not in the trigger. Hold off time is 1 us.
rgk_out_v1.1_300MeV.trg Outbending DC roads, Hold off time is 2 us.

Reference Values

FSD Thresholds

  • Upstream: 2 kHz
  • Midstream: 2 kHz
  • Downstream: 100 kHz
  • BOM: 50 kHz
  • 5 ms dwell time

Nominal Beam Positions

2C24A

  • x = -1.7 mm
  • y = +0.5 mm

2H01

  • x = -0.7 mm
  • y = +0.6 mm

2C21A (not important for production)

  • x = -0.4 mm
  • y = +0.7 mm

Harp Scan References

Tagger (2C24A): Jan. 18, 2024, https://logbooks.jlab.org/entry/4240378

2H01: Jan. 18, 2024, https://logbooks.jlab.org/entry/4240397

2C21A: Jan. 18, 2024, https://logbooks.jlab.org/entry/4240375

Retrieved from "https://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&oldid=7227"