Difference between revisions of "Run Group E"

From clas12-run
Jump to navigation Jump to search
(2 intermediate revisions by the same user not shown)
Line 84: Line 84:
  
 
=== 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. This gets done upon request of DAQ or MVT expert only.
+
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 experts 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 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.  
+
* 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 minutes after LV is turned back ON.  
 
* Reboot mvt1, mvt2, and mvt3 ROCS.  
 
* Reboot mvt1, mvt2, and mvt3 ROCS.  
 
* Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).  
 
* Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).  
−
* '''If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert'''.  
+
* '''If we have a beam and a reboot process takes more than 5 minutes, call the DAQ or MVT expert'''.
  
 
=== RICH issues ===
 
=== RICH issues ===
−
* The RICH fibers alarm leads to web guidance aka logbook entry [https://logbooks.jlab.org/entry/3562273 3562273 - RICH recovery procedure].  
+
* The RICH fibers alarm leads to web guidance, aka logbook entry [https://logbooks.jlab.org/entry/3562273 3562273 - RICH recovery procedure].  
 
* Check the RICH manual for the current guidance: '''https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf'''
 
* Check the RICH manual for the current guidance: '''https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf'''
 
* See below for current issues
 
* See below for current issues
Line 99: Line 99:
 
=== Rapid/Controlled Access to the Hall ===
 
=== Rapid/Controlled Access to the Hall ===
 
* Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.
 
* Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.
−
* After higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.
+
* After a higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.
  
 
=== 24/7 ZOOM connection for Counting House ===
 
=== 24/7 ZOOM connection for Counting House ===
−
* Click on [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939], included in "Remote Shifts" in tab  "Shift Worker"  
+
* Click on [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939], which is included in "Remote Shifts" in the "{{#switchtablink:Shift_Worker|Shift Worker}}" tab.
−
* 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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab.
  
 
== '''Current Issues''' ==  
 
== '''Current Issues''' ==  
  
 
=== Lights in the Hall ===
 
=== Lights in the Hall ===
−
The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the detectors. If these lights are switched on during an access, they '''should be switched off when leaving the Hall'''.  
+
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the detectors. If these lights are switched on during an access, they '''should be switched off when leaving the Hall'''.  
 
* Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]
 
* Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]
 
* We have a '''new dome light switch outside of the hall''' in the labyrinth.  See logbook entry: https://logbooks.jlab.org/entry/4204460
 
* We have a '''new dome light switch outside of the hall''' in the labyrinth.  See logbook entry: https://logbooks.jlab.org/entry/4204460
Line 116: Line 116:
 
=== Beamline ===
 
=== Beamline ===
  
−
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running").  
+
* Orbit locks are on BPMs '''2C24A and 2H01''', and the locks should generally be on ("Running").  
−
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
+
:- Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
 
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.
 
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.
 
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).
 
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).
 
*'''After the HWP change'''  
 
