Run Group E

From clas12-run
Revision as of 07:33, 16 April 2024 by Hayk (talk | contribs)
Jump to navigation Jump to search
[edit]
Role Phone Number
Hall B Run Coordinator (757) 575-7540 (cell)
Hall B Physics Division Liaison (757) 876-1789 (cell)
MCC 7048
Crew Chief 7045
Crew Chief (757) 876-3367 (cell)
Program Deputy (757) 876-7997 (cell)
RadCon (757) 876-1743 (cell)
Gate House Guard 5822
Location Phone Number
Hall B Floor 5165
Hall B Space Frame 5170 and 5171
Hall B Forward Carriage 5371
Hall B Gas Shed 7115
Hall B Counting House 5244 (Shift Expert)
Hall B Counting House (757) 329-4846 (Shift Expert cell)
Hall B Counting House 5245 or 5126 (Shift Worker)
Hall A Counting House 5501
Hall C Counting House 6000
Hall D Counting House 5504
Hall B System Phone Number On-Call Person
Engineering (757) 748-5048 (cell)
(757) 897-9060 (cell)
Engineering On-Call (primary)
Denny Insley (secondary)
Slow Controls (757) 748-6922 (cell) Nathan Baltzell
Beamline (757) 303-3996 (cell) Eugene Pasyuk
DC (757) 218-4372 (cell)
(757) 748-5048 (cell)
Florian Hauenstein (primary)
Engineering On-Call (secondary)
SVT/MVT/MM (757) 541-7539 (cell)
(757) 753-7769 (cell)
Yuri Gotra (primary)
Rafo Paremuzyan (secondary)
ECAL (757) 810-1489 (cell) Cole Smith
FTOF/CTOF/CND (757) 344-7204 (cell) Daniel Carman
ALERT (757) 329-4844 (cell) Raphael Dupré
HTCC/LTCC (757) 344-7174 (cell) Youri Sharabian
FT (757) 344-1848 (cell) Raffaella De Vita
BAND (757) 310-7198 (cell) Florian Hauenstein
RICH (757) 344-3235 (cell)
(757) 748-6922 (cell)
Christopher Dilks (primary)
Nathan Baltzell (secondary)
DAQ (757) 232-6221 (cell) Sergey Boiarinov
HYDRA (317) 550-9226 (cell) Torri Jeske
Authorized Hall B Solenoid/Torus Operators
Hall B Denny Insley, Morgan Cook, Eugene Pasyuk
Magnet Group Probir Ghosha, Renuka Rajput-Ghoshal
Detector Support Group Brian Eng, Pablo Campero, Tyler Lemon
DC Power Onish Kumar, Sarin Philip
  • Note, all non-JLab numbers must be dialed with an area code. When calling from a counting-house landline, dial "9" first.
  • To call JLab phones from outside the lab, all 4-digit numbers must be preceded by 757-269
  • Click Here to edit Phone Numbers. Note, you then also have to edit the current page to force a refresh.

Run Coordinator: Sebouh Paul (757) 575-7540

Current RP Coordinator: Lamiaa El Fassi

PDL: Nathan Baltzell (757) 876-1789, Office: x5902

Daily RC Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1605705819), except on Wednesdays, which is @ 15:00 in CH Room 200C and via the same ZOOM link.

Important Notes

  • In case of medical or fire emergency, call 911 or 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 can call MCC to turn the beam OFF for 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, the RC, and JLab medical services immediately to arrange replacements.
  • In case of a problem with the HV Slow Controls, EPICS in general, please call the primary expert on-call, Nathan Baltzell, before reaching out to anyone else.
  • Please put all essential information on the main Hall B logbook HBLOG. Some important alarms have been documented on HBRUN. Use the pulldown menu to choose where an error is reported.

Current Run Plan: May 18th to May 19th

  • Take production data! Don't break anything!
  • Keep an eye on the backgrounds, such as in the halo counters and the 2C24A and 2H01 BPM positions. Both give confidence that the beam remains centered on the RG-E target.
  • If you need to manipulate the whole target system - cryo-target or solid - please contact the target experts.

Outbending Configuration Runs

