Difference between revisions of "Run Group A"

From clas12-run
Jump to: navigation, search
(Short Term Schedule)
(Phone Numbers)
(76 intermediate revisions by 7 users not shown)
Line 72: Line 72:
 
</center>
 
</center>
  
== RC: Daniel S. Carman ==
+
== RC: Nick Markov ==
 
* (757) 575-7540   
 
* (757) 575-7540   
 
* 9 575 7540 from Counting Room
 
* 9 575 7540 from Counting Room
* [mailto:carman@jlab.org carman@jlab.org]
+
* [mailto:markov@jlab.org markov@jlab.org]
 
   
 
   
 
== PDL: Maurizio Ungaro ==
 
== PDL: Maurizio Ungaro ==
Line 86: Line 86:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
== <font color=blue>''' Run Plan: March. 25-30, 2019'''</font>==
+
== <font color=blue>''' Run Plan: April 8-15, 2019'''</font>==
(Last updated: March 22, 2019 @ 10:03 a.m.)
+
(Last updated: April 12th, 2019 @ 19:00)
  
DAQ config: PROD66
+
<b>DAQ config: PROD66; Trigger file: rga_v2.trg</b>
Trigger file: rga_vXX.trg
+
<!--
 
+
* When the Hall is in beam permit:
* As soon Hall will be in beam permit, energize the tagger. Make sure the target is full and all detectors are off (except for MVT in safe mode).
+
** Energize the tagger
** The solenoid should be at -100% field (2416 A) and the torus should be at -100% field (3770 A negatives inbending).
+
 
** The liquid-hydrogen target should be full  
 
** The liquid-hydrogen target should be full  
 +
** All detectors should be off (except for MVT in safe mode).
 +
** The solenoid should be at -100% field (2416 A) and the torus should be at -100% field (3770 A negatives inbending).
  
 
* When beam is available:
 
* When beam is available:
Line 102: Line 103:
 
* If beam is acceptable:
 
* If beam is acceptable:
 
** Degauss the tagger magnet
 
** Degauss the tagger magnet
** Set the FSD thresholds(upstream 2000, midstream 1000, downstream 750000, BOM 30000, 5.0 ms dwell time)
+
** Set the FSD thresholds(upstream 2000, midstream 2000, downstream 500000, BOM 35000, 5.0 ms dwell time)
 
** Send 5 nA beam to Faraday cup and make sure beam is clearly seen on the downstream viewer and the halo counter rates are acceptable.
 
** Send 5 nA beam to Faraday cup and make sure beam is clearly seen on the downstream viewer and the halo counter rates are acceptable.
 
** Perform 2H01 harp scan (follow instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]).
 
** Perform 2H01 harp scan (follow instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]).
  
* After beam is established on FC and the beam profile is acceptable, turn on the CLAS12 detectors
+
* After beam is established on FC and the beam profile is acceptable, turn on the CLAS12 detectors.
 +
 
 +
* Take low current production at 10 nA for 4 hr.
 +
-->
 +
<!--
 +
* Take production data at 50 nA in 4 hr runs!
 +
 
 +
*Note: <font color=red>DO NOT IGNORE</font> unsafe FSD masking alarm! Follow alarm guidance.
 +
Take production data at 50nA for 4 hr until he swing shift.
 +
 
 +
Starting from the swing shift,
 +
 
 +
* Take 2 hours random trigger run at 10 nA using  rgb_v9_1_faraday_noprescale.trg trigger file and beam blocker removed. Expect 10 kHz DAQ rate. Change the DAQ alarm limits by going to DAQ /CLAS12 Trigger /Menu /Alarm Settings Expert/ Set All Normalized Rate Limits when the beam and rates are stable.
 +
 
 +
* Take 20 minutes random trigger run at 50 nA using  rgb_v9_1_presxcale_3.trg trigger file and beam blocker removed. Expect 15 kHz DAQ rate. Change the DAQ alarm limits by going to DAQ /CLAS12 Trigger /Menu /Alarm Settings Expert/ Set All Normalized Rate Limits when the beam and rates are stable.
 +
 
 +
* Take 6 hours low luminosity run at 10 nA with the beam blocker in and rga_v2.trg trigger. Change the DAQ alarm limits by going to DAQ /CLAS12 Trigger /Menu /Alarm Settings Expert/ Set All Normalized Rate Limits when the beam and rates are stable.
 +
 
 +
