Difference between revisions of "Template:ShortTermSchedule-RGE"

From clas12-run
Jump to navigation Jump to search
 
(42 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''Run Coordinator: Lamiaa El Fassi ''' (757) 575-7540
+
'''Run Coordinator: Sebouh Paul ''' (757) 575-7540  
 +
 
 +
'''Current RP Coordinator: Lamiaa El Fassi'''
  
 
'''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/1605705819 URL Link] ('''''Meeting ID''''': 1605705819'')''', ''except on '''Wednesdays''', which is ''' @ 15:00 in CH Room 200C and at the same ZOOM link. </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 via the same ZOOM link. </center>
  
== 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 can call MCC to turn the beam OFF for 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.
Line 11: Line 13:
 
* <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>
 
* <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.'''
  
 
{| {{TableStyle1}}  
 
{| {{TableStyle1}}  
Line 17: Line 19:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
== '''Current Run Plan: May 8<sup>th</sup> to May 19<sup>th</sup>''' ==
+
== '''Current Run Plan: May 18<sup>th</sup> to May 19<sup>th</sup>''' ==
 
* Take production data! Don't break anything!
 
* 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.
+
* 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.
  
* See the {{#switchtablink:General_Information|General_Information}} tab for specific issues with the detector subsystems.
+
* See the {{#switchtablink:General_Information|General Information}} tab for specific issues with the detector subsystems.
  
 
* If you need to manipulate the whole target system - cryo-target or solid - please contact the target experts.
 
* If you need to manipulate the whole target system - cryo-target or solid - please contact the target experts.
Line 28: Line 30:
 
* For information on triggers, please see here: https://logbooks.jlab.org/entry/4267187
 
* For information on triggers, please see here: https://logbooks.jlab.org/entry/4267187
  
=== '''Lumi Scan for LD2+Al on May 15<sup>th</sup>''' ===
+
* Long-term run plan was also highlighted in this [https://docs.google.com/spreadsheets/d/13CvaWromHWRBfxoPrRsy8AD4omTOl0SQkHT6A3mJbRw/edit#gid=967597323 RG-E Calendar link]
  
:<font color=Brown>&bull; Beam Blocker: OUT
+
=== '''Outbending Configuration Runs''' ===
 +
:<font color=Brown>&bull; Beam Blocker: IN
 +
:&bull; Beam Current: 70 nA
 +
:&bull; Target: LD2+Pb
 
:&bull; Configuration: <tt>PROD67</tt> (w/o. PIN option)
 
:&bull; Configuration: <tt>PROD67</tt> (w/o. PIN option)
:&bull; Take one 5 nA run for 4 hours
+
:&bull; Trigger: <tt>rge_noDC_v1.0_300MeV.trg</tt>
:&bull; Take one 20 nA run for 3 hours
+
:&bull; 3-hour or 100 M events run, whatever comes first!</font>
:&bull; Take one 45 nA run for 1.5 hours
 
 
 
:&bull; P.S.: ''Still waiting for the verdict from Hall C on whether they will perform their 5<sup>th</sup> pass change tomorrow or Thursday morning, as that will slightly affect the sequence of our planned run plan activities''. </font>
 
  
* <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:  
+
<!--and is outlined below::# Take outbending data with LD2+C, then LD2+Pb until the beam is taken away on May 19<sup>th</sup> at 7 a.m. for the accelerator beam studies.-->
<!--:&bull; ''Luminosity scan for LD2+Al'': Take runs at various beam currents spanning the range from 5 nA to 70 nA with a 15 nA step.-->
 
:# Conduct Lumi. scan for LD2+Pb at 5 nA (~ 4h), 10 nA (~ 4h), 20 nA (~ 3h), and 40 nA (~ 2h)
 
:# Perform the '''Streaming Readout Test'''
 
:# 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 down on May 19<sup>th</sup> at 7 a.m.</font>
 
  
 
== ''Previous Dual-target Configuration Plans'' ==
 
== ''Previous Dual-target Configuration Plans'' ==
=== ''- DC firmware test plan (LD2 + Pb)'' ===
+
<big>''- DC firmware test plan (LD2+Pb):''</big>
  
 
1) Take one run each with 1M events with the trigger files and beam current at 70 nA
 
1) Take one run each with 1M events with the trigger files and beam current at 70 nA
Line 77: Line 72:
 
* 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
== '' LD2+Al runs'' ===
+
== '' LD2+Al runs'' ==
 
<!--:<font color=Brown>&bull; Target: LD2 + Al </font-->
 
<!--:<font color=Brown>&bull; Target: LD2 + Al </font-->
 
:&bull; Beam Blocker: IN
 
:&bull; Beam Blocker: IN
Line 84: Line 79:
 
:&bull; Beam Current: 70 nA
 
:&bull; Beam Current: 70 nA
 
:&bull; 3-hour runs
 
:&bull; 3-hour runs
 +
 +
== ''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 w/. beam ON
 +
:&bull; Take one 10 nA run for 6 hours w/. beam ON
 +
:&bull; Take one 20 nA run for 3 hours w/. beam ON
 +
:&bull; Take one 45 nA run for 3 hours w/. beam ON
 +
 +
== ''Lumi Scan for LD2+Pb on May 15<sup>th</sup> - 16<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 w/. beam ON
 +
:&bull; Take one 10 nA run for 3 hours w/. beam ON
 +
:&bull; Take one 20 nA run for 3 hours w/. beam ON
 +
:&bull; Take one 40 nA run for 3 hours w/. beam ON
 +
:&bull; Take one 55 nA run for 3 hours w/. beam ON
 +
 +
== ''Streaming Readout Test'' ==
 +
:&bull; Performed in coordination with Sergey and David Lawrence (''Done from 9 to 11 a.m. on May 16<sup>th</sup>'').
 +
 +
== ''Empty-target runs on May 16<sup>th</sup> - 17<sup>th</sup>'' ==
 +
:&bull; Beam Blocker: IN
 +
:&bull; Configuration: <tt>PROD67</tt> (w/o. PIN option)
 +
:&bull; Trigger: <tt>rge_inb_v1.0_200MeV.trg</tt>
 +
:&bull; Take one Empty+Al run @ 70 nA w/. BB for 5 hours (w/. Beam ON)
 +
:&bull; Take one Empty+Wire run @ 200 nA w/. BB for approx. 8 hours (''BB calibration is done by Rafo and Lamiaa/MCC OPS over phone'')
 +
 +
== ''Outbending Configuration Runs'' on May 17<sup>th</sup> - 19<sup>th</sup>'' ===
 +
:&bull; Beam Blocker: IN
 +
:&bull; Beam Current: 70 nA
 +
:&bull; Target: LD2+C
 +
:&bull; Configuration: <tt>PROD67</tt> (w/o. PIN option)
 +
:&bull; Trigger: <tt>rge_noDC_v1.0_300MeV.trg</tt>, or
 +
::&diams; Trigger: <tt>rge_noDC_v1.0_200MeV.trg</tt>, and Beam Current: 60 nA or
 +
::&diams; Trigger: <tt>rge_noDC_v1.0_250MeV.trg</tt>, and Beam Current: 65 nA
 +
:&bull; 3-hour or 100 M events run, whatever comes first!
  
 
| valign=top |
 
| valign=top |
Line 93: Line 127:
 
:*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.
 
:*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 101: Line 143:
 
|-
 
|-
 
|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]
Line 136: Line 177:
  
 
* Beamline
 
* Beamline
:&bull; 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 ('''''50 nA for now while studying FCup behavior''''') with a 5-pass beam without the beam blocker IN.
 
:&bull; 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).
 
:&bull; Document any beam condition change and send scaler GUIs to HBLOG.
 
:&bull; Document any beam condition change and send scaler GUIs to HBLOG.

Latest revision as of 18:44, 18 May 2024

Run Coordinator: Sebouh Paul (757) 575-7540

Current RP Coordinator: Lamiaa El Fassi

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 via 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 18th 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.

Outbending Configuration Runs

• Beam Blocker: IN
• Beam Current: 70 nA
• Target: LD2+Pb
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_noDC_v1.0_300MeV.trg
• 3-hour or 100 M events run, whatever comes first!


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 w/. beam ON
• Take one 10 nA run for 6 hours w/. beam ON
• Take one 20 nA run for 3 hours w/. beam ON
• Take one 45 nA run for 3 hours w/. beam ON

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
• Take one 55 nA run for 3 hours w/. beam ON

Streaming Readout Test

• Performed in coordination with Sergey and David Lawrence (Done from 9 to 11 a.m. on May 16th).

Empty-target runs on May 16th - 17th

• Beam Blocker: IN
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_inb_v1.0_200MeV.trg
• Take one Empty+Al run @ 70 nA w/. BB for 5 hours (w/. Beam ON)
• Take one Empty+Wire run @ 200 nA w/. BB for approx. 8 hours (BB calibration is done by Rafo and Lamiaa/MCC OPS over phone)

Outbending Configuration Runs on May 17th - 19th =

• Beam Blocker: IN
• Beam Current: 70 nA
• Target: LD2+C
• Configuration: PROD67 (w/o. PIN option)
• Trigger: rge_noDC_v1.0_300MeV.trg, or
♦ Trigger: rge_noDC_v1.0_200MeV.trg, and Beam Current: 60 nA or
♦ Trigger: rge_noDC_v1.0_250MeV.trg, and Beam Current: 65 nA
• 3-hour or 100 M events run, whatever comes first!

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 (50 nA for now while studying FCup behavior) 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.