Difference between revisions of "Template:ShortTermSchedule-RGK"

From clas12-run
Jump to navigation Jump to search
Line 32: Line 32:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
−
== '''Run Plan''', '''Friday, Jan. 12 - Tuesday, Jan. 16, 2024'''==
+
== '''Run Plan''', '''Saturday, Jan. 13 - Tuesday, Jan. 16, 2024'''==
  
 
*'''Friday, Jan. 12''':  
 
*'''Friday, Jan. 12''':  
−
:: SWING
 
−
::: - Take alignment run with cold/empty target
 
−
::::  - Turn all detectors on; use nominal DC HV setting (10, 11, 11); torus and solenoid should be off;
 
−
:::::  - Note: Instructions for BMT for zero field: BMT Overview → HV → Save/Restore HV Settings → Restore → MVT_HV → zero_field.snp → Restore from Selected Snapshot → Ok (Yuri Gotra)
 
−
::::  - 3-5 nA beam (increase beam until R1 DC occupancies < 2%)
 
−
::::  - Use rgk_v1.0_zero_150MeV.trg, PROD67_PIN configuration
 
−
::::  - Take data for 200M total events
 
−
*'''Saturday, Jan. 13''':
 
−
:: OWL
 
−
:: 00:00 - 02:00
 
−
::: - Continue to take alignment run with cold/empty target
 
−
::::  - 3-5 nA beam (increase beam until R1 DC occupancies < 2.5%)
 
−
::::  - Use rgk_v1.0_zero_150MeV.trg, PROD67_PIN configuration
 
−
::::  - continue until 200M total events, which should be approx. 02:00
 
−
:: 02:00 - 04:00
 
−
::: - By this time, we'll have sufficient alignment stats - Prepare for production running
 
−
::: - Stop the beam, stop the run.
 
−
::: - Ramp up the torus (-100%) and the solenoid (100% POSITIVE polarity) (<font color="red">call Eugene Pasyuk to do this.</font>)
 
−
::: - Once the Solenoid current is above 1000 A ask MCC to <font color="red">unmask Solenoid FSD</font>
 
−
::: - While the magnet is ramping, fill the target (<font color="red">James Brock</font>)
 
−
:::: - Target should take 20-30 minutes to fill. If it is not done by 45 minutes, call James.
 
−
:: 04:00 - 08:00 - Preliminary production running.
 
−
::: Note: make sure to change BMT HV to full field setting.
 
−
::: - Take production data runs - rgk_noDC_v1.0_300MeV.trg, PROD67_PIN configuration
 
−
:::: - 100M events per run
 
−
::: - Start with 75 nA, but adjust as needed to keep R1 DC occupancies < 5% and DAQ livetime ~90%
 
−
::::  - Feel free to call RC for guidance on settings
 
−
::: - <font color="red"> Look at DC occupancy in Mon12 to check that sectors are relatively uniform. If a large degree of non-uniformity, call the RC</font> so we can consider a small change in the beam position to see if the uniformity can be improved. If things are relatively uniform, keep the beam where it is.
 
−
::: - Normalize the DAQ trigger alarms once final beam current is chosen
 
−
::: - Review all mon12 plots throughout the run
 
−
::: - Monitor the DAQ rate via strip chart throughout the run and notify the RC if there are any DAQ trigger alarms not due to beam excursions/trips
 
−
::: - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
 
 
:: DAY
 
:: DAY
−
:: 08:00 - Continue preliminary production until Florian arrives.
+
:: 08:00 - DC Studies
 
::: - Florian will test DC thresholds and HV settings, and recommend a setting for production running.
 
::: - Florian will test DC thresholds and HV settings, and recommend a setting for production running.
 
:: Resume production running with Florian's DC settings
 
:: Resume production running with Florian's DC settings
−
::: - Take first production data run - rgk_noDC_v1.0_300MeV.trg, PROD67_PIN configuration
+
::: - Take first production data run - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration, 200M events per run.
−
:::: - Note: make sure to change BMT HV to full field setting, if not done already.
 
−
::: - Data run should use approx. 75 nA beam; collect 100M events - RC will dictate final beam current (R1 DC occupancies < 5% and DAQ livetime ~90%)
 
 
::: - Confirm with RC and DC Expert (<font color="red">Florian</font>) about final DC settings
 
