Difference between revisions of "Run Group A"

From clas12-run
Jump to navigation Jump to search
 
(400 intermediate revisions by 16 users not shown)
Line 11: Line 11:
 
* See guidance for BTA in '''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf Beam Time Accounting User Guide]'''.
 
* See guidance for BTA in '''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf Beam Time Accounting User Guide]'''.
 
<!-- ===[https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc#CLAS12_Operations_Documentation Operations Documentation]=== -->
 
<!-- ===[https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc#CLAS12_Operations_Documentation Operations Documentation]=== -->
 +
===[https://www.jlab.org/Hall-B/run-web/rga/ESAD_HallB-CLAS12_rgA.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rga/COO_HallB-CLAS12_rgA.pdf COO], [https://www.jlab.org/Hall-B/run-web/rga/RSAD_HallB-CLAS12_rgA.pdf RSAD], [https://www.jlab.org/div_dept/train/SAF111/Hall%20B%20worker%20Safety%20Training%20%28SAF111%29%20%2008%2001-12-1.pdf ERG] ===
  
 
| valign=top |
 
| valign=top |
 
===Manuals===
 
===Manuals===
 +
* [https://clasweb.jlab.org/wiki/images/c/c2/Band_om.pdf BAND]
 +
* [https://clasweb.jlab.org/wiki/images/4/4d/Beamline_manual.pdf Beamline]
 +
* [https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf CND]
 +
* [https://clasweb.jlab.org/wiki/images/c/c1/Shift_Worker_Manual_January_2018.pdf Cryo-Target]
 +
* [https://clasweb.jlab.org/wiki/images/0/0f/Ctof_manual.pdf CTOF]
 +
* [https://clasweb.jlab.org/wiki/images/a/ab/Opman_master.pdf DAQ]
 
* [https://clasweb.jlab.org/wiki/images/b/b2/Drift-chamber-operating-procedure.pdf DC]
 
* [https://clasweb.jlab.org/wiki/images/b/b2/Drift-chamber-operating-procedure.pdf DC]
 +
* [https://clasweb.jlab.org/wiki/images/a/a2/Ec_manual.pdf ECAL]
 +
* [https://clasweb.jlab.org/wiki/images/3/3b/FT-Manual.pdf FT]
 
* [https://clasweb.jlab.org/wiki/images/b/b0/Ftof_manual.pdf  FTOF]
 
* [https://clasweb.jlab.org/wiki/images/b/b0/Ftof_manual.pdf  FTOF]
* [https://clasweb.jlab.org/wiki/images/a/a2/Ec_manual.pdf ECAL]
+
* [https://clasweb.jlab.org/wiki/images/f/f1/HTCC_MANUAL.pdf HTCC]
 
* [https://wiki.jlab.org/clas12-run/images/d/d2/Ltcc_manual.pdf LTCC]
 
* [https://wiki.jlab.org/clas12-run/images/d/d2/Ltcc_manual.pdf LTCC]
* [https://clasweb.jlab.org/wiki/images/f/f1/HTCC_MANUAL.pdf HTCC]
 
* RICH: [https://clasweb.jlab.org/wiki/images/e/ea/RICH_Manual.pdf expert] [https://wiki.jlab.org/clas12-run/images/d/d9/RICH_Controls_mc.pdf novice]
 
* [https://clasweb.jlab.org/wiki/images/0/0f/Ctof_manual.pdf CTOF]
 
* [https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf CND]
 
* [https://clasweb.jlab.org/wiki/images/9/96/Svt_operation_manual_v1_1.pdf  SVT]
 
 
* [https://clasweb.jlab.org/wiki/images/a/ad/Documentation_Shifters_MVT.pdf MVT]
 
* [https://clasweb.jlab.org/wiki/images/a/ad/Documentation_Shifters_MVT.pdf MVT]
 
** [https://wiki.jlab.org/clas12-run/images/b/bf/MVT_for_Dummies.pdf MVT turn on procedure]
 
** [https://wiki.jlab.org/clas12-run/images/b/bf/MVT_for_Dummies.pdf MVT turn on procedure]
* [https://clasweb.jlab.org/wiki/images/3/3b/FT-Manual.pdf FT]
+
* RICH: [https://clasweb.jlab.org/wiki/images/e/ea/RICH_Manual.pdf expert] [https://wiki.jlab.org/clas12-run/images/d/d9/RICH_Controls_mc.pdf novice]
* [https://clasweb.jlab.org/wiki/images/4/4d/Beamline_manual.pdf Beamline]
+
* [[Media:clas12controls_shift.pdf|Slow Controls]]
 +
* [https://clasweb.jlab.org/wiki/images/d/dc/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid Power-Up and Power-Down Procedure]
 +
* [https://clasweb.jlab.org/wiki/images/9/96/Svt_operation_manual_v1_1.pdf  SVT]To switch on SVT see [https://logbooks.jlab.org/files/2018/10/3615766/svt_problem_solving_0.pdf SVT short]
 
* [https://clasweb.jlab.org/wiki/images/d/d6/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus Power-Up and Power-Down Procedure]
 
* [https://clasweb.jlab.org/wiki/images/d/d6/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus Power-Up and Power-Down Procedure]
* [https://clasweb.jlab.org/wiki/images/d/dc/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid Power-Up and Power-Down Procedure]
 
* [https://clasweb.jlab.org/wiki/images/c/c1/Shift_Worker_Manual_January_2018.pdf Cryo Target Operation manual]
 
* [https://clasweb.jlab.org/wiki/images/a/ab/Opman_master.pdf DAQ]
 
* [[Media:clas12controls_shift.pdf|Slow Controls]]
 
  
 
| valign=top |
 
| valign=top |
 
===Procedures===
 
===Procedures===
 
* [[Media:estab_beam.pdf|Establishing Physics-Quality Beam]]
 
* [[Media:estab_beam.pdf|Establishing Physics-Quality Beam]]
* [[Media:moller.pdf|Performing M&oslash;ller Runs]]
+
* [[Media:clas12moller.pdf|Performing M&oslash;ller Runs]]<!--** [[Media:moller.pdf|Old, Expert M&oslash;ller]]-->
 
* [[Media:HarpScanManual.pdf|Performing Harp Scans]]
 
* [[Media:HarpScanManual.pdf|Performing Harp Scans]]
 
* [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Tunnel/Hall Access]
 
* [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Tunnel/Hall Access]
* [https://clonwiki0.jlab.org/wiki/index.php/DAQ/Online_Quick_Reference <span style="color:red;"><b>DAQ Quick Reference/Recovery</b></span>]
+
<!--* [https://clonwiki0.jlab.org/wiki/index.php/DAQ/Online_Quick_Reference <span style="color:red;"><b>DAQ Quick Reference/Recovery</b></span>] -->
  
 
| valign=top |
 
| valign=top |
Line 59: Line 61:
 
<!--#######################################  PHONE NUMBERS  #############################################-->
 
<!--#######################################  PHONE NUMBERS  #############################################-->
 
{{PhoneNumbers}}
 
{{PhoneNumbers}}
[https://wiki.jlab.org/clas12-run/index.php?title=Template:PhoneNumbers&action=edit Click Here]  to edit Phone Numbers.  Note, you then also have to [https://wiki.jlab.org/clas12-run/index.php?title=Run_Group_A&action=edit&section=11 edit this page] to force a refresh.
+
[https://wiki.jlab.org/clas12-run/index.php?title=Template:PhoneNumbers&action=edit Click Here]  to edit Phone Numbers.  Note, you then also have to [https://wiki.jlab.org/clas12-run/index.php?title=Run_Group_A&action=edit&section=9 edit this page] to force a refresh.
  
<!-- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATEs-->
+
<!-- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE-->
  
 
= Short Term Schedule =
 
= Short Term Schedule =
<!--#######################################  SHORT TERM  ################################################-->
 
 
<center><font color=blue size=4>
 
<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>
 
''' Important: Document all your work in the logbook! '''<br>
''' Remember to fill in the [https://docs.google.com/spreadsheets/d/1j6UMJsId8VlsY00dg9Vqm0wmEJZLWVZlsBS-aL49xxw/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/1g2L33OKvKVFMq3MNGYAuS02l0CCKomPbDm8iULLhueY/edit#gid=0 run list] at the beginning and end of each run
 
 
 
</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: Eugene Pasyuk ==
+
== PDL: Maurizio Ungaro ==
 
*  (757) 876-1789  
 
*  (757) 876-1789  
 
* 9 876-1789 from Counting Room
 
* 9 876-1789 from Counting Room
* [mailto:pasyuk@jlab.org pasyuk@jlab.org]
+
* [mailto:ungaro@jlab.org ungaro@jlab.org]
 
 
<br>
 
 
 
* '''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 UPSTREAM counters has to be  in the range 0-15 Hz (rates up 100 Hz are acceptable) and MIDSTREAM has to be in the rage 10-20 Hz (acceptable up to 50 Hz) @50 nA. Count rates in the range of hundreds or more may indicate bad beam tune or bleed-through from other Halls.
 
 
 
* ''' Note 2: At the end of each run, follow the DAQ restart sequence '''
 
 
 
''' "end run", "cancel", "reset"''', then
 
 
 
if run ended correctly ''' "download", "prestart", "iocjscalerRestartAll.sh", "go". '''
 
 
 
if run did not ended correctly, or ROCs had to be rebooted '''"Configure", "download", "prestart", "iocjscalerRestartAll.sh", "go". '''
 
 
 
After DAQ prestart is complete reboot the scaler IOCs with the command:'''  iocjscalerRestartAll.sh. '''
 
 
 
Note: 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:''' ''' 2C24A (X=0.5,Y=0.5) ''', '''2H01 (X=1.0 mm, Y=-1.0 mm)''' see log entry https://logbooks.jlab.org/entry/3570290.
 
 
 
* '''Note 4: Do not turn OFF FTOF HVs, even during the beam tune'''
 
 
 
* '''Note 5: In case of the Torus and/or Solenoid Fast Dump  do the following -
 
*# Notify MCC, request beam OFF and drop Hall status to Power Permit
 
*# Call Engineering on-call
 
*# Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" filed add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org
 
*# Notify Run Coordinator
 
*# Call the MM expert to turn the detector off
 
*# Call SVT expert to turn SVT off
 
*# Turn off all the other detectors'''
 
 
 
*'''Note 6: When beam is being delivered to the  Faraday Cup -'''
 
*# the Fast Shut Down: Upstream, Midstream, Downstream, BOM and Solenoid should be always <font color=red> Unmasked</font>,
 
*# No changes to the FSD threshold without RC or beamline expert approval.
 
 
 
*'''Note 7: Do not turn on or off SVT - only SVT expert can do that'''
 
*'''Note 8: Any request for a special run or change of configuration has to be approved by RC & documented.'''
 
*'''Note 9: Check carefully BTA every hour and run script <font color=red> btaGet.py </font>. It will  print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.'''
 
*'''Note 10: Reset CLAS12MON frequently to avoid histogram saturation.'''
 
  
 
{| {{TableStyle1}}  
 
{| {{TableStyle1}}  
Line 126: Line 87:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
== <font color=blue>''' Run Plan: May3-May 6 '''</font>==
+
== <font color=blue>''' Run Plan: April 8-15, 2019'''</font>==
 +
(Last updated: April 12th, 2019 @ 19:00)
  
 +
<b>DAQ config: PROD66; Trigger file: rga_v2.trg</b>
 +
<!--
 +
* When the Hall is in beam permit:
 +
** Energize the tagger
 +
** 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).
  
May 4 (Day/Swing)  
+
* When beam is available:
There are a series of special runs planned.  
+
** Establish the beam on the tagger yoke dump (see instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]).
 +
** Perform 2C21 and 2C24 harp scans (follow instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf])
  
1. FT-only trigger runs: Genova group (Raffaella/Andrea) just finished this run
+
* If beam is acceptable:
 +
** Degauss the tagger magnet
 +
** 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.
 +
** Perform 2H01 harp scan (follow instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]).
  
2. Random-trigger with existing PCAL/FTOF map: Started around 9am and should conclude around 2pm. If there is any issue, contact Andrea via bluejeans.com/1342978709
+
* After beam is established on FC and the beam profile is acceptable, turn on the CLAS12 detectors.
  
For 3--5, Sergey will take control of DAQ
+
* Take low current production at 10 nA for 4 hr.
 +
-->
 +
<!--
 +
* Take production data at 50 nA in 4 hr runs!
  
3. DAQ studies(Sergey): Starting from 2:00pm. Sergey must be notified around 1:30pm if he is not already in the counting house. This is a series of short 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.  
  
4. DC/Varying readout window size/current scans: This will be a series of short runs (~30min each). For exact setting, please contact Volker (phone # on white board); Sergey will implement the changes.
+
Starting from the swing shift,
  
5. Mode 7: Sergey will perform this run (~2 hrs). Dan should be contacted if needed via FTOF expert phone.
+
* 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.
  
May 4(Swing) --- May 6th (Owl)
+
* 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.
  
When the above special runs are finished. Resume production runs at 50nA with trigger_v12_3.cnf
+
* 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).
  
  
'''May 6 at 5 am''' MCC will terminate beam delivery.<br>
+
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 
 +
-->
  
Start preparation for summer shutdown after that
+
Take production data at in 4 hours runs at 50 nA, DAQ config: PROD66; Trigger file: rga_v2.trg.
* '''Turn HV OFF for:'''
 
** '''DC'''
 
** '''FTOF'''
 
** '''ECAL/PCAL'''
 
** '''LTCC'''
 
** '''HTCC'''
 
** '''FTT'''
 
** '''BMT/FMT'''
 
** '''CTOF'''
 
** '''CND'''
 
* '''Detectors remain ON for post calibrations:'''
 
** '''RICH'''
 
** '''SVT'''
 
** '''FTC/FTH'''
 
** '''Cryotarget stays FULL'''
 
* '''Turn OFF Solenoid and Torus''' (call PDL)
 
  
 +
On the Torus/Magnet power Suppy monitor torus MPS Control Comm  light. It should be green. If not, contact Magnet group.
  
May 6 7am.
+
<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>
  
A small reception full of fancy food will be held in the counting house at 7am for the early birds. No reservation needed. Dress code: photo-friendly.
+
<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>
  
* From time to time, we might experience trigger bit issues (FT bits: 24, 25, and 26 and 27). bit 26 might not trigger the alarm but when this issue happens it will count abnormally high pre-prescale. For the time being, shift leaders cand try to do the sequence of End->Cance->Reset, roc_reboot adcft1 (and adcft2, adcft3), make sure the roc 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 persist, please continue take production data without fixing it -- please make sure you log this infor in the RCDB "Comment" field.  
+
- <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>
  
* If the machine is down for few hours 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 50 nA and continue data for production. If there are issues with the beam call the RC. Sometimes MCC operator might ask to deliver tune beam --- please do not accept it. We need CW beam sent to the Faraday cup. If there is in deed a need for tune beam, it should be sent to the tagger dump with the tagger magent on. If you are uncertain, please call RC/PDL.
+
</font>
  
 +
*Note: <font color=red>DO NOT IGNORE</font> unsafe FSD masking alarm! Follow alarm guidance.
  
* <font color=red>'''Please contact the Micromegas (BMT, FMT & FTT) expert if there are trips, or if you notice any issues in the online monitoring. Do not turn OFF or ON the MM only the expert  can do that. See Log entry https://logbooks.jlab.org/entry/3556528 '''</font>
 
  
Sometimes, a couple of RICH channel scalers would go to 0 and there is no alarm, even though the "# of fjibers 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, please refer to the instruction below.
+
<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>'''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, please contact the RICH expert on call '''</font>
+
<b><font color=red> At the end of each run, follow the standard DAQ restart sequence ''' <br>
 +
''(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"
 +
</font></b>
  
 +
== <font color=blue>''' References and Standards:'''</font>==
 +
''(last update March 27, 2019 @ 8:53 a.m.)''
  
 +
<b> Restoration of Beam to Hall B</b>
  
'''In case of other questions or uncertainties of what to do, please call the RC'''
+
<b> Nominal Beam Positions </b>
 +
*2H01, X: +3.0 mm, Y: -1.0 mm
 +
*2C24, X: +0.25 mm, Y: 0.35 mm
  
 +
<b> FSD Thresholds </b>
 +
* Upstream: 2000 Hz
 +
* Midstream: 2000 Hz
 +
* Downstream: 500000 Hz
 +
* BOM: 35000
  
 +
<b> Reference Harp Scans for Beam on Tagger Dump: </b> 2C21 [https://logbooks.jlab.org/entry/3672101], 2C24 [https://logbooks.jlab.org/entry/3672102]
  
<!-- === Updated March 6, 9:39 ===
+
<b> Reference Harp Scans for Beam on Faraday Cup: </b> 2H01 [https://logbooks.jlab.org/entry/3672120]
*Due to the power failure, accelerator will be off for some extended time. All shifts are canceled for the 48 hours.
 
Next staffed shift will be Thursday, March 8'th expert day shift.
 
*Machine update https://logbooks.jlab.org/entry/3543255
 
-->
 
<!--
 
Due to the power failure, accelerator will be off for some extended time. All shifts are canceled for the 24 hours. Next staffed shift will be Tuesday, March 6'th expert swing shift.
 
Machine update https://logbooks.jlab.org/entry/3543255
 
  
*Take data with the 50 nA beam, trigger file trigger_v9.cnf, 100M  events per run.
+
<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)
*Monitor livetime closely.
 
  
* ''Sat Feb 23: Take data with 35 nA beam until Sergei creates the new trigger file''
+
<b> Reference Scalers and Halo-Counter Rates: </b>
* ''When Sergei comes he will test the new trigger file with 50 nA beam '', if it works, then the plan for the weekend is to take production data with 50 nA beam.
+
* 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 beam during Moller run [https://logbooks.jlab.org/entry/3649364]
 +
* Well-tuned beam on Tagger Dump at 5 nA during harp scans: [https://logbooks.jlab.org/entry/3649358]
 +
* Reference FTC histogram for 5 nA running: [https://logbooks.jlab.org/entry/3665122]
  
* ''' Before Accelerator gets beam off for beam studies we should take empty target run, It will be around Monday 7 AM. RC will notify later if the time for empty target runs is changed '''
+
<b> SVT acceptable currents: </b> 1 uA
  
* ''' Monday when MCC takes the beam off we might go to "Controlled access" during beam studies. Please ask MCC for controlled access with Radiation survay  '''
+
| valign=top |
* ''' Monday when hall is sweeped, ask MCC to energize the tagger magnet, and then follow instructions in section 1 "Beam to tagger-yoke dump" from this link https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf  '''
 
  
* ''' When good beam is establisged on tagger magnet Yoke, we should do two Moller runs, 1st with half wave plate OUT, and 2nd with half wave plate "IN", please follow instructions in this link https://wiki.jlab.org/clas12-run/images/1/1d/Moller.pdf'''
+
==<font color=blue>''' General Instructions''':</font>==
  
* ''' When Moeller runs are finished, ask MCC to deGaus the tagger magnet, and follow instructions for sending the beam to Faraday Cup  https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf Section 2'''.
+
* 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.
  
* ''' As soon a good beam is established (good harpscan, beam is centered in FTCalo), then turn on HV on detectors, and start taking data with trigger_v7 '''.
+
'''Once Per Day (on day shift):'''
* ''' We want to check whether we can go to a higher current 55 nA, and check whether DAQ is stable and livetime is around 90%, if it works, then we should keep the 55 nA beam current, otherwise we should go back to 50 nA '''
+
* Complete RICH recovery procedure - see Note: 14 below
-->
 
<!--
 
The beam position should be as indicated above. Make sure FSD thresholds are set correctly for whatever current is selected (refer to instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]), integration time is set to 5 ms, and that the orbit locks are on. -->
 
  
 +
'''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
 +
* [https://bta.acc.jlab.org 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 [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.
  
<!--
+
'''Every Run:'''
<font color=blue>''' February 20 swing, February 21 owl and day shifts Run Plan'''</font>
 
  
* Take data with a production trigger trigger_v4.trg untill 1 PM Wed. Feb. 21, and at 1PM call MCC and request "Restricted" access.
+
*Log screenshots of:
** HV on all detectors should be off, except SVT you can turn HV off, for SVT call Yuri and ask to turn SVT HV off
+
** main scaler GUI display
** Call PDL (Eugene) and ask to rump Solenoid and Torus down.
+
** Trigger rate gui
 +
** Beam strip charts
 +
** FTC scalers
 +
* 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.
 +
* <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.
 +
* Same holds for FT.</b>
  
* When we back again to beam permit, we should directly go into FCup
+
|}
** Eugune will rump up Solenoid and Torus magnets
 
** Make sure Solenoid FSD is unmasked "There should not be any Yellow or Red lights under the Solenoid FSD"
 
** Make sure HV on all detectors are off except FT CALO.
 
** Tagger magnet is "OFF"
 
** Collimator is at '20 mm' position
 
** Request for 2 nA beam
 
  
** Make sure Solenoid FSD is unmasked "There should not be any Yellow or Red lights under the Solenoid FSD"
+
* '''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.'''
** Make sure HV on all detectors are off except FT CALO.
+
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.
** Tagger magnet is "OFF"
 
** Collimator is at '20 mm' position
 
** Request for 5 nA beam
 
  
** Look carefully int Halo counters, all halo counters upstream of the target are counting less than 10 Hz
+
* '''Note 2: FTOF HVs: The goal is to minimize the number of power cycles of the dividers.
** Look into FT Calo scaler screen, which is the main measure how the beam is centered, for reference look https://logbooks.jlab.org/entry/3535015 this, and make sure X and Y asymmetry is close to 0 (less than +/-6% with 2 nA beam, and less than 3% when you go to production current).
+
** 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.'''
** If the beam is centered enough and halo rates on midstream and upstream halo counters don't exceed few Hz, request for 20 nA beam, and ask out orbit lock to be engaged. Check again beam is centered, and halo counters still coun order of few Hz.
+
** should be left on after an initial beam tune has been established and if there are only minor steering adjustments and “tweaks” being made.
** Check also beam position on 2H01, should be around '''2H01 (X=1.0 mm, Y=-1.5 mm)'''
+
** if shift workers have doubts what to do with the HVs, they can always contact the TOF on-call expert for advice.
  
* Next step is to do harp scans with all three harps, 2c21 harp, tagger harp and 2H01 harp
+
* '''Note 3: In case of a Torus and/or Solenoid Fast Dump do the following:
** Before 2C21 and tagger harps scans put Upstream and midstream FSD thresholds to 100000, and the integration time 50ms.
+
*# Notify MCC to request beam OFF and to drop Hall B status to Power Permit
** You should not see any signifcant halo, the bgr/Peak ratio should be below 5e-3
+
*# Call Engineering on-call
** As soon you are done with 2c21 and tagger harp scans, put back FSD hresholds for upstream and midstream counters to 1000, and integration time to 5 ms.
+
*# 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'''
  
** For 2H01 harp scan, ask BOM limit to be 1000000 and itegration time 50 ms. then do 2H01 harp scan. Compare harp scan result to the most recent one https://logbooks.jlab.org/entry/3534806, make sure beam sigmas are close to the one in the link.
+
*'''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>
 +
*# No changes to the FSD threshold should be made without RC or beamline expert approval
  
* Next step is to tur HV on for detectors, for '''SVT''' only call Yuri and ask him to turn SVT HV on.
+
*'''Note 5: Any request for a special run or change of configuration has to be approved by the RC & documented'''
* Sergei has added a new component PCal Ustrips (PCU) in the trigger, it's timing should be checked, call sergei and ask him to take over the DAQ to adjust the relative timing of PCU. This should approximetely take about 1 hour.
 
* As soon Sergei has finished timing adjustment, ask for 35 nA beam, and take production data with trigger_v5.trg
 
-->
 
<!-- * If the machine is down and it is back start with low current first  (2nA and 5 nA)  making sure that the beam is stable in current and position before moving to 30 nA
 
-->
 
  
 +
*'''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 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 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]'''-->
  
<!--
+
*'''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:
'''[[Every Shift:]]'''
+
*# SafeMode.snp for beam tuning and Moeller runs
*Follow run plan as outlined by RC
+
*# MV_HV_FullField.snp for full solenoid field
* If any concern about beam stability, ask MCC if orbit locks are on (they should be).
+
*# MV_HV_MidField.snp wgeb solenoid < 4T
* 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
+
*'''Note 10: Check the vacuum periodically, make sure vacuum is not higher than 5e-5 '''
* 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.
 
*Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
 
  
'''[[Every Run:]]'''
+
*''' Note 11: Always reset the CFD threshold after all power off/on on the CND CAMAC crate'''  
''Log screenshots of:''
+
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
* main scaler GUI display
+
following command from any clon machine terminal: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0
* Detector occupancy plots
 
* Trigger rate gui
 
* Beam strip charts
 
* FTCalo FADC scalers
 
  
-->
+
If this command is failing and the crate is not responding, reboot it as follows: roc_reboot camac1
| valign=top |
 
  
==<font color=blue>''' General Instructions''':</font>==
+
*'''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.
  
* 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.
+
*'''Note 13: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766'''
* 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.
 
* 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 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.
 
  
'''Every Shift:'''
+
*'''Note 14:'''  
*Follow run plan as outlined by RC
+
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.
* If any concern about beam stability, ask MCC if orbit locks are on (they should be).
+
** 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.
* 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.
 
* 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:
 
** From main clascss open '''FTT Gas'''
 
** 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:'''
+
*'''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.
  
'' Log screenshots of:''
+
*'''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
* main scaler GUI display
 
* Detector occupancy plots
 
* Trigger rate gui
 
* Beam strip charts
 
* FTCalo FADC scalers
 
 
 
|}
 
  
 
= Monitoring =
 
= Monitoring =
Line 333: Line 299:
 
* [http://hallbcam06.jlab.org/ Faraday Cup Beam Viewer]
 
* [http://hallbcam06.jlab.org/ Faraday Cup Beam Viewer]
 
* [http://cctv1.jlab.org Tagger Beam Dump Viewer]
 
* [http://cctv1.jlab.org Tagger Beam Dump Viewer]
* [http://cctv12.jlab.org CTOF Ammeter]
+
<!--* [http://cctv12.jlab.org CND/CTOF Ammeter]
* [http://cctv7.jlab.org FC Ammeter]
+
* [http://cctv7.jlab.org FTOF/ECAL Ammeter]-->
 
* [http://hallbcam02.jlab.org Hall Fisheye]
 
* [http://hallbcam02.jlab.org Hall Fisheye]
 
* [http://cctv11.jlab.org Saclay Cryotarget]
 
* [http://cctv11.jlab.org Saclay Cryotarget]
Line 350: Line 316:
  
 
|}
 
|}
 +
 +
== Fall 2018 Run ==
 +
{| {{TableStyle1}}
 +
| valign=top |
 +
[[Image:Fall2018_charge.jpg|fall2018_charge.jpg|700px]]
 +
 +
| valign=top |
 +
[[Image:moller_rg_a_fall.jpeg|500px]]
 +
|}
 +
 +
== Spring 2018 Run ==
  
 
{| {{TableStyle1}}
 
{| {{TableStyle1}}
Line 370: Line 347:
 
* [http://clasweb.jlab.org/rcdb RCDB]
 
* [http://clasweb.jlab.org/rcdb RCDB]
 
* [https://clas12mon.jlab.org/ CLAS12 mon page]
 
* [https://clas12mon.jlab.org/ CLAS12 mon page]
* [https://clas12mon.jlab.org/mon12/histograms/ Comparison between mon12 histograms (last 5 runs)]  
+
* [https://clas12mon.jlab.org/mon12/histograms/?reference=3630375 Comparison between mon12 histograms (reference in 1st column compared to last entries)]  
 
* [https://clas12mon.jlab.org/datasize/ Accumulated datasize]
 
* [https://clas12mon.jlab.org/datasize/ Accumulated datasize]
 +
* [https://clas12mon.jlab.org/charge/ Accumulated charge]
 +
 
===Run lists===
 
===Run lists===
* [https://docs.google.com/spreadsheets/d/1j6UMJsId8VlsY00dg9Vqm0wmEJZLWVZlsBS-aL49xxw RGA run list]
+
*[https://docs.google.com/spreadsheets/d/1NpojoOi7_gTt_abxgKoHBlofOL7iNWDrtYuiOJ1zoMw RGA Fall 18 run list]
 +
* [https://docs.google.com/spreadsheets/d/1j6UMJsId8VlsY00dg9Vqm0wmEJZLWVZlsBS-aL49xxw RGA Winter 18 run list]
 
* [https://docs.google.com/spreadsheets/d/1frfBlq51qDXZD6fW5rcRefNXSGdVvdMozKUlAVNoUGc ER run list]
 
* [https://docs.google.com/spreadsheets/d/1frfBlq51qDXZD6fW5rcRefNXSGdVvdMozKUlAVNoUGc ER run list]
 
| valign=top |
 
| valign=top |
Line 380: Line 360:
 
* [http://opweb.acc.jlab.org/CSUEApps/bta03/pd_shiftplan_history.php Program Deputy Shift Plans]
 
* [http://opweb.acc.jlab.org/CSUEApps/bta03/pd_shiftplan_history.php Program Deputy Shift Plans]
 
* [http://opweb.acc.jlab.org/internal/ops/ops_webpage/run_coord/runcoord_form.php?action=main Run Coordinator Reports]
 
* [http://opweb.acc.jlab.org/internal/ops/ops_webpage/run_coord/runcoord_form.php?action=main Run Coordinator Reports]
 +
* 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
 
 
|}
 
|}
  

Latest revision as of 13:44, 25 July 2024

[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]

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