Difference between revisions of "Run Group B"

From clas12-run
Jump to navigation Jump to search
(Created page with "= Shift Documentation = <!--####################################### SHIFT DOCUMENTATION ########################################--> {| {{TableStyle1}} | valign=top | <!--==...")
 
 
(598 intermediate revisions by 16 users not shown)
Line 14: Line 14:
 
| 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://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/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/b/b0/Ftof_manual.pdf  FTOF]
 
 
* [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://www.jlab.org/Hall-B/ftof/notes/ftof_manual.pdf  FTOF]
 +
* [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]
 +
* [[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]
* [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]]
+
* [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf Performing M&oslash;ller Runs]
 
* [[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]
Line 49: Line 50:
 
* [https://logbooks.jlab.org/book/hclog Hall-C]
 
* [https://logbooks.jlab.org/book/hclog Hall-C]
 
* [https://logbooks.jlab.org/book/hdlog Hall-D]
 
* [https://logbooks.jlab.org/book/hdlog Hall-D]
 +
 +
| valign=top |
 +
===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
 +
 
</font>
 
</font>
  
Line 56: Line 69:
 
<!--#######################################  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=Engineering_Run&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_B&action=edit&section=11 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  ################################################-->
 
<!--#######################################  SHORT TERM  ################################################-->
 
<center><font color=blue size=4>
 
<center><font color=blue size=4>
''' CLAS12 Run Group A, Winter 2018 </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/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/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: Latifa Elouadrhiri ==
+
== RC: Bryan McKinnon ==
 
* (757) 575-7540   
 
* (757) 575-7540   
 
* 9 575 7540 from Counting Room
 
* 9 575 7540 from Counting Room
* latifa@jlab.org
+
* [mailto:mckinnon@jlab.org mckinnon@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
* pasyuk@jlab.org
+
* [mailto:ungaro@jlab.org ungaro@jlab.org]
  
 
<br>
 
<br>
 +
 
 +
 +
{| {{TableStyle1}}
 +
 +
| valign=top width=50% |
 +
== <font color=blue>''' Run Plan: Jan 29 - 30 2020 '''</font>==
  
* 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.
+
* Wednesday
 +
** Owl - Production data at 50nA
 +
** Day - Production data at 50nA
 +
** Swing - Production data at 50nA
  
* Note 2: At the end of each run, follow the DAQ restart sequence "end run", "abort", "reset", "download", "prestart", "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.
+
*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
  
* Note 3: Nominal beam positions: '''2C21 (X=-0.1 mm, Y=0.1 mm), 2C24 (X=0.5mm, Y=-0.5 mm), 2H01 (X=0.7 mm, Y=-2.0 mm)'''
 
  
* Note 4: With beam to the Faraday Cup, typical rates on all halo counters upstream from the target should be either 0 or of the order of few counts. Count rates in the range of tens or more may indicate bad beam tune or bleed-through from other Halls.
+
* 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>
  
{| {{TableStyle1}}
+
'''Trigger file : rgb_inbending_v9_1.trg '''
 +
 
 +
 
 +
<b> Compare the monitoring histograms </b> <!-- from [https://clas12mon.jlab.org/mon12/histograms/?reference=3748541 clas12mon] to the reference and troubleshoot as needed.-->
 +
 +
 
 +
<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.
 +
 
 +
 
 +
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]
 +
 
 +
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.
 +
 
 +
------
 +
 
 +
'''<b> At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font> ''' </b>'''<br>
 +
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.
  
| valign=top width=50% |
 
  
== <font color=blue>''' Run Plan:'''</font>==
+
== <font color=blue>''' References and Standards:'''</font>==
''(last update 2/14- 8:30 AM)''
+
''(last update 1/14/2020- 23:20)''
*<font color=red> '''Always monitor the rates on the Halo counters when they are tuning beam to the other halls'''
 
* '''Do Not turn on or off SVT only SVT expert can do that'''
 
'''</font>
 
  
<!--
+
<b> Nominal Beam Positions </b>
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.  
+
*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
  
* Change the TORUS poalrity to -2827 A (By trained personnel)
+
<b> FSD Thresholds </b>
* At the same time Check the beam tune:
+
* Upstream: 2000 Hz
** Turn off the detectors: SVT (contact expert to do it), MVT (see [https://wiki.jlab.org/clas12-run/images/b/bf/MVT_for_Dummies.pdf instructions]), CND, CTOF, FTT, HTCC, DC, FTOF
+
* Midstream: 2000 Hz
** Follow the instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]. Compare harp scan to the standards at [https://logbooks.jlab.org/entry/3527777 2C21] and [https://logbooks.jlab.org/entry/3527790 2C24]. Consult with the beamline expert in case of issues.</s>
+
* Downstream: 700000 Hz
** If beam profiles at the tagger are acceptable, move to beam tuning to the Faraday Cup with a 5 nA beam. Again, refer to the instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]. Compare harp scan with the standard at [https://logbooks.jlab.org/entry/3527871 2H01].
+
* BOM: 60000
** If beam quality is not good call beamline expert
 
** Once beam to Faraday Cup is established, prepare to start data taking. Switch on all detectors, except the MM and the RICH with 5 nA beam; contact expert to switch on SVT.
 
* Call MCC for beam at 5nA check that the beam position and rates are Ok before moving to 20 nA
 
* Once the beam quality is establiched call Sergey and valery to start the runs for trigger studies (Random & HTCC efficiency studies and FT) this will take about 5 to 6 hours
 
* 11:30 Maxime started the gas for the MVT then he will turn the HV on
 
* Once the trigger studies completed contact RICH detctor expert to change RICH detecor configuration
 
*Then ask MCC for 15 nA and start production runs
 
* Take data at 15 nA with PROD/elec_6gev_htcc_1phe_pcal_150.trg for 2 hours
 
* Continue data taking at 15nA starting a new run every 2 hours until 6:30 am
 
* At 6:30, first turn off HV for MVT, once the HV channels are OFF (~30 sec for the ramp down), turn off MVT gas OFF.
 
* At 7:00 am MVT expert will come to take a run without gas flow, it will be dedicated run of 15-20 mn-->
 
  
 +
<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]
  
<font color=blue>''' Plan for February 14 Day Shift '''</font>
+
<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/3748541]
  
* Take production data with at 25 nA, 2hours/run Note that we are running with  SVT is OFF and it will remain OFF  until the cooling issue is fixed.
+
<b> Counter rates </b>
* MCC will take beam away for about one hour starting 8:45
+
* Upstream counters integrated rates: 0-15 Hz (acceptable up to 100 Hz are acceptable) @50 nA.
* We will ask for controlled access for Morgan to wok on one board of the DC
+
* Midstream counters: 10-20 Hz (acceptable up to 50 Hz) @50 nA.
* Call Dan and Cole to adjust FADC and TDC window  the PMT-based detectors
+
* Counting rates of ~ hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.
* Once this they are done, call Maurizio  to take data for LTCC calibration/setting
 
* After LTCC  calibration data taking is complete Resume normal data taking
 
* Follow the RC plan and the instruction for beam and data quality monitoring and documentation/run
 
* In case of questions contact the RC or system expert
 
  
 +
<b> Beamline vacuum: </b> should be not higher than 5e-5.
  
<!--
+
<!---
'''[[Every Shift:]]'''
+
<b> Reference Scalers and Halo-Counter Rates: </b>
*Follow run plan as outlined by RC
+
* Well-tuned CW beam on FC, Full LD2 target, CLAS12 ON (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]
* If any concern about beam stability, ask MCC if orbit locks are on (they should be).
+
* Well-tuned CW beam on FC, Empty Target, CLAS12 OFF (Feb 2019): 5 nA [https://logbooks.jlab.org/entry/3649436]
* Keep shift summary up to date in HBLOG. Record all that happens.
+
* Well-tuned beam during Moller run  (Feb 2019) [https://logbooks.jlab.org/entry/3649364]
* Check on white board all scalers, strip charts and monitoring plots that need to be logged regularly
+
* Well-tuned beam on Tagger Dump at 5 nA during harp scans (Feb 2019): [https://logbooks.jlab.org/entry/3649358]  
* Document any beam condition change and send scaler GUIs to HBLOG
+
* Reference FTC histogram for 5 nA running (Feb 2019): [https://logbooks.jlab.org/entry/3665122]
* [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:]]'''
+
<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]
*Log screenshots of:
+
--->
* main scaler GUI display
 
* Detector occupancy plots
 
* Trigger rate gui
 
* Beam strip charts
 
  
-->
 
 
| valign=top |
 
| valign=top |
  
 
==<font color=blue>''' General Instructions''':</font>==
 
==<font color=blue>''' General Instructions''':</font>==
  
* For a given beam current, compute the FSD thresholds according to the [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf Establish Physics Quality Beam] document. Call MCC to update the values. Contact the beamline expert if there are questions about setting the FSD thresholds.
+
* The <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.
* 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 <b> beam blocker in front of Faraday cup </b>. Put beam blocker in for long running at high currents for 5 pass operations.
* 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 <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.
* 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 <b> IOCBTARG </b>, follow instructions at https://logbooks.jlab.org/entry/3502218
* 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 - <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.
* 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!
* All jscaler iocs (iocjscalerX) on the health screen (under DAQ tab) must be restarted after every DAQ prestart is completed.
+
 
* 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''':
+
'''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.
* 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
 
* 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!
# Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
+
* 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).
# Perform 2H01A harp scan once per shift or when beam conditions have changed, based on beam monitors (BPMs, halo rates, beam-viewer). During harp scans the HV for DC and HTCC should be OFF.
+
** 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]
 +
* 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.
 +
 
 +
 
 +
'''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 [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>
 +
 
  
[['''Every Run:''']]
+
'''To access the Hall:'''
*Log screenshots of:
+
* 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).
* main scaler GUI display
+
* Check in with the shift personnel before entering the hall.
* Detector occupancy plots
 
* Trigger rate gui
 
* Beam strip charts
 
  
 
|}
 
|}
 +
 +
 +
==<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.
 +
** 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>
 +
 +
<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>
 +
*# Notify MCC to request beam OFF and to drop Hall B status to Power Permit
 +
*# Call Engineering on-call
 +
*# Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org
 +
*# Notify Run Coordinator
 +
*# Turn off all detectors
 +
 +
 +
<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
 +
 +
 +
<b> Turning MVT off: </b> do not press "All HV OFF". Instead go to 'Restore settings' from the MVT overview screen:
 +
*# SafeMode.snp for beam tuning and Moeller runs
 +
*# MV_HV_FullField.snp for full solenoid field
 +
*# MV_HV_MidField.snp wgeb solenoid < 4T
 +
 +
 +
<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, 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.
 +
 +
 +
<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 203: Line 321:
 
===Epics on the web===
 
===Epics on the web===
 
*[https://hallbopi.jlab.org/webopi3.3/w WebOPI] (CUE Login)
 
*[https://hallbopi.jlab.org/webopi3.3/w WebOPI] (CUE Login)
 +
 +
| valign=top |
 +
===Runs and Coooking Info===
 +
*[https://docs.google.com/spreadsheets/d/1NY1GNIZXPtpB9u4QwP6eNRSrvDkCzFmhQg5RR3V3j7E/edit?usp=sharing Google Spreadsheet Run list]
 +
*[https://clas12mon.jlab.org/fstree Run list of decoded and cooked files (auto updating every 30m)]
 +
*[https://jeffersonlab-my.sharepoint.com/:x:/g/personal/zwzhao_jlab_org/Ef0DF0RF5UpCvKrwZf5u4cAB3IYkCp8-vaXCk8NmjewvKw?e=cSQB3m Run list with decoding and cooking software version/condition]
  
 +
|}
 +
== 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 ==
 +
{| {{TableStyle1}}
 +
| valign=top |
 +
[[Image:rgb_winter_charge.jpg|fall2018_charge.jpeg|700px]]
 +
 +
| valign=top |
 +
[[Image:Rgb_spring_moller.jpg|500px]]
 +
|}
 +
 +
{| {{TableStyle1}}
 +
=== mini-Spin dance ===
 +
| valign=top |
 +
[[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 212: Line 371:
 
===Hall-B===
 
===Hall-B===
 
* [https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc Operation Safety Procedures]
 
* [https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc Operation Safety Procedures]
* [https://wiki.jlab.org/clas12-run/index.php/Engineering_Run Engineering Run Wiki]
 
* [https://clasweb.jlab.org/wiki/index.php/Engineering_Run_Analysis Offline Analysis Wiki]
 
 
* [http://clasweb.jlab.org/rcdb RCDB]
 
* [http://clasweb.jlab.org/rcdb RCDB]
 +
* [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/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/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]
 
| valign=top |
 
| valign=top |
===Bluejean meetings===
+
===Bluejeans meetings===
* [https://bluejeans.com/502085879 Daily analysis meeting] 502085879
+
* [https://bluejeans.com/8928008153 Daily Run meeting] 8928008153
* [https://bluejeans.com/502085879 Daily Run meeting] 502085879
+
* [https://bluejeans.com/237353330 Weekly RGB meeting] 237353330
* [https://bluejeans.com/7572697303 RGA Wed meeting] 7572697303
+
 
 
|}
 
|}
  

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

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 (757) 344-7204 (cell) Daniel Carman
CND (757) 329-4844 (cell) Pierre Chatagnon
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)
Valery Kubarovsky (primary)
Nathan Baltzell (secondary)
DAQ (757) 232-6221 (cell) Sergey Boiarinov
Cryotarget (757) 218-2266 (cell)
(757) 871-5374 (cell)
(757) 897-1415 (cell)
(757) 746-9277 (cell)
Xiangdong Wei (first)
James Brock (second)
James Maxwell (third)
Chris Keith (fourth)
RG-E Solid Target (757) 344-1848 (cell) Antonio Radic
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 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