Difference between revisions of "Run Group C"
Line 77: | Line 77: | ||
* (757) 575-7540 or | * (757) 575-7540 or | ||
* (757) 639-6640 | * (757) 639-6640 | ||
− | + | * Dial "9" before all numbers when calling from CH | |
=== PDL: Eugene Pasyuk === | === PDL: Eugene Pasyuk === | ||
− | * | + | * (757) 876-1789 , x6020 office |
<!--* 9 876-1789 from Counting Room--> | <!--* 9 876-1789 from Counting Room--> | ||
=== [https://userweb.jlab.org/~kuhn/RGC/RCschedule.pdf Run Coordinator and Target Expert Schedule] === | === [https://userweb.jlab.org/~kuhn/RGC/RCschedule.pdf Run Coordinator and Target Expert Schedule] === | ||
Line 90: | Line 90: | ||
== <font color=blue>''' Run Plan: June 2022 '''</font> == | == <font color=blue>''' Run Plan: June 2022 '''</font> == | ||
− | + | * Tue, 6/7: Complete beam line; Hall closes up at 3:00 for beam line magnet tests | |
+ | * Wed, 6/8: Finish all surveys and alignments, calibrate BPMs. Test target samples (TE, polarize). Check out raster. | ||
+ | * Thu, 6/9: Continue HCO for all components, target polarization / swap tests. Install cross-hair target probe for beam. If ready, close Hall and get ready for beam. | ||
+ | * Fri, 6/10: If possible, tune 1-pass beam to FC. Begin commissioning and raster calibration | ||
+ | * Weekend: Take data with MT, 12C and polarized NH3 targets. | ||
+ | * Early next week: If time allows, take data on CH2, CD2 and polarized ND3. | ||
+ | * Then change from 1-pass to 5 pass. | ||
− | Run duration 100M events or 4 hours, whichever comes first. | + | === 1-pass (2.1 GeV) Running conditions === |
+ | * Establish optimal compromise between raster size (if possible, 7 mm radius), luminosity (goal: 5 nA), and background. | ||
+ | * Run duration 100M events or 4 hours, whichever comes first. | ||
+ | ** For empty target runs, increase beam current as much as possible (up to 50 nA). | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== <font color=blue> DAQ configuration </font> == | == <font color=blue> DAQ configuration </font> == | ||
− | * Configuration <tt> | + | * Configuration <tt>TBA</tt>, trigger file <tt>rgc_100MeV_V1.0_no_DC.trg</tt> |
* NOTE: UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to do a RICH recovery - instead do this in between runs. | * NOTE: UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to do a RICH recovery - instead do this in between runs. | ||
− | * NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems. | + | * NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems.'''Watch the raster pattern!''' |
* At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font>: | * At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font>: | ||
** "end run", if the run ended correctly then: "prestart", "go" | ** "end run", if the run ended correctly then: "prestart", "go" | ||
Line 123: | Line 121: | ||
'''Nominal Beam Positions''' | '''Nominal Beam Positions''' | ||
− | *2H01, X: | + | *2H01, X: ? mm, Y: ? mm (only used/useful without restoring) |
− | *2C24, X: - | + | *2C24, X: -? mm, Y: ? mm (orbit lock) |
− | '''FSD Thresholds''' | + | '''FSD Thresholds''' (to be updated) |
* Upstream: 2000 Hz | * Upstream: 2000 Hz | ||
* Midstream: 2000 Hz | * Midstream: 2000 Hz | ||
Line 153: | Line 151: | ||
== <font color=blue> Notes </font> == | == <font color=blue> Notes </font> == | ||
− | #'''LTCC''' | + | # '''LTCC''': 4 sectors are used (2,3,5,6) |
− | # ''' | + | # '''NEW:''' TWO sectors (1 and 4) now have a RICH installed (RICH II in Sector 1, RICH I in Sector 4). |
+ | # '''FMT''' is NOT installed. | ||
+ | # '''BAND''' is NOT installed. | ||
# 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 access, they should be switched off when leaving the Hall. Refer to these photos: | # 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 access, they should be switched off when leaving the Hall. Refer to these photos: | ||
#* ON: [https://logbooks.jlab.org/entry/3825712] | #* ON: [https://logbooks.jlab.org/entry/3825712] | ||
Line 161: | Line 161: | ||
# In case of a '''Torus and/or Solenoid Fast Dump''' do the following: | # 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 | #* Notify MCC to request beam OFF and to drop Hall B status to Power Permit | ||
− | #* Call Engineering on-call | + | #* Call Engineering on-call and target expert |
#* Make a separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Probir Goshal, Dave Kashy, and esr-users@jlab.org | #* Make a separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Probir Goshal, Dave Kashy, and esr-users@jlab.org | ||
#* Notify Run Coordinator | #* Notify Run Coordinator | ||
Line 168: | Line 168: | ||
== <font color=blue> Known Issues </font> == | == <font color=blue> Known Issues </font> == | ||
+ | To be updated | ||
* '''Beamline overview''' No Data from Faraday cup viewer camera, network switch died | * '''Beamline overview''' No Data from Faraday cup viewer camera, network switch died |
Revision as of 12:17, 7 June 2022
- Shift Documentation
- Phone Numbers
- Short Term Schedule
- Shift Expert
- Remote Worker Shift
- Monitoring
- Useful Links
Shift ScheduleHall B LogbookESAD, COO, RSADShift ChecklistHot CheckoutBeam Time Accounting
|
Manuals
|
Procedures |
JLab Logbooks
|
|
|
- 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 the current page to force a refresh.
CLAS12 Run Group C, Summer 2022
Daily RC Meetings at 14:00: CH Room 200C, and on Zoom
Zoom information: Link, Meeting ID: 160 867 4253, Passcode: 786506
RC: Sebastian Kuhn
- (757) 575-7540 or
- (757) 639-6640
- Dial "9" before all numbers when calling from CH
PDL: Eugene Pasyuk
- (757) 876-1789 , x6020 office
Run Coordinator and Target Expert Schedule
Longterm Run Plan
IMPORTANT NOTE: Before leaving the hall and going to beam permit check that dome lights, froward carriage lights, and pie tower lights are OFF
Run Plan: June 2022
- Tue, 6/7: Complete beam line; Hall closes up at 3:00 for beam line magnet tests
- Wed, 6/8: Finish all surveys and alignments, calibrate BPMs. Test target samples (TE, polarize). Check out raster.
- Thu, 6/9: Continue HCO for all components, target polarization / swap tests. Install cross-hair target probe for beam. If ready, close Hall and get ready for beam.
- Fri, 6/10: If possible, tune 1-pass beam to FC. Begin commissioning and raster calibration
- Weekend: Take data with MT, 12C and polarized NH3 targets.
- Early next week: If time allows, take data on CH2, CD2 and polarized ND3.
- Then change from 1-pass to 5 pass.
1-pass (2.1 GeV) Running conditions
- Establish optimal compromise between raster size (if possible, 7 mm radius), luminosity (goal: 5 nA), and background.
- Run duration 100M events or 4 hours, whichever comes first.
- For empty target runs, increase beam current as much as possible (up to 50 nA).
DAQ configuration
- Configuration TBA, trigger file rgc_100MeV_V1.0_no_DC.trg
- NOTE: UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to do a RICH recovery - instead do this in between runs.
- NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems.Watch the raster pattern!
- At the end of each run, follow the STANDARD DAQ RESTART SEQUENCE:
- "end run", if the run ended correctly then: "prestart", "go"
- if the run did not end correctly or if any ROCs had to be rebooted:
- "cancel", "reset"
- "configure", "download", "prestart", "go"
- After each step, make sure it is completed in the Run Control message window. If a ROC has crashed, find which one it is, issue a roc_reboot command ON JUST THAT ROC and try again. Contact the DAQ expert if there are any questions.
References and Standards
Solenoid set-point of 2417.5 A results in read back 2419.57 A and exactly 5.00 T field on center
Nominal Beam Positions
- 2H01, X: ? mm, Y: ? mm (only used/useful without restoring)
- 2C24, X: -? mm, Y: ? mm (orbit lock)
FSD Thresholds (to be updated)
- Upstream: 2000 Hz
- Midstream: 2000 Hz
- Downstream: 500000 Hz
- BOM: 10000
- 5 ms dwell time
Reference Harp Scans for Beam on Faraday Cup 2H01 [1]
Reference Harp Scans for Beam on Tagger dump 2C21 [2], tagger harp [3]
Reference Monitoring Histograms
Counter rates
- Upstream counters integrated rates: 0-15 Hz (acceptable up to 100 Hz are acceptable) @50 nA.
- Midstream counters: 10-20 Hz (acceptable up to 50 Hz) @50 nA.
- Counting rates of ~ hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.
NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms at least once every 30 - 60 minutes to make sure there are no major detector problems.
(remote) shift worker: see dedicated Remote Shifts tab above. |
TasksEvery Run:
Every Shift:
Regularly:
|
|
Webcams
|
Manuals |
Epics on the web
|
Live Monitoring Links |
Hall-B |
Accelerator |
ZOOM meetings
|