* At 2 am empty the target and run 150 nA beam until the beam is taken away with rga_v2.trg and the beam blocker in. Change the DAQ alarm limits by going to DAQ /CLAS12 Trigger /Menu /Alarm Settings Expert/ Set All Normalized Rate Limits when the beam and rates are stable. Change the BTA accounting limits in the Beamlin/BTA config (replace the upper limit with 160 nA).
 +
 
 +
 
 +
The beam is expected to be back around 3-15 pm on Monday, April 8'th.
 +
Change HWP to "OUT" and take a Moeller run.
 +
After establishing the physics-quality beam (follow the procedure outlined in https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf) take production data at in 4 hours runs at 50 nA, DAQ config: PROD66; Trigger file: rga_v2.trg.
 +
On the Torus/Magnet power Suppy monitor torus MPS Control Comm 
 +
-->
 +
 
 +
Take production data at in 4 hours runs at 50 nA, DAQ config: PROD66; Trigger file: rga_v2.trg.
 +
 
 +
On the Torus/Magnet power Suppy monitor torus MPS Control Comm  light. It should be green. If not, contact Magnet group.
 +
 
 +
<b>Pay special attention to scalers of the PCAL and FTOF in sector 5 (under scalers/CLAS12 Forward Carriage/Sector 5) and make sure there are no dead channels in PCAL and FTOF. Also, when looking at monitoring histograms, pay special attention to sector 5 for the same detectors.</b>
 +
<b> We had a problem with scalers in sector FTOF 4 which went out. Please monitor it very closely (along with sector 5) and if anyhitng happen contact Sergey (DAQ expert) right away.</b>
 +
 
 +
<font color=red>
 +
After the beam is off at 6 am on Monday morning:<br>
 +
- turn the HTCC HV off;<br>
 +
- turn the LTCC HV off;<br>
 +
- turn the FT HV off (only HV!);<br>
 +
 
 +
- <b>Do Not turn BAND HV Off</b>.<br>
 +
- <b>Do Not turn EC/PCAL HV Off</b>.<br>
 +
- <b>Do Not turn CTOF and FTOF HV Off</b>.<br>
 +
- <b>Do Not turn RICH HV Off</b>.<br>
 +
- <b>Do Not turn SVT HV Off</b>.<br>
  
* Allow trigger group to setup and test the RG-A trigger. Take 4 hr of random trigger data.
+
</font>
  
* Take low current production run for 4 hr at 5 nA with DAQ configuration '''PROD66''', and trigger '''rga_vXX.trg'''.  
+
*Note: <font color=red>DO NOT IGNORE</font> unsafe FSD masking alarm! Follow alarm guidance.
  
* Take production data at 50 nA; take 4 hr 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>
 
<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>
Line 125: Line 169:
 
** "configure", "download", "prestart", "go"
 
** "configure", "download", "prestart", "go"
 
</font></b>
 
</font></b>
 
<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)
 
* 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
 
  
 
== <font color=blue>''' References and Standards:'''</font>==
 
== <font color=blue>''' References and Standards:'''</font>==
''(last update 3/13/2019- 12:00 PM)''
+
''(last update March 27, 2019 @ 8:53 a.m.)''
  
 
<b> Restoration of Beam to Hall B</b>
 
<b> Restoration of Beam to Hall B</b>
Line 147: Line 185:
 
* BOM: 35000
 
* BOM: 35000
  