• Beam Blocker: IN
• Beam Current: 70 nA
• Target: LD2+Pb
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_noDC_v1.0_300MeV.trg
• 3-hour or 100 M events run, whatever comes first!


Previous Dual-target Configuration Plans

- DC firmware test plan (LD2+Pb):

1) Take one run each with 1M events with the trigger files and beam current at 70 nA

  • rge_inb_v1.0_200MeV_dcrb17_1.trg : DCRB Threshold (30, 45, 45 nA)
  • rge_inb_v1.0_200MeV_dcrb17_4.trg : DCRB Threshold (30, 60, 45 nA)
  • rge_inb_v1.0_200MeV_dcrb17_3.trg : DCRB Threshold (45, 60, 60 nA)
  • rge_inb_v1.0_200MeV_dcrb17_2.trg : DCRB Threshold (30, 30, 30 nA)

2) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_2.trg

3) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_4.trg

• Before the last run, call DC expert Florian so that he can change the firmware after the last run is finished.

*** Notes ***

• In every step, follow DAQ procedure (End run, Cancel, Reset, Configure, Download, Prestart, Go)
• For every run please log clas12mon plots from the special version at /usr/clas12/offline/clas12mon/dcrb/bin/mon12

LD2+Pb runs

  • Trigger: rge_inb_v1.0_200MeV.trg
  • Beam Current: 70 nA
  • Use PROD67 configuration (this will not PIN data)
  • 3-hour runs

LD2+Sn runs

  • Trigger: rge_inb_v1.0_200MeV.trg
  • Beam Current: 65 nA
  • Use PROD67 configuration (this will not PIN data)
  • 3-hour runs

LD2+Al runs

• Beam Blocker: IN
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Beam Current: 70 nA
• 3-hour runs

Lumi Scan for LD2+Al on May 15th

• Beam Blocker: OUT
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Take one 5 nA run for 4 hours w/. beam ON
• Take one 10 nA run for 6 hours w/. beam ON
• Take one 20 nA run for 3 hours w/. beam ON
• Take one 45 nA run for 3 hours w/. beam ON

Lumi Scan for LD2+Pb on May 15th - 16th

• Beam Blocker: OUT
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Take one 5 nA run for 4 hours w/. beam ON
• Take one 10 nA run for 3 hours w/. beam ON
• Take one 20 nA run for 3 hours w/. beam ON
• Take one 40 nA run for 3 hours w/. beam ON
• Take one 55 nA run for 3 hours w/. beam ON

Streaming Readout Test

• Performed in coordination with Sergey and David Lawrence (Done from 9 to 11 a.m. on May 16th).

Empty-target runs on May 16th - 17th

• Beam Blocker: IN
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Take one Empty+Al run @ 70 nA w/. BB for 5 hours (w/. Beam ON)
• Take one Empty+Wire run @ 200 nA w/. BB for approx. 8 hours (BB calibration is done by Rafo and Lamiaa/MCC OPS over phone)

Outbending Configuration Runs on May 17th - 19th =

• Beam Blocker: IN
• Beam Current: 70 nA
• Target: LD2+C
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_noDC_v1.0_300MeV.trg, or
♦ Trigger: rge_noDC_v1.0_200MeV.trg, and Beam Current: 60 nA or
♦ Trigger: rge_noDC_v1.0_250MeV.trg, and Beam Current: 65 nA
• 3-hour or 100 M events run, whatever comes first!

References

- BPM Positions

  • The most important BPMs to monitor are 2C24A and 2H01, from the point of view of assuring the beam remains centered on the RG-E target. Other steering/focusing beamline elements can influence the values of the others.
BPM 2C21A 2C24A 2H01
X (mm) -0.4 -1.7 -1.0
Y (mm) +0.7 +0.5 +0.25

- Harp Scans

- FSD Thresholds

  • Do NOT change FSD settings without approval from RC or beamline expert!
• Upstream: 2 kHz
• Midstream: 3 kHz
• Downstream: 150 kHz
• BOM: 50 kHz
• 5 ms dwell time

- Charge Asymmetry

- Upstream Halo counters

  • If the reading on the upstream halo counters exceeds 10, please contact MCC.

