Difference between revisions of "Run Group A"
Jump to navigation
Jump to search
| Line 140: | Line 140: | ||
<i>(Updated: Oct. 17 2018 at 15:30)</i> | <i>(Updated: Oct. 17 2018 at 15:30)</i> | ||
| + | ""Continue production data taking at 45 nA, full target at nominal DAQ setting."" | ||
| + | |||
| + | |||
* <font color=red> ''' Make sure that the FSD thresholds are set correctly and they are unmask when ready to receive beam to the FC | * <font color=red> ''' Make sure that the FSD thresholds are set correctly and they are unmask when ready to receive beam to the FC | ||
** Upstream 1000 | ** Upstream 1000 | ||
| Line 148: | Line 151: | ||
'''</font> | '''</font> | ||
| − | |||
| − | |||
== <font color=blue>''' Shift Worker Notes:'''</font>== | == <font color=blue>''' Shift Worker Notes:'''</font>== | ||
| Line 156: | Line 157: | ||
* 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. | ||
| − | * If the machine is down for | + | * 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 the RC. Sometimes MCC operator might ask to deliver tuned 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: | * 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: | ||
Revision as of 16:03, 17 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 A, 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
RC: Stepan Stepanyan
- (757) 575-7540
- 9 575 7540 from Counting Room
- markov@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", "iocjscalerRestartAll.sh", "go". If the run did not end correctly or if any ROCs had to be rebooted, "configure", "download", "prestart", "iocjscalerRestartAll.sh", "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.4 mm) , 2H01 (X=0.6 mm, Y=0.2 mm)
- Note 4: Do not turn OFF FTOF HVs, even during the beam tune with CW beam (turn off if 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 Due to instability of the solenoid field measurement, BMT software solenoid interlock is currently bypassed. In case of the solenoid accident, shift operator should put the BMT to the safe mode manually.
Run Plan:(Updated: Oct. 17 2018 at 15:30) ""Continue production data taking at 45 nA, full target at nominal DAQ setting.""
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
|
|
|
