Difference between revisions of "Template:ShortTermSchedule-RGK"

From clas12-run
Jump to navigation Jump to search
(Created page with "'''Run Coordinator: Susan Scha''' (757) 575-7540 ''' PDL: Nathan Baltzell''' (9-) 757 876-1789; ''Office'': x5902 '''RG/Analysis Coordinator (AC): Lamiaa El Fassi''' (630...")
 
 
(411 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
'''Run Coordinator: Susan Scha''' (757) 575-7540
+
'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span>
  
−
''' PDL: Nathan Baltzell''' (9-) 757 876-1789; ''Office'': x5902
+
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman''' (757) 575-7540 </span>
  
−
'''RG/Analysis Coordinator (AC): Lamiaa El Fassi''' (630) 605-4259
+
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789 </span>
  
−
''' [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'''.
+
'''<span style="font-size:120%; line-height: 1.3em;"> [https://clasweb.jlab.org/wiki/index.php/Run_Group_K#RGK_FALL_2023__2F_SPRING_2024 Daily RC Meetings] </span>
  
 
== '''Important Notes''' ==
 
== '''Important Notes''' ==
Line 11: Line 11:
 
:::::::::::::::<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;"><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''' 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''' (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''':
+
'''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.
−
:&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}}
+
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.
  
−
| valign=top width=50% |
+
'''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!
  
−
== '''Run Plan''', '''Thursday, Nov. 16<sup>th</sup> - Tuesday, Nov. 21<sup>st</sup>, 2023'''==
+
'''Note to Shift Takers''':
 +
* Read the '''ESAD, COO, RSAD, and ERG''' documents found on the "[https://www.jlab.org/Hall-B/run-web/index_rgk.html Current RG-K 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'''
 +
** If it is your first shift or a shift after a long pause, do <font color=red> '''shadow an earlier shift for at least 4 hours''' </font> to familiarize yourself with all shift duties and technicalities of the ongoing experiment.
  
−
*'''Thursday, Nov 16<sup>th</sup>''':
+
* Refresh the run wiki page/tabs; look over it/them every shift
−
:&bull; '''Owl Shift: Canceled since no beam is expected until 16 Nov. day shift!
+
* Follow the '''Shift Expert/Worker tab's instructions'''
−
:&bull; '''Day Shift: Injector Recovery''':
+
* '''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; Please call the '''RC''' whenever you know when the beam will be back, as she needs to be here for the beam restoration!
 
−
::&loz; Beam restoration: Please review the [[General How-to]] link above for instructions on how to:
 
−
:::- Establish the physics beam to the tagger dump;
 
−
:::- Perform a M&oslash;ller run;
 
−
:::- Establish the physics beam to the Faraday Cup.  
 
  
−
::&loz; If everything goes well with the beam restoration steps and Moller run, please insert CxC back in the beamline and resume its data-taking as follows:
+
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for ===
−
:::- Beam current: '''50 nA'''
+
* '''Recent Changes'''
−
:::- Beam Blocker: '''OUT'''
+
* '''Current Issues'''
−
:::- Run duration: '''100 M events'''  
+
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)
−
:::- DAQ configuration: <tt>'''PROD67'''</tt>
 
−
:::- Trigger file: '''rgd_out_v2.3_Q2_1.2.trg'''
 
  
−
*'''Saturday, Nov 18<sup>th</sup>, Swing Shift''':
+
== '''Run Plan: Mar. 10 - Mar. 11, 2024''' ==
−
:&bull; '''Please call the engineering on-call to change the target position in the hall to the liquid target position'''. Please keep the run ongoing until the engineer arrives, even if it exceeds 100 M.
+
−
:&bull; '''In parallel with rapid (controlled) access, change the solid flag assembly to "Empty" from the drop menu in the cryo-target GUI and start filling 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]'''.
+
'''Production Running ... to the end!!'''
−
 
+
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg
−
:&bull; Once the access is done, ask for 5 nA to check the BPMs positions. If everything is fine, resume LD2 production as follows:
+
- Beam current request: 75 nA
−
::- Target: '''LD2'''
+
- Run duration: 3 hrs
−
::- Beam current: '''60 nA'''
 
−
::- Beam Blocker: '''OUT'''
 
−
::- Run duration: '''100 M events'''
 
−
::- DAQ configuration: <tt>'''PROD67'''</tt>
 
−
::- Trigger file: '''rgd_out_v2.3_Q2_1.2.trg'''
 
  
−
*'''Sunday, Nov 19<sup>th</sup>, Swing Shift''':  
+
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.
−
:&bull; '''Please call the engineering on-call to change the target position in the hall to the solid target position'''. Please keep the run ongoing until the engineer arrives, even if it exceeds 100 M.   
+
  - Turn all detectors off and put BMT HV in safe mode
−
:&bull; '''In parallel with rapid (controlled) access, change the solid flag assembly to "CuSn" 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]'''. Also, move the Beam Blocker to the beamline position.
+
- Ramp torus and solenoid to zero field (contact Eugene to do this)
−
:&bull; Resume CuSn data-taking as follows:
+
- Call to put Hall B in Restricted Access
−
::- Target: '''CuSn'''
 
−
::- Beam Blocker: '''IN'''
 
−
::- Beam current: '''95 nA +/- 3nA 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 95 nA, please ask MCC to narrow down the fluctuation margin and give us +/- 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.'''</font></p></span>
+
=== Related Information ===
 +
Find detailed information at tab "GENERAL INFORMATION".
  
−
*'''Tuesday, Nov 21<sup>th</sup>, Day Shift''':
+
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time.
−
:&bull; ''' MCC Beam Studies!'''
 
  
−
<!--** 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>-->
+
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running").  
−
<!--<font color=blue> Follow the DAQ instructions below to change its configurations.</font>
+
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
−
-->
 
  
−
| valign=top |
+
* The beam position at '''2C21A''' is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.
 +
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).
  
−
==<font color=BLACK>''' General Instructions'''</font>==
+
* If '''HWP is changed''', start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.
  
−
* 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'''.
+
* '''Beam tuning and M&oslash;ller runs'''
−
:&bull; Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]
+
** Generally, Detector HV OFF but
−
:&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
+
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''
−
:&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.
+
** Turn <b> DC HV </b> off only for beam tuning
  
