Difference between revisions of "Template:ShortTermSchedule-RGD"

From clas12-run
Jump to navigation Jump to search
 
(227 intermediate revisions by 3 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
Line 12: Line 12:
  
 
* '''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 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''' (eg due to fire alarm in Counting House) grab the shift expert phone and call the RC from outside. RC will call MCC: Take beam down for Hall B.
+
* '''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:
 
:&loz; Read the '''logbook''', be aware of previous 24 hours
 
:&loz; Arrive at least 10 minutes early for '''shift change'''
 
:&loz; Refresh the run wiki pages; look over them every shift
 
::- Follow the '''expert/worker shift instructions'''.
 
:&loz; For advice, '''do not hesitate to call the RC''' first and foremost, day or night.
 
 
 
== '''Current Issues''' ==
 
 
 
* '''Do not spend more than 15-20 min trying to fix a problem'''. With any issue, contact On-Call Experts or RC.
 
 
 
* NEW: when starting a new run after successful end, do not go from Prestart, but Abort and then Download, Prestart, Go
 
 
 
* Especially after HWP change, check the SLM and FCUP '''charge asymmetry''' (Q-Asym on Beamline Overview), the absolute values should be less than 0.1%. If they are out of range, contact the beamline expert.
 
 
 
* NOTE, the beam position on BPM  2C21A is not important during production, the beam orbit lock is on BPM 2H01.
 
 
 
* '''RICH''':
 
** '''New RICH recovery protocol''': see tab expert "Shift Expert" for new information. '''Avoid unnecessary recoveries'''.
 
** RICH Sector 1 has three missing tiles, this is known, no action by shift required.
 
 
 
* '''BMT/FMT/SVT:''' If new hot channels appear, '''call the MVT/SVT/MM expert Yuri Gotra''' (757-541-7539). These channels need to be addressed by the expert.
 
 
 
* '''Tagger magnet procedure:''' If the tagger magnet needs to be turned off, tell the operator to use '''only the script for degaussing, NEVER do "by hand"!'''
 
  
* '''Change of target in the hall:''' In case of questions from MCC about the necessary controlled access, refer to the logbook entry #: '''[https://logbooks.jlab.org/entry/4196113 4196113]''' for the access requirements.
+
* '''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}}  
 
{| {{TableStyle1}}  
Line 48: Line 31:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
== '''Run Plan''' for Mon., Oct. 31<sup>st</sup> - Sat., Nov. 11<sup>th</sup>, 2023 ==
+
== '''Run Plan''', '''Thursday, Dec. 14<sup>th</sup> - Friday, Dec. 15<sup>th</sup>, 2023'''==
  
* Continue LD2 production as follows:  
+
* 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:
:- Beam current: '''60 nA'''  
+
:- Target: '''CuSn'''
 +
:- Beam Blocker: '''IN'''
 +
:- Beam current: '''100 nA +/- 4 nA on 2C21A'''  
 
:- Run duration: '''100 M events'''  
 
:- Run duration: '''100 M events'''  
:- Beam Blocker: '''OUT'''
 
 
:- DAQ configuration: <tt>'''PROD67'''</tt>  
 
:- DAQ configuration: <tt>'''PROD67'''</tt>  
:- Trigger file: '''rgd_out_v2.1_Q2_1.2.trg'''
+
:- Trigger file: '''rgd_out_v2.3_Q2_1.2.trg'''
  
* '''Wednesday, Nov. 1<sup>st</sup>, Day Shift''':  
+
<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>
:&bull; MCC Beam Studies! The hall will be in Controlled Access. '''Beam down for Hall B at 8:30 AM.'''
 
  
:&bull; '''Please call the engineering on-call to change the target position in the hall to the solid target position.
+
| valign=top |
  
:&bull; '''Once the target work is done, change the solid flag assembly to "Empty" from the drop menu in the cryo-target GUI and start emptying the LD2 cell. For more details, please refer to the cryo-target and flag assembly: [https://docs.google.com/document/d/1kBNmLYg2gqa4XjWgMpbh0rBUxkSAupqdnMV4THepv7k/edit#heading=h.13kef88y2w8q manual]'''.
+
==<font color=BLACK>''' General Instructions'''</font>==
  
* '''Wednesday, Nov. 1<sup>st</sup>, Swing Shift''':
+
* 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; Beam restoration: Please review the {{#switchtablink:General_How-to|General How-to}} tab instructions to:
+
:&bull; Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]
::&loz; Establish the physics beam to the tagger dump;
+
:&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
::&loz; Take a M&oslash;ller run (with a 1/2-wave plate OUT and the new Wien Angle);
+
:&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.
::&loz; Establish the physics beam to the Faraday Cup.  
 
  
:&bull; If everything is fine, please insert CuSn back in the beamline along the beam blocker. Resume CuSn data-taking as follows:
+
* '''Beamline''':
<!--* Continue production on CuSn target as follows:-->
+
:&bull; Ignore the Faraday Cup beam current (see Current Issues).
:- Target: '''CuSn'''
+
:&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.
:- Beam Blocker: '''IN'''
+
:&bull; If there is any concern about beam stability, ask MCC if orbit locks are on (they should be).
:- Beam current: '''95 nA +/- 3nA on 2C21A'''  
+
:&bull; Document any beam condition change and send scaler GUIs to HBLOG.
:- Run duration: '''100 M events'''  
+
:&bull; If HWP is changed, start a new run:
:- DAQ configuration: <tt>'''PROD67'''</tt>
+
::&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%.
:- Trigger file: '''rgd_out_v2.1_Q2_1.2.trg'''
+
 
 +
* For '''beam tuning and M&oslash;ller runs'''
 +
:&bull; 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.
 +
:&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.
  
<span style="font-size:100%; line-height: 2em;"><p class="animate flash"><font color=brown>'''P.S.: If the beam is widely fluctuating above 95 nA, please ask MCC to narrow down the fluctuation margin and give us the required 95 nA +/- 3nA based on 2C21A reading. They could put the beam current lock on 2C21A in case that may help with the wide fluctuation as it's currently done. We will keep the beam blocker IN while using this target combination!'''</font></p></span>
+
*''' 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).
** 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>-->
+
:&bull; Check in with the shift personnel before entering the hall.
<!--<font color=blue> Follow the DAQ instructions below to change its configurations.</font>
 
-->
 
  
== <font color=blue> DAQ Operation </font> ==
+
|}
  
* (New) '''STANDARD''' end of run and start of new run:
+
{| {{TableStyle1}}
 +
== <font color=Navy> '''DAQ Operation & related General Instructions''' </font> ==
 +
| valign=top width=50% |
 +
* (New) '''STANDARD''' end and start of the run:
 
:- "End run"
 
:- "End run"
:- "Abort"
+
:- <font color=BROWN>'''"Abort"'''
:- "Download"
+
:- '''"Download"'''</font>
 
:- "Prestart"
 
:- "Prestart"
 
:- "Go"
 
:- "Go"
  
* '''Restart 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 FAST/Fully recovered, as follows:
+
* <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>
 +
 
 +
* '''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"
 
:- "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"
 
:- "Configure"
 
:- "Download"
 
:- "Download"
Line 101: Line 94:
 
:- "Go"
 
:- "Go"
  
== Reference Values ==
+
| valign=top |
 +
 
 +
* '''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.
 +
 
 +
|}
 +
 
 +
== '''Reference Values''' ==
  
 
=== FSD Thresholds from RG-D ===
 
=== FSD Thresholds from RG-D ===
Line 118: Line 133:
 
* 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>==
 
 
* <font color=red>'''Data Acquisition:'''</font>
 
:&bull; '''Configuration''' is <tt>'''PROD66/67'''</tt> (or <tt>'''PROD66(/67)_PIN'''</tt> for fast reconstruction of ''some calibration/reference runs'' from the cache disk);
 
:&bull; In case of '''DAQ Disk space alarm''', call the DAQ expert.
 
:&bull; '''Trigger files''':
 
::- <tt> Inbending production: '''rgd_inb_v1.0.trg'''</tt>
 
::- <tt> Outbending production: '''rgd_out_v2.1_Q2_1.2.trg'''</tt> with ''low-Q<sup>2</sup> suppression''
 
:&bull; If a ROC has crashed, find which one it is, end the current run, issue a '''roc_reboot''' command ON JUST THAT ROC, and RESTART DAQ.
 
:&bull; Unless a RICH problem crashes the DAQ, '''do NOT interrupt an otherwise smooth run for a RICH recovery'''. Instead, do this in between runs.
 
:&bull; The shift '''MUST check and reset monitoring histograms at least once every 30-60 minutes''' to ensure no major detector problems. Sometimes, it is the only way to know that a specific roc needs to be rebooted.
 
:&bull; '''Pop-up window''': Enter the beam current and the type of runs (e.g., Production) in the "Comment" field. 
 
:&bull; After each step of a DAQ RESTART, ensure it is completed in the '''Run Control message window'''.
 
:&bull; Contact the DAQ expert if there are any questions.
 
 
* 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 https://logbooks.jlab.org/entry/4204460
 
:&bull; Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cool down.
 
 
* '''Beamline''':
 
:&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%
 
 
* 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 fields filled manually.
 
 
* For '''beam tuning and M&oslash;ller runs'''
 
:&bull; 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.
 
:&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.
 
 
|}
 

Latest revision as of 00:44, 15 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