Difference between revisions of "Template:ShortTermSchedule-RGE"

From clas12-run
Jump to navigation Jump to search
 
(223 intermediate revisions by 10 users not shown)
Line 1: Line 1:
'''Run Coordinator: Hayk Hakyoban''' (757) 575-7540
+
'''Run Coordinator: Sebouh Paul ''' (757) 575-7540  
  
''' PDL: Nathan Baltzell''' (9-) 757 876-1789; ''Office'': x5902
+
'''Current RP Coordinator: Lamiaa El Fassi'''  
  
''' [https://clasweb.jlab.org/wiki/index.php/Run_Group_D#tab=Daily_RC/OA_Meetings Daily RC/OA Meetings] at 13:00 in CH Room 200C, and on ZOOM: [https://jlab-org.zoomgov.com/j/1611984219?pwd=MnZMM0pDdzhlUnlOR2c3MnRFUlFqQT09 URL Link] ('''''Meeting ID''''': 1611984219; '''''Passcode''''': RGD-RC23)''', ''except on '''Wednesdays''', which is '''on ZOOM ONLY @ 15:30'''.
+
'''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 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.
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span>
+
* 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, 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>
  
* '''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.
+
* '''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.'''
* '''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.
 
  
 
{| {{TableStyle1}}  
 
{| {{TableStyle1}}  
Line 17: Line 19:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
== '''Run Plan''', '''Monday, Nov. 20<sup>th</sup> - Monday, Dec. 4<sup>th</sup>, 2023'''==
+
== '''Current Run Plan: May 18<sup>th</sup> to May 19<sup>th</sup>''' ==
 +
* 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.
 +
 
 +
* 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.
 +
 
 +
* For information on triggers, please see here: https://logbooks.jlab.org/entry/4267187
 +
 
 +
* Long-term run plan was also highlighted in this [https://docs.google.com/spreadsheets/d/13CvaWromHWRBfxoPrRsy8AD4omTOl0SQkHT6A3mJbRw/edit#gid=967597323 RG-E Calendar link]
  
* Continue CuSn data-taking as follows:
+
=== '''Outbending Configuration Runs''' ===
:- Target: '''CuSn'''
+
:<font color=Brown>&bull; Beam Blocker: IN
:- Beam Blocker: '''IN'''
+
:&bull; Beam Current: 70 nA
 +
:&bull; Target: LD2+Pb
 +
:&bull; Configuration: <tt>PROD67</tt> (w/o. PIN option)
 +
:&bull; Trigger: <tt>rge_noDC_v1.0_300MeV.trg</tt>
 +
:&bull; 3-hour or 100 M events run, whatever comes first!</font>
 +
 
 +
<!--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.-->
 +
 
 +
== ''Previous Dual-target Configuration Plans'' ==
 +
<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
 +
* 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
 +
 
 +
:&bull; Before the last run, call DC expert Florian so that he can change the firmware after the last run is finished.
 +
 
 +
'''*** 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+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
 +
== '' 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
 +
 
 +
== ''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 |
  
==<font color=BLACK>''' General Instructions'''</font>==
+
== '''References''' ==
  
* The <b> main lights in the Hall </b> (dome lights) and the Forward Carriage lights are being kept off because of light leaks affecting some of the detectors (especially ECAL sec 2 and 3). If these lights are switched on during an access, they '''should be switched off when leaving the Hall'''.
+
=== ''- BPM Positions'' ===
** Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]
 
** We have a new dome light switch outside of the hall in the labyrinth. The lights can be turned off without entering the Hall. See logbook entry: https://logbooks.jlab.org/entry/4204460
 
** Note that when the dome lights are switched off, they cannot be turned back on immediately because they require 10-15 min to cool down.
 
  
* '''Beamline''':
+
:*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.
:&bull; Do not run over XX minutes above YY nA with a 5-pass beam without the <b> beam blocker IN </b>. The beam blocker must be IN for long-running at high currents for 5-pass operations.
+
 