−
* '''Beamline''':
+
'''Access to the Hall'''
−
:&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.
+
* 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; If there is any concern about beam stability, ask MCC if orbit locks are on (they should be).
+
* Check in with the shift personnel before entering the hall.
−
:&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%.
 
  
−
* For '''beam tuning and M&oslash;ller runs'''
+
{| {{TableStyle1}}
−
:&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:'''
+
== <font color=Navy> '''DAQ Operation''' & Related Information </font> ==
−
:&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.
 
  
−
|}
+
| valign=top width=50% |
  
−
{| {{TableStyle1}}
+
<font color=red>'''NEW STANDARD''' end and start of the run:</font>
−
== <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"
−
:- <font color=BROWN>'''"Abort"'''
+
:- "Cancel"
−
:- '''"Download"'''</font>
+
:- "Reset"
 +
:- "Download"
 
:- "Prestart"
 
:- "Prestart"
 
:- "Go"
 
:- "Go"
 +
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.
  
−
* '''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 FAST/Fully recovered, as follows:
+
'''Restart DAQ'''  
−
:- "Cancel", "Reset"
+
:-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:
 +
:- "Cancel"
 +
:- "Reset"
 
:- "Configure"
 
:- "Configure"
 
:- "Download"
 
:- "Download"
Line 129: Line 94:
 
| valign=top |
 
| 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).
+
* '''Restart DAQ''': ensure that each step is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.
 +
* ''Some ROCs keep printing error messages while functioning properly'', see logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] .
 +
* If a ROC is disconnected, the message will appear in the run control message window.
 +
* If a '''ROC has crashed'''.
 +
** Find out which one (look for busy ROCs)
 +
** End the current run
 +
** Issue a '''roc_reboot''' command on just that ROC
 +
** ''PING'' the ROC to check that it is back up (some take longer than others)
 +
** '''Restart DAQ'''
 +
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field. 
 +
* At the start and end of a run, check that the data in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.
 +
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.
 
* In case of '''DAQ Disk space alarm''', call the DAQ expert.
 
* In case of '''DAQ Disk space alarm''', call the DAQ expert.
−
* '''Trigger files''':
+
* Contact the DAQ expert if you have any questions or doubts about how to proceed.
−
:- <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 any of them get disconnected, the message will appear in the run control itself!
 
−
* If a ROC has crashed, find which one is (look for busy ROCs), end the current run, issue a '''roc_reboot''' command ON JUST THAT ROC, and test with ''SSH'' or ''PING'' to check whether the ROC is back up (some take longer than others). Then, '''RESTART DAQ from scratch'''.
 
