Difference between revisions of "Template:ShortTermSchedule-RGD"

From clas12-run
Jump to navigation Jump to search
 
(380 intermediate revisions by 4 users not shown)
Line 1: Line 1:
'''Run Coordinator: Susan Schadmand'''  (757) 575-7540 (or 757-223-6213)
+
'''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>
  
<span style="font-size:122%; line-height: 2em;"><font color=red> ''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></span>
+
* '''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.
 +
* '''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''':
 +
:&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; Read at least the previous 24 hours '''logbook entries''' to be aware of recent run details and changes;
 +
:&loz; Arrive at least 10 minutes early for '''shift change''';
 +
:&loz; Refresh the runwiki page/tabs; look over it/them every shift:
 +
::- Follow the '''Shift Expert/Worker tab's instructions'''.
 +
:&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.
 +
:&loz;<span style="font-size:122%; line-height: 1.3em;"><font color=blue> Review these important links:
 +
::- '''[[Recent Changes and Current Issues]]'''
 +
::- '''[[General How-to]]''' for beam restoration procedures and M&oslash;ller runs.</font></p></span>
 +
 
 +
{| {{TableStyle1}}
 +
 
 +
| valign=top width=50% |
 +
 
 +
== '''Run Plan''', '''Thursday, Dec. 14<sup>th</sup> - Friday, Dec. 15<sup>th</sup>, 2023'''==
  
* '''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House'''
+
* 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:
* 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.
+
:- Target: '''CuSn'''
* '''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!
+
:- Beam Blocker: '''IN'''
 +
:- Beam current: '''100 nA +/- 4 nA on 2C21A'''
 +
:- Run duration: '''100 M events'''  
 +
:- DAQ configuration: <tt>'''PROD67'''</tt>
 +
:- Trigger file: '''rgd_out_v2.3_Q2_1.2.trg'''
 +
 
 +
<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>
 +
 
 +
| valign=top |
 +
 
 +
==<font color=BLACK>''' General Instructions'''</font>==
 +
 
 +
* 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'''.
 +
:&bull; Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]
 +
:&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
 +
:&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.
 +
 
 +
