Difference between revisions of "Template:ShortTermSchedule-RGD"

From clas12-run
Jump to navigation Jump to search
 
(504 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
'''Run Coordinator: Susan Schadmand'''  (757) 575-7540
+
'''Run Coordinator: Lamiaa El Fassi'''  (757) 575-7540
  
−
''' PDL: Nathan Baltzell''' (9-)757 876-1789 , x5902 office
+
''' PDL: Nathan Baltzell''' (9-) 757 876-1789; ''Office'': x5902  
  
 
'''RG/Analysis Coordinator (AC): Lamiaa El Fassi'''  (630) 605-4259
 
'''RG/Analysis Coordinator (AC): Lamiaa El Fassi'''  (630) 605-4259
  
−
''' [https://clasweb.jlab.org/wiki/index.php/Run_Group_D#tab=Daily_RC_Meetings Daily RC Meetings] at 13:00 in CH Room 200C, and on ZOOM: [https://jlab-org.zoomgov.com/j/1611984219?pwd=MnZMM0pDdzhlUnlOR2c3MnRFUlFqQT09 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 meeting'''.
+
''' [https://clasweb.jlab.org/wiki/index.php/Run_Group_D#tab=Daily_RC/OA_Meetings Daily RC/OA Meetings] at 13:00 in CH Room 200C, and on ZOOM: [https://jlab-org.zoomgov.com/j/1611984219?pwd=MnZMM0pDdzhlUnlOR2c3MnRFUlFqQT09 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''' ==
 
== '''Important Notes''' ==
 +
 +
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span>
  
−
* '''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''' 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 "<font color=red>EXIT</font>" 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.
 
* 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 "Worker Shift" Tab - you need some lead time to set up!
+
* '''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 "{{#switchtablink:Shift_Worker|Shift Worker}}" tab, as you need some lead time to set up!
  
−
* Note to shift takers, please:
+
* '''Note to Shift Takers''':
−
:&loz; Read the '''logbook''', be aware of previous 24 hours
+
:&loz; Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgd.html 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.
−
:&loz; Arrive at least 10 minutes early for '''shift change'''
+
:&loz; Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes;
−
:&loz; Refresh the run wiki pages; look over them every shift
+
:&loz; Arrive at least 10 minutes early for '''shift change''';
−
::- Follow the '''expert/worker shift instructions'''  
+
:&loz; Refresh the runwiki page/tabs; look over it/them every shift:
−
:&loz; '''Communicate''' with your co-shift person
+
::- Follow the '''Shift Expert/Worker tab's instructions'''.
−
::- The shift expert should know about and refer to logbook entries in their shift summary
+
:&loz; '''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.
−
::- The shift worker should discuss an issue with the shift expert before making extra logbook entries
+
:&loz;<span style="font-size:122%; line-height: 1.3em;"><font color=blue> Review these important links:
−
 
+
::- '''[[Recent Changes and Current Issues]]'''
−
<!--font color=red>'''LE: Please don't change: Work in progress ''' </font-->
+
::- '''[[General How-to]]''' for beam restoration procedures and M&oslash;ller runs.</font></p></span>
  
 
{| {{TableStyle1}}  
 
{| {{TableStyle1}}  
Line 28: Line 31:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
−
== '''Run Plan for''' '''Oct. 6th to Oct. 8th''', 2023 ==
+
== '''Run Plan''', '''Thursday, Dec. 14<sup>th</sup> - Friday, Dec. 15<sup>th</sup>, 2023'''==
−
* '''Friday, Oct. 6th, Owl Shift''':
+
 
−
:&bull; Please continue watching the Solenoid temperature in Solenoid LHe - Coils or Solenoid LHe - PLC. In case of anything abnormal, please call the Hall B engineering-on-call, Morgan. Otherwise, once it reaches 5K, '''call Eugene, the RC, and the AC'''.
+
* Continue CuSn data-taking as follows until 7 AM on Dec. 15<sup>th</sup> when the beam will be taken away for the RG-K setup:
−
:&bull; If everything looks well, Eugene will start ramping up the solenoid and torus currents, which may take 1.5h to 2h at max!
+
:- Target: '''CuSn'''
−
:&bull; Next, the collimator needs to be moved to a 20 mm position, mask beam halos, and send the beam to FC, then take a harp scan in 2H01 and compare their results to the reference one at the bottom of this page. 
+
:- Beam Blocker: '''IN'''
−
:&bull; If everything is fine, we will resume the plan by filling the LD2 with beam OFF to perform its luminosity scan.<font color=blue><center>-------- ''If everything goes well, that should bring us to the Day shift''-------</font></center>
+
:- Beam current: '''100 nA +/- 4 nA on 2C21A'''  
−
* '''Friday, Oct. 6th, Day Shift''':
+
:- Run duration: '''100 M events'''  
−
:&bull; '''LD2 Luminosity Scan''':
+
:- DAQ configuration: <tt>'''PROD67'''</tt>  
−
::&loz; The purpose of these runs is to study TOF/ECAL linearity and AI training with the following beam currents and the specified trigger files but with the same DAQ configuration:
+
:- Trigger file: '''rgd_out_v2.3_Q2_1.2.trg'''
−
:::- ''DAQ Config.'': <tt>PROD66_PIN</tt>
+
 
−
::&Dagger; '''P.S.: Before starting each luminosity scan run, please call ''in advance'' the SVT/MVT experts, Yuri and Rafo ''at least 45 min and 30 min, respectively'', to check the HV setting of MVT'''. Also, ''keep an eye on the DC occupancy on mon12 and refresh it frequently during the Lumi. scan runs''.
+
<span style="font-size:100%; line-height: 2em;"><p class="animate flash"><font color=Blue>'''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 [https://logbooks.jlab.org/entry/4224300 4224300] and [https://logbooks.jlab.org/entry/4225220 4225220].'''</font></p></span>
−
::&Dagger; Ask MCC for 5 nA and take a 7 M triggers run.
 
−
:::- ''Trigger file'': '''rgd_v1.0_no_DC_5nA.trg'''. <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>.
 
−
::&Dagger; Ask MCC for 20 nA and take a 10 M triggers run with the following trigger file:
 
−
:::- ''Trigger file'': '''rgd_v1.0_no_DC_20nA.trg'''. <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>.
 
−
::&Dagger; Ask MCC for 35 nA and take a 25 M triggers run with the following trigger file:  
 
−
:::- ''Trigger file'': '''rgd_v1.0_no_DC_35nA.trg'''. <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>.
 
−
::&Dagger; Ask MCC for 50 nA and take a 25 M triggers run with the following trigger file:
 
−
:::- ''Trigger file'': '''rgd_v1.0_no_DC_50nA.trg'''. <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>
 
−
::&loz; Two high-current runs for AI training purposes:
 
−
:::&Dagger; Ask MCC for 75 nA and take a 50 M triggers run with the following trigger file:
 
−
::::- ''Trigger file'': '''rgd_v1.0_no_DC_90nA.trg'''. <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>.
 
−
:::&Dagger; Ask MCC for 100 nA, insert ''beam blocker in front of the Faraday cup'', and take a 50 M triggers run with the following trigger file:
 
−
::::- ''Trigger file'': '''rgd_v1.0_no_DC_100nA.trg'''. <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>. <font color=brown>Depending on the detector's performance (HV trips?), the beam current can be reduced to 90 nA or until the level that the trips cease!</font>. Once done, remove the ''beam blocker'' from the front of the Faraday cup.
 
−
::&Dagger; '''Parasitically''', a 1.5-hour run with just EPICS, no DAQ, can be taken in blocks in between the luminosity runs. List of points at [https://wiki.jlab.org/clas12-run/images/a/a8/RGD_DCHVEPICtesttable.pdf Overview Table]. '''Florian needs to be notified to be present in the CR during this run'''.
 
−
::&Dagger; '''Parasitically to the EPICS run''', perform a slow beam current ramps up for scaler linearity. That can be done over the phone with the MCC Ops using a 5 nA beam current increase steps until reaching 35 nA. The process should take 5 to 7 min at max. <font color=blue><center>-----''If everything goes well, the Swing shift should start somewhere in-between the LD2 Lumi. scans!'' -----</font></center>
 
−
* '''Friday, Oct. 6th, Swing Shift''':
 
−
:&bull; Once the Lumi. scan is done, continue LD2 data-taking with 35 nA (''check with RC/AC after Lumi. scan is done''), and 100 M triggers runs until the end of the Swing shift, but start performing the RICH Threshold scan as follows, assuming all other detectors are at their nominal settings, ''please check with the RC/AC'':
 
−
::- Load the ''trigger file'': '''rgd_v1.0_no_DC_RICH_50.trg'''; <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>, and take a 100 M run;
 
−
::- Load the ''trigger file'': '''rgd_v1.0_no_DC_RICH_100.trg'''; <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>, and take a 100 M run;
 
−
::- Load the ''trigger file'': '''rgd_v1.0_no_DC_RICH_200.trg'''; <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>, and take a 100 M run.
 
−
''' P.S.: Both Denny and Xiaodong must be notified ahead of time (at least 1/2h) to inform them about performing access to change the target position to the solid-foil position as well as emptying the target in parallel'''!
 
−
<!--::&Dagger; Whenever the RICH scan is done, continue LD2 data-taking with 35 nA and 100 M triggers runs until the end of the Swing shift but change the DAQ/trigger configuration to:
 
−
:::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations.</font>
 
−
:::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. -->
 
−
:&bull; '''Solid-target, CxC Configuration, Luminosity Scan''':
 
−
::&loz; '''P.S.: Before starting each luminosity scan run, please call ''in advance'' the SVT/MVT experts, Yuri and Rafo ''at least 45 min and 30 min, respectively'',  to check the HV setting of MVT'''. Also, ''keep an eye on the DC occupancy on mon12 and refresh it frequently during the Lumi. scan runs''.
 
−
::&Dagger; Ask MCC for 10 nA and take a 5 M triggers run with the following trigger file:
 
−
:::- ''Trigger file'': '''rgd_v1.0_no_DC_10nA.trg'''. <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>.<font color=blue><center>-----''If everything goes well, that should bring us to the Owl shift'' -----</font></center>
 
−
* '''Saturday, Oct. 7th, Owl Shift''':
 
−
:&Dagger; We will scan three beam currents in this 5 M triggers run. Ask MCC for 20 nA, take roughly 1.5 M events, ''monitor the DC occupancy in mon12'', then increase the current to 30 nA for another 1.5 or 2 M events, ''refresh mon12 and monitor the DC occupancy'', and then increase the current to 45 nA for the last 1.5 M events while ''monitoring the DC occupancy in mon12'', but with the following trigger file:
 
−
::- ''Trigger file'': '''rgd_v1.0_no_DC_30nA.trg'''. <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>.
 
−
:&Dagger; ''Once done, take a 15 M run @ 30 nA with the same trigger file and DAQ configuration''.  
 
−
:&Dagger; Next, we will scan much higher beam currents in the last 5 M triggers run with this target. Ask MCC for 50 nA, take roughly 1.5 M events, ''monitor the DC occupancy in mon12'', then increase the current to 75 nA for another 1.5 or 2 M events, ''refresh mon12 and monitor the DC occupancy'', and then increase the current to 90 nA for another 1.5 M events while ''monitoring the DC occupancy in mon12'', but with the following trigger file:
 
−
::- ''Trigger file'': '''rgd_v1.0_no_DC_50nA.trg'''. <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>. <font color=brown>Depending on the detector's performance (HV trips?) during this run, the beam current can be reduced until the level at which the trips cease. If approaching the current of the previously taken run, check with the RC or AC whether the luminosity scan should stop or whether this last scan should be taken at a specific current value. </font>
 
−
:&Dagger; Depending on the stability of detectors in the last higher beam currents run, we can take a 25 M run @ 50 nA.
 
−
:&bull; Once done, ask for 30 nA (''check with RC/AC after Lumi. scan is done'') and take 100 M electron triggers runs with '''CxC''' target until the end of the Swing shift, but change the DAQ/trigger configuration to:
 
−
::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations</font>.
 
−
::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Day shift''-----</font></center>
 
−
* '''Saturday, Oct. 7th, Day Shift''':  
 
−
:&bull; Continue '''CxC''' data-taking with 30 nA (''TBD after Lumi. scan'') and 100 M triggers runs until the end of the Day shift with the same <tt>PROD66</tt> DAQ configuration and '''rgd_v1.0_no_DC.trg''' trigger file.<font color=blue><center>---''If everything goes well, that should bring us to the Swing shift''---</font></center>
 
−
* '''Saturday, Oct. 7th, Swing Shift''':
 
−
:&bull; '''Solid-target, CuSn Configuration, Luminosity Scan''':
 
−
::&Dagger;'''P.S.: Before starting each luminosity scan run, please call ''in advance'' the SVT/MVT experts, Yuri and Rafo ''at least 45 min and 30 min, respectively'', to check the HV setting of MVT'''.
 
−
::&Dagger; Change the flag assembly setup to the '''CuSn''' target configuration and perform its luminosity scan with the specified trigger files but with the same DAQ configuration:
 
−
:::- ''DAQ Config.'': <tt>PROD66_PIN</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations.</font>
 
−
::&Dagger; Ask MCC for 90 nA and take a 5 M triggers run with the following trigger file:
 
−
:::- ''Trigger file'': '''rgd_v1.0_no_DC_90nA.trg'''.
 
−
::&Dagger; We will scan three beam currents in this 5 M triggers run. Ask MCC for 110 nA, insert ''beam blocker in front of the Faraday cup'', and take roughly 1.5 M events, ''monitor the DC occupancy in mon12'', then increase the current to 120 nA, take another 1.5 M events, ''refresh mon12 and monitor the DC occupancy'', and then increase the current to 130 nA for the last 2 M events while ''monitoring the DC occupancy in mon12'', but with the following trigger file:
 
−
:::- ''Trigger file'': '''rgd_v1.0_no_DC_100nA.trg'''. <font color=blue> Follow the DAQ instructions below to load a new trigger file</font>.
 
−
::&Dagger; ''Once done, take a 25 M run @ 130 nA with the same trigger file and DAQ configuration'' as well as the ''beam blocker.
 
−
::&Dagger; Next, we will scan much higher beam currents in the last 5 M triggers run with this target. Ask MCC for 150 nA, take roughly 1.5 M events, ''monitor the DC occupancy in mon12'', then increase the current to 175 nA for another 1.5 M events, ''refresh mon12 and monitor the DC occupancy'', and then increase the current to 200 nA for the last 2 M events while ''monitoring the DC occupancy in mon12''.. <font color=brown>Depending on the detector's performance (HV trips?) during this run, the beam current can be reduced until the level at which the trips cease. If approaching the current of the previously taken run, check with the RC or AC whether the luminosity scan should stop or whether this last scan should be taken at a specific current value. </font>
 
−
::&Dagger; Depending on the stability of detectors in the last higher beam currents run, we can take a 25 M run @ 150 nA.
 
−
:&bull; Once done, ask for 125 nA, keep the ''beam blocker in front of the Faraday cup'' (''check with RC/AC after Lumi. scan is done''), and take 100 M electron triggers runs of '''CuSn''' until the end of the Day shift with the following configuration:
 
−
::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations</font>.  
 
−
::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''.<font color=blue><center>---''If everything goes well, that should bring us to the Owl shift''---</font></center>
 
−
* '''Sunday, Oct. 8th, Owl Shift''':
 
−
:&bull; Continue '''CuSn''' data-taking with 125 nA (''TBD after Lumi. scan is done'') and 100 M triggers runs until the end of the Swing shift.<font color=blue><center>-----''If everything goes well, that should bring us to the Owl shift''----</font>
 
−
* '''Sunday, Oct. 8th, Day Shift''':
 
−
:&bull;<font color=Brown> Please call Eugene to change the torus polarity to the outbending configuration. In parallel, Denny/Xiaodong should be called so Denny will perform a controlled access to move the target back to the LD2 position while the RC/Xiaodong will fill the LD2 cell. </font>
 
−
:&bull; Once the torus is ramped up to the outbending setting, take another 50 M triggers run @ 35 nA with LD2 for the ECAL calibration upon Cole's request:
 
−
::- ''DAQ Config.'': <tt>PROD66_PIN</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations.</font>
 
−
::- ''Trigger file'': '''rgd_v1.0_no_DC.trg'''.
 
−
:&bull; Once done, we will switch to production mode with outbending configuration:
 
−
::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations and load new trigger files.</font>
 
−
::- ''Trigger file'': '''rgd_out_v1.0.trg'''.
 
−
:&bull; ''To-be-continued''....
 
−
<!--** Once the access is done, please ask MCC for 165 nA and take 100 M triggers runs with an empty target for a couple of hours with the same <tt>PROD66</tt> DAQ configuration, but the following trigger file: ''Trigger file'': '''rgd_v1.0_no_DC_100nA.trg'''-->.
 
−
<!--
 
  
−
* In-bending torus field, 5-pass beam on ND3.
+
| valign=top |
−
* Beam Current: 666 nA
 
−
* Run duration: 100M events or 4 hours, whichever comes first.
 
−
* CODA Configuration:  PROD66
 
−
* Trigger file:  <tt>rgd_300MeV_v1.0.trg</tt>
 
−
-->
 
  
−
== <font color=blue> DAQ configuration </font> ==  
+
==<font color=BLACK>''' General Instructions'''</font>==
  
−
* '''Configuration''' is <tt>'''PROD66'''</tt> or <tt>'''PROD66_PIN'''</tt> for fast reconstruction of ''some commissioning/reference runs'' from the cache disk.
+
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights are being kept off because of light leaks affecting some of the detectors (especially ECAL sec 2 and 3). If these lights are switched on during an access, they '''should be switched off when leaving the Hall'''.  
−
* <tt>Trigger file: '''rgd_inb_v1.0.trg''' and '''rgd_out_v1.0.trg''' for inbending and outbending production.</tt>
+
:&bull; Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]
−
* '''NOTE''': UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to make a RICH recovery - instead, do this in between runs.
+
:&bull; 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''': 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.
+
:&bull; 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.
−
* At the end of each run, follow the <font color=brown>STANDARD DAQ RESTART SEQUENCE</font>:
 
−
:&loz; "end run."
 
−
:&loz; If the run ended correctly and you will run with the same configuration and trigger file, then: "prestart", "go"
 
−
:&loz; If you are changing configuration (between PROD6X and PROD6X_PIN) or trigger file: "Cancel", "reset", "configure", "download", "prestart", "go".  
 
−
:&loz; If the run did not end correctly or if any ROCs had to be rebooted:
 
−
::- Quit ALL running instances of mon12
 
−
::- "Cancel", "reset"
 
−
::- "configure", "download", "prestart", "go"
 
−
::- restart mon12
 
−
* 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.
 
  
−
== Reference Values ==
+
* '''Beamline''':
 +
:&bull; Ignore the Faraday Cup beam current (see Current Issues).
 +
:&bull; Do not run over 30 minutes above 90 nA with a 5-pass beam without the <b> beam blocker IN </b>. The beam blocker must be IN for long-running at high currents for 5-pass operations.
 +
:&bull; If there is any concern about beam stability, ask MCC if orbit locks are on (they should be).
 +
:&bull; Document any beam condition change and send scaler GUIs to HBLOG.
 +
:&bull; If HWP is changed, start a new run:
 +
::&loz; 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%.
  
−
=== FSD Thresholds from RG-D ===
+
* For '''beam tuning and M&oslash;ller runs'''
−
* Upstream: 2 kHz
+
:&bull; Make sure the SVT/MVT are set as follows: '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON in SAFE Mode.'''
−
* Midstream: 2 kHz
+
::- 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'''.
−
* Downstream: 100 kHz
+
::-  When '''turning MVT ON''': go to HV->Overview->Actions, and select BMT (/FMT) "HV ON - Full Voltage".
−
* BOM: 100 kHz
+
::-  '''DO NOT start runs in SAFE Mode''' for Production/Calibration/Various-Studies.
−
* 5 ms dwell time
+
:&bull; Turn <b> DC HV </b> 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:'''
 +
:&bull; 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).
 +
:&bull; Check in with the shift personnel before entering the hall.
 +
 
 +
|}
 +
 
 +
{| {{TableStyle1}}
 +
== <font color=Navy> '''DAQ Operation & related General Instructions''' </font> ==  
 +
| valign=top width=50% |
 +
* (New) '''STANDARD''' end and start of the run:
 +
:- "End run"
 +
:- <font color=BROWN>'''"Abort"'''
 +
:- '''"Download"'''</font>
 +
:- "Prestart"
 +
:- "Go"
 +
 
 +
* <font color=red> 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. </font>
 +
:&loz; <font color=brown> When pinging a ROC, e.g., "''ping mvt1''", stop it with ''Ctrl+C'' after a couple of printouts showing different latency times. </font>
  
−
=== Harp Scan References from RG-D ===
+
* '''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:
−
* 2H01 [https://logbooks.jlab.org/entry/4192230]; x= -1.4 mm; y= +1.0 mm
+
:- "Cancel", "Reset"
−
* 2C21A [https://logbooks.jlab.org/entry/4122116]; Not done yet for RG-D, but from RG-C:  
+
:- "Needed operations: change configuration or trigger files, or a run did not end correctly, or a ROC crash or RICH is Fastly/Fully recovered";  
−
** x= -0.4 mm; y= +0.6 mm
+
:- "Configure"
−
* Tagger (2C24A [https://logbooks.jlab.org/entry/4191955]; x= -2.0 mm; y= +0.6 mm
+
:- "Download"
 +
:- "Prestart"
 +
:- "Go"
  
 
| valign=top |
 
| valign=top |
  
−
==<font color=blue>''' General Instructions''':</font>==
+
* '''Configuration''' is <tt>'''PROD66/67'''</tt> (or <tt>'''PROD66_PIN'''</tt> for fast reconstruction of ''some calibration/reference runs'' from the cache disk).
 +
:&bull;<font color=BROWN> 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 <tt>'''PROD67_noRICH'''</tt> until further notice; see the logbook entry #: [https://logbooks.jlab.org/entry/4226898 4226898]. </font>
 +
<!--:&bull;<font color=BROWN> As of 11/25/23, DAQ Configuration is <tt>'''PROD67_noRICH'''</tt> until further notice to don't bother with any RICH issues and no recoveries are needed! </font-->
 +
* In case of '''DAQ Disk space alarm''', call the DAQ expert.
 +
* '''Trigger files''':
 +
:- <tt> Inbending production: '''rgd_inb_v1.0.trg'''</tt>
 +
:- <tt> Outbending production: '''rgd_out_v2.1_Q2_1.2.trg''' or '''rgd_out_v2.3_Q2_1.2.trg''' </tt> with ''low-Q<sup>2</sup> 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 # [https://logbooks.jlab.org/entry/4215299 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''';
 +
:&bull; 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.
 +
:&bull; 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 '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.
  
−
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights are being kept off because of light leaks affecting some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall. Note that the dome lights, when switched off, cannot be turned back on immediately because they require 10-15 min to cool down. Now we have a new dome light switch outside of the hall in the labyrinth. The lights can be turned off without entering the hall.
+
|}
−
* Do not run more than 30 minutes above 90 nA with a 5-pass beam without the <b> beam blocker in front of the Faraday cup </b>. Put beam blocker in for long-running at high currents for 5-pass operations.
 
−
* Turn <b> DC HV </b> off only for beam tuning; if no beam is available or when the beam is stable, keep them on even if you are not taking data.
 
−
* For '''beam tuning and M&oslash;ller runs''', please make sure the SVT/MVT are set as follows: '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON in SAFE Mode.'''
 
−
:&loz; When '''turning MVT OFF''', do not press "BMT HV OFF" from HV->Overview->Actions, but instead '''select BMT HV ON - Safe Voltage'''.
 
−
:&loz; When '''turning MVT ON''': '''go to HV->Overview->Actions, and select BMT HV ON - Full Voltage'''.
 
−
:&loz; '''DO NOT start Production/Calibration/Various-Studies runs in the SAFE Mode'''.
 
−
* With any issue, contact On-Call Experts or RC - <b> do not spend more than 15-20 min trying to fix the problem</b>. If the phone is not answered, try the "Page Experts" button on top of CLASCSS.
 
−
* Check for and read any comments to log-book entries made during your shift!
 
  
−
'''Every Shift:'''
+
== '''Reference Values''' ==
−
* Follow the run plan as outlined by RC
 
−
* If there is any concern about beam stability, ask MCC if orbit locks are on (they should be).
 
−
* Keep shift summary up to date in HBLOG. Record all that happens.
 
−
* Document any beam condition change and send scaler GUIs to HBLOG
 
−
* If HWP is changed, start a new run
 
−
<!--
 
−
* [https://bta.acc.jlab.org Fill out BTA] hourly.  Click "Load from EPICS" to automatically fill the left side. Run the script <font color=red>btaGet.py</font> to print you the correct BTA info for this hour -- edit the values on the BTA page if they are wrong!-->
 
−
* Upload spectra from clas12mon at the beginning and end of the shift and cross-check with reference spectra (make sure you select the SAME SECTOR for the reference plots on tabs with multiple sectors);
 
−
:&loz; Reset clas12mon every ~2 hours and inspect spectra (some detectors have buttons at the bottom to toggle between the sectors -- please check all of them).
 
−
* Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook]
 
  
−
'''Every Run:'''
+
=== FSD Thresholds from RG-D ===
−
* Check values at the start of every run and log screenshots of:
+
* Upstream: 2 kHz
−
:&loz; Main scaler GUI display
+
* Midstream: 2 kHz
−
:&loz; Trigger rate GUI
+
* Downstream: 100 kHz
−
:&loz; Beam strip charts
+
* BOM: 50 kHz
−
:&loz; FTC scalers
+
* 5 ms dwell time
−
* At the start and end of every run, check that the data filled in the [https://clasweb.jlab.org/rcdb database run list] is correct (especially fields that are filled in manually, like beam current and comments). This replaces the previously used spreadsheet.
 
  
−
''' To access the Hall:'''
+
=== Harp Scan References from RG-D ===
−
* If you need to go down into Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).
+
* 2H01 [https://logbooks.jlab.org/entry/4192230]; x= -1.4 mm; y= 0.0 mm
−
* Check in with the shift personnel before entering the hall.
+
* Tagger (2C24A) [https://logbooks.jlab.org/entry/4191955]: x= -2.0 mm; y= +0.6 mm
 +
* 2C21A [https://logbooks.jlab.org/entry/4122116]: x= -0.4 mm; y= +0.6 mm (''less important; values form RG-C'')
  
−
|}
+
=== IA for Q Asymmetry ===
 +
* HWP IN: https://logbooks.jlab.org/entry/4194811 and https://logbooks.jlab.org/entry/4195453
 +
* HWP OUT: https://logbooks.jlab.org/entry/4195738 and https://logbooks.jlab.org/entry/4195733

Latest revision as of 23:44, 14 December 2023

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

Retrieved from "https://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGD&oldid=6863"