Difference between revisions of "Run Group A"
| Line 126: | Line 126: | ||
| valign=top width=50% | | | valign=top width=50% | | ||
| − | == <font color=blue>''' Run Plan: | + | == <font color=blue>''' Run Plan: May3-May 6 '''</font>== |
| − | May | + | May 3(Swing) - May 6 (Owl) |
| − | + | Torus Magnet is being ramped back up. Tagger is already ramped up to 462.7A. Check with MCC when beam might be ready and log it in the shift summary. When they are ready, put "blank" collimator in and then request 5nA CW beam first to be sent to tagger yoke. Perform hapr scan on 2c21A and tagger Verify that the FTC asymmetry is low, and the beam positions are good. Perform 2H01 Harp scan on both 2C21A and tagger, and verify the beam (widths) are good by following the beam-establishment procedure. If the results are satifactory, log the results, and request tagger magent degaussing. When that is done, move "20mm collimator" in and make sure all detectors are off except FTOF and FTC. Take beam blocker out and request 5nA CW beam to Faraday cup. Remind MCC our desired beam positions ("Note 3" above). Then increase the beam current to 50nA. Perform 2H01 harp scan. If results are acceptable, and FTC asymmetry are low (<1%) log it. | |
| − | + | If good beam is established, rest FSD thresholds to previous values (1000, 1000, 850000, 5000, for up, mid, dowstream and BOM) and change the drell time to 5ms. Call Yuri to turn SVT back on. Shift workers should then turn all other detectors back on. Put beam blocker in. Resume production data taking afterwards. | |
| − | + | If the above failed, follow the procedure for reestablishing the beam and notify RC and beamline expert. | |
| − | |||
| − | + | May 4 (Owl) -- May 6th (Owl) | |
| − | + | Continue produciton data taking. During owl shift, Genova group (Raffaella/Andrea) might call in and perform FT-trigger-only data for calibration purpose. Please work with them. This should take about 2hours. Continue production data afterwards | |
| − | + | During Day shift, a series of special runs will be taken. Take produciton data til 9am (or whenver 100M events are reached for the on-going run), then call Sergey for teh special runs, which includes the DAQ tests, and then random trigger runs. There might also be need for Drift chamber varying read-out window sizes runs at low intensity (2-5nA) that might be needed. Detailed plan will be updated druing noon time. | |
| − | + | After all special runs are over, continue produciton data taking until May 6 5am (Owl). A small reception full of fancy food will be held in the counting house at 7am for the early birds. No reservation needed. | |
| − | * From time to time, we might experience trigger bit issues (FT bits: 24, 25, and 26 and 27). bit 26 might not trigger the alarm but when this issue happens it will count abnormally high pre-prescale. For the time being, shift leaders cand try to do the sequence of End->Cance->Reset, ro_reboot adcft1 (and adcft2, adcft3), make sure the roc are | + | * From time to time, we might experience trigger bit issues (FT bits: 24, 25, and 26 and 27). bit 26 might not trigger the alarm but when this issue happens it will count abnormally high pre-prescale. For the time being, shift leaders cand try to do the sequence of End->Cance->Reset, ro_reboot adcft1 (and adcft2, adcft3), make sure the roc 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 persist, please continue take production data without fixing it -- please make sure you log this infor in the RCDB "Comment" field. |
* If the machine is down for few hours 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 50 nA and continue data for production. If there are issues with the beam call the RC. Sometimes MCC operator might ask to deliver tune beam --- please do not accept it. We need CW beam sent to the Faraday cup. If there is in deed a need for tune beam, it should be sent to the tagger dump with the tagger magent on. If you are uncertain, please call RC/PDL. | * If the machine is down for few hours 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 50 nA and continue data for production. If there are issues with the beam call the RC. Sometimes MCC operator might ask to deliver tune beam --- please do not accept it. We need CW beam sent to the Faraday cup. If there is in deed a need for tune beam, it should be sent to the tagger dump with the tagger magent on. If you are uncertain, please call RC/PDL. | ||
Revision as of 18:34, 3 May 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 A, Spring 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: Lei Guo
- (757) 575-7540
- 9 575 7540 from Counting Room
- lguo@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 UPSTREAM counters has to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and MIDSTREAM has to be in the rage 10-20 Hz (acceptable up to 50 Hz) @50 nA. Count rates in the range of hundreds or more may indicate bad beam tune or bleed-through from other Halls.
- Note 2: At the end of each run, follow the DAQ restart sequence
"end run", "cancel", "reset", then
if run ended correctly "download", "prestart", "iocjscalerRestartAll.sh", "go".
if run did not ended correctly, or ROCs had to be rebooted "Configure", "download", "prestart", "iocjscalerRestartAll.sh", "go".
After DAQ prestart is complete reboot the scaler IOCs with the command: iocjscalerRestartAll.sh.
Note: 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.5,Y=0.5) , 2H01 (X=1.0 mm, Y=-1.0 mm) see log entry https://logbooks.jlab.org/entry/3570290.
- Note 4: Do not turn OFF FTOF HVs, even during the beam tune
- Note 5: In case of the Torus and/or Solenoid Fast Dump do the following -
- Notify MCC, request beam OFF and drop Hall status to Power Permit
- Call Engineering on-call
- Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" filed add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org
- Notify Run Coordinator
- Call the MM expert to turn the detector off
- Call SVT expert to turn SVT off
- Turn off all the other detectors
- Note 6: When beam is being delivered to the Faraday Cup -
- the Fast Shut Down: Upstream, Midstream, Downstream, BOM and Solenoid should be always Unmasked,
- No changes to the FSD threshold without RC or beamline expert approval.
- Note 7: Do not turn on or off SVT - only SVT expert can do that
- Note 8: Any request for a special run or change of configuration has to be approved by RC & documented.
- Note 9: Check carefully BTA every hour and run script btaGet.py . It will print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.
- Note 10: Reset CLAS12MON frequently to avoid histogram saturation.
Run Plan: May3-May 6May 3(Swing) - May 6 (Owl)
If good beam is established, rest FSD thresholds to previous values (1000, 1000, 850000, 5000, for up, mid, dowstream and BOM) and change the drell time to 5ms. Call Yuri to turn SVT back on. Shift workers should then turn all other detectors back on. Put beam blocker in. Resume production data taking afterwards. If the above failed, follow the procedure for reestablishing the beam and notify RC and beamline expert.
Continue produciton data taking. During owl shift, Genova group (Raffaella/Andrea) might call in and perform FT-trigger-only data for calibration purpose. Please work with them. This should take about 2hours. Continue production data afterwards During Day shift, a series of special runs will be taken. Take produciton data til 9am (or whenver 100M events are reached for the on-going run), then call Sergey for teh special runs, which includes the DAQ tests, and then random trigger runs. There might also be need for Drift chamber varying read-out window sizes runs at low intensity (2-5nA) that might be needed. Detailed plan will be updated druing noon time. After all special runs are over, continue produciton data taking until May 6 5am (Owl). A small reception full of fancy food will be held in the counting house at 7am for the early birds. No reservation needed.
Sometimes, a couple of RICH channel scalers would go to 0 and there is no alarm, even though the "# of fjibers 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, please refer to the instruction below.
|
General Instructions:
Every Shift:
Every Run: Log screenshots of:
|
Webcams |
Manuals |
Epics on the web
|
|
|
|
Hall-B
Run lists |
Accelerator |
Bluejean meetings
|
|
|
