Difference between revisions of "Template:ShortTermSchedule-RGE"

From clas12-run
Jump to navigation Jump to search
Line 25: Line 25:
 
| valign=top |
 
| valign=top |
  
−
== General Instructions ==
+
== General Reminders ==
  
−
* The main lights in the Hall and the Forward Carriage lights must be kept off during data taking. If these lights are switched on during an access, they '''should be switched off when leaving the Hall'''.
+
* The main lights in the Hall and the Forward Carriage lights must be kept off during data taking.
−
** Refer to these photos: ON: [https://logbooks.jlab.org/entry/3825712], OFF: [https://logbooks.jlab.org/entry/3825731]
+
** Refer to these photos, [https://logbooks.jlab.org/entry/3825712 ON] and [https://logbooks.jlab.org/entry/3825731 OFF]
 
** 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
 
** 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.
 
** 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
 
* Beamline
−
** '''Do not run over XX minutes above YY nA with a 5-pass beam without the beam blocker IN.''' The beam blocker must be IN for long-running at high currents for 5-pass operations.
+
** '''Do not run over XX minutes above YY 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).
 
** 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.
 
** Document any beam condition change and send scaler GUIs to HBLOG.

Revision as of 12:04, 26 February 2024

Run Coordinator: Hayk Hakyoban (757) 575-7540

PDL: Nathan Baltzell (9-) 757 876-1789; Office: x5902

Daily RC Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1611984219; Passcode: RGD-RC23), except on Wednesdays, which is on ZOOM ONLY @ 15:30.

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.

Monday, March 10 - Monday, Dec. 4

  • Continue CuSn data-taking as follows:
- Target: CuSn
- Beam Blocker: IN

General Reminders

  • The main lights in the Hall and the Forward Carriage lights must be kept off during data taking.
    • Refer to these photos, ON and OFF
    • 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
    • Do not run over XX minutes above YY 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.
  • 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 in SAFE Mode.
    • 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.
    • 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.
    • 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 Instructions

  • (New) STANDARD end and start of the run:
- "End run"
- "Abort"
- "Download"
- "Prestart"
- "Go"
  • 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.
  • 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:
- "Cancel", "Reset"
- "Configure"
- "Download"
- "Prestart"
- "Go"
  • Configuration is PROD66/67 (or PROD66_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:
- Inbending production: rgd_inb_v1.0.trg
- Outbending production: rgd_out_v2.1_Q2_1.2.trg or rgd_out_v2.3_Q2_1.2.trg with low-Q2 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 # 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;
• 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.
• 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-D

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

Harp Scan References from RG-D

  • 2H01 [1]; x= -1.4 mm; y= 0.0 mm
  • Tagger (2C24A) [2]: x= -2.0 mm; y= +0.6 mm
  • 2C21A [3]: x= -0.4 mm; y= +0.6 mm (less important; values form RG-C)

IA for Q Asymmetry

Retrieved from "https://wiki.jlab.org/clas12-run/index.php?title=Template:ShortTermSchedule-RGE&oldid=7345"