Difference between revisions of "Template:ShortTermSchedule-RGK"

From clas12-run
Jump to navigation Jump to search
 
(268 intermediate revisions by 3 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: Susan Schadmand'''  (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_s_1613823885&d=DwMFaQ&c=CJqEzB1piLOyyvZjb8YUQw&r=eD2eIWJtzd_0pBXdk6zLEQ&m=aITu0ps9wU_2NIx5HWL0fnCywIAlGV0rhQoEhp3s1SpX6aR3xJ7qrKmdAOhEGyOX&s=ZIcygrMxBgoKIomLBse777fTFeTQobKD2awZ-LaTP1w&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.
−
** 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''';
 
−
** 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.
 
−
** '''Important links'''
 
−
*** '''[[Recent Changes and Current Issues]]'''
 
−
*** '''[[General How-to]]''' for beam restoration procedures and M&oslash;ller runs.
 
  
 +
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.
  
−
{| {{TableStyle1}}  
+
'''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!
  
−
| valign=top width=50% |
+
'''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.
  
−
== '''Run Plan''', '''Tuesday, Jan. 16 - Wednesday, Jan. 17, 2024'''==
+
* 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.
  
−
*'''Tuesday Day/Swing'''
+
=== See tab <font color=red> '''GENERAL INFORMATION''' </font> for ===
−
:: Keep HV for detectors on while we wait for beam to come back.
+
* '''Recent Changes'''
 +
* '''Current Issues'''
 +
* '''Beam Restoration''' (for beam restoration procedures and M&oslash;ller runs)
  
−
*'''Tuesday Swing/Wednesday Owl'''
+
== '''Run Plan: Mar. 10 - Mar. 11, 2024''' ==
−
:: Restore the beam (See manuals on [https://github.com/JeffersonLab/clas12-manuals/raw/master/beamline/manual/beam_estab_rgd.pdf Establishing Physics-Quality Beam], [[Media:clas12moller.pdf|Performing M&oslash;ller Runs]], and [[Media:HarpScanManual.pdf|Performing Harp Scans]] for details)
+
−
::: Turn off (or move to safe) all detector HV
+
'''Production Running ... to the end!!'''
−
::: '''Ask MCC to take out the half-wave plate'''
+
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg
−
::: Steer to tagger dump
+
- Beam current request: 75 nA
−
::: Take a Moller Run
+
- Run duration: 3 hrs
−
::: Steer to FC
 
−
:: Trigger Tests
 
−
::: Notify Valery that trigger tests are about to start.
 
−
::: Take a 10 minute run with trigger rgk_noDC_v1.2_300MeV.trg, PROD67_PIN configuration.
 
−
::: Switch the trigger to rgk_out_v1.1_300MeV.trg. Take a full 200M event run with PROD67_PIN configuration.
 
−
::: Switch the trigger to rgk_noDC_v1.1_300MeV.trg. Take a full 200M event run with PROD67_PIN configuration.
 
−
:: Resume production data with PROD_67 configuration.
 
  
−
''' Taking Production Data '''
+
<font color="red">Note</font>: RG-K run ends on Mar. 11 at 7 a.m.
−
: Trigger is rgk_noDC_v1.1_300MeV.trg ; PROD67 configuration; collect 200M events per run
+
- Turn all detectors off and put BMT HV in safe mode
−
: 65 nA beam current for now, though this may change
+
- Ramp torus and solenoid to zero field (contact Eugene to do this)
−
:: - Keep an eye that R1 DC occupancies are <5%, and DAQ livetime ~90%
+
- Call to put Hall B in Restricted Access
−
:: - <font color=red> Make sure to notate any DC trips in a logbook entry, not just when but '''WHERE''' they occur. </font>
 
−
: - Review all mon12 and Hydra plots throughout the run
 
−
: - Monitor the DAQ rate via strip chart throughout the run and notify the RC if there are any DAQ trigger alarms not due to beam excursions/trips
 
−
: - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
 
  
−
| valign=top width=50% |
+
=== Related Information ===
 +
Find detailed information at tab "GENERAL INFORMATION".
  
−
==<font color=BLACK>''' General Information'''</font>==
+
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights must be OFF during run time.
  
−
* 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'''.  
+
* Orbit locks are on BPMs '''2C24A and 2H01''' and the locks should generally be on ("Running").  
−
** Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]
+
** Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
−
** 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''':
+
* 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.
−
** If there is any concern about beam stability, ask MCC if orbit locks are on (they should be).
+
** The beam position at 2C21A is important for initial beam tuning (on tagger dump).
−
** Document any beam condition change and send scaler GUIs to HBLOG.
 
−
** 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%.
 
  
−
* For '''beam tuning and M&oslash;ller runs'''
+
* 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%.
−
** Make sure the SVT/MVT are set as follows: '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''
 
−
*** From HV &rarr; Overview &rarr; Actions, '''select BMT HV ON - Safe Voltage'''
 
−
*** For Production/Calibration/Various-Studies, select BMT (/FMT) "HV ON - Full Voltage".</font>
 
−
** 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:'''
+
* '''Beam tuning and M&oslash;ller runs'''
−
** 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).
+
** Generally, Detector HV OFF but
−
** Check in with the shift personnel before entering the hall.
+
** '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON - Safe Voltage'''
 +
** Turn <b> DC HV </b> 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.
  
 
{| {{TableStyle1}}
 
{| {{TableStyle1}}
  
−
== <font color=Navy> '''DAQ Operation & Related General Information''' </font> ==  
+
== <font color=Navy> '''DAQ Operation''' & Related Information </font> ==  
 +
 
 
| valign=top width=50% |
 
| valign=top width=50% |
−
* <font color=red>'''NEW STANDARD''' end and start of the run:</font>
+
 
 +
<font color=red>'''NEW STANDARD''' end and start of the run:</font>
 
:- "End run"
 
:- "End run"
 
:- "Cancel"
 
:- "Cancel"
Line 98: Line 81:
 
:- "Prestart"
 
:- "Prestart"
 
:- "Go"
 
:- "Go"
−
This will ensure proper compression of the FADCs and therefore a smaller data rate.
+
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 Fast/Full 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"
 
:- "Cancel"
 
:- "Reset"
 
:- "Reset"
Line 110: 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.
−
** Production running: <tt> '''rgk_noDC_v1.1_300MeV.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'''.
 
−
* 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 shift '''MUST check and reset monitoring histograms at least once every 30-60 minutes''' to identify 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.
 
−
** 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.
 
  
 
|}
 
|}
  
−
== <font color=Navy> '''Glossary of Triggers'''</font> ==
+
== <font color=Navy> '''Triggers files'''</font> ==
  
−
''' Our current default production trigger is rgk_noDC_v1.1_300MeV.trg.'''
 
 
{| class="wikitable"
 
{| class="wikitable"
−
|+ What do the various triggers mean?
 
−
|-
 
−
! Trigger !! Explanation
 
 
|-
 
|-
 
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.
 
| rgk_noDC_v1.0_300MeV.trg || DC roads are not in the trigger. Hold off time is 3 us.
Line 144: Line 125:
  
 
== <font color=Navy> '''Reference Values''' </font> ==
 
== <font color=Navy> '''Reference Values''' </font> ==
 +
<!--- {| {{TableStyle1}} | valign=top width=50% | | valign=top | |} -->
 +
 +
=== FSD Thresholds ===
 +
* Upstream: 2 kHz
 +
* Midstream: 2 kHz
 +
* Downstream: 100 kHz
 +
* BOM: 50 kHz
 +
* 5 ms dwell time
 +
 +
=== Nominal Beam Positions ===
  
−
{| {{TableStyle1}}
+
'''2C21A''' (not important for production)
 +
* x = -0.4 mm
 +
* y = +0.7 mm
  
−
| valign=top width=50% |
+
'''2C24A''' 
 +
* x = -1.7 mm
 +
* y = +0.5 mm
  
−
=== BPM Settings ===
+
'''2H01''' 
 +
* x = -0.7 mm
 +
* y = +0.6 mm
  
−
{| class="wikitable"
+
=== 8.5 GeV Harp Scan References (Feb. 14, 2024) ===
−
|+ Latest settings. If these don't match the white board, call the RC.
 
−
|-
 
−
! BPM !! Coordinate !! Reading (mm)
 
−
|-
 
−
| 2C24A || x || -1.7
 
−
|-
 
−
|  || y || +0.5
 
−
|-
 
−
| 2H01 || x || -0.7
 
−
|-
 
−
| || y || +0.6
 
−
|-
 
−
| 2C21A || x || -0.4
 
−
|-
 
−
|  || y || +0.7
 
−
|}
 
  
−
| valign=top |
+
2C21A: https://logbooks.jlab.org/entry/4252495
  
−
=== FSD Thresholds from RG-K ===
+
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496
−
* Upstream: 2 kHz
 
−
* Midstream: 2 kHz
 
−
* Downstream: 100 kHz
 
−
* BOM: 50 kHz
 
−
* 5 ms dwell time
 
  
−
|}
+
2H01:  https://logbooks.jlab.org/entry/4252514
  
−
=== Harp Scan References from RG-K ===
+
=== 6.4 GeV Harp Scan References (Jan. 18, 2024) ===
  
−
* Tagger (2C24A)
+
2C21A: https://logbooks.jlab.org/entry/4240375
−
** Jan. 12, 2024 Swing (after attempts to improve beam profile): https://logbooks.jlab.org/entry/4238887
 
−
** Jan. 12, 2024 Owl: https://logbooks.jlab.org/entry/4238638 x= -2.0 mm; y= +0.6 mm
 
−
** Compare to Dec 2023: https://logbooks.jlab.org/entry/4238622
 
−
* 2H01
 
−
** Jan. 12, 2024 Swing (after attempts to improve beam profile): https://logbooks.jlab.org/entry/4238889
 
−
** Jan. 12, 2024 Owl: https://logbooks.jlab.org/entry/4238673 x= -1.1 mm; y= 0.6 mm
 
−
** Compare to Dec 2023: https://logbooks.jlab.org/entry/4234764
 
−
* 2C21A  
 
−
** Jan. 12, 2024 Owl: https://logbooks.jlab.org/entry/4238636 x= -0.4 mm; y= +0.6 mm
 
−
** Compare to Dec 2023: https://logbooks.jlab.org/entry/4238636
 
  
−
== <font color=Navy> '''To Do Items'''</font> ==
+
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378
  
−
* Faraday Cup Calibration
+
2H01: https://logbooks.jlab.org/entry/4240397
−
** Rafo can use beam current scan taken from Sat. Jan. 13, during 13:50 - 14:20
 
−
* Empty target running (with full field)
 
−
** Goal is to take > 5% integrated charge, but not until about 2 weeks in
 
−
* Prescale on FC cup trigger
 
−
** Discuss when to study after we have a plan for Tuesday Jan. 16 down time
 

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"