Difference between revisions of "Template:ShortTermSchedule-RGE"

From clas12-run
Jump to navigation Jump to search
Line 22: Line 22:
  
 
=== Production data taking ===
 
=== Production data taking ===
* Target: LD2 + Pb
+
* Target: LD2 + Sn
 
* Beam Blocker: IN
 
* Beam Blocker: IN
 
* Configuration: <tt>PROD67</tt>
 
* Configuration: <tt>PROD67</tt>
Line 52: Line 52:
 
* Trigger: <tt>rge_inb_v1.0_200MeV.trg</tt>
 
* Trigger: <tt>rge_inb_v1.0_200MeV.trg</tt>
 
* Beam Current: 70 nA
 
* Beam Current: 70 nA
 +
* Use <tt>PROD67</tt> configuration (this will not PIN data)
 +
* 3-hour runs
 +
 +
== 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)
 
* Use <tt>PROD67</tt> configuration (this will not PIN data)
 
* 3-hour runs
 
* 3-hour runs
Line 124: Line 130:
 
:- If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator.
 
:- 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.
 
:- Check in with the shift personnel before entering the hall.
 +
  
 
| valign=top |
 
| valign=top |
Line 143: Line 150:
 
*# Prestart
 
*# Prestart
 
*# Go
 
*# Go
 +
 +
* DAQ instructions
 +
Please make logentry (logbook RICH, notify vpk@jlab.org) with RICH temp and scalers screenshots when you have RICH problems.
 +
You do not need to stop run each time when you are getting 1-2 dead tiles if DAQ is still working, continue data taking. When you will start new run, the dead tiles will recover without your intervention during DAQ Prestart with high probability. If you still have problems, make full RICH recovery and call Valery #5647.
  
 
|}
 
|}

Revision as of 18:34, 29 April 2024

Run Coordinator: Taisiya Mineeva (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 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.

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.

Run Plan

Take production data! Don't break anything!

Keep an eye on the backgrounds, for example as seen in the halo counters, and on the 2C24 and 2H01 BPM positions. Both of these give confidence that the beam remains centered on the RGE target.

Production data taking

  • Target: LD2 + Sn
  • Beam Blocker: IN
  • Configuration: PROD67

In case of the need to manipulate the whole target system - cryotarget or solids - please contact the target experts.


DC firmware test plan (LD2 + Pb)

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

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

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 back the firmware after the last run is finished.

Note:

  • 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

For information on triggers, please see here: https://logbooks.jlab.org/entry/4267187

Long term run plan [1]

References

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.

BPM X (mm) Y (mm)
2C21A -0.4 +0.7
2C24A -1.7 +0.5
2H01 -1.0 +0.25

Harp Scans

FSD Thresholds

Do NOT change FSD settings without approval from RC or beamline expert!

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

Charge Asymmetry

Upstream Halo counters

If 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, tracking detectors (above) 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 logentry (logbook RICH, notify vpk@jlab.org) with RICH temp and scalers screenshots when you have RICH problems. You do not need to stop run each time when you are getting 1-2 dead tiles if DAQ is still working, continue data taking. When you will start new run, the dead tiles will recover without your intervention during DAQ Prestart with high probability. If you still have problems, make full RICH recovery and call Valery #5647.