Difference between revisions of "Run Group C"
Jump to navigation
Jump to search
(Created page with "= Shift Documentation = <!--####################################### SHIFT DOCUMENTATION ########################################--> {| {{TableStyle1}} | valign=top | ===[ht...") |
|||
| Line 40: | Line 40: | ||
* [[Media:HarpScanManual.pdf|Performing Harp Scans]] | * [[Media:HarpScanManual.pdf|Performing Harp Scans]] | ||
* [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Tunnel/Hall Access] | * [https://wiki.jlab.org/hps-run/images/0/0c/Accessing_the_tunnel.pdf Tunnel/Hall Access] | ||
| − | * [https://www.jlab.org/Hall-B/run-web/ | + | * [https://www.jlab.org/Hall-B/run-web/index_rgc.html ESAD, COO, RSAD] |
| valign=top | | | valign=top | | ||
| Line 102: | Line 102: | ||
== <font color=blue> DAQ configuration </font> == | == <font color=blue> DAQ configuration </font> == | ||
| − | + | * PROD67_noVTPread </b>, production trigger <b> rgm_6GeV_inb_v1_0.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. | |
| − | + | * 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" | |
| − | + | ** 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. | |
| − | * | ||
| − | |||
| − | |||
| − | * 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. | ||
== <font color=blue> References and Standards </font>== | == <font color=blue> References and Standards </font>== | ||
| − | |||
| − | + | '''Nominal Beam Positions''' | |
*2H01, X: -0.6 mm, Y: 0.8 mm | *2H01, X: -0.6 mm, Y: 0.8 mm | ||
*2C24, X: -2.0 mm, Y: +0.6 mm | *2C24, X: -2.0 mm, Y: +0.6 mm | ||
| − | + | '''FSD Thresholds''' | |
* Upstream: 2000 Hz | * Upstream: 2000 Hz | ||
* Midstream: 2000 Hz | * Midstream: 2000 Hz | ||
| Line 133: | Line 125: | ||
* 5 ms dwell time | * 5 ms dwell time | ||
| − | + | '''Reference Harp Scans for Beam on Faraday Cup 2H01''' [https://logbooks.jlab.org/entry/3963256] | |
| − | + | '''Reference Harp Scans for Beam on Tagger dump 2C21''' [https://logbooks.jlab.org/entry/3963244], tagger harp [https://logbooks.jlab.org/entry/3963250] | |
| − | + | '''Reference Monitoring Histograms''' | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''Counter rates''' | |
* Upstream counters integrated rates: 0-15 Hz (acceptable up to 100 Hz are acceptable) @50 nA. | * 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. | * 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. | * Counting rates of ~ hundreds of Hz may indicate bad beam tune or bleed-through from other Halls. | ||
| − | + | '''Beamline vacuum''': should be not higher than 5e-5. | |
| + | |||
| + | <!--####################################### Notes/Known Issues ################################################--> | ||
| + | <!-- | ||
= Notes/Known Issues = | = Notes/Known Issues = | ||
| − | |||
'''NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms (mon12) 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 (mon12) at least once every 30-60 minutes to make sure there are no major detector problems.''' | ||
| Line 170: | Line 160: | ||
#* Turn off all detectors | #* Turn off all detectors | ||
# Observe the guidance of the alarm handler. | # Observe the guidance of the alarm handler. | ||
| − | |||
| − | |||
== <font color=blue> Known Issues </font> == | == <font color=blue> Known Issues </font> == | ||
| Line 190: | Line 178: | ||
* '''RICH''' recovery only between runs. also when you see problems like a missing tile | * '''RICH''' recovery only between runs. also when you see problems like a missing tile | ||
* '''RICH''' FPGA temperatures can show yellow tiles. Yellow tiles in the RICH temperature map are normal. It is done just to pay attention to the tiles with temp>70 degrees. The alarm is set to 75 degrees https://logbooks.jlab.org/entry/3975547 | * '''RICH''' FPGA temperatures can show yellow tiles. Yellow tiles in the RICH temperature map are normal. It is done just to pay attention to the tiles with temp>70 degrees. The alarm is set to 75 degrees https://logbooks.jlab.org/entry/3975547 | ||
| + | --> | ||
= Shift Expert = | = Shift Expert = | ||
Revision as of 11:06, 29 March 2022
[edit]
- 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
RC: Jane Doe
- (757) 575-7540
PDL: Eugene Pasyuk
- (757) 876-1789
Run Plan: June 2022
Production runs use PROD67_noVTPread and the trigger rgm_6GeV_inb_v1_0.trg
Run duration 100M events or 4 hours, whichever comes first.
- run 6GeV 80 nA on Ca48 target (240 mg/cm2), beam blocker IN, until SAD
- low luminosity runs:(ca 3pm - 9pm on Feb 7)
- 2 hrs 5nA
- 2 hrs 10 nA
- 2 hrs 40 nA
- the run on Ca48 until 6am, Feb 8
- 6am Feb 8: Investigate BLA tune beam trips with tune beam to Hall B, https://devweb.acc.jlab.org/CSUEApps/atlis/task/24015
- RC will be there at 6 am and follow Eugene's instruction
- put the blank collimator in
- turn HV off for all tracking detectors, just in case if the tagger magnet trips during the test
- MCC may mask upstream halo FSD if necessary but keep all other FSD unmasked
DAQ configuration
- PROD67_noVTPread , production trigger rgm_6GeV_inb_v1_0.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.
- 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
Nominal Beam Positions
- 2H01, X: -0.6 mm, Y: 0.8 mm
- 2C24, X: -2.0 mm, Y: +0.6 mm
FSD Thresholds
- 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.
Beamline vacuum: should be not higher than 5e-5.
|
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 |
Hall Webcams |
Epics on the web
|
Live Monitoring Links
|
|
|
Hall-B
Run lists |
AcceleratorReferences |
ZOOM meetings
|
|
|
