Difference between revisions of "Run Group F"

From clas12-run
Jump to navigation Jump to search
Line 107: Line 107:
 
* When we get done with DC roads study ad the beam is stable, using the highest luminosity, take 50M events in a single run for ctof and ftof calibration and notify David (dpaye001@odu.edu and hattawy@jlab.org) to cook the run and notify Daniel Carmen (carmen@jlab.org) when the cooking is finished.  
 
* When we get done with DC roads study ad the beam is stable, using the highest luminosity, take 50M events in a single run for ctof and ftof calibration and notify David (dpaye001@odu.edu and hattawy@jlab.org) to cook the run and notify Daniel Carmen (carmen@jlab.org) when the cooking is finished.  
  
===<font color=blue>''A. ESTABLISH BEAM ''</font>===
+
<font color=green>
 
 
 
====<font color=blue>''A. Establishing the beam (Updated at 18:03)''</font>====
 
====<font color=blue>''A. Establishing the beam (Updated at 18:03)''</font>====
 
# Keep not changed:
 
# Keep not changed:
Line 127: Line 126:
 
# if what you get is similar to the references, call the mcc and tell them the the beam is acceptable and take beam away.  
 
# if what you get is similar to the references, call the mcc and tell them the the beam is acceptable and take beam away.  
  
 +
</font>
  
====<font color=blue>''B. Electron-inbending Configuration, D2 target @ 10.4 GeV beam''</font>====
+
====<font color=blue>''B. Electron-inbending Configuration, D2 target @ 10.4 GeV beam (100M events in total)''</font>====
 
<b>DAQ config:PROD66_PIN; Trigger file:rgf_inbending_v2_1.trg </b>
 
<b>DAQ config:PROD66_PIN; Trigger file:rgf_inbending_v2_1.trg </b>
  

Revision as of 21:55, 18 February 2020

[edit]

Shift Schedule

Shift Checklist

Hot Checkout

Beam Time Accounting

  • See guidance for BTA in

Beam Time Accounting User Guide.

Manuals

Procedures

JLab Logbooks


RC schedule Weekly form

  • Feb 12 - Feb 18: Mohammad Hattawy
  • Feb 19 - Feb 25: Florian Hauenstien
  • Feb 26 - Mar 3: Eric Christy
  • Mar 4 - Mar 17: Sebastian Kuhn
  • Mar 18 - Mar 24: Mohammad Hattawy
  • Mar 25 - Mar 31: Raphael Dupre
  • Apr 1 - Apr 7 : Narbe Kalantarians
  • Apr 8 - Apr 14: Carlos Ayerbe
  • Apr 15 - Apr 21: Mohammad Hattawy
  • Apr 22 - May 6 : Stephen Bultmann

If calling local numbers (with area code prefix 757) from the counting room dial 9+[last 7 digits]. To call other area codes dial 91+[10 digit number]

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 Here to edit Phone Numbers. Note, you then also have to edit this page to force a refresh.


CLAS12 Run Group F, Spring 2020
Beam energy 10.38 GeV (5 pass)
Important: Document all your work in the logbook!

RC: Mohammad Hattawy (Full list of RG-F RCs)

  • 757-575-7540
  • 9 757-575-7540 from Counting Room

PDL: Stepan Stepanyan

  • (757) 876-1789
  • 9 876-1789 from Counting Room

Run Plan, 2020

(Last updated: Feb 18th, 2020 @ 9:00 AM)

Requests

  • At the coming 0 fields in the solenoid and the torus, notify Brent (bmorris@jlab.org), Stepan (stepanya@jlab.org), Ruben Fair (rfair@jlab.org) about the Hall access to change the switch.
  • When we get done with DC roads study ad the beam is stable, using the highest luminosity, take 50M events in a single run for ctof and ftof calibration and notify David (dpaye001@odu.edu and hattawy@jlab.org) to cook the run and notify Daniel Carmen (carmen@jlab.org) when the cooking is finished.

