Difference between revisions of "Run Group K"

From clas12-run
Jump to navigation Jump to search
(new reference run mon12)
 
(69 intermediate revisions by 3 users not shown)
Line 9: Line 9:
 
===[http://www.jlab.org/Hall-B/shifts Shift Schedule]===
 
===[http://www.jlab.org/Hall-B/shifts Shift Schedule]===
 
===[https://docs.google.com/spreadsheets/d/1p_NaWUtR5q7lrO3np076EcClwUNqVzb2NymTndiqI8k/edit?usp=sharing Run Coordinator Schedule]===
 
===[https://docs.google.com/spreadsheets/d/1p_NaWUtR5q7lrO3np076EcClwUNqVzb2NymTndiqI8k/edit?usp=sharing Run Coordinator Schedule]===
===[https://www.jlab.org/Hall-B/run-web/rgk/ESAD_HallB-CLAS12_rgK.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rgk/COO_HallB-CLAS12_RGK.pdf COO], [https://www.jlab.org/Hall-B/run-web/rgk/RSAD_HallB-CLAS12_rgk.pdf RSAD]===
 
 
===[https://logbooks.jlab.org/checklists/151 Shift Checklist] ===
 
===[https://logbooks.jlab.org/checklists/151 Shift Checklist] ===
 
===[https://ace.jlab.org/btm/timesheet/eb Beam Time Accounting]===
 
===[https://ace.jlab.org/btm/timesheet/eb Beam Time Accounting]===
 
* '''[https://ace.jlab.org/cdn/doc/btm/userguide.pdf Beam Time Accounting User Guide]'''.
 
* '''[https://ace.jlab.org/cdn/doc/btm/userguide.pdf Beam Time Accounting User Guide]'''.
 
===[https://accweb.acc.jlab.org/hco/readiness Hot Checkout]===
 
===[https://accweb.acc.jlab.org/hco/readiness Hot Checkout]===
 +
===[https://www.jlab.org/Hall-B/run-web/rgk/ESAD_HallB-CLAS12_rgK.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rgk/COO_HallB-CLAS12_RGK.pdf COO], [https://www.jlab.org/Hall-B/run-web/rgk/RSAD_HallB-CLAS12_rgk.pdf RSAD], [https://www.jlab.org/sites/default/files/Hall-B_ERG_09012023%20updated.pdf ERG] ===
  
 
| valign=top |
 
| valign=top |
Line 21: Line 21:
 
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus]
 
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus]
 
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid]
 
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid]
* [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q Cryotarget & Flag Assembly Controls]
+
* [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q Cryotarget]
 
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/daq/opman_master.pdf DAQ]
 
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/daq/opman_master.pdf DAQ]
 
* [[Media:clas12controls_shift.pdf|Slow Controls]]
 
* [[Media:clas12controls_shift.pdf|Slow Controls]]
Line 40: Line 40:
 
=====Software=====
 
=====Software=====
 
* [https://wiki.jlab.org/clas12-run/images/c/c9/CedManual.pdf CED]
 
* [https://wiki.jlab.org/clas12-run/images/c/c9/CedManual.pdf CED]
* [https://wiki.jlab.org/clas12-run/images/f/fd/CLAS12Mon_documentation.pdf MON12]
+
* [https://wiki.jlab.org/clas12-run/images/f/fd/CLAS12Mon_documentation.pdf mon12]
  
 
| valign=top |
 
| valign=top |
Line 73: Line 73:
  
 
<!--#######################################  GENERAL INFORMATION  #############################################-->
 
<!--#######################################  GENERAL INFORMATION  #############################################-->
= GENERAL INFORMATION =
+
= General Information =
  
 
This tab contains information on  
 
This tab contains information on  
Line 82: Line 82:
 
== '''Recent Changes''' ==
 
== '''Recent Changes''' ==
  
=== New MVT LV Reboot Procedure ===
+
=== New '''MVT LV''' Reboot Procedure ===
* See '''https://logbooks.jlab.org/entry/4217011''' for detailed information on rebooting the MVT LV when observing a drop in BMT strip occupancies. In brief, it requires a reboot of LV as follows:
+
See '''https://logbooks.jlab.org/entry/4217011''' for detailed information on rebooting the MVT LV when observing a drop in BMT strip occupancies. This gets done upon request of DAQ or MVT expert only.
 
* Turn '''LV OFF from MVT Overview->Low Voltage->MVT-All'''. LV status indicators should change from green to black;  
 
* Turn '''LV OFF from MVT Overview->Low Voltage->MVT-All'''. LV status indicators should change from green to black;  
* '''Wait 20 seconds''', then '''turn LV back from the same menu''';
+
* '''Wait 20 seconds''', then '''turn LV back from the same menu'''.
* In the alarm handler, with a 2-minute alarm delay, there can be alarm NActiveCrates, status also reported on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON;
+
* In the alarm handler, with a 2-minute alarm delay, there can be an alarm "NActiveCrates", the status is also seen on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON.
* At this point, mvt1, mvt2, and mvt3 ROCS can be rebooted;
+
* Reboot mvt1, mvt2, and mvt3 ROCS.
* Start a run (Cancel &rarr; Reset &rarr; Configure &rarr; Download &rarr; Prestart &rarr; Go).  
+
* Start a run with restart DAQ (Cancel &rarr; Reset &rarr; Configure &rarr; Download &rarr; Prestart &rarr; Go).  
* '''If the beam is ON, and a reboot process takes more than 5 min, please call the DAQ and/or SVT/MVT/MM expert'''.  
+
* '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.  
  
=== RICH alarm ===
+
=== RICH issues ===
* Make a logbook entry with screen shots of the RICH temperature and scaler screens, notify the RICH expert (vpk@jlab.org).
+
* The RICH fibers alarm leads to web guidance aka logbook entry [https://logbooks.jlab.org/entry/3562273 3562273 - RICH recovery procedure].  
* If the DAQ did not crash continue data taking.
+
* Check the RICH manual for the current guidance: '''https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf'''
* For the next run, "restart DAQ".
+
* See below for current issues
* If you still see dead RICH tiles in the temperature or scaler maps.
 
** Make another logbook entry with screenshots,
 
** Do a full RICH recovery after the run.
 
* If it did not help call the RICH expert.
 
* Remember to "restart DAQ" for the next run after full recovery.
 
  
 
=== Rapid/Controlled Access to the Hall ===
 
=== Rapid/Controlled Access to the Hall ===
Line 109: Line 104:
 
* choose the option to "'''join from browser'''" (''Chrome is recommended'') and ignore all other messages to update the ZOOM APP in the pop-up windows,.  
 
* choose the option to "'''join from browser'''" (''Chrome is recommended'') and ignore all other messages to update the ZOOM APP in the pop-up windows,.  
 
* Enter the passcode from the logbook entry in tab  "Shift Worker"
 
* Enter the passcode from the logbook entry in tab  "Shift Worker"
 
  
 
== '''Current Issues''' ==  
 
== '''Current Issues''' ==  
Line 130: Line 124:
 
* '''Tagger Magnet Procedure:''' If the tagger magnet needs to be turned off, tell the operator to '''ONLY''' use '''the script for degaussing, NEVER do it "by hand"!''' The latter method might/will trip the circuit breaker for the power supply in the Hall.
 
* '''Tagger Magnet Procedure:''' If the tagger magnet needs to be turned off, tell the operator to '''ONLY''' use '''the script for degaussing, NEVER do it "by hand"!''' The latter method might/will trip the circuit breaker for the power supply in the Hall.
  
=== BMT/SVT ===
+
=== BMT / SVT ===
 
* If new hot channels appear, '''call the SVT/MM expert Yuri Gotra''' (757-541-7539). These channels need to be addressed by the expert.
 
* If new hot channels appear, '''call the SVT/MM expert Yuri Gotra''' (757-541-7539). These channels need to be addressed by the expert.
* '''BMT HV trips''': no screenshots are necessary, power-cycle the channel HV '''as fast as possible''' (the ''underlying script will take care of ramping it up''), note the trip and sector/layer in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.
+
* '''BMT HV trips''': no screenshots are necessary, power-cycle the channel HV '''as fast as possible''' (the ''underlying script will take care of ramping it up''), note the information in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.
* BMT S1L5 strip is OFF
+
* BMT HV S1 L2 STRIP in safe mode (low voltage) by expert - appears blue in MVT overview
 +
* BMT HV S1 L5 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
 +
* BMT HV S2 L6 STRIP and DRIFT are OFF (Vset=0V) - appears blue in MVT overview
 +
 
 +
=== CND ===
 +
* CAMAC crate alarm:
 +
** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, can be done via the alarm handler.
 +
** After reboot, the CFD thresholds need to be set by running a script, see page 12 in the CND manual at tab "General", https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf
  
 
=== DAQ ===
 
=== DAQ ===
 
* Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected!   
 
* Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected!   
 
* <font color=red>'''NEW STANDARD''' end and start of the run:</font> End run, Cancel, Reset, <u> Download</u> , Prestart, Go. This will ensure proper compression of the FADCs and therefore a smaller data rate.
 
* <font color=red>'''NEW STANDARD''' end and start of the run:</font> End run, Cancel, Reset, <u> Download</u> , Prestart, Go. This will ensure proper compression of the FADCs and therefore a smaller data rate.
 +
* roc reboot instructions:
 +
** To reboot i.e. adcecal1, type on a clasrun terminal: clasrun> roc_reboot adcecal1
 +
** To check that the crate is back alive, type:clasrun> ping adcecal1
 +
** The ping will start to answer as soon as the crate communicates again.
  
 
=== DC ===
 
=== DC ===
 
* Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.
 
* Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.
 +
 +
=== ECAL/PCAL ===
 +
*  "ECAL_SEC6_UO26 Noisy" https://logbooks.jlab.org/entry/4241957
 +
* "PCAL_HV_SEC2_U25 turned off" https://logbooks.jlab.org/entry/4247187, https://logbooks.jlab.org/entry/4247400
  
 
=== FTOF ===
 
=== FTOF ===
 
* FTOF S2 Paddle 19-left and S4 Paddle 16-left are known to be "weak" channels that tend to come and go depending on torus polarity and rates. This cannot be fixed during this run period; see https://logbooks.jlab.org/entry/4219555 and https://logbooks.jlab.org/entry/4219876.
 
* FTOF S2 Paddle 19-left and S4 Paddle 16-left are known to be "weak" channels that tend to come and go depending on torus polarity and rates. This cannot be fixed during this run period; see https://logbooks.jlab.org/entry/4219555 and https://logbooks.jlab.org/entry/4219876.
 +
* "FTOF HV Adjustment - S5 P2 2R" https://logbooks.jlab.org/entry/4249754
  
 
=== RICH ===
 
=== RICH ===
* RICH Sector 1 has three missing tiles; this is known, and no action is required from the shifters.
+
* '''Known problematic PMTs and tile''':
 
+
** You don't need to report about it.
 +
** PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.
 +
** Problematic tiles and PMTs:
 +
*** Sector 1 Tile 21 dead (PMT 55,56,57)
 +
*** Sector 1 Tile 1 PMT 2
 +
*** Sector 4 Tile 34 PMT 92
  
 
== '''Beam Restoration''' ==  
 
== '''Beam Restoration''' ==  
  
 
* Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]. If you do not feel confident to do this by yourself, contact the Beamline Expert.
 
* Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]. If you do not feel confident to do this by yourself, contact the Beamline Expert.
 +
 +
* Find all Reference values on the white board at tab Short_Term_Schedule
  
 
=== Restoring Beam after Short Downtime ===
 
=== Restoring Beam after Short Downtime ===
Line 158: Line 175:
 
** beam steering or orbit change
 
** beam steering or orbit change
 
** change in beam current, e.g., after a target change
 
** change in beam current, e.g., after a target change
** If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values, see run wiki tab "Short Term Schedule"
+
** If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values
** The beam position at 2C21A is not important for production
+
 
 +
=== Beam Tuning to Tagger Yoke Dump ===
 +
 
 +
Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam].
 +
* Contact Eugene Pasyuk if issues arise.
  
=== Beam Tuning to Tagger Dump ===
+
* Ask MCC to energize the tagger magnet
 +
:- blank collimator
 +
:- beam type "Photon"
  
* Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam], and take into account the first steps mentioned therein.
+
* All CLAS12 detectors HV off (BMT HV in safe mode)
:&loz; Make sure the BMT along FMT is in SAFE mode, SVT HV is OFF, (LV is ALWAYS ON), and all other CLAS12 detectors HV are OFF.
 
  
* A few points to note:
+
* Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM)  
:&bull; Change the beam type to "Photon" from the "BTA Config"
+
* Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
:&bull; Ask MCC to energize the tagger magnet
+
* If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values
:&bull; Move the collimator to the Blank position after the tagger is energized
+
* Take harp scans
:&bull; Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM)  
+
:- at Harp 2C21A (Upstream Right Counter)
:&bull; Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
+
:- at Tagger Harp 2C24A Upstream Right Counter)
:&bull; Check the 2C21A and 2C24A beam positions (x, y) against the Reference Values (tab "Short Term Schedule")
+
* If the beam trips, abort the scan and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.  
::- If the beam positions are OFF, ask MCC to bring them to the reference values.
+
* Compare the results with the Harp Scan References
:&bull; In case the two BPMs (x, y) positions look good, take a harp scan (HS) at Harp 2C21 (Upstream Right Counter) and Tagger Harp (2C24; Upstream Right Counter)
+
* The fit ranges might need to be adjusted manually to assess the fit results
::- It should be noted that the beam must be ON during the scan. Once OFF, abort and restart once the beam is back.  
+
 
::- Compare the results with the HS References (run wiki tab "Short Term Schedule") and bear in mind that the fit ranges might need to be adjusted manually to assess the fit results;
+
* If good, log the new scan results.
::- If good, log the new scan results.
 
  
 
=== M&oslash;ller run ===
 
=== M&oslash;ller run ===
  
 
Follow the standard procedure as described in the manual [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf Performing M&oslash;ller Runs].
 
Follow the standard procedure as described in the manual [https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf Performing M&oslash;ller Runs].
 +
* Contact Nathan Baltzell if issues arise
  
 
A few points to note:
 
A few points to note:
* '''Request 20 nA''' , Orbit Locks should be OFF;
+
* '''Request 20 nA''' , Orbit Locks should be off
 
* The BPMs 2C21 and 2C24A may be out of range after the M&oslash;ller configuration.   
 
* The BPMs 2C21 and 2C24A may be out of range after the M&oslash;ller configuration.   
 
* Keep running until the polarization uncertainty is < 1.5%
 
* Keep running until the polarization uncertainty is < 1.5%
Line 190: Line 212:
 
=== Beam Tuning to Faraday Cup ===
 
=== Beam Tuning to Faraday Cup ===
  
Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam], and take into account the first steps mentioned therein. This is typically done after tuning to the tagger dump (and possibly taking a Moller run).  
+
Study the manual: [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam], and take into account the first steps mentioned therein.  
 +
 
 +
This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
 +
 
 +
* All CLAS12 detectors HV off (BMT HV in safe mode)
  
A few points to note:
+
* Ask MCC to de-energize the tagger magnet
* Change the beam type to "Electron";
+
:- 20 mm collimator
* Ask MCC to de-energize the tagger magnet, which includes degaussing the tagger magnet and turning the power supply OFF;
+
:- beam type electron
* ''Ask the operator to use the script only, not try it by hand, as this might trip the circuit breaker of the tagger magnet power supply.''
+
:- beam blocker out
* (If initial beam tune, target should be "Empty")
+
* If initial beam tune, target should be "Empty"
* Make sure the Beam Blocker is OUT
 
* Move the collimator to the 20 mm position
 
 
* Ask MCC to unmask beam halos
 
* Ask MCC to unmask beam halos
 
* Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds
 
* Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds
 
* Insert the Downstream Viewer, Chromax, in the beamline
 
* Insert the Downstream Viewer, Chromax, in the beamline
 
* Ask MCC for 5 nA beam current
 
* Ask MCC for 5 nA beam current
** If the 2C24A and 2H01  beam positions are OFF, ask MCC to bring them to the reference values (see run wiki tab Short_Term_Schedule)
+
* If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the Reference Values
** In case the BPM (x, y) positions look good, take a harp scan at 2H01 (Midstream Left)
+
* Take a harp scan at 2H01 (Midstream Left)
** The beam must be ON during the scan. Once OFF, abort and restart once the beam is back
+
* If the beam trips, abort and restart. The beam must be on during the scan, otherwise the fit to the beam profile will not work.
** Compare the results with the harp scan references (see tab Short_Term_Schedule)
+
* Compare the results with the Harp Scan References
** If good, log the new scan results.
+
* If good, log the new scan results.
  
 
Once done and before resuming the production data-taking:
 
Once done and before resuming the production data-taking:
* Retract the Downstream Viewer from the beamline;
+
* Retract the Downstream Viewer from the beamline
* Put the FSDs thresholds and integration time to their reference values;
+
* Put the FSDs thresholds and integration time to their reference values
* Turn all detector HV ON, for MVT  "HV ON - Full Voltage";
+
* Turn all detector HV ON, for MVT  "HV ON - Full Voltage"
 
* MCC might need to adjust the beam positions after going to the production beam current.
 
* MCC might need to adjust the beam positions after going to the production beam current.
 
  
 
<!--#######################################  Shift Expert  ################################################-->
 
<!--#######################################  Shift Expert  ################################################-->
Line 228: Line 251:
  
 
Take action on and log '''alarms'''
 
Take action on and log '''alarms'''
 +
 +
At '''the end of the shift''', submit the '''strip charts''' to the logbook
 +
* If they are not up already: (CS-Studio &rarr; Tools &rarr; Strip Charts &rarr; livePlot)
 +
* Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"
 +
* Choose a '''time-span width of 10 hours''' (right-click below x-axis)
 +
* <font color=red> To make a logbook entry:</font>
 +
:- Right click within the grid of one of the charts, choose "Make Logbook Entry"
 +
:- The title of the logbook entry can be changed, eg to Strip charts
 +
:- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit
  
 
'''Communicate''' with your co-shift person:
 
'''Communicate''' with your co-shift person:
Line 233: Line 265:
 
* Discuss any issues with the shift worker before making extra logbook entries.
 
* Discuss any issues with the shift worker before making extra logbook entries.
 
* Remind the shift worker of the '''end-of-shift Checklist'''.
 
* Remind the shift worker of the '''end-of-shift Checklist'''.
 +
* <font color=red> Use the CS-Studio '''Logbook entry tool''' for all screen shots (but the strip charts)!</font>
 +
* Note that the Logbook Entry tool puts the entry in the HBRUN logbook by default. Other logbooks can be added or selected from the drop down menu.
  
Check for and read any comments to '''log-book entries''' made during your shift.
+
Check for and read any comments to '''logbook entries''' made during your shift.
  
 
Keep your '''shift summary''' up to date in HBLOG. Record all significant happenings.  
 
Keep your '''shift summary''' up to date in HBLOG. Record all significant happenings.  
Line 240: Line 274:
 
* Include a run list for the shift with relevant run information.
 
* Include a run list for the shift with relevant run information.
  
Ensure that all '''monitoring plots''' are logged and checked against the reference plots for every single run.
+
Ensure that all '''monitoring plots''' and  are logged and checked against the reference plots for every single run.
* Both, you and the shift worker should run MON12 and '''reset & check spectra frequently'''.
+
* Both, you and the shift worker should run mon12 and '''reset & check spectra frequently'''.
  
 
* If the worker shift is remote, maintain communication over Zoom.  
 
* If the worker shift is remote, maintain communication over Zoom.  
Line 247: Line 281:
 
* If you have any other questions or uncertainties about what to do, call the RC.
 
* If you have any other questions or uncertainties about what to do, call the RC.
  
 +
The shift worker (if in person) should log the '''clas12online'' reconstruction plots at the end of a run. Running the program on more than one CH computer has been causing problems.
  
In case of '''RICH alarm''', see tab 'Recent Changes and Current Issues'.
+
In case of '''RICH issues''', check the RICH manual for the current guidance: https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf
  
'''New MVT LV Reboot Procedure''' can be found at tab 'Recent Changes and Current Issues'.
+
'''New MVT LV Reboot Procedure''' can be found at tab 'GENERAL INFORMATION'.
  
 
+
'''[https://ace.jlab.org/btm Fill out BTA]''' hourly;
'''[https://bta.acc.jlab.org Fill out BTA]''' hourly;
 
 
* Accelerator beam time (do not change these values):
 
* Accelerator beam time (do not change these values):
 
** ABU: acceptable beam used  
 
** ABU: acceptable beam used  
Line 266: Line 300:
 
** ''Exception'': ''BANU, due to time spent on beam tuning and BPM checks after beam down, should be counted as ER on our side''.
 
** ''Exception'': ''BANU, due to time spent on beam tuning and BPM checks after beam down, should be counted as ER on our side''.
 
* Enter fields at the "Shift Information" tab.
 
* Enter fields at the "Shift Information" tab.
* You must save at 7:00, 15:00, and 23:00, to send info to MCC. To see the save button, click 'edit all' or 'edit cc hours.' You can check, https://ace.jlab.org/btm/reports/activity-audit, whether you saved successfully. <font color=fuchsia><i> Not sure this is true? </i></font>
+
* You must save at 7:00, 15:00, and 23:00, to send info to MCC. To see the save button, click 'edit all' or 'edit cc hours.'  
 
* Acknowledge the popup error message about the last hour not being completed by clicking OK.
 
* Acknowledge the popup error message about the last hour not being completed by clicking OK.
 
* Sign, viz log completed 8-hour sheet.  
 
* Sign, viz log completed 8-hour sheet.  
* '''Note: we can change the time sheet up to 48 hours after completion.''' <font color=fuchsia><i> Still true? </i></font>
+
* '''Note: we can change the time sheet up to 48 hours after completion.'''  
 
 
  
 
<!--#######################################  Shift Worker ################################################-->
 
<!--#######################################  Shift Worker ################################################-->
Line 279: Line 312:
  
 
Discuss any issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary.
 
Discuss any issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary.
 +
 +
<font color=red> Use the CS-Studio '''Logbook entry tool''' for all screen shots (but the strip charts)! </font>
  
 
=== Frequently ===
 
=== Frequently ===
  
Reset and check MON12 histograms frequently, preferably each 1h
+
Reset and check mon12 histograms frequently, preferably each 1h
 
* Note that some plots have radio buttons at the bottom to choose the sector. Remember to cycle through and check all sectors.
 
* Note that some plots have radio buttons at the bottom to choose the sector. Remember to cycle through and check all sectors.
  
 
=== Once per run ===
 
=== Once per run ===
  
Submit EPICS '''screenshots''' to the HBRUN logbook '''with beam ON'''
+
Note that the CS-Studio '''Logbook Entry tool''' puts the entry in the HBRUN logbook by default. Other logbooks can be added or selected from the drop down menu.  
* Beamline overview, in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser]
 
* CLAS12 trigger rates and DAQ status
 
  
Upload '''MON12''' monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see {{#switchtablink:Monitoring|Monitoring}} tab).
+
Using the Logbook Entry tool, submit EPICS '''screenshots''' to the HBRUN logbook (one logbook entry) '''with beam ON'''
 +
# Beamline overview (remote shift: in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser])
 +
# DAQ status
 +
# CLAS12 trigger rates
  
Submit '''Beam current and position strip charts''' to the logbook at '''the end of the run'''
+
Upload '''mon12''' monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see {{#switchtablink:Monitoring|Monitoring}} tab).
 +
 
 +
At the '''end of the run''', submit the '''strip charts''' to the logbook
 
* If they are not up already: (CS-Studio &rarr; Tools &rarr; Strip Charts &rarr; livePlot)
 
* If they are not up already: (CS-Studio &rarr; Tools &rarr; Strip Charts &rarr; livePlot)
 
* Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"
 
* Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"
* Choose the 'time-span width' to be compatible with the run duration (right-click below x-axis)
+
* Choose a '''time-span width of 4 hours''', compatible with the run duration (right-click below x-axis)
* To make a logbook entry:
+
* <font color=red> To make a logbook entry:</font>
 
:- Right click within the grid of one of the charts, choose "Make Logbook Entry"
 
:- Right click within the grid of one of the charts, choose "Make Logbook Entry"
:- The title of the logbook entry can be changed
+
:- The title of the logbook entry can be changed, eg to Strip charts
 
:- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit
 
:- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit
 +
 +
At the '''end of the run''', upload the '''[https://github.com/JeffersonLab/caos/tree/main#readme clas12online]''' plots to the logbook.
 +
* The program can continue through a standard end/start of a run. However, after a DAQ restart, you must back out and restart clas12online.
 +
* If the DAQ has to be restarted, you can still make the upload before backing out.
  
 
=== Once per shift ===
 
=== Once per shift ===
Line 307: Line 349:
 
* During production, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status and CLAS12 Trigger;
 
* During production, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status and CLAS12 Trigger;
 
* During extended downtime, get relevant values from the latest EPICS screenshots that you made during production  
 
* During extended downtime, get relevant values from the latest EPICS screenshots that you made during production  
 
Upload by the end of the shift while data is being collected '''[https://github.com/JeffersonLab/caos/tree/main#readme clas12online]''' plots to the HBLOG logbook, with sufficient statistics
 
* Please refresh the [https://github.com/JeffersonLab/caos/tree/main#readme clas12online] program at the beginning of your shift in case the previous shift does not do it after uploading the snapshots. Also, do that while the DAQ is running!
 
* Note that the program must also be restarted after each DAQ crash!
 
  
 
== For Remote Shifts ==
 
== For Remote Shifts ==
Line 317: Line 355:
  
 
You must test your setup, including Zoom and VNC connections, at least 24 hours before your first shift!
 
You must test your setup, including Zoom and VNC connections, at least 24 hours before your first shift!
* Zoom for 24-7 communication with counting house:
+
* Zoom for 24-7 communication with Counting House:
 
** In the Zoom app: [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939]
 
** In the Zoom app: [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939]
 
** Or in a web browser: [https://jlab-org.zoomgov.com/wc/1618614939/join?pwd=U003MnRuNVdiU1EzaFpXV0JuNWV1Zz09 https://jlab-org.zoomgov.com/wc/1618614939/join?pwd=U003MnRuNVdiU1EzaFpXV0JuNWV1Zz09]
 
** Or in a web browser: [https://jlab-org.zoomgov.com/wc/1618614939/join?pwd=U003MnRuNVdiU1EzaFpXV0JuNWV1Zz09 https://jlab-org.zoomgov.com/wc/1618614939/join?pwd=U003MnRuNVdiU1EzaFpXV0JuNWV1Zz09]
Line 333: Line 371:
 
= Run Coordinator =
 
= Run Coordinator =
  
Check the upcoming shifts, and if necessary, coordinate with the PDL to contact shift takers about their training and site access status.
+
Check the '''upcoming shifts''', and if necessary, coordinate with the PDL to contact shift takers about their training and site access status.
 +
 
 +
'''Remote shifts''' are listed [[Upcoming-remote-shifts|here]].
  
Remote shifts are listed [[Upcoming-remote-shifts|here]].
+
'''Backup shift personnel''' is listed [https://jeffersonlab-my.sharepoint.com/:x:/r/personal/baltzell_jlab_org/Documents/Backup%20Shifters.xlsx?d=wf18dc5909cf84424840d73cc9bd8ce8e&csf=1&web=1&e=QwY1fs here].
  
Backup shift personnel is listed [https://jeffersonlab-my.sharepoint.com/:x:/r/personal/baltzell_jlab_org/Documents/Backup%20Shifters.xlsx?d=wf18dc5909cf84424840d73cc9bd8ce8e&csf=1&web=1&e=QwY1fs here].
+
'''Meeting ZOOM connections:''' see tab {{#switchtablink:Important Links|Important Links}}
  
 
=== Daily ===
 
=== Daily ===
  
Attend the in-person PD/RC and MCC/OPS meetings (7:45 AM and 8 AM Daily). The PD will communicate when and how meetings happen on the weekend.
+
* '''Report at the PD/RC and attend the MCC/OPS meetings''' (weekdays 7:45 AM and 8 AM Daily, MCC building). The PD will communicate when and how meetings happen on the weekend.
* See the ZOOM connection info under {{#switchtablink:Important_Links|Important Links}} tab.
 
  
Update the run plan in the {{#switchtablink:Short_Term_Schedule|Short Term Schedule}} tab in coordination with the RG-K experiment coordinators (i.e., Annalisa, Daniel) and communicate it to the shift crew.  
+
* Update the run plan in tab '''{{#switchtablink:Short_Term_Schedule|Short Term Schedule}}''' (and on the white board in CH) in coordination with the RG-K experiment coordinators (i.e., Annalisa, Daniel) and communicate it to the shift crew.  
  
Log the RC summary in the HBLOG.  
+
* Log the '''RC Daily summary''' in the HBLOG.  
  
Update the list of runs taken on the [https://docs.google.com/spreadsheets/d/1xplXDIiio_TkimucPBSf7i-bAbbM7mpWzZ1zevt4edQ/edit#gid=0 Google Spreadsheet]
+
* Update the '''list of runs''' taken on the [https://docs.google.com/spreadsheets/d/1xplXDIiio_TkimucPBSf7i-bAbbM7mpWzZ1zevt4edQ/edit#gid=0 Google Spreadsheet]
  
Send a daily invitation for the RC meeting to mailing lists hallb, clas12_rgk, clas_members.
+
* '''[[https://ace.jlab.org/btm/timesheet/eb BTA time sheet]''': Make sure, the "Beam Available Not Used" (BANU) time is accounted for as explained at tab {{#switchtablink:Shift_Expert|Shift Expert}}. The BTA information can be modified post-signature.
 +
** NOTE: "After 48 hours you cannot modify a User signed timesheet unless you are the signer, Hall Manager, or Admin"
  
Run the '''RC meetings''' at 13:00 in CH Room 200C and on ZOOM, except on Wednesdays.
+
* Run the daily '''RC meetings''' in CH Room 200C and on ZOOM
* On Wednesdays, the RC meeting is held on Zoom only at 15:00, due to the conflict with the 13:30 MCC meeting and the unavailability of the CH room afterwards.
+
** Mo-Tu,Th-Fr at 13:00 ET in the Counting House Conference Room
* Keep the '''Daily RC Meeting Minutes''' at [https://clasweb.jlab.org/wiki/index.php/Run_Group_K Run_Group_K wiki], tab "RGK FALL 2023 / SPRING 2024"  
+
** Wednesdays at 3 PM, zoom only
 +
** Weekends upon agreement
 +
** Send a '''daily invitation''' for the RC meeting to mailing lists hallb, clas12_rgk, clas_members.
 +
** Keep the '''Daily RC Meeting Minutes''' at [https://clasweb.jlab.org/wiki/index.php/Run_Group_K Run_Group_K wiki], tab "RGK FALL 2023 / SPRING 2024"  
  
Connect to Zoom in CH Room 200C:
+
* Connect to '''Zoom in CH Room 200C''':
* Turn on the projector with the white remote control, then log into your CUE account. If not listed yet, click "Not listed?" in the bottom left to add your account.  
+
** Turn on the projector with the white remote control, then log into your CUE account. If not listed yet, click "Not listed?" in the bottom left to add your account.  
* Once logged in, use the recommended Google Chrome to join the ZOOM meeting on the browser or use the ZOOM application.  
+
** Once logged in, use the recommended Google Chrome to join the ZOOM meeting on the browser or use the ZOOM application.  
* Since the room doesn't have audio, don't connect with the computer audio, but choose "Call Me," then enter the number in the small Cisco answering device. Once it rings, answer the call, and you will be prompted to join the meeting.  
+
** Since the room doesn't have audio, don't connect with the computer audio, but choose "Call Me," then enter the number in the small Cisco answering device. Once it rings, answer the call, and you will be prompted to join the meeting.  
* The room has a camera, which can be turned on via ZOOM.  
+
** The room has a camera, which can be turned on via ZOOM.  
  
 
=== Weekly ===
 
=== Weekly ===
  
'''MCC/OPS planning meeting''' is in person, on Wednesdays at 13:30, MCC building.
+
*'''MCC/OPS planning meeting''', on Wednesdays at 13:30, MCC building.
* Submit (save) the online form [https://ace.jlab.org/apps/pd/run-coordinator-reports Run Coordinator Weekly Summary] before the meeting and present the contents at the meeting.
+
** Submit (save) the online form '''[https://ace.jlab.org/apps/pd/run-coordinator-reports Run Coordinator Weekly Summary]''' before the meeting and present the contents at the meeting.
* The summary covers the data taking status from 7 am on the previous Wednesday to 7 am on the current Wednesday.
+
** The summary covers the data taking status '''from 7 am on the previous Wednesday to 7 am on the current Wednesday'''.
* The beam time accounting can be retrieved from:
+
** '''Beam time accounting''': [https://ace.jlab.org/btm/reports/physics-summary Beam Time Manager; Physics Time Accounting]
** OPS logbook entries with tag 'Beam Accounting': [https://logbooks.jlab.org/tag/beamaccounting Timesheet Summaries]
+
** For the '''percentage of scheduled experiment hours to date''' contact Daniel Carman.
** [https://ace.jlab.org/btm/reports/physics-summary Beam Time Manager; Physics Time Accounting]
+
** The '''total experiment data collected to date''' can be retrieved from the up-to-date "Accumulated Charge" depicted at [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html]
** To calculate the percentage of scheduled experiment hours to date contact Daniel Carman.
 
** The total experiment data collected to date could be retrieved from the up-to-date "Accumulated Charge" depicted at [https://clasweb.jlab.org/clas12online/timelines/rg-k/RGK2024_progress_all.html]
 
  
'''Hall B meeting''' is on Mondays at 9 AM. Present your summary slides that should be sent beforehand to the Hall B leader, Patrick Achenbach.  
+
*'''Hall B meeting''' is on Mondays at 9 AM. Present your summary slides that should be sent beforehand to the Hall B leader, Patrick Achenbach.  
  
  
<!--####################################### MONITORING ################################################-->
+
<!--####################################### MONITORING ################################################-->
 
= Monitoring =
 
= Monitoring =
  
Line 397: Line 438:
 
| valign=top |
 
| valign=top |
 
=== Data Quality ===
 
=== Data Quality ===
* Mon12 histograms: reference and most recent uploads [https://clas12mon.jlab.org/mon12/histograms/?reference=4241301 run 19407]
+
* mon12 histograms: [https://clas12mon.jlab.org/mon12/histograms/?reference=4263114 reference (run 19868)]
 
* [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox!
 
* [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox!
 
* [https://github.com/JeffersonLab/caos/tree/main#readme clas12mltrack/clas12online]:  
 
* [https://github.com/JeffersonLab/caos/tree/main#readme clas12mltrack/clas12online]:  
Line 420: Line 461:
 
* [https://accweb.acc.jlab.org/apps/pd/shift-plans Program Deputy Shift Plans]
 
* [https://accweb.acc.jlab.org/apps/pd/shift-plans Program Deputy Shift Plans]
 
* [https://cebaf.jlab.org/pd/run-coordinator-reports Run Coordinator Reports]
 
* [https://cebaf.jlab.org/pd/run-coordinator-reports Run Coordinator Reports]
* [https://accweb.acc.jlab.org/btm/reports/physics-summary Beam Time Accounting Reports]
+
* [https://ace.jlab.org/btm/reports/physics-summary Beam Time Accounting Reports]
* [http://opsweb.acc.jlab.org/CSUEApps/PSSestamp/psslog.php PSS Elog]
+
* [https://opsweb.acc.jlab.org/CSUEApps/PSSestamp/psslog.php?numdays=5&entry_types_wanted%5BACCESS%5D=ACCESS&group_by=AREA&output_format=SCROLLABLE PSS Elog]
 
* [http://opsweb.acc.jlab.org/internal/ops/ops_webpage/restrictions/ops_restrictions.html Operational Restrictions]
 
* [http://opsweb.acc.jlab.org/internal/ops/ops_webpage/restrictions/ops_restrictions.html Operational Restrictions]
  

Latest revision as of 13:50, 25 July 2024

[edit]


Clas12design.png