Difference between revisions of "Template:ShortTermSchedule-RGD"
Jump to navigation
Jump to search
| Line 50: | Line 50: | ||
:- Run duration: '''100 M events''' | :- Run duration: '''100 M events''' | ||
:- DAQ configuration: <tt>'''PROD67'''</tt> | :- DAQ configuration: <tt>'''PROD67'''</tt> | ||
| − | :- Trigger file: ''' | + | :- Trigger file: '''rgd_out_v2.1_Q2_1.2.trg''' |
<!-- | <!-- | ||
** Once the access is done, please ask MCC for 165 nA and take 100 M triggers runs with an empty target for a couple of hours with the same <tt>PROD66</tt> DAQ configuration, but the following trigger file: ''Trigger file'': '''rgd_v1.0_no_DC_100nA.trg'''<font color=blue><center>-----''If everything goes well, that should bring us to the Swing shift''----</font>--> | ** Once the access is done, please ask MCC for 165 nA and take 100 M triggers runs with an empty target for a couple of hours with the same <tt>PROD66</tt> DAQ configuration, but the following trigger file: ''Trigger file'': '''rgd_v1.0_no_DC_100nA.trg'''<font color=blue><center>-----''If everything goes well, that should bring us to the Swing shift''----</font>--> | ||
| Line 62: | Line 62: | ||
* <tt>Trigger files</tt>: | * <tt>Trigger files</tt>: | ||
:◊ <tt>Inbending production: '''rgd_inb_v1.0.trg'''</tt> | :◊ <tt>Inbending production: '''rgd_inb_v1.0.trg'''</tt> | ||
| − | :◊ <tt>Outbending production: '''rgd_out_v1.1.trg'''</tt> (https://logbooks.jlab.org/entry/4201027) | + | :◊ <tt>Outbending production: '''rgd_out_v1.1.trg'''</tt> (https://logbooks.jlab.org/entry/4201758) with low-Q<sup>2</sup> suppression. |
| + | :◊ <tt>Outbending production: '''rgd_out_v2.1_Q2_1.2.trg'''</tt> (https://logbooks.jlab.org/entry/4201027) | ||
* '''NOTE''': UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to make a RICH recovery - instead, do this in between runs. Review its new recovery procedure in HBLOG entry #: [https://logbooks.jlab.org/entry/4197225 4197225]. | * '''NOTE''': UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to make a RICH recovery - instead, do this in between runs. Review its new recovery procedure in HBLOG entry #: [https://logbooks.jlab.org/entry/4197225 4197225]. | ||
* '''NOTE''': BOTH the shift expert AND the shift worker MUST check and reset monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems. Sometimes, it is the only way to know that a roc needs to be rebooted. | * '''NOTE''': BOTH the shift expert AND the shift worker MUST check and reset monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems. Sometimes, it is the only way to know that a roc needs to be rebooted. | ||
Revision as of 15:58, 18 October 2023
Run Coordinator: Susan Schadmand (757) 575-7540 (or 757-223-6213)
PDL: Nathan Baltzell (9-)757 876-1789 , x5902 office
RG/Analysis Coordinator (AC): Lamiaa El Fassi (630) 605-4259
Daily RC/OA 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 due to the conflict with the 13:30 MCC Scheduling/Planning meeting.
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
- 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 "Worker Shift" Tab - you need some lead time to set up!
- Note to shift takers, please:
- ◊ Read the logbook, be aware of previous 24 hours
- ◊ Arrive at least 10 minutes early for shift change
- ◊ Refresh the run wiki pages; look over them every shift
- - Follow the expert/worker shift instructions
- ◊ Communicate with your co-shift person
- - The shift expert should know about and refer to logbook entries in their shift summary
- - The shift worker should discuss an issue with the shift expert before making extra logbook entries
- ◊ For advice, do not hesitate to call the RC first and foremost, day or night.
Current Issues
- BMT/FMT/SVT:
- ◊ If new hot channels appear, please call the MVT/SVT/MM expert Yuri Gotra (757-541-7539) to address them.
- ◊ SVT low voltage alarms (minor, every ~2 hours) is a communication problem in the system, not an issue with the voltages. Acknowledge the alarm.
- The '"ECAL_adcSum" histograms in mon12 are filled depending on trigger bits 0-6, which are prescaled in the current outbending configuration trigger file "rgd_out_v1.1.trg" by a factor of 20; see HBLOG entry #: 4201027. Thus, the relatively smaller number of histogram entries.
- Tagger magnet procedure If the tagger magnet needs to be turned off, tell the operator to use only the script only for degaussing, NEVER do "by hand"!
- Change the LD2 and solid targets positions in the hall: In case of questions from MCC about the necessary controlled access, please refer to the logbook entry #: 4196113 for the access requirements.
Run Plan for Wed, Oct. 18 - Sat., Oct. 21, 2023
DAQ configuration
Reference ValuesFSD Thresholds from RG-D
Harp Scan References from RG-D
IA for Q Asymmetry |
General Instructions
Every Shift:
Every Run:
To access the Hall:
|