Difference between revisions of "Template:ShortTermSchedule-RGK"

From clas12-run
Jump to navigation Jump to search
 
(351 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 
'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span>
 
'''<span style="font-size:120%; line-height: 1.3em;">Experiment Coordinator: Annalisa D'Angelo''' </span>
  
−
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Bill Briscoe'''  (757) 575-7540</span>
+
'''<span style="font-size:120%; line-height: 1.3em;">Run Coordinator: Daniel Carman'''  (757) 575-7540 </span>
  
−
'''<span style="font-size:120%; line-height: 1.3em;">PDL: Daniel Carman''' (757) 876-1789; Office: x5586</span>
+
'''<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_K#tab=Daily_RC/OA_Meetings Daily RC/OA Meetings] at 13:00 in CH Room 200C, and on ZOOM: [https://urldefense.proofpoint.com/v2/url?u=https-3A__jlab-2Dorg.zoomgov.com_j_1613823885-3Fpwd-3DU0FYcUNObys4dEZmRlNnbG1aVDN4UT09&d=DwIDaQ&c=CJqEzB1piLOyyvZjb8YUQw&r=eD2eIWJtzd_0pBXdk6zLEQ&m=ObntkopZuX0DEoWyyRip_uZsJOA50F051TWnG6S21CSOhXRR7RS-gvr8emaeXaML&s=5rvCisAH8YD8KQCNQO4yVxQVwdHmCF58DyTYpgz0dR8&e= URL Link]
+
'''<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_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.
 
−
:&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!
 +
 
 +
'''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.
  
−
<font color="CCCCCC">
+
* Refresh the run wiki page/tabs; look over it/them every shift
−
== '''Run Plan''', '''Friday, Dec. 15 - Tuesday, Dec. 19, 2023'''==
+
* 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.
  
−
*'''Friday, Dec. 15''': 
+
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for ===
−
:: 07:00 – RG-D ends, beam off
+
* '''Recent Changes'''
−
::: - Call MCC to put hall in Controlled Access
+
* '''Current Issues'''
−
::: - Turn off all detectors - except CTOF, EC/PCAL, SVT HV/LV remain on, BMT is "safe" mode, FMT off
+
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)
−
::: - Torus and solenoid remain on
 
−
::: - Target Group arrives at 07:30 to begin work
 
−
:: 08:00 – 13:00: Hall B in Controlled Access
 
−
::: - ACC completes change from 5-pass to 3-pass beam
 
−
::: - Target Group completes change from LD2 to LH2 target (Chris Keith, James Brock)
 
−
:: 13:00 – 16:00 – Beam tuning + Moller run
 
−
::: - Tune beam to tagger dump yoke with necessary harp scans (Eugene Pasyuk)
 
−
::: - Take three Moller runs, one with each target polarization direction, flip HWP and take another run (Nathan Baltzell)
 
−
::: - Tune beam to Faraday cup with empty target (Eugene Pasyuk)
 
−
::: - Fill LH2 target (Chris Keith, James Brock)
 
−
:: 16:00 – 21:00 – Trigger validation (Valery Kubarovsky) (i) rgk_noDC_v1.0_validation, ii) rgk_v1.0_30kHz_150MeV, PROD67_PIN configuration)
 
−
::: - Use nominal DC HV setting (10, 11, 11)
 
