Difference between revisions of "Template:ShortTermSchedule-RGD"
(103 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | '''Run Coordinator: | + | '''Run Coordinator: Lamiaa El Fassi''' (757) 575-7540 |
''' PDL: Nathan Baltzell''' (9-) 757 876-1789; ''Office'': x5902 | ''' PDL: Nathan Baltzell''' (9-) 757 876-1789; ''Office'': x5902 | ||
Line 31: | Line 31: | ||
| valign=top width=50% | | | valign=top width=50% | | ||
− | == '''Run Plan''', ''' | + | == '''Run Plan''', '''Thursday, Dec. 14<sup>th</sup> - Friday, Dec. 15<sup>th</sup>, 2023'''== |
− | * | + | * Continue CuSn data-taking as follows until 7 AM on Dec. 15<sup>th</sup> when the beam will be taken away for the RG-K setup: |
− | : | + | :- Target: '''CuSn''' |
− | + | :- Beam Blocker: '''IN''' | |
− | + | :- Beam current: '''100 nA +/- 4 nA on 2C21A''' | |
− | + | :- Run duration: '''100 M events''' | |
− | + | :- DAQ configuration: <tt>'''PROD67'''</tt> | |
− | + | :- Trigger file: '''rgd_out_v2.3_Q2_1.2.trg''' | |
− | + | <span style="font-size:100%; line-height: 2em;"><p class="animate flash"><font color=Blue>'''P.S.: If the beam is widely fluctuating above 105 nA, constantly overshooting over 105 nA on 2C21A, please ask MCC to narrow down the fluctuation margin to keep it below 105 nA based on 2C21A reading. They could put the beam current monitor lock on 2C21A in case that may help with the wide fluctuation and/or adjust our laser phase as well as narrow down the slit width, see ELOG entries [https://logbooks.jlab.org/entry/4224300 4224300] and [https://logbooks.jlab.org/entry/4225220 4225220].'''</font></p></span> | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | <span style="font-size:100%; line-height: 2em;"><p class="animate flash"><font color=Blue>'''P.S.: If the beam is widely fluctuating above | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| valign=top | | | valign=top | | ||
Line 83: | Line 53: | ||
* '''Beamline''': | * '''Beamline''': | ||
+ | :• Ignore the Faraday Cup beam current (see Current Issues). | ||
:• Do not run over 30 minutes above 90 nA with a 5-pass beam without the <b> beam blocker IN </b>. The beam blocker must be IN for long-running at high currents for 5-pass operations. | :• Do not run over 30 minutes above 90 nA with a 5-pass beam without the <b> beam blocker IN </b>. The beam blocker must be IN for long-running at high currents for 5-pass operations. | ||
:• 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. | ||
:• If HWP is changed, start a new run: | :• If HWP is changed, start a new run: | ||
− | ::◊ Please check with the beamline expert whether the SLM and | + | ::◊ Please check with the beamline expert whether the SLM and FCup charge asymmetry (Q-Asym (%)) readings are set properly, as they will be out of range in case Eugene's script is not run by the experts after the HWP change. The absolute values should be less than 0.1%. |
* For '''beam tuning and Møller runs''' | * For '''beam tuning and Møller runs''' | ||
Line 112: | Line 83: | ||
:- "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 do "Cancel" and "Reset" in the DAQ Run Control before issuing a '''roc_reboot''' command ON JUST THAT ROC and continuing with the DAQ Restart chain from "Configure". Test with ''ping'' ONLY instead of ''ssh'' to check whether the ROC is backed up. </font> |
+ | :◊ <font color=brown> When pinging a ROC, e.g., "''ping mvt1''", stop it with ''Ctrl+C'' after a couple of printouts showing different latency times. </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 Fastly/Fully recovered, as follows: | ||
:- "Cancel", "Reset" | :- "Cancel", "Reset" | ||
+ | :- "Needed operations: change configuration or trigger files, or a run did not end correctly, or a ROC crash or RICH is Fastly/Fully recovered"; | ||
:- "Configure" | :- "Configure" | ||
:- "Download" | :- "Download" | ||
Line 122: | Line 97: | ||
* '''Configuration''' is <tt>'''PROD66/67'''</tt> (or <tt>'''PROD66_PIN'''</tt> for fast reconstruction of ''some calibration/reference runs'' from the cache disk). | * '''Configuration''' is <tt>'''PROD66/67'''</tt> (or <tt>'''PROD66_PIN'''</tt> for fast reconstruction of ''some calibration/reference runs'' from the cache disk). | ||
+ | :•<font color=BROWN> As of 11/25/23, whenever there is an issue with the RICH alarms that can't be resolved within 10 to 15 minutes, please contact the RC (/AC) and the RICH experts to discuss the issue. Meanwhile, we may switch the DAQ configuration to <tt>'''PROD67_noRICH'''</tt> until further notice; see the logbook entry #: [https://logbooks.jlab.org/entry/4226898 4226898]. </font> | ||
+ | <!--:•<font color=BROWN> As of 11/25/23, DAQ Configuration is <tt>'''PROD67_noRICH'''</tt> until further notice to don't bother with any RICH issues and no recoveries are needed! </font--> | ||
* In case of '''DAQ Disk space alarm''', call the DAQ expert. | * In case of '''DAQ Disk space alarm''', call the DAQ expert. | ||
* '''Trigger files''': | * '''Trigger files''': | ||
Line 127: | Line 104: | ||
:- <tt> Outbending production: '''rgd_out_v2.1_Q2_1.2.trg''' or '''rgd_out_v2.3_Q2_1.2.trg''' </tt> with ''low-Q<sup>2</sup> suppression'' | :- <tt> Outbending production: '''rgd_out_v2.1_Q2_1.2.trg''' or '''rgd_out_v2.3_Q2_1.2.trg''' </tt> with ''low-Q<sup>2</sup> suppression'' | ||
* 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 | + | * ''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 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. | * 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 | + | * 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 | + | * '''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. | * 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. | :• Contact the DAQ expert if you have any questions or doubts about how to proceed. |
Latest revision as of 00:44, 15 December 2023
Run Coordinator: Lamiaa El Fassi (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, Thursday, Dec. 14th - Friday, Dec. 15th, 2023
P.S.: If the beam is widely fluctuating above 105 nA, constantly overshooting over 105 nA on 2C21A, please ask MCC to narrow down the fluctuation margin to keep it below 105 nA based on 2C21A reading. They could put the beam current monitor lock on 2C21A in case that may help with the wide fluctuation and/or adjust our laser phase as well as narrow down the slit width, see ELOG entries 4224300 and 4225220. |
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)