Difference between revisions of "Template:ShortTermSchedule-RGE"

From clas12-run
Jump to navigation Jump to search
m
 
(66 intermediate revisions by 5 users not shown)
Line 1: Line 1:
'''Run Coordinator: William Brooks '''  (757) 575-7540
+
'''Run Coordinator: Sebouh Paul '''  (757) 575-7540
  
 
'''PDL: Nathan Baltzell''' (757) 876-1789, Office: x5902  
 
'''PDL: Nathan Baltzell''' (757) 876-1789, Office: x5902  
Line 7: Line 7:
 
== Important Notes ==
 
== Important Notes ==
 
* In case of medical or fire emergency, call 911 or 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 911 or 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.
+
* 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 can call MCC to turn the beam OFF for 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, the RC, and JLab medical services immediately to arrange replacements.
 +
* <font color=Blue>In case of a problem with the HV Slow Controls, EPICS in general, please call the primary expert on-call, Nathan Baltzell, before reaching out to anyone else.</font>
  
'''Please put all essential information on the main hall B log HBLOG. Some important alarms have been documented on HBRUN. Use the pulldown menu to choose where an error is reported.'''
+
* '''Please put all essential information on the main Hall B logbook HBLOG. Some important alarms have been documented on HBRUN. Use the pulldown menu to choose where an error is reported.'''
  