−
* 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 major detector problems. Sometimes, it 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 runs (e.g., Production) 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''' ==
+
== <font color=Navy> '''Triggers files'''</font> ==
  
−
=== FSD Thresholds from RG-D ===
+
{| class="wikitable"
 +
|-
 +
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.
 +
|-
 +
| rgk_noDC_v1.1_300MeV.trg || DC roads are not in the trigger. Hold off time is 2 us.
 +
|-
 +
| rgk_noDC_v1.2_300MeV.trg || DC roads are not in the trigger. Hold off time is 1 us.
 +
|-
 +
| rgk_out_v1.1_300MeV.trg || Outbending DC roads, Hold off time is 2 us.
 +
|}
 +
 
 +
== <font color=Navy> '''Reference Values''' </font> ==
 +
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} -->
 +
 
 +
=== FSD Thresholds ===
 
* Upstream: 2 kHz
 
* Upstream: 2 kHz
 
* Midstream: 2 kHz
 
* Midstream: 2 kHz
Line 155: Line 134:
 
* 5 ms dwell time
 
* 5 ms dwell time
  
−
=== Harp Scan References from RG-D ===
+
=== Nominal Beam Positions ===
−
* 2H01 [https://logbooks.jlab.org/entry/4192230]; x= -1.4 mm; y= 0.0 mm
+
 
−
* Tagger (2C24A) [https://logbooks.jlab.org/entry/4191955]: x= -2.0 mm; y= +0.6 mm
+
'''2C21A''' (not important for production)
−
* 2C21A [https://logbooks.jlab.org/entry/4122116]: x= -0.4 mm; y= +0.6 mm (''less important; values form RG-C'')
+
* x = -0.4 mm
 +
* y = +0.7 mm
 +
 
 +
'''2C24A''' 
 +
* x = -1.7 mm
 +
* y = +0.5 mm
 +
 
 +
'''2H01''' 
 +
* x = -0.7 mm
 +
* y = +0.6 mm
 +
 
 +
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===
 +
 
 +
2C21A: https://logbooks.jlab.org/entry/4252495
 +
 
 +
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496
 +
 
 +
2H01:  https://logbooks.jlab.org/entry/4252514
 +
 
 +
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===
 +
 
 +
2C21A: https://logbooks.jlab.org/entry/4240375
 +
 
 +
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378
  
−
=== IA for Q Asymmetry ===
+
2H01: https://logbooks.jlab.org/entry/4240397
−
* 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 07:14, 10 March 2024

Experiment Coordinator: Annalisa D'Angelo

Run Coordinator: Daniel Carman (757) 575-7540

PDL: Daniel Carman (757) 876-1789

Daily RC Meetings

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-K 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
    • If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.
  • Refresh the run wiki 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.

See tab GENERAL INFORMATION for

  • Recent Changes
  • Current Issues
  • Beam Restoration (for beam restoration procedures and Møller runs)

Run Plan: Mar. 10 - Mar. 11, 2024

Production Running ... to the end!! 

- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg
- Beam current request: 75 nA
- Run duration: 3 hrs

Note: RG-K run ends on Mar. 11 at 7 a.m. 

- Turn all detectors off and put BMT HV in safe mode
- Ramp torus and solenoid to zero field (contact Eugene to do this)
- Call to put Hall B in Restricted Access

Related Information

Find detailed information at tab "GENERAL INFORMATION".

  • The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF during run time.
  • Orbit locks are on BPMs 2C24A and 2H01 and the locks should generally be on ("Running").
    • Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
  • The beam position at 2C21A is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.
    • The beam position at 2C21A is important for initial beam tuning (on tagger dump).
  • If HWP is changed, start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.
  • Beam tuning and Møller runs
    • Generally, Detector HV OFF but
    • SVT: LV ON; HV OFF, and MVT: LV ON; HV ON - Safe Voltage
    • Turn DC HV off only for beam tuning

Access to 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 Information

NEW STANDARD end and start of the run:

- "End run"
- "Cancel"
- "Reset"
- "Download"
- "Prestart"
- "Go"

This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery.

Restart DAQ

-- when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:
- "Cancel"
- "Reset"
- "Configure"
- "Download"
- "Prestart"
- "Go"
  • Restart DAQ: ensure that each step is completed in the Run Control message window. During "Configure", look for error messages in the ROC terminals.
  • Some ROCs keep printing error messages while functioning properly, see logbook entry # 4215299 .
  • If a ROC is disconnected, the message will appear in the run control message window.
  • If a ROC has crashed.
    • Find out which one (look for busy ROCs)
    • End the current run
    • Issue a roc_reboot command on just that ROC
    • PING the ROC to check that it is back up (some take longer than others)
    • Restart DAQ
  • Pop-up window: Enter the beam current and the type of run in the "Comment" field.
  • At the start and end of a run, check that the data in the Run Condition Data Base (RCDB) is correct, especially the manually filled fields.
  • Check and reset monitoring histograms every hour. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.
  • In case of DAQ Disk space alarm, call the DAQ expert.
  • Contact the DAQ expert if you have any questions or doubts about how to proceed.

Triggers files

rgk_noDC_v1.0_300MeV.trg DC roads are not in the trigger. Hold off time is 3 us.
rgk_noDC_v1.1_300MeV.trg DC roads are not in the trigger. Hold off time is 2 us.
rgk_noDC_v1.2_300MeV.trg DC roads are not in the trigger. Hold off time is 1 us.
rgk_out_v1.1_300MeV.trg Outbending DC roads, Hold off time is 2 us.

Reference Values

FSD Thresholds

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

Nominal Beam Positions

2C21A (not important for production)

  • x = -0.4 mm
  • y = +0.7 mm

2C24A

  • x = -1.7 mm
  • y = +0.5 mm

2H01

  • x = -0.7 mm
  • y = +0.6 mm

8.5 GeV Harp Scan References (Feb. 14, 2024)

2C21A: https://logbooks.jlab.org/entry/4252495

Tagger (2C24A): https://logbooks.jlab.org/entry/4252496

2H01: https://logbooks.jlab.org/entry/4252514

6.4 GeV Harp Scan References (Jan. 18, 2024)

2C21A: https://logbooks.jlab.org/entry/4240375

Tagger (2C24A): https://logbooks.jlab.org/entry/4240378

2H01: https://logbooks.jlab.org/entry/4240397

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