Difference between revisions of "Template:ShortTermSchedule-RGD"
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
:::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span> | :::::::::::::::<span style="font-size:122%; line-height: 2em;"><p class="animate flash"><font color=red>''' Do NOT change FSD settings without approval from RC or beamline expert!'''</font></p></span> | ||
| − | * '''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' | + | * '''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' and inform the Crew Chief. |
* 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. | * 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! | * '''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! | ||
| Line 19: | Line 19: | ||
:◊ Arrive at least 10 minutes early for '''shift change''' | :◊ Arrive at least 10 minutes early for '''shift change''' | ||
:◊ Refresh the run wiki pages; look over them every shift | :◊ Refresh the run wiki pages; look over them every shift | ||
| − | ::- Follow the '''expert/worker shift instructions''' | + | ::- Follow the '''expert/worker shift instructions'''. |
| − | :◊ ''' | + | :◊ For advice, '''do not hesitate to call the RC''' first and foremost, day or night. |
| − | |||
| − | |||
| − | |||
== Current Issues == | == Current Issues == | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | * '''Tagger magnet procedure''' If the tagger magnet needs to be turned off, tell the operator to use '''only the script for degaussing, NEVER do "by hand"!''' | + | * '''Do not spend more than 15-20 min trying to fix a problem'''. With any issue, contact On-Call Experts or RC. |
| − | * '''Change | + | |
| − | + | * '''New RICH recovery protocol''': see tab expert "Shift Expert" for new information. '''Avoid unnecessary recoveries'''. | |
| + | |||
| + | * '''BMT/FMT/SVT:''' If new hot channels appear, '''call the MVT/SVT/MM expert Yuri Gotra''' (757-541-7539). These channels need to be addressed by the expert. | ||
| + | |||
| + | * '''Tagger magnet procedure:''' If the tagger magnet needs to be turned off, tell the operator to use '''only the script for degaussing, NEVER do "by hand"!''' | ||
| + | |||
| + | * '''Change of target in the hall:''' In case of questions from MCC about the necessary controlled access, refer to the logbook entry #: '''[https://logbooks.jlab.org/entry/4196113 4196113]''' for the access requirements. | ||
{| {{TableStyle1}} | {| {{TableStyle1}} | ||
| Line 40: | Line 39: | ||
== '''Run Plan''' for Thurs., Oct. 26<sup>th</sup> - Tue., Oct. 31<sup>st</sup>, 2023 == | == '''Run Plan''' for Thurs., Oct. 26<sup>th</sup> - Tue., Oct. 31<sup>st</sup>, 2023 == | ||
| − | * Continue production on CuSn | + | * Continue production on CuSn |
:- Target: '''CuSn''' | :- Target: '''CuSn''' | ||
:- Beam Blocker: '''IN''' | :- Beam Blocker: '''IN''' | ||
| Line 52: | Line 51: | ||
* '''Tuesday, Oct. 31<sup>st</sup>, Day Shift''': | * '''Tuesday, Oct. 31<sup>st</sup>, Day Shift''': | ||
:• Switch back to LD2 around 8:30 AM. | :• Switch back to LD2 around 8:30 AM. | ||
| − | |||
<!-- | <!-- | ||
** 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 58: | Line 56: | ||
--> | --> | ||
| − | == <font color=blue> DAQ | + | == <font color=blue> DAQ operation </font> == |
| − | + | '''STANDARD''' end run and start new run: | |
| − | + | ::- "End run" | |
| − | + | ::- "Prestart", "Go" | |
| − | + | ||
| − | + | If changing configuration or trigger file, if the run did not end correctly, if ROC(s) were rebooted, after any RICH recovery, <br> | |
| − | + | '''RESTART''' DAQ: | |
| − | + | ::- "Cancel", "Reset", "Configure", "Download" | |
| − | + | ::- "Prestart", "Go" | |
| − | |||
| − | |||
| − | |||
| − | : | ||
| − | : | ||
| − | |||
| − | |||
| − | ::- "Cancel", " | ||
| − | |||
| − | |||
| − | |||
== Reference Values == | == Reference Values == | ||
| Line 101: | Line 88: | ||
==<font color=blue>''' General Instructions'''</font>== | ==<font color=blue>''' General Instructions'''</font>== | ||
| + | |||
| + | * <font color=red>'''Data Acquisition:'''</font> | ||
| + | ** '''Configuration''' is <tt>'''PROD66'''</tt> (or <tt>'''PROD66_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. | ||
| + | ** <tt> Trigger files </tt>: | ||
| + | *** <tt> Inbending production: '''rgd_inb_v1.0.trg'''</tt> | ||
| + | *** <tt> Outbending production: '''rgd_out_v1.1.trg'''</tt>, or <tt>'''rgd_out_v2.1_Q2_1.2.trg'''</tt> with ''low-Q<sup>2</sup> suppression'' | ||
| + | ** If a ROC has crashed, find which one it is, end the current run, issue a '''roc_reboot''' command ON JUST THAT ROC, and RESTART DAQ. | ||
| + | ** 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 shift '''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 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, make sure it is completed in the '''Run Control message window'''. | ||
| + | ** Contact the DAQ expert if there are any questions. | ||
* The <b> main lights in the Hall </b> (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. | * The <b> main lights in the Hall </b> (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. | ||
| Line 107: | Line 107: | ||
** Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cool down. | ** Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cool down. | ||
| − | * Do not run more than 30 minutes above 90 nA with a 5-pass beam without the <b> beam blocker | + | * '''Beamline''': |
| − | * | + | ** Do not run more than 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). |
| − | * | + | ** Document any beam condition change and send scaler GUIs to HBLOG. |
| − | + | ** If HWP is changed, start a new run. | |
| − | |||
| − | |||
| − | * | ||
| − | |||
| − | + | * 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 fields of that are filled manually. | |
| − | * | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | ''' | + | * 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 thing 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 <b> DC HV </b> 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:''' | ''' To access the Hall:''' | ||
Revision as of 07:13, 28 October 2023
Run Coordinator: Susan Schadmand (757) 575-7540
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 and inform the Crew Chief.
- 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.
- ◊ For advice, do not hesitate to call the RC first and foremost, day or night.
Current Issues
- Do not spend more than 15-20 min trying to fix a problem. With any issue, contact On-Call Experts or RC.
- New RICH recovery protocol: see tab expert "Shift Expert" for new information. Avoid unnecessary recoveries.
- BMT/FMT/SVT: If new hot channels appear, call the MVT/SVT/MM expert Yuri Gotra (757-541-7539). These channels need to be addressed by the expert.
- Tagger magnet procedure: If the tagger magnet needs to be turned off, tell the operator to use only the script for degaussing, NEVER do "by hand"!
- Change of target in the hall: In case of questions from MCC about the necessary controlled access, refer to the logbook entry #: 4196113 for the access requirements.
Run Plan for Thurs., Oct. 26th - Tue., Oct. 31st, 2023
P.S.: If the beam is widely fluctuating above 90 nA, please ask MCC to narrow down the fluctuation margin and give us the required 90 nA +/- 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. We will keep the beam blocker IN while using this target combination!
DAQ operationSTANDARD end run and start new run:
If changing configuration or trigger file, if the run did not end correctly, if ROC(s) were rebooted, after any RICH recovery,
Reference ValuesFSD Thresholds from RG-D
Harp Scan References from RG-D
IA for Q Asymmetry |
General Instructions
To access the Hall:
|