Difference between revisions of "Run Group B"

From clas12-run
Jump to navigation Jump to search
Line 107: Line 107:
 
* Take 30nA and 5nA runs when beam is available
 
* Take 30nA and 5nA runs when beam is available
 
* During controlled access: debug BOM counter issue and Moller measurement issues
 
* During controlled access: debug BOM counter issue and Moller measurement issues
 +
  
 
------
 
------
Line 117: Line 118:
 
<b> Compare the monitoring histograms </b> from [https://clas12mon.jlab.org/mon12/histograms/?reference=3746641 clas12mon] to the reference and troubleshoot as needed.
 
<b> Compare the monitoring histograms </b> from [https://clas12mon.jlab.org/mon12/histograms/?reference=3746641 clas12mon] to the reference and troubleshoot as needed.
  
When stopping a run, check the current entered in the pop-up window and put run comments when relevant -- <b> please label junk runs. </b>
+
When stopping a run, check the current entered in the pop-up window and put run comments when relevant -- <b> please label junk runs. </b>  
 
 
 
------
 
------
 +
  
 
''' Thursday Swing / Owl '''
 
''' Thursday Swing / Owl '''
 +
 
Once we get beam back, bring it to Faraday Cup and do harp scans. If good, proceed to trigger validation. If not, send it to tagger dump and set up from there.
 
Once we get beam back, bring it to Faraday Cup and do harp scans. If good, proceed to trigger validation. If not, send it to tagger dump and set up from there.
 
Next: trigger validation (see below).
 
Next: trigger validation (see below).

Revision as of 17:30, 5 December 2019

[edit]

Shift Schedule

Shift Checklist

Hot Checkout

Beam Time Accounting

Manuals

Procedures

JLab Logbooks

RC schedule

  • Nov 20 - Nov 27: S. Stepanyan
  • Nov 27 - Dec 4: M. Contalbrigo
  • Dec 4 - Dec 11: D. Sokhan
  • Dec 11 - Dec 19: S. Niccolai
  • Jan 7 - Jan 15: J. Gilfoyle
  • Jan 15 - Jan 22: V. Kubarovsky
  • Jan 22 - Jan 29: B. McKinnon

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, December 2019 - January 2020
Beam energy ~10.4 GeV (5 pass)
Important: Document all your work in the logbook!

RC: Daria Sokhan

PDL: Maurizio Ungaro



Run Plan: December 4-5

  • Perform detector rate and occupancy studies, establish running conditions
  • Run 100 M events with production trigger for calibration of new FTOF fADC thresholds and for HTCC checks
  • Perform harp scans for new nominal beam positions
  • FC calibration runs (full and empty target)
  • FTHodo calibration runs
  • Run trigger validation following program in https://logbooks.jlab.org/entry/3745954
  • Take 30nA and 5nA runs when beam is available
  • During controlled access: debug BOM counter issue and Moller measurement issues



DAQ config: PROD66 (for runs written to tape and deleted from disk), PROD66_PIN (for runs which need to be kept on disk for immediate access)

Trigger file: rgb_outbending_v11_1.trg

Nominal current: 30 nA

Compare the monitoring histograms from clas12mon to the reference and troubleshoot as needed.

When stopping a run, check the current entered in the pop-up window and put run comments when relevant -- please label junk runs.



Thursday Swing / Owl

Once we get beam back, bring it to Faraday Cup and do harp scans. If good, proceed to trigger validation. If not, send it to tagger dump and set up from there. Next: trigger validation (see below). If everything done, take production data at the highest current possible (which gives electron rate ~ 15kHz), with trigger given by Valery.

Trigger Validation runs ~ 6 hours at least See Valery's plan in logbook

    • Current 50 nA
    • DAQ config: RNDM66_PIN.
    • rgb_outbending_v11_1_random_60kHz.trg
    • ~2 hours WITH BEAM!!!
    • If 60 kHz will not work, try rgb_outbending_v11_1_random_30kHz.trg and stay 3 hours with beam.
    • rgb_outbending_v11_1_validation.trg
    • adjust rate to the maximum possible by prescale of trigger #30 (now set to 30)
    • 2 hours with beam


At the end of each run, follow the STANDARD DAQ RESTART SEQUENCE
This needs to be followed at the end of every run. 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"
  • After each step, make sure it completed in the Run Control message window. If a ROC has crashed, find which one it is, issue a roc_reboot command ON JUST THAT ROC and try again. Contact the DAQ expert if there are any questions.



References and Standards:

(last update 12/4/2019- 17:00)

Nominal Beam Positions

  • 2H01, X: +1.5 mm, Y: -1.0 mm
  • 2C21, X: -0.2 mm, Y: -0.25 mm
  • 2C24, X: -0.3 mm, Y: -0.8 mm

FSD Thresholds

  • Upstream: 2000 Hz
  • Midstream: 2000 Hz
  • Downstream: 700000 Hz
  • BOM: 60000

Reference Harp Scans for Beam on Faraday Cup: 2C21 [1], 2C24 [2], 2H01 [3]

Reference Monitoring Histograms (40 nA, production trigger) [4]

Counter rates

  • Upstream counters integrated rates: 0-15 Hz (acceptable up to 100 Hz are acceptable) @50 nA.
  • Midstream counters: 10-20 Hz (acceptable up to 50 Hz) @50 nA.
  • Counting rates of ~ hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.

Beamline vacuum: should be not higher than 5e-5.


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. If the phone is not answered, try the "Page Experts" button on top of CLASCSS.
  • 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.
  • 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. Run the script btaGet.py to print for you the correct BTA info for this hour -- edit the values on the BTA page if they are wrong!
  • 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
  • Monitor the SVT Slow Controls status, post plot of current stability in the HBSVT elog once per shift.


Every Run:

  • Check values at the start of every run and log screenshots of:
    • Main scaler GUI display
    • Trigger rate GUI
    • Beam strip charts
    • FTC scalers
  • At the start and end of every run, check that the data filled in the database run list is correct (especially fields which are filled in manually, like beam current and comments). This replaces the previously-used spreadsheet.
  • 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.


Notes / Troubleshooting :

FTOF HVs: The goal is to minimize the number of power cycles of the dividers.

    • OFF during: initial beam tuning to the Faraday Cup after CLAS12 has been off for a long shutdown, during a Moller run, harp scans, or if there is tuned/pulsed beam in the upstream beamline.
    • ON after an initial beam tune has been established and if there are only minor steering adjustments and “tweaks” being made.
    • If in doubt, call FTOF expert


Torus and/or Solenoid Fast Dump

    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


Beam to the Faraday Cup: Fast Shut Down elements

  • Upstream, Midstream, Downstream, BOM, and Solenoid FSD elements should always be in the state UNMASKED
  • No changes to the FSD threshold should be made without RC or beamline expert approval


Turning MVT off: do not press "All HV OFF". 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


CND CAMAC crate switch on / reboot:

If CAMAC crate (camac1) holding CND CFD boards is switched off for any reason, always reset the associated CND CFD thresholds by typing, 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


Solutions for common SVT issues: see [5]


RICH recovery procedures: [6]

To be followed in case 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 purpose other than data taking (for which the RICH acceptance is important) do not initiate the recovery procedure. The most critical parameter for the RICH is the temperature of the photosensors. If the temperature rises above limits, an interlock will automatically turn the RICH HV and LV off. If this happens, notify the expert on call and keep taking data without RICH.


Observed asymmetry in FTCal ADC Scalers

When running at low current (<10 nA), FTC asymmetries can be affected by hot channels. If large asymmetries are detected in those conditions, cross check with other detectors (BOM rates, DC occupancies) before taking further action.


Clas12design.png