Difference between revisions of "Template:ShortTermSchedule-RGD"
Jump to navigation
Jump to search
| Line 112: | Line 112: | ||
:- "Go" | :- "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> |
* '''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: | * '''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: | ||
| Line 130: | Line 130: | ||
* During "Configure", observe the ROC terminals to see whether any '''ROC has error messages'''. | * 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! | ||
| − | * | + | * <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> |
* Unless a RICH problem crashes the DAQ, '''do NOT interrupt an otherwise smooth run for a RICH recovery'''. Instead, do this in between runs. | * 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. | * 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. | ||
Revision as of 19:00, 19 November 2023
Run Coordinator: Susan Schadmand (757) 575-7540
PDL: Nathan Baltzell (9-) 757 876-1789; Office: x5902
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 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-D 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.
- ◊ Review these important links:
- - Recent Changes and Current Issues
- - General How-to for beam restoration procedures and Møller runs.
Run Plan, Friday, Nov. 17th - Tuesday, Dec. 5th, 2023
P.S.: If the beam is widely fluctuating above 95 nA, please ask MCC to narrow down the fluctuation margin and give us +/- 3nA based on 2C21A reading. They could put the beam current lock on 2C21A in case that may help with the wide fluctuation as it's currently done.
|
General Instructions
|
|
|
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 [3]; x= -1.4 mm; y= 0.0 mm
- Tagger (2C24A) [4]: x= -2.0 mm; y= +0.6 mm
- 2C21A [5]: x= -0.4 mm; y= +0.6 mm (less important; values form RG-C)