Difference between revisions of "Run Group E"

From clas12-run
Jump to navigation Jump to search
(Undo revision 7587 by Brooksw (talk))
Tag: Undo
(Undo revision 7587 by Brooksw (talk))
Tag: Undo
Line 134: Line 134:
  
 
|}
 
|}
 +
 +
<!--#######################################  GENERAL INFORMATION  #############################################-->
 +
= General Information =
 +
 +
This tab contains information on
 +
* '''Recent Changes'''
 +
* '''Current Issues'''
 +
*'''Beam Restoration'''
 +
 +
== '''Recent Changes''' ==
 +
 +
=== New '''MVT LV''' Reboot Procedure ===
 +
See '''https://logbooks.jlab.org/entry/4217011''' for detailed information on rebooting the MVT LV when observing a drop in BMT strip occupancies. This gets done upon request of DAQ or MVT expert only.
 +
* Turn '''LV OFF from MVT Overview->Low Voltage->MVT-All'''. LV status indicators should change from green to black;
 +
* '''Wait 20 seconds''', then '''turn LV back from the same menu'''.
 +
* In the alarm handler, with a 2-minute alarm delay, there can be an alarm "NActiveCrates", the status is also seen on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON.
 +
* Reboot mvt1, mvt2, and mvt3 ROCS.
 +
* Start a run with restart DAQ (Cancel &rarr; Reset &rarr; Configure &rarr; Download &rarr; Prestart &rarr; Go).
 +
* '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.
 +
 +
=== RICH issues ===
 +
* The RICH fibers alarm leads to web guidance aka logbook entry [https://logbooks.jlab.org/entry/3562273 3562273 - RICH recovery procedure].
 +
* Check the RICH manual for the current guidance: '''https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf'''
 +
* See below for current issues
 +
 +
=== Rapid/Controlled Access to the Hall ===
 +
* Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.
 +
* After higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.
 +
 +
=== 24/7 ZOOM connection for Counting House ===
 +
* Click on [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab  "Shift Worker"
 +
* choose the option to "'''join from browser'''" (''Chrome is recommended'') and ignore all other messages to update the ZOOM APP in the pop-up windows,.
 +
* Enter the passcode from the logbook entry in tab  "Shift Worker"
 +
 +
== '''Current Issues''' ==
 +
 +
=== Lights in the Hall ===
 +
The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the  detectors. If these lights are switched on during an access, they '''should be switched off when leaving the Hall'''.
 +
* Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]
 +
* We have a '''new dome light switch outside of the hall''' in the labyrinth.  See logbook entry: https://logbooks.jlab.org/entry/4204460
 +
* When the dome lights are switched off, they cannot be turned back on immediately, they require 10-15 min to cool down.
 +
 +
=== Beamline ===
 +
 +
* 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).
 +
*'''After the HWP change'''
 +
** The absolute values of the SLM and FCUP '''charge asymmetry''' (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.
 +
** Start a new run
 +
* '''Tagger Magnet Procedure:''' If the tagger magnet needs to be turned off, tell the operator to '''ONLY''' use '''the script for degaussing, NEVER do it "by hand"!''' The latter method might/will trip the circuit breaker for the power supply in the Hall.
 +
 +
=== BMT / SVT ===
 +
* If new hot channels appear, '''call the SVT/MM expert Yuri Gotra''' (757-541-7539). These channels need to be addressed by the expert.
 +
* '''BMT HV trips''': no screenshots are necessary, power-cycle the channel HV '''as fast as possible''' (the ''underlying script will take care of ramping it up''), note the information in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.
 +
* BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview
 +
* BMT HV S1 L5 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
 +
* BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
 +
 +
=== CND ===
 +
* CAMAC crate alarm:
 +
** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, can be done via the alarm handler.
 +
** After reboot, the CFD thresholds need to be set by running a script, see page 12 in the CND manual at tab "General", https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf
 +
 +
=== DAQ ===
 +
* Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected! 
 +
* <font color=red>'''NEW STANDARD''' end and start of the run:</font> End run, Cancel, Reset, <u> Download</u> , Prestart, Go. This will ensure proper compression of the FADCs and therefore a smaller data rate.
 +
* roc reboot instructions:
 +
** To reboot i.e. adcecal1, type on a clasrun terminal: clasrun> roc_reboot adcecal1
 +
** To check that the crate is back alive, type:clasrun> ping adcecal1
 +
** The ping will start to answer as soon as the crate communicates again.
 +
 +
=== DC ===
 +
* Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.
 +
 +
=== ECAL/PCAL ===
 +
*  "ECAL_SEC6_UO26 Noisy" https://logbooks.jlab.org/entry/4241957
 +
* "PCAL_HV_SEC2_U25 turned off" https://logbooks.jlab.org/entry/4247187, https://logbooks.jlab.org/entry/4247400
 +
 +
=== FTOF ===
 +
* FTOF S2 Paddle 19-left and S4 Paddle 16-left are known to be "weak" channels that tend to come and go depending on torus polarity and rates. This cannot be fixed during this run period; see https://logbooks.jlab.org/entry/4219555 and https://logbooks.jlab.org/entry/4219876.
 +
* "FTOF HV Adjustment - S5 P2 2R" https://logbooks.jlab.org/entry/4249754
 +
 +
=== RICH ===
 +
* '''Known problematic PMTs and tile''':
 +
** You don't need to report about it.
 +
** PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.
 +
** Problematic tiles and PMTs:
 +
*** Sector 1 Tile 21 dead (PMT 55,56,57)
 +
*** Sector 1 Tile 1 PMT 2
 +
*** Sector 4 Tile 34 PMT 92
 +
 +
== '''Beam Restoration''' ==
 +
 +
* Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]. If you do not feel confident to do this by yourself, contact the Beamline Expert.
 +
 +