*'''After the HWP change'''  
−
** The absolute values of the SLM and FCUP '''charge asymmetry''' (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.
+
:- The absolute values of the SLM and FCUP '''charge asymmetry''' (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.
 
** Start a new run
 
** Start a new run
 
* '''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.
Line 135: Line 135:
 
=== CND ===
 
=== CND ===
 
* CAMAC crate alarm:  
 
* CAMAC crate alarm:  
−
** CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, can be done via the alarm handler.  
+
:- CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, which 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
+
:- 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:
 
* roc reboot instructions:
−
** To reboot i.e. adcecal1, type on a clasrun terminal: clasrun> roc_reboot adcecal1
+
:- 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
+
:- 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.  
+
:- The ping will start to answer as soon as the crate communicates again.  
  
 
=== DC ===
 
=== DC ===
Line 150: Line 150:
  
 
=== ECAL/PCAL ===
 
=== ECAL/PCAL ===
−
* "ECAL_SEC6_UO26 Noisy" https://logbooks.jlab.org/entry/4241957
+
* "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
 
* "PCAL_HV_SEC2_U25 turned off" https://logbooks.jlab.org/entry/4247187, https://logbooks.jlab.org/entry/4247400
  
Line 159: Line 159:
 
=== RICH ===
 
=== RICH ===
 
* '''Known problematic PMTs and tile''':
 
* '''Known problematic PMTs and tile''':
−
** You don't need to report about it.
+
:- 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.
+
:- PMT 2 (sector 1) and PMT 92 (sector 4) are not completely dead and may be visible depending on statistics.
−
** Problematic tiles and PMTs:
+
:- Problematic tiles and PMTs:
−
*** Sector 1 Tile 21 dead (PMT 55,56,57)
+
::&bull; Sector 1 Tile 21 dead (PMT 55,56,57)
−
*** Sector 1 Tile 1 PMT 2
+
::&bull; Sector 1 Tile 1 PMT 2
−
*** Sector 4 Tile 34 PMT 92
+
::&bull; Sector 4 Tile 34 PMT 92
  
 
== '''Beam Restoration''' ==  
 
== '''Beam Restoration''' ==  
Line 170: Line 170:
 
* 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 doing this alone, 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 doing this alone, contact the Beamline Expert.
  
−
* Find all Reference values on the CH whiteboard as well as the Short_Term_Schedule tab.
+
* Find all Reference values on the CH whiteboard as well as the {{#switchtablink:Short_Term_Schedule|Short Term Schedule}} tab.
  
 
=== Restoring Beam after Short Downtime ===
 
=== Restoring Beam after Short Downtime ===
  
 
* Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after   
 
* Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after   
−
** 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
+
:- If BPM 2C24A and 2H01 positions are off (not within +/-0.1 mm), ask MCC to bring them to the reference values
  
 
=== Beam Tuning to Tagger Yoke Dump ===
 
=== 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].  
+
* 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.
 
* Contact Eugene Pasyuk if issues arise.
  
Line 193: Line 193:
 
* Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
 
* Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
 
* If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values
 
* If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values
−
* Take harp scans
+
* Take harp scans:
 
:- at Harp 2C21A (Upstream Right Counter)
 
:- at Harp 2C21A (Upstream Right Counter)
 
:- at Tagger Harp 2C24A Upstream Right Counter)
 
:- at Tagger Harp 2C24A Upstream Right Counter)
Line 204: Line 204:
 
=== 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
 
* 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%
  
 
=== 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.  
+
* Study the manual [https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam] and consider the first steps mentioned therein.  
  
−
This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
+
* 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)
 
* All CLAS12 detectors HV off (BMT HV in safe mode)
Line 224: Line 224:
 
:- beam type electron
 
:- beam type electron
 
:- beam blocker out
 
:- beam blocker out
−
* If initial beam tune, target should be "Empty"
+
* If initial beam tune, the target should be "Empty"
 
* 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
Line 235: Line 235:
 
* 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  ################################################-->
 
= Shift Expert =
 
= Shift Expert =
  
−
Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift.  
+
* Arrive at your shift in time for the '''shift change''', 10-15 minutes before the start of your shift.  
−
* If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.
+
:- If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.
  
−
Follow the '''Short Term Schedule'''
+
* Follow the '''{{#switchtablink:Short_Term_Schedule|Short Term Schedule}}''';
−
* The RC must be notified before changing run conditions
+
:- The RC must be notified before changing run conditions.
  
−
Operate the '''Data Acquisition'''
+
* Operate the '''Data Acquisition'''.
  
−
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
+
* '''Communicate''' with your co-shift person:
−
* If they are not up already: (CS-Studio &rarr; Tools &rarr; Strip Charts &rarr; livePlot)
+
:- Remind them to read the tab 'Shift Worker'.
−
* Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"
+
:- The shift worker should discuss an issue with the shift expert before making extra logbook entries.
−
* Choose a '''time-span width of 10 hours''' (right-click below x-axis)
+
:- During production, not in extended downtime, the shift expert should ensure the shift worker is filling their '''end-of-shift Checklist''' when the beam is ON, not in the period of beam trips.
−
* <font color=red> To make a logbook entry:</font>
+
:- <font color=red> Use the CS-Studio '''Logbook entry tool''' for all screenshots (but the strip charts)!</font>
−
:- Right click within the grid of one of the charts, choose "Make Logbook Entry"
+
:- Note that the Logbook Entry tool defaults the entry in the HBRUN logbook. Other logbooks can be added or selected from the drop-down menu.  
−
:- 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:
 
−
* Remind them to read the tab 'Shift Worker'.
 
−
* Discuss any issues with the shift worker before making extra logbook entries.
 
−
* 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 '''logbook entries''' made during your shift.
+
* Check for and read any comments made to '''log-book entries''' 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 shift activities, issues, if any, and related communications with experts with details and/or reference to any associated logbook entries: 
−
* Refer to relevant logbook entries in the shift summary.
+
:- Refer to relevant logbook entries in the shift summary.
−
* Include a run list for the shift with relevant run information.
+
:- Include a list of runs taken during the shift with relevant run information;
 +
::- See, for instance, this [https://logbooks.jlab.org/entry/4214804 shift summary] where all relevant run info, links, and shift activities are cited.
  
−
Ensure that all '''monitoring plots''' and  are logged and checked against the reference plots for every single run.
+
* Ensure that all '''MON12 monitoring plots''' are logged and checked against the reference plots for every single run; see the links under {{#switchtablink:Monitoring|Monitoring}} tab;
−
* 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 283: Line 275:
 
* 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 issues''', check the RICH manual for the current guidance: https://github.com/JeffersonLab/clas12-manuals/blob/master/rich/Novice/RICH_Controls.pdf
  
−
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 in the {{#switchtablink:General_Information|General_Information}} tab.
  
−
'''New MVT LV Reboot Procedure''' can be found at tab 'GENERAL INFORMATION'.
+
* 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>
 +
::&bull; Right-click within the grid of one of the charts, choose "Make Logbook Entry"
 +
::&bull; The title of the logbook entry can be changed, eg to Strip charts
 +
::&bull; Un-click ELOG, select HBLOG and click "Make Entry" to submit.
  
−
'''[https://ace.jlab.org/btm Fill out BTA]''' hourly;
+
* '''[https://ace.jlab.org/btm 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  
−
** BANU: beam acceptable but not used (should be reflected in our PCC and UED)
+
:- BANU: beam acceptable but not used (should be reflected in our PCC and UED)
−
** BNA: beam not acceptable (e.g., tuning, drifting, not focused)
+
:- BNA: beam not acceptable (e.g., tuning, drifting, not focused)
−
** ACC: Accelerator Configuration Change (e.g., pass change)
+
:- ACC: Accelerator Configuration Change (e.g., pass change)
−
** OFF: Accelerator is down
+
:- OFF: Accelerator is down
 
* Experiment beam time (do change these values):
 
* Experiment beam time (do change these values):
−
** ER: Experiment ready (should be 60 minutes - PCC - UED)
+
:- ER: Experiment ready (should be 60 minutes - PCC - UED)
−
** PCC: Planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, etc.)
+
:- PCC: Planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, etc.)
−
** UED: Unplanned experiment down (hardware failure, DAQ crashes, our problems, ...)
+
:- UED: Unplanned experiment down (hardware failure, DAQ crashes, our problems, ...)
−
** ''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.'  
+
* To send information to MCC, you must save at 7:00, 15:00, and 23:00. 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.'''  
 
* '''Note: we can change the time sheet up to 48 hours after completion.'''  
 +
  
 
<!--#######################################  Shift Worker ################################################-->
 
<!--#######################################  Shift Worker ################################################-->
Line 391: Line 391:
 
* 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]
  
−
* '''[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.
+
* '''[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"
+
** NOTE: "After 48 hours, you cannot modify a User signed timesheet unless you are the signer, Hall Manager, or Admin".
  
 
* Run the daily '''RC meetings''' in CH Room 200C and on ZOOM
 
* Run the daily '''RC meetings''' in CH Room 200C and on ZOOM
Line 410: Line 410:
 
*'''MCC/OPS planning meeting''', 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 a.m. on the previous Wednesday to 7 a.m. on the current Wednesday'''.
 
** '''Beam time accounting''': [https://ace.jlab.org/btm/reports/physics-summary Beam Time Manager; Physics Time Accounting]
 
** '''Beam time accounting''': [https://ace.jlab.org/btm/reports/physics-summary Beam Time Manager; Physics Time Accounting]
 
** The '''total experiment data collected to date''' could be retrieved from the up-to-date "Accumulated Charge" depicted on the "RGE 2024 Progress" plot. See the {{#switchtablink:Monitoring|Monitoring}} tab
 
** The '''total experiment data collected to date''' could be retrieved from the up-to-date "Accumulated Charge" depicted on the "RGE 2024 Progress" plot. See the {{#switchtablink:Monitoring|Monitoring}} tab
−
*'''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, which should be sent beforehand to the Hall B leader, Patrick Achenbach.  
  
  
Line 442: Line 442:
 
* [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]: real-time reconstructed vertices & various event topologies
 
* [https://github.com/JeffersonLab/caos/tree/main#readme clas12mltrack]: real-time reconstructed vertices & various event topologies
−
* [https://clasweb.jlab.org/clas12online/timelines/rg-e/RGE2024_progress_all_charge.html] Data CHARGE accumulation timeline [https://clasweb.jlab.org/clas12online/timelines/rg-e/RGE2024_progress_all_lumi.html] LUMINOSITY accumulation timeline
+
* [https://clasweb.jlab.org/clas12online/timelines/rg-e/RGE2024_progress_all_charge.html] Data CHARGE accumulation timeline [https://clasweb.jlab.org/clas12online/timelines/rg-e/RGE2024_progress_all_lumi_unzoom.html] LUMINOSITY accumulation timeline
 +
<!--https://clasweb.jlab.org/clas12online/timelines/rg-e/RGE2024_progress_all_lumi.html] -->
 
|}
 
|}
  

Revision as of 19:23, 9 May 2024

[edit]
Role Phone Number
Hall B Run Coordinator (757) 575-7540 (cell)
Hall B Physics Division Liaison (757) 876-1789 (cell)
MCC 7048
Crew Chief 7045
Crew Chief (757) 876-3367 (cell)
Program Deputy (757) 876-7997 (cell)
RadCon (757) 876-1743 (cell)
Gate House Guard 5822
Location Phone Number
Hall B Floor 5165
Hall B Space Frame 5170 and 5171
Hall B Forward Carriage 5371
Hall B Gas Shed 7115
Hall B Counting House 5244 (Shift Expert)
Hall B Counting House (757) 329-4846 (Shift Expert cell)
Hall B Counting House 5245 or 5126 (Shift Worker)
Hall A Counting House 5501
Hall C Counting House 6000
Hall D Counting House 5504
Hall B System Phone Number On-Call Person
Engineering (757) 748-5048 (cell)
(757) 897-9060 (cell)		 Engineering On-Call (primary)
Denny Insley (secondary)
Slow Controls (757) 748-6922 (cell) Nathan Baltzell
Beamline (757) 303-3996 (cell) Eugene Pasyuk
DC (757) 218-4372 (cell)
(757) 748-5048 (cell)		 Florian Hauenstein (primary)
Engineering On-Call (secondary)
SVT/MVT/MM (757) 541-7539 (cell)
(757) 753-7769 (cell)		 Yuri Gotra (primary)
Rafo Paremuzyan (secondary)
ECAL (757) 810-1489 (cell) Cole Smith
FTOF/CTOF/CND (757) 344-7204 (cell) Daniel Carman
ALERT (757) 329-4844 (cell) Raphael Dupré
HTCC/LTCC (757) 344-7174 (cell) Youri Sharabian
FT (757) 344-1848 (cell) Raffaella De Vita
BAND (757) 310-7198 (cell) Florian Hauenstein
RICH (757) 344-3235 (cell)
(757) 748-6922 (cell)		 Christopher Dilks (primary)
Nathan Baltzell (secondary)
DAQ (757) 232-6221 (cell) Sergey Boiarinov
HYDRA (317) 550-9226 (cell) Torri Jeske
Authorized Hall B Solenoid/Torus Operators
Hall B Denny Insley, Morgan Cook, Eugene Pasyuk
Magnet Group Probir Ghosha, Renuka Rajput-Ghoshal
Detector Support Group Brian Eng, Pablo Campero, Tyler Lemon
DC Power Onish Kumar, Sarin Philip
  • Note, all non-JLab numbers must be dialed with an area code. When calling from a counting-house landline, dial "9" first.
  • To call JLab phones from outside the lab, all 4-digit numbers must be preceded by 757-269
  • Click Here to edit Phone Numbers. Note, you then also have to edit the current page to force a refresh.

Run Coordinator: Sebouh Paul (757) 575-7540

Current RP Coordinator: Lamiaa El Fassi

PDL: Nathan Baltzell (757) 876-1789, Office: x5902

Daily RC Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1605705819), except on Wednesdays, which is @ 15:00 in CH Room 200C and via the same ZOOM link.

Important Notes

  • In case of medical or fire emergency, call 911 or 9-911 from a LANDLINE phone in the Counting House and inform the Crew Chief and RC.
  • In case of evacuation of the Counting Room (e.g., due to a fire alarm), grab the shift expert phone and leave the room through the "EXIT" door leading to the parking lot. Do not leave through the hallway! Call the RC once outside so the latter can call MCC to turn the beam OFF for Hall B and inform other Hall B staff members.
  • If you have symptoms or a positive COVID test, do NOT come to your shift. Instead, inform the PDL, the RC, and JLab medical services immediately to arrange replacements.
  • In case of a problem with the HV Slow Controls, EPICS in general, please call the primary expert on-call, Nathan Baltzell, before reaching out to anyone else.
  • Please put all essential information on the main Hall B logbook HBLOG. Some important alarms have been documented on HBRUN. Use the pulldown menu to choose where an error is reported.

Current Run Plan: May 18th to May 19th

  • Take production data! Don't break anything!
  • Keep an eye on the backgrounds, such as in the halo counters and the 2C24A and 2H01 BPM positions. Both give confidence that the beam remains centered on the RG-E target.
  • If you need to manipulate the whole target system - cryo-target or solid - please contact the target experts.

Outbending Configuration Runs

• Beam Blocker: IN
• Beam Current: 70 nA
• Target: LD2+Pb
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_noDC_v1.0_300MeV.trg
• 3-hour or 100 M events run, whatever comes first!


Previous Dual-target Configuration Plans

- DC firmware test plan (LD2+Pb):

1) Take one run each with 1M events with the trigger files and beam current at 70 nA

  • rge_inb_v1.0_200MeV_dcrb17_1.trg : DCRB Threshold (30, 45, 45 nA)
  • rge_inb_v1.0_200MeV_dcrb17_4.trg : DCRB Threshold (30, 60, 45 nA)
  • rge_inb_v1.0_200MeV_dcrb17_3.trg : DCRB Threshold (45, 60, 60 nA)
  • rge_inb_v1.0_200MeV_dcrb17_2.trg : DCRB Threshold (30, 30, 30 nA)

2) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_2.trg

3) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_4.trg

• Before the last run, call DC expert Florian so that he can change the firmware after the last run is finished.

*** Notes ***

• In every step, follow DAQ procedure (End run, Cancel, Reset, Configure, Download, Prestart, Go)
• For every run please log clas12mon plots from the special version at /usr/clas12/offline/clas12mon/dcrb/bin/mon12

LD2+Pb runs

  • Trigger: rge_inb_v1.0_200MeV.trg
  • Beam Current: 70 nA
  • Use PROD67 configuration (this will not PIN data)
  • 3-hour runs

LD2+Sn runs

  • Trigger: rge_inb_v1.0_200MeV.trg
  • Beam Current: 65 nA
  • Use PROD67 configuration (this will not PIN data)
  • 3-hour runs

LD2+Al runs

• Beam Blocker: IN
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Beam Current: 70 nA
• 3-hour runs

Lumi Scan for LD2+Al on May 15th

• Beam Blocker: OUT
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Take one 5 nA run for 4 hours w/. beam ON
• Take one 10 nA run for 6 hours w/. beam ON
• Take one 20 nA run for 3 hours w/. beam ON
• Take one 45 nA run for 3 hours w/. beam ON

Lumi Scan for LD2+Pb on May 15th - 16th

• Beam Blocker: OUT
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Take one 5 nA run for 4 hours w/. beam ON
• Take one 10 nA run for 3 hours w/. beam ON
• Take one 20 nA run for 3 hours w/. beam ON
• Take one 40 nA run for 3 hours w/. beam ON
• Take one 55 nA run for 3 hours w/. beam ON

Streaming Readout Test

• Performed in coordination with Sergey and David Lawrence (Done from 9 to 11 a.m. on May 16th).

Empty-target runs on May 16th - 17th

• Beam Blocker: IN
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Take one Empty+Al run @ 70 nA w/. BB for 5 hours (w/. Beam ON)
• Take one Empty+Wire run @ 200 nA w/. BB for approx. 8 hours (BB calibration is done by Rafo and Lamiaa/MCC OPS over phone)

Outbending Configuration Runs on May 17th - 19th =

• Beam Blocker: IN
• Beam Current: 70 nA
• Target: LD2+C
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_noDC_v1.0_300MeV.trg, or
♦ Trigger: rge_noDC_v1.0_200MeV.trg, and Beam Current: 60 nA or
♦ Trigger: rge_noDC_v1.0_250MeV.trg, and Beam Current: 65 nA
• 3-hour or 100 M events run, whatever comes first!

References

- BPM Positions

  • The most important BPMs to monitor are 2C24A and 2H01, from the point of view of assuring the beam remains centered on the RG-E target. Other steering/focusing beamline elements can influence the values of the others.
BPM 2C21A 2C24A 2H01
X (mm) -0.4 -1.7 -1.0
Y (mm) +0.7 +0.5 +0.25

- Harp Scans

- FSD Thresholds

  • Do NOT change FSD settings without approval from RC or beamline expert!
• Upstream: 2 kHz
• Midstream: 3 kHz
• Downstream: 150 kHz
• BOM: 50 kHz
• 5 ms dwell time

- Charge Asymmetry

- Upstream Halo counters

  • If the reading on the upstream halo counters exceeds 10, please contact MCC.

General Reminders

  • The main lights in the Hall and the Forward Carriage lights must be kept off during data taking.
• Refer to these reference photos, ON and OFF
• The main, dome lights can be turned off without entering the Hall.
  • Beamline
• Do not run over 30 minutes above 90 nA (50 nA for now while studying FCup behavior) with a 5-pass beam without the beam blocker IN.
• If there is any concern about beam stability, ask MCC if orbit locks are on (they should be).
• Document any beam condition change and send scaler GUIs to HBLOG.
• If HWP is changed, start a new run.
  • During beam tuning and Møller runs
• DC: HV OFF
• SVT: LV ON, HV OFF
• MVT: LV ON, HV ON in SAFE Mode
• All CLAS12 detectors should be OFF; aforementioned tracking detectors are the most critical.
  • To access the Hall
• If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator.
• Check in with the shift personnel before entering the hall.

DAQ Operation

  • Standard end and start of a run
    1. End run
    2. Abort
    3. Download
    4. Prestart
    5. "Go"
  • Restart DAQ from scratch
• E.g., when changing configuration or trigger files, when the run did not end correctly, or after ROCs are rebooted
  1. Cancel
  2. Reset
  3. Configure
  4. Download
  5. Prestart
  6. Go
  • DAQ instructions
• Please make a log entry (logbook RICH, notify vpk@jlab.org) with RICH temp and scalers screenshots when you have RICH problems.
• You do not need to stop the run each time you get 1-2 dead tiles if DAQ is still working. Continue data taking. When you start a new run, the dead tiles will recover without your intervention during DAQ Prestart with a high probability. If you still have problems, make a full RICH recovery and call Valery #5647.

This tab contains information on

  • Recent Changes
  • Current Issues
  • Beam Restoration

Recent Changes

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. This gets done upon request of DAQ or MVT experts only.

  • 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.
  • 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 minutes after LV is turned back ON.
  • Reboot mvt1, mvt2, and mvt3 ROCS.
  • Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
  • If we have a beam and a reboot process takes more than 5 minutes, call the DAQ or MVT expert.

RICH issues

Rapid/Controlled Access to the Hall

  • Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.
  • After a higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.

24/7 ZOOM connection for Counting House

Current Issues

Lights in the Hall

  • The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall.
  • Refer to these photos: ON: [1], OFF: [2]
  • We have a new dome light switch outside of the hall in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460
  • When the dome lights are switched off, they cannot be turned back on immediately, they require 10-15 min to cool down.

Beamline

  • Orbit locks are on BPMs 2C24A and 2H01, and the locks should generally be on ("Running").
- Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
  • The beam position at 2C21A is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.
    • The beam position at 2C21A is important for initial beam tuning (on tagger dump).
  • After the HWP change
- The absolute values of the SLM and FCUP charge asymmetry (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.
    • Start a new run
  • 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

  • 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 information in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.
  • 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
  • If FMT gas errors appear, please follow the instructions in [3]

CND

  • CAMAC crate alarm:
- CAMAC crate (CND Constant Fraction Discriminators) needs rebooting, which 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

  • Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # 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!
  • NEW STANDARD end and start of the run: End run, Cancel, Reset, Download , 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

  • Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.

ECAL/PCAL

FTOF

RICH

  • 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

Restoring Beam after Short Downtime

  • Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after
- beam steering or orbit 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

Beam Tuning to Tagger Yoke Dump

  • Ask MCC to energize the tagger magnet
- blank collimator
- beam type "Photon"
  • All CLAS12 detectors HV off (BMT HV in safe mode)
  • Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM)
  • Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
  • If necessary, ask MCC to bring the 2C21A and 2C24A beam positions to the Reference Values
  • Take harp scans:
- at Harp 2C21A (Upstream Right Counter)
- at Tagger Harp 2C24A Upstream Right Counter)
  • 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.
  • Compare the results with the Harp Scan References
  • The fit ranges might need to be adjusted manually to assess the fit results
  • If good, log the new scan results.

Møller run

  • Follow the standard procedure as described in the manual Performing Møller Runs.
  • Contact Nathan Baltzell if issues arise
  • A few points to note:
- Request 20 nA , Orbit Locks should be off
- The BPMs 2C21 and 2C24A may be out of range after the Møller configuration.
- Keep running until the polarization uncertainty is < 1.5%

Beam Tuning to Faraday Cup

  • 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)
  • Ask MCC to de-energize the tagger magnet
- 20 mm collimator
- beam type electron
- beam blocker out
  • If initial beam tune, the target should be "Empty"
  • Ask MCC to unmask beam halos
  • 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
  • Ask MCC for 5 nA beam current
  • If necessary, ask MCC to bring the beam positions at 2C24A and 2H01 to the Reference Values
  • Take a harp scan at 2H01 (Midstream Left)
  • 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
  • If good, log the new scan results.
  • Once done and before resuming the production data-taking:
- Retract the Downstream Viewer from the beamline
- Put the FSDs thresholds and integration time to their reference values
- 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.
  • Arrive at your shift in time for the shift change, 10-15 minutes before the start of your shift.
- If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.
- The RC must be notified before changing run conditions.
  • Operate the Data Acquisition.
  • Take action on and log alarms.
  • Communicate with your co-shift person:
- Remind them to read the tab 'Shift Worker'.
- The shift worker should discuss an issue with the shift expert before making extra logbook entries.
- During production, not in extended downtime, the shift expert should ensure the shift worker is filling their end-of-shift Checklist when the beam is ON, not in the period of beam trips.
- Use the CS-Studio Logbook entry tool for all screenshots (but the strip charts)!
- Note that the Logbook Entry tool defaults the entry in the HBRUN logbook. Other logbooks can be added or selected from the drop-down menu.
  • Check for and read any comments made to log-book entries during your shift.
  • Keep your shift summary up to date in HBLOG. Record all shift activities, issues, if any, and related communications with experts with details and/or reference to any associated logbook entries:
- Refer to relevant logbook entries in the shift summary.
- Include a list of runs taken during the shift with relevant run information;
- See, for instance, this shift summary where all relevant run info, links, and shift activities are cited.
  • Ensure that all MON12 monitoring plots are logged and checked against the reference plots for every single run; see the links under Monitoring tab;
- 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 you have any other questions or uncertainties about what to do, call the RC.
  • At the end of the shift, submit the strip charts to the logbook:
- If they are not up already: (CS-Studio → Tools → Strip Charts → 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)
- To make a 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, eg to Strip charts
• Un-click ELOG, select HBLOG and click "Make Entry" to submit.
  • Fill out BTA hourly;
  • Accelerator beam time (do not change these values):
- ABU: acceptable beam used
- BANU: beam acceptable but not used (should be reflected in our PCC and UED)
- BNA: beam not acceptable (e.g., tuning, drifting, not focused)
- ACC: Accelerator Configuration Change (e.g., pass change)
- OFF: Accelerator is down
  • Experiment beam time (do change these values):
- ER: Experiment ready (should be 60 minutes - PCC - UED)
- PCC: Planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, etc.)
- UED: Unplanned experiment down (hardware failure, DAQ crashes, our problems, ...)
- 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.
  • To send information to MCC, you must save at 7:00, 15:00, and 23:00. 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.
  • Sign, viz log completed 8-hour sheet.
  • Note: we can change the time sheet up to 48 hours after completion.


Come to your shift in time for the shift change, 10-15 minutes before the start of your shift;

  • If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.

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.

Use the CS-Studio Logbook entry tool for all screen shots (but the strip charts)!

Frequently

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.

Once per run

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.

Using the Logbook Entry tool, submit EPICS screenshots to the HBRUN logbook (one logbook entry) with beam ON

  1. Beamline overview (remote shift: in VNC or Web Browser)
  2. DAQ status
  3. CLAS12 trigger rates

Upload mon12 monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see Monitoring tab).

At the end of the run, submit the strip charts to the logbook

  • If they are not up already: (CS-Studio → Tools → Strip Charts → livePlot)
  • Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"
  • Choose a time-span width of 4 hours, compatible with the run duration (right-click below x-axis)
  • To make a 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, eg to Strip charts
- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit

At the end of the run, upload the 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

Fill the shift checklist;

  • 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

For Remote Shifts

Please inform the PDL that your shifts will be remote. Remote shifts are listed here

You must test your setup, including Zoom and VNC connections, at least 24 hours before your first shift!


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 here.

Backup shift personnel is listed here.

Meeting ZOOM connections: see tab Important Links

Daily

  • 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.
  • Update the run plan in tab 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 Daily summary in the HBLOG.
  • BTA time sheet: Make sure the "Beam Available Not Used" (BANU) time is accounted for as explained at tab 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 daily RC meetings in CH Room 200C and on ZOOM
    • Mo-Tu,Th-Fr at 13:00 ET in the Counting House Conference Room
    • Wednesdays at 3 PM, zoom only
    • Weekends upon agreement
    • Send a daily invitation for the RC meeting to mailing lists hallb, clas12_rge, clas_members.
  • 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.
    • 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.
    • The room has a camera, which can be turned on via ZOOM.

Weekly

  • MCC/OPS planning meeting, on Wednesdays at 13:30, MCC building.
    • Submit (save) the online form Run Coordinator Weekly Summary before the meeting and present the contents at the meeting.
    • The summary covers the data-taking status from 7 a.m. on the previous Wednesday to 7 a.m. on the current Wednesday.
    • Beam time accounting: Beam Time Manager; Physics Time Accounting
    • The total experiment data collected to date could be retrieved from the up-to-date "Accumulated Charge" depicted on the "RGE 2024 Progress" plot. See the Monitoring tab
  • Hall B meeting is on Mondays at 9 AM. Present your summary slides, which should be sent beforehand to the Hall B leader, Patrick Achenbach.


Webcams

EPICS

• Accelerator Status
• Strip Charts

Data Quality

  • MON12 histograms: reference and most recent uploads
• New: LD2+Al dual-target @ 70 nA: run #: 20438
• Old: LD2+Sn dual-target @ 65 nA: run #: 20367
  • Hydra (CUE Login) Google-Chrome ONLY, Not Firefox!
  • clas12mltrack: real-time reconstructed vertices & various event topologies
  • [4] Data CHARGE accumulation timeline [5] LUMINOSITY accumulation timeline


Clas12design.png









Retrieved from "https://wiki.jlab.org/clas12-run/index.php?title=Run_Group_E&oldid=7672"