Difference between revisions of "Run Group B"

From clas12-run
Jump to: navigation, search
(Monitoring)
(Short Term Schedule)
 
(348 intermediate revisions by 15 users not shown)
Line 18: Line 18:
 
* [https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf CND]
 
* [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/c/c1/Shift_Worker_Manual_January_2018.pdf Cryo-Target]
* [https://clasweb.jlab.org/wiki/images/0/0f/Ctof_manual.pdf CTOF]
+
* [https://www.jlab.org/Hall-B/ctof/notes/ctof_manual.pdf CTOF]
 
* [https://clasweb.jlab.org/wiki/images/a/ab/Opman_master.pdf DAQ]
 
* [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/a/a2/Ec_manual.pdf ECAL]
 
* [https://clasweb.jlab.org/wiki/images/3/3b/FT-Manual.pdf FT]
 
* [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://www.jlab.org/Hall-B/ftof/notes/ftof_manual.pdf  FTOF]
 
* [https://clasweb.jlab.org/wiki/images/f/f1/HTCC_MANUAL.pdf HTCC]
 
* [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]
Line 31: Line 31:
 
* [[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 53: Line 53:
 
| valign=top |
 
| valign=top |
 
===RC schedule===
 
===RC schedule===
* Jan 26 - Feb 6: S. Niccolai
+
* Nov 20 - Nov 27: S. Stepanyan
* Feb 6 - Feb 13: Y. Ilieva
+
* Nov 27 - Dec 4: M. Contalbrigo
* Feb 13 - Feb 20: S. Stepanyan
+
* Dec 4 - Dec 11: D. Sokhan
* Feb 20 - Feb 27: F. Hauenstein
+
* Dec 11 - Dec 18: S. Niccolai
* Feb 27 - Mar 6: S. Niccolai
+
* Dec 18 - Dec 20 S. Stepanyan
* Mar 6 to Mar 12: J. Gilfoyle  
+
* Jan 7 - Jan 15: J. Gilfoyle
* Mar 12 to Mar 19: V. Kubarowsky
+
* Jan 15 - Jan 22: F. Hauenstein /W. Phelps
 +
* Jan 22 - Jan 30: B. McKinnon
  
 
</font>
 
</font>
Line 75: Line 76:
 
<!--#######################################  SHORT TERM  ################################################-->
 
<!--#######################################  SHORT TERM  ################################################-->
 
<center><font color=blue size=4>
 
<center><font color=blue size=4>
''' CLAS12 Run Group B, spring 2019 </font> '''<br>
+
''' CLAS12 Run Group B, December 2019 - January 2020 </font> '''<br>
''' Beam energy 10.6 GeV (5 pass) '''<br>
+
''' Beam energy ~10.4 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/1NY1GNIZXPtpB9u4QwP6eNRSrvDkCzFmhQg5RR3V3j7E/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/17U7tyDwf1j9sdd4vd6g4ZQdKkDw3WNsdIuBRhiWy6CE/edit?usp=sharing run list] at the beginning and end of each run (clas12run@gmail.com can fill the run list)'''<br> --->
 
</center>
 
</center>
  
== RC: Silvia Niccolai ==
+
== RC: Bryan McKinnon ==
 
* (757) 575-7540   
 
* (757) 575-7540   
 
* 9 575 7540 from Counting Room
 
* 9 575 7540 from Counting Room
* [mailto:silvia@jlab.org silvia@jlab.org]
+
* [mailto:mckinnon@jlab.org mckinnon@jlab.org]
  
 
== PDL: Maurizio Ungaro ==
 
== PDL: Maurizio Ungaro ==
Line 92: Line 93:
  
 
<br>
 
<br>
 +
 
  
 
{| {{TableStyle1}}  
 
{| {{TableStyle1}}  
  
 
| valign=top width=50% |
 
| valign=top width=50% |
 +
== <font color=blue>''' Run Plan: Jan 29 - 30 2020 '''</font>==
  
== <font color=blue>''' Run Plan: Feb. 22 - 24'''</font>==
+
* Wednesday
<!--* Hall-B should be closed before 2 pm. As soon Hall will be in beam permit, energize the tagger. When beam is available proceed with establishing the beam on the tagger yoke dump (see instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]).
+
** Owl - Production data at 50nA
 +
** Day - Production data at 50nA
 +
** Swing - Production data at 50nA
  
* Perform Moller runs, use "right" target, two measurements with 1/2 wave plate IN (as is now) then OUT. Leave 1/2 wave plate in "IN" position for data taking.
+
*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
  
* When finished the Moler runs
 
* If beam is acceptable degauss the tagger magnet and send the beam to Faraday cup, make sure beam is clearly seen on the downstream viewer and the halo counter rates are as expected (compare to earlier rates). Perform 2H01 harp scan(follow instructions [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]). , ''Note harp wire was fixed''  -->
 
  
* After beam is established on FC and the beam profile is acceptable, start bringing CLAS12 is ON, make sure beam position and detector and halo rates are as expected for full target.  
+
* 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: <b>PROD66</b>
  
* Continue production data on LD2 target at 50 nA (<b> if the trigger rate will be higher than 20 kHz, lower beam current to stay <~20 kHz</b>. Data taking is 4 hour-long runs with DAQ configuration '''PROD66''', and trigger '''rgb_v8_1.trg'''.
+
'''Trigger file : rgb_inbending_v9_1.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>
+
<b> Compare the monitoring histograms </b> <!-- from [https://clas12mon.jlab.org/mon12/histograms/?reference=3748541 clas12mon] to the reference and troubleshoot as needed.-->
 +
  
<b><font color=red> At the end of each run, follow the standard DAQ restart sequence '''
+
<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.
"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".</font></b>
+
  
  
<b> Weekly plan for remainder of the run: </b>
+
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]
* 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
+
  
 +
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.
  
 +
------
  
== <font color=blue>''' References and Standards:'''</font>==
+
'''<b> At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font> ''' </b>'''<br>
''(last update 2/10/2019- 12:00 PM)''
+
This needs to be followed at the end of every run. Note: this might be different from the instructions coming up on RunControl.
 +
<b><font color=red>
 +
* "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"
 +
* 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.
  
<b> Restoration of Beam to Hall B</b>
+
 
 +
== <font color=blue>''' References and Standards:'''</font>==
 +
''(last update 1/14/2020- 23:20)''
  
 
<b> Nominal Beam Positions </b>
 
<b> Nominal Beam Positions </b>
*2H01, X: +3.0 mm, Y: -1.0 mm
+
*2H01, X: +1.0 mm, Y: -2.6 mm
*2C24, X: +0.16 mm, Y: 0.26 mm
+
*2C21, X:  0.0 mm, Y:  0.2 mm
 +
*2C24, X: -0.3 mm, Y: -0.8 mm
  
 
<b> FSD Thresholds </b>
 
<b> FSD Thresholds </b>
 
* Upstream: 2000 Hz
 
* Upstream: 2000 Hz
 
* Midstream: 2000 Hz
 
* Midstream: 2000 Hz
* Downstream: 500000 Hz
+
* Downstream: 700000 Hz
* BOM: 35000
+
* BOM: 60000
 +
 
 +
<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/3649356], 2C24 [https://logbooks.jlab.org/entry/3649362]
+
<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 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 (40 nA, production trigger) </b> [https://logbooks.jlab.org/entry/3748541]
  
<b> Reference Monitoring Histograms (20 nA, production trigger) </b> [https://logbooks.jlab.org/entry/3650218]
+
<b> Counter rates </b>
 +
* Upstream counters integrated rates: 0-15 Hz (acceptable up to 100 Hz are acceptable) @50 nA.
 +
* Midstream counters: 10-20 Hz (acceptable up to 50 Hz) @50 nA.
 +
* Counting rates of ~ hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.
  
<b> Reference Monitoring Histograms (35 nA, production trigger) </b> [https://logbooks.jlab.org/entry/3650729]
+
<b> Beamline vacuum: </b> should be not higher than 5e-5.
  
 +
<!---
 
<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 LD2 target, CLAS12 ON (Feb 2019): 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, Empty Target, CLAS12 OFF: 5 nA [https://logbooks.jlab.org/entry/3649436]
+
* Well-tuned CW beam on FC, Empty Target, CLAS12 OFF (Feb 2019): 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 (Feb 2019) [https://logbooks.jlab.org/entry/3649364]
* Well-tuned beam on Tagger Dump at 5 nA during harp scans: [https://logbooks.jlab.org/entry/3649358]  
+
* Well-tuned beam on Tagger Dump at 5 nA during harp scans (Feb 2019): [https://logbooks.jlab.org/entry/3649358]  
 
+
* Reference FTC histogram for 5 nA running (Feb 2019): [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 (Feb 2019): </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]
 +
--->
  
 
| valign=top |
 
| valign=top |
Line 160: Line 187:
 
==<font color=blue>''' General Instructions''':</font>==
 
==<font color=blue>''' General Instructions''':</font>==
  
* 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.
+
* The <b> main lights in the Hall </b> (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.
+
* Do not run more than 30 minutes above 30 nA with 5-pass beam without the <b> beam blocker in front of Faraday cup </b>. 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.
+
* Turn <b> DC HV </b> 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
+
* In case of loss of communication with <b> IOCBTARG </b>, follow instructions at https://logbooks.jlab.org/entry/3502218
* With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem.
+
* With any issue contact On-Call Experts or RC - <b> do not spend more than 15-20 min trying to fix the problem</b>. If the phone is not answered, try the "Page Experts" button on top of CLASCSS.
* 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!
 +
 
  
 
'''Every Shift:'''
 
'''Every Shift:'''
*Follow run plan as outlined by RC
+
* Follow run plan as outlined by RC
 
* If any concern about beam stability, ask MCC if orbit locks are on (they should be).
 
* 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.
 
* Keep shift summary up to date in HBLOG. Record all that happens.
 
* Document any beam condition change and send scaler GUIs to HBLOG
 
* Document any beam condition change and send scaler GUIs to HBLOG
* [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side.
+
* [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side. 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 (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 (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.
* As of 9th of February, once per shift stop and start the gas flow of the FTT (see logbook entry [https://logbooks.jlab.org/entry/3649533] for more details. Check the FTT HV after the procedure. If it is Off, check the status of all gas interlocks, reset the one that is at "Fault" and turn the FTT HV back ON.
 
'''Every Run:'''
 
  
*Log screenshots of:
+
 
** main scaler GUI display  
+
'''Every Run:'''
** Detector occupancy plots from clas12mon
+
*Check values at the start of every run and log screenshots of:
** Trigger rate gui
+
** Main scaler GUI display  
 +
** Trigger rate GUI
 
** Beam strip charts
 
** Beam strip charts
* 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.
+
** FTC scalers
* <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>
+
* 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.
 +
* 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.
  
 
|}
 
|}
  
  
* '''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.'''
+
==<font color=blue>''' Notes / Troubleshooting ''':</font>==
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.
+
 
 +
<b>If crate ADCBAND was rebooted:</b> Contact BAND expert and make a note in the HBBAND logbook and in HBLOG.
  
* ''' Note 2: At the end of each run, follow the standard DAQ restart sequence '''
+
<b> FTOF HVs: </b> 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".
+
** OFF during: initial beam tuning to the Faraday Cup after CLAS12 has been off for a long shutdown, during a Moller run, harp scans, or if there is tuned/pulsed beam in the upstream beamline.
 +
** ON after an initial beam tune has been established and if there are only minor steering adjustments and “tweaks” being made.
 +
** <i>If in doubt, call FTOF expert </i>
  
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.
+
<b>FTT (mmft1) recovery</b>:
  
* '''Note 3: FTOF HVs: The goal is to minimize the number of power cycles of the dividers.
+
** power cycle FTT LV (FT->FTT->turn LV OFF, turn LV ON)
** 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.'''
+
** RunControl "reset"
** should be left on after an initial beam tune has been established and if there are only minor steering adjustments and “tweaks” being made.
+
** roc_reboot mmft1
** 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:
+
<b>Torus and/or Solenoid Fast Dump </b>
 
*# 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
 
*# 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  
 
*# 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
 
*# Notify Run Coordinator
*# Turn off all detectors'''
+
*# Turn off all detectors
  
*'''Note 5: When beam is being delivered to the Faraday Cup:'''
 
*# the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state <font color=red>UNMASKED</font>
 
*# No changes to the FSD threshold should be made without RC or beamline expert approval
 
  
*'''Note 6: Any request for a special run or change of configuration has to be approved by the RC & documented'''
+
<b> Beam to the Faraday Cup: Fast Shut Down elements </b>
 +
* Upstream, Midstream, Downstream, BOM, and Solenoid FSD elements should always be in the state <font color=red>UNMASKED</font>
 +
* No changes to the FSD threshold should be made without RC or beamline expert approval
  
*'''Note 7: 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.'''
+
<b> Turning MVT off: </b> do not press "All HV OFF". Instead go to 'Restore settings' from the MVT overview screen:
 
+
*'''Note 9: Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/?reference=3650729]'''
+
<!--[https://clas12mon.jlab.org/mon12/histograms/?reference=3621580]'''-->
+
 
+
*'''Note 10 Do not Turn OFF MVT HV: 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 12 Always reset the CFD threshold after all power off/on on the CND CAMAC crate'''
 
After the CAMAC crate (camac1) holding the CND CFD boards is switched off for any reason, it is mandatory to reset the associated thresholds typing the
 
following command from any clon machine terminal: $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0
 
  
If this command is failing and the crate is not responding, reboot it as follows: roc_reboot camac1
+
<b> CND CAMAC crate switch on / reboot: </b>
  
*'''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.
+
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:
  
*'''NOTE 14: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766'''
+
$CODA/src/rol/Linux_x86_64/bin/cnd-cfd-thresh -w 0
  
*'''NOTE 15:'''
+
If this command is failing and the crate is not responding, first reboot it as follows: roc_reboot camac1
For RICH recovery procedures, please see Log entry https://logbooks.jlab.org/entry/3562273.  This would apply in the cases of  1. DAQ crash: rich4 is not responding or 2. RICH alarms (LV,missing tile, temperature etc). If it does not work or you are uncertain about what to do, contact the RICH expert on call. <u>Please, note </u> that missing tiles typically occur due to lost communication. Keep in mind that the recovery procedure will kill DAQ. If DAQ is running for other purpose, rather than data taking (for which the RICH acceptance would be important) do not initiate the recovery procedure.
+
** The most critical parameter for RICH is the temperature of the photosensors. If the temperature rises above limits, an interlock will automatically turn the RICH HV and LV. If this happens, notify the expert on call and keep taking data without RICH.
+
  
*'''NOTE 16:''' Asymmetry on FTCal ADC Scalers: If the beam current is 5 - 10 nA, and the observed asymmetry is out of specs, i.e. > +-2.5%, check (1) that the beam position is according to specs, (2) the response of the rest of CLAS (compare the scalers of FTOF, CTOF, ECAL, etc. from the Scalers GUI to the reference for that current, as posted above). If positions and other detectors do not show any anomalies, keep running. The ADC scalers require at least ~15 nA for a reliable response.
+
and then repeat the threshold reset command above.
 +
 
 +
 
 +
<b> Solutions for common SVT issues: </b> see [https://logbooks.jlab.org/entry/3615766]
 +
 
 +
 
 +
<b> RICH recovery procedures: </b> [https://logbooks.jlab.org/entry/3562273]
 +
 
 +
To be followed in case of:
 +
# DAQ crash: rich4 is not responding or
 +
# RICH alarms (LV,missing tile, temperature, etc).
 +
<i> If it does not work or you are uncertain about what to do, contact the RICH expert on call. </i>
 +
<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 purpose other than data taking (for which the RICH acceptance is important) do not initiate the recovery procedure.
 +
The most critical parameter for the RICH is the temperature of the photosensors. If the temperature rises above limits, an interlock will automatically turn the RICH HV and LV off. If this happens, notify the expert on call and keep taking data without RICH.
 +
 
 +
 
 +
<b> Observed asymmetry in FTCal ADC Scalers </b>
 +
 
 +
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 273: Line 329:
  
 
|}
 
|}
 +
== December 2019 - January 2020 Run ==
 +
{| {{TableStyle1}}
 +
| valign=top |
 +
[[Image:rgb_winter_charge.jpg|fall2018_charge.jpeg|700px]]
 +
 +
| valign=top |
 +
[[Image:Rgb_spring_moller.jpg|500px]]
 +
|}
 +
 
== Winter 2019 Run ==
 
== Winter 2019 Run ==
 
{| {{TableStyle1}}
 
{| {{TableStyle1}}
 
| valign=top |
 
| valign=top |
[[Image:rgb_winter_charge.jpg|fall2018_charge.jpg|700px]]
+
[[Image:rgb_winter_charge.jpg|fall2018_charge.jpeg|700px]]
  
 
| valign=top |
 
| valign=top |
Line 286: Line 351:
 
| valign=top |
 
| valign=top |
 
[[Image:rgb_sd_final.jpg|500px]]
 
[[Image:rgb_sd_final.jpg|500px]]
 +
 +
| valign=top |
 +
[[Image:rgb_sprn_dance_10p2.jpg|500px]]
 +
 +
|}
 +
{| {{TableStyle1}}
 +
=== mini-Spin dance ===
 +
| valign=top |
 +
[[Image:rgb_sprn_dance_10p2.jpg|500px]]
 +
 +
| valign=top |
 +
[[Image:Rgb_spring_moller_10p2.jpg|500px]]
 
|}
 
|}
  
Line 297: Line 374:
 
* [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=3650729 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]
 +
 +
===Run lists===
 +
* [https://docs.google.com/spreadsheets/d/1NY1GNIZXPtpB9u4QwP6eNRSrvDkCzFmhQg5RR3V3j7E/edit?usp=sharing  RGB Winter  19 run list]
 +
* [https://docs.google.com/spreadsheets/d/17U7tyDwf1j9sdd4vd6g4ZQdKkDw3WNsdIuBRhiWy6CE/edit?usp=sharing  RGB Fall 19 run list]
  
 
| valign=top |
 
| valign=top |
 
===Accelerator===
 
===Accelerator===
 
* [http://accboard.acc.jlab.org Accelerator Whiteboard]
 
* [http://accboard.acc.jlab.org Accelerator Whiteboard]
* [http://opweb.acc.jlab.org/CSUEApps/bta03/pd_shiftplan_history.php Program Deputy Shift Plans]
+
* [https://accweb.acc.jlab.org/apps/pd/shift-plans 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]
 
* Accelerator daily meetings notes (by Mauri) [https://www.evernote.com/pub/maureeungaro/pdldaily]
 
| 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 RGB meeting] 237353330
+
* [https://bluejeans.com/237353330 Weekly RGB meeting] 237353330
  
 
|}
 
|}

Latest revision as of 22:53, 29 January 2020

[edit]

Shift Schedule

Shift Checklist

Hot Checkout

Beam Time Accounting

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

Person Phone Number
Run Coordinator 9-757 575-7540 (cell)
Physics Division Liaison 9-757 876-1789 (cell)
Shift Expert 5244 or 9-757 329-4846 (cell)
Shift Worker 5126
MCC-OPS 7048
Crew Chief 7045
Crew Chief 9-757 876-3367 (cell)
Program Deputy 9-757 876-7997 (cell)
Engineering on-call 9-757 748-5048 (cell)
Engineering on-call secondary 9-757 897-9060 (cell)
Radcon (needed for target cell swaps) 9-757 876-1743 (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) Yuri 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) Jose Carvajal
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
Pol. Target On-Call (757) 218 2266 (cell) Tsuneo Kageya
Polarized Target (757) 746-9277 (cell) Chris Keith
Polarized Target (757) 897-1415 (cell) James Maxwell
Polarized Target (757) 871-5374 (cell) James Brock
Target (not used) (757) 822-9586 (cell) Bob Miller Primary
Target (not used) (757) 897-9060 (cell) Denny Insley Secondary
Counting House C x6000
Counting House D x5504

In case of a problem with superconducting magnets call Engineering on-call first, particularly if it is related to cryo.
For all other superconducting magnet problems call magnet group.
Their schedule and phone numbers are posted on the wall next to the Saclay target computer.




Click Here to edit Phone Numbers. Note, you then also have to edit this page to force a refresh.


CLAS12 Run Group B, December 2019 - January 2020
Beam energy ~10.4 GeV (5 pass)
Important: Document all your work in the logbook!

RC: Bryan McKinnon

PDL: Maurizio Ungaro



Run Plan: Jan 29 - 30 2020

  • Wednesday
    • 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) include the DAQ gui 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 trigger structure (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

Trigger file : rgb_inbending_v9_1.trg


Compare the monitoring histograms


Run database: 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") -- please label junk runs if you get the chance. Please also keep a record of run numbers and their conditions in the shift summary. The information you enter in the dialogue box goes directly into the run database -- it's our primary source of run info and mistakes are hard to correct a posteriori.


Please run the script to look at trigger structure once per shift and check that you get a smooth distribution. Instructions are here: [1]

Keep an eye on CND channel S14L1R -- it's a bit temperamental. If it trips, switch HV off and on again for it and make an entry in the log book.


At the end of each run, follow the STANDARD DAQ RESTART SEQUENCE
This needs to be followed at the end of every run. 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"
  • After each step, make sure it completed in the Run Control message window. 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.


References and Standards:

(last update 1/14/2020- 23:20)

Nominal Beam Positions

  • 2H01, X: +1.0 mm, Y: -2.6 mm
  • 2C21, X: 0.0 mm, Y: 0.2 mm
  • 2C24, X: -0.3 mm, Y: -0.8 mm

FSD Thresholds

  • Upstream: 2000 Hz
  • Midstream: 2000 Hz
  • Downstream: 700000 Hz
  • BOM: 60000

Reference Harp Scans for Beam on Faraday Cup: 2C21 [2], 2C24 (tagger harp) [3], 2H01 [4]

Reference Harp Scans for Beam on Tagger dump: 2C21 [5], 2C24 (tagger harp) [6]

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

Counter rates

  • Upstream counters integrated rates: 0-15 Hz (acceptable up to 100 Hz are acceptable) @50 nA.
  • Midstream counters: 10-20 Hz (acceptable up to 50 Hz) @50 nA.
  • Counting rates of ~ hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.

Beamline vacuum: should be not higher than 5e-5.


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. If the phone is not answered, try the "Page Experts" button on top of CLASCSS.
  • Check for and read any comments to log-book entries made during your shift!


Every Shift:

  • Follow run plan as outlined by RC
  • If any concern about beam stability, ask MCC if orbit locks are on (they should be).
  • Keep shift summary up to date in HBLOG. Record all that happens.
  • Document any beam condition change and send scaler GUIs to HBLOG
  • Fill out BTA hourly. Click "Load from EPICS" to automatically fill the left side. Run the script btaGet.py 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 (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 (some detectors have buttons at the bottom to toggle between the sectors -- please check all of them).
  • Fill and submit the shift checklist in the logbook
  • Run script to check smoothness of the trigger time structure: [8]
  • Monitor the SVT Slow Controls status, post plot of current stability in the HBSVT elog once per shift.


Every Run:

  • Check values at the start of every run and log screenshots of:
    • Main scaler GUI display
    • Trigger rate GUI
    • Beam strip charts
    • FTC scalers
  • At the start and end of every run, check that the data filled in the database run list is correct (especially fields which are filled in manually, like beam current and comments). This replaces the previously-used spreadsheet.
  • 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 FTOF.


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.


Notes / Troubleshooting :

If crate ADCBAND was rebooted: Contact BAND expert and make a note in the HBBAND logbook and in HBLOG.

FTOF HVs: The goal is to minimize the number of power cycles of the dividers.

    • OFF during: initial beam tuning to the Faraday Cup after CLAS12 has been off for a long shutdown, during a Moller run, harp scans, or if there is tuned/pulsed beam in the upstream beamline.
    • ON after an initial beam tune has been established and if there are only minor steering adjustments and “tweaks” being made.
    • If in doubt, call FTOF expert

FTT (mmft1) recovery:

    • power cycle FTT LV (FT->FTT->turn LV OFF, turn LV ON)
    • RunControl "reset"
    • roc_reboot mmft1

Torus and/or Solenoid Fast Dump

    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


Beam to the Faraday Cup: Fast Shut Down elements

  • Upstream, Midstream, Downstream, BOM, and Solenoid FSD elements should always be in the state UNMASKED
  • No changes to the FSD threshold should be made without RC or beamline expert approval


Turning 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


CND CAMAC crate switch on / reboot:

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

If this command is failing and the crate is not responding, first reboot it as follows: roc_reboot camac1

and then repeat the threshold reset command above.


Solutions for common SVT issues: see [9]


RICH recovery procedures: [10]

To be followed in case 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 purpose other than data taking (for which the RICH acceptance is important) do not initiate the recovery procedure. The most critical parameter for the RICH is the temperature of the photosensors. If the temperature rises above limits, an interlock will automatically turn the RICH HV and LV off. If this happens, notify the expert on call and keep taking data without RICH.


Observed asymmetry in FTCal ADC Scalers

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.


CED display not showing events

Sometimes, CED screens are up but not active (events not showing at all). To solve this:

  1. Close the CED sceen
  2. ssh to clondaq4
  3. Once in the right machine, type ced, and wait for the windows to appear.
  4. Go to "File" -> "Connect to ET ring". Make sure to select clondaq6, as the online data is being streamed.
  5. 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.


Clas12design.png