* Find all Reference values on the white board at tab Short_Term_Schedule
 +
 +
=== Restoring Beam after Short Downtime ===
 +
 +
* Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after 
 +
** beam steering or orbit change
 +
** change in beam current, e.g., after a target change
 +
** If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values
 +
 +
=== Beam Tuning to Tagger Yoke Dump ===
 +
 +
Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam].
 +
* Contact Eugene Pasyuk if issues arise.
 +
 +
* Ask MCC to energize the tagger magnet
 +
:- blank collimator
 +
:- beam type "Photon"
 +
 +
* All CLAS12 detectors HV off (BMT HV in safe mode)
 +
 +
* Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM)
 +
* Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
 +
* If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values
 +
* Take harp scans
 +
:- at Harp 2C21A (Upstream Right Counter)
 +
:- at Tagger Harp 2C24A Upstream Right Counter)
 +
* If the beam trips, abort the scan and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.
 +
* Compare the results with the Harp Scan References 
 +
* The fit ranges might need to be adjusted manually to assess the fit results
 +
 +
* If good, log the new scan results.
 +
 +
=== M&oslash;ller run ===
 +
 +
Follow the standard procedure as described in the manual [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf Performing M&oslash;ller Runs].
 +
* Contact Nathan Baltzell if issues arise
 +
 +
A few points to note:
 +
* '''Request 20 nA''' , Orbit Locks should be off
 +
* The BPMs 2C21 and 2C24A may be out of range after the M&oslash;ller configuration. 
 +
* Keep running until the polarization uncertainty is < 1.5%
 +
 +
=== Beam Tuning to Faraday Cup ===
 +
 +
Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam], and take into account the first steps mentioned therein.
 +
 +
This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
 +
 +
* All CLAS12 detectors HV off (BMT HV in safe mode)
 +
 +
* Ask MCC to de-energize the tagger magnet
 +
:- 20 mm collimator
 +
:- beam type electron
 +
:- beam blocker out
 +
* If initial beam tune, target should be "Empty"
 +
* Ask MCC to unmask beam halos
 +
* Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds
 +
* Insert the Downstream Viewer, Chromax, in the beamline
 +
* Ask MCC for 5 nA beam current
 +
* If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the Reference Values
 +
* Take a harp scan at 2H01 (Midstream Left)
 +
* If the beam trips, abort and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.
 +
* Compare the results with the Harp Scan References
 +
* If good, log the new scan results.
 +
 +
Once done and before resuming the production data-taking:
 +
* Retract the Downstream Viewer from the beamline
 +
* Put the FSDs thresholds and integration time to their reference values
 +
* Turn all detector HV ON, for MVT  "HV ON - Full Voltage"
 +
* MCC might need to adjust the beam positions after going to the production beam current.
 +
 +
  
 
<!--#######################################  GENERAL INFORMATION  #############################################-->
 
<!--#######################################  GENERAL INFORMATION  #############################################-->

Revision as of 16:11, 16 April 2024

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

This tab contains information on

  • Recent Changes
  • Current Issues
  • Beam Restoration

Recent Changes

New MVT LV Reboot Procedure

See https://logbooks.jlab.org/entry/4217011 for detailed information on rebooting the MVT LV when observing a drop in BMT strip occupancies. This gets done upon request of DAQ or MVT expert only.

  • Turn LV OFF from MVT Overview->Low Voltage->MVT-All. LV status indicators should change from green to black;
  • Wait 20 seconds, then turn LV back from the same menu.
  • In the alarm handler, with a 2-minute alarm delay, there can be an alarm "NActiveCrates", the status is also seen on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON.
  • Reboot mvt1, mvt2, and mvt3 ROCS.
  • Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
  • If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert.

RICH issues

Rapid/Controlled Access to the Hall

  • Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.
  • After higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.

