Difference between revisions of "Template:ShortTermSchedule-RGE"

From clas12-run
Jump to navigation Jump to search
 
(109 intermediate revisions by 10 users not shown)
Line 1: Line 1:
'''Run Coordinator: Hayk Hakobyan'''  (757) 575-7540
+
'''Run Coordinator: Lamiaa El Fassi '''  (757) 575-7540
  
 
'''PDL: Nathan Baltzell''' (757) 876-1789, Office: x5902  
 
'''PDL: Nathan Baltzell''' (757) 876-1789, Office: x5902  
  
<center>Daily RC Meetings at 13:00 in CH Room 200C, and on ZOOM: [https://jlab-org.zoomgov.com/j/1602110826?pwd=UzM5dHZ4bWZUNkJBc3NLUitod1pXZz09 URL Link] ('''''Meeting ID''''': 1602110826; '''''Passcode''''': 650675)''', ''except on '''Wednesdays''', which is '''on ZOOM ONLY @ 15:30.</center>
+
<center>Daily RC Meetings at 13:00 in CH Room 200C, and on ZOOM: [https://jlab-org.zoomgov.com/j/1605705819 URL Link] ('''''Meeting ID''''': 1605705819'')''', ''except on '''Wednesdays''', which is ''' @ 15:00 in CH Room 200C and at the same ZOOM link. </center>
  
 
== Important Notes ==
 
== Important Notes ==
* 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 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.'''
  
 
{| {{TableStyle1}}  
 
{| {{TableStyle1}}  
Line 14: Line 17:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
== Friday, March 15 - Monday, March 18 ==
+
== '''Current Run Plan: May 8<sup>th</sup> to May 15<sup>th</sup>''' ==
* Target: Yes
+
* Take production data! Don't break anything!
* Beam Blocker: OUT
 
* Trigger:  <tt>rge-asdf.trg</tt>
 
* Configuration:  <tt>PROD67</tt>
 
  
''''''
+
* Keep an eye on the backgrounds, such as in the halo counters and the 2C24 and 2H01 BPM positions. Both of these give confidence that the beam remains centered on the RGE target.
== Special Test Runs: ==
 
  
'''
+
* See the General Information tab for specific issues with the detector subsystems.
  
'''Cryocell Empty & PIN data to cache for fast cooking:
+
=== '''Production data taking: LD2+Al runs''' ===
'''
+
:- <font color=Brown>Target: LD2 + Al
 +
:- Beam Blocker: IN
 +
:- Configuration: <tt>PROD67</tt> (w/o. PIN option)
 +
:- Trigger: <tt>rge_inb_v1.0_200MeV.trg</tt>
 +
:- Beam Current: 70 nA
 +
:- 3-hour runs</font>
  
1. Double Target system alignment with all solid targets successively on beam position: app. 12 hrs
+
* If you need to manipulate the whole target system - cryotarget or solids - please contact the target experts.
  
2. Trigger validation: with random trigger: app. 4 hrs
+
* For information on triggers, please see here: https://logbooks.jlab.org/entry/4267187
  
3. Trigger validation: no DC-roads electron trigger: app 1 hrs
+
* Long-term run plan can be found in this link: [https://docs.google.com/spreadsheets/d/13CvaWromHWRBfxoPrRsy8AD4omTOl0SQkHT6A3mJbRw/edit#gid=967597323], which will be updated based on the following May 8<sup>th</sup> RC meeting discussion:
 +
:- ''Luminosity scan for LD2+Al'': Take runs at various beam currents scanning the range from 5 nA to 70 nA with a 15 nA step.  
 +
:- Take more runs at low current for LD2+Pb, if the time allows, once the LD2+Al production runs are completed! 
 +
:- Perform the '''Streaming Readout Test''', which could be done in parallel with reversing the torus magnet polarity. The latter will be considered if the LD2+Al production runs are completed.
 +
:- Take data with the outbending configuration with the to-be-determined dual-target configuration if the LD2+Al inbending production runs are completed.
  
4. PMT gain/HV calibrations for CND/CTOF/ECAL/FTOF with 75M events: app. 4 hrs
+
== ''Previous Dual-target Configuration Plans'' ==
 +
=== ''- DC firmware test plan (LD2 + Pb)'' ===
  
5. Zero field alignment run with empty cryotarget, 10M electron triggers with ~3nA current, just before/after a scheduled down time for torus/solenoid ramping: app. 4 hrs
+
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)
  
6. Empty cryotarget run with C on: app. 16 hrs
+
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.
 +
 +
'''*** 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: <tt>rge_inb_v1.0_200MeV.trg</tt>
 +
* 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)
 +
* 3-hour runs
  
 
| valign=top |
 
| valign=top |
  
== References ==
+
== '''References''' ==
  
=== BPM Positions ===
+
=== ''- BPM Positions'' ===
''Note, these are currently copied from RG-K.''
+
 
* 2C21A:  x/y = -0.4/+0.7 mm
+
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.
* 2C24A/Tagger:  x/y = -1.7/+0.5 mm
 
* 2H01:  x/y = -0.7/+0.6 mm
 
  
 
{| 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;"
Line 58: Line 88:
 
| 2C24A || -1.7 || +0.5
 
| 2C24A || -1.7 || +0.5
 
|-
 
|-
|style="border-bottom:2px solid gray;" | 2H01 ||style="border-bottom:2px solid gray;"| -0.7 ||style="border-bottom:2px solid gray;"| +0.6
+
|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'' ===
''Note, these are currently copied from RG-K.''
+
* [https://logbooks.jlab.org/entry/4268480 2C21A]
* [https://logbooks.jlab.org/entry/4122116 2C21A]
+
* [https://logbooks.jlab.org/entry/4268530 2C24A/Tagger]
* [https://logbooks.jlab.org/entry/4191955 2C24A/Tagger]
+
* [https://logbooks.jlab.org/entry/4268606 2H01]
* [https://logbooks.jlab.org/entry/4192230 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
 
* Upstream: 2 kHz
* Midstream: 2 kHz
+
* Midstream: 3 kHz
* Downstream: 100 kHz
+
* Downstream: 150 kHz
 
* BOM: 50 kHz
 
* BOM: 50 kHz
 
* 5 ms dwell time
 
* 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 85: Line 117:
 
| 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.
Line 92: Line 124:
  
 
* Beamline
 
* Beamline
:- Do not run over XX minutes above YY nA with a 5-pass beam without the beam blocker IN.
+
:- 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).
 
:- 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.
 
:- Document any beam condition change and send scaler GUIs to HBLOG.
Line 101: Line 133:
 
:- SVT: LV ON, HV OFF
 
:- SVT: LV ON, HV OFF
 
:- MVT: LV ON, HV ON in SAFE Mode
 
:- MVT: LV ON, HV ON in SAFE Mode
 +
:- All CLAS12 detectors should be off, tracking detectors (above) 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.
 
:- 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 |
  
== DAQ Operation ==  
+
== '''DAQ Operation''' ==  
 
* Standard end and start of a run
 
* Standard end and start of a run
 
*# End run
 
*# End run
Line 124: Line 158:
 
*# Prestart
 
*# Prestart
 
*# Go
 
*# 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.
  
 
|}
 
|}

Latest revision as of 18:59, 8 May 2024

Run Coordinator: Lamiaa El Fassi (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 log 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 15th

  • Take production data! Don't break anything!
  • Keep an eye on the backgrounds, such as in the halo counters and the 2C24 and 2H01 BPM positions. Both of these give confidence that the beam remains centered on the RGE target.
  • See the General Information tab for specific issues with the detector subsystems.

Production data taking: LD2+Al runs

- Target: LD2 + Al
- Beam Blocker: IN
- Configuration: PROD67 (w/o. PIN option)
- Trigger: rge_inb_v1.0_200MeV.trg
- Beam Current: 70 nA
- 3-hour runs
  • If you need to manipulate the whole target system - cryotarget or solids - please contact the target experts.
  • Long-term run plan can be found in this link: [1], which will be updated based on the following May 8th RC meeting discussion:
- Luminosity scan for LD2+Al: Take runs at various beam currents scanning the range from 5 nA to 70 nA with a 15 nA step.
- Take more runs at low current for LD2+Pb, if the time allows, once the LD2+Al production runs are completed!
- Perform the Streaming Readout Test, which could be done in parallel with reversing the torus magnet polarity. The latter will be considered if the LD2+Al production runs are completed.
- Take data with the outbending configuration with the to-be-determined dual-target configuration if the LD2+Al inbending production runs are completed.

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.

*** 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

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: 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, 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 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.