::: - Confirm with RC and DC Expert (<font color="red">Florian</font>) about final DC settings
 +
:::: - Data run should use approx. 75 nA beam - RC will dictate final beam current (R1 DC occupancies < 5% and DAQ livetime ~90%)
 
::: - Normalize the DAQ trigger alarms once final beam current is chosen
 
::: - Normalize the DAQ trigger alarms once final beam current is chosen
 
::: - Review all mon12 and Hydra plots throughout the run
 
::: - Review all mon12 and Hydra plots throughout the run
Line 81: Line 48:
 
:: Rest of DAY and SWING
 
:: Rest of DAY and SWING
 
:: - Production running (continued)
 
:: - Production running (continued)
−
::: - Take production data - rgk_noDC_v1.0_300MeV.trg, now with the PROD67 configuration
+
::: - Take production data - rgk_noDC_v1.0_300MeV.trg, with the PROD67 configuration; collect 200M events per run
−
::: - Data run should use approx 75 nA beam (confirm with RC about exact number); collect 100M events per run
+
::: - Data run should use approx 75 nA beam (confirm with RC about exact number)
 
::: - Review all mon12 and Hydra plots throughout the run
 
::: - Review all mon12 and Hydra plots throughout the run
 
::: - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
 
::: - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
 
*'''Sunday, Jan. 14''':
 
*'''Sunday, Jan. 14''':
 
:: 00:00 – 24:00 – Production running (continued)
 
:: 00:00 – 24:00 – Production running (continued)
−
::: - Take production data - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration
+
::: - Take production data - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration; collect 200M events per run
−
::: - Data run should use approx 75 nA beam (confirm with RC about exact number); collect 100M events per run
+
::: - Data run should use approx 75 nA beam (confirm with RC about exact number)
 
::: - Review all mon12 and Hydra plots throughout the run
 
::: - Review all mon12 and Hydra plots throughout the run
 
::: - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
 
::: - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
 
*'''Monday, Jan. 15''':
 
*'''Monday, Jan. 15''':
 
:: 00:00 – 24:00 – Production running (continued)
 
:: 00:00 – 24:00 – Production running (continued)
−
::: - Take production data - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration
+
::: - Take production data - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration; collect 200M events per run
−
::: - Data run should use approx 75 nA beam (confirm with RC about exact number); collect 100M events per run
+
::: - Data run should use approx 75 nA beam (confirm with RC about exact number)
 
::: - Review all mon12 and Hydra plots throughout the run
 
::: - Review all mon12 and Hydra plots throughout the run
 
::: - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
 
::: - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
 
*'''Tuesday, Jan. 16''':
 
*'''Tuesday, Jan. 16''':
 
:: 00:00 – 07:00 – Production running (continued)
 
:: 00:00 – 07:00 – Production running (continued)
−
::: - Take production data - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration
+
::: - Take production data - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration; collect 200M events per run
−
::: - Data run should use approx 75 nA beam (confirm with RC about exact number); collect 100M events per run
+
::: - Data run should use approx 75 nA beam (confirm with RC about exact number)
 
::: - Review all mon12 and Hydra plots throughout the run
 
::: - Review all mon12 and Hydra plots throughout the run
 
::: - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
 
::: - Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook

Revision as of 08:29, 13 January 2024

Experiment Coordinator: Annalisa D'Angelo

Run Coordinator: Axel Schmidt (757) 575-7540

PDL: Daniel Carman (757) 876-1789; Office: x5586

Daily RC/OA Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link

Important Notes

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

  • 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 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.
  • Remote shift: If needed, worker shifts can be taken from off-site. Inform the PDL and RC. Also, make sure that you follow the instructions under the "Shift Worker" tab, as you need some lead time to set up!
  • Note to Shift Takers:
    • Read the ESAD, COO, RSAD, and ERG documents found on the "Current RG-K Run Info" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.
    • Read at least the previous 24 hours logbook entries to be aware of recent run details and changes;
      Arrive at least 10 minutes early for shift change;
    • Refresh the runwiki page/tabs; look over it/them every shift:
      • Follow the Shift Expert/Worker tab's instructions.
    • Do not spend more than 15-20 min trying to fix a problem. In case of any issue, contact the On-call Experts or the RC.
    • Important links


