Difference between revisions of "Run Group M"
Jump to navigation
Jump to search
Line 75: | Line 75: | ||
</center> | </center> | ||
− | == RC: | + | == RC: Someone == |
* (757) 575-7540 | * (757) 575-7540 | ||
* 9 575 7540 from Counting Room | * 9 575 7540 from Counting Room | ||
− | * [mailto:hszumila@jlab.org | + | * [mailto:hszumila@jlab.org someone@jlab.org] |
== PDL: XXXXX == | == PDL: XXXXX == | ||
* (757) 876-1789 | * (757) 876-1789 | ||
* 9 876-1789 from Counting Room | * 9 876-1789 from Counting Room | ||
− | * [mailto:pasyuk@jlab.org | + | * [mailto:pasyuk@jlab.org someone@jlab.org] |
<br> | <br> | ||
+ | <!-- | ||
* '''Note 1: Be very mindful of the background rates in the halo counters, rates in the detectors, and currents in the SVT for all settings to ensure that they are at safe levels.''' | * '''Note 1: Be very mindful of the background rates in the halo counters, rates in the detectors, and currents in the SVT for all settings to ensure that they are at safe levels.''' | ||
The integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and the rates on the midstream counters have to be in the range 10-20 Hz (acceptable up to 50 Hz) @50 nA. Counting rates in the range of hundreds of Hz may indicate bad beam tune or bleed-through from other Halls. | The integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and the rates on the midstream counters have to be in the range 10-20 Hz (acceptable up to 50 Hz) @50 nA. Counting rates in the range of hundreds of Hz may indicate bad beam tune or bleed-through from other Halls. | ||
Line 119: | Line 120: | ||
*'''Note 11: Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/ https://clas12mon.jlab.org/mon12/histograms/]''' | *'''Note 11: Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/ https://clas12mon.jlab.org/mon12/histograms/]''' | ||
+ | |||
+ | --> | ||
{| {{TableStyle1}} | {| {{TableStyle1}} | ||
Line 125: | Line 128: | ||
== <font color=blue>''' Run Plan:'''</font>== | == <font color=blue>''' Run Plan:'''</font>== | ||
+ | <!-- | ||
<i>(Updated: Oct. 3 2018 at 14:30)</i> | <i>(Updated: Oct. 3 2018 at 14:30)</i> | ||
Line 139: | Line 143: | ||
** The beam current should be 45 nA, and He will take care of the DAQ. | ** The beam current should be 45 nA, and He will take care of the DAQ. | ||
** With good beam it will take approximately 4-6 hours. | ** With good beam it will take approximately 4-6 hours. | ||
− | + | --> | |
− | |||
* Any questions call system expert, RC or PDL. | * Any questions call system expert, RC or PDL. | ||
== <font color=blue>''' Shift Worker Notes:'''</font>== | == <font color=blue>''' Shift Worker Notes:'''</font>== | ||
− | + | <-- | |
* From time to time, we might experience trigger bit issues (FT bits: 24, 25, 26, 27). Bit 26 might not trigger the alarm but when this issue happens it will count abnormally high. For the time being, shift leaders can try to do the sequence of End->Cancel->Reset, roc_reboot adcft1 (and adcft2, adcft3), make sure the ROCs are connected, then Download->Prestart->Go. If this does not work, repeat the sequence and add "Configure" in front of "Download". If the trig issue persists, continue to take production data without fixing it -- please make sure you log this infor in the RCDB "Comment" field. | * From time to time, we might experience trigger bit issues (FT bits: 24, 25, 26, 27). Bit 26 might not trigger the alarm but when this issue happens it will count abnormally high. For the time being, shift leaders can try to do the sequence of End->Cancel->Reset, roc_reboot adcft1 (and adcft2, adcft3), make sure the ROCs are connected, then Download->Prestart->Go. If this does not work, repeat the sequence and add "Configure" in front of "Download". If the trig issue persists, continue to take production data without fixing it -- please make sure you log this infor in the RCDB "Comment" field. | ||
Line 151: | Line 154: | ||
* Sometimes, a couple RICH channel scalers go to 0 and there is no alarm, even though the "# of fibers connected" would be shown to be the correct 138. Shift takers therefore should periodically, especially at the end of run, check the RICH scalers GUI. If there is an issue: | * Sometimes, a couple RICH channel scalers go to 0 and there is no alarm, even though the "# of fibers connected" would be shown to be the correct 138. Shift takers therefore should periodically, especially at the end of run, check the RICH scalers GUI. If there is an issue: | ||
** For RICH recovery procedures, please see Log entry https://logbooks.jlab.org/entry/3562273. This would apply in the cases of 1. DAQ crash: rich4 is not responding or 2. RICH alarms (LV,missing tile, temperature etc). If it does not work or you are uncertain about what to do, contact the RICH expert on call. | ** For RICH recovery procedures, please see Log entry https://logbooks.jlab.org/entry/3562273. This would apply in the cases of 1. DAQ crash: rich4 is not responding or 2. RICH alarms (LV,missing tile, temperature etc). If it does not work or you are uncertain about what to do, contact the RICH expert on call. | ||
− | + | --> | |
'''In case of other questions or uncertainties of what to do, call the RC''' | '''In case of other questions or uncertainties of what to do, call the RC''' | ||
<!-- | <!-- | ||
'''[[Every Shift:]]''' | '''[[Every Shift:]]''' | ||
− | *Follow run plan as outlined by RC | + | * Follow run plan as outlined by RC |
* If any concern about beam stability, ask MCC if orbit locks are on (they should be). | * If any concern about beam stability, ask MCC if orbit locks are on (they should be). | ||
* Keep shift summary up to date in HBLOG. Record all that happens. | * Keep shift summary up to date in HBLOG. Record all that happens. | ||
Line 162: | Line 165: | ||
* Document any beam condition change and send scaler GUIs to HBLOG | * Document any beam condition change and send scaler GUIs to HBLOG | ||
* [https://bta.acc.jlab.org Fill out BTA] hourly. Click "Load from EPICS" to automatically fill the left side. | * [https://bta.acc.jlab.org Fill out BTA] hourly. Click "Load from EPICS" to automatically fill the left side. | ||
− | *Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook] | + | * Fill and submit the [https://logbooks.jlab.org/checklists/151 shift checklist in the logbook] |
'''[[Every Run:]]''' | '''[[Every Run:]]''' | ||
Line 176: | Line 179: | ||
==<font color=blue>''' General Instructions''':</font>== | ==<font color=blue>''' General Instructions''':</font>== | ||
− | + | <-- | |
* For a given beam current, compute the FSD thresholds according to the [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf Establish Physics Quality Beam] document. Call MCC to update the values. Contact the beamline expert if there are questions about setting the FSD thresholds. | * For a given beam current, compute the FSD thresholds according to the [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf Establish Physics Quality Beam] document. Call MCC to update the values. Contact the beamline expert if there are questions about setting the FSD thresholds. | ||
* The main lights in the Hall (dome lights) and the Forward Carriage lights are being kept off because of light leaks affecting some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall. Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cooldown. | * The main lights in the Hall (dome lights) and the Forward Carriage lights are being kept off because of light leaks affecting some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall. Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cooldown. | ||
Line 186: | Line 189: | ||
* Check that no unnecessary beamline-related screens are open. This includes particularly the big beamline overview screen, but also and any motor/harp/collimator screens, and ioc health screens. | * Check that no unnecessary beamline-related screens are open. This includes particularly the big beamline overview screen, but also and any motor/harp/collimator screens, and ioc health screens. | ||
* Reference harp scans: [https://logbooks.jlab.org/entry/3571664 2C21], [https://logbooks.jlab.org/entry/3571676 2C24], [https://logbooks.jlab.org/entry/3571859 2H01] | * Reference harp scans: [https://logbooks.jlab.org/entry/3571664 2C21], [https://logbooks.jlab.org/entry/3571676 2C24], [https://logbooks.jlab.org/entry/3571859 2H01] | ||
− | + | --> | |
'''Every Shift:''' | '''Every Shift:''' | ||
− | *Follow run plan as outlined by RC | + | * Follow run plan as outlined by RC |
* If any concern about beam stability, ask MCC if orbit locks are on (they should be). | * If any concern about beam stability, ask MCC if orbit locks are on (they should be). | ||
* Keep shift summary up to date in HBLOG. Record all that happens. | * Keep shift summary up to date in HBLOG. Record all that happens. |
Revision as of 13:56, 5 October 2018
[edit]
Shift ScheduleShift ChecklistHot CheckoutBeam Time Accounting
|
Manuals |
Procedures |
JLab Logbooks
|
If calling local numbers (with area code prefix 757) from the counting room dial 9+[last 7 digits]. To call other area codes dial 91+[10 digit number]
|
|
- Note, all non-JLab numbers must be dialed with an area code. When calling from a counting-house landline, dial "9" first.
- To call JLab phones from outside the lab, all 4-digit numbers must be preceded by 757-269
- Click Here to edit Phone Numbers. Note, you then also have to edit the current page to force a refresh.
Click Here to edit Phone Numbers. Note, you then also have to edit this page to force a refresh.
CLAS12 Run Group M, Summer 2020
Beam energies: 1.1, 2.2, 4.4, 6.6 GeV (1.1 GeV/pass)
Important: Document all your work in the logbook!
RC: Someone
- (757) 575-7540
- 9 575 7540 from Counting Room
- someone@jlab.org
PDL: XXXXX
- (757) 876-1789
- 9 876-1789 from Counting Room
- someone@jlab.org
Run Plan:
Shift Worker Notes:<--
--> In case of other questions or uncertainties of what to do, call the RC |
General Instructions:<--
--> Every Shift:
Every Run: Log screenshots of:
|
Webcams |
Manuals |
Epics on the web
|
Hall-B
Run lists |
Accelerator |
Bluejean meetings
|