Difference between revisions of "Run Group B"

From clas12-run
Jump to navigation Jump to search
Line 175: Line 175:
 
Production-run DAQ configuration '''PROD66''', trigger file '''rgb_v2.trg'''.
 
Production-run DAQ configuration '''PROD66''', trigger file '''rgb_v2.trg'''.
  
−
<!--
 
−
<b> Data taking on 10 Feb </b>
 
−
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).
+
<b> Plan for 13-14 Feb </b>
−
*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).
 
  
−
1) Trigger validation studies (random trigger), 200 M events at 40 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 40 nA, prorate the 200 M events to a larger value. When you start the run, call Zhiwen to begin cooking the run.
 
  
−
2) Take a production run at 20 nA (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 you start the run, contact Zhiwen (phone number on white board in the counting house) to start cooking the run.
+
After random trigger run, take 2-hrs long runs with <b> PROD66 </b> and <b> rgb_v3.trg </b>.
−
 
 
−
---------
 
−
1) Take tracking efficiency run with '''PROD66_PIN''' and '''rgb_v0.trg''' at 5 nA for about 4 hours.
 
−
 
 
−
2) Take tracking efficiency run with '''PROD66_PIN''' and '''rgb_v0.trg''' at 35 nA for about 2 hours.
 
−
 
 
−
3) Take tracking efficiency run with '''PROD66''' and '''rgb_v0.trg''' at 10 nA until Monday morning or until further notice by RC. One run is about 2-hours long.
 
−
 
 
−
-->
 
−
 
 
−
<!--
 
−
3) Trigger validation studies (random trigger), ... M events at 10 nA; stable beam. Valery and Rafo should advise on the number of events to collect. DAQ configura3) Trigger validation studies (random trigger), ... M events at 10 nA; stable beam. Valery and Rafo should advise on the number of events to collect. DAQ configuration: PROD66_PIN. Trigger file: Diagnostics/RGB_trg_v30_validate_Basicelectron.trg. Determine the average current after ... hours of running (myStats -b -180m -l IPM2C21A) and if it is less than 10 nA, prorate the ... M events to a larger value. When you start the run, call Zhiwen to begin cooking the run.
 
−
If beam is stable and we had completed the beam-current measurements to high currents, take a tracking efficiency run with '''PROD66_PIN''' and '''rgb_v0.trg''' at 50 nA for about 2 hours. (Confirm with RC that you can request such a high current).
 
−
-->
 
−
 
 
−
<!--
 
−
<b> Plan for 10, 11 Feb </b>
 
−
 
 
−
1) Keep running at 10 nA until MCC calls and informs that they are ready for Spin Dance.
 
−
2) Complete all logbook screenshots of scalers, etc. and submit monitoring histos to logbook if not done earlier.
 
−
 
 
−
*Beam is OFF for RF studies. CLAS12 has HV OFF (LV remain ON), except for MVT, which is placed in a "Safe Mode" as per instructions above and on the white board.
 
−
* Hall B is in controlled access.
 
−
*Wait for MCC to call that they will begin Spin Dance
 
−
*Preparation for and taking Moller runs [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf]
 
−
**Blank collimator is IN
 
−
**MCC will energize the tagger magnet
 
−
**Take a Moller run at the current value of the Wien angle. Polarization uncertainty must be <=1.5%.
 
−
**MCC will change the Wien angle by 25deg. When they call that this is complete, take a Moller run at that angle. Polarization uncertainty must be <=1.5%.
 
−
**MCC will change the Wien angle by -25deg. When they call that this is complete, take a Moller run at that angle. Polarization uncertainty must be <=1.5%.
 
−
**Using the three sets of values (polarization, Wien angle), MCC will estimate at which angle, theta_W_max, the polarization is maximal and will set that angle.
 
−
**Take a Moller run at the new angle and the current position of the half-wave plate (HWP), IN. Polarization uncertainty must be <=1.5%.
 
−
**Ask MCC to change the position of the HWP to OUT. Take a Moller run. Polarization uncertainty must be <=1.5%.
 
−
**End of Spin Dance. Record the new value of the Wien angle.
 
−
* Ask MCC to take the beam away, turn off the tagger magnet, and degauss it. Ask MCC to unmask our FSDs.
 
−
* Retract the blank collimator and put the 20-mm collimator on the beam line.
 
−
* With beam off, turn all detectors' HV ON, except for MVT, which needs to be brought to "HV_FullField".
 
−
* Ask for 5 nA beam. Check that the beam positions, the rates of the beam halo scalers, FSD scalers, detector scalers, and the FTCal asymmetries are consistent with the reference values at the same current (see References and Standards above). If beam positions are off, ask MCC to engage the orbit locks. If orbits locks are engaged, but the beam positions are not up to specs, call the RC.
 
−
* If beam looks good, ask MCC for 35-nA beam and start taking production data. Each run is 2-hours long.
 
−
** Take the first run with PROD66_PIN and $CLON_PARMS/trigger/rgb_v1.trg.
 
−
** Take the rest of the runs with PROD66 and $CLON_PARMS/trigger/rgb_v1.trg.
 
−
-->
 
−
 
 
−
<b> Plan for 12 Feb </b>
 