Tomorrow (Thursday) accel crews will be setting the beam for Hall A we will go to controlled access, and bring magnets down (The Torus ramp down will take about 1 hour.) for cryo tuning and walkthroughs. Short term schedule [https://cebaf.jlab.org/files/ops/accboard/]
+
{| {{TableStyle1}}
  
 +
| valign=top width=50% |
  
{| {{TableStyle1}}
+
== '''Current Run Plan: May 8<sup>th</sup> to May 19<sup>th</sup>''' ==
 +
* Take production data! Don't break anything!
  
| valign=top width=50% |
+
* Keep an eye on the backgrounds, such as in the halo counters and the 2C24A and 2H01 BPM positions. Both give confidence that the beam remains centered on the RG-E target.
  
========= Preparation for Beam after many changes (Friday April 12)===========
+
* See the {{#switchtablink:General_Information|General Information}} tab for specific issues with the detector subsystems.
New Wien angle and other changes and therefore expecting a new tune.
 
  
Therefore when the beam is back, start with beam tuning in the tagger dump:see Establishing beam[https://raw.githubusercontent.com/JeffersonLab/clas12-manuals/master/beamline/manual/beam_estab_rgd.pdf]
+
* If you need to manipulate the whole target system - cryo-target or solid - please contact the target experts.
  
==========  Eugene suggests we should be ready=========
+
* For information on triggers, please see here: https://logbooks.jlab.org/entry/4267187
We can prepare all this now: turn all detectors off and request to energize the tagger magnet.
 
  
* ALL DETECTORS OFF  (especially the tracking detectors: DC,SVT,MVT,FMT)
+
=== '''Lumi Scan for LD2+Pb on May 15<sup>th</sup> - 16<sup>th</sup>''' ===
* Torus and solenoid magnet on (Eugene will do),
+
:<font color=Brown>&bull; Beam Blocker: OUT
* ask MCC to energize the tagger magnet,
+
:&bull; Configuration: <tt>PROD67</tt> (w/o. PIN option)
* mask halo counters and BOM in FSD, and move the collimator to the "Blank" position,
+
:&bull; Trigger: <tt>rge_inb_v1.0_200MeV.trg</tt>
* ask for a 5 nA beam to the tagger dump, rates on upstream halo counters should be ~<1 kHz,
+
:&bull; Take one 5 nA run for 4 hours w/. beam ON
* perform harp scans, 2C21 first, then the tagger_harp, and compare results with nominals (links are ported on the right side of this page).
+
:&bull; Take one 10 nA run for 3 hours w/. beam ON
* If the beam profile and the position (standard deviation and the mean values of the Gaussian fits) are close to the previous tune, ask to take the beam away to prepare for the Moller run. Otherwise, work with MCC OPS to correct beam profiles and positions.
+
:&bull; Take one 20 nA run for 3 hours w/. beam ON
 +
:&bull; Take one 40 nA run for 3 hours w/. beam ON </font>
  
If the beam is not acceptable Eugene asked to be called to help to establish good beam.
+
* <font color=BLUE>Long-term run plan can be found in this link: [https://docs.google.com/spreadsheets/d/13CvaWromHWRBfxoPrRsy8AD4omTOl0SQkHT6A3mJbRw/edit#gid=967597323], and is outlined below:
 +
:# Perform the '''Streaming Readout Test''' (''when possible om May 16<sup>th</sup>; will be coordinated with Sergey'');
 +
:# Take one Empty+Al run @ 70 nA w/. BB for 3 hours;
 +
:# Take one Empty+Empty run @ 200 nA w/. BB for 5 hours (do BB calibration);
 +
:# Reverse the torus magnet polarity and fill the LD2 target;
 +
:# Take outbending data with LD2+C and/or LD2+Pb until the beam is taken away on May 19<sup>th</sup> at 7 a.m. for the accelerator beam studies.</font>
  
 +
== ''Previous Dual-target Configuration Plans'' ==
 +
=== ''- DC firmware test plan (LD2 + Pb)'' ===
  
Preparing for the Moller run: Performing Moeller[https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf]
+
1) Take one run each with 1M events with the trigger files and beam current at 70 nA
* take the beam away, open the Moller GUI, and follow instructions to configure the Moller polarimeter,
+
* rge_inb_v1.0_200MeV_dcrb17_1.trg  : DCRB Threshold (30, 45, 45 nA)
* when ready, ask for a 20 nA beam and start the run. Make sure the ACC/Coinc ratio is <0.1, and the charge asymmetry is <0.2%
+
* rge_inb_v1.0_200MeV_dcrb17_4.trg  : DCRB Threshold (30, 60, 45 nA)
* repeat the Moller reversed Helmholtz field.
+
* rge_inb_v1.0_200MeV_dcrb17_3.trg  : DCRB Threshold (45, 60, 60 nA)
 +
* rge_inb_v1.0_200MeV_dcrb17_2.trg  : DCRB Threshold (30, 30, 30 nA)
  
 +
2) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_2.trg
  
 +
3) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_4.trg
  
=== Production data taking ===
+
:&bull; Before the last run, call DC expert Florian so that he can change the firmware after the last run is finished.
* Target: Yes
 
* Beam Blocker: OUT
 
* Configuration:  <tt>PROD67</tt>
 
  
In case of the need to manipulate the whole target system - cryotarget or solids - please contact the target experts.
+
'''*** Notes ***'''
 +
:&bull; In every step, follow DAQ procedure (End run, Cancel, Reset, Configure, Download, Prestart, Go)
 +
:&bull; For every run please log clas12mon plots from the special version at /usr/clas12/offline/clas12mon/dcrb/bin/mon12
  
LD2+C runs  
+
== ''LD2+Pb runs'' ==
 
* Trigger: <tt>rge_inb_v1.0_200MeV.trg</tt>
 
* Trigger: <tt>rge_inb_v1.0_200MeV.trg</tt>
* Beam Current: 85 nA
+
* Beam Current: 70 nA
 
* Use <tt>PROD67</tt> configuration (this will not PIN data)
 
* Use <tt>PROD67</tt> configuration (this will not PIN data)
 
* 3-hour runs
 
* 3-hour runs
  
For information on triggers, please see here: https://logbooks.jlab.org/entry/4267187
+
== ''LD2+Sn runs'' ==
 +
* Trigger: <tt>rge_inb_v1.0_200MeV.trg</tt>
 +
* Beam Current: 65 nA
 +
* Use <tt>PROD67</tt> configuration (this will not PIN data)
 +
* 3-hour runs
 +
== '' LD2+Al runs'' ==
 +
<!--:<font color=Brown>&bull; Target: LD2 + Al </font-->
 +
:&bull; Beam Blocker: IN
 +
:&bull; Configuration: <tt>PROD67</tt> (w/o. PIN option)
 +
:&bull; Trigger: <tt>rge_inb_v1.0_200MeV.trg</tt>
 +
:&bull; Beam Current: 70 nA
 +
:&bull; 3-hour runs
  
Long term run plan [https://wiki.jlab.org/clas12-run/images/7/70/RG-E_New-Run-Plan.pdf]
+
== ''Lumi Scan for LD2+Al on May 15<sup>th</sup>'' ==
 +
:&bull; Beam Blocker: OUT
 +
:&bull; Configuration: <tt>PROD67</tt> (w/o. PIN option)
 +
:&bull; Trigger: <tt>rge_inb_v1.0_200MeV.trg</tt>
 +
:&bull; Take one 5 nA run for 4 hours
 +
:&bull; Take one 20 nA run for 3 hours
 +
:&bull; Take one 45 nA run until the beam is off for the Hall C 5<sup>th</sup> pass change.
  
 
| valign=top |
 
| valign=top |
  
== References ==
+
== '''References''' ==
  
=== BPM Positions ===
+
=== ''- BPM Positions'' ===
  
The most important BPMs to monitor are 2C24 and 2H01, from the point of view of assuring the beam remains centered on the RGE target. The values of the others can be influenced by other steering/focusing beamline elements.
+
:*The most important <font color=red>'''BPMs to monitor are 2C24A and 2H01'''</font>, from the point of view of assuring the beam remains centered on the RG-E target. Other steering/focusing beamline elements can influence the values of the others.
  
{| class=wikitable cellpadding="10" cellspacing="0" style="border-left:2px solid gray;border-right:2px solid gray;border-bottom:1px solid gray;"
+
:{| class=wikitable cellpadding="10" cellspacing="0" style="border-left:2px solid gray;border-right:2px solid gray;border-bottom:1px solid gray"
 +
!style="background:#ffdead;border-bottom:2px solid gray; border-top:2px solid gray;border-right:2px solid gray" | '''BPM''' || style="border-bottom:2px solid gray; border-top:2px solid gray" | 2C21A || style="border-bottom:2px solid gray; border-top:2px solid gray" | 2C24A || style="border-bottom:2px solid gray; border-top:2px solid gray" | 2H01
 +
|-
 +
| style="background:#ffdead;border-bottom:2px solid gray;border-top:2px solid gray;border-right:2px solid gray" | '''X (mm)''' || -0.4 || -1.7 || -1.0
 +
|-
 +
| style="background:#ffdead;border-bottom:2px solid gray;border-top:2px solid gray;border-right:2px solid gray" | '''Y (mm)'''|| style="border-bottom:2px solid gray"|+0.7 || style="border-bottom:2px solid gray"|+0.5 || style="border-bottom:2px solid gray"|+0.25
 +
|-
 +
|}
 +
<!--:{| class=wikitable cellpadding="10" cellspacing="0" style="border-left:2px solid gray;border-right:2px solid gray;border-bottom:1px solid gray;"
 
!style="background:#ffdead;border-bottom:2px solid gray; border-top:2px solid gray" | '''BPM''' ||style="background:#ffdead;border-bottom:2px solid gray;border-top:2px solid gray" | '''X (mm)''' ||style="background:#ffdead;border-bottom:2px solid gray;border-top:2px solid gray" | '''Y (mm)'''  
 
!style="background:#ffdead;border-bottom:2px solid gray; border-top:2px solid gray" | '''BPM''' ||style="background:#ffdead;border-bottom:2px solid gray;border-top:2px solid gray" | '''X (mm)''' ||style="background:#ffdead;border-bottom:2px solid gray;border-top:2px solid gray" | '''Y (mm)'''  
 
|-
 
|-
Line 78: Line 114:
 
|-
 
|-
 
|style="border-bottom:2px solid gray;" | 2H01 ||style="border-bottom:2px solid gray;"| -1.0 ||style="border-bottom:2px solid gray;"| +0.25
 
|style="border-bottom:2px solid gray;" | 2H01 ||style="border-bottom:2px solid gray;"| -1.0 ||style="border-bottom:2px solid gray;"| +0.25
|}
+
|}-->
 
+
=== ''- Harp Scans'' ===
=== Harp Scans ===
 
 
* [https://logbooks.jlab.org/entry/4268480 2C21A]
 
* [https://logbooks.jlab.org/entry/4268480 2C21A]
 
* [https://logbooks.jlab.org/entry/4268530 2C24A/Tagger]
 
* [https://logbooks.jlab.org/entry/4268530 2C24A/Tagger]
 
* [https://logbooks.jlab.org/entry/4268606 2H01]
 
* [https://logbooks.jlab.org/entry/4268606 2H01]
  
=== FSD Thresholds ===
+
=== ''- FSD Thresholds'' ===
'''Do NOT change FSD settings without approval from RC or beamline expert!'''
+
:* '''Do NOT change FSD settings without approval from RC or beamline expert!'''
* Upstream: 2 kHz
+
::&bull; Upstream: 2 kHz
* Midstream: 2 kHz
+
::&bull; Midstream: 3 kHz
* Downstream: 100 kHz
+
::&bull; Downstream: 150 kHz
* BOM: 50 kHz
+
::&bull; BOM: 50 kHz
* 5 ms dwell time
+
::&bull; 5 ms dwell time
  
=== Charge Asymmetry ===
+
=== ''- Charge Asymmetry'' ===
 
* HWP IN: [https://logbooks.jlab.org/entry/4194811 4194811] and [https://logbooks.jlab.org/entry/4195453 4195453]
 
* HWP IN: [https://logbooks.jlab.org/entry/4194811 4194811] and [https://logbooks.jlab.org/entry/4195453 4195453]
 
* HWP OUT: [https://logbooks.jlab.org/entry/4195738 4195738] and [https://logbooks.jlab.org/entry/4195733 4195733]
 
* HWP OUT: [https://logbooks.jlab.org/entry/4195738 4195738] and [https://logbooks.jlab.org/entry/4195733 4195733]
 +
 +
=== ''- Upstream Halo counters'' ===
 +
* If the reading on the upstream halo counters exceeds 10, please contact MCC.
  
 
|}
 
|}
Line 103: Line 141:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
== General Reminders ==
+
== '''General Reminders''' ==
  
 
* The main lights in the Hall and the Forward Carriage lights must be kept off during data taking.
 
* The main lights in the Hall and the Forward Carriage lights must be kept off during data taking.
:- Refer to these reference photos, [https://logbooks.jlab.org/entry/3825712 ON] and [https://logbooks.jlab.org/entry/3825731 OFF]
+
:&bull; Refer to these reference photos, [https://logbooks.jlab.org/entry/3825712 ON] and [https://logbooks.jlab.org/entry/3825731 OFF]
:- The main, dome lights can be [https://logbooks.jlab.org/entry/4204460 turned off without entering the Hall].
+
:&bull; The main, dome lights can be [https://logbooks.jlab.org/entry/4204460 turned off without entering the Hall].
  
 
* Beamline
 
* Beamline
:- Do not run over 30 minutes above 90 nA with a 5-pass beam without the beam blocker IN.
+
:&bull; Do not run over 30 minutes above 90 nA with a 5-pass beam without the beam blocker IN.
:- If there is any concern about beam stability, ask MCC if orbit locks are on (they should be).
+
:&bull; 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.
+
:&bull; Document any beam condition change and send scaler GUIs to HBLOG.
:- If HWP is changed, start a new run.
+
:&bull; If HWP is changed, start a new run.
  
 
* During beam tuning and M&oslash;ller runs
 
* During beam tuning and M&oslash;ller runs
:- DC:  HV OFF
+
:&bull; DC:  HV OFF
:- SVT: LV ON, HV OFF
+
:&bull; SVT: LV ON, HV OFF
:- MVT: LV ON, HV ON in SAFE Mode
+
:&bull; MVT: LV ON, HV ON in SAFE Mode
:- All CLAS12 detectors should be off but tracking detectors (above) most critical.
+
:&bull; All CLAS12 detectors should be OFF; aforementioned tracking detectors are the most critical.
  
 
* To access the Hall
 
* 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.
+
:&bull; If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator.
:- Check in with the shift personnel before entering the hall.
+
:&bull; Check in with the shift personnel before entering the hall.
 +
 
  
 
| valign=top |
 
| valign=top |
  
== DAQ Operation ==  
+
== '''DAQ Operation''' ==  
 
* Standard end and start of a run
 
* Standard end and start of a run
 
*# End run
 
*# End run
Line 136: Line 175:
  
 
* Restart DAQ from scratch
 
* Restart DAQ from scratch
** e.g., when changing configuration or trigger files, when the run did not end correctly, or after ROCs are rebooted
+
:&bull; E.g., when changing configuration or trigger files, when the run did not end correctly, or after ROCs are rebooted
*# Cancel
+
:# Cancel
*# Reset
+
:# Reset
*# Configure
+
:# Configure
*# Download
+
:# Download
*# Prestart
+
:# Prestart
*# Go
+
:# Go
 +
 
 +
* DAQ instructions
 +
:&bull; Please make a log entry (logbook RICH, notify vpk@jlab.org) with RICH temp and scalers screenshots when you have RICH problems.
 +
:&bull; You do not need to stop the run each time you get 1-2 dead tiles if DAQ is still working. Continue data taking. When you start a new run, the dead tiles will recover without your intervention during DAQ Prestart with a high probability. If you still have problems, make a full RICH recovery and call Valery #5647.
  
 
|}
 
|}

Latest revision as of 21:51, 15 May 2024

Run Coordinator: Sebouh Paul (757) 575-7540

PDL: Nathan Baltzell (757) 876-1789, Office: x5902

Daily RC Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1605705819), except on Wednesdays, which is @ 15:00 in CH Room 200C and at the same ZOOM link.

Important Notes

  • In case of medical or fire emergency, call 911 or 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 can call MCC to turn the beam OFF for 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, the RC, and JLab medical services immediately to arrange replacements.
  • In case of a problem with the HV Slow Controls, EPICS in general, please call the primary expert on-call, Nathan Baltzell, before reaching out to anyone else.
  • Please put all essential information on the main Hall B logbook HBLOG. Some important alarms have been documented on HBRUN. Use the pulldown menu to choose where an error is reported.

Current Run Plan: May 8th to May 19th

  • Take production data! Don't break anything!
  • Keep an eye on the backgrounds, such as in the halo counters and the 2C24A and 2H01 BPM positions. Both give confidence that the beam remains centered on the RG-E target.
  • If you need to manipulate the whole target system - cryo-target or solid - please contact the target experts.

Lumi Scan for LD2+Pb on May 15th - 16th

• Beam Blocker: OUT
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Take one 5 nA run for 4 hours w/. beam ON
• Take one 10 nA run for 3 hours w/. beam ON
• Take one 20 nA run for 3 hours w/. beam ON
• Take one 40 nA run for 3 hours w/. beam ON
  • Long-term run plan can be found in this link: [1], and is outlined below:
  1. Perform the Streaming Readout Test (when possible om May 16th; will be coordinated with Sergey);
  2. Take one Empty+Al run @ 70 nA w/. BB for 3 hours;
  3. Take one Empty+Empty run @ 200 nA w/. BB for 5 hours (do BB calibration);
  4. Reverse the torus magnet polarity and fill the LD2 target;
  5. Take outbending data with LD2+C and/or LD2+Pb until the beam is taken away on May 19th at 7 a.m. for the accelerator beam studies.

Previous Dual-target Configuration Plans

- DC firmware test plan (LD2 + Pb)

1) Take one run each with 1M events with the trigger files and beam current at 70 nA

  • rge_inb_v1.0_200MeV_dcrb17_1.trg : DCRB Threshold (30, 45, 45 nA)
  • rge_inb_v1.0_200MeV_dcrb17_4.trg : DCRB Threshold (30, 60, 45 nA)
  • rge_inb_v1.0_200MeV_dcrb17_3.trg : DCRB Threshold (45, 60, 60 nA)
  • rge_inb_v1.0_200MeV_dcrb17_2.trg : DCRB Threshold (30, 30, 30 nA)

2) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_2.trg

3) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_4.trg

• Before the last run, call DC expert Florian so that he can change the firmware after the last run is finished.

*** Notes ***

• In every step, follow DAQ procedure (End run, Cancel, Reset, Configure, Download, Prestart, Go)
• For every run please log clas12mon plots from the special version at /usr/clas12/offline/clas12mon/dcrb/bin/mon12

LD2+Pb runs

  • Trigger: rge_inb_v1.0_200MeV.trg
  • Beam Current: 70 nA
  • Use PROD67 configuration (this will not PIN data)
  • 3-hour runs

LD2+Sn runs

  • Trigger: rge_inb_v1.0_200MeV.trg
  • Beam Current: 65 nA
  • Use PROD67 configuration (this will not PIN data)
  • 3-hour runs

LD2+Al runs

• Beam Blocker: IN
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Beam Current: 70 nA
• 3-hour runs

Lumi Scan for LD2+Al on May 15th

• Beam Blocker: OUT
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Take one 5 nA run for 4 hours
• Take one 20 nA run for 3 hours
• Take one 45 nA run until the beam is off for the Hall C 5th pass change.

References

- BPM Positions

  • The most important BPMs to monitor are 2C24A and 2H01, from the point of view of assuring the beam remains centered on the RG-E target. Other steering/focusing beamline elements can influence the values of the others.
BPM 2C21A 2C24A 2H01
X (mm) -0.4 -1.7 -1.0
Y (mm) +0.7 +0.5 +0.25

- Harp Scans

- FSD Thresholds

  • Do NOT change FSD settings without approval from RC or beamline expert!
• Upstream: 2 kHz
• Midstream: 3 kHz
• Downstream: 150 kHz
• BOM: 50 kHz
• 5 ms dwell time

- Charge Asymmetry

- Upstream Halo counters

  • If the reading on the upstream halo counters exceeds 10, please contact MCC.

General Reminders

  • The main lights in the Hall and the Forward Carriage lights must be kept off during data taking.
• Refer to these reference photos, ON and OFF
• The main, dome lights can be turned off without entering the Hall.
  • Beamline
• Do not run over 30 minutes above 90 nA with a 5-pass beam without the beam blocker IN.
• 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.
  • During beam tuning and Møller runs
• DC: HV OFF
• SVT: LV ON, HV OFF
• MVT: LV ON, HV ON in SAFE Mode
• All CLAS12 detectors should be OFF; aforementioned tracking detectors are the most critical.
  • 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.
• Check in with the shift personnel before entering the hall.


DAQ Operation

  • Standard end and start of a run
    1. End run
    2. Abort
    3. Download
    4. Prestart
    5. "Go"
  • Restart DAQ from scratch
• E.g., when changing configuration or trigger files, when the run did not end correctly, or after ROCs are rebooted
  1. Cancel
  2. Reset
  3. Configure
  4. Download
  5. Prestart
  6. Go
  • DAQ instructions
• Please make a log entry (logbook RICH, notify vpk@jlab.org) with RICH temp and scalers screenshots when you have RICH problems.
• You do not need to stop the run each time you get 1-2 dead tiles if DAQ is still working. Continue data taking. When you start a new run, the dead tiles will recover without your intervention during DAQ Prestart with a high probability. If you still have problems, make a full RICH recovery and call Valery #5647.