Difference between revisions of "Template:ShortTermSchedule-RGK"

From clas12-run
Jump to navigation Jump to search
Line 98: Line 98:
 
This will ensure proper compression of the FADCs and therefore a smaller data rate.
 
This will ensure proper compression of the FADCs and therefore a smaller data rate.
  
−
* '''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:
+
* '''Restart DAQ''' when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:
 
:- "Cancel"
 
:- "Cancel"
 
:- "Reset"
 
:- "Reset"
Line 108: Line 108:
 
| valign=top |
 
| valign=top |
  
−
* '''Configuration''' is <tt>'''PROD67'''</tt> (or <tt>'''PROD67_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.
 
* In case of '''DAQ Disk space alarm''', call the DAQ expert.
−
* '''Trigger files''':
+
* After each step of '''restart DAQ''', ensure it is completed in the '''Run Control message window'''. During "Configure", look for error messages in the ROC terminals.
−
** Production running: <tt> '''rgk_noDC_v1.1_300MeV.trg'''</tt>
 
−
* 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 any of them get disconnected, the message will appear in the run control itself!  
 
* ''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 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'''.  
 
* 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.
+
* '''Pop-up window''': Enter the beam current and the type of run in the "Comment" field.   
−
* 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 '''[https://clasweb.jlab.org/rcdb Run Condition Data Base (RCDB)]''' is correct, especially the manually filled fields.
 
* 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.
 +
* Check and reset monitoring histograms every hour'''. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.
 +
* Contact the DAQ expert if you have any questions or doubts about how to proceed.
  
 
|}
 
|}

Revision as of 18:14, 17 January 2024

Experiment Coordinator: Annalisa D'Angelo

Run Coordinator: Susan Schadmand (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 Wednesday, Jan. 17, 2024

  • HWP OUT

Beam Restoration

  • when beam is announced, ask MCC to energize the tagger, ask Eugene to ramp up magnets
  • Beam tune on tagger dump
  • Moller Run
  • Beam tune on Faraday Cup, incl. 2H00 steering (?)

Trigger Tests

  • DAQ configuration: PROD67_PIN
  • Notify Valery that trigger tests are about to start
    • Trigger rgk_noDC_v1.2_300MeV.trg - 10 minute run
    • Trigger to rgk_out_v1.1_300MeV.trg - 200M events
    • Trigger to rgk_noDC_v1.1_300MeV.trg - 200M events

Production

DAQ configuration: PROD67
Trigger: rgk_noDC_v1.1_300MeV.trg
Run: 200M events
Beam current: 65 nA
  • DAQ livetime ~90%
  • R1 DC occupancies <5% (log DC trips, see 'Recent Changes and Current Issues')

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

  • NEW STANDARD end and start of the run:
- "End run"
- "Cancel"
- "Reset"
- "Download"
- "Prestart"
- "Go"

This will ensure proper compression of the FADCs and therefore a smaller data rate.

  • Restart DAQ when changing configuration or trigger files, when the run did not end correctly, when ROCs are rebooted, or after RICH recovery:
- "Cancel"
- "Reset"
- "Configure"
- "Download"
- "Prestart"
- "Go"
  • In case of DAQ Disk space alarm, call the DAQ expert.
  • After each step of restart DAQ, ensure it is completed in the Run Control message window. During "Configure", look for error messages in the ROC terminals.
  • 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.
  • Pop-up window: Enter the beam current and the type of run in the "Comment" field.
  • 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.
  • Check and reset monitoring histograms every hour. Sometimes, it is the only way to know that a specific ROC needs to be rebooted.
  • Contact the DAQ expert if you have any questions or doubts about how to proceed.

Glossary of Triggers

Trigger Explanation
rgk_noDC_v1.0_300MeV.trg DC roads are not in the trigger. Hold off time is 3 us.
rgk_noDC_v1.1_300MeV.trg DC roads are not in the trigger. Hold off time is 2 us.
rgk_noDC_v1.2_300MeV.trg DC roads are not in the trigger. Hold off time is 1 us.
rgk_out_v1.1_300MeV.trg Outbending DC roads, Hold off time is 2 us.

Reference Values

FSD Thresholds

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

Nominal Beam Positions

BPM Coordinate Reading (mm)
2C24A x -1.7
y +0.5
2H01 x -0.7
y +0.6
2C21A x -0.4
y +0.7

Harp Scan References from RG-K

To Do Items

  • Faraday Cup Calibration
    • Rafo can use beam current scan taken from Sat. Jan. 13, during 13:50 - 14:20
  • Empty target running (with full field)
    • Goal is to take > 5% integrated charge, but not until about 2 weeks in
  • Prescale on FC cup trigger
    • Discuss when to study after we have a plan for Tuesday Jan. 16 down time
Retrieved from "https://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGK&oldid=7034"