−
 
 
−
Spin Dance is complete. Results [[Media:SpinDance_11Feb.pdf | here]]. Wien angle: 34 deg; measured polarization HWP IN: 85.4+-1.5; measured polarization HWP OUT: 83.6+-1.5. HWP is now OUT.
 
−
 
 
−
We run with trigger file rgb_v2.rg, which provides the same trigger as v1 (v0) but has some built-in checks of the muon trigger.
 
−
 
 
−
* Run 6197 ongoing with PROD66 and rgb_v2.trg. Take data for 2 hours. 35 nA.
 
−
* Expect a request from the trigger experts (Sergei, Valeri, Ben) to stop running in order to measure delay curves of the trigger. As soon as the request is made, stop the ongoing run and let the experts do their study.
 
−
* If a request for a run (about 1-hour long) is made by Rafo, Valeri, and Ben with a random trigger to validate the electron trigger (after Ben corrected the 35-ns shift observed in the trigger signals). Rafo will be present in the counting house to setup DAQ and check the data stream. As soon as he is ready to setuo and take the run, stop the ongoing data taking and let him proceed. After the run is finished, go back to PROD66, rgb_v2.trg and continue taking data.
 
−
* For the rest of the day, take 2-hrs long runs with <b> PROD66 </b> and <b> rgb_v2.trg </b>.
 
−
* Complete all tasks as speficied on this page "Once per Run" and "Once per Shift".
 
  
  
Line 252: Line 192:
 
* In case of loss of communication with IOCBTARG, follow instructions at https://logbooks.jlab.org/entry/3502218
 
* 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.
 
* 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.
 
* Check for and read any comments to log-book entries made during your shift.
  
Line 263: Line 201:
 
* Document any beam condition change and send scaler GUIs to HBLOG
 
* Document any beam condition change and send scaler GUIs to HBLOG
 
* [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side.
 
* [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side.
−
# Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
+
* Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
−
# 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.
 
* Monitor the SVT Slow Controls status, post plot of current stability in the HBSVT elog once per shift.
 
* As of 9th of February, once per shift stop and start the gas flow of the FTT (see logbook entry [https://logbooks.jlab.org/entry/3649533] for more details. Check the FTT HV after the procedure. If it is Off, check the status of all gas interlocks, reset the one that is at "Fault" and turn the FTT HV back ON.
 
* As of 9th of February, once per shift stop and start the gas flow of the FTT (see logbook entry [https://logbooks.jlab.org/entry/3649533] for more details. Check the FTT HV after the procedure. If it is Off, check the status of all gas interlocks, reset the one that is at "Fault" and turn the FTT HV back ON.
Line 287: Line 224:
  
 
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.
 
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: <font color=red>''' ''' 2C24A (X= 0.16 mm, Y= 0.26 mm) ''', '''2H01 (X=3.00 mm, Y= -1.00 mm)''' </font>
 
  
 
* '''Note 4: FTOF HVs: The goal is to minimize the number of power cycles of the dividers.
 
* '''Note 4: FTOF HVs: The goal is to minimize the number of power cycles of the dividers.

Revision as of 16:51, 13 February 2019

[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: Stepan Stepanyan

PDL: Maurizio Ungaro


References and Standards:

(last update 2/10/2019- 12:00 PM)


Nominal Beam Positions

  • 2H01, X: +3.0 mm, Y: -1.0 mm
  • 2C24, X: +0.16 mm, Y: 0.26 mm

FSD Thresholds

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

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

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

Reference Monitoring Histograms (20 nA, production trigger) [6]

Reference Monitoring Histograms (35 nA, production trigger) [7]

Reference Scalers and Halo-Counter Rates:

  • Well-tuned CW beam on FC, Full LD2 target, CLAS12 ON: 5 nA [8], 10 nA [9], 20 nA [10], 30 nA [11], 40 nA [12], 50 nA [13], 60 nA [14], 75 nA [15]
  • Well-tuned CW beam on FC, Empty Target, CLAS12 OFF: 5 nA [16]
  • Well-tuned beam during Moller run [17]
  • Well-tuned beam on Tagger Dump at 5 nA during harp scans: [18]

SVT acceptable currents: <10 nA (typically < 1 nA) with no beam and no HV; ~< 400 nA (HV ON, no beam); 10 nA [19], 20 nA [20], 30 nA [21], 40 nA [22], 50 nA [23], 60 nA [24], 75 nA [25]

Run Plan:

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


Plan for 13-14 Feb


After random trigger run, take 2-hrs long runs with PROD66 and rgb_v3.trg .


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.
  • 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.
  • 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.
  • As of 9th of February, once per shift stop and start the gas flow of the FTT (see logbook entry [26] for more details. Check the FTT HV after the procedure. If it is Off, check the status of all gas interlocks, reset the one that is at "Fault" and turn the FTT HV back ON.

Every Run:

  • Log screenshots of:
    • main scaler GUI display (both at the begining and at the end of run)
    • Detector occupancy plots from clas12mon
    • Trigger rate gui
    • Beam strip charts
  • Fill out the run info in run list at the beginning and at the end of each run.
  • Compare the monitoring histograms from clas12mon to the reference and troubleshoot as needed. 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.


  • 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 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, 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 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: [27]
  • 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.
    • 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 18: 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.


Clas12design.png

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