General Reminders

  • The main lights in the Hall and the Forward Carriage lights must be kept off during data taking.
• Refer to these reference photos, ON and OFF
• The main, dome lights can be turned off without entering the Hall.
  • Beamline
• Do not run over 30 minutes above 90 nA (50 nA for now while studying FCup behavior) with a 5-pass beam without the beam blocker IN.
• If there is any concern about beam stability, ask MCC if orbit locks are on (they should be).
• Document any beam condition change and send scaler GUIs to HBLOG.
• If HWP is changed, start a new run.
  • During beam tuning and Møller runs
• DC: HV OFF
• SVT: LV ON, HV OFF
• MVT: LV ON, HV ON in SAFE Mode
• All CLAS12 detectors should be OFF; aforementioned tracking detectors are the most critical.
  • To access the Hall
• If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator.
• Check in with the shift personnel before entering the hall.


DAQ Operation

  • Standard end and start of a run
    1. End run
    2. Abort
    3. Download
    4. Prestart
    5. "Go"
  • Restart DAQ from scratch
• E.g., when changing configuration or trigger files, when the run did not end correctly, or after ROCs are rebooted
  1. Cancel
  2. Reset
  3. Configure
  4. Download
  5. Prestart
  6. Go
  • DAQ instructions
• Please make a log entry (logbook RICH, notify vpk@jlab.org) with RICH temp and scalers screenshots when you have RICH problems.
• You do not need to stop the run each time you get 1-2 dead tiles if DAQ is still working. Continue data taking. When you start a new run, the dead tiles will recover without your intervention during DAQ Prestart with a high probability. If you still have problems, make a full RICH recovery and call Valery #5647.


Responsibilities

  • The RC duties are detailed in the COO.
  • Check and contact, if needed, upcoming shifts about their training or site access status.
  • The training requirements for the shift are:
- ES&H Orientation (SAF 100);
- Radiation Worker Training (SAF 801);
- Oxygen Deficiency Hazard Training (SAF 103);
- Hall B Safety Awareness Walk-Through (SAF111)
  • Remote shifts are listed here.
  • Backup shifters are listed here.

Daily

  • Attend the in-person PD/RC and MCC/OPS meetings (7:45 AM and 8 AM Daily). The PD will communicate when and how meetings happen on the weekend.
- See the ZOOM connection info under Important Links tab.
  • Update the run plan in the Short Term Schedule tab in coordination with the run group coordinator and communicate it to the shift crew.
  • Log a daily RC summary in HBLOG and send a daily invitation for the RC meeting to hallb@jlab.org and clas_members@jlab.org
  • Run the daily RC meetings at 1 PM in CH Room 200C and on ZOOM, except on Wednesdays.
- On Wednesdays, the RC meeting is on ZOOM ONLY @ 15:30 due to the conflict with the 13:30 MCC meeting and the unavailability of the CH room afterwards.
  • To connect to Zoom in CH Room 200C, follow these steps:
- Turn on the projector with the white remote control, then log into your CUE account. If not listed yet, click "Not listed?" in the bottom left to add your account.
- Once logged in, use the recommended Google Chrome to join the ZOOM meeting on the browser or use the ZOOM application.
- Since the room doesn't have audio, don't connect with the computer audio, but choose "Call Me," then enter the number in the small Cisco answering device near the microphone in the middle of the conference table. Once it rings, answer the call, and you will be prompted to join the meeting.
- The room has a camera, so you may turn it on, if you wish, in the ZOOM browser interface.

Weekly

- The report summarizes the data-taking status concerning the available beam used (ABU), any beam losses (BANU), CW on target (ABU+ABNU), etc., from 7 AM past Wed. through 7 AM the Wednesday the report is due, in addition to any standing and critical issues, plans for next week, and general comments/requests, if any.
- Our beam time accounting info can be retrieved either from:
- OPS logbook entries with tag 'Beam Accounting': Timesheet Summaries;
- Beam Time Manager; Physics Time Accounting.
- Refer to the [RC Timesheet] to calculate the percentage of scheduled experiment hours to date.
- The total experiment data collected to date could be retrieved from the up-to-date "Accumulated Charge" depicted on the "Total Charge on Target Plot" in the Monitoring tab.
  • Attend the Hall B meeting on Mondays at 9 AM and present your summary slides.

