Difference between revisions of "Run Group B"

From clas12-run
Jump to navigation Jump to search
 
(214 intermediate revisions by 12 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/rgb/ESAD_HallB-CLAS12_rgB.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rgb/COO_HallB-CLAS12_rgB.pdf COO], [https://www.jlab.org/Hall-B/run-web/rgb/RSAD_HallB-CLAS12_rgB.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 |
Line 31: Line 32:
 
* [[Media:clas12controls_shift.pdf|Slow Controls]]
 
* [[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/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]
+
* [[Media:Svt_operation_manual_v1_7.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]
  
Line 56: Line 57:
 
* Nov 27 - Dec 4: M. Contalbrigo
 
* Nov 27 - Dec 4: M. Contalbrigo
 
* Dec 4 - Dec 11: D. Sokhan
 
* Dec 4 - Dec 11: D. Sokhan
* Dec 11 - Dec 19: S. Niccolai
+
* Dec 11 - Dec 18: S. Niccolai
 +
* Dec 18 - Dec 20 S. Stepanyan
 
* Jan 7 - Jan 15: J. Gilfoyle
 
* Jan 7 - Jan 15: J. Gilfoyle
* Jan 15 - Jan 22: V. Kubarovsky
+
* Jan 15 - Jan 22: F. Hauenstein /W. Phelps
* Jan 22 - Jan 29: B. McKinnon
+
* Jan 22 - Jan 30: B. McKinnon
  
 
</font>
 
</font>
Line 81: Line 83:
 
</center>
 
</center>
  
== RC: Daria Sokhan ==
+
== RC: Bryan McKinnon ==
 
* (757) 575-7540   
 
* (757) 575-7540   
 
* 9 575 7540 from Counting Room
 
* 9 575 7540 from Counting Room
* [mailto:daria@jlab.org daria@jlab.org]
+
* [mailto:mckinnon@jlab.org mckinnon@jlab.org]
  
 
== PDL: Maurizio Ungaro ==
 
== PDL: Maurizio Ungaro ==
Line 92: Line 94:
  
 
<br>
 
<br>
+
 
  
 
{| {{TableStyle1}}  
 
{| {{TableStyle1}}  
  
 
| valign=top width=50% |
 
| valign=top width=50% |
== <font color=blue>''' Run Plan: December 6'''</font>==
+
== <font color=blue>''' Run Plan: Jan 29 - 30 2020 '''</font>==  
  
* Run trigger validation following program in  [https://logbooks.jlab.org/entry/3745954 https://logbooks.jlab.org/entry/3745954]
+
* Wednesday
* Once HTCC is calibrated (morning), take production data with new trigger.
+
** Owl - Production data at 50nA
 +
** Day - Production data at 50nA
 +
** Swing - Production data at 50nA
  
 +
*Thursday
 +
** Owl - Production data at 50nA
 +
** 7am Request Restricted Access, Ramp Down the magnets, Empty and warm up target
 +
** 7am Contact Eugene as soon as beam off
  
 +
 +
* Please note that we have added two items to the list of tasks for each run.
 +
** (1) When you collect the gui snapshots for the logbook (scalar gui, FTC Asym plot, livetime, ROC rates, beamline stripcharts) <b>include the DAQ gui</b> AND make sure the snapshot is taken when you're running. We want to record the rate plots on the DAQ gui.
 +
** (2) Measure the <b>trigger structure</b> (trigger-time distribution) about every 30 minutes and at least once per run enter the results in the logbook. See below for instructions. This is needed to monitor the injector laser phase which created serious problems last week.
 +
* If the trigger-time distribution or region 1 DC occupancies get worse ( > 6.5%) call the RC. What we will likely do is reduce the beam and restart.
 +
* At some later time we need to do an empty target run. Current will be 150 nA for 50M triggers which should take 2-3 hours.
 
------
 
------
'''DAQ config: PROD66 ''' (for runs written to tape and deleted from disk), <b>PROD66_PIN</b> (for runs which need to be kept on disk for immediate access)
+
'''DAQ config: <b>PROD66</b>  
  
'''Trigger file: rgb_outbending_v11_1.trg '''
+
'''Trigger file : rgb_inbending_v9_1.trg '''
  
''' Nominal current: 30 nA '''
 
  
<b> Compare the monitoring histograms </b> from [https://clas12mon.jlab.org/mon12/histograms/?reference=3746641 clas12mon] to the reference and troubleshoot as needed.
+
<b> Compare the monitoring histograms </b> <!-- from [https://clas12mon.jlab.org/mon12/histograms/?reference=3748541 clas12mon] to the reference and troubleshoot as needed.-->
 +
  
When stopping a run, check the current entered in the pop-up window and put run comments when relevant -- <b> please label junk runs. </b>  
+
<b> Run database: </b> <font color=red>when starting/stopping a run, enter (or check if already present) the requested current in the pop-up window and put RELEVANT COMMENTS (eg: "production run", "trigger test vXX, changed this and that" not just "run")  -- <b> please label junk runs </b> if you get the chance. Please also keep a record of run numbers and their conditions in the shift summary. </font> The information you enter in the dialogue box goes directly into the [https://clasweb.jlab.org/rcdb run database] -- it's our primary source of run info and mistakes are hard to correct a posteriori.
------
 
  
  
''' Thursday Swing / Owl '''
+
Please run the script to look at <b> trigger structure </b> once per shift and check that you get a smooth distribution. Instructions are here: [https://logbooks.jlab.org/entry/3760614]
  
Once we get beam back, bring it to Faraday Cup and do harp scans. If good, proceed to trigger validation. If not, send it to tagger dump and set up from there.
+
Keep an eye on <b> CND channel S14L1R </b> -- it's a bit temperamental. If it trips, switch HV off and on again for it and make an entry in the log book.
 
 
Next: random trigger runs (see below -- configuration RNDM66_PIN for random trigger, then PROD66_PIN for production).
 
 
 
If everything done, take production data at the highest current possible (which gives live-time ~90%) with Valery's validation trigger (switch MVT back on).
 
 
 
''' Trigger Validation runs ~ 6 hours at least ''' See Valery's plan in [https://logbooks.jlab.org/entry/3745954 logbook]
 
  
 +
------
  
 
'''<b> At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font> ''' </b>'''<br>
 
'''<b> At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font> ''' </b>'''<br>
Line 136: Line 144:
 
** "configure", "download", "prestart", "go"
 
** "configure", "download", "prestart", "go"
 
* After each step, make sure it completed in the Run Control message window.</font></b> If a ROC has crashed, find which one it is, issue a roc_reboot command ON JUST THAT ROC and try again. Contact the DAQ expert if there are any questions.
 
* After each step, make sure it completed in the Run Control message window.</font></b> If a ROC has crashed, find which one it is, issue a roc_reboot command ON JUST THAT ROC and try again. Contact the DAQ expert if there are any questions.
 
 
  
  
 
== <font color=blue>''' References and Standards:'''</font>==
 
== <font color=blue>''' References and Standards:'''</font>==
''(last update 12/4/2019- 17:00)''
+
''(last update 1/14/2020- 23:20)''
  
 
<b> Nominal Beam Positions </b>
 
<b> Nominal Beam Positions </b>
*2H01, X: +1.5 mm, Y: -1.0 mm
+
*2H01, X: +1.0 mm, Y: -2.6 mm
*2C21, X: -0.2 mm, Y: -0.25 mm
+
*2C21, X: 0.0 mm, Y: 0.2 mm
 
*2C24, X: -0.3 mm, Y: -0.8 mm
 
*2C24, X: -0.3 mm, Y: -0.8 mm
  
Line 154: Line 160:
 
* BOM: 60000
 
* BOM: 60000
  
<b> Reference Harp Scans for Beam on Faraday Cup: </b> 2C21 [https://logbooks.jlab.org/entry/3746682], 2C24 [https://logbooks.jlab.org/entry/3746686], 2H01 [https://logbooks.jlab.org/entry/3746687]
+
<b> Reference Harp Scans for Beam on Faraday Cup: </b> 2C21 [https://logbooks.jlab.org/entry/3759969], 2C24 (tagger harp) [https://logbooks.jlab.org/entry/3759229], 2H01 [https://logbooks.jlab.org/entry/3759255]
 +
 
 +
<b> Reference Harp Scans for Beam on Tagger dump: </b> 2C21 [https://logbooks.jlab.org/entry/3759158], 2C24 (tagger harp) [https://logbooks.jlab.org/entry/3759160]
  
<b> Reference Monitoring Histograms (40 nA, production trigger) </b> [https://logbooks.jlab.org/entry/3746641]
+
<b> Reference Monitoring Histograms (40 nA, production trigger) </b> [https://logbooks.jlab.org/entry/3748541]
  
 
<b> Counter rates </b>
 
<b> Counter rates </b>
Line 194: Line 202:
 
* Document any beam condition change and send scaler GUIs to HBLOG
 
* Document any beam condition change and send scaler GUIs to HBLOG
 
* [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side. Run the script <font color=red>btaGet.py</font> to print for you the correct BTA info for this hour -- edit the values on the BTA page if they are wrong!
 
* [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side. Run the script <font color=red>btaGet.py</font> to print for you the correct BTA info for this hour -- edit the values on the BTA page if they are wrong!
* Upload spectra from clas12mon at begin and end of shift and cross-check with reference spectra
+
* Upload spectra from clas12mon at begin and end of shift and cross-check with reference spectra (make sure you select the SAME SECTOR as for the reference plots on tabs which have multiple sectors).
** Reset clas12mon every ~2 hours and inspect spectra.
+
** Reset clas12mon every ~2 hours and inspect spectra (some detectors have buttons at the bottom to toggle between the sectors -- please check all of them).
 
* 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]
 +
* Run script to check smoothness of the trigger time structure: [https://logbooks.jlab.org/entry/3749715]
 
* 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.
  
Line 208: Line 217:
 
* At the start and end of every run, check that the data filled in the [https://clasweb.jlab.org/rcdb database run list] is correct (especially fields which are filled in manually, like beam current and comments). This replaces the previously-used spreadsheet.
 
* At the start and end of every run, check that the data filled in the [https://clasweb.jlab.org/rcdb database run list] is correct (especially fields which are filled in manually, like beam current and comments). This replaces the previously-used spreadsheet.
 
* <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.  
 
* <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>
+
* Same holds for FTOF.</b>
 +
 
 +
 
 +
'''To access the Hall:'''
 +
* If you need to go down into Hall B alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).
 +
* Check in with the shift personnel before entering the hall.
  
 
|}
 
|}
Line 215: Line 229:
 
==<font color=blue>''' Notes / Troubleshooting ''':</font>==
 
==<font color=blue>''' Notes / Troubleshooting ''':</font>==
  
 +
<b>If crate ADCBAND was rebooted:</b> Contact BAND expert and make a note in the HBBAND logbook and in HBLOG.
  
 
<b> FTOF HVs: </b> The goal is to minimize the number of power cycles of the dividers.
 
<b> FTOF HVs: </b> The goal is to minimize the number of power cycles of the dividers.
Line 221: Line 236:
 
** <i>If in doubt, call FTOF expert </i>
 
** <i>If in doubt, call FTOF expert </i>
  
 +
<b>FTT (mmft1) recovery</b>:
 +
 +
** power cycle FTT LV (FT->FTT->turn LV OFF, turn LV ON)
 +
** RunControl "reset"
 +
** roc_reboot mmft1
  
 
<b>Torus and/or Solenoid Fast Dump </b>
 
<b>Torus and/or Solenoid Fast Dump </b>
Line 243: Line 263:
 
<b> CND CAMAC crate switch on / reboot: </b>
 
<b> CND CAMAC crate switch on / reboot: </b>
  
If CAMAC crate (camac1) holding CND CFD boards is switched off for any reason, always reset the associated CND CFD thresholds by typing, from any clon machine terminal:  
+
If CAMAC crate (camac1) holding CND CFD boards is switched off for any reason, always reset the associated CND CFD thresholds by typing, ssh into clondaq3 and type:  
 +
 
 +
$CODA/src/rol/Linux_x86_64/bin/cnd-cfd-thresh -w 0
  
$CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0
+
If this command is failing and the crate is not responding, first 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
+
and then repeat the threshold reset command above.
  
  
Line 266: Line 288:
  
 
When running at low current (<10 nA), FTC asymmetries can be affected by hot channels. If large asymmetries are detected in those conditions, cross check with other  detectors (BOM rates, DC occupancies) before taking further action.
 
When running at low current (<10 nA), FTC asymmetries can be affected by hot channels. If large asymmetries are detected in those conditions, cross check with other  detectors (BOM rates, DC occupancies) before taking further action.
 +
 +
 +
<b> CED display not showing events </b>
 +
 +
Sometimes, CED screens are up but not active (events not showing at all). To solve this:
 +
 +
# Close the CED sceen
 +
# ssh to clondaq4
 +
# Once in the right machine, type ced, and wait for the windows to appear.
 +
# Go to "File" -> "Connect to ET ring". Make sure to select clondaq6, as the online data is being streamed.
 +
# Go to "Events" (same level as "File") and check "Auto Next-Event Every 2.0 sec" (if it is not selected).
 +
 +
You should see the events now, if all is working well.
  
 
= Monitoring =
 
= Monitoring =
Line 340: Line 375:
 
* [https:////clasweb.jlab.org/wiki/index.php/Run_Group_B Run Group B Wiki]
 
* [https:////clasweb.jlab.org/wiki/index.php/Run_Group_B Run Group B Wiki]
 
* [https://clas12mon.jlab.org/ CLAS12 mon page]
 
* [https://clas12mon.jlab.org/ CLAS12 mon page]
* [https://clas12mon.jlab.org/mon12/histograms/?reference=3667461 Comparison of current mon12 histos (second column) to a reference set of histograms (first column) and mon12 histograms (last 5 runs in last columns)]  
+
<!-- * [https://clas12mon.jlab.org/mon12/histograms/?reference=3767514 Comparison of current mon12 histos (second column) to a reference set of histograms (first column) and mon12 histograms (last 5 runs in last columns)]  -->
 +
* [https://clas12mon.jlab.org/mon12/histograms/?reference=3768773 Comparison of current mon12 histos (second column) to a reference set of histograms (first column) and mon12 histograms (last 5 runs in last columns)]  
 
* [https://clas12mon.jlab.org/datasize/ Accumulated datasize]
 
* [https://clas12mon.jlab.org/datasize/ Accumulated datasize]
 
* [https://clas12mon.jlab.org/charge/ Accumulated charge]
 
* [https://clas12mon.jlab.org/charge/ Accumulated charge]
Line 356: Line 392:
 
| valign=top |
 
| valign=top |
 
===Bluejeans meetings===
 
===Bluejeans meetings===
* [https://bluejeans.com/230805731 Daily Run meeting] 230805731
+
* [https://bluejeans.com/8928008153 Daily Run meeting] 8928008153
 
* [https://bluejeans.com/237353330 Weekly RGB meeting] 237353330
 
* [https://bluejeans.com/237353330 Weekly RGB meeting] 237353330
  

Latest revision as of 13:42, 25 July 2024

[edit]

Shift Schedule

Shift Checklist

Hot Checkout

Beam Time Accounting

ESAD, COO, RSAD, ERG

Manuals

Procedures

JLab Logbooks

RC schedule

  • Nov 20 - Nov 27: S. Stepanyan
  • Nov 27 - Dec 4: M. Contalbrigo
  • Dec 4 - Dec 11: D. Sokhan
  • Dec 11 - Dec 18: S. Niccolai
  • Dec 18 - Dec 20 S. Stepanyan
  • Jan 7 - Jan 15: J. Gilfoyle
  • Jan 15 - Jan 22: F. Hauenstein /W. Phelps
  • Jan 22 - Jan 30: B. McKinnon


Clas12design.png