<b> Reference Harp Scans for Beam on Tagger Dump: </b> 2C21 [https://logbooks.jlab.org/entry/3649356], 2C24 [https://logbooks.jlab.org/entry/3649362]
+
<b> Reference Harp Scans for Beam on Tagger Dump: </b> 2C21 [https://logbooks.jlab.org/entry/3672101], 2C24 [https://logbooks.jlab.org/entry/3672102]
 
+
<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]
+
  
<b> Reference Monitoring Histograms (20 nA, production trigger) </b> [https://logbooks.jlab.org/entry/3650218]
+
<b> Reference Harp Scans for Beam on Faraday Cup: </b> 2H01 [https://logbooks.jlab.org/entry/3672120]
  
<b> Reference Monitoring Histograms (35 nA, production trigger) </b> [https://logbooks.jlab.org/entry/3650729]
+
<b> Reference Monitoring Histograms</b> 5 nA production trigger [https://logbooks.jlab.org/entry/3672274], 50 nA, production trigger [https://logbooks.jlab.org/entry/3672136] (to be updated)
  
 
<b> Reference Scalers and Halo-Counter Rates: </b>  
 
<b> Reference Scalers and Halo-Counter Rates: </b>  
* 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]
+
* Well-tuned CW beam on FC, Full LH2 target, CLAS12 ON: 5 nA [https://logbooks.jlab.org/entry/3672117], 50 nA [https://logbooks.jlab.org/entry/3672129]  
 
* Well-tuned CW beam on FC, Empty Target, CLAS12 OFF: 5 nA [https://logbooks.jlab.org/entry/3649436]
 
* Well-tuned CW beam on FC, Empty Target, CLAS12 OFF: 5 nA [https://logbooks.jlab.org/entry/3649436]
 
* Well-tuned beam during Moller run [https://logbooks.jlab.org/entry/3649364]
 
* Well-tuned beam during Moller run [https://logbooks.jlab.org/entry/3649364]
Line 162: Line 198:
 
* Reference FTC histogram for 5 nA running: [https://logbooks.jlab.org/entry/3665122]
 
* Reference FTC histogram for 5 nA running: [https://logbooks.jlab.org/entry/3665122]
  
<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]
+
<b> SVT acceptable currents: </b> 1 uA
  
 
| valign=top |
 
| valign=top |
Line 174: Line 210:
 
* 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.
 
* 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.
 +
 +
'''Once Per Day (on day shift):'''
 +
* Complete RICH recovery procedure - see Note: 14 below
  
 
'''Every Shift:'''
 
'''Every Shift:'''
Line 185: Line 224:
 
* 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]
 
* 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 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).
+
 
 
'''Every Run:'''
 
'''Every Run:'''
  
Line 202: Line 241:
 
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.
 
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 '''
+
* '''Note 2: FTOF HVs: The goal is to minimize the number of power cycles of the dividers.
"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 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.
 
** 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.
 
** 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:
+
* '''Note 3: 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
 
*# Notify MCC to request beam OFF and to drop Hall B status to Power Permit
 
*# Call Engineering on-call
 
*# Call Engineering on-call
Line 219: Line 253:
 
*# Turn off all detectors'''
 
*# Turn off all detectors'''
  
*'''Note 5: When beam is being delivered to the Faraday Cup:'''
+
*'''Note 4: 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>
 
*# 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
 
*# 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 5: 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 6: 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 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 [https://logbooks.jlab.org/entry/3667416]'''
  
*'''Note 9: Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/?reference=3650729]'''
+
*'''Note 8: 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]'''-->
 
<!--[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:
+
*'''Note 9: 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
 
*# SafeMode.snp for beam tuning and Moeller runs
 
*# MV_HV_FullField.snp for full solenoid field
 
*# MV_HV_FullField.snp for full solenoid field
 
*# MV_HV_MidField.snp wgeb solenoid < 4T
 
*# MV_HV_MidField.snp wgeb solenoid < 4T
 
'''
 
'''
*'''NOTE 11 Check the vacuum periodically, make sure vacuum id not higher than 5e-5 '''
+
*'''Note 10: Check the vacuum periodically, make sure vacuum is not higher than 5e-5 '''
  
*''' NOTE 12 Always reset the CFD threshold after all power off/on on the CND CAMAC crate'''  
+
*''' 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
 
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
 
following command from any clon machine terminal: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0
Line 245: Line 279:
 
If this command is failing and the crate is not responding, reboot it as follows: roc_reboot camac1
 
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 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: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766'''
+
*'''Note 13: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766'''
  
*'''NOTE 15:'''  
+
*'''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. <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.  
 
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.
 
** 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.
+
*'''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
  
 
= Monitoring =
 
= Monitoring =
Line 280: Line 316:
 
|}
 
|}
  
== Spring 2019 Run ==
+
== Fall 2018 Run ==
 
{| {{TableStyle1}}
 
{| {{TableStyle1}}
 
| valign=top |
 
| valign=top |
Line 289: Line 325:
 
|}
 
|}
  
== Spring 2019 Run ==
+
== Spring 2018 Run ==
  
 
{| {{TableStyle1}}
 
{| {{TableStyle1}}
Line 325: Line 361:
 
* Accelerator daily meetings notes (by Mauri) [https://www.evernote.com/pub/maureeungaro/pdldaily]
 
* Accelerator daily meetings notes (by Mauri) [https://www.evernote.com/pub/maureeungaro/pdldaily]
 
| valign=top |
 
| valign=top |
===Bluejean meetings===
+
===Bluejeans meetings===
 
+
* [https://bluejeans.com/230805731 Daily Run meeting] 230805731
* [https://bluejeans.com/7572697303] RGA RC and analysis meetings 7572697303
+
 
|}
 
|}
  

Revision as of 09:22, 19 March 2020

[edit]

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]

Person Phone Number
Run Coordinator (757) 575-7540 (cell)
Physics Division Liaison (757) 876-1789 (cell)
Shift Expert (757) 329-4846 (cell)
Remote Shifter (757) 310-7198 (cell)
MCC-OPS 7048
Crew Chief 7045
Crew Chief 9-876-3367 (cell)
Program Deputy 9-876-7997 (cell)
Engineering on-call 757 748-5048 (cell)
Engineering on-call secondary 757 897-9060 (cell)
Gate House Guard 5822
Location Phone Number
Hall-B Floor 5165
Hall-B Space Frame 5170, 5171
Hall-B Forward Carriage 5371
Hall-B Counting Room 5245 (Shift1), 5126 (Shift2)
Hall-B Counting Room 5244 (Expert)
Hall-B Gas Shed 7115
System Phone Number On-Call Person
DC (757) 748-5048 (cell) Engineering On-Call
SVT + MM (757) 541-7539 (cell) Yori Gotra Primary
SVT + MM (757) 753-7769 (cell) Rafo Paremuzyan (secondary)
ECAL (757) 810-1489 (cell) Cole Smith
FTOF/CTOF (757) 344-7204 (cell) Jose Carvajal
CND (757) 344-7204 (cell) Silvia Niccolai
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) Valery Kubarovsky
DAQ (757) 232-6221 (cell) Sergey Boiarinov
Slow Controls (757) 748-6922 (cell) Nathan Baltzell
Beamline (757) 303-3996 (cell) Eugene Pasyuk
Target (757) 822-9586 (cell) Bob Miller Primary
Target secondary (757) 897-9060 (cell) Denny Insley

Paging system in case the on-call
phone is unanswered

PageExpertScreenshot.png

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: Nick Markov

PDL: Maurizio Ungaro

Run Plan: April 8-15, 2019

(Last updated: April 12th, 2019 @ 19:00)

DAQ config: PROD66; Trigger file: rga_v2.trg

Take production data at in 4 hours runs at 50 nA, DAQ config: PROD66; Trigger file: rga_v2.trg.

On the Torus/Magnet power Suppy monitor torus MPS Control Comm light. It should be green. If not, contact Magnet group.

Pay special attention to scalers of the PCAL and FTOF in sector 5 (under scalers/CLAS12 Forward Carriage/Sector 5) and make sure there are no dead channels in PCAL and FTOF. Also, when looking at monitoring histograms, pay special attention to sector 5 for the same detectors. We had a problem with scalers in sector FTOF 4 which went out. Please monitor it very closely (along with sector 5) and if anyhitng happen contact Sergey (DAQ expert) right away.

After the beam is off at 6 am on Monday morning:
- turn the HTCC HV off;
- turn the LTCC HV off;
- turn the FT HV off (only HV!);

- Do Not turn BAND HV Off.
- Do Not turn EC/PCAL HV Off.
- Do Not turn CTOF and FTOF HV Off.
- Do Not turn RICH HV Off.
- Do Not turn SVT HV Off.

  • Note: DO NOT IGNORE unsafe FSD masking alarm! Follow alarm guidance.


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

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 March 27, 2019 @ 8:53 a.m.)

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: 2H01 [3]

Reference Monitoring Histograms 5 nA production trigger [4], 50 nA, production trigger [5] (to be updated)

Reference Scalers and Halo-Counter Rates:

  • Well-tuned CW beam on FC, Full LH2 target, CLAS12 ON: 5 nA [6], 50 nA [7]
  • Well-tuned CW beam on FC, Empty Target, CLAS12 OFF: 5 nA [8]
  • Well-tuned beam during Moller run [9]
  • Well-tuned beam on Tagger Dump at 5 nA during harp scans: [10]
  • Reference FTC histogram for 5 nA running: [11]

SVT acceptable currents: 1 uA

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
  • 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
    • 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 [12]
  • Note 8: Shift workers must check the occupancies! Use this tool to compare to previous runs: [13]
  • Note 9: 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 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