Run Plan, Saturday, Jan. 13 - Tuesday, Jan. 16, 2024

  • Friday, Jan. 12:
DAY
08:00 - DC Studies
- Florian will test DC thresholds and HV settings, and recommend a setting for production running.
Resume production running with Florian's DC settings
- Take first production data run - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration, 200M events per run.
- Confirm with RC and DC Expert (Florian) about final DC settings
- Data run should use approx. 75 nA beam - RC will dictate final beam current (R1 DC occupancies < 5% and DAQ livetime ~90%)
- Normalize the DAQ trigger alarms once final beam current is chosen
- Review all mon12 and Hydra plots throughout the run
- Monitor the DAQ rate via strip chart throughout the run and notify the RC if there are any DAQ trigger alarms not due to beam excursions/trips
- Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
Rest of DAY and SWING
- Production running (continued)
- Take production data - rgk_noDC_v1.0_300MeV.trg, with the PROD67 configuration; collect 200M events per run
- Data run should use approx 75 nA beam (confirm with RC about exact number)
- Review all mon12 and Hydra plots throughout the run
- Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
  • Sunday, Jan. 14:
00:00 – 24:00 – Production running (continued)
- Take production data - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration; collect 200M events per run
- Data run should use approx 75 nA beam (confirm with RC about exact number)
- Review all mon12 and Hydra plots throughout the run
- Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
  • Monday, Jan. 15:
00:00 – 24:00 – Production running (continued)
- Take production data - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration; collect 200M events per run
- Data run should use approx 75 nA beam (confirm with RC about exact number)
- Review all mon12 and Hydra plots throughout the run
- Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
  • Tuesday, Jan. 16:
00:00 – 07:00 – Production running (continued)
- Take production data - rgk_noDC_v1.0_300MeV.trg, PROD67 configuration; collect 200M events per run
- Data run should use approx 75 nA beam (confirm with RC about exact number)
- Review all mon12 and Hydra plots throughout the run
- Post standard beamline overview screen and DAQ screens (CLAS12 Trigger Bits, ROC Rates, ROC Busies, DAQ status) in the logbook
Approx. 07:00, Accelerator will turn off to permit work in the tunnel.

General Information

  • The main lights in the Hall (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.
    • Refer to these photos: ON: [1], OFF: [2]
    • 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:
    • 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
      • The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.
  • For beam tuning and Møller runs
    • Make sure the SVT/MVT are set as follows: SVT: LV ON; HV OFF, and MVT: LV ON; HV ON - Safe Voltage
      • From HV → Overview → Actions, select BMT HV ON - Safe Voltage
      • For Production/Calibration/Various-Studies, select BMT (/FMT) "HV ON - Full Voltage".
    • Turn DC HV 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:
    • 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).
    • Check in with the shift personnel before entering the hall.

DAQ Operation & Related General Information

  • STANDARD end and start of the run:
- "End run"
- "Cancel"
- "Reset"
- "Download"
- "Prestart"
- "Go"
  • Restart DAQ when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH Fast/Full recovery:
- "Cancel"
- "Reset"
- "Configure"
- "Download"
- "Prestart"
- "Go"
  • Configuration is PROD67 (or PROD67_PIN 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:
    • Production running: rgk_noDC_v1.0_300MeV.trg
  • 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 # 4215299 to avoid unnecessary reboot since the printout in the ROC terminal won't change. If any of them get disconnected, the message will appear in the run control itself!
  • If a ROC has crashed, find which one is (look for busy ROCs), end the current run, issue a roc_reboot command ON JUST THAT ROC, and test with SSH or PING to check whether the ROC is back up (some take longer than others). Then, Restart DAQ from scratch.
  • 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 shift MUST check and reset monitoring histograms at least once every 30-60 minutes to identify major detector problems. Sometimes, it 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 runs (e.g., Production) 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.
    • 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 Run Condition Data Base (RCDB) is correct, especially the manually filled fields.

Reference Values

FSD Thresholds from RG-K

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

Harp Scan References from RG-K

* Tagger (2C24A) x= -1.7 mm; y= +0.5 mm
* 2H01 x= -0.7 mm; y= +0.6 mm
* 2C21A  x= -0.4 mm; y= +0.7 mm (not important for production!?)

To Do Items

  • Faraday Cup Calibration
  • Empty target running (with full field)
Retrieved from "https://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&oldid=6999"