Difference between revisions of "The HPS Run Wiki"
Line 117: | Line 117: | ||
<b> To establish good beam conditions first send beam to the tagger dump (ask MCC to turn ON the tagger).</b> | <b> To establish good beam conditions first send beam to the tagger dump (ask MCC to turn ON the tagger).</b> | ||
# Check position, it should corresponds to previous good settings [https://logbooks.jlab.org/entry/3334787] | # Check position, it should corresponds to previous good settings [https://logbooks.jlab.org/entry/3334787] | ||
− | # Check profile, it should correspond to previous | + | # Check profile using 2C21 and tagger harp scans, it should correspond to previous settings ([https://logbooks.jlab.org/entry/3334749],[https://logbooks.jlab.org/entry/3334751]) |
# Beam can be accepted at this level if it is within 20% of previous standards | # Beam can be accepted at this level if it is within 20% of previous standards | ||
− | + | # Halo counters TAG-L/T/T2 should be ~10Hz/nA [https://logbooks.jlab.org/entry/3326723], | |
− | + | <b>Turn the chicane ON</b> | |
− | + | # Strictly follow the procedure in the beam line manual! | |
− | + | <b>Send beam to the Faraday cup</b> | |
− | + | # Check 3mm collimator is IN | |
− | * | + | # Check HPS target is OUT |
− | + | # Tune beam profile with 2H02A harp scan to be wide in X-direction and narrow in Y (see ref [https://logbooks.jlab.org/entry/3334783]) | |
− | * The halo counter rates on HPS, HPS-L/R/T/SC, depends on the collimator and HPS chicane settings, but should not be more than 100 Hz/nA[https://logbooks.jlab.org/entry/3328991] | + | # The halo counter rates before HPS must be low: |
− | + | #* UPS-L and UPS-R few Hz/nA, | |
− | <b> Always read previous log entries, compare settings of BPMs and correctors with previous settings using scaler_hps GUI. </b> | + | #* The tagger counters and downstream counters should count <<1 Hz/nA |
+ | #* The halo counter rates on HPS, HPS-L/R/T/SC, depends on the collimator and HPS chicane settings, but should not be more than 100 Hz/nA [https://logbooks.jlab.org/entry/3328991] | ||
+ | # Positions on BPMs must be close to what where before [https://logbooks.jlab.org/entry/3334787] | ||
+ | <b>Before accepting beam, make sure all the previous conditions are met. Always read previous log entries, compare settings of BPMs and correctors with previous settings using scaler_hps GUI. </b> | ||
</font> | </font> | ||
==<font color=red size=+2>Every Run:</font>== | ==<font color=red size=+2>Every Run:</font>== | ||
− | # | + | # <b>ECal logs</b> |
− | # b | + | #* Pdf output from the ECal monitoring App |
− | # | + | #* FADC & DISC Scalers |
− | # | + | # <b>SVT logs</b> |
− | + | #* Occupencies | |
+ | #* Timing plots (Max Sample) | ||
+ | #* Track momenta | ||
+ | # <b> DAQ logs </b> | ||
+ | #* Trigger rate GUI | ||
Revision as of 14:04, 25 April 2015
Important Phone NumbersShift ScheduleShift-Taker's Checklist (old)Hot CheckoutBeam Time AccountingHPS Run Spreadsheet |
Procedures
|
Manuals |
JLab Logbooks
|
RC: Raphael Dupre
PDL: Stepan StepanyanEvery Shift:
SVT InstructionsBefore sending beam to Faraday cup, verify (and page SVT expert if otherwise):
The first time sending beam to the Faraday cup after the hall is closed, page the SVT expert.
Acceptable Beam Conditions:To establish good beam conditions first send beam to the tagger dump (ask MCC to turn ON the tagger).
Turn the chicane ON
Send beam to the Faraday cup
Before accepting beam, make sure all the previous conditions are met. Always read previous log entries, compare settings of BPMs and correctors with previous settings using scaler_hps GUI. Every Run:
|
Run Plan: April 17-22, 2015 (day/swing/owl)During week days, Mon-Thursday, there will be no Day shifts due to work in the hall. Friday day shift may happen (slim probability), so be prepared. Monday Swing shift will recover after significant amounts of accelerator work, so a full tune up of the Hall-B beamline will be required. Short Term Schedule: Study Trigger and SVT running conditions. We will be running with 1.05GeV beam. This beam needs to be carefully restored, first to the tagger dump, then the alcove and Faraday cup screen. Before sending beam to the alcove, call the RC.
When we're back, proceed with program
MCC works on beam optics and matching, and tunes beam to tagger
Standards are on this page: ACCEPTABLE BEAM CONDITIONS.
Restore Beam to the Hall-B Dump
Energize Chicane
Be very careful when changing magnet currents when beams are on. Must enter new current ACCURATELY. Small steps (few amps) only.
Are we centered? Beamline Expert should enter new target positions if not.
Subsystem Commissioning Studies. Begin Data Taking. DO NOT RUN MORE THAN 30 MINUTES ABOVE 50 nA WITHOUT THE BEAM BLOCKER
|
Trigger | |||
---|---|---|---|
FADC | GTP | ||
NSB/NSA | 20/100 ns | Samples Before/After | 3/3 |
Readout Threshold | 12 ADC | Seed Threshold | 80 MeV |
SSP | |||
Singles-0 | Singles-1 | ||
# Hits | >2 | >2 | |
Cluster Energy | 0.1 < E < 2.5 GeV | 0.5 < E < 1.2 GeV | |
Pairs-0 | Pairs-1 | ||
Cluster Energy | 0.09 < E < 1.3 GeV | 0.1 < E < 0.6 GeV | |
Energy Sum | 0.19 GeV < E < 2.2 GeV | 0.21 < E < 1.0 GeV | |
Energy Difference | dE < 1.2 GeV | dE < 0.65 GeV | |
Coplanarity | N/A | Theta < 40 deg | |
Energy Slope | N/A | > 0.6 GeV | |
TI Prescales | |||
Singles-0 | Singles-1 | Pairs-0 | Pairs-1 |
0 | 0 | 0 | 0 |
|
|
|
|
|
|
|
Webcams: |
Trigger: |
Accelerator: Slow Controls:
|
Online & Offline: |