Difference between revisions of "Template:ShortTermSchedule-RGE"

Latest revision as of 11:20, 27 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 + Pb
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

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

HWP IN: 4194811 and 4195453
HWP OUT: 4195738 and 4195733

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

@@ Line 1: / Line 1: @@
-'''Run Coordinator: William Brooks '''  (757) 575-7540
+'''Run Coordinator: Taisiya Mineeva '''  (757) 575-7540
 '''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/1605705819 URL Link] ('''''Meeting ID''''': 1605705819'')''', ''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 ==
-* 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.
 * 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 pull down menu to choose where an error is reported.'''
+'''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}}
+| valign=top width=50% |
-{| {{TableStyle1}}
+=== Run Plan ===
+Take production data! Don't break anything!
-| valign=top width=50% |
+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 + Pb
+* Beam Blocker: IN
+* Configuration: <tt>PROD67</tt>
-========= Preparation for Beam after recovery (Wednesday April 10)===========
+In case of the need to manipulate the whole target system - cryotarget or solids - please contact the target experts.
-New Wien angle 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]
-* ALL DETECTORS OFF  (especially the tracking detectors: DC,SVT,MVT,FMT)
+== DC firmware test plan (LD2 + Pb) ==
-* ask MCC to energize the tagger magnet,
-* mask halo counters and BOM in FSD, and move the collimator to the "Blank" position,
-* ask for a 5 nA beam to the tagger dump, rates on upstream halo counters should be ~<1 kHz,
-* perform harp scans, 2C21 first, then the tagger_harp, and compare results with nominals (links are ported on the right side of this page).
-* 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.
-If the beam is not acceptable Eugene asked to be called to help establishing good beam.
+) 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)
+) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_2.trg
-Preparing for the Moller run: Performing Moeller[https://wiki.jlab.org/clas12-run/images/e/e4/Clas12moller.pdf]
+) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_4.trg
-* take the beam away, open the Moller GUI, and follow instructions to configure the Moller polarimeter,
-* 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%
-* repeat the Moller revered Helmholtz field.
+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
-=== Production data taking ===
-* 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.
-LD2+C runs
+== LD2+Pb runs ==
 * 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)
 * 3-hour runs
@@ Line 57: / Line 57: @@
 For information on triggers, please see here: https://logbooks.jlab.org/entry/4267187
-Long term run plan [https://wiki.jlab.org/clas12-run/images/7/70/RG-E_New-Run-Plan.pdf]
+Long term run plan [https://docs.google.com/spreadsheets/d/13CvaWromHWRBfxoPrRsy8AD4omTOl0SQkHT6A3mJbRw/edit#gid=967597323]
 | valign=top |
@@ Line 64: / Line 64: @@
 === 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.
 {| 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)'''
@@ Line 90: / Line 93: @@
 * 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]
+=== Upstream Halo counters ===
+If reading on the upstream halo counters exceeds 10, please, contact MCC.
 |}
@@ Line 113: / Line 119: @@
 :- SVT: LV ON, HV OFF
 :- MVT: LV ON, HV ON in SAFE Mode
-:- All CLAS12 detectors should be off but tracking detectors (above) most critical.
+:- All CLAS12 detectors should be off, tracking detectors (above) most critical.
 * To access the Hall