Difference between revisions of "Run Group D"

From clas12-run
Jump to navigation Jump to search
 
(369 intermediate revisions by 6 users not shown)
Line 1: Line 1:
= Shift Documentation =
+
= General =
 
<!--#######################################  SHIFT DOCUMENTATION  ########################################-->
 
<!--#######################################  SHIFT DOCUMENTATION  ########################################-->
 
{| {{TableStyle1}}
 
{| {{TableStyle1}}
  
 
| valign=top |
 
| valign=top |
 +
==General==
 +
===[https://logbooks.jlab.org/book/hallb Logbook]===
 
===[http://www.jlab.org/Hall-B/shifts Shift Schedule]===
 
===[http://www.jlab.org/Hall-B/shifts Shift Schedule]===
===[https://logbooks.jlab.org/book/hallb Hall B Logbook]===
+
===[https://docs.google.com/spreadsheets/d/1VgDXAPe2px4KhHSwoFT8JC7Gt5-2b_zuquG18qWFI3I/edit?usp=sharing Run Coordinator Schedule]===
===[https://www.jlab.org/Hall-B/run-web/index_rgc.html ESAD, COO, RSAD]===
+
===[[Media:ESAD-RGD.pdf|ESAD]], [[Media:COO-RGDE.pdf|COO]], [[Media:RSAD-RGD-signed.pdf|RSAD]]===
* Note new [https://logbooks.jlab.org/entry/4047791 DOE guidance] on beam limits to FC! We should be allowed to run up to 90 nA without beam blocker.
 
 
===[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/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://bta Beam Time Accounting]===
+
===[https://www.jlab.org/Hall-B/run-web/rgd/ESAD_HallB-CLAS12_RGD.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rgd/COO_HallB-CLAS12_RGDE.pdf COO], [https://www.jlab.org/Hall-B/run-web/rgd/RSAD_HallB-CLAS12_RGD.pdf RSAD], [https://www.jlab.org/sites/default/files/Hall-B_ERG_09012023%20updated.pdf ERG] ===
* See guidance at '''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf BTA User Guide]'''.
+
 
 
 
| valign=top |
 
| valign=top |
===Manuals===
+
==Manuals==
 +
=====Systems=====
 +
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beamline_manual.pdf Beamline]
 +
* [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://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q Cryotarget & Flag Assembly Controls]
 +
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/daq/opman_master.pdf DAQ]
 +
* [[Media:clas12controls_shift.pdf|Slow Controls]]
 +
=====Detectors=====
 
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/dc/Drift-chamber-operating-procedure.pdf  DC]
 
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/dc/Drift-chamber-operating-procedure.pdf  DC]
 
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/ftof/ftof_manual.pdf  FTOF]
 
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/ftof/ftof_manual.pdf  FTOF]
Line 24: Line 34:
 
* [https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf CND]
 
* [https://clasweb.jlab.org/wiki/images/9/97/Ops_manual_cnd.pdf CND]
 
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/svt/svt_operation_manual.pdf  SVT]
 
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/svt/svt_operation_manual.pdf  SVT]
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/mm/Documentation_Shifters_MVT.pdf MVT]
+
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/mm/Documentation_Shifters_MVT.pdf MVT] and its [https://wiki.jlab.org/clas12-run/images/b/bf/MVT_for_Dummies.pdf Turn-on procedure]
** [https://wiki.jlab.org/clas12-run/images/b/bf/MVT_for_Dummies.pdf MVT turn on procedure]
 
 
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/ft/FT-Manual.pdf FT]
 
* [https://github.com/JeffersonLab/clas12-manuals/blob/master/ft/FT-Manual.pdf FT]
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beamline_manual.pdf Beamline]
+
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/band/band_om.pdf BAND]
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Torus_Power-Up_and_Power-Down_Procedure.pdf Torus Power-Up/Down Procedure]
+
 
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/torus/Hall_B_Solenoid_Power-Up_and_Power-Down_Procedure.pdf Solenoid Power-Up/Down Procedure]
+
=====Software=====
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/daq/opman_master.pdf DAQ]
+
* [https://wiki.jlab.org/clas12-run/images/c/c9/CedManual.pdf CED]
* [[Media:clas12controls_shift.pdf|Slow Controls]]
+
* [https://wiki.jlab.org/clas12-run/images/f/fd/CLAS12Mon_documentation.pdf MON12]
 +
 
  
 
| valign=top |
 
| valign=top |
===Procedures===
+
==Procedures==
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beam_estab_rgc.pdf Physics-Quality Beam]
+
* [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam]
 
* [[Media:clas12moller.pdf|Performing M&oslash;ller Runs]]
 
* [[Media:clas12moller.pdf|Performing M&oslash;ller Runs]]
 
* [[Media:HarpScanManual.pdf|Performing Harp Scans]]
 
* [[Media:HarpScanManual.pdf|Performing Harp Scans]]
* [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Tunnel/Hall Access]
+
* [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Accessing the Tunnel/Hall]
  
| valign=top |
+
==Logbooks==
===JLab Logbooks===
 
 
<font size=3>
 
<font size=3>
 
* [https://logbooks.jlab.org/book/elog MCC]
 
* [https://logbooks.jlab.org/book/elog MCC]
Line 53: Line 62:
  
 
= Phone Numbers =
 
= Phone Numbers =
 
=== NOTE: All NON-JLab numbers MUST be dialed with (757) area code. When calling from a CH landline, dial "9" first. To call from outside, all 4-digit numbers must be preceded by 757-269 === 
 
 
 
<!--#######################################  PHONE NUMBERS  #############################################-->
 
<!--#######################################  PHONE NUMBERS  #############################################-->
{{PhoneNumbers}}  
+
{{PhoneNumbers}}
[https://wiki.jlab.org/clas12-run/index.php?title=Template:PhoneNumbers&action=edit Click Here] to edit Phone Numbers.  Note, you then also have to edit the current page to force a refresh.
+
<!--- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE! -->
 
 
<!--- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE -->
 
  
 
= Short Term Schedule =
 
= Short Term Schedule =
 
<!--#######################################  Short Term Schedule  #############################################-->
 
<!--#######################################  Short Term Schedule  #############################################-->
 +
'''[https://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGD&action=edit Click to Edit]''' solely this tab. P.S.: You must click on the top Edit, next to Read, followed by "Save changes" to force the current page to refresh. <br>
  
=== <font color=blue size=4> ''' CLAS12 Run Group D </font> ''' ===
+
{{ShortTermSchedule-RGD}}
  
'''Run Coordinator: Lamiaa El Fassi'''  757 575-7540
 
  
''' PDL: Nathan Baltzell'''  (9-)757 876-1789 , x5902 office
+
= Run Coordinator =
 +
<!--####################################### Run Coordinator ################################################-->
  
''' [https://clasweb.jlab.org/wiki/index.php/RGC_RC Daily RC Meetings] at 14:00: CH Room 200C, and on Zoom '''
+
== '''Responsibilities''' ==
Zoom information: [https://jlab-org.zoomgov.com/j/1608674253?pwd=SFZyYmZLWXJieGtpV2dEdVRiUEJnUT09&from=addon Link], Meeting ID: 160 867 4253, Passcode: 786506
 
  
''' [https://userweb.jlab.org/~kuhn/RGC/RCschedule.pdf Run Coordinator Schedule] '''
+
* The RC duties are detailed in the [[Media:COO-RGDE.pdf|COO]].
 +
* Check and contact, if needed, upcoming shifts about their training or site access status.
 +
* The training requirements for the shift are:
 +
:- ES&H Orientation (SAF 100);<br>
 +
:- Radiation Worker Training (SAF 801);<br>
 +
:- Oxygen Deficiency Hazard Training (SAF 103);<br>
 +
:- Hall B Safety Awareness Walk-Through (SAF111)
 +
* Remote shifts are listed [[Upcoming-remote-shifts|here]].
 +
* Backup shifters are 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].
  
== Important Shift Notes ==
+
=== Daily ===
  
* In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House
+
* 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.
* If you have symptoms or a positive COVID test, do NOT come to your shift - instead, inform the PDL and the RC and JLab medical services immediately so that replacements can be arranged.
+
:&bull; See the ZOOM connection info under {{#switchtablink:Important_Links|Important Links}} tab.
* Read the logbook and be aware of previous 24 hours
 
* Arrive at least 10 minutes early for shift change
 
* Refresh the run wiki pages, look over them every shift.
 
* Follow the expert/worker shift instructions at the tabs above.  
 
* Communicate with your co-shift person!
 
** The shift expert should know about and refer to logbook entries in their shift summary
 
** The shift worker should discuss an issue with the shift expert before making extra logbook entries
 
  
== Short Term Schedule for the Week from Burgsday, July 17, 2023 - ==
+
* Update the run plan in the {{#switchtablink:Short_Term_Schedule|Short Term Schedule}} tab in coordination with the run group coordinator and communicate it to the shift crew.  
* Inbending torus field, 5-pass beam on ND3.  
 
* Beam Current: 666 nA
 
* Run duration: 100M events or 4 hours, whichever comes first.
 
* CODA Configuration:  PROD66
 
* Trigger file:  rgd_300MeV_v1.0.trg
 
* If HWP is changed, start a new run
 
  
== Reference Values ==
+
* Log the RC summary in the HBLOG.
  
=== FSD Thresholds ===
+
* Send a daily invitation for the RC meeting to hallb, clas_members, and rgd_ana mailing list.
* Upstream: 2k Hz
 
* Midstream: 2 kHz
 
* Downstream: 10 kHz
 
* BOM: 1 MHz
 
* 5 ms dwell time
 
  
=== Harp Scan References from RG-C ===
+
* Run the RC meetings at 1 PM in CH Room 200C and on ZOOM, except on Wednesdays.
* 2H01 [https://logbooks.jlab.org/entry/4037457]
+
* On Wednesdays, the RC meeting is on ZOOM ONLY @ 15:30 due to the conflict with the 13:30 MCC meeting and the unavailability of the CH room afterwards.
* 2C21 [https://logbooks.jlab.org/entry/4122116]
 
* Tagger [https://logbooks.jlab.org/entry/4122122]
 
  
 +
:&Dagger; To connect to Zoom in CH Room 200C, follow these steps:
 +
::&loz; 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.
 +
::&loz; Once logged in, use the recommended Google Chrome to join the ZOOM meeting on the browser or use the ZOOM application.
 +
::&loz; 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 near the microphone in the middle of the conference table. Once it rings, answer the call, and you will be prompted to join the meeting.
 +
::&loz; The room has a camera, so you may turn it on, if you wish, in the ZOOM browser interface.
  
= GENERAL INFORMATION =
+
=== Weekly ===
<!--####################################### GENERAL INFORMATION ########################################-->
+
* Attend in-person the MCC scheduling meeting on Wednesdays at 1:30 PM and report the run status via the submitted [https://ace.jlab.org/apps/pd/run-coordinator-reports Run Coordinator Weekly Summary];
  
'''see below for Known Detector Issues'''
+
:&Dagger; The report summarizes the data-taking status concerning the available beam used (ABU), any beam losses (BANU), CW on target (ABU+ABNU), etc., from 7 AM past Wed. through 7 AM the Wednesday the report is due, in addition to any standing and critical issues, plans for next week, and general comments/requests, if any.
 +
:&Dagger; Our beam time accounting info can be retrieved either from:
 +
::&loz; OPS logbook entries with tag 'Beam Accounting': [https://logbooks.jlab.org/tag/beamaccounting Timesheet Summaries];
 +
::&loz; [https://ace.jlab.org/btm/reports/physics-summary Beam Time Manager; Physics Time Accounting].
 +
:&Dagger; Refer to the [https://docs.google.com/spreadsheets/d/1VgDXAPe2px4KhHSwoFT8JC7Gt5-2b_zuquG18qWFI3I/edit?usp=sharing RC Timesheet] to calculate the percentage of scheduled experiment hours to date.
 +
:&Dagger; The total experiment data collected to date could be retrieved from the up-to-date "Accumulated Charge" depicted on the "Total Charge on Target Plot" in the {{#switchtablink:Monitoring|Monitoring}} tab.
 +
:&Dagger; A detailed plan of the target configuration change will be generated as soon as the run starts; however, an overview of it is summarized in slide 6 of this [https://clasweb.jlab.org/wiki/images/d/d4/RGD-Aug3023v1.pdf RG-D Overview].
  
== General Information ==
+
* Attend the Hall B meeting on Mondays at 9 AM and present your summary slides that should be sent beforehand to the Hall B leader, Patrick Achenbach, after checking them; please, with the Run Group Coordinator Lamiaa El Fassi.
  
* '''Controlled access''': after you call MCC, they will drop the hall to controlled access once someone goes down and calls them for entry. Then call when they should go back to beam permit and call again to say you want the beam back and what beam current. Rapid access is controlled access without RadCon.
 
  
* If MCC needs to '''diagnose beam with a harp''', we can offer them tagger 2C24 and follow the procedures required for that. '''2H01 harp scan should not be done when we have beam raster on.'''
+
= Shift Expert =
 +
<!--#######################################  Shift Expert  ################################################-->
  
* '''BMT''':
+
== '''Tasks''' ==
** '''After HV trip''': the channel HV should be turned back on as soon as you notice the trip, power cycle by turning HV OFF and ON '''without waiting for any amount of time'''.
 
** '''HV frequently tripping''': Call expert. Do not change HVs without approval from the expert.
 
  
* '''mon12''': It can happen that histograms do not get cleared completely at run start. This is seen eg as an excess of small multiplicities. The remedy is to quit mon12 and open it again. Other than that, small multiplicities come from time intervals with beam down. You might want to look at the multiplicities before uploading the mon12 histograms in the logbook.
+
* Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift.  
 
+
:&bull; If it's your first shift or a shift after a long pause, please come at least 4 hours before your shift (or even better, come a day earlier) to shadow the previous shifter and familiarize yourself with all shift duties and technicalities of the ongoing experiment.  
* '''DAQ''':
 
** clondaq6/data is full, switched to clondaq7, rastermon should be using ET on clondaq7
 
*** this means startup of rastermon via command line: rastermon --et --host clondaq7
 
*** see https://logbooks.jlab.org/entry/4066149, default for rastermon has been changed to clondaq7
 
** It should no longer be necessary to quit RasterMon at the end of each run and restart after a successful "Go" for the next run. However, if DAQ crashes, you SHOULD follow these steps, and the same for mon12.  
 
 
* '''Magnet trip''': call "Engineering on call", if due to cryo, also inform the target expert about the cryogenic issues.
 
 
 
* '''Holes in CND occupancies: CAMAC CFD crate was turned off/on for some reason. You need to run the script to set the thresholds for CND CFDs. Go on a clondaq machine and type cnd-cfd-thresh -w 0. Or call the CND phone if this doesn't work.
 
 
 
* '''Hall lights''': Before leaving the hall''' and going to beam permit check that dome lights, forward carriage lights, and pie tower lights are OFF.
 
  
* '''Moller runs''': should be taken with 8-10 nA.
+
* Follow the '''{{#switchtablink:Short_Term_Schedule|Short Term Schedule}}''';
 +
:&bull; The RC must be notified before changing run conditions.
  
* '''Beam viewer''': Please REMOVE the beam viewer unless we are actively tuning the beam or calibrating beam position/raster, to avoid damage to electronics, cameras etc.
+
* Operate the '''Data Acquisition'''.
 +
* Take action on and log '''alarms'''.
  
* '''Change of running conditions'''  
+
* '''Communicate''' with your co-shift person:
** Check that the trigger alarms (on rate/nA) are set appropriately and RC changes them as needed.
+
:&bull; The shift worker should discuss an issue with the shift expert before making extra logbook entries.
** Whenever the target type or polarization direction changes, or the half-wave plate status changes, make sure to enter a comment in the BEGIN RUN / END RUN comment box.
+
:&bull; 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.
** Do not change running conditions while a run is ongoing. This includes changing target polarization or HWP, etc.
 
  
== Known Issues ==
+
* Check for and read any comments to '''log-book entries''' made during your shift.
  
Fr 11 Nov 2022
+
* 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: 
ECAL PMT_SEC2_WO8 HV is disabled
+
:&bull; Refer to relevant logbook entries in the shift summary.
https://logbooks.jlab.org/entry/4080950
+
:&bull; Include a list of runs taken during the shift with relevant run information;
 +
<!--::- See, for instance https://logbooks.jlab.org/entry/4202910, where the information is simply copied from the RCDB.-->
 +
::- See, for instance, this [https://logbooks.jlab.org/entry/4214804 shift summary] where all relevant run info, links, and shift activities are cited.
  
Follow-up Re: RICH tile 21 in sector 1 is dead. Working without one tile out of 276 for a moment
+
* 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;
https://logbooks.jlab.org/entry/4079453
+
:&bull; Both, you and the shift worker should run MON12 and '''reset & check spectra frequently'''.
  
Run #17396: RICH lost three scalars
+
* If the worker shift is remote, maintain communication in Zoom: https://jlab-org.zoomgov.com/j/1619881100
https://logbooks.jlab.org/entry/4079190
 
  
Tuesday, February 7, 2023:
+
* If you have any other questions or uncertainties about what to do, call the RC.
BMT Sector 2 Layer 5 is broken (HV set to 200 V)
 
  
= Shift Expert =
+
* <!--font color=BROWN>New as of 11/25/23: No RICH recoveries are needed until further notice!</font><font color=Grey-->
<!--#######################################  Shift Expert ################################################-->
+
*'''New RICH recovery protocol:'''
 +
:&bull; See '''https://logbooks.jlab.org/entry/4201728''' for important details.
 +
:&bull; In case of a RICH issue a '''screen shot of both scalers and temperatures''' should be logged in the '''RICH logbook''' before running the appropriate recovery.
 +
:&bull; '''Issues''' can be seen from missing tiles in the scaler and temperature GUIs or the occupancy as seen in MON12. Do not stop an ongoing run, but do the '''fast recovery between runs'''.
 +
:&bull; If the issue is seen in the scaler but not in the temperature GUI, then you should do a full recovery; see https://logbooks.jlab.org/entry/4214184. This might preempt the daily full recovery.
 +
:&bull; '''Daily full RICH recovery''' remains part of the protocol, preferably done during the daytime and only between runs; do not stop an ongoing run. State in your shift summary that you did the recovery (or why you did not).
 +
:&bull; '''Avoid unnecessary recoveries''', see https://logbooks.jlab.org/entry/4208477. The RICH overview GUI shows how many seconds have passed since the last full recovery. Also, there is a minor alarm when 24 hours have passed since the last full recovery. Acknowledge the alarm and wait for the end of the run before running the recovery.
 +
:&bull; Note that you have to '''Restart DAQ from Scratch; see DAQ Operation & related General Instructions under {{#switchtablink:Short_Term_Schedule|Short Term Schedule}}, after any RICH recovery'''.
 +
::&loz; In case of getting a '''ROC error''' during the recovery, it's advised to "'''roc_reboot rich4'''" in the '''DAQ VNC terminal''' then "ping rich4" instead of "ssh rich4" to check whether it's initialized.
 +
:::- <font color=brown> When pinging a ROC, e.g., "ping rich4", stop it with Ctrl+C after a couple of printouts showing different latency times. </font>
 +
:&bull; '''If the beam is ON and a RICH recovery is taking more than 5 min, please call the RICH expert''', preferably ''the secondary number before the primary''.
 +
* For any '''RICH problems overnight or on weekends/holidays, please call the RICH expert''', preferably ''the secondary number before the primary'', '''along with the RC''' to discuss and fix the issue!  </font>
  
== Shift expert tasks ==
 
* Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift.
 
* Follow the '''Short Term Schedule''' as outlined by RC
 
** Run Plan, DAQ Configuration, and References and Standards
 
** also check tab '''GENERAL INFORMATION'''
 
* Keep '''shift summary''' up to date in HBLOG. Record all that happens.
 
  
* Ensure that all '''monitoring''' plots are logged correctly and checked against the reference plots for every single run, see link under https://wiki.jlab.org/clas12-run/index.php/Run_Group_C#Useful_Links
+
* '''New MVT LV Reboot Procedure'''
 +
:&bull; 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:
 +
::&loz; Turn '''LV OFF from MVT Overview->Low Voltage->MVT-All'''. LV status indicators should change from green to black;
 +
::&loz; '''Wait 20 seconds''', then '''turn LV back from the same menu''';
 +
::&loz; 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;
 +
::&loz; At this point, mvt1, mvt2, and mvt3 ROCS can be rebooted;
 +
::&loz; Start a run by '''Restarting DAQ from Scratch; see DAQ Operation & related General Instructions under {{#switchtablink:Short_Term_Schedule|Short Term Schedule}}.
 +
::&loz; '''If the beam is ON, and a reboot process takes more than 5 min, please call the DAQ and/or SVT/MVT/MM expert'''.  
  
* '''Polarized target''':
 
** Helicity-Latched Trigger GUI  and the Helicity Trigger Asymmetry strip-chart (not accessible remotely) (example https://logbooks.jlab.org/entry/4041939).  (''ONLY WHILE ACTUALLY RUNNING ON NH3 AND ND3 targets!'')
 
** In case of any issues, ''contact the polarized target expert on call''.
 
** '''Ice on the run valve'''
 
*** See the run valve via camera http://hallbcam04/view/index.shtml, (see also Camera on PT12 -- web link at Lognumber 4002803.) Example of ice on the valve, see https://logbooks.jlab.org/entry/4001225.
 
** '''NMR running'''  (''ONLY WHILE ACTUALLY RUNNING ON NH3 AND ND3 targets!'')
 
*** The JLab Polarization Display is seen via a VNC window in the counting room. Here, the NMR Controls' blue bar must be moving, indicating that the NMR is running and the polarization is measured.
 
*** The NMR frequency needs to be controlled by hand. If you see target polarization (on the red graph) starting to drop, call the expert. They will guide you through the adjustment procedure.  This will be in the electronics room by the door to the counting room, in the third crate from the right ("CR-6"). White box which says "EIO Tube" and has a red button at the top right, which says "Move", next to a display for "Position". This will be the one to press, under guidance of the target expert.
 
** '''Alarms''' from System RG-C Polarized Target (alarm handler).
 
  
* Do a '''RICH recovery''' (press the RICH Recovery button on the GUI) once daily during day shift, between runs. Please log in shift summary.
+
* '''[https://bta.acc.jlab.org Fill out BTA]''' hourly;
** Note the automated "RICH Recovery" sequence already confirms RICH4 is up and accepting ssh connections before claiming success.
+
:&bull; Accelerator beam time:
** You have to "Cancel->Reset->Configure->Download->Prestart" before starting the next run.
+
::&loz; ABU: acceptable beam used,
 +
::&loz; BANU: beam acceptable but not used (''should be reflected in our PCC or UED'');
 +
:::- ''Exception: BANU due to beam tuning with harp scans or Moller runs might be included in BNA''.
 +
::&loz; BNA: beam not acceptable (e.g., tuning, drifting, not focused);
 +
::&loz; ACC: Accelerator configuration change (e.g., pass change or Maintenance/Beam Studies recovery);
 +
::&loz; OFF: Accelerator is down.
 +
:&bull; Experiment beam time (do change these values):
 +
::&loz; ER: Experiment ready (should be 1 hour - PCC - UED)
 +
::&loz; PCC: Planned configuration change (beam tuning with harp scans or Moller runs, target change, DAQ; e.g., stopping/starting runs, tests, etc.)
 +
::&loz; UED: Unplanned experiment down (hardware failure, DAQ crashes, including sudden livetime drop to "''zero''" or low trigger rates, or experiment/hall problems)
 +
:::- ''Exception: BANU, due to time spent on drifting beam positions after beam down, may be counted as ER on our side''.
 +
:&bull; Enter fields at the "Shift Information" tab;
 +
:&bull; 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 here, https://ace.jlab.org/btm/reports/activity-audit, whether you saved correctly!
 +
::&loz; Acknowledge the popup error message about the last hour not being completed by clicking OK.
 +
:&bull; Sign, viz log completed 8-hour sheet.
 +
:&bull; '''Note: we can change the timesheet up to 48 hours after completion.'''
  
* '''[https://bta.acc.jlab.org Fill out BTA]''' hourly. Click "Load from EPICS" to automatically fill the left side then correct as needed.
+
= Shift Worker =
** Accelerator beam time:
+
<!--####################################### Shift Worker ################################################-->
*** ABU: acceptable beam used (eg harp scans, calibrations, trigger settings, running)
+
== Tasks ==
**** The info from EPICS is not always correct, e.g. when taking data with low beam current, you should change the ABU to the proper (estimated) time by hand instead of simply accepting "0" if you are actually taking data.
 
*** BANU: beam acceptable but not used (eg radiator change or our problems)
 
*** BNA: beam not acceptable (eg tuning, drifting, not focused)
 
** Experiment beam time
 
*** ER: experiment ready
 
*** PCC: planned configuration change (when beam is masked while radiators are moved, DAQ (stopping/starting runs, tests, ...) are PCC..
 
*** UED: unplanned experiment down, is used for hardware failure
 
** Enter fields at tab "Shift Information"
 
** Promptly send "Info for MCC" at 7:00, 15:00, and 23:00
 
** Sign, viz log completed 8 hour sheet
 
  
 +
* Come to your shift in time for the shift change, 10-15 minutes before the start of your shift;
 +
:&bull; If it's your first shift or a shift after a long pause, please come at least 4 hours before your shift (or even better, come a day earlier) to shadow the previous shifter and familiarize yourself with all shift duties and technicalities of the ongoing experiment.
  
'''In case of other questions or uncertainties of what to do, call the RC or PDL'''
+
* Discuss an issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary and the start/end of run ''Comment field'' in the DAQ pop-up window.
  
(remote) shift worker: see dedicated [https://wiki.jlab.org/clas12-run/index.php/Run_Group_M#tab=Remote_Shifts Worker Shift] tab above.
+
=== Frequently ===
  
 +
* Reset and check MON12 histograms frequently, preferably each 1/2h, during a run:
 +
<!--* Kill and restart the '''MON12 program''' after the end of each run until it's instructed otherwise! -->
 +
:&bull; Note that some plots have radio buttons at the bottom to choose the sector, so you should cycle through and check all sectors.
  
 +
=== Once per run ===
  
= Worker Shift =
+
* Submit EPICS '''screenshots''' to the HBRUN logbook '''with beam ON'''
<!--#######################################  Worker Shift  ################################################-->
+
:&loz; Beamline overview, in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser]
== Shift Worker Tasks ==
+
:&loz; CLAS12 trigger rates and DAQ status
  
* Check the information in the '''Short Term Schedule''' and '''GENERAL INFORMATION''', for every shift
+
* Upload '''MON12''' monitoring plots to the logbook with sufficient statistics:
* Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift.
+
:&loz; Afterwards, compare them to the reference and recent uploads; see the top-right link at the {{#switchtablink:Monitoring|Monitoring}} tab.
* Use the new '''HBRUN logbook''' for automated and run-specific entries and screenshots, see https://logbooks.jlab.org/entry/4048698
 
  
 +
* Submit '''Beam current and position strip charts''' to the logbook at '''the end of the run'''
 +
:&loz; If they are not up already: (CS-Studio &rarr; Beamline &rarr; Strip Charts);
 +
:&loz; Choose the 'time-span width' to be compatible with the run duration.
 +
:&loz; To make the logbook entry using the clascss:
 +
::- On the bottom chart, click on parameter "'''B_DAQ:EB:datarate'''" so that its range is seen on the y-axis and take the first snapshot;
 +
::- On the same Bottom (fourth) chart, click on the parameter "'''B_DAQ:EB:eventrate'''", take the second snapshot, then submit!
 +
<!--choose "Append to Logbook Entry", provide the above logbook entry number, and click on "Append" to submit.
 +
::- In the blank area within the dotted lines in any chart, right-click, and choose "Make Logbook Entry";
 +
::- The title of the logbook entry can be changed;
 +
::- Un-click ELOG, select HBLOG, and click on "Make Entry" to submit;
 +
::- Click on the parameter "'''B_DAQ:EB:eventrate'''", then choose "Append to Logbook Entry", provide the above logbook entry number, and click on "Append" to submit.-->
  
'''Make the following log entries ONCE per run'''
+
=== Once per shift ===
* '''Screenshots''': submit to logbook only if you capture the information '''with beam ON'''
 
** 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
 
** RGC Polarized Target GUI - under Beamline on CS-Studio
 
** Helicity Asymmetry Strip Charts - see [https://logbooks.jlab.org/entry/4123228] for an example. Also read and follow the instructions below under "Log the Strip Charts".
 
  
* '''Upload monitoring plots to logbook'''
+
* Fill the [https://logbooks.jlab.org/checklists/151 shift checklist];
** Standard spectra (mon12): inspect '' all monitoring histograms ''' and carefully compare them to the corresponding reference histograms: reference, current, and 5 most recent runs, see link under tab Useful Links
+
:&bull; During production or if the beam is down for your entire shift, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status, and CLAS12 Trigger;
*** You can choose a different reference run if you are confident what you are doing, the reference numbers refer to logbook entries.
+
:&bull; During extended downtime, get relevant values from the latest EPICS screenshots you made during production.
** Raster Monitoring  (use "Log Entry" button on RasterMon screen at bottom-right corner).
 
*** An example of a "decent looking" RasterMon is here: [https://logbooks.jlab.org/entry/4040598]. The x and y distributions should show a smooth dome, without any horns or spikes on it and without the distributions being cut off at the edges.  
 
  
'''Once per shift:'''
+
* <!--span style="font-size:112%; line-height: 2em;"><font color=red>'''Please ignore for now as the program is under debugging!'''</font></span Per Gagik Gavalian's request-->Upload by the end of the shift while data is being collected [https://github.com/JeffersonLab/caos/tree/main#readme clas12online] tabs plots to the HBLOG logbook '''with sufficient statistics''';
 +
:&loz; Please refresh the [https://github.com/JeffersonLab/caos/tree/main#readme clas12online] program at the beginning of your shift in case the previous shifter does not do it after uploading the snapshots. Also, do that while the DAQ is running!
 +
:&loz; Note that the program must be restarted after each DAQ crash!
 +
<!--:&dagger; ''Please note that [https://github.com/JeffersonLab/caos/tree/main#readme clas12online] needs to be relaunched at the beginning of each run as instructed in the Github [https://github.com/JeffersonLab/caos/tree/main#readme Readme] so the plots will be refreshed''.-->
 +
<!--** ''Please note that at the beginning of the run, only one sector, sector 1, distributions will be displayed in the VERTEX tab since this is the only sector trained so far. As soon as RG-D data are taken, the AI/ML network will be retrained, and thus, the other sector distributions will be populated''. -->
  
* Fill the [https://logbooks.jlab.org/checklists/151 shift checklist]
+
== For Remote Shifts ==
* Log screen shots of RICH temperature and scaler maps. '''Log in RICH logbook.'''
+
<font color=red>'''Please inform the PDL that your shifts will be remote.''' </font color=red>
 +
Remote shifts are listed [[upcoming-remote-shifts|here]]
  
'''Regularly''':
+
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:  [https://jlab-org.zoomgov.com/j/1618614939 https://jlab-org.zoomgov.com/j/1618614939]
* '''reset & check spectra frequently (every 30 - 60 minutes)'''
+
:&loz; The passcode is required and contained in [https://logbooks.jlab.org/entry/4158818 this log entry]
** Some plots in the online mon12 have a choice of histogram sets per sector, select buttons at the bottom of the plot. That means you have to look at all sectors for these histograms.
+
:&loz; Remind the expert in the counting-house to restart their ZOOM, if necessary
** The logbook entry shows all histograms.
+
* Remote VNC connection instructions:  https://logbooks.jlab.org/entry/3906039
 +
* '''If you mistyped''' (username, pincode, passcode,...) a string of numbers will appear with text asking you to respond to this challenge. Back out with ctrl_c to get another try! After N+1 mistypes, you will be locked out. For several hours after that, you will not even be able to get to the public JLab webpages.
 +
:&loz; All necessary applications should be available from the desktop menu (left/right click on the desktop)
 +
:&loz; EPICS GUIs should be accessed '''ONLY''' via the desktop menu or by running <tt>clascss-remote</tt>.
 +
<!--* [https://userweb.jlab.org/~baltzell/clas12/shift/remote-demo.mp4 Remote Demonstration Video (150 MB)]-->
 +
:&loz; Some charts are also accessible via web browser: [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Upstream+and+Midstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scaler_cS3b&pv=scaler_cS4b&pv=scaler_cS6b&pv=scaler_cS12b&pv=scaler_cS13b&pv=scaler_cS14b&pv=scaler_cS15b&scaler_cS3blabel=scaler_cS3b&scaler_cS3bcolor=%23a6cee3&scaler_cS3byAxisLabel=Rate++%28Hz%29&scaler_cS3byAxisMin=&scaler_cS3byAxisMax=&scaler_cS3byAxisLog&scaler_cS3bscaler=&start=2020-08-08+09%3A02%3A36&end=2020-08-08+09%3A07%3A36&scaler_cS4blabel=scaler_cS4b&scaler_cS4bcolor=%231f78b4&scaler_cS4byAxisLabel=&scaler_cS4byAxisMin=&scaler_cS4byAxisMax=&scaler_cS4byAxisLog=&scaler_cS4bscaler=&scaler_cS5byAxisLabel=&scaler_cS5byAxisMin=&scaler_cS5byAxisMax=&scaler_cS5byAxisLog=&scaler_cS5bscaler=&scaler_cS6blabel=scaler_cS6b&scaler_cS6bcolor=%2333a02c&scaler_cS6byAxisLabel=&scaler_cS6byAxisMin=&scaler_cS6byAxisMax=&scaler_cS6byAxisLog=&scaler_cS6bscaler=&scaler_cS7byAxisLabel=&scaler_cS7byAxisMin=&scaler_cS7byAxisMax=&scaler_cS7byAxisLog=&scaler_cS7bscaler=&scaler_cS12blabel=scaler_cS12b&scaler_cS12bcolor=%23e31a1c&scaler_cS12byAxisLabel=&scaler_cS12byAxisMin=&scaler_cS12byAxisMax=&scaler_cS12byAxisLog=&scaler_cS12bscaler=&scaler_cS13blabel=scaler_cS13b&scaler_cS13bcolor=%23fdbf6f&scaler_cS13byAxisLabel=&scaler_cS13byAxisMin=&scaler_cS13byAxisMax=&scaler_cS13byAxisLog=&scaler_cS13bscaler=&scaler_cS14blabel=scaler_cS14b&scaler_cS14bcolor=%23ff7f00&scaler_cS14byAxisLabel=&scaler_cS14byAxisMin=&scaler_cS14byAxisMax=&scaler_cS14byAxisLog=&scaler_cS14bscaler=&scaler_cS15blabel=scaler_cS15b&scaler_cS15bcolor=%23cab2d6&scaler_cS15byAxisLabel=&scaler_cS15byAxisMin=&scaler_cS15byAxisMax=&scaler_cS15byAxisLog=&scaler_cS15bscaler= Upstream/Midstream Halo Counters], [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Downstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scalerS8b&pv=scalerS9b&scalerS8blabel=scalerS8b&scalerS8bcolor=%23a6cee3&scalerS8byAxisLabel=Rate++%28Hz%29&scalerS8byAxisMin=&scalerS8byAxisMax=&scalerS8byAxisLog&scalerS8bscaler=&pv=scalerS10b&pv=scalerS11b&scalerS9blabel=scalerS9b&scalerS9bcolor=%231f78b4&scalerS9byAxisLabel=&scalerS9byAxisMin=&scalerS9byAxisMax=&scalerS9byAxisLog=&scalerS9bscaler=&scalerS10blabel=scalerS10b&scalerS10bcolor=%23b2df8a&scalerS10byAxisLabel=&scalerS10byAxisMin=&scalerS10byAxisMax=&scalerS10byAxisLog=&scalerS10bscaler=&scalerS11blabel=scalerS11b&scalerS11bcolor=%2333a02c&scalerS11byAxisLabel=&scalerS11byAxisMin=&scalerS11byAxisMax=&scalerS11byAxisLog=&scalerS11bscaler= Downstream Halo Counters], [https://epicsweb.jlab.org/wave/?start=2020-07-08+16%3A50%3A02&end=2020-07-08+16%3A55%3A02&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Beam+Currents&fullscreen=false&layoutMode=2&viewerMode=2&pv=IPM2C21A&pv=IPM2C24A&pv=scaler_calc1b&IPM2C21Alabel=IPM2C21A&IPM2C21Acolor=%23a6cee3&IPM2C21AyAxisLabel=Beam+Current+%28nA%29&IPM2C21AyAxisMin=0&IPM2C21AyAxisMax=300&IPM2C21AyAxisLog&IPM2C21Ascaler=&scaler_calc1blabel=Faraday+Cup&scaler_calc1bcolor=%23b2df8a&scaler_calc1byAxisLabel=&scaler_calc1byAxisMin=&scaler_calc1byAxisMax=&scaler_calc1byAxisLog&scaler_calc1bscaler= Beam Currents], [https://epicsweb.jlab.org/wave/?start=2020-08-03+12%3A30%3A57&end=2020-08-03+12%3A35%3A57&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=BPM+Positions+%28Y-Axis+is+mean+%2B%2F-+0.5+mm%29&fullscreen=false&layoutMode=3&viewerMode=2&pv=IPM2C24A.XPOS&pv=IPM2C24A.YPOS&pv=IPM2H01.XPOS&pv=IPM2H01.YPOS&IPM2C24A.XPOSlabel=IPM2C24A.XPOS&IPM2C24A.XPOScolor=%23e31a1c&IPM2C24A.XPOSyAxisLabel=&IPM2C24A.XPOSyAxisMin=-2.0&IPM2C24A.XPOSyAxisMax=+1.0&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=pink&IPM2C24A.YPOSyAxisLabel=&IPM2C24A.YPOSyAxisMin=-2.0&IPM2C24A.YPOSyAxisMax=1.0&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=darkgreen&IPM2H01.XPOSyAxisLabel=&IPM2H01.XPOSyAxisMin=-2.0&IPM2H01.XPOSyAxisMax=1.0&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=lightgreen&IPM2H01.YPOSyAxisLabel=&IPM2H01.YPOSyAxisMin=-2.0&IPM2H01.YPOSyAxisMax=1.0&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler=#a6cee3&IPM2C24A.XPOSyAxisLabel=2C24+X+(mm)&IPM2C24A.XPOSyAxisMin=-1.5&IPM2C24A.XPOSyAxisMax=-0.5&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=%231f78b4&IPM2C24A.YPOSyAxisLabel=2C24+Y+(mm)&IPM2C24A.YPOSyAxisMin=0.3&IPM2C24A.YPOSyAxisMax=1.3&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=pink&IPM2H01.XPOSyAxisLabel=2H01+X+(mm)&IPM2H01.XPOSyAxisMin=-0.6&IPM2H01.XPOSyAxisMax=0.4&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=darkred&IPM2H01.YPOSyAxisLabel=2H01+Y+(mm)&IPM2H01.YPOSyAxisMin=0.4&IPM2H01.YPOSyAxisMax=1.4&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler= BPM Positions]
  
* '''Check''' the [http://hallbcam04/view/index.shtml life cam] of the polarized target run valve for plumes or ice buildup (hallbcam04)
 
** Make sure you refresh the web page! Its no longer necessary to put a snapshot into the logbook UNLESS something looks suspicious. In THAT case, immediately inform the target expert(s).
 
  
* '''Log the ''strip charts'' in time intervals ''according to the x-axis time span'', via right-click on the screen and selecting "Make Elog Entry". Make sure NOT to submit to ELOG.'''
 
** Beam current and position strip-charts (CS-Studio -> Beamline -> Strip Charts)
 
** Helicity Trigger Asymmetry strip-chart (CS-Studio -> DAQ -> Helicity-Latched Trigger GUI Screen -> click on "Menu" -> myaPlot (not accessible remotely) -> Choose "load config time axis: start: -12 hours end: NOW" and click "accept"
 
*** [https://logbooks.jlab.org/entry/4123228 Example] 
 
*** '''Choose reasonable y / x axis ranges:''' R-click on the axis -> Modify (axis-name) Axis
 
*** For the y axis in the bottom panel, choose the NMR polarization and a reasonable range for the y axis (always from 0 to some maximum value), same for the 60-min trigger bit polarization. Those two do NOT have to have the same scale - it is better to try to get the dark blue and red curves to lie on top of each other (more or less).
 
*** Set the time axis auto-update.  ">>" symbol will appear below the time axis when this is activated.  (Right-click on X axis ->" [A] Set Auto Time Stepping")
 
 
* You can also see beam charts in the Web Browser: [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Upstream+and+Midstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scaler_cS3b&pv=scaler_cS4b&pv=scaler_cS6b&pv=scaler_cS12b&pv=scaler_cS13b&pv=scaler_cS14b&pv=scaler_cS15b&scaler_cS3blabel=scaler_cS3b&scaler_cS3bcolor=%23a6cee3&scaler_cS3byAxisLabel=Rate++%28Hz%29&scaler_cS3byAxisMin=&scaler_cS3byAxisMax=&scaler_cS3byAxisLog&scaler_cS3bscaler=&start=2020-08-08+09%3A02%3A36&end=2020-08-08+09%3A07%3A36&scaler_cS4blabel=scaler_cS4b&scaler_cS4bcolor=%231f78b4&scaler_cS4byAxisLabel=&scaler_cS4byAxisMin=&scaler_cS4byAxisMax=&scaler_cS4byAxisLog=&scaler_cS4bscaler=&scaler_cS5byAxisLabel=&scaler_cS5byAxisMin=&scaler_cS5byAxisMax=&scaler_cS5byAxisLog=&scaler_cS5bscaler=&scaler_cS6blabel=scaler_cS6b&scaler_cS6bcolor=%2333a02c&scaler_cS6byAxisLabel=&scaler_cS6byAxisMin=&scaler_cS6byAxisMax=&scaler_cS6byAxisLog=&scaler_cS6bscaler=&scaler_cS7byAxisLabel=&scaler_cS7byAxisMin=&scaler_cS7byAxisMax=&scaler_cS7byAxisLog=&scaler_cS7bscaler=&scaler_cS12blabel=scaler_cS12b&scaler_cS12bcolor=%23e31a1c&scaler_cS12byAxisLabel=&scaler_cS12byAxisMin=&scaler_cS12byAxisMax=&scaler_cS12byAxisLog=&scaler_cS12bscaler=&scaler_cS13blabel=scaler_cS13b&scaler_cS13bcolor=%23fdbf6f&scaler_cS13byAxisLabel=&scaler_cS13byAxisMin=&scaler_cS13byAxisMax=&scaler_cS13byAxisLog=&scaler_cS13bscaler=&scaler_cS14blabel=scaler_cS14b&scaler_cS14bcolor=%23ff7f00&scaler_cS14byAxisLabel=&scaler_cS14byAxisMin=&scaler_cS14byAxisMax=&scaler_cS14byAxisLog=&scaler_cS14bscaler=&scaler_cS15blabel=scaler_cS15b&scaler_cS15bcolor=%23cab2d6&scaler_cS15byAxisLabel=&scaler_cS15byAxisMin=&scaler_cS15byAxisMax=&scaler_cS15byAxisLog=&scaler_cS15bscaler= Upstream/Midstream Halo Counters], [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Downstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scalerS8b&pv=scalerS9b&scalerS8blabel=scalerS8b&scalerS8bcolor=%23a6cee3&scalerS8byAxisLabel=Rate++%28Hz%29&scalerS8byAxisMin=&scalerS8byAxisMax=&scalerS8byAxisLog&scalerS8bscaler=&pv=scalerS10b&pv=scalerS11b&scalerS9blabel=scalerS9b&scalerS9bcolor=%231f78b4&scalerS9byAxisLabel=&scalerS9byAxisMin=&scalerS9byAxisMax=&scalerS9byAxisLog=&scalerS9bscaler=&scalerS10blabel=scalerS10b&scalerS10bcolor=%23b2df8a&scalerS10byAxisLabel=&scalerS10byAxisMin=&scalerS10byAxisMax=&scalerS10byAxisLog=&scalerS10bscaler=&scalerS11blabel=scalerS11b&scalerS11bcolor=%2333a02c&scalerS11byAxisLabel=&scalerS11byAxisMin=&scalerS11byAxisMax=&scalerS11byAxisLog=&scalerS11bscaler= Downstream Halo Counters], [https://epicsweb.jlab.org/wave/?start=2020-07-08+16%3A50%3A02&end=2020-07-08+16%3A55%3A02&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Beam+Currents&fullscreen=false&layoutMode=2&viewerMode=2&pv=IPM2C21A&pv=IPM2C24A&pv=scaler_calc1b&IPM2C21Alabel=IPM2C21A&IPM2C21Acolor=%23a6cee3&IPM2C21AyAxisLabel=Beam+Current+%28nA%29&IPM2C21AyAxisMin=0&IPM2C21AyAxisMax=300&IPM2C21AyAxisLog&IPM2C21Ascaler=&scaler_calc1blabel=Faraday+Cup&scaler_calc1bcolor=%23b2df8a&scaler_calc1byAxisLabel=&scaler_calc1byAxisMin=&scaler_calc1byAxisMax=&scaler_calc1byAxisLog&scaler_calc1bscaler= Beam Currents], [https://epicsweb.jlab.org/wave/?start=2020-08-03+12%3A30%3A57&end=2020-08-03+12%3A35%3A57&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=BPM+Positions+%28Y-Axis+is+mean+%2B%2F-+0.5+mm%29&fullscreen=false&layoutMode=3&viewerMode=2&pv=IPM2C24A.XPOS&pv=IPM2C24A.YPOS&pv=IPM2H01.XPOS&pv=IPM2H01.YPOS&IPM2C24A.XPOSlabel=IPM2C24A.XPOS&IPM2C24A.XPOScolor=%23e31a1c&IPM2C24A.XPOSyAxisLabel=&IPM2C24A.XPOSyAxisMin=-2.0&IPM2C24A.XPOSyAxisMax=+1.0&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=pink&IPM2C24A.YPOSyAxisLabel=&IPM2C24A.YPOSyAxisMin=-2.0&IPM2C24A.YPOSyAxisMax=1.0&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=darkgreen&IPM2H01.XPOSyAxisLabel=&IPM2H01.XPOSyAxisMin=-2.0&IPM2H01.XPOSyAxisMax=1.0&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=lightgreen&IPM2H01.YPOSyAxisLabel=&IPM2H01.YPOSyAxisMin=-2.0&IPM2H01.YPOSyAxisMax=1.0&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler=#a6cee3&IPM2C24A.XPOSyAxisLabel=2C24+X+(mm)&IPM2C24A.XPOSyAxisMin=-1.5&IPM2C24A.XPOSyAxisMax=-0.5&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=%231f78b4&IPM2C24A.YPOSyAxisLabel=2C24+Y+(mm)&IPM2C24A.YPOSyAxisMin=0.3&IPM2C24A.YPOSyAxisMax=1.3&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=pink&IPM2H01.XPOSyAxisLabel=2H01+X+(mm)&IPM2H01.XPOSyAxisMin=-0.6&IPM2H01.XPOSyAxisMax=0.4&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=darkred&IPM2H01.YPOSyAxisLabel=2H01+Y+(mm)&IPM2H01.YPOSyAxisMin=0.4&IPM2H01.YPOSyAxisMax=1.4&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler= BPM Positions]
 
 
== For REMOTE Shifts (offsite): ==
 
* '''Zoom for 24-7 communication with counting house:'''  https://jlab-org.zoomgov.com/j/1619881100
 
** Passcode REQUIRED: 927417
 
* Remind the expert in the counting house to restart their zoom, if necessary
 
 
* Remote VNC connection instructions:  https://logbooks.jlab.org/entry/3906039
 
** All necessary applications should be avaible from the desktop menu (left/right click on the desktop)
 
* EPICS GUIs should be accessed '''ONLY''' via the desktop menu or by running <tt>clascss-remote</tt>.
 
* [https://userweb.jlab.org/~baltzell/clas12/shift/remote-demo.mp4 Remote Demonstration Video (150 MB)]
 
 
==== ATTENTION: If you plan to take (a) remote shift(s), you MUST test your setup (including VNC connection) at least 24 hours before your first shift! ====
 
  
 
= Monitoring =
 
= Monitoring =
Line 273: Line 268:
 
{| {{TableStyle1}}
 
{| {{TableStyle1}}
 
| valign=top |
 
| valign=top |
===Webcams===
+
=== Webcams ===
 
* [http://cctv1.jlab.org Tagger Beam Dump Viewer]
 
* [http://cctv1.jlab.org Tagger Beam Dump Viewer]
* [http://hallbcam02.jlab.org Hall Fisheye]
+
* [http://hallbcam02.jlab.org Hall Fisheye]; [http://hallbcam00.jlab.org/aca/index.html#view Additional Hall Cams]
 
* Faraday Cup beam viewer
 
* Faraday Cup beam viewer
** To reboot it, run <tt>beam-viewer-reboot</tt>
+
:&bull; To reboot it, run <tt>beam-viewer-reboot</tt>
* Hall Cameras:  [https://hallach-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall A], [https://hallbch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall B],  [https://hallcch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall C], [https://halldch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall D]
+
* Hall Cameras:  [https://www.jlab.org/~baltzell/ch-abcd.html 2x2], [https://hallach-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall A], [https://hallbch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall B],  [https://hallcch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall C], [https://halldch-cam.jlab.org/axis-cgi/mjpg/video.cgi?date=1&clock=1 Hall D]
  
 
| valign=top |
 
| valign=top |
===Manuals===
+
=== EPICS ===
*[https://wiki.jlab.org/clas12-run/images/c/c9/CedManual.pdf CED Manual]
+
* [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Hall B] (CUE Login)
*[https://wiki.jlab.org/clas12-run/images/f/fd/CLAS12Mon_documentation.pdf MON12 Manual]
+
* [https://epicsweb.jlab.org epicsweb]
*[https://github.com/JeffersonLab/RasterMon/wiki RasterMon Manual]
+
:&bull;  [https://epicsweb.jlab.org/wedm/screen?edl=/cs/opshome/edm/wall/Status_W_Accel.edl Accelerator Status]
*[https://wiki.jlab.org/clas12-run/images/a/ae/Online_shifts.pdf  off-line Manual]
+
:&bull;  [https://epicsweb.jlab.org/wave Strip Charts]
  
 
| valign=top |
 
| valign=top |
===Epics on the web===
+
=== Data Quality ===
* [https://hallbopi.jlab.org/webopi3.3/w Hall B WebOPI] (CUE Login)
+
* MON12 histograms: reference and most recent uploads
* [https://epicsweb.jlab.org Accelerator]
+
:&bull; '''New'''; 100 nA on CuSn target (S<sub>T</sub>=+1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4232231 run 19087]
* [https://epicsweb.jlab.org/wave/?start=2022-09-18+11%3A56%3A22&end=2022-09-21+12%3A01%3A22&myaDeployment=ops&myaLimit=100000&windowMinutes=4000&title=&fullscreen=false&layoutMode=3&viewerMode=2&pv=TGT%3APT12%3APolarization&pv=IGL1I00OD16_16&pv=B_DAQ%3AHEL%3A60m%3A29%3Apol&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisLabel=&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisMin=-0.025&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisMax=0.025&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisLog&B_DAQ%3AHEL%3A60m%3A29%3Aasycorrscaler=&TGT%3APT12%3APolarizationlabel=NMR+Target+Polarization&TGT%3APT12%3APolarizationcolor=%23ff0000&TGT%3APT12%3APolarizationyAxisLabel=&TGT%3APT12%3APolarizationyAxisMin=-0.9&TGT%3APT12%3APolarizationyAxisMax=0.9&TGT%3APT12%3APolarizationyAxisLog&TGT%3APT12%3APolarizationscaler=&IGL1I00OD16_16label=Half-Wave+Plate&IGL1I00OD16_16color=%23b2df8a&IGL1I00OD16_16yAxisLabel=&IGL1I00OD16_16yAxisMin=&IGL1I00OD16_16yAxisMax=&IGL1I00OD16_16yAxisLog&IGL1I00OD16_16scaler=&B_DAQ%3AHEL%3A60m%3A29%3Apollabel=Trigger+Target+Polarization&B_DAQ%3AHEL%3A60m%3A29%3Apolcolor=%230000ff&B_DAQ%3AHEL%3A60m%3A29%3ApolyAxisLabel=&B_DAQ%3AHEL%3A60m%3A29%3ApolyAxisMin=&B_DAQ%3AHEL%3A60m%3A29%3ApolyAxisMax=&B_DAQ%3AHEL%3A60m%3A29%3ApolyAxisLog&B_DAQ%3AHEL%3A60m%3A29%3Apolscaler= Polarization Strip Chart on the web]
+
::- Due to the beam current change and slight difference observed mainly in the forward tracking occupancy plots!
 
+
:&bull; '''Old'''; 95 nA on CuSn target (S<sub>T</sub>=+1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4223511 run 18875]
<!--* [https://epicsweb.jlab.org/wave/?start=2022-09-18+11%3A56%3A22&end=2022-09-21+12%3A01%3A22&myaDeployment=ops&myaLimit=100000&windowMinutes=1440&title=&fullscreen=false&layoutMode=3&viewerMode=2&pv=B_DAQ%3AHEL%3A60m%3A29%3Aasycorr&pv=TGT%3APT12%3APolarization&pv=IGL1I00OD16_16&B_DAQ%3AHEL%3A60m%3A29%3Aasycorrlabel=Trigger+Asymmetry&B_DAQ%3AHEL%3A60m%3A29%3Aasycorrcolor=%230000cc&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisLabel=&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisMin=-0.025&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisMax=0.025&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisLog&B_DAQ%3AHEL%3A60m%3A29%3Aasycorrscaler=&TGT%3APT12%3APolarizationlabel=NMR+Polarization&TGT%3APT12%3APolarizationcolor=%23ff0000&TGT%3APT12%3APolarizationyAxisLabel=&TGT%3APT12%3APolarizationyAxisMin=-0.9&TGT%3APT12%3APolarizationyAxisMax=0.9&TGT%3APT12%3APolarizationyAxisLog&TGT%3APT12%3APolarizationscaler=&IGL1I00OD16_16label=Half-Wave+Plate&IGL1I00OD16_16color=%23b2df8a&IGL1I00OD16_16yAxisLabel=&IGL1I00OD16_16yAxisMin=&IGL1I00OD16_16yAxisMax=&IGL1I00OD16_16yAxisLog&IGL1I00OD16_16scaler= Polarizatin/Asymmetry Strip Chart on the web]-->
+
::- Due to turning back some BMT Layers/strips after training and recovering them!
 
+
:&bull; '''New'''; 60 nA on LD2 target (S<sub>T</sub>=+1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4222938 run 18851]
| valign=top |
+
::- Due to turning back some BMT Layers/strips after training and recovering them!
===Live Monitoring Links===
+
:&bull; '''New'''; 50 nA on CxC target (S<sub>T</sub>=+1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4220609 run 18805]
*[https://clas12mon.jlab.org/rgc CLAS12 Monitoring Timelines]
+
::- Due to FTOF changes in some PMTs and sectors, see, e.g., https://logbooks.jlab.org/entry/4220567.
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge.html Live Charge Collected Plots for FTon '23]
+
:&bull; 60 nA on LD2 target (S<sub>T</sub>=+1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4219272 run 18767]
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge_r12.html Charge Collected Plots for FTon '22]
+
:&bull; 95 nA on CuSn target (S<sub>T</sub>=+1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4216247 run 18712] <!-- 4213795 (r18663) -->
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge_r3.html Charge Collected Plots for FToff '22]
+
:&bull; 50 nA on CxC target (S<sub>T</sub>=+1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4203079 run 18508] (''Outdated'')
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_target_illum.html Total Charge on Target Plot]
+
:&bull; 50 nA on LD2 targets (S<sub>T</sub>=+1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4198621 run 18428]
*[https://clasweb.jlab.org/hydra/HydraRun.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox!
+
:&bull; 130 nA on CuSn target (S<sub>T</sub>=-1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4196200 run 18376]
 
+
* [https://clasweb.jlab.org/clas12online/timelines/rg-d/RGD2023_progress_all.html Total Charge on Target Plot]
<!--
+
* [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox!
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress.html Live Luminosity Collected Plots]
+
* [https://github.com/JeffersonLab/caos/tree/main#readme clas12online]:
-->
+
:&bull; '''New'''; displaying real-time reconstructed vertices & various event topologies
 
|}
 
|}
  
<!--
 
{| {{TableStyle1}}
 
| valign=center |
 
[[File:RGM_monitoring_dec_21_charge.png|1100px]]
 
|}
 
-->
 
  
= Useful Links =
+
= Important Links =
<!--#######################################  USEFUL LINKS ### #############################################-->
+
<!--- = Miscellaneous =--#######################################  USEFUL LINKS ################################################-->
 
{| {{TableStyle1}}
 
{| {{TableStyle1}}
 
| valign=top |
 
| valign=top |
 
===Hall-B===
 
===Hall-B===
 
* [https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc Operation Safety Procedures]
 
* [https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc Operation Safety Procedures]
* [https://clasweb.jlab.org/wiki/index.php/Run_Group_C Run Group C Analysis Wiki]
+
* [https://clasweb.jlab.org/wiki/index.php/Run_Group_D Run Group D Analysis Wiki]
 
* [http://clasweb.jlab.org/rcdb RCDB]
 
* [http://clasweb.jlab.org/rcdb RCDB]
* [https://clas12mon.jlab.org/mon12/histograms/?reference=4130446 All monitoring histograms: reference, current, and 5 most recent runs]
+
* [https://clasweb.jlab.org/cgi-bin/ccdb/objects CCDB]
* [https://clas12mon.jlab.org/ CLAS12 mon page]
 
* '''[https://clasweb.jlab.org/wiki/index.php/RG-C_RC_and_Target_Expert_Volunteers Run Coordinators and Target Experts Instructions and List]'''
 
 
 
<!--
 
* [https://clas12mon.jlab.org/charge/ Accumulated Charge]
 
* [https://clas12mon.jlab.org/datasize/ Accumulated datasize]
 
* [https://docs.google.com/spreadsheets/d/1KazAyOTyajKfq6xMqFSQJBYTAEPN80TlgtkLOytvFUA/edit?usp=sharing Run Coordinator Schedule]
 
* [https://docs.google.com/spreadsheets/d/1WOXy15v5imrpeAVoLV9D-qU4dyjqf2VRKmhkqVtGBM4/edit?usp=sharing Target and Run Plan Summary]
 
* [https://docs.google.com/spreadsheets/d/1xKeXvBn_euvj17BU_hW6Zvrfq9bOgUILlinU_CR2YXQ/edit?usp=sharing Full Run Plan]
 
-->
 
  
 
| valign=top |
 
| valign=top |
Line 343: Line 322:
 
* [https://accweb.acc.jlab.org/btm/reports/physics-summary Beam Time Accounting Reports]
 
* [https://accweb.acc.jlab.org/btm/reports/physics-summary Beam Time Accounting Reports]
 
* [http://opsweb.acc.jlab.org/CSUEApps/PSSestamp/psslog.php PSS Elog]
 
* [http://opsweb.acc.jlab.org/CSUEApps/PSSestamp/psslog.php PSS Elog]
 +
* [http://opsweb.acc.jlab.org/internal/ops/ops_webpage/restrictions/ops_restrictions.html Operational Restrictions]
  
 
| valign=top |
 
| valign=top |
===ZOOM meetings===
+
===ZOOM Meetings===
 
* 07:45 [https://jlab-org.zoomgov.com/j/1611456010?pwd=d2RJWTJQRDM0ZkNaZ1dpTmtLWDAwQT09 RC/PD Morning Meeting]
 
* 07:45 [https://jlab-org.zoomgov.com/j/1611456010?pwd=d2RJWTJQRDM0ZkNaZ1dpTmtLWDAwQT09 RC/PD Morning Meeting]
 
* 08:00 [https://jlab-org.zoomgov.com/j/1601304841?pwd=Z1RIOVVUdkdXL2R2LzREZUNOUlh1dz09 MCC/OPS Morning and Wednesday 1:30 Meeting]
 
* 08:00 [https://jlab-org.zoomgov.com/j/1601304841?pwd=Z1RIOVVUdkdXL2R2LzREZUNOUlh1dz09 MCC/OPS Morning and Wednesday 1:30 Meeting]
* [https://logbooks.jlab.org/entry/4000274 See also this log entry]
+
* [https://logbooks.jlab.org/entry/4000274 See also this logbook entry]
* (Week-)Daily RC Meeting  
+
* Daily Hall B Run Coordinator Meeting:
** [https://jlab-org.zoomgov.com/j/1608674253?pwd=SFZyYmZLWXJieGtpV2dEdVRiUEJnUT09&from=addon Zoom Link]
+
** [https://jlab-org.zoomgov.com/j/1611984219?pwd=MnZMM0pDdzhlUnlOR2c3MnRFUlFqQT09 URL Link] (''including Passcode'')
** Meeting ID: 160 867 4253
+
** Meeting ID: 161 198 4219
** Passcode: 786506
+
** Passcode: see emails
** [https://clasweb.jlab.org/wiki/index.php/RGC_RC Meeting Schedule and Agendae]
+
* [https://logbooks.jlab.org/entry/4158818 Hall B Remote Shifts & Counting House]
 
 
 
|}
 
|}
  

Latest revision as of 13:39, 25 July 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.

Click to Edit solely this tab. P.S.: You must click on the top Edit, next to Read, followed by "Save changes" to force the current page to refresh.

Run Coordinator: Lamiaa El Fassi (757) 575-7540

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

RG/Analysis Coordinator (AC): Lamiaa El Fassi (630) 605-4259

Daily RC/OA Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1611984219; Passcode: RGD-RC23), except on Wednesdays, which is on ZOOM ONLY @ 15:30 due to the conflict with the 13:30 MCC Scheduling/Planning meeting.

Important Notes

Do NOT change FSD settings without approval from RC or beamline expert!

  • In case of medical or fire emergency, call 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 will call MCC to turn the beam OFF to 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 and the RC and JLab medical services immediately to arrange replacements.
  • Remote shift: If needed, worker shifts can be taken from off-site. Inform the PDL and RC. Also, make sure that you follow the instructions under the "Shift Worker" tab, as you need some lead time to set up!
  • Note to Shift Takers:
◊ Read the ESAD, COO, RSAD, and ERG documents found on the "Current RG-D Run Info" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.
◊ Read at least the previous 24 hours logbook entries to be aware of recent run details and changes;
◊ Arrive at least 10 minutes early for shift change;
◊ Refresh the runwiki page/tabs; look over it/them every shift:
- Follow the Shift Expert/Worker tab's instructions.
Do not spend more than 15-20 min trying to fix a problem. In case of any issue, contact the On-call Experts or the RC.
Review these important links:
- Recent Changes and Current Issues
- General How-to for beam restoration procedures and Møller runs.

Run Plan, Thursday, Dec. 14th - Friday, Dec. 15th, 2023

  • Continue CuSn data-taking as follows until 7 AM on Dec. 15th when the beam will be taken away for the RG-K setup:
- Target: CuSn
- Beam Blocker: IN
- Beam current: 100 nA +/- 4 nA on 2C21A
- Run duration: 100 M events
- DAQ configuration: PROD67
- Trigger file: rgd_out_v2.3_Q2_1.2.trg

P.S.: If the beam is widely fluctuating above 105 nA, constantly overshooting over 105 nA on 2C21A, please ask MCC to narrow down the fluctuation margin to keep it below 105 nA based on 2C21A reading. They could put the beam current monitor lock on 2C21A in case that may help with the wide fluctuation and/or adjust our laser phase as well as narrow down the slit width, see ELOG entries 4224300 and 4225220.

General Instructions

  • The main lights in the Hall (dome lights) and the Forward Carriage lights are being kept off because of light leaks affecting some of the detectors (especially ECAL sec 2 and 3). 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. The lights can be turned off without entering the Hall. See logbook entry: https://logbooks.jlab.org/entry/4204460
• Note that when the dome lights are switched off, they cannot be turned back on immediately because they require 10-15 min to cool down.
  • Beamline:
• Ignore the Faraday Cup beam current (see Current Issues).
• Do not run over 30 minutes above 90 nA with a 5-pass beam without the beam blocker IN . The beam blocker must be IN for long-running at high currents for 5-pass operations.
• 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:
◊ Please check with the beamline expert whether the SLM and FCup charge asymmetry (Q-Asym (%)) readings are set properly, as they will be out of range in case Eugene's script is not run by the experts after the HWP change. The absolute values should be less than 0.1%.
  • For beam tuning and Møller runs
• Make sure the SVT/MVT are set as follows: SVT: LV ON; HV OFF, and MVT: LV ON; HV ON in SAFE Mode.
- When turning MVT OFF, do not press "BMT HV OFF" from HV->Overview->Actions, but instead select BMT HV ON - Safe Voltage. The same applies to FMT select FMT HV ON - Safe Voltage.
- When turning MVT ON: go to HV->Overview->Actions, and select BMT (/FMT) "HV ON - Full Voltage".
- DO NOT start runs in SAFE Mode for Production/Calibration/Various-Studies.
• Turn DC HV off only for beam tuning; if no beam is available or when the beam is stable, keep them on even if you are not taking data.
  • 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 (757-575-7540).
• Check in with the shift personnel before entering the hall.

DAQ Operation & related General Instructions

  • (New) STANDARD end and start of the run:
- "End run"
- "Abort"
- "Download"
- "Prestart"
- "Go"
  • If any ROC crashes, find out which one (look at the ROC Busies GUI or ROCS tabs in the DAQ runcontrol), and end the ongoing run, which might fail to end properly, and that is OK. You SHOULD do "Cancel" and "Reset" in the DAQ Run Control before issuing a roc_reboot command ON JUST THAT ROC and continuing with the DAQ Restart chain from "Configure". Test with ping ONLY instead of ssh to check whether the ROC is backed up.
When pinging a ROC, e.g., "ping mvt1", stop it with Ctrl+C after a couple of printouts showing different latency times.
  • Restart DAQ from Scratch when changing configuration or trigger files, or when the run did not end correctly, or when ROC(s) is(are) rebooted, or when RICH is Fastly/Fully recovered, as follows:
- "Cancel", "Reset"
- "Needed operations: change configuration or trigger files, or a run did not end correctly, or a ROC crash or RICH is Fastly/Fully recovered";
- "Configure"
- "Download"
- "Prestart"
- "Go"
  • Configuration is PROD66/67 (or PROD66_PIN for fast reconstruction of some calibration/reference runs from the cache disk).
As of 11/25/23, whenever there is an issue with the RICH alarms that can't be resolved within 10 to 15 minutes, please contact the RC (/AC) and the RICH experts to discuss the issue. Meanwhile, we may switch the DAQ configuration to PROD67_noRICH until further notice; see the logbook entry #: 4226898.
  • In case of DAQ Disk space alarm, call the DAQ expert.
  • Trigger files:
- Inbending production: rgd_inb_v1.0.trg
- Outbending production: rgd_out_v2.1_Q2_1.2.trg or rgd_out_v2.3_Q2_1.2.trg with low-Q2 suppression
  • During "Configure", observe the ROC terminals to see whether any ROC has error messages.
  • Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # 4215299 to avoid unnecessary reboot since the printout in the ROC terminal won't change. If they get disconnected, the message will appear in the run control itself!
  • In case of DAQ livetime "0" alarm, RESTART DAQ from Scratch;
• Note that you also get a DAQ livetime alarm at the start of a run; that is OK and can be simply acknowledged.
  • Unless a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run for a RICH recovery. Instead, do this in between runs.
  • The shifter MUST check and reset monitoring histograms at least once every 30-60 minutes to ensure no significant detector problems. Sometimes, this is the only way to know that a specific ROC needs to be rebooted.
  • Pop-up window: Enter the beam current and the type of run (e.g., Production and HWP state, IN or OUT) in the "Comment" field.
  • After each step of a DAQ RESTART, ensure it is completed in the Run Control message window. Also, during "Configure", look for error messages in the ROC terminals.
• Contact the DAQ expert if you have any questions or doubts about how to proceed.
  • At the start and end of every run, check that the data filled in the Run Condition Data Base (RCDB) is correct, especially the manually filled fields.

Reference Values

FSD Thresholds from RG-D

  • Upstream: 2 kHz
  • Midstream: 2 kHz
  • Downstream: 100 kHz
  • BOM: 50 kHz
  • 5 ms dwell time

Harp Scan References from RG-D

  • 2H01 [3]; x= -1.4 mm; y= 0.0 mm
  • Tagger (2C24A) [4]: x= -2.0 mm; y= +0.6 mm
  • 2C21A [5]: x= -0.4 mm; y= +0.6 mm (less important; values form RG-C)

IA for Q Asymmetry


Responsibilities

  • The RC duties are detailed in the COO.
  • Check and contact, if needed, upcoming shifts about their training or site access status.
  • The training requirements for the shift are:
- ES&H Orientation (SAF 100);
- Radiation Worker Training (SAF 801);
- Oxygen Deficiency Hazard Training (SAF 103);
- Hall B Safety Awareness Walk-Through (SAF111)
  • Remote shifts are listed here.
  • Backup shifters are listed here.

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.
• See the ZOOM connection info under Important Links tab.
  • Update the run plan in the Short Term Schedule tab in coordination with the run group coordinator and communicate it to the shift crew.
  • Log the RC summary in the HBLOG.
  • Send a daily invitation for the RC meeting to hallb, clas_members, and rgd_ana mailing list.
  • Run the RC meetings at 1 PM in CH Room 200C and on ZOOM, except on Wednesdays.
  • On Wednesdays, the RC meeting is on ZOOM ONLY @ 15:30 due to the conflict with the 13:30 MCC meeting and the unavailability of the CH room afterwards.
‡ To connect to Zoom in CH Room 200C, follow these steps:
◊ 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 near the microphone in the middle of the conference table. Once it rings, answer the call, and you will be prompted to join the meeting.
◊ The room has a camera, so you may turn it on, if you wish, in the ZOOM browser interface.

Weekly

‡ The report summarizes the data-taking status concerning the available beam used (ABU), any beam losses (BANU), CW on target (ABU+ABNU), etc., from 7 AM past Wed. through 7 AM the Wednesday the report is due, in addition to any standing and critical issues, plans for next week, and general comments/requests, if any.
‡ Our beam time accounting info can be retrieved either from:
◊ OPS logbook entries with tag 'Beam Accounting': Timesheet Summaries;
Beam Time Manager; Physics Time Accounting.
‡ Refer to the RC Timesheet to calculate the percentage of scheduled experiment hours to date.
‡ The total experiment data collected to date could be retrieved from the up-to-date "Accumulated Charge" depicted on the "Total Charge on Target Plot" in the Monitoring tab.
‡ A detailed plan of the target configuration change will be generated as soon as the run starts; however, an overview of it is summarized in slide 6 of this RG-D Overview.
  • Attend the Hall B meeting on Mondays at 9 AM and present your summary slides that should be sent beforehand to the Hall B leader, Patrick Achenbach, after checking them; please, with the Run Group Coordinator Lamiaa El Fassi.


Tasks

  • Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.
• If it's your first shift or a shift after a long pause, please come at least 4 hours before your shift (or even better, come a day earlier) to shadow the previous shifter and 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:
• 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.
  • Check for and read any comments to log-book entries made 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 you have any other questions or uncertainties about what to do, call the RC.
  • New RICH recovery protocol:
• See https://logbooks.jlab.org/entry/4201728 for important details.
• In case of a RICH issue a screen shot of both scalers and temperatures should be logged in the RICH logbook before running the appropriate recovery.
Issues can be seen from missing tiles in the scaler and temperature GUIs or the occupancy as seen in MON12. Do not stop an ongoing run, but do the fast recovery between runs.
• If the issue is seen in the scaler but not in the temperature GUI, then you should do a full recovery; see https://logbooks.jlab.org/entry/4214184. This might preempt the daily full recovery.
Daily full RICH recovery remains part of the protocol, preferably done during the daytime and only between runs; do not stop an ongoing run. State in your shift summary that you did the recovery (or why you did not).
Avoid unnecessary recoveries, see https://logbooks.jlab.org/entry/4208477. The RICH overview GUI shows how many seconds have passed since the last full recovery. Also, there is a minor alarm when 24 hours have passed since the last full recovery. Acknowledge the alarm and wait for the end of the run before running the recovery.
• Note that you have to Restart DAQ from Scratch; see DAQ Operation & related General Instructions under Short Term Schedule, after any RICH recovery.
◊ In case of getting a ROC error during the recovery, it's advised to "roc_reboot rich4" in the DAQ VNC terminal then "ping rich4" instead of "ssh rich4" to check whether it's initialized.
- When pinging a ROC, e.g., "ping rich4", stop it with Ctrl+C after a couple of printouts showing different latency times.
If the beam is ON and a RICH recovery is taking more than 5 min, please call the RICH expert, preferably the secondary number before the primary.
  • For any RICH problems overnight or on weekends/holidays, please call the RICH expert, preferably the secondary number before the primary, along with the RC to discuss and fix the issue!


  • 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:
◊ 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 alarm NActiveCrates, status also reported 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;
◊ Start a run by Restarting DAQ from Scratch; see DAQ Operation & related General Instructions under Short Term Schedule.
If the beam is ON, and a reboot process takes more than 5 min, please call the DAQ and/or SVT/MVT/MM expert.


• Accelerator beam time:
◊ ABU: acceptable beam used,
◊ BANU: beam acceptable but not used (should be reflected in our PCC or UED);
- Exception: BANU due to beam tuning with harp scans or Moller runs might be included in BNA.
◊ BNA: beam not acceptable (e.g., tuning, drifting, not focused);
◊ ACC: Accelerator configuration change (e.g., pass change or Maintenance/Beam Studies recovery);
◊ OFF: Accelerator is down.
• Experiment beam time (do change these values):
◊ ER: Experiment ready (should be 1 hour - PCC - UED)
◊ PCC: Planned configuration change (beam tuning with harp scans or Moller runs, target change, DAQ; e.g., stopping/starting runs, tests, etc.)
◊ UED: Unplanned experiment down (hardware failure, DAQ crashes, including sudden livetime drop to "zero" or low trigger rates, or experiment/hall problems)
- Exception: BANU, due to time spent on drifting beam positions after beam down, may be counted as ER on our side.
• 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 here, https://ace.jlab.org/btm/reports/activity-audit, whether you saved correctly!
◊ 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 timesheet up to 48 hours after completion.

Tasks

  • Come to your shift in time for the shift change, 10-15 minutes before the start of your shift;
• If it's your first shift or a shift after a long pause, please come at least 4 hours before your shift (or even better, come a day earlier) to shadow the previous shifter and familiarize yourself with all shift duties and technicalities of the ongoing experiment.
  • Discuss an issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary and the start/end of run Comment field in the DAQ pop-up window.

Frequently

  • Reset and check MON12 histograms frequently, preferably each 1/2h, during a run:
• Note that some plots have radio buttons at the bottom to choose the sector, so you should cycle through and check all sectors.

Once per run

  • Submit EPICS screenshots to the HBRUN logbook with beam ON
◊ Beamline overview, in VNC or Web Browser
◊ CLAS12 trigger rates and DAQ status
  • Upload MON12 monitoring plots to the logbook with sufficient statistics:
◊ Afterwards, compare them to the reference and recent uploads; see the top-right link at the Monitoring tab.
  • Submit Beam current and position strip charts to the logbook at the end of the run
◊ If they are not up already: (CS-Studio → Beamline → Strip Charts);
◊ Choose the 'time-span width' to be compatible with the run duration.
◊ To make the logbook entry using the clascss:
- On the bottom chart, click on parameter "B_DAQ:EB:datarate" so that its range is seen on the y-axis and take the first snapshot;
- On the same Bottom (fourth) chart, click on the parameter "B_DAQ:EB:eventrate", take the second snapshot, then submit!

Once per shift

• During production or if the beam is down for your entire shift, 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 you made during production.
  • Upload by the end of the shift while data is being collected clas12online tabs plots to the HBLOG logbook with sufficient statistics;
◊ Please refresh the clas12online program at the beginning of your shift in case the previous shifter does not do it after uploading the snapshots. Also, do that while the DAQ is running!
◊ Note that the program must be restarted after each DAQ crash!

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!

◊ The passcode is required and contained in this log entry
◊ Remind the expert in the counting-house to restart their ZOOM, if necessary
  • Remote VNC connection instructions: https://logbooks.jlab.org/entry/3906039
  • If you mistyped (username, pincode, passcode,...) a string of numbers will appear with text asking you to respond to this challenge. Back out with ctrl_c to get another try! After N+1 mistypes, you will be locked out. For several hours after that, you will not even be able to get to the public JLab webpages.
◊ All necessary applications should be available from the desktop menu (left/right click on the desktop)
◊ EPICS GUIs should be accessed ONLY via the desktop menu or by running clascss-remote.
◊ Some charts are also accessible via web browser: Upstream/Midstream Halo Counters, Downstream Halo Counters, Beam Currents, BPM Positions


Webcams

• To reboot it, run beam-viewer-reboot

EPICS

Accelerator Status
Strip Charts

Data Quality

  • MON12 histograms: reference and most recent uploads
New; 100 nA on CuSn target (ST=+1.0): run 19087
- Due to the beam current change and slight difference observed mainly in the forward tracking occupancy plots!
Old; 95 nA on CuSn target (ST=+1.0): run 18875
- Due to turning back some BMT Layers/strips after training and recovering them!
New; 60 nA on LD2 target (ST=+1.0): run 18851
- Due to turning back some BMT Layers/strips after training and recovering them!
New; 50 nA on CxC target (ST=+1.0): run 18805
- Due to FTOF changes in some PMTs and sectors, see, e.g., https://logbooks.jlab.org/entry/4220567.
• 60 nA on LD2 target (ST=+1.0): run 18767
• 95 nA on CuSn target (ST=+1.0): run 18712
• 50 nA on CxC target (ST=+1.0): run 18508 (Outdated)
• 50 nA on LD2 targets (ST=+1.0): run 18428
• 130 nA on CuSn target (ST=-1.0): run 18376
New; displaying real-time reconstructed vertices & various event topologies



Clas12design.png