Run Group B

From clas12-run
Jump to navigation Jump to search
[edit]

Shift Schedule

Shift Checklist

Hot Checkout

Beam Time Accounting

Manuals

Procedures

JLab Logbooks

RC schedule

  • Jan 26 - Feb 6: S. Niccolai
  • Feb 6 - Feb 13: Y. Ilieva
  • Feb 13 - Feb 20: S. Stepanyan
  • Feb 20 - Feb 27: F. Hauenstein
  • Feb 27 - Mar 6: S. Niccolai
  • Mar 6 to Mar 12: J. Gilfoyle
  • Mar 12 to Mar 19: V. Kubarowsky

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 B, spring 2019
Beam energy 10.6 GeV (5 pass)
Important: Document all your work in the logbook!
Remember to fill in the run list at the beginning and end of each run (clas12run@gmail.com can fill the run list)

RC: Yordanka Ilieva

PDL: Maurizio Ungaro


Initial Run Plan:

(last update 2/7/2019- 9:30 AM)

Preparation for Beam in Hall B

  • NEVER allow MCC to send tune (pulsed beam to the Faraday Cup).
  • If MCC ask for harp scans , make sure the beam current is below 10 nA.

1) Torus and solenoid should be energized (ramping up to begin around 8:10 am of 8 Feb 2018). Torus full field (3770 A during RGA) inbending [1], solenoid full field (2416 A during RGA)[2].

2) Target is EMPTY (target will be made ready starting at 8 am on 8 Feb 2018).

3) Once the magnets are ON, take a cosmic run with PROD66_PIN and trigger rgb_v0_cosmic.trg. Make sure that the following detectors must be ON: DC, HTCC, ECAL, PCAL, and FTOF. Take data as long as possible during the day shift, until MCC calls that they ready to send beam to Hall B. Call Zhiwen to start cooking the run.
Note: If MCC is ready to send beam to Hall-B before we can take this run, turn the HV of the above detectors OFF and let Hall-B go to Beam Permit status.

4) When MCC is ready to send beam for tuning in the hall

  • Turn the HV of all detectors OFF (including FTOF), except for MVT, which should be placed in "Safe" mode (see Note 11 below). LV should remain ON (especially important for CVT).
  • Confirm with MCC that our BPMs have been calibrated.


Restoration of Beam to Hall B

During beam tuning one should continuously monitor the leakage current on the SVT ("SVT HV Currents" graph on "SVT temps" graphic window). The SVT currents should be below 10 nA.

  • When the beam is on the tagger dump, higher currents are an indication of a massive bleedthrough from other halls. To confirm, ask MCC to turn our laser off and check the currents measured by the BPMs. If bleedthrough is confirmed ask MCC to address the problem. Notify Yuri Gotra that SVT currents are high.
  • When the beam is on the FC, higher currents are an indication of a tune beam on the FC, that goes through detector material. Tune beam on FC should never be allowed . Call MCC and ask to turn the tune beam OFF. Notify Yuri Gotra that SVT currents are high.

1) Tune beam by deflecting it to the tagger dump following the procedures described in [3].

2) Check beam quality using harp scans 2C21 and 2C24, and compare to reference [4]

3) Call Stepan (beamline expert cell number) to be present in the counting house. When the beam quality is acceptable, take a Moeller run to verify polarization, following procedures [5]. Acceptable polarization is >=85%. If the polarization is not acceptable, make a separate entry in the LogBook. A spin-dance may be necessary to find the Wien angle maximizing our polarization. Such a spin dance will take place on Monday (11 Feb) morning. On 8 - 10 Feb and 11 Feb owl shifts we run with delivered polarization. In any case, record the measured polarization in the shift summary.

4) Send beam to Faraday cup according to the procedure in [6]. Reference H201 harp scan from RGA: [7].

5) Stepan (beamline expert cell number) is to be present in the counting house during the beam alignment with respect to the target. Check and adjust the alignment of beam with respect to the target, according to the procedure in [8].

6) Put the beam blocker IN. Turn ON the FT Calorimeter. Ask for 15 nA beam. Check the asymmetries in X and Y on the FTCal. Acceptable values are up to 2.5%. Good tune will yield asymmetries below 1%. If the beam position needs to be adjusted, ask MCC to move the beam in small steps using 2H01 BPM. Record the final beam position values on 2C21, 2C24, and 2H01.

7) Calculate the thresholds for the Downstream and BOM components of the FSD system according to the formula in [9]. The thresholds for the Upstream and Midstream components are 1000. Confirm with Stepan the values and finalize the thresholds.

8) Ask MCC to lock the orbits on the final position (typically using 2C24 and 2H01) and to set the FSD limits to the values from 7). Ask for 5 nA beam.

9) Call Youri Gotra to come to the counting house for the first turing ON of MVT and SVT (the procedure of turning ON SVT is in https://logbooks.jlab.org/entry/3615766). Turn all other detectors ON.

10) RC fills up the target with LD2 (the procedure is written in the papers which is on the left of the keyboard of the target computer, which is facing the window looking over the electronics room).

11) If beam energy is too different (by ~ one hundred or more MeV), contact Rafo for re-calibration of the FC reading.


Data taking during the weekend

Production-run DAQ configuration PROD66, trigger file rgb_v0.trg.

