Run Group F

From clas12-run
Revision as of 20:38, 16 February 2020 by Hattawy (talk | contribs)
Jump to navigation Jump to search
[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 2.2 GeV (1 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 16th, 2020 @ 19:00)


A. ESTABLISH BEAM

DAQ config:PROD66_PIN ; Trigger file:rgf_inbending_v1_1.trg (same for inbending and outbending)

  1. At the beginning of the shift: Call Eugene (PDL: (757) 3033996) to start energizing the solenoid at full field (2416 A) and start energizing Torus at 1/2 maximum field (-1886.5 A) in out-bending polarity. Once the magnets at the requested fields, please sumbit screenshots to logbook. clascss->Soleoind/Torus->Magnet Power Supply.
  2. In parallel to 1, call RTPC expert to set target to “empty” (= 1 atm H2).
  3. In parallel to 1 and 2, Restore beam to the hall, first to the tagger dump, following the procedures described in [1].
  4. Check beam quality using harp scans 2C21 and 2C24, following the procedures described in [2]
  5. When the beam quality is acceptable, Call MCC and ask for a low-intensity (~5nA) beam to FC, complete harp scans (Performing Harp Scans). We require less than 0.3 mm (1σ) beam widths in x and y (As measured by 2H01A harp) and halo below 10^−4 (As measured by 2H01A harp).
  6. Center beam on target, using rates in BOM and downstream beam monitors. Establish range where beam starts directly interacting with target walls and take middle.
  7. Engage orbit locks and ascertain that they are stable.
  8. Set alarms and interlocks.
  9. TURN HV ON for all the detectors.
  10. ask for 5 to 10 nA to the tagger.
  11. take harp scans for 2c21 and 2c24 and compare them to 2C21 [3], 2C24 [4].
  12. if what you get is similar to the references, call the mcc and tell them the the beam is acceptable and ready to be taken to the FC.
  13. put 20 mm collimator and change the beam to electron and ask the mcc for 10 nA to the FC.
  14. compare what you get on 2H01 to the 2H01 [5].
  1. fill the target with 68 psig H2 (call Mohammad or rtpc expert)


B. CALIBRATION AND COMMISSIONING AT 1 PASS (2.2 GEV)

I. Outbending Configuration, H2 target (about 1 day)

DAQ config:PROD66_PIN; Trigger file:rgf_inbending_v1_1.trg (same for inbending and outbending)

# Checking:

    1. Solenoid at full field (2420 A).
    2. Torus at 1/2 maximum field (-1880 A) in out-bending polarity
  2. Call MCC and ask for 5 nA beam.
  1. Re-check alarms and interlocks, rates and occupancies and make adjustments as necessary.
  2. Start DAQ and start taking data. Look at CED and monitoring plots to check occupancies.
  3. IF trigger rate is much less than 5kHz, we can increase the beam current (observe DC occupancies, BOM, downstream monitors) up to 50 nA in steps of 10 nA.
  4. Check the DAQ trigger rate, it must be less than 5kHz. If it is higher call MCC and reduce the beam current as needed.
  5. At the end of every run (~2 hours):
    1. submit screenshots for the DAQvnc, Beamline overview, BONuS overview from clascss.
    2. From live plot, submit the Beam X-positions, Y positions for 2C21, 2C24, 2H00, 2H01.
    3. from live plot, submit screenshot for beam current at 2C21, 2C24, 2H00, 2H01.
    4. Run clas12mon over 10000 events and submit the occupancy plots.
  6. Scan the solenoid field ( nominal HV set in the bonus:
    1. take run at 5T Solenoid (5M events)
    2. Take run at 4.5 T Solenoid(5M events)
    3. Take run at 4 T solenoid ( 5M events)
    4. Take run at 3.5 T solenoid (5 M events)
  7. At the best two B solenoid field configurations: (Call the rtpc expert)
    1. Increase the HV across the transfer regions between the GEM foils ( 300 V-> 330V), keep 380 acroos the GEM foils and the drift region
    2. Increase the gain across the GEMs (380 ->410).
  8. Take data with the current BONUS HV setting [6] and 4T solenoid filed till 3:00 AM.
  9. Call the Mohammad at 2:30 AM to empty the traget.
  10. take empty target run at the current setting.


III. Electron-oubending Configuration, D2 target (3:00 PM)

DAQ config:PROD66_PIN; Trigger file:rgf_inbending_v1_1.trg (same for inbending and outbending)

# Call Mohammad to purge the target and fill it with D2 gas target (68 psig) .

  1. Call MCC and ask for 5nA beam.
  2. Start DAQ and start taking data.
  3. Check the DAQ trigger rate, it must be less than 2kHz. If it is higher call MCC and reduce the beam current as needed.
  4. At the end of every run (~1 hours, 5 M events):
    1. submit screenshots for the DAQvnc, Beamline overview, BONuS overview from clascss.
    2. Run clas12mon over 10000 events and submit the occupancy plots.


III. Electron-outbending Configuration, 4He target (from 15:00 to 18:00)

DAQ config:PROD66_PIN; Trigger file:rgf_inbending_v1_1.trg (same for inbending and outbending)

# Call Mohammad ( or ask any available rtpc expert) to purge the target and fill it with 4He gas target (68 psig) .

  1. Beam current is 5nA beam.
  2. Start DAQ and start taking data.
  3. At the end of every run (~1 hours, 5 M events):
    1. submit screenshots for the DAQvnc, Beamline overview, BONuS overview from clascss.
    2. Run clas12mon over 10000 events and submit the occupancy plots.

III. Electron-inbending Configuration, D2 target @ 10.4 GeV beam

DAQ config:PROD66_PIN; Trigger file:rgf_inbending_v1_1.trg # Turn off all the HV on ALL the detectors.

  1. call RTPC expert to purge the target and fill it with D2 gas target (68 psig) .
  2. call MCC and tell them that we are ready to go to 5 pass and take the beam away.
  3. call beamline expert to flip the polarity of the torus and go to full in bending field.
  4. Call MCC and ask to take the beam to the tagger and ask for 5 nA beam for harp scans.
  5. follow the procedures for the harp scans [7]
  6. compare the results of the scans to 2C21 [8], 2C24 [9].
  7. take a Moller run to measure the beam polarization as described here [10]
  8. if what you get is similar to the references, call the mcc and tell them the the beam is acceptable and ready to be taken to the FC.
  9. put 20 mm collimator and change the beam to electron and ask the mcc start with 1 nA to the FC. If it goes to the FC, increase to 5 nA.
  10. compare what you get on 2H01 to the 2H01 [11].
  11. IF the beam looks acceptable, turn on HV on all the detectors except FMT.
  12. call beamline expert to put the FC blocker.
  13. Start DAQ and start taking data.
  14. Check the DAQ trigger rate, it must be less than 5kHz. If it is higher call MCC and reduce the beam current as needed, if it is lower than 5kHz, increase the beam current but less than 50 nA unless approved by an expert.
  15. Take data till 8:00 AM, Monday Feb 17th. At the end of every run (10M events):
    1. submit screenshots for the DAQvnc, Beamline overview, BONuS overview from clascss.
    2. Run clas12mon over 100000 events and submit the occupancy plots.


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 16, 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: -1.1 mm, Y: -0.9 mm
  • 2C24, X: +0.8 mm, Y: -0.5 mm
  • 2C21, X: 0.1 mm, Y: 0.0 mm

FSD Thresholds

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

BONuS HV setting

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

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

Reference Monitoring Histograms 5 nA production trigger [15]

Reference Scalers and Halo-Counter Rates:

  • Well-tuned CW beam on FC, Full LH2 target, CLAS12 ON: 5 nA [16], 50 nA [17]
  • Well-tuned CW beam on FC, Empty Target, CLAS12 OFF: 5 nA [18]
  • Well-tuned beam during Moller run [19]
  • Well-tuned beam on Tagger Dump at 5 nA during harp scans: [20]

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 (on day shift):

  • Complete RICH recovery procedure - see Note: 14 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
    • FTC scalers
  • Fill out the run info in run list at the beginning and at the end of each run.
  • 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: 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: 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 3: 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 4: 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 5: Any request for a special run or change of configuration has to be approved by the RC & documented
  • Note 6: 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 7: 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 [21]
  • Note 8: Shift workers must check the occupancies! Use this tool to compare to previous runs: [22]


  • Note 10: Check the vacuum periodically, make sure vacuum is not higher than 5e-5
  • Note 11: 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 12: 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 14:

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 15: 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 16: 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

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