* '''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%.
  
* Note to shift takers, please:
+
* For '''beam tuning and M&oslash;ller runs'''
:&loz; Read the '''logbook''', be aware of previous 24 hours
+
:&bull; Make sure the SVT/MVT are set as follows: '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON in SAFE Mode.'''
:&loz; Arrive at least 10 minutes early for '''shift change'''
+
::- 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'''.
:&loz; Refresh the run wiki pages; look over them every shift
+
::- When '''turning MVT ON''': go to HV->Overview->Actions, and select BMT (/FMT) "HV ON - Full Voltage".
::- Follow the '''expert/worker shift instructions'''  
+
::- '''DO NOT start runs in SAFE Mode''' for Production/Calibration/Various-Studies.
:&loz; '''Communicate''' with your co-shift person
+
:&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.
::- 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
 
:&loz; For advice, do not hesitate to call the RC first and foremost, day and night.
 
  
== Current Issues ==
+
*''' To access the Hall:'''
* If new '''hot channels appear in BMT/FMT/SVT''', please '''call the MVT/SVT/MM expert Yuri Gotra''' (757-541-7539) to address them.
+
:&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).
* If the '''tagger magnet''' needs to be turned off, tell the operator to use '''only the script only for degaussing, NEVER do "by hand"!'''
+
:&bull; Check in with the shift personnel before entering the hall.
* In case of questions from MCC about the necessary controlled access to '''change the LD2 and solid targets positions in the hall''', please refer to the logbook entry #: '''[https://logbooks.jlab.org/entry/4196113 4196113]''' for the access requirements.
+
 
 +
|}
  
 
{| {{TableStyle1}}  
 
{| {{TableStyle1}}  
 
+
== <font color=Navy> '''DAQ Operation & related General Instructions''' </font> ==
 
| valign=top width=50% |
 
| valign=top width=50% |
 +
* (New) '''STANDARD''' end and start of the run:
 +
:- "End run"
 +
:- <font color=BROWN>'''"Abort"'''
 +
:- '''"Download"'''</font>
 +
:- "Prestart"
 +
:- "Go"
  
== '''Run Plan for''' '''Oct. 12th to Oct. 14th''', 2023 ==
+
* <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>
* '''Friday, Oct. 13th, Owl Shift''':
+
:&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>
:&bull; Continue the LD2 outbending production with 45 nA and 100 M runs by using the following 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_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Owl shift''----</font>
 
* '''Friday, Oct. 13th, Day Shift''':
 
:&bull; Depending on the status of the run during the shift changeover, please end the run once it reaches 100 M, then start the RICH threshold scans.
 
:&bull; Please ask MCC for 35 nA and take three 1h 30min runs with BEAM-ON and the following DAQ configuration and trigger files :
 
::- ''DAQ Config.'': <tt>PROD66_PIN</tt>. <font color=blue> Follow the DAQ instructions below to change its configurations and load new trigger files.</font>
 
::- Load the ''trigger file'': '''rgd_v1.0_no_DC_RICH_50.trg''' for the first 1h 30min BEAM-ON run,
 
::- Load the ''trigger file'': '''rgd_v1.0_no_DC_RICH_100.trg'''for the second 1h 30min BEAM-ON run,
 
::- Load the ''trigger file'': '''rgd_v1.0_no_DC_RICH_200.trg'''for the third 1h 30min BEAM-ON run.
 
:&bull; '''P.S.: While approaching the end of the 3rd run (''at least 1/2h before its end''), please contact the SVT/MVT experts, Yuri and Rafo, to keep an eye on MVT during the next Lumi. scans runs. Also, please watch the DC occupancy on mon12 and refresh it frequently during the Lumi. scans.
 
::&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 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>.
 
::&Dagger; Ask MCC for 75 nA and take a 25 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>.
 
:&bull; Once done, continue the LD2 outbending production with 45 nA and 100 M runs by using the following 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_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Swing shift''----</font>
 
* '''Friday, Oct. 13th, Swing Shift''':
 
:&bull; Continue the LD2 outbending production with 45 nA and 100 M runs by using the following 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_v1.0_no_DC.trg'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Owl shift''----</font>
 
* '''Saturday, Oct. 14th, Owl Shift''':
 
:&bull; Continue LD2 outbending production with 50 nA by taking 100 M runs with the following configuration:
 
::- ''DAQ Config.'': <tt>PROD66</tt>. <font color=blue> Follow the DAQ instructions below to load new trigger file.</font>
 
::- ''Trigger file'': '''rgd_out_v1.0.trg'''.
 
''' P.S.: At 7:30 AM, please call the engineering-on-call to inform him that we want to change the target position downstairs to the solid target position by the end of this run, and thus, we need him to come for controlled access. Don't end the run even if it exceeds 100 M until the engineer arrives'''. <font color=blue><center>-----''If everything goes well, that should bring us to the Day shift''----</font></center>
 
* '''Saturday, Oct. 14th, Day Shift''':
 
:&bull; In parallel with controlled access, empty the cryo-target cell and insert CxC solid target in the beamline from the drop menu in the cryo-target GUI. For more details, please refer to the cryo-target and flag assembly: [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q manual].
 
:&bull; Ask MCC for 50 nA and start CxC outbending production of 100 M runs 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_out_v1.0.trg'''
 
:&bull; Continue CxC production for the next couple of days as mentioned above until otherwise instructed!
 
:&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'''<font color=blue><center>-----''If everything goes well, that should bring us to the Swing shift''----</font>-->.
 
<!--
 
  
* In-bending torus field, 5-pass beam on ND3.
+
* '''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:
* Beam Current: 666 nA
+
:- "Cancel", "Reset"
* Run duration: 100M events or 4 hours, whichever comes first.
+
:- "Needed operations: change configuration or trigger files, or a run did not end correctly, or a ROC crash or RICH is Fastly/Fully recovered";
* CODA Configuration: PROD66
+
:- "Configure"
* Trigger file: <tt>rgd_300MeV_v1.0.trg</tt>
+
:- "Download"
-->
+
:- "Prestart"
 +
:- "Go"
  
== <font color=blue> DAQ configuration </font> ==
+
| valign=top |
  
* '''Configuration''' is <tt>'''PROD66'''</tt> or <tt>'''PROD66_PIN'''</tt> for fast reconstruction of ''some commissioning/reference runs'' from the cache disk.
+
* '''Configuration''' is <tt>'''PROD66/67'''</tt> (or <tt>'''PROD66_PIN'''</tt> for fast reconstruction of ''some calibration/reference runs'' from the cache disk).
* <tt>Trigger file: '''rgd_inb_v1.0.trg''' and '''rgd_out_v1.0.trg''' for inbending and outbending production.</tt>
+
:&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>
* '''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;<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-->
* '''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.
+
* In case of '''DAQ Disk space alarm''', call the DAQ expert.
* At the end of each run, follow the <font color=brown>STANDARD DAQ RESTART SEQUENCE</font>:
+
* '''Trigger files''':
:&loz; "end run."
+
:- <tt> Inbending production: '''rgd_inb_v1.0.trg'''</tt>
:&loz; If the run ended correctly and you will run with the same configuration and trigger file, then: "prestart", "go"
+
:- <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''
:&loz; If you are changing configuration (between PROD6X and PROD6X_PIN) or trigger file: "Cancel", "reset", "configure", "download", "prestart", "go".  
+
* During "Configure", observe the ROC terminals to see whether any '''ROC has error messages'''.
:&loz; If the run did not end correctly or if any ROCs had to be rebooted:
+
* ''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!
::- Quit ALL running instances of mon12
+
* In case of '''DAQ livetime "0" alarm''', '''RESTART DAQ from Scratch''';
::- "Cancel", "reset"
+
:&bull; Note that you also get a ''DAQ livetime alarm'' at the start of a run; that is OK and can be simply acknowledged.
::- "configure", "download", "prestart", "go"
+
* Unless a RICH problem crashes the DAQ, '''do NOT interrupt an otherwise smooth run for a RICH recovery'''. Instead, do this in between runs.  
::- restart mon12
+
* 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.
* 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.
+
* '''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.
  
== Reference Values ==
+
|}
 +
 
 +
== '''Reference Values''' ==
  
 
=== FSD Thresholds from RG-D ===
 
=== FSD Thresholds from RG-D ===
Line 110: Line 127:
 
=== Harp Scan References from RG-D ===
 
=== Harp Scan References from RG-D ===
 
* 2H01 [https://logbooks.jlab.org/entry/4192230]; x= -1.4 mm; y= 0.0 mm
 
* 2H01 [https://logbooks.jlab.org/entry/4192230]; x= -1.4 mm; y= 0.0 mm
* 2C21A [https://logbooks.jlab.org/entry/4122116]; Not done yet for RG-D, but from RG-C:  
+
* Tagger (2C24A) [https://logbooks.jlab.org/entry/4191955]: x= -2.0 mm; y= +0.6 mm
** x= -0.4 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'')
* Tagger (2C24A) [https://logbooks.jlab.org/entry/4191955]; x= -2.0 mm; y= +0.6 mm
 
  
 
=== IA for Q Asymmetry ===
 
=== IA for Q Asymmetry ===
 
* HWP IN: https://logbooks.jlab.org/entry/4194811 and https://logbooks.jlab.org/entry/4195453
 
* 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
 
* HWP OUT: https://logbooks.jlab.org/entry/4195738 and https://logbooks.jlab.org/entry/4195733
 
| valign=top |
 
 
==<font color=blue>''' General Instructions''':</font>==
 
 
* 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'''. The same thing applies to FMT '''select FMT HV ON - Safe Voltage'''.
 
:&loz; When '''turning MVT ON''': '''go to HV->Overview->Actions, and select BMT (/FMT) 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:'''
 
* 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:'''
 
* Check values at the start of every run and log screenshots of:
 
:&loz; Main scaler GUI display
 
:&loz; Trigger rate GUI
 
:&loz; Beam strip charts
 
:&loz; FTC scalers
 
* 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:'''
 
* 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).
 
* Check in with the shift personnel before entering the hall.
 
 
|}
 

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