:&bull; If there is any concern about beam stability, ask MCC if orbit locks are on (they should be).
+
:{| class=wikitable cellpadding="10" cellspacing="0" style="border-left:2px solid gray;border-right:2px solid gray;border-bottom:1px solid gray"
:&bull; Document any beam condition change and send scaler GUIs to HBLOG.
+
!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
:&bull; If HWP is changed, start a new run:
+
|-
 +
| 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)'''
 +
|-
 +
| 2C21A || -0.4 || +0.7
 +
|-
 +
| 2C24A || -1.7 || +0.5
 +
|-
 +
|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'' ===
 +
* [https://logbooks.jlab.org/entry/4268480 2C21A]
 +
* [https://logbooks.jlab.org/entry/4268530 2C24A/Tagger]
 +
* [https://logbooks.jlab.org/entry/4268606 2H01]
 +
 
 +
=== ''- FSD Thresholds'' ===
 +
:* '''Do NOT change FSD settings without approval from RC or beamline expert!'''
 +
::&bull; Upstream: 2 kHz
 +
::&bull; Midstream: 3 kHz
 +
::&bull; Downstream: 150 kHz
 +
::&bull; BOM: 50 kHz
 +
::&bull; 5 ms dwell time
  
* For '''beam tuning and M&oslash;ller runs'''
+
=== ''- Charge Asymmetry'' ===
:&bull; Make sure the SVT/MVT are set as follows: '''SVT: LV ON; HV OFF''', and '''MVT: LV ON; HV ON in SAFE Mode.'''
+
* HWP IN: [https://logbooks.jlab.org/entry/4194811 4194811] and [https://logbooks.jlab.org/entry/4195453 4195453]
::- When '''turning MVT OFF''', do not press "BMT HV OFF" from HV->Overview->Actions, but instead '''select BMT HV ON - Safe Voltage'''. The same applies to FMT '''select FMT HV ON - Safe Voltage'''.
+
* HWP OUT: [https://logbooks.jlab.org/entry/4195738 4195738] and [https://logbooks.jlab.org/entry/4195733 4195733]
::-  When '''turning MVT ON''': go to HV->Overview->Actions, and select BMT (/FMT) "HV ON - Full Voltage".
 
::-  '''DO NOT start runs in SAFE Mode''' for Production/Calibration/Various-Studies.
 
:&bull; Turn <b> DC HV </b> off only for beam tuning; if no beam is available or when the beam is stable, keep them on even if you are not taking data.
 
  
*''' To access the Hall:'''
+
=== ''- Upstream Halo counters'' ===
:&bull; If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).
+
* If the reading on the upstream halo counters exceeds 10, please contact MCC.
:&bull; Check in with the shift personnel before entering the hall.
 
  
 
|}
 
|}
  
{| {{TableStyle1}}  
+
{| {{TableStyle1}}
== <font color=Navy> '''DAQ Operation & related General Instructions''' </font> ==
+
 
 
| valign=top width=50% |
 
| valign=top width=50% |
* (New) '''STANDARD''' end and start of the run:
 
:- "End run"
 
:- <font color=BROWN>'''"Abort"'''
 
:- '''"Download"'''</font>
 
:- "Prestart"
 
:- "Go"
 
  
* <font color=red> If any ROC crashes, find out which one (''look at the ROC Busies GUI or ROCS tabs in the DAQ runcontrol''), and end the ongoing run, which ''might fail to end properly, and that is OK''. You SHOULD issue a '''roc_reboot''' command ON JUST THAT ROC before RESTARTING the DAQ. Test with ''SSH'' or ''PING'' to check whether the ROC is backed up (''some may take longer than others''). Then, '''RESTART the DAQ from scratch'''. </font>
+
== '''General Reminders''' ==
  
* '''RESTART DAQ from Scratch''' when changing configuration or trigger files, or when the run did not end correctly, or when ROC(s) is(are) rebooted, or when RICH is FAST/Fully recovered, as follows:
+
* The main lights in the Hall and the Forward Carriage lights must be kept off during data taking.
:- "Cancel", "Reset"
+
:&bull; Refer to these reference photos, [https://logbooks.jlab.org/entry/3825712 ON] and [https://logbooks.jlab.org/entry/3825731 OFF]
:- "Configure"
+
:&bull; The main, dome lights can be [https://logbooks.jlab.org/entry/4204460 turned off without entering the Hall].
:- "Download"
 
:- "Prestart"
 
:- "Go"
 
  
| valign=top |
+
* Beamline
 +
:&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; Document any beam condition change and send scaler GUIs to HBLOG.
 +
:&bull; If HWP is changed, start a new run.
 +
 
 +
* During beam tuning and M&oslash;ller runs
 +
:&bull; DC:  HV OFF
 +
:&bull; SVT: LV ON, HV OFF
 +
:&bull; MVT: LV ON, HV ON in SAFE Mode
 +
:&bull; All CLAS12 detectors should be OFF; aforementioned tracking detectors are the most critical.
 +
 
 +
* To access the Hall
 +
:&bull; If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator.
 +
:&bull; Check in with the shift personnel before entering the hall.
  
* '''Configuration''' is <tt>'''PROD66/67'''</tt> (or <tt>'''PROD66_PIN'''</tt> for fast reconstruction of ''some calibration/reference runs'' from the cache disk).
 
* In case of '''DAQ Disk space alarm''', call the DAQ expert.
 
* '''Trigger files''':
 
:- <tt> Inbending production: '''rgd_inb_v1.0.trg'''</tt>
 
:- <tt> Outbending production: '''rgd_out_v2.1_Q2_1.2.trg''' or '''rgd_out_v2.3_Q2_1.2.trg''' </tt> with ''low-Q<sup>2</sup> suppression''
 
* During "Configure", observe the ROC terminals to see whether any '''ROC has error messages'''.
 
* ''Some ROCs keep printing error messages while functioning properly''; please see their list in this logbook entry # [https://logbooks.jlab.org/entry/4215299 4215299] to avoid unnecessary reboot since the printout in the ROC terminal won't change. If they get disconnected, the message will appear in the run control itself!
 
* In case of '''DAQ livetime "0" alarm''', '''RESTART DAQ from Scratch''';
 
:&bull; Note that you also get a ''DAQ livetime alarm'' at the start of a run; that is OK and can be simply acknowledged.
 
* Unless a RICH problem crashes the DAQ, '''do NOT interrupt an otherwise smooth run for a RICH recovery'''. Instead, do this in between runs.
 
* The shifter '''MUST check and reset monitoring histograms at least once every 30-60 minutes''' to ensure no significant detector problems. Sometimes, this is the only way to know that a specific ROC needs to be rebooted.
 
* '''Pop-up window''': Enter the beam current and the type of run (e.g., Production and HWP state, ''IN'' or ''OUT'') in the "Comment" field. 
 
* After each step of a '''DAQ RESTART''', ensure it is completed in the '''Run Control message window'''. Also, during "Configure", look for error messages in the ROC terminals.
 
:&bull; Contact the DAQ expert if you have any questions or doubts about how to proceed.
 
* At the start and end of every run, check that the data filled in the '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.
 
  
|}
+
| valign=top |
  
== '''Reference Values''' ==
+
== '''DAQ Operation''' ==  
 +
* Standard end and start of a run
 +
*# End run
 +
*# Abort
 +
*# Download
 +
*# Prestart
 +
*# "Go"
  
=== FSD Thresholds from RG-D ===
+
* Restart DAQ from scratch
* Upstream: 2 kHz
+
:&bull; E.g., when changing configuration or trigger files, when the run did not end correctly, or after ROCs are rebooted
* Midstream: 2 kHz
+
:# Cancel
* Downstream: 100 kHz
+
:# Reset
* BOM: 50 kHz
+
:# Configure
* 5 ms dwell time
+
:# Download
 +
:# Prestart
 +
:# Go
  
=== Harp Scan References from RG-D ===
+
* DAQ instructions
* 2H01 [https://logbooks.jlab.org/entry/4192230]; x= -1.4 mm; y= 0.0 mm
+
:&bull; Please make a log entry (logbook RICH, notify vpk@jlab.org) with RICH temp and scalers screenshots when you have RICH problems.
* Tagger (2C24A) [https://logbooks.jlab.org/entry/4191955]: x= -2.0 mm; y= +0.6 mm
+
:&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.
* 2C21A [https://logbooks.jlab.org/entry/4122116]: x= -0.4 mm; y= +0.6 mm (''less important; values form RG-C'')
 
  
=== IA for Q Asymmetry ===
+
|}
* HWP IN: https://logbooks.jlab.org/entry/4194811 and https://logbooks.jlab.org/entry/4195453
 
* HWP OUT: https://logbooks.jlab.org/entry/4195738 and https://logbooks.jlab.org/entry/4195733
 

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.