1) Call FTOF/CTOF expert on call, Florian Hauenstein, and Yuri Gotra to be present in the counting house during the luminosity scans. Do a current scan (5, 10, 20, 40, 50, 60, 65, 75 nA) checking and writing down trigger rates, data rates, DC occupancies, FTOF and CTOF scalers, and CVT current. Be aware that with a deuterium target we may get higher rates than for RGA, at a given current. The current values above are tentative. The maximum current, beyond which we cannot go is determined by the DC occupancies (3% - 4%). However, if DC occupancies permit it, we should go up to 75 nA in the scan even if trigger and data rates are above the nominal limits. This is a quick scan where all data are in a single run. (~5 min per beam current).

  • If the detector can handle higher current, but the data rate is higher than ~450 MB/s, or average rate is higher than 350 MB/s, make a separate log entry. We will have to negotiate with scicomp an increase of our allowed data rate.
  • Pick the beam current for standard production running that allows acceptable rates (DC occupancies ~3-4%, trigger rates~10k, data rates~450 MB/s).

2) Trigger validation studies (random trigger), 150 M events at 50 nA; stable beam. Valery and Rafo should be called in advance (see white board in the counting house for cell numbers). DAQ configuration: PROD66_PIN. Trigger file: Diagnostics/RGB_trg_v30_validate_Basicelectron.trg. Determine the average current after 3 hours of running (myStats -b -180m -l IPM2C21A) and if it is less than 50 nA, prorate the 150 M events to a larger value. Call Zhiwen to begin cooking the run.

3) Take a production run at 20 nA (about 3 - 4 hours) with PROD66_PIN and rgb_v0.trg to be used for HTCC and FTOF/CTOF thresholds and HV final adjustments, as well as trigger validation. When data have been taken, contact Zhiwen (phone number on white board in the counting house) to start cooking the run. This run should also establish if beam is stable.

4) Take data with the nominal production current established in 2). One run should be about 2-hrs long. This will determine the goal number of events per run.

5) If beam is stable, take 1 run at 5 nA for tracking efficiency studies.

6) If the polarization is catastrophically poor, RC will empty the target. Take empty-target run.

General Instructions:

  • For a given beam current, compute the FSD thresholds according to the Establish Physics Quality Beam document. Call MCC to update the values. Contact the beamline expert if there are questions about setting the FSD thresholds.
  • 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 60 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.
  • All jscaler iocs (iocjscalerX) on the health screen (under DAQ tab) must be restarted after every DAQ prestart is completed.
  • Check that no unecessary beamline-related screens are open. This includes particularly the big beamline overview screen, but also and any motor/harp/collimator screens, and ioc health screens.
  • Check for and read any comments to log-book entries made during your shift.

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.
  • Check on white board all scalers, strip charts and monitoring plots that need to be logged regularly
  • 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.
  1. Fill and submit the shift checklist in the logbook
  2. Perform 2H01A harp scan once per shift or when beam conditions have changed, based on beam monitors (BPMs, halo rates, beam-viewer). During harp scans the HV for DC and HTCC should be OFF.
  • Monitor the SVT Slow Controls status, post plot of current stability in the HBSVT elog once per shift.

Every Run:

  • Log screenshots of:
    • main scaler GUI display (both at the begining and at the end of run)
    • Detector occupancy plots
    • Trigger rate gui
    • Beam strip charts
  • Fill out the run info in run list at the beginning and at the end of each run.


  • Note 1: Be very mindful of the background rates in the halo counters, rates in the detectors, and currents in the SVT for all settings to ensure that they are at safe levels.

The integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and the rates on the midstream counters have to be in the range 10-20 Hz (acceptable up to 50 Hz) @50 nA. Counting rates in the range of hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.

  • Note 2: At the end of each run, follow the standard DAQ restart sequence

"end run", "cancel", "reset", then 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".

After each step, make sure it is complete in the Run Control message window. If a ROC has crashed, find which one it is and issue a roc_reboot command and try again. Contact the DAQ expert if there are any questions.

  • Note 3: Nominal beam positions: 2C24A (X= mm, Y= mm) , 2H01 (X=mm, Y= mm)
  • Note 4: 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, 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 5: 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 6: 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 7: Any request for a special run or change of configuration has to be approved by the RC & documented
  • Note 8: 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 9: Reset CLAS12MON frequently to avoid histogram saturation.
  • Note 10: Shift workers must check the occupancies! Use this tool to compare to previous runs: [10]
  • Note 11 Do not Turn OFF MVT HV: Instead go to 'Restore settings' from the MVT overview screen:
    1. SafeMode.snp for beam tuning and Moeller runs
    2. MV_HV_FullField.snp for full solenoid field
    3. MV_HV_MidField.snp wgeb solenoid < 4T

  • NOTE 12 Check the vacuum periodically, make sure vacuum id not higher than 5e-5
  • NOTE 13 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 14 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 16: After any reboot of crate 'adcband1', reboot tdcband1 crate to avoid sync problems of TDCs.
  • NOTE 17: * 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. Also, during production runs, one may want to end the run, recover the missing tiles afterwards, and then begin a new run.
    • The most critical problem for RICH would be too high temperature. 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.


Clas12design.png

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