Difference between revisions of "Run Group A"

Revision as of 10:06, 14 March 2019

See guidance for BTA in Beam Time Accounting User Guide.

Manuals

DC
FTOF
ECAL
LTCC
HTCC
RICH: expert novice
CTOF
CND
SVT
MVT
- MVT turn on procedure
FT
Beamline
Torus Power-Up and Power-Down Procedure
Solenoid Power-Up and Power-Down Procedure
Cryo Target Operation manual
DAQ
Slow Controls

Procedures

JLab Logbooks

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 A, Spring 2019
Beam energy 10.2 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

RC: Daniel S. Carman

(757) 575-7540
9 575 7540 from Counting Room
carman@jlab.org

PDL: Maurizio Ungaro

(757) 876-1789
9 876-1789 from Counting Room
ungaro@jlab.org

Run Plan: March. 20-27

Put run plan here

DAQ config: PROD66

Trigger file: rga_vXX.trg

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"

Weekly plan for remainder of the run:

Moller runs after coming back a long down due to beam studies of RF recovery (Mondays or Tuesdays)
empty target run at 150 nA, one 4 hour run with production DAQ configuration
low luminosity runs for 8 hours, two 4-hour long runs with full target at 5 nA
rest of the time production running at 50 nA on full target

References and Standards:

(last update 3/13/2019- 12:00 PM)

Restoration of Beam to Hall B

Nominal Beam Positions

2H01, X: +3.0 mm, Y: -1.0 mm
2C24, X: +0.25 mm, Y: 0.35 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]
Reference FTC histogram for 5 nA running: [19]

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

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.

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
Monitor the SVT Slow Controls status, post plot of current stability in the HBSVT elog once per shift.
As of March 9 we no longer have to stop and start the gas flow of the FTT (see logbook entry [27] for more details).

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: 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: 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 4: 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 5: 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 6: Any request for a special run or change of configuration has to be approved by the RC & documented

Note 7: 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 8: Reset CLAS12MON frequently to avoid histogram saturation.

Note 9: Shift workers must check the occupancies! Use this tool to compare to previous runs: [28]

Note 10 When you have to turn the whole 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

NOTE 11 Check the vacuum periodically, make sure vacuum id not higher than 5e-5

NOTE 12 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 13 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: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766

NOTE 15:

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

Difference between revisions of "Run Group A"

Revision as of 10:06, 14 March 2019

Shift Schedule

Shift Checklist

Hot Checkout

Beam Time Accounting

Manuals

Procedures

JLab Logbooks

RC: Daniel S. Carman

PDL: Maurizio Ungaro

Run Plan: March. 20-27

References and Standards:

General Instructions:

Webcams

Manuals

Epics on the web

Fall 2018 Run

Spring 2018 Run

Hall-B

Run lists

Accelerator

Bluejean meetings

Navigation menu

Search

@@ Line 65: / Line 65: @@
 = Short Term Schedule =
 <center><font color=blue size=4>
-''' CLAS12 Run Group A, Fall 2018 </font> '''<br>
+''' CLAS12 Run Group A, Spring 2019 </font> '''<br>
-''' Beam energy 10.6 GeV (5 pass) '''<br>
+''' Beam energy 10.2 GeV (5 pass) '''<br>
 ''' Important: Document all your work in the logbook! '''<br>