A. Establishing the beam (Updated at 18:03)

  1. Keep not changed:
    1. ALL the detectors are off except FTOF (Read note # 1 for ftof turn off cases).
    2. put 20 mm collimator
    3. beam blocker is out
    4. change the beam to electron
    5. call mcc to unmask U/M/D counters. keep BOM masked.
    6. Thresholds on U/M/D is 1M/1M/1M and dwel time is 50 ms.
  1. When beam comes back:
    1. turn HV off on the ftof
    2. Call MCC and ask to take the beam to the FC and ask for 5 nA beam for harp scans to the FC.
    3. compare the 2c21, 2c24, 2H01 positions to the reference below.
    4. follow the procedures for the harp scans 2c21, 2c24, 2H01 [1]
    5. compare the results of the reference scans below.
  1. if what you get is similar to the references, call the mcc and tell them the the beam is acceptable and take beam away.

B. Electron-inbending Configuration, D2 target @ 10.4 GeV beam (100M events in total)

DAQ config:PROD66_PIN; Trigger file:rgf_inbending_v2_1.trg

  1. IF the beam looks acceptable, turn on HV on all the detectors except the FMT (call Yuri Gotra for that).
  2. Put the FC blocker.
  3. Keep taking data IF AND ONLY IF the torus is at fixed current (either half current or full current) and stable. Ask MCC for 100 nA beam current.
  4. At the end of every run (10M events):
    1. submit screenshots for the DAQvnc, Beamline overview, RTPC (BONuS) overview from clascss.
    2. Run clas12mon over 100000 events and submit the occupancy plots.
    3. Screenshot for DAQ/Trigger GUIs to logbook when beam is only ON.


At the end of each run, follow the standard DAQ restart sequence
(Note, this might be different from the instructions coming up on RunControl.)

  • "end run", "cancel", "reset"
  • if the run ended correctly:
    • "download", "prestart", "go"
  • if the run did not end correctly or if any ROCs had to be rebooted:
    • "configure", "download", "prestart", "go"

References and Standards:

(last update Feb 18, 2020 @ 19:00 PM.)

Restoration of Beam to Hall B


Default solenoid current and B field 1933 A (~4.06 T)

Nominal Beam Positions

  • 2H01, X: -0.6 mm, Y: -0.6 mm
  • 2C24, X: +0.1 mm, Y: -0.4 mm
  • 2C21, X: +0.1 mm, Y: 0.0 mm
  • the acceptable trajectory for the beam before entering the hall must be established while on the tagger dump. The relation between the 2C24 BPM positrons and the X,Y values measured with the tagger harp are:
    • X_harp=36.68-X_2C24
    • Y_harp=20.97-Y_2C24

FSD Thresholds

  • Upstream: 2000 Hz
  • Midstream: 2000 Hz
  • Downstream: 500000 Hz
  • BOM: 100000

FSD Dwell time

  • Upstream: 5 ms
  • Midstream: 5 ms
  • Downstream: 5 ms
  • BOM: 5 ms

BONuS HV setting

Reference Harp Scans for Beam on Tagger Dump: 2C21 [2], 2C24 [3]

Reference Harp Scans for Beam on Faraday Cup: 2H01 [4]

Reference Monitoring Histograms 5 nA production trigger [5]

Reference Scalers and Halo-Counter Rates:

  • Well-tuned CW beam on FC, Full LH2 target, CLAS12 ON: 5 nA [6], 50 nA [7]
  • Well-tuned CW beam on FC, Empty Target, CLAS12 OFF: 5 nA [8]
  • Well-tuned beam during Moller run [9]
  • Well-tuned beam on Tagger Dump at 5 nA during harp scans: [10]

General Instructions:

  • The main lights in the Hall (dome lights) and the Forward Carriage lights are being kept off because of light leaks affecting some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall. Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cooldown.
  • Do not run more than 30 minutes above 30 nA with 5-pass beam without the beam blocker in front of Faraday cup. Put beam blocker in for long running at high currents for 5 pass operations.
  • Turn DC HV off only for beam tuning; if no beam is available or when beam is stable, keep them on even if you are not taking data.
  • In case of loss of communication with IOCBTARG, follow instructions at https://logbooks.jlab.org/entry/3502218
  • With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem.
  • Check for and read any comments to log-book entries made during your shift.

Once Per Day (At 13:00):

  • Call RTPC expert to purge the target and fill it with the appropriate target gas.
  • Complete RICH recovery procedure - see Note: 11 below

Every Shift:

  • Follow run plan as outlined by RC
  • If any concern about beam stability, ask MCC if orbit locks are on (they should be).
  • Keep shift summary up to date in HBLOG. Record all that happens.
  • Document any beam condition change and send scaler GUIs to HBLOG
  • Fill out BTA hourly. Click "Load from EPICS" to automatically fill the left side.
  • Upload spectra from clas12mon at begin and end of shift and cross-check with reference spectra
    • Reset clas12mon every ~2 hours and inspect spectra
  • Fill and submit the shift checklist in the logbook


Every Run:

  • Log screenshots of:
    • main scaler GUI display
    • Trigger rate gui
    • Beam strip charts
  • When checking the ECAL response, make sure to look at the histograms for each sector by using the sector buttons at the bottom of the clas12mon window - if adcecal* or/and adcpcal* ROC crashes, there will be no alarm and the histograms are the way to notice this issue.
  • Same holds for FT.


  • Note 1: FTOF HVs: The goal is to minimize the number of power cycles of the dividers.
    • should be turned off during the initial beam tuning down to the Faraday Cup after CLAS12 has been off for a long shutdown, when doing a Moller run, when doing harp scans, or if there is tuned/pulsed beam in the upstream beamline.
    • should be left on after an initial beam tune has been established and if there are only minor steering adjustments and “tweaks” being made.
    • if shift workers have doubts what to do with the HVs, they can always contact the TOF on-call expert for advice.
  • Note 2: In case of a Torus and/or Solenoid Fast Dump do the following:
    1. Notify MCC to request beam OFF and to drop Hall B status to Power Permit
    2. Call Engineering on-call
    3. Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org
    4. Notify Run Coordinator
    5. Turn off all detectors
  • Note 3: When beam is being delivered to the Faraday Cup:
    1. the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state UNMASKED
    2. No changes to the FSD threshold should be made without RC or beamline expert approval
  • Note 4: Any request for a special run or change of configuration has to be approved by the RC & documented
  • Note 5: Carefully check the BTA every hour and run the script btaGet.py to print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.
  • Note 6: Reset CLAS12MON frequently to avoid histogram saturation. If CLAS12MON is restarted change MAX scale to 10 (default is 5) for DC normalized occupncy histograms. This would prevent them from saturation. See log entry [11]
  • Note 7: Shift workers must check the occupancies! Use this tool to compare to previous runs: [12]


  • Note 8: Check the vacuum periodically, make sure vacuum is not higher than 5e-5
  • Note 9: Always reset the CFD threshold after all power off/on on the CND CAMAC crate

After the CAMAC crate (camac1) holding the CND CFD boards is switched off for any reason, it is mandatory to reset the associated thresholds typing the following command from any clon machine terminal: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0

If this command is failing and the crate is not responding, reboot it as follows: roc_reboot camac1

  • Note 10: Shift workers should anyway check routinely scalers to verify they update correctly and make a logbook entry if anomalies are observed after starting a new run.


  • Note 11:

For RICH recovery procedures, please see Log entry https://logbooks.jlab.org/entry/3562273. This would apply in the cases of 1. DAQ crash: rich4 is not responding or 2. RICH alarms (LV,missing tile, temperature etc). If it does not work or you are uncertain about what to do, contact the RICH expert on call. Please, note that missing tiles typically occur due to lost communication. Keep in mind that the recovery procedure will kill DAQ. If DAQ is running for other purpose, rather than data taking (for which the RICH acceptance would be important) do not initiate the recovery procedure.

    • The most critical parameter for RICH is the temperature of the photosensors. If the temperature rises above limits, an interlock will automatically turn the RICH HV and LV. If this happens, notify the expert on call and keep taking data without RICH.
  • Note 12: Asymmetry on FTCal ADC Scalers: If the beam current is 5 - 10 nA, and the observed asymmetry is out of specs, i.e. > +-2.5%, check (1) that the beam position is according to specs, (2) the response of the rest of CLAS (compare the scalers of FTOF, CTOF, ECAL, etc. from the Scalers GUI to the reference for that current, as posted above). If positions and other detectors do not show any anomalies, keep running. The ADC scalers require at least ~15 nA for a reliable response.
  • Note 13: If ROC mmft1 is 100% busy: power cycle FTT LV (FT->FTT Overview, HV stays ON), roc_reboot mmft1, wait until it reboots (ssh mmft1 to verify). If the first LV recycle/mmft1 reboot doesn’t work call FT expert

Webcams

Manuals

Epics on the web

Fall 2018 Run

fall2018_charge.jpg

Moller rg a fall.jpeg

Spring 2018 Run

chart.jpeg

Moller measurement rg-a.jpg


Clas12design.png