Difference between revisions of "Run Group C"
Jump to navigation
Jump to search
(211 intermediate revisions by 14 users not shown) | |||
Line 12: | Line 12: | ||
===[https://bta Beam Time Accounting]=== | ===[https://bta Beam Time Accounting]=== | ||
* See guidance at '''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf BTA User Guide]'''. | * See guidance at '''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf BTA User Guide]'''. | ||
+ | ===[https://www.jlab.org/Hall-B/run-web/rgc/ESAD_HallB-CLAS12_rgC.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rgc/COO_HallB-CLAS12_RGC.pdf COO], [https://www.jlab.org/Hall-B/run-web/rgc/RSAD_HallB-CLAS12_rgC.pdf RSAD], [https://www.jlab.org/div_dept/train/SAF111/Hall%20B%20worker%20Safety%20Training%20%28SAF111%29%20%2008%2001-12-1.pdf ERG] === | ||
+ | ===[https://clasweb.jlab.org/wiki/images/e/ef/Longitudiannly_polarized_target_OSP.pdf Longitudinally Polarized Target OSP]=== | ||
+ | ===[https://www.jlab.org/Hall-B/run-web/rgc/RICH_OSP_131114.pdf RICH OSP]=== | ||
| valign=top | | | valign=top | | ||
Line 66: | Line 69: | ||
<!--- 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 #############################################--> | ||
− | = | + | <!-- === <font color=red size=6> '''ALL shifts are presently canceled until Monday, January 30, 8 AM. </font> ''' === --> |
+ | |||
=== <font color=blue size=4> ''' CLAS12 Run Group C </font> ''' === | === <font color=blue size=4> ''' CLAS12 Run Group C </font> ''' === | ||
− | '''Run Coordinator: | + | '''Run Coordinator: Mohammad Hattawy''' (9-)757 575-7540 |
''' PDL: Eugene Pasyuk ''' (9-)757 876-1789 , x6020 office | ''' PDL: Eugene Pasyuk ''' (9-)757 876-1789 , x6020 office | ||
Line 87: | Line 91: | ||
''' [https://userweb.jlab.org/~kuhn/RGC/RunPlan.pdf Longterm Run Plan] ''' | ''' [https://userweb.jlab.org/~kuhn/RGC/RunPlan.pdf Longterm Run Plan] ''' | ||
− | ''' [https://userweb.jlab.org/~kuhn/RGC/ | + | ''' [https://userweb.jlab.org/~kuhn/RGC/RunPlan_FTon2.pdf Medium-Term Run Plan] (FTon Portion Part 2) ''' |
== '''IMPORTANT SHIFT NOTES'''== | == '''IMPORTANT SHIFT NOTES'''== | ||
+ | |||
* '''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' | * '''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' | ||
* 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. | * 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. | ||
+ | * '''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 "Worker Shift" Tab - you need some lead time to set up! | ||
− | + | Note to shifts, please: | |
− | * | + | * read the '''logbook''', 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''' | |
+ | ** find latest pitfalls and known issues under '''GENERAL INFORMATION''' | ||
+ | * '''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 Wednesday, March 15th, to Monday March 20th, 2023''' == | |
− | * Current: | + | * Current: 4 nA |
− | * Run duration: 100M events or 4 hours, whichever comes first | + | * Run duration: 100M events or 4 hours, whichever comes first. |
* Note, BOM is not installed for this experiment, so it does not matter whether it appears masked in FSD or not. | * Note, BOM is not installed for this experiment, so it does not matter whether it appears masked in FSD or not. | ||
Line 109: | Line 119: | ||
* '''The Faraday Cup power limit''' for the continuous operation was lifted up to 1 kW. For the remainder of the RG-C the beam blocker should not be used https://logbooks.jlab.org/entry/4047791 | * '''The Faraday Cup power limit''' for the continuous operation was lifted up to 1 kW. For the remainder of the RG-C the beam blocker should not be used https://logbooks.jlab.org/entry/4047791 | ||
− | * ''' | + | * '''Conditions for raster operation:''' |
** IF there is any ammonia sample (NH3 and ND3) in the target, the raster '''MUST''' be operating at all times. The Raster FSD must be UNMASKED. Orbit locks MUST be OFF (except for brief moments to restore beam position). | ** IF there is any ammonia sample (NH3 and ND3) in the target, the raster '''MUST''' be operating at all times. The Raster FSD must be UNMASKED. Orbit locks MUST be OFF (except for brief moments to restore beam position). | ||
** For beam tuning or other non-rastered beam, the '''Raster FSD''' must be MASKED. | ** For beam tuning or other non-rastered beam, the '''Raster FSD''' must be MASKED. | ||
− | ** 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 | + | ** 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.''' |
** '''Changing raster offset''': ask MCC to NOT correct whatever happens on 2H01. Note new 2H01 values and inform MCC of the new 2H01 x and y values - then they can keep the beam at those positions. | ** '''Changing raster offset''': ask MCC to NOT correct whatever happens on 2H01. Note new 2H01 values and inform MCC of the new 2H01 x and y values - then they can keep the beam at those positions. | ||
− | * Experiment setup is " | + | * Experiment setup is "FTon" |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | * | + | * If HWP is changed, start a new run |
− | |||
+ | === PLAN for March 15-20, 2023 === | ||
+ | Note: an hour before changing the HWP, call Bill Henry (from Hall A) at 215-908-2245. He offered his help in optimizing the beam charge asymmetries when changing the HWP. He will stop by the counting house and run his code, which will take a minute. We will do the HWP changes during the day shifts. | ||
− | + | *Wednesday, March 15th: Beam study downtime starts at 8:00 AM. Beam is expected to be back by 15:00 PM. If they beam shows up before 22:00 PM, we will need to take a Moller run. Then, start taking data on ND3(+) (torus outbending, 4nA beam current, HWP IN). | |
+ | *Thursday, March 16th: Data taking on ND3 (+) (torus outbending, 4nA, HWP out) | ||
+ | * Friday, March 17th: anneal the target and flip the polarization to negative. Will take about 3 hours starting around 9AM. Then, take data on ND3 (torus outbending, 4nA, HWP out) | ||
+ | * Saturday, March 18th: Continue taking data on ND3(-) (torus outbending, 4nA, HWP IN) | ||
+ | * Sunday, March 19th: Will change the target to C sometime in the day shift and start taking data. Will go to restricted access and will organize this between RadCon and Target Experts. | ||
+ | * Till Monday, March 20th, 07:00 AM: Continue taking data till the beam goes away. | ||
− | * | + | * When the beam goes away: |
− | + | # Turn all HV OFF except SVT and BMT. For FT we turn HV OFF, but keep the chiller and LV ON, Raffaella will do some LED calibrations. | |
− | + | # Solenoid will remain ON for the target group to do NMR studies. | |
− | + | # The torus should be ramped down. Morgan or Denny can do it if they are around at that time, or call Eugene and he do it. | |
− | + | # The hall should go to controlled access awaiting for radcon to come and do a full survey for restricted access. | |
− | + | NOTES: | |
− | + | * Watch the beam positions (and thus the midstream halo counters) closely and ask MCC to adjust the positions if they are (on average) >=0.1mm off. | |
− | + | * Remember, the hall will only be dropped in controlled mode once someone goes downstairs and enters the hall. You/RadCon should do that right away after calling MCC. | |
− | * | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | * | ||
− | |||
== <font color=blue> DAQ configuration </font> == | == <font color=blue> DAQ configuration </font> == | ||
− | * Configuration is currently <tt> | + | * Configuration is currently <tt>'''PROD66'''</tt>/<tt>PROD66_PIN</tt>, trigger file <tt>'''rgc_300MeV_v1.4_no_DC.trg'''</tt> |
* '''NOTE''': UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to do a RICH recovery - instead do this in between runs. | * '''NOTE''': UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to do a RICH recovery - instead do this in between runs. | ||
− | * '''NOTE''': BOTH the shift expert AND the shift worker MUST check and reset monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems.'''Watch the raster pattern!''' | + | * '''NOTE''': BOTH the shift expert AND the shift worker MUST check and reset monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems. Sometimes it is the only way to know that a roc needs to be rebooted. '''Watch the raster pattern!''' |
* At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font>: | * At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font>: | ||
** "end run". | ** "end run". | ||
Line 180: | Line 165: | ||
* After each step, make sure it is completed in the Run Control message window. If a ROC has crashed, find which one it is, issue a roc_reboot command ON JUST THAT ROC and try again. Contact the DAQ expert if there are any questions. | * After each step, make sure it is completed in the Run Control message window. If a ROC has crashed, find which one it is, issue a roc_reboot command ON JUST THAT ROC and try again. Contact the DAQ expert if there are any questions. | ||
− | == <font color=blue> References and Standards </font>== | + | == <font color=blue> References and Standards </font>== |
=== 5-pass (10.55 GeV) Running conditions === | === 5-pass (10.55 GeV) Running conditions === | ||
* Torus at 100% current, inbending electrons. Setpoint = +3770 A (Readback = +3766 A) | * Torus at 100% current, inbending electrons. Setpoint = +3770 A (Readback = +3766 A) | ||
+ | <!-- | ||
* Solenoid setpoint inverted (Oct 14 2022) -2417.5 A | * Solenoid setpoint inverted (Oct 14 2022) -2417.5 A | ||
** with using shim coils of polarized target on (Oct 26, 2022) -2418.50 A | ** with using shim coils of polarized target on (Oct 26, 2022) -2418.50 A | ||
* Solenoid setpoint +2417.5 A (normal conditions RGA-M) | * Solenoid setpoint +2417.5 A (normal conditions RGA-M) | ||
+ | i--> | ||
+ | * Solenoid set-point of 2416.4 A results in the read back 2419.23 A and exactly 5.00 T field on center | ||
− | + | '''Raster settings (current as of February 9, 2023)''' | |
− | + | * x: Vpp = 2.7 V, offset = 0.0 | |
− | '''Raster settings''' | + | * y: Vpp = 2.05 V, offset = 0.50 V |
− | * x: Vpp = | ||
− | * y: Vpp = | ||
* Fundamental Period = 2 s | * Fundamental Period = 2 s | ||
* The correct raster calibration constants should be automatically loaded by rastermon - if not, enter them through "Config" by hand: | * The correct raster calibration constants should be automatically loaded by rastermon - if not, enter them through "Config" by hand: | ||
Line 198: | Line 184: | ||
* f(y) = -0.0115*y + 24.4 | * f(y) = -0.0115*y + 24.4 | ||
− | '''Nominal Beam Positions''' | + | '''Nominal Beam Positions (current as of February 9, 2023) ''' |
*2C21A, X = -0.4 mm, Y = +0.6 mm | *2C21A, X = -0.4 mm, Y = +0.6 mm | ||
*2C24A, X = -2.0 mm, Y = +0.6 mm | *2C24A, X = -2.0 mm, Y = +0.6 mm | ||
− | *2H01, X = -1. | + | <!-- *2H01, X = -1.8 mm, Y = +0.9 mm --> |
+ | *2H01, X = -1.0 mm, Y = +0.9 mm | ||
* Orbit lock on 2C24 and 2H01 ONLY if raster is OFF, otherwise orbit lock on 2C21 and 2C24 (note: this appears as "stopped" on the beam line GUI). | * Orbit lock on 2C24 and 2H01 ONLY if raster is OFF, otherwise orbit lock on 2C21 and 2C24 (note: this appears as "stopped" on the beam line GUI). | ||
Line 215: | Line 202: | ||
* Harp Scans for Beam on Faraday Cup, 2H01 [https://logbooks.jlab.org/entry/3963256], '' more recent scan (3 Sept 2022): '' [https://logbooks.jlab.org/entry/4037457] | * Harp Scans for Beam on Faraday Cup, 2H01 [https://logbooks.jlab.org/entry/3963256], '' more recent scan (3 Sept 2022): '' [https://logbooks.jlab.org/entry/4037457] | ||
− | * Harp Scans for Beam on 2C21 [https://logbooks.jlab.org/entry/4021281], '' more recent scan (3 Sept 2022):'' [https://logbooks.jlab.org/entry/4037438] | + | * Harp Scans for Beam on 2C21 [https://logbooks.jlab.org/entry/4021281], '' more recent scan (3 Sept 2022):'' [https://logbooks.jlab.org/entry/4037438] , '' even more recent scan (1 Feb 2023):'' [https://logbooks.jlab.org/entry/4122116] |
− | * Harp Scan on Tagger Dump (3 Sep 2022) [https://logbooks.jlab.org/entry/4037440] | + | * Harp Scan on Tagger Dump (3 Sep 2022) [https://logbooks.jlab.org/entry/4037440], ''more recent scan (1 Feb 2023):'' [https://logbooks.jlab.org/entry/4122122] |
− | * RasterMon (20 Oct 2022) [https://logbooks.jlab.org/entry/4064143] | + | * RasterMon (20 Oct 2022) [https://logbooks.jlab.org/entry/4064143], ''more recent raster (2 Feb 2023):'' [https://logbooks.jlab.org/entry/4122766] |
* Monitoring Histograms | * Monitoring Histograms | ||
** run 17240, DAY Fr, 10/21/2022, ND3 (ECAL good) [https://logbooks.jlab.org/entry/4065165 https://logbooks.jlab.org/entry/4065165] | ** run 17240, DAY Fr, 10/21/2022, ND3 (ECAL good) [https://logbooks.jlab.org/entry/4065165 https://logbooks.jlab.org/entry/4065165] | ||
** run 17348, DAY We, 11/02/2022, CH2 [https://logbooks.jlab.org/entry/4075177 https://logbooks.jlab.org/entry/4075177] | ** run 17348, DAY We, 11/02/2022, CH2 [https://logbooks.jlab.org/entry/4075177 https://logbooks.jlab.org/entry/4075177] | ||
** run 17363, OWL Sa, 11/05/2022, NH3 [https://logbooks.jlab.org/entry/4076956 https://logbooks.jlab.org/entry/4076956] | ** run 17363, OWL Sa, 11/05/2022, NH3 [https://logbooks.jlab.org/entry/4076956 https://logbooks.jlab.org/entry/4076956] | ||
+ | ** run 17492, DAY Th, 02/02/2023, ND3 (post-solenoid hiatus) [https://logbooks.jlab.org/entry/4122528 https://logbooks.jlab.org/entry/4122528] | ||
+ | ** run 17542, EVE Th, 02/09/2023, ND3 [https://logbooks.jlab.org/entry/4127691 https://logbooks.jlab.org/entry/4127691] | ||
+ | ** run 17547, DAY Sa, 02/11/2023, ND3 [https://logbooks.jlab.org/entry/4128938 https://logbooks.jlab.org/entry/4128938] | ||
+ | ** run 17562, DAY Mo, 02/13/2023, ND3 [https://logbooks.jlab.org/entry/4130446 https://logbooks.jlab.org/entry/4130446] | ||
'''Counter rates''' | '''Counter rates''' | ||
Line 227: | Line 218: | ||
* The Midstream ones should read 0-20 Hz or so. | * The Midstream ones should read 0-20 Hz or so. | ||
* Greatly increased rates may indicate bad beam tune or bleed-through from other Halls. | * Greatly increased rates may indicate bad beam tune or bleed-through from other Halls. | ||
+ | |||
+ | = GENERAL INFORMATION = | ||
+ | <!--####################################### GENERAL INFORMATION ########################################--> | ||
+ | |||
+ | '''see below for Known Detector Issues''' | ||
+ | |||
+ | == General Information == | ||
+ | |||
+ | * To open CS Studio interface, type "clascss" in some terminal. | ||
+ | |||
+ | * '''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.''' | ||
+ | |||
+ | * '''BMT''': | ||
+ | ** '''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. | ||
+ | |||
+ | * '''DAQ''': | ||
+ | ** rastermon should be using ET on clondaq6 | ||
+ | *** this means startup of rastermon via command line: rastermon --et --host clondaq6 | ||
+ | ** 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. | ||
+ | |||
+ | * '''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. | ||
+ | |||
+ | * '''Change of running conditions''' | ||
+ | ** Check that the trigger alarms (on rate/nA) are set appropriately and RC changes them as needed. | ||
+ | ** 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. | ||
+ | ** Do not change running conditions while a run is ongoing. This includes changing target polarization or HWP, etc. | ||
+ | |||
+ | == Known Issues == | ||
+ | FTT alarms - can be ignored (we do not have the FTT installed) | ||
+ | |||
+ | Fr 11 Nov 2022 | ||
+ | ECAL PMT_SEC2_WO8 HV is disabled | ||
+ | https://logbooks.jlab.org/entry/4080950 | ||
+ | |||
+ | Follow-up Re: RICH tile 21 in sector 1 is dead. Working without one tile out of 276 for a moment | ||
+ | https://logbooks.jlab.org/entry/4079453 | ||
+ | |||
+ | Run #17396: RICH lost three scalars | ||
+ | https://logbooks.jlab.org/entry/4079190 | ||
+ | |||
+ | Tuesday, February 7, 2023: | ||
+ | BMT Sector 2 Layer 5 is broken (HV set to 200 V) | ||
= Shift Expert = | = Shift Expert = | ||
<!--####################################### Shift Expert ################################################--> | <!--####################################### Shift Expert ################################################--> | ||
− | |||
− | |||
== Shift expert tasks == | == Shift expert tasks == | ||
* Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift. | * 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 | * 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. | * 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 | * 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 | ||
+ | * Both, you and the shift worker should '''reset & check spectra frequently''' | ||
* '''Polarized target''': | * '''Polarized target''': | ||
Line 248: | Line 294: | ||
** '''NMR running''' (''ONLY WHILE ACTUALLY RUNNING ON NH3 AND ND3 targets!'') | ** '''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 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. | ||
+ | *** If the NMR display is frozen or disappears, here are the steps to follow: | ||
+ | **** Open a new terminal window on the bottom right-most screen. | ||
+ | **** Type "ssh clasrun@clonsl1" | ||
+ | **** Type "nmr-vnc” | ||
+ | **** Click "Run" under "NMR Controls" - the window should now be updating (blue bar moving) | ||
*** 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. | *** 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). | ** '''Alarms''' from System RG-C Polarized Target (alarm handler). | ||
Line 274: | Line 325: | ||
(remote) shift worker: see dedicated [https://wiki.jlab.org/clas12-run/index.php/Run_Group_M#tab=Remote_Shifts Worker Shift] tab above. | (remote) shift worker: see dedicated [https://wiki.jlab.org/clas12-run/index.php/Run_Group_M#tab=Remote_Shifts Worker Shift] tab above. | ||
− | + | = Worker Shift = | |
+ | <!--####################################### Worker Shift ################################################--> | ||
+ | == Shift Worker Tasks == | ||
− | + | * Check the information in the '''Short Term Schedule''' and '''GENERAL INFORMATION''', for every shift | |
− | |||
− | * Check the information in the '''Short Term Schedule''', for every shift | ||
* Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift. | * Come to your shift in time for the '''shift change''', 10-15 minutes before the start of your shift. | ||
* Use the new '''HBRUN logbook''' for automated and run-specific entries and screenshots, see https://logbooks.jlab.org/entry/4048698 | * Use the new '''HBRUN logbook''' for automated and run-specific entries and screenshots, see https://logbooks.jlab.org/entry/4048698 | ||
− | |||
'''Make the following log entries ONCE per run''' | '''Make the following log entries ONCE per run''' | ||
Line 289: | Line 339: | ||
** CLAS12 Trigger rates and DAQ status | ** CLAS12 Trigger rates and DAQ status | ||
** RGC Polarized Target GUI - under Beamline on CS-Studio | ** 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''' | * '''Upload monitoring plots to logbook''' | ||
Line 310: | Line 361: | ||
** 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). | ** 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 | + | * '''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) | ** 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" | |
− | ** Helicity Trigger Asymmetry strip-chart (CS-Studio -> Helicity-Latched Trigger GUI Screen -> Menu -> myaPlot | + | *** [https://logbooks.jlab.org/entry/4123228 Example] |
− | *** | ||
*** '''Choose reasonable y / x axis ranges:''' R-click on the axis -> Modify (axis-name) Axis | *** '''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 | + | *** 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. | + | *** 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] | * 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] | ||
Line 363: | Line 412: | ||
===Live Monitoring Links=== | ===Live Monitoring Links=== | ||
*[https://clas12mon.jlab.org/rgc CLAS12 Monitoring Timelines] | *[https://clas12mon.jlab.org/rgc CLAS12 Monitoring Timelines] | ||
− | *[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge.html Live Charge Collected Plots for | + | *[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge.html Live Charge Collected Plots for FTon '23] |
− | *[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge_r12.html | + | *[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge_r12.html Charge Collected Plots for FTon '22] |
+ | *[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge_r3.html Charge Collected Plots for FToff '22] | ||
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_target_illum.html Total Charge on Target Plot] | *[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_target_illum.html Total Charge on Target Plot] | ||
+ | *[https://clasweb.jlab.org/hydra/HydraRun.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox! | ||
<!-- | <!-- | ||
Line 387: | Line 438: | ||
* [https://clasweb.jlab.org/wiki/index.php/Run_Group_C Run Group C Analysis Wiki] | * [https://clasweb.jlab.org/wiki/index.php/Run_Group_C Run Group C Analysis Wiki] | ||
* [http://clasweb.jlab.org/rcdb RCDB] | * [http://clasweb.jlab.org/rcdb RCDB] | ||
− | * [https://clas12mon.jlab.org/mon12/histograms/?reference= | + | * [https://clas12mon.jlab.org/mon12/histograms/?reference=4130409 All monitoring histograms: reference, current, and 5 most recent runs] |
* [https://clas12mon.jlab.org/ CLAS12 mon page] | * [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://clasweb.jlab.org/wiki/index.php/RG-C_RC_and_Target_Expert_Volunteers Run Coordinators and Target Experts Instructions and List]''' | ||
Line 412: | Line 463: | ||
* 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 log entry] | ||
− | * | + | * (Week-)Daily RC Meeting |
** [https://jlab-org.zoomgov.com/j/1608674253?pwd=SFZyYmZLWXJieGtpV2dEdVRiUEJnUT09&from=addon Zoom Link] | ** [https://jlab-org.zoomgov.com/j/1608674253?pwd=SFZyYmZLWXJieGtpV2dEdVRiUEJnUT09&from=addon Zoom Link] | ||
** Meeting ID: 160 867 4253 | ** Meeting ID: 160 867 4253 | ||
** Passcode: 786506 | ** Passcode: 786506 | ||
− | ** [https://clasweb.jlab.org/wiki/index.php/RGC_RC Meeting Agendae] | + | ** [https://clasweb.jlab.org/wiki/index.php/RGC_RC Meeting Schedule and Agendae] |
|} | |} |