24/7 ZOOM connection for Counting House

  • Click on https://jlab-org.zoomgov.com/j/1618614939, included in "Remote Shifts" in tab "Shift Worker"
  • choose the option to "join from browser" (Chrome is recommended) and ignore all other messages to update the ZOOM APP in the pop-up windows,.
  • Enter the passcode from the logbook entry in tab "Shift Worker"

Current Issues

Lights in the Hall

The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall.

  • Refer to these photos: ON: [1], OFF: [2]
  • We have a new dome light switch outside of the hall in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460
  • When the dome lights are switched off, they cannot be turned back on immediately, they require 10-15 min to cool down.

Beamline

  • 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).
  • After the HWP change
    • The absolute values of the SLM and FCUP charge asymmetry (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.
    • Start a new run
  • Tagger Magnet Procedure: If the tagger magnet needs to be turned off, tell the operator to ONLY use the script for degaussing, NEVER do it "by hand"! The latter method might/will trip the circuit breaker for the power supply in the Hall.

BMT / SVT

  • If new hot channels appear, call the SVT/MM expert Yuri Gotra (757-541-7539). These channels need to be addressed by the expert.
  • BMT HV trips: no screenshots are necessary, power-cycle the channel HV as fast as possible (the underlying script will take care of ramping it up), note the information in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.
  • BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview
  • BMT HV S1 L5 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
  • BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview

CND

DAQ

  • Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # 4215299 to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected!
  • 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.
  • roc reboot instructions:
    • To reboot i.e. adcecal1, type on a clasrun terminal: clasrun> roc_reboot adcecal1
    • To check that the crate is back alive, type:clasrun> ping adcecal1
    • The ping will start to answer as soon as the crate communicates again.

DC

  • Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.

ECAL/PCAL

FTOF

RICH

  • Known problematic PMTs and tile:
    • You don't need to report about it.
    • PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.
    • Problematic tiles and PMTs:
      • Sector 1 Tile 21 dead (PMT 55,56,57)
      • Sector 1 Tile 1 PMT 2
      • Sector 4 Tile 34 PMT 92

Beam Restoration

  • Find all Reference values on the white board at tab Short_Term_Schedule

Restoring Beam after Short Downtime

  • Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after
    • beam steering or orbit change
    • change in beam current, e.g., after a target change
    • If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values

Beam Tuning to Tagger Yoke Dump

Study the manual: Establishing Physics-Quality Beam.

  • Contact Eugene Pasyuk if issues arise.
  • Ask MCC to energize the tagger magnet
- blank collimator
- beam type "Photon"
  • All CLAS12 detectors HV off (BMT HV in safe mode)
  • Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM)
  • Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
  • If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values
  • Take harp scans
- at Harp 2C21A (Upstream Right Counter)
- at Tagger Harp 2C24A Upstream Right Counter)
  • If the beam trips, abort the scan and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.
  • Compare the results with the Harp Scan References
  • The fit ranges might need to be adjusted manually to assess the fit results
  • If good, log the new scan results.

Møller run

Follow the standard procedure as described in the manual Performing Møller Runs.

  • Contact Nathan Baltzell if issues arise

A few points to note:

  • Request 20 nA , Orbit Locks should be off
  • The BPMs 2C21 and 2C24A may be out of range after the Møller configuration.
  • Keep running until the polarization uncertainty is < 1.5%

Beam Tuning to Faraday Cup

Study the manual: Establishing Physics-Quality Beam, and take into account the first steps mentioned therein.

This is typically done after tuning to the tagger dump (and possibly taking a Moller run).

  • All CLAS12 detectors HV off (BMT HV in safe mode)
  • Ask MCC to de-energize the tagger magnet
- 20 mm collimator
- beam type electron
- beam blocker out
  • If initial beam tune, target should be "Empty"
  • Ask MCC to unmask beam halos
  • Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds
  • Insert the Downstream Viewer, Chromax, in the beamline
  • Ask MCC for 5 nA beam current
  • If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the Reference Values
  • Take a harp scan at 2H01 (Midstream Left)
  • If the beam trips, abort and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.
  • Compare the results with the Harp Scan References
  • If good, log the new scan results.

Once done and before resuming the production data-taking:

  • Retract the Downstream Viewer from the beamline
  • Put the FSDs thresholds and integration time to their reference values
  • Turn all detector HV ON, for MVT "HV ON - Full Voltage"
  • MCC might need to adjust the beam positions after going to the production beam current.


This tab contains information on

  • Recent Changes
  • Current Issues
  • Beam Restoration

Recent Changes

New MVT LV Reboot Procedure

