Difference between revisions of "Run Group K"
(Created page with "= Shift Documentation = <!--####################################### SHIFT DOCUMENTATION ########################################--> {| {{TableStyle1}} | valign=top | <!--==...") |
|||
Line 67: | Line 67: | ||
<center><font color=blue size=4> | <center><font color=blue size=4> | ||
''' CLAS12 Run Group K, Fall 2018 </font> '''<br> | ''' CLAS12 Run Group K, Fall 2018 </font> '''<br> | ||
− | |||
''' Beam energy 10.6 GeV (5 pass) '''<br> | ''' Beam energy 10.6 GeV (5 pass) '''<br> | ||
''' Important: Document all your work in the logbook! '''<br> | ''' Important: Document all your work in the logbook! '''<br> | ||
Line 74: | Line 73: | ||
</center> | </center> | ||
− | == RC: | + | == RC: Annalisa D'Angelo == |
* (757) 575-7540 | * (757) 575-7540 | ||
* 9 575 7540 from Counting Room | * 9 575 7540 from Counting Room | ||
− | * [mailto: | + | * [mailto:annalisa@jlab.org annalisa@jlab.org] |
== PDL: Eugene Pasyuk == | == PDL: Eugene Pasyuk == | ||
Line 87: | Line 86: | ||
* '''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 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. |
− | * ''' Note 2: At the end of each run, follow the DAQ restart sequence ''' | + | * ''' Note 2: At the end of each run, follow the standard DAQ restart sequence ''' |
+ | "end run", "cancel", "reset", then if the run ended correctly, '''"download", "prestart", "go"'''. If the run did not end correctly or if any ROCs had to be rebooted, "configure", "download", "prestart", "go". | ||
− | + | After each step, make sure it is complete in the Run Control message window. If a ROC has crashed, find which one it is and issue a roc_reboot command and try again. Contact the DAQ expert if there are any questions. | |
− | + | * '''Note 3: Nominal beam positions: <font color=red>''' ''' 2C24A (X=0.2 mm, Y=0.2 mm) ''', '''2H01 (X=0.3 mm, Y=-0.9 mm)''' </font> | |
− | + | * '''Note 4: Do not turn OFF FTOF HVs, even during the beam tune with CW beam (turn off when doing a Moller run or if there is tuned/pulsed beam in the upstream beamline)''' | |
− | + | * '''Note 5: In case of a Torus and/or Solenoid Fast Dump do the following: | |
− | + | *# Notify MCC to request beam OFF and to drop Hall B status to Power Permit | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | * '''Note 5: In case of | ||
− | *# Notify MCC | ||
*# Call Engineering on-call | *# Call Engineering on-call | ||
− | *# Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" | + | *# Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org |
*# Notify Run Coordinator | *# Notify Run Coordinator | ||
− | + | *# Turn off all detectors''' | |
− | |||
− | *# Turn off all | ||
− | *'''Note 6: When beam is being delivered to the | + | *'''Note 6: When beam is being delivered to the Faraday Cup:''' |
− | *# the Fast Shut Down: Upstream, Midstream, Downstream, BOM and Solenoid should be | + | *# the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state <font color=red>UNMASKED</font> |
− | *# No changes to the FSD threshold without RC or beamline expert approval | + | *# No changes to the FSD threshold should be made without RC or beamline expert approval |
+ | <!--*'''Note 7: Do not turn on the SVT or MM - only the SVT or MM expert can do that''' --> | ||
− | *'''Note 7 | + | *'''Note 7: Any request for a special run or change of configuration has to be approved by the RC & documented''' |
− | |||
− | |||
− | |||
− | + | *'''Note 8: Carefully check the BTA every hour and run the script <font color=red>btaGet.py</font> to print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.''' | |
− | + | *'''Note 9: Reset CLAS12MON frequently to avoid histogram saturation.''' | |
− | + | *'''Note 10: 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 Do not Turn OFF MVT HV: Instead go to 'Restore settings' from the MVT overview screen: | ||
+ | *# SafeMode.snp for beam tuning and Moeller runs | ||
+ | *# MV_HV_FullField.snp for full solenoid field | ||
+ | *# MV_HV_MidField.snp wgeb solenoid < 4T | ||
+ | ''' | ||
+ | *'''NOTE 12 Check the vacuum periodically, make sure vacuum id not higher than 5e-5 ''' | ||
− | + | *''' NOTE 13 Always reset the CFD threshold after all power off/on on the CFD crate''' | |
− | + | After the CAMAC crate 1 holding the CND CFD boards is switched | |
+ | off for any reason, it is mandatory to reset the associated thesholds typing the | ||
+ | following command from any clon machine terminal: | ||
+ | >> $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0 | ||
− | + | *'''NOTE 14: As of 10/25, the issue of detector scalers being frozen and starting a new run has been resolved.''' Shift workers should anyway check routinely scalers to verify they update correctly and make a logbook entry if anomalies are observed after starting a new run. | |
− | + | *'''NOTE 15: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766''' | |
− | + | {| {{TableStyle1}} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | | valign=top width=50% | | ||
− | < | + | <i>(Updated: Nov. 20, 2018 at 11:50>/i> |
− | + | * Before beam delivery ramp torus to -3770 A (100% field - negatives outbending) and solenoid to 2416 A (100% field); empty target and turn all detectors off | |
+ | * Tune beam in upstream beamline following nominal procedures | ||
+ | * Take Moller run | ||
+ | * Tune 5 nA beam to Faraday Cup following nominal procedures | ||
+ | * Ensure the beam position at the target is optimized for minimal rates | ||
+ | * Take 2 hr empty target run (beam current TBD) | ||
+ | * Begin to optimize DAQ and trigger setup | ||
+ | * Turn beam off and fill target | ||
+ | * Take 2 hr run with 5 nA | ||
+ | * Complete initial trigger studies | ||
+ | * Production with configuration PROD66 and '''trigger_v23.trg''' at '''30''' nA. | ||
+ | * Any questions or uncertainty about what to do please call RC | ||
− | + | '''<font color=red> Make sure to save ROC Rates (MB/s) GUI to logbook for each run together with beam screens and trigger GUI </font>''' | |
− | ** | + | |
− | ** | + | * <font color=blue> ''' Make sure that the FSD thresholds are set correctly and they are unmask when ready to receive beam to the FC @50 nA |
+ | ** Upstream 2000 | ||
+ | ** Midstream 1000 | ||
+ | ** Downstream 900000 | ||
+ | ** BOM 15000 | ||
+ | ** Dwell time 5 ms | ||
+ | '''</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. --> |
− | |||
− | |||
− | |||
− | |||
− | * | + | * If the machine is down for more than 30 min ask for low current first 5 nA ,make sure that the beam is stable both in position and current, check that the rates are OK on all the detectors and halo counters. Then ask for 45 nA and continue data for production. If there are issues with the beam call RC. Sometimes MCC operator may ask to deliver tuned mode beam --- do not accept it. We need CW beam sent to the Faraday cup. If there is indeed a need for tuned beam, it should be sent to the tagger dump with the tagger magnet on. If you are uncertain, please call RC/PDL. |
− | |||
− | |||
− | |||
− | * | + | <!--* 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. |
− | |||
− | |||
− | + | '''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. | ||
− | |||
* 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] | ||
Line 282: | Line 186: | ||
* main scaler GUI display | * main scaler GUI display | ||
* Detector occupancy plots | * Detector occupancy plots | ||
− | * Trigger rate | + | * Trigger rate GUI |
* Beam strip charts | * Beam strip charts | ||
− | * | + | * FT-Cal FADC scalers |
+ | --> | ||
− | |||
| valign=top | | | valign=top | | ||
Line 297: | Line 201: | ||
* In case of loss of communication with IOCBTARG, follow instructions at https://logbooks.jlab.org/entry/3502218 | * In case of loss of communication with IOCBTARG, follow instructions at https://logbooks.jlab.org/entry/3502218 | ||
* With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem. | * With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem. | ||
− | * All jscaler iocs (iocjscalerX) on the health screen (under DAQ tab) must be restarted after every DAQ prestart is completed. Follow this link for detailed instructions https://userweb.jlab.org/~baltzell/CLAS12/SC/jlabScalersOps.txt | + | <!--* All jscaler iocs (iocjscalerX) on the health screen (under DAQ tab) must be restarted after every DAQ prestart is completed. Follow this link for detailed instructions https://userweb.jlab.org/~baltzell/CLAS12/SC/jlabScalersOps.txt--> |
− | * Check that no | + | * 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] | ||
'''Every Shift:''' | '''Every Shift:''' | ||
Line 307: | Line 212: | ||
* 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. | ||
+ | * When you do BTA keep track of of BANU. Include at the end of shift summary log details of BANU: the reason and duration. | ||
* 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] | ||
<!-- * Once a shift between the runs Restart FTT gas flow. Follow these steps: | <!-- * Once a shift between the runs Restart FTT gas flow. Follow these steps: | ||
Line 318: | Line 224: | ||
'''Every Run:''' | '''Every Run:''' | ||
− | '' Log screenshots of | + | '' Log screenshots of the following screens, and |
+ | <font color="orange"> make sure at the moment you capture the screen the beam is ON </font> '' | ||
* main scaler GUI display | * main scaler GUI display | ||
* Detector occupancy plots | * Detector occupancy plots | ||
− | * Trigger rate | + | * Trigger rate GUI |
+ | * Roc Rates (MB/s) GUI | ||
* Beam strip charts | * Beam strip charts | ||
− | * | + | * FT-Cal FADC scalers |
|} | |} |
Revision as of 11:56, 20 November 2018
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 K, Fall 2018
Beam energy 10.6 GeV (5 pass)
Important: Document all your work in the logbook!
Remember to fill in the run list at the beginning and end of each run (clas12run@gmail.com can fill the run list)
RC: Annalisa D'Angelo
- (757) 575-7540
- 9 575 7540 from Counting Room
- annalisa@jlab.org
PDL: Eugene Pasyuk
- (757) 876-1789
- 9 876-1789 from Counting Room
- pasyuk@jlab.org
- 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.
- Note 2: At the end of each run, follow the standard DAQ restart sequence
"end run", "cancel", "reset", then if the run ended correctly, "download", "prestart", "go". If the run did not end correctly or if any ROCs had to be rebooted, "configure", "download", "prestart", "go".
After each step, make sure it is complete in the Run Control message window. If a ROC has crashed, find which one it is and issue a roc_reboot command and try again. Contact the DAQ expert if there are any questions.
- Note 3: Nominal beam positions: 2C24A (X=0.2 mm, Y=0.2 mm) , 2H01 (X=0.3 mm, Y=-0.9 mm)
- Note 4: Do not turn OFF FTOF HVs, even during the beam tune with CW beam (turn off when doing a Moller run or if there is tuned/pulsed beam in the upstream beamline)
- Note 5: In case of a Torus and/or Solenoid Fast Dump do the following:
- Notify MCC to request beam OFF and to drop Hall B status to Power Permit
- Call Engineering on-call
- Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org
- Notify Run Coordinator
- Turn off all detectors
- Note 6: When beam is being delivered to the Faraday Cup:
- the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state UNMASKED
- No changes to the FSD threshold should be made without RC or beamline expert approval
- Note 7: Any request for a special run or change of configuration has to be approved by the RC & documented
- Note 8: Carefully check the BTA every hour and run the script btaGet.py to print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.
- Note 9: Reset CLAS12MON frequently to avoid histogram saturation.
- Note 10: Shift workers must check the occupancies! Use this tool to compare to previous runs: https://clas12mon.jlab.org/mon12/histograms/
- Note 11 Do not Turn OFF MVT HV: Instead go to 'Restore settings' from the MVT overview screen:
- SafeMode.snp for beam tuning and Moeller runs
- MV_HV_FullField.snp for full solenoid field
- MV_HV_MidField.snp wgeb solenoid < 4T
- NOTE 12 Check the vacuum periodically, make sure vacuum id not higher than 5e-5
- NOTE 13 Always reset the CFD threshold after all power off/on on the CFD crate
After the CAMAC crate 1 holding the CND CFD boards is switched off for any reason, it is mandatory to reset the associated thesholds typing the following command from any clon machine terminal:
>> $CODA/src/rol/Linux_x86_64/bin/cnd_cfd_thresh -w 0
- NOTE 14: As of 10/25, the issue of detector scalers being frozen and starting a new run has been resolved. Shift workers should anyway check routinely scalers to verify they update correctly and make a logbook entry if anomalies are observed after starting a new run.
- NOTE 15: To solve common SVT issues see https://logbooks.jlab.org/entry/3615766
(Updated: Nov. 20, 2018 at 11:50>/i>
Make sure to save ROC Rates (MB/s) GUI to logbook for each run together with beam screens and trigger GUI
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 the following screens, and make sure at the moment you capture the screen the beam is ON
|
Webcams |
Manuals |
Epics on the web
|
Hall-B
Run lists |
Accelerator |
Bluejean meetings
|