−
::: - Complete trigger validation test plans with DAQ ([https://wiki.jlab.org/clas12-run/images/a/a6/RGK_trigger.pdf RG_K trigger details])
 
−
:: 21:00 – 24:00 – Luminosity scan (rgk_noDC_v1.0_300MeV.trg, PROD67 configuration)
 
−
::: - Take runs with 10M events at 10, 20, 30, 40, 50, 60 nA
 
−
::: - Take 10M event runs at 75 nA and 90 nA if possible with DAQ operation (check with RC)
 
−
::: - Use nominal DC HV setting (10, 11, 11)
 
−
::: - For each beam current put mon12 plots in logbook. The first will use the nominal DC occupancy z-scale (10%), the second should have the scale set appropriately for each current to prevent cut off.
 
−
</font>
 
  
−
*'''Saturday, Dec. 16''':
+
== '''Run Plan: Mar. 10 - Mar. 11, 2024''' ==
−
<font color="CCCCCC">
+
−
:: 00:00 – 08:00 – Luminosity scans cont'd (rgk_noDC_v1.0_300MeV.trg, PROD67 configuration)
+
'''Production Running ... to the end!!'''
−
::: - Take runs with 10M events at 10, 20, 30, 40, 50, 60 nA
+
  - DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg
−
::: - Take 10M event runs at 75 nA and 90 nA if possible with DAQ operation (check with RC)
+
- Beam current request: 75 nA
−
::: - Use nominal DC HV setting (10, 11, 11)
+
- Run duration: 3 hrs
−
::: - For each beam current put mon12 plots in logbook. The first will use the nominal DC occupancy z-scale (10%), the second should have the scale set appropriately for each current to prevent cut off
 
−
</font>
 
−
:: 08:00 – 24:00 - DC test plan part I (<font color="red">Florian Hauenstein</font>) (PROD67_PIN configuration)
 
−
::: - DC HV studies at 40 nA (75M trigger runs) ([https://wiki.jlab.org/clas12-run/images/e/e7/DCplansRGK.pdf DC test plan document])
 
−
:::: - The first 75M event run will use the nominal DC settings. Start run and call DC expert (Florian) when it gets to 50M.
 
−
::: - Collect data for gain calibration CTOF, ECAL, FTOF, HTCC
 
−
::: - For each HV setting put mon12 plots in logbook. The first will use the nominal DC normalized occupancy z-scale (10%), the second should have the scale set appropriately for each current to prevent cut off
 
−
::: - For each HV setting post plots to HBLOG of DC HV currents (all Regions) and "DC HV measured current and voltage" screen (see DC HV, under monitoring button) (see last night's logbook for the full set)
 
  
−
*'''Sunday, Dec. 17''': 
+
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.
−
:: 00:00 – 08:00 – Data collection (shifters) (rgk_noDC_v1.0_300MeV.trg, PROD67 configuration)
+
- Turn all detectors off and put BMT HV in safe mode
−
::: - Use DC (10 11 11) setting (Florian will set the DC HV)
+
- Ramp torus and solenoid to zero field (contact Eugene to do this)
−
::: - Take one 4-hr run with 75 nA
+
- Call to put Hall B in Restricted Access
−
::: - Take one 4-hr run with 90 nA
 
−
:: 08:00 – 11:00 – Streaming readout tests (<font color="red">Sergey Boyarinov</font>, <font color="red">David Lawrence</font> ([https://wiki.jlab.org/epsciwiki/images/f/f0/SRO_LDRD_Test_Plan_2024v0.5.pdf Streaming readout test plan document])
 
−
::: - Turn off all detectors except FTOF and ECAL; Consult Yuri for SVT and CVT settings.
 
−
::: - Runs up to 150 nA
 
−
:: 11:00 – 22:00 – DC test plan part II (<font color="red">Florian Hauenstein</font>) (use PROD67_PIN configuration)
 
−
::: - DC HV studies at 40 nA (75M trigger runs) ([https://wiki.jlab.org/clas12-run/images/e/e7/DCplansRGK.pdf DC test plan document])
 
−
::: - For each HV setting put mon12 plots in logbook. The first will use the nominal DC occupancy z-scale (10%), the second should have the scale set appropriately for each current to prevent cut off
 
−
::: - For each HV setting post plots to HBLOG of DC HV currents (all Regions) and "DC HV measured current and voltage" screen (see DC HV, under monitoring button)
 
−
:: 22:00 – 24:00 – Data collection (shifters) (rgk_noDC_v1.0_200MeV.trg, PROD67 configuration)
 
−
::: - Use DC (10 11 11) setting (Florian will set the DC HV)
 
−
::: - Take one 4-hr run with 60 nA
 
−
::: - Take one 4-hr run with 75 nA
 
  
−
*'''Monday, Dec. 18''': 
+
=== Related Information ===
−
:: 00:00 – 08:00 – Data collection cont’d (shifters) (rgk_noDC_v1.0_200MeV.trg, PROD67 configuration)
+
Find detailed information at tab "GENERAL INFORMATION".
−
::: - Use DC (10 11 11) setting (Florian will set the DC HV)
 
−
::: - Take one 4-hr run with 60 nA
 
−
::: - Take one 4-hr run with 75 nA
 
−
:: 08:00 – 14:00 – Reverse solenoid polarity (<font color="red">Eugene Pasyuk</font>, <font color="red">Engineering</font>)
 
−
:: 14:00 – 17:00 – Trigger validation (<font color="red">Valery Kubarovsky</font>) (use PROD67_PIN configuration)
 
−
::: - Complete trigger validation test plans with DAQ ([https://wiki.jlab.org/clas12-run/images/a/a6/RGK_trigger.pdf RG_K trigger details])
 
−
:: 17:00 – 24:00 – Data collection (shifters) (PROD67 configuration)
 
−
::: - Use DC (10 11 11) setting (Florian will set the DC HV)
 
−
::: - Take one 4-hr run with 60 nA (rgk_noDC_v1.0_300MeV.trg)
 
−
::: - Take one 4-hr run with 75 nA (rgk_noDC_v1.0_300MeV.trg)
 
−
::: - Take one 4-hr run with 60 nA (rgk_noDC_v1.0_200MeV.trg)
 
−
::: - Take one 4-hr run with 75 nA (rgk_noDC_v1.0_200MeV.trg)
 
  
−
*'''Tuesday, Dec. 19''': 
+
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time.
−
:: 00:00 – 07:00 – Data collection cont’d (shifters)
 
−
::: - Use DC (10 11 11) setting (Florian will set the DC HV)
 
−
::: - Take one 4-hr run with 60 nA (rgk_noDC_v1.0_300MeV.trg)
 
−
::: - Take one 4-hr run with 75 nA (rgk_noDC_v1.0_300MeV.trg)
 
−
::: - Take one 4-hr run with 60 nA (rgk_noDC_v1.0_200MeV.trg)
 
−
::: - Take one 4-hr run with 75 nA (rgk_noDC_v1.0_200MeV.trg)
 
−
:: 07:00 – Beam off
 
−
:: 07:00 – 08:00 – Prepare CLAS12 for accelerator down
 
−
::: - Turn CLAS12 detectors off (shifters)
 
−
::: - Ramp down magnets (<font color="red">Eugene Pasyuk</font>)
 
−
::: - Empty and secure target (<font color="red">Chris Keith</font>, <font color="red">James Brock</font>) 
 
  
−
| valign=top |
+
* 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").
  
−
==<font color=BLACK>''' General Instructions'''</font>==
+
* 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).
  
−
* 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'''.
+
* 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%.
−
:&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''':
+
* '''Beam tuning and M&oslash;ller runs'''
−
:&bull; Do not run over 30 minutes above 90 nA with a 5-pass beam without the <b> beam blocker IN </b>.
+
** Generally, Detector HV OFF but
−
:&bull; If there is any concern about beam stability, ask MCC if orbit locks are on (they should be).
+
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''
−
:&bull; Document any beam condition change and send scaler GUIs to HBLOG.
+
** Turn <b> DC HV </b> off only for beam tuning
−
:&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'''
+
'''Access to the Hall'''
−
:&bull; Make sure the SVT/MVT are set as follows: '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON in SAFE Mode.'''
+
* 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).
−
::- 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'''.
+
* Check in with the shift personnel before entering the hall.
−
::-  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:'''
+
{| {{TableStyle1}}
−
:&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.
 
  
−
|}
+
== <font color=Navy> '''DAQ Operation''' & Related Information </font> ==
  
−
{| {{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:
+
 
 +
<font color=red>'''NEW STANDARD''' end and start of the run:</font>
 
:- "End run"
 
:- "End run"
 
:- "Cancel"
 
:- "Cancel"
 
:- "Reset"
 
:- "Reset"
−
:- "Configure"
 
 
:- "Download"
 
:- "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 168: Line 94:
 
| valign=top |
 
| valign=top |
  
−
* '''Configuration''' is <tt>'''PROD67'''</tt> (or <tt>'''PROD67_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> '''XXX.trg'''</tt>
+
 
−
* 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'''.
+
== <font color=Navy> '''Triggers files'''</font> ==
−
* 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.
 
  
 +
{| 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.
 
|}
 
|}
  
−
== '''Reference Values''' ==
+
== <font color=Navy> '''Reference Values''' </font> ==
 +
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} -->
  
−
=== FSD Thresholds from RG-K ===
+
=== FSD Thresholds ===
 
* Upstream: 2 kHz
 
* Upstream: 2 kHz
 
* Midstream: 2 kHz
 
* Midstream: 2 kHz
Line 193: Line 134:
 
* 5 ms dwell time
 
* 5 ms dwell time
  
−
=== Harp Scan References from RG-K ===
+
=== Nominal Beam Positions ===
−
* 2C21A [https://logbooks.jlab.org/entry/4234734]: x= -0.4 mm; y= +0.6 mm
+
 
−
* Tagger (2C24A) [https://logbooks.jlab.org/entry/4234737]: x= -2.0 mm; y= +0.6 mm
+
'''2C21A''' (not important for production)
−
* 2H01 [https://logbooks.jlab.org/entry/4234764]; x= -1.4 mm; y= 0.0 mm
+
* 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"