See https://logbooks.jlab.org/entry/4217011 for detailed information on rebooting the MVT LV when observing a drop in BMT strip occupancies. This gets done upon request of DAQ or MVT expert only.

  • Turn LV OFF from MVT Overview->Low Voltage->MVT-All. LV status indicators should change from green to black;
  • Wait 20 seconds, then turn LV back from the same menu.
  • In the alarm handler, with a 2-minute alarm delay, there can be an alarm "NActiveCrates", the status is also seen on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON.
  • Reboot mvt1, mvt2, and mvt3 ROCS.
  • Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
  • If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert.

RICH issues

Rapid/Controlled Access to the Hall

  • Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.
  • After higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.

24/7 ZOOM connection for Counting House

  • Click on https://jlab-org.zoomgov.com/j/1618614939, included in "Remote Shifts" in tab "Shift Worker"
  • choose the option to "join from browser" (Chrome is recommended) and ignore all other messages to update the ZOOM APP in the pop-up windows,.
  • Enter the passcode from the logbook entry in tab "Shift Worker"

Current Issues

Lights in the Hall

The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall.

  • Refer to these photos: ON: [3], OFF: [4]
  • We have a new dome light switch outside of the hall in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460
  • When the dome lights are switched off, they cannot be turned back on immediately, they require 10-15 min to cool down.

Beamline

  • 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).
  • After the HWP change
    • The absolute values of the SLM and FCUP charge asymmetry (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.
    • Start a new run
  • Tagger Magnet Procedure: If the tagger magnet needs to be turned off, tell the operator to ONLY use the script for degaussing, NEVER do it "by hand"! The latter method might/will trip the circuit breaker for the power supply in the Hall.

BMT / SVT

  • If new hot channels appear, call the SVT/MM expert Yuri Gotra (757-541-7539). These channels need to be addressed by the expert.
  • BMT HV trips: no screenshots are necessary, power-cycle the channel HV as fast as possible (the underlying script will take care of ramping it up), note the information in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.
  • BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview
  • BMT HV S1 L5 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
  • BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview

CND

DAQ

  • Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # 4215299 to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected!
  • 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.
  • roc reboot instructions:
    • To reboot i.e. adcecal1, type on a clasrun terminal: clasrun> roc_reboot adcecal1
    • To check that the crate is back alive, type:clasrun> ping adcecal1
    • The ping will start to answer as soon as the crate communicates again.

DC

  • Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.

ECAL/PCAL

FTOF

RICH

  • Known problematic PMTs and tile:
    • You don't need to report about it.
    • PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.
    • Problematic tiles and PMTs:
      • Sector 1 Tile 21 dead (PMT 55,56,57)
      • Sector 1 Tile 1 PMT 2
      • Sector 4 Tile 34 PMT 92

Beam Restoration

  • Find all Reference values on the white board at tab Short_Term_Schedule

Restoring Beam after Short Downtime

  • Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after
    • beam steering or orbit change
    • change in beam current, e.g., after a target change
    • If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values

Beam Tuning to Tagger Yoke Dump

Study the manual: Establishing Physics-Quality Beam.

  • Contact Eugene Pasyuk if issues arise.
  • Ask MCC to energize the tagger magnet
- blank collimator
- beam type "Photon"
  • All CLAS12 detectors HV off (BMT HV in safe mode)
  • Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM)
  • Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
  • If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values
  • Take harp scans
- at Harp 2C21A (Upstream Right Counter)
- at Tagger Harp 2C24A Upstream Right Counter)
  • If the beam trips, abort the scan and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.
  • Compare the results with the Harp Scan References
  • The fit ranges might need to be adjusted manually to assess the fit results
  • If good, log the new scan results.

Møller run

Follow the standard procedure as described in the manual Performing Møller Runs.

  • Contact Nathan Baltzell if issues arise

A few points to note:

  • Request 20 nA , Orbit Locks should be off
  • The BPMs 2C21 and 2C24A may be out of range after the Møller configuration.
  • Keep running until the polarization uncertainty is < 1.5%

Beam Tuning to Faraday Cup

Study the manual: Establishing Physics-Quality Beam, and take into account the first steps mentioned therein.

This is typically done after tuning to the tagger dump (and possibly taking a Moller run).

  • All CLAS12 detectors HV off (BMT HV in safe mode)
  • Ask MCC to de-energize the tagger magnet
- 20 mm collimator
- beam type electron
- beam blocker out
  • If initial beam tune, target should be "Empty"
  • Ask MCC to unmask beam halos
  • Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds
  • Insert the Downstream Viewer, Chromax, in the beamline
  • Ask MCC for 5 nA beam current
  • If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the Reference Values
  • Take a harp scan at 2H01 (Midstream Left)
  • If the beam trips, abort and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.
  • Compare the results with the Harp Scan References
  • If good, log the new scan results.

Once done and before resuming the production data-taking:

  • Retract the Downstream Viewer from the beamline
  • Put the FSDs thresholds and integration time to their reference values
  • Turn all detector HV ON, for MVT "HV ON - Full Voltage"
  • MCC might need to adjust the beam positions after going to the production beam current.