Tasks

  • Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.
- If it's your first shift or a shift after a long pause, please come at least 4 hours before your shift (or even better, come a day earlier) to shadow the previous shifter and familiarize yourself with all shift duties and technicalities of the ongoing experiment.
- The RC must be notified before changing run conditions.
  • Operate the Data Acquisition.
  • Take action on and log alarms.
  • Communicate with your co-shift person:
- The shift worker should discuss an issue with the shift expert before making extra logbook entries.
- During production, not in extended downtime, the shift expert should ensure the shift worker is filling their end-of-shift Checklist when the beam is ON, not in the period of beam trips.
  • Check for and read any comments to log-book entries made during your shift.
  • Keep your shift summary up to date in HBLOG. Record all shift activities, issues, if any, and related communications with experts with details and/or reference to any associated logbook entries:
- Refer to relevant logbook entries in the shift summary.
- Include a list of runs taken during the shift with relevant run information;
- See, for instance, this shift summary where all relevant run info, links, and shift activities are cited.
  • Ensure that all MON12 monitoring plots are logged and checked against the reference plots for every single run; see the links under Monitoring tab;
- Both, you and the shift worker should run MON12 and reset & check spectra frequently.
  • If you have any other questions or uncertainties about what to do, call the RC.
  • MVT LV Reboot Procedure
    1. Turn LV OFF from MVT Overview->Low Voltage->MVT-All. LV status indicators should change from green to black;
    2. Wait 20 seconds, then turn LV back from the same menu;
    3. In the alarm handler, with a 2-minute alarm delay, there can be alarm NActiveCrates, status also reported on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON;
    4. At this point, mvt1, mvt2, and mvt3 ROCS can be rebooted;
    5. Start a run by initializing DAQ from scratch: cancel-->reset-->configure-->download-->Prestart-->Go.
    6. If the beam is ON, and a reboot process takes more than 5 min, please call the DAQ and/or SVT/MVT/MM expert.

Tasks

  • Come to your shift in time for the shift change, 10-15 minutes before the start of your shift;
- If it's your first shift or a shift after a long pause, please come at least 4 hours before your shift (or even better, come a day earlier) to shadow the previous shifter and familiarize yourself with all shift duties and technicalities of the ongoing experiment.
  • Discuss an issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary and the start/end of run Comment field in the DAQ pop-up window.

Frequently

  • Reset and check MON12 histograms frequently, preferably each 1/2h, during a run:
• Note that some plots have radio buttons at the bottom to choose the sector, so you should cycle through and check all sectors.

Once per run

  • Submit EPICS screenshots with beam ON to the HBRUN logbook
- Beamline overview, in VNC or Web Browser
- CLAS12 trigger rates and DAQ status
  • Upload MON12 monitoring plots to the logbook with sufficient statistics:
- Afterwards, compare them to the reference and recent uploads; see the top-right link at the Monitoring tab.
  • Submit Beam current and position strip charts to the logbook at the end of the run
- If they are not up already: (CS-Studio → Beamline → Strip Charts);
- Choose the 'time-span width' to be compatible with the run duration.

Once per shift

- During production or if the beam is down for your entire shift, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status, and CLAS12 Trigger;
- During extended downtime, get relevant values from the latest EPICS screenshots you made during production.

For Remote Shifts

Please inform the PDL that your shifts will be remote. Remote shifts are listed here

You must test your setup, including Zoom and VNC connections, at least 24 hours before your first shift!

- The passcode is required and contained in this log entry
- Remind the expert in the counting-house to restart their ZOOM, if necessary
- All necessary applications should be available from the desktop menu (left/right click on the desktop)
- EPICS GUIs should be accessed ONLY via the desktop menu or by running clascss-remote.
◊ Some charts are also accessible via web browser: Upstream/Midstream Halo Counters, Downstream Halo Counters, Beam Currents, BPM Positions


Webcams

EPICS

- Accelerator Status
- Strip Charts

Data Quality



Clas12design.png