-''' Remember to fill in the [https://docs.google.com/spreadsheets/d/1NpojoOi7_gTt_abxgKoHBlofOL7iNWDrtYuiOJ1zoMw/edit?usp=sharing run list] at the beginning and end of each run <!--(clas12run@gmail.com can fill the run list)'''<br>-->
+''' Remember to fill in the [https://docs.google.com/spreadsheets/d/1NpojoOi7_gTt_abxgKoHBlofOL7iNWDrtYuiOJ1zoMw/edit?usp=sharing run list] at the beginning and end of each run
-<!--
-*'''<font color=red size=6> Shifts are cancelled until 08:00 Saturday September 22, 2018 </font>'''<br>
--->
 </center>
-== RC: Raffaella De Vita ==
+== RC: Daniel S. Carman ==
 * (757) 575-7540
 * 9 575 7540 from Counting Room
-* [mailto:devita@jlab.org devita@jlab.org]
+* [mailto:carman@jlab.org carman@jlab.org]
-== PDL: Eugene Pasyuk ==
+== PDL: Maurizio Ungaro ==
 *  (757) 876-1789
 * 9 876-1789 from Counting Room
-* [mailto:pasyuk@jlab.org pasyuk@jlab.org]
+* [mailto:ungaro@jlab.org ungaro@jlab.org]
 <br>
+{| {{TableStyle1}}
-* '''Note 1: Be very mindful of the background rates in the halo counters, rates in the detectors, and leakage currents in the SVT (<0.4 uA) for all settings to ensure that they are at safe levels.'''
+| valign=top width=50% |
-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 '''
+== <font color=blue>''' Run Plan: March. 20-27'''</font>==
-"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: <font color=red>''' ''' 2C24A (X=0.2 mm, Y=0.2 mm) ''', '''2H01 (X=0.3 mm, Y=-0.9 mm)''' </font>
+* Put run plan here
-* '''Note 4: Do not turn OFF FTOF HVs, even during the beam tune with CW beam (turn off when doing a Moller run or if there is tuned/pulsed beam in the upstream beamline)'''
-* '''Note 5: In case of a Torus and/or Solenoid Fast Dump do the following:
+DAQ config: PROD66
-*# Notify MCC to request beam OFF and to drop Hall B status to Power Permit
-*# Call Engineering on-call
-*# 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
-*# Notify Run Coordinator
-*# Turn off all detectors'''
-*'''Note 6: When beam is being delivered to the Faraday Cup:'''
+Trigger file: rga_vXX.trg
-*# the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state <font color=red>UNMASKED</font>
-*# No changes to the FSD threshold should be made without RC or beamline expert approval
-<!--*'''Note 7: Do not turn on the SVT or MM - only the SVT or MM expert can do that''' -->
-*'''Note 7: Any request for a special run or change of configuration has to be approved by the RC & documented'''
+<!--* Hall-B should be closed before 2 pm. As soon Hall will be in beam permit, energize the tagger. When beam is available proceed with establishing the beam on the tagger yoke dump (see instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]).
-*'''Note 8: Carefully check the BTA every hour and run the script <font color=red>btaGet.py</font> to print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.'''
+* Perform Moller runs, use "right" target, two measurements with 1/2 wave plate IN (as is now) then OUT. Leave 1/2 wave plate in "IN" position for data taking.
-*'''Note 9: Reset CLAS12MON frequently to avoid histogram saturation.'''
+* When finished the Moler runs
+* If beam is acceptable degauss the tagger magnet and send the beam to Faraday cup, make sure beam is clearly seen on the downstream viewer and the halo counter rates are as expected (compare to earlier rates). Perform 2H01 harp scan(follow instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]). , ''Note harp wire was fixed''
-*'''Note 10: Shift workers must check monitoring histograms! Use this tool to compare to reference: [https://clas12mon.jlab.org/mon12/histograms/?reference=3630375]'''
+* After beam is established on FC and the beam profile is acceptable, start bringing CLAS12 is ON, make sure beam position and detector and halo rates are as expected for full target.
-*'''Note 11 Do not Turn OFF MVT HV: Instead go to 'Restore settings' from the MVT overview screen:
-*# SafeMode.snp for beam tuning and Moeller runs
-*# MV_HV_FullField.snp for full solenoid field
-*# 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 CFD crate'''
-After the CAMAC crate 1 holding the CND CFD boards is switched
-off for any reason, it is mandatory to reset the associated thesholds typing the
-following command from any clon machine terminal:
- >> $CODA/src/rol/Linux_x86_64/bin/cnd-cfd-thresh -w 0
-Check the CND manual for further information.
-*'''NOTE 14: As of 10/25, the issue of detector scalers being frozen and starting a new run has been resolved.''' 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 15: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766'''
-{| {{TableStyle1}}
-| valign=top width=50% |
-== <font color=blue>''' Run Plan:'''</font>==
-<i>(Updated: Nov. 25, 2018 at 20:00)</i>
-* Take production data with configuration PROD66 and '''trigger_v22_1_no_dc_roads.trg''' at '''50''' nA.
-* Beam will be terminated around 8am on 11/26 for the planned energy change. At that time magnets will be ramped down while detectors will be left on unless the detector experts will request to turn them off. The Hall will be in restricted access.
+* Continue production data on LH2 target at 50 nA (<b> if the trigger rate will be higher than 20 kHz, lower beam current to stay <~20 kHz</b>. Data taking is 4 hour-long runs with DAQ configuration '''PROD66''', and trigger '''rga_vXX.trg'''.
+<font color=red>'' [https://clas12mon.jlab.org/mon12/histograms/?reference=3630375 Compare the monitoring histograms from clas12mon to the reference and troubleshoot as needed.] ''</font>  -->
-<!--'''Analysis of calibrated run 5215, with 1 ph.e. threshold in the trigger for HTCC, shows the same dips in the phi-distributions of electrons at certain thetas. So, looks like problem of dips is not related to the trigger thresholds. We will go back to nominal trigger condition (file trigger_v21_0.trg) with 2 ph.e. threshold for HTCC.
+<b><font color=red> At the end of each run, follow the standard DAQ restart sequence ''' <br>
-New rigger file is trigger_v21_0_1phe.trg, with HTCC threshold at 1 ph.e., will stay with this setting until electron efficiency will be checked in offline analysis.'''-->
+''(Note, this might be different from the instructions coming up on RunControl.)''
-'''<font color=red> Make sure to save Roc Rates (MB/s) GUI to logbook for each run together with beam screens and trigger GUI </font>'''
+* "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"
+</font></b>
-<!--'''Mini-spin dance with Wien angle at 50 degrees (present setup), 25 degrees and 75 degrees will be diverted to later time (Wednesday or Thursday).''' -->
+<b> Weekly plan for remainder of the run: </b>
+* Moller runs after coming back a long down due to beam studies of RF recovery (Mondays or Tuesdays)
-* <font color=blue> ''' Make sure that the FSD thresholds are set correctly and they are unmask when ready to receive beam to the FC @50 nA
+* empty target run at 150 nA, one 4 hour run with production DAQ configuration
-** Upstream 2000
+* low luminosity runs for 8 hours, two 4-hour long runs with full target at 5 nA
-** Midstream 1000
+* rest of the time production running at 50 nA on full target
-** Downstream 900000
-** BOM 20000
-** Dwell time 5 ms
-'''</font>
+== <font color=blue>''' References and Standards:'''</font>==
+''(last update 3/13/2019- 12:00 PM)''
+<b> Restoration of Beam to Hall B</b>
-== <font color=blue>''' Shift Worker Notes:'''</font>==
+<b> Nominal Beam Positions </b>
+*2H01, X: +3.0 mm, Y: -1.0 mm
+*2C24, X: +0.25 mm, Y: 0.35 mm
-<!-- * From time to time, we might experience trigger bit issues (FT bits: 24, 25, 26, 27). Bit 26 might not trigger the alarm but when this issue happens it will count abnormally high. For the time being, shift leaders can try to do the sequence of End->Cancel->Reset, roc_reboot adcft1 (and adcft2, adcft3), make sure the ROCs are connected, then Download->Prestart->Go. If this does not work, repeat the sequence and add "Configure" in front of "Download". If the trig issue persists, continue to take production data without fixing it -- please make sure you log this infor in the RCDB "Comment" field. -->
+<b> FSD Thresholds </b>
+* Upstream: 2000 Hz
+* Midstream: 2000 Hz
+* Downstream: 500000 Hz
+* BOM: 35000
-* If the machine is down for more than 30 min ask for low current first 5 nA ,make sure that the beam is stable both in position and current, check that the rates are OK on all the detectors and halo counters. Then ask for 45 nA and continue data for production. If there are issues with the beam call RC. Sometimes MCC operator may ask to deliver tuned mode beam --- do not accept it. We need CW beam sent to the Faraday cup. If there is indeed a need for tuned beam, it should be sent to the tagger dump with the tagger magnet on. If you are uncertain, please call RC/PDL.
+<b> Reference Harp Scans for Beam on Tagger Dump: </b> 2C21 [https://logbooks.jlab.org/entry/3649356], 2C24 [https://logbooks.jlab.org/entry/3649362]
-<!--* Sometimes, a couple RICH channel scalers go to 0 and there is no alarm, even though the "# of fibers connected" would be shown to be the correct 138. Shift takers therefore should periodically, especially at the end of run, check the RICH scalers GUI. If there is an issue:-->
+<b> Reference Harp Scans for Beam on Faraday Cup: </b> 2C21 [https://logbooks.jlab.org/entry/3649467], 2C24 [https://logbooks.jlab.org/entry/3649472], 2H01 [https://logbooks.jlab.org/entry/3656599]
-* 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.
-'''In case of other questions or uncertainties of what to do, call the RC'''
+<b> Reference Monitoring Histograms (20 nA, production trigger) </b> [https://logbooks.jlab.org/entry/3650218]
+<b> Reference Monitoring Histograms (35 nA, production trigger) </b> [https://logbooks.jlab.org/entry/3650729]
-<!--'''[[Every Shift:]]'''
+<b> Reference Scalers and Halo-Counter Rates: </b>
-*Follow run plan as outlined by RC
+* Well-tuned CW beam on FC, Full LD2 target, CLAS12 ON: 5 nA [https://logbooks.jlab.org/entry/3649861], 10 nA [https://logbooks.jlab.org/entry/3649888], 20 nA [https://logbooks.jlab.org/entry/3649905], 30 nA [https://logbooks.jlab.org/entry/3649916], 40 nA [https://logbooks.jlab.org/entry/3649938], 50 nA [https://logbooks.jlab.org/entry/3649959], 60 nA [https://logbooks.jlab.org/entry/3649970], 75 nA [https://logbooks.jlab.org/entry/3649985]
-* If any concern about beam stability, ask MCC if orbit locks are on (they should be).
+* Well-tuned CW beam on FC, Empty Target, CLAS12 OFF: 5 nA [https://logbooks.jlab.org/entry/3649436]
-* Keep shift summary up to date in HBLOG. Record all that happens.
+* Well-tuned beam during Moller run [https://logbooks.jlab.org/entry/3649364]
-* Document any beam condition change and send scaler GUIs to HBLOG
+* Well-tuned beam on Tagger Dump at 5 nA during harp scans: [https://logbooks.jlab.org/entry/3649358]
-* [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side.
+* Reference FTC histogram for 5 nA running: [https://logbooks.jlab.org/entry/3665122]
-*Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
+<b> SVT acceptable currents: </b> <10 nA (typically < 1 nA) with no beam and no HV; ~< 400 nA (HV ON, no beam); 10 nA [https://logbooks.jlab.org/entry/3649889], 20 nA [https://logbooks.jlab.org/entry/3649911], 30 nA [https://logbooks.jlab.org/entry/3649920], 40 nA [https://logbooks.jlab.org/entry/3649941], 50 nA [https://logbooks.jlab.org/entry/3649960], 60 nA [https://logbooks.jlab.org/entry/3649972], 75 nA [https://logbooks.jlab.org/entry/3649986]
-'''[[Every Run:]]'''
- ''Log screenshots of:''
-* main scaler GUI display
-* Detector occupancy plots
-* Trigger rate GUI
-* Statistics of DAQ rates GUI
-* Beam strip charts
-* FT-Cal FADC scalers
--->
 | valign=top |
@@ Line 198: / Line 163: @@
 ==<font color=blue>''' General Instructions''':</font>==
-* For a given beam current, compute the FSD thresholds according to the [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf 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.
+* 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.
-<!--* All jscaler iocs (iocjscalerX) on the health screen (under DAQ tab) must be restarted after every DAQ prestart is completed. Follow this link for detailed instructions https://userweb.jlab.org/~baltzell/CLAS12/SC/jlabScalersOps.txt-->
+* Check for and read any comments to log-book entries made during your shift.
-* Check that no unnecessary 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.
-* Reference harp scans: [https://logbooks.jlab.org/entry/3571664 2C21], [https://logbooks.jlab.org/entry/3571676 2C24], [https://logbooks.jlab.org/entry/3571859 2H01]
 '''Every Shift:'''
-*Follow run plan as outlined by RC
+* 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
 * [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side.
-* When you do BTA keep track of of BANU. Include at the end of shift summary log details of BANU: the reason and duration.
+* 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 [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
-<!-- * Once a shift between the runs Restart FTT gas flow. Follow these steps:
+* Monitor the SVT Slow Controls status, post plot of current stability in the HBSVT elog once per shift.
-** From main clascss open '''FTT Gas'''
+* As of March 9 we no longer have to stop and start the gas flow of the FTT (see logbook entry [https://logbooks.jlab.org/entry/3665232] for more details).
-** Click '''STOP''' and then '''START'''. If you do it quickly interlock will not trip. If interlock trips it will turn OFF FTT HV and you will get an alarm. If this happens do the following:
-*** On '''FTT Gas''' make sure the gas is flowing
-*** Open '''FTT Soft Interlocks'''. At the bottom of the screen in the 'FTT gas' section click '''Reset''' for those in red.
-*** Turn FTT HV back ON.
-** If not sure or have problems call FT on-call. -->
 '''Every Run:'''
-'' Log screenshots of the following screens, and
+*Log screenshots of:
-<font color="orange"> make sure at the moment you capture the screen the beam is ON </font> ''
+** main scaler GUI display
-* main scaler GUI display
+** Trigger rate gui
-* Detector occupancy plots
+** Beam strip charts
-* Trigger rate gui
+** FTC scalers
-* Roc Rates (MB/s) gui
+* Fill out the run info in [https://docs.google.com/spreadsheets/d/1NY1GNIZXPtpB9u4QwP6eNRSrvDkCzFmhQg5RR3V3j7E/edit#gid=0 run list] at the beginning and at the end of each run.
-* Beam strip charts
+* <b> 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.
-* FTCalo FADC scalers
+* Same holds for FT.</b>
 |}
+* '''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: 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 4: In case of a Torus and/or Solenoid Fast Dump do the following:
+*# Notify MCC to request beam OFF and to drop Hall B status to Power Permit
+*# Call Engineering on-call
+*# 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
+*# Notify Run Coordinator
+*# Turn off all detectors'''
+*'''Note 5: When beam is being delivered to the Faraday Cup:'''
+*# the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state <font color=red>UNMASKED</font>
+*# No changes to the FSD threshold should be made without RC or beamline expert approval
+*'''Note 6: Any request for a special run or change of configuration has to be approved by the RC & documented'''
+*'''Note 7: Carefully check the BTA every hour and run the script <font color=red>btaGet.py</font> to print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.'''
+*'''Note 8: Reset CLAS12MON frequently to avoid histogram saturation.'''
+*'''Note 9: Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/?reference=3650729]'''
+<!--[https://clas12mon.jlab.org/mon12/histograms/?reference=3621580]'''-->
+*'''Note 10 When you have to turn the whole MVT off, do not press "All HV OFF": Instead go to 'Restore settings' from the MVT overview screen:
+*# SafeMode.snp for beam tuning and Moeller runs
+*# MV_HV_FullField.snp for full solenoid field
+*# MV_HV_MidField.snp wgeb solenoid < 4T
+'''
+*'''NOTE 11 Check the vacuum periodically, make sure vacuum id not higher than 5e-5 '''
+*''' NOTE 12 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 13 ''' 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: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766'''
+*'''NOTE 15:'''
+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. <u>Please, note </u> 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 16:''' 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.
 = Monitoring =