This tab contains information on

  • Recent Changes
  • Current Issues
  • Beam Restoration

Recent Changes

New MVT LV Reboot Procedure

See https://logbooks.jlab.org/entry/4217011 for detailed information on rebooting the MVT LV when observing a drop in BMT strip occupancies. This gets done upon request of DAQ or MVT expert only.

  • Turn LV OFF from MVT Overview->Low Voltage->MVT-All. LV status indicators should change from green to black;
  • Wait 20 seconds, then turn LV back from the same menu.
  • In the alarm handler, with a 2-minute alarm delay, there can be an alarm "NActiveCrates", the status is also seen on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON.
  • Reboot mvt1, mvt2, and mvt3 ROCS.
  • Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
  • If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert.

RICH issues

Rapid/Controlled Access to the Hall

  • Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.
  • After higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.

24/7 ZOOM connection for Counting House

  • Click on https://jlab-org.zoomgov.com/j/1618614939, included in "Remote Shifts" in tab "Shift Worker"
  • choose the option to "join from browser" (Chrome is recommended) and ignore all other messages to update the ZOOM APP in the pop-up windows,.
  • Enter the passcode from the logbook entry in tab "Shift Worker"

Current Issues

Lights in the Hall

The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall.

  • Refer to these photos: ON: [5], OFF: [6]
  • We have a new dome light switch outside of the hall in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460
  • When the dome lights are switched off, they cannot be turned back on immediately, they require 10-15 min to cool down.

Beamline

  • 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).
  • After the HWP change
    • The absolute values of the SLM and FCUP charge asymmetry (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.
    • Start a new run
  • Tagger Magnet Procedure: If the tagger magnet needs to be turned off, tell the operator to ONLY use the script for degaussing, NEVER do it "by hand"! The latter method might/will trip the circuit breaker for the power supply in the Hall.

BMT / SVT

  • If new hot channels appear, call the SVT/MM expert Yuri Gotra (757-541-7539). These channels need to be addressed by the expert.
  • BMT HV trips: no screenshots are necessary, power-cycle the channel HV as fast as possible (the underlying script will take care of ramping it up), note the information in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.
  • BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview
  • BMT HV S1 L5 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
  • BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview

CND

DAQ

  • Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # 4215299 to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected!
  • 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.
  • roc reboot instructions:
    • To reboot i.e. adcecal1, type on a clasrun terminal: clasrun> roc_reboot adcecal1
    • To check that the crate is back alive, type:clasrun> ping adcecal1
    • The ping will start to answer as soon as the crate communicates again.

DC

  • Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.

ECAL/PCAL

FTOF

RICH

  • Known problematic PMTs and tile:
    • You don't need to report about it.
    • PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.
    • Problematic tiles and PMTs:
      • Sector 1 Tile 21 dead (PMT 55,56,57)
      • Sector 1 Tile 1 PMT 2
      • Sector 4 Tile 34 PMT 92

Beam Restoration

  • Find all Reference values on the white board at tab Short_Term_Schedule

Restoring Beam after Short Downtime

  • Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after
    • beam steering or orbit change
    • change in beam current, e.g., after a target change
    • If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values

Beam Tuning to Tagger Yoke Dump

Study the manual: Establishing Physics-Quality Beam.

  • Contact Eugene Pasyuk if issues arise.
  • Ask MCC to energize the tagger magnet
- blank collimator
- beam type "Photon"
  • All CLAS12 detectors HV off (BMT HV in safe mode)
  • Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM)
  • Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
  • If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values
  • Take harp scans
- at Harp 2C21A (Upstream Right Counter)
- at Tagger Harp 2C24A Upstream Right Counter)
  • If the beam trips, abort the scan and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.
  • Compare the results with the Harp Scan References
  • The fit ranges might need to be adjusted manually to assess the fit results
  • If good, log the new scan results.

Møller run

Follow the standard procedure as described in the manual Performing Møller Runs.

  • Contact Nathan Baltzell if issues arise

A few points to note:

  • Request 20 nA , Orbit Locks should be off
  • The BPMs 2C21 and 2C24A may be out of range after the Møller configuration.
  • Keep running until the polarization uncertainty is < 1.5%

Beam Tuning to Faraday Cup

Study the manual: Establishing Physics-Quality Beam, and take into account the first steps mentioned therein.

This is typically done after tuning to the tagger dump (and possibly taking a Moller run).

  • All CLAS12 detectors HV off (BMT HV in safe mode)
  • Ask MCC to de-energize the tagger magnet
- 20 mm collimator
- beam type electron
- beam blocker out
  • If initial beam tune, target should be "Empty"
  • Ask MCC to unmask beam halos
  • Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds
  • Insert the Downstream Viewer, Chromax, in the beamline
  • Ask MCC for 5 nA beam current
  • If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the Reference Values
  • Take a harp scan at 2H01 (Midstream Left)
  • If the beam trips, abort and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.
  • Compare the results with the Harp Scan References
  • If good, log the new scan results.

Once done and before resuming the production data-taking:

  • Retract the Downstream Viewer from the beamline
  • Put the FSDs thresholds and integration time to their reference values
  • Turn all detector HV ON, for MVT "HV ON - Full Voltage"
  • MCC might need to adjust the beam positions after going to the production beam current.


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.

Click to Edit solely this tab. P.S.: You must click on the top Edit, next to Read, followed by "Save changes" to force the current page to refresh.

Experiment Coordinator: Annalisa D'Angelo

Run Coordinator: Daniel Carman (757) 575-7540

PDL: Daniel Carman (757) 876-1789

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)

Run Plan: Mar. 10 - Mar. 11, 2024

Production Running ... to the end!! 

- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg
- Beam current request: 75 nA
- Run duration: 3 hrs

Note: RG-K run ends on Mar. 11 at 7 a.m. 

- Turn all detectors off and put BMT HV in safe mode
- Ramp torus and solenoid to zero field (contact Eugene to do this)
- Call to put Hall B in Restricted Access

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

2C21A (not important for production)

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

2C24A

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

2H01

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

8.5 GeV Harp Scan References (Feb. 14, 2024)

2C21A: https://logbooks.jlab.org/entry/4252495

Tagger (2C24A): https://logbooks.jlab.org/entry/4252496

2H01: https://logbooks.jlab.org/entry/4252514

6.4 GeV Harp Scan References (Jan. 18, 2024)

2C21A: https://logbooks.jlab.org/entry/4240375

Tagger (2C24A): https://logbooks.jlab.org/entry/4240378

2H01: https://logbooks.jlab.org/entry/4240397

This tab contains information on

  • Recent Changes
  • Current Issues
  • Beam Restoration

Recent Changes

New MVT LV Reboot Procedure

See https://logbooks.jlab.org/entry/4217011 for detailed information on rebooting the MVT LV when observing a drop in BMT strip occupancies. This gets done upon request of DAQ or MVT expert only.

  • Turn LV OFF from MVT Overview->Low Voltage->MVT-All. LV status indicators should change from green to black;
  • Wait 20 seconds, then turn LV back from the same menu.
  • In the alarm handler, with a 2-minute alarm delay, there can be an alarm "NActiveCrates", the status is also seen on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON.
  • Reboot mvt1, mvt2, and mvt3 ROCS.
  • Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
  • If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert.

RICH issues

Rapid/Controlled Access to the Hall

  • Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.
  • After higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.

24/7 ZOOM connection for Counting House

  • Click on https://jlab-org.zoomgov.com/j/1618614939, included in "Remote Shifts" in tab "Shift Worker"
  • choose the option to "join from browser" (Chrome is recommended) and ignore all other messages to update the ZOOM APP in the pop-up windows,.
  • Enter the passcode from the logbook entry in tab "Shift Worker"

Current Issues

Lights in the Hall

The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall.

  • Refer to these photos: ON: [7], OFF: [8]
  • We have a new dome light switch outside of the hall in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460
  • When the dome lights are switched off, they cannot be turned back on immediately, they require 10-15 min to cool down.

Beamline

  • 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).
  • After the HWP change
    • The absolute values of the SLM and FCUP charge asymmetry (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.
    • Start a new run
  • Tagger Magnet Procedure: If the tagger magnet needs to be turned off, tell the operator to ONLY use the script for degaussing, NEVER do it "by hand"! The latter method might/will trip the circuit breaker for the power supply in the Hall.

BMT / SVT

  • If new hot channels appear, call the SVT/MM expert Yuri Gotra (757-541-7539). These channels need to be addressed by the expert.
  • BMT HV trips: no screenshots are necessary, power-cycle the channel HV as fast as possible (the underlying script will take care of ramping it up), note the information in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.
  • BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview
  • BMT HV S1 L5 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
  • BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview

CND

DAQ

  • Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # 4215299 to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected!
  • 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.
  • roc reboot instructions:
    • To reboot i.e. adcecal1, type on a clasrun terminal: clasrun> roc_reboot adcecal1
    • To check that the crate is back alive, type:clasrun> ping adcecal1
    • The ping will start to answer as soon as the crate communicates again.

DC

  • Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.

ECAL/PCAL

FTOF

RICH

  • Known problematic PMTs and tile:
    • You don't need to report about it.
    • PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.
    • Problematic tiles and PMTs:
      • Sector 1 Tile 21 dead (PMT 55,56,57)
      • Sector 1 Tile 1 PMT 2
      • Sector 4 Tile 34 PMT 92

Beam Restoration

  • Find all Reference values on the white board at tab Short_Term_Schedule

Restoring Beam after Short Downtime

  • Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after
    • beam steering or orbit change
    • change in beam current, e.g., after a target change
    • If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values

Beam Tuning to Tagger Yoke Dump

Study the manual: Establishing Physics-Quality Beam.

  • Contact Eugene Pasyuk if issues arise.
  • Ask MCC to energize the tagger magnet
- blank collimator
- beam type "Photon"
  • All CLAS12 detectors HV off (BMT HV in safe mode)
  • Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM)
  • Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
  • If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values
  • Take harp scans
- at Harp 2C21A (Upstream Right Counter)
- at Tagger Harp 2C24A Upstream Right Counter)
  • If the beam trips, abort the scan and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.
  • Compare the results with the Harp Scan References
  • The fit ranges might need to be adjusted manually to assess the fit results
  • If good, log the new scan results.

Møller run

Follow the standard procedure as described in the manual Performing Møller Runs.

  • Contact Nathan Baltzell if issues arise

A few points to note:

  • Request 20 nA , Orbit Locks should be off
  • The BPMs 2C21 and 2C24A may be out of range after the Møller configuration.
  • Keep running until the polarization uncertainty is < 1.5%

Beam Tuning to Faraday Cup

Study the manual: Establishing Physics-Quality Beam, and take into account the first steps mentioned therein.

This is typically done after tuning to the tagger dump (and possibly taking a Moller run).

  • All CLAS12 detectors HV off (BMT HV in safe mode)
  • Ask MCC to de-energize the tagger magnet
- 20 mm collimator
- beam type electron
- beam blocker out
  • If initial beam tune, target should be "Empty"
  • Ask MCC to unmask beam halos
  • Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds
  • Insert the Downstream Viewer, Chromax, in the beamline
  • Ask MCC for 5 nA beam current
  • If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the Reference Values
  • Take a harp scan at 2H01 (Midstream Left)
  • If the beam trips, abort and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.
  • Compare the results with the Harp Scan References
  • If good, log the new scan results.

Once done and before resuming the production data-taking:

  • Retract the Downstream Viewer from the beamline
  • Put the FSDs thresholds and integration time to their reference values
  • Turn all detector HV ON, for MVT "HV ON - Full Voltage"
  • MCC might need to adjust the beam positions after going to the production beam current.

Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.

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

Follow the Short Term Schedule

  • The RC must be notified before changing run conditions

Operate the Data Acquisition

Take action on and log alarms

At the end of the shift, submit the strip charts to the logbook

  • If they are not up already: (CS-Studio → Tools → Strip Charts → livePlot)
  • Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"
  • Choose a time-span width of 10 hours (right-click below x-axis)
  • To make a logbook entry:
- Right click within the grid of one of the charts, choose "Make Logbook Entry"
- The title of the logbook entry can be changed, eg to Strip charts
- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit

Communicate with your co-shift person:

  • Remind them to read the tab 'Shift Worker'.
  • Discuss any issues with the shift worker before making extra logbook entries.
  • Remind the shift worker of the end-of-shift Checklist.
  • Use the CS-Studio Logbook entry tool for all screen shots (but the strip charts)!
  • Note that the Logbook Entry tool puts the entry in the HBRUN logbook by default. Other logbooks can be added or selected from the drop down menu.

Check for and read any comments to logbook entries made during your shift.

Keep your shift summary up to date in HBLOG. Record all significant happenings.

  • Refer to relevant logbook entries in the shift summary.
  • Include a run list for the shift with relevant run information.

Ensure that all monitoring plots and are logged and checked against the reference plots for every single run.

  • Both, you and the shift worker should run mon12 and reset & check spectra frequently.
  • If the worker shift is remote, maintain communication over Zoom.
  • If you have any other questions or uncertainties about what to do, call the RC.

The shift worker (if in person) should log the 'clas12online reconstruction plots at the end of a run. Running the program on more than one CH computer has been causing problems.

In case of RICH issues, check the RICH manual for the current guidance: https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf

New MVT LV Reboot Procedure can be found at tab 'GENERAL INFORMATION'.

Fill out BTA hourly;

  • Accelerator beam time (do not change these values):
    • ABU: acceptable beam used
    • BANU: beam acceptable but not used (should be reflected in our PCC and UED)
    • BNA: beam not acceptable (e.g., tuning, drifting, not focused)
    • ACC: Accelerator Configuration Change (e.g., pass change)
    • OFF: Accelerator is down
  • Experiment beam time (do change these values):
    • ER: Experiment ready (should be 60 minutes - PCC - UED)
    • PCC: Planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, etc.)
    • UED: Unplanned experiment down (hardware failure, DAQ crashes, our problems, ...)
    • Exception: BANU, due to time spent on beam tuning and BPM checks after beam down, should be counted as ER on our side.
  • Enter fields at the "Shift Information" tab.
  • You must save at 7:00, 15:00, and 23:00, to send info to MCC. To see the save button, click 'edit all' or 'edit cc hours.'
  • Acknowledge the popup error message about the last hour not being completed by clicking OK.
  • Sign, viz log completed 8-hour sheet.
  • Note: we can change the time sheet up to 48 hours after completion.

Come to your shift in time for the shift change, 10-15 minutes before the start of your shift;

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

Discuss any issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary.

Use the CS-Studio Logbook entry tool for all screen shots (but the strip charts)!

Frequently

Reset and check mon12 histograms frequently, preferably each 1h

  • Note that some plots have radio buttons at the bottom to choose the sector. Remember to cycle through and check all sectors.

Once per run

Note that the CS-Studio Logbook Entry tool puts the entry in the HBRUN logbook by default. Other logbooks can be added or selected from the drop down menu.

Using the Logbook Entry tool, submit EPICS screenshots to the HBRUN logbook (one logbook entry) with beam ON

  1. Beamline overview (remote shift: in VNC or Web Browser)
  2. DAQ status
  3. CLAS12 trigger rates

Upload mon12 monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see Monitoring tab).

At the end of the run, submit the strip charts to the logbook

  • If they are not up already: (CS-Studio → Tools → Strip Charts → livePlot)
  • Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"
  • Choose a time-span width of 4 hours, compatible with the run duration (right-click below x-axis)
  • To make a logbook entry:
- Right click within the grid of one of the charts, choose "Make Logbook Entry"
- The title of the logbook entry can be changed, eg to Strip charts
- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit

At the end of the run, upload the clas12online plots to the logbook.

  • The program can continue through a standard end/start of a run. However, after a DAQ restart, you must back out and restart clas12online.
  • If the DAQ has to be restarted, you can still make the upload before backing out.

Once per shift

Fill the shift checklist;

  • During production, 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 that 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!


Check the upcoming shifts, and if necessary, coordinate with the PDL to contact shift takers about their training and site access status.

Remote shifts are listed here.

Backup shift personnel is listed here.

Meeting ZOOM connections: see tab Important Links

Daily

  • Report at the PD/RC and attend the MCC/OPS meetings (weekdays 7:45 AM and 8 AM Daily, MCC building). The PD will communicate when and how meetings happen on the weekend.
  • Update the run plan in tab Short Term Schedule (and on the white board in CH) in coordination with the RG-K experiment coordinators (i.e., Annalisa, Daniel) and communicate it to the shift crew.
  • Log the RC Daily summary in the HBLOG.
  • [BTA time sheet: Make sure, the "Beam Available Not Used" (BANU) time is accounted for as explained at tab Shift Expert. The BTA information can be modified post-signature.
    • NOTE: "After 48 hours you cannot modify a User signed timesheet unless you are the signer, Hall Manager, or Admin"
  • Run the daily RC meetings in CH Room 200C and on ZOOM
    • Mo-Tu,Th-Fr at 13:00 ET in the Counting House Conference Room
    • Wednesdays at 3 PM, zoom only
    • Weekends upon agreement
    • Send a daily invitation for the RC meeting to mailing lists hallb, clas12_rgk, clas_members.
    • Keep the Daily RC Meeting Minutes at Run_Group_K wiki, tab "RGK FALL 2023 / SPRING 2024"
  • Connect to Zoom in CH Room 200C:
    • 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. Once it rings, answer the call, and you will be prompted to join the meeting.
    • The room has a camera, which can be turned on via ZOOM.

Weekly

  • MCC/OPS planning meeting, on Wednesdays at 13:30, MCC building.
    • Submit (save) the online form Run Coordinator Weekly Summary before the meeting and present the contents at the meeting.
    • The summary covers the data taking status from 7 am on the previous Wednesday to 7 am on the current Wednesday.
    • Beam time accounting: Beam Time Manager; Physics Time Accounting
    • For the percentage of scheduled experiment hours to date contact Daniel Carman.
    • The total experiment data collected to date can be retrieved from the up-to-date "Accumulated Charge" depicted at [9]
  • Hall B meeting is on Mondays at 9 AM. Present your summary slides that should be sent beforehand to the Hall B leader, Patrick Achenbach.


Webcams

EPICS

• Accelerator Status
• Strip Charts

Data Quality

• New; displaying real-time reconstructed vertices & various event topologies


Clas12design.png



Run Coordinator

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.

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

Shift Worker

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


Monitoring

Webcams

EPICS

- Accelerator Status
- Strip Charts

Data Quality


Important Links

Hall-B

Accelerator

ZOOM Meetings



Clas12design.png

Retrieved from "https://wiki.jlab.org/clas12-run/index.php?title=Run_Group_E&oldid=7594"