Difference between revisions of "Run Group M"
Line 178: | Line 178: | ||
== <font color=blue> Notes </font> == | == <font color=blue> Notes </font> == | ||
− | * 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. | + | * Note 1: 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] | ||
** OFF: [https://logbooks.jlab.org/entry/3825731] | ** OFF: [https://logbooks.jlab.org/entry/3825731] | ||
** Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cool down. | ** Note that the dome lights when switched off cannot be turned back on immediately because they require 10-15 min to cool down. | ||
− | * Note | + | * Note 2: 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 to 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 a bad beam tune or bleed-through from other Halls. | The integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up to 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 a bad beam tune or bleed-through from other Halls. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
* Note 3: 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 3: 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 4: In case of a Torus and/or Solenoid Fast Dump do the following: | + | * Note 4: 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 | ||
Line 201: | Line 195: | ||
*# Turn off all detectors | *# Turn off all detectors | ||
− | *Note 5: When the beam is being delivered to the Faraday Cup: | + | * Note 5: When the '''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 <font color=red>UNMASKED</font> | *# the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state <font color=red>UNMASKED</font> | ||
*# No changes to the FSD threshold should be made without RC or beamline expert approval | *# No changes to the FSD threshold should be made without RC or beamline expert approval | ||
− | *Note 6: Any request for a special run or change of configuration has to be approved by the RC & documented | + | *Note 6: Any request for a '''special run or change of configuration''' has to be approved by the RC & documented |
− | *Note 7: | + | *Note 7: |
+ | Turn DC HV off only for beam tuning; if no beam is available or when the beam is stable, keep them on even if you are not taking data. | ||
− | *Note 8: Reset CLAS12MON frequently to avoid histogram saturation. | + | *Note 8: '''Reset CLAS12MON''' frequently to avoid histogram saturation. |
− | *Note 9: | + | *Note 9: Do not run more than 30 minutes with >150 W beam to Faraday cup without the beam blocker. |
− | *Note 10: LTCC is NOT used in this experiment. HV should be kept OFF. | + | *Note 10: '''LTCC is NOT used''' in this experiment. HV should be kept OFF. |
− | *Note 11: If responding to RICH or Trigger alarms please post screens also to RICH or HBTRIGGER logbook, respectively. | + | *Note 11: If responding to '''RICH or Trigger alarms''' please post screens also to RICH or HBTRIGGER logbook, respectively. |
− | *Note 12: Do a RICH recovery (press the RICH Recovery button on the GUI) once daily during the day shift between runs. | + | *Note 12: Do a '''RICH recovery''' (press the RICH Recovery button on the GUI) once daily during the day shift between runs. |
− | *Note 13: Cycle the FMT Gas once per shift. If | + | *Note 13: '''Cycle the FMT Gas once per shift'''. If it is not reset, the interlock may drop and disable the HV. |
*Note 14: The error messages " ERR: Event ..." for crates tdcband1, tdcecal1 and tdcecal6 are NOT a problem | *Note 14: The error messages " ERR: Event ..." for crates tdcband1, tdcecal1 and tdcecal6 are NOT a problem | ||
− | |||
− | |||
− | |||
− | |||
<!-- | <!-- | ||
− | *Note | + | *Note : Shift workers must check the occupancies! Use this tool to compare to previous runs: [https://clas12mon.jlab.org/mon12/histograms/ https://clas12mon.jlab.org/mon12/histograms/] |
+ | --> | ||
+ | <!-- | ||
+ | * Note : 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. | ||
--> | --> | ||
+ | |||
| valign=top | | | valign=top | | ||
== <font color=blue> Known Issues </font> == | == <font color=blue> Known Issues </font> == | ||
+ | |||
+ | * ECAL HV SEC2_WI_E36 is known to be problematic. Channel stays off for now. | ||
* If any weird stripes appear in the DC occupancy plots, call Sergey. This is a known problem. | * If any weird stripes appear in the DC occupancy plots, call Sergey. This is a known problem. |
Revision as of 22:35, 26 January 2022
- Shift Documentation
- Phone Numbers
- Short Term Schedule
- Notes/Known Issues
- Shift Expert
- Remote Shifts
- Monitoring
- Useful Links
Shift ScheduleESAD, COO, RSADShift 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+[ten 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 the current page to force a refresh.
CLAS12 Run Group M, Fall 2021
Beam energies: 2.1, 4.0, 6.0 GeV (1.96 GeV/pass)
Important: Document all your work in the logbook!
RC: Susan Schadmand (phone below) and Sebastian Kuhn (kuhn@jlab.org, 757-639-6640)
- (757) 575-7540
- 9 575 7540 from Counting Room
- susansch@jlab.org
PDL: Valery Kubarovsky
- (757) 876-1789
- 9 876-1789 from Counting Room
- vpk@jlab.org
Run Plan: Jan 26 - Jan 30 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.
- Get Beam (pass2, 4 GeV beam)
- harp scans
- target centering
- if BEFORE 9pm:
- fill Ar target
- luminosity scan - increase downstream halo FSD threshold, if needed
- beam blocker calibration (during day)
- run for 2 days
- if AFTER 9pm:
- insert C target
- decide 80 or 90 nA
- beam blocker calibration
- run 12 hours
- switch to Ar (2 days)
- switch back to C
- Sunday switch to LH2
- take C data while purging ?
- 1 shift LH2
- beam blocker calibration
- 4 hours empty target
- Monday pass change (6GeV beam)
DAQ configuration PROD67_noVTPread , production trigger rgm_6GeV_inb_v1_0.trg . At the end of each run, follow the STANDARD DAQ RESTART SEQUENCE
References and Standards:(last update 01/18/2022- 23:30 Nominal Beam Positions
FSD Thresholds
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 (6 nA, production C) [4] Old reference Monitoring Histograms (50 nA, production LD2) [5] Counter rates
Beamline vacuum: should be not higher than 5e-5. |
Notes
The integrated rates on the upstream counters have to be in the range 0-15 Hz (rates up to 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 a bad beam tune or bleed-through from other Halls.
Turn DC HV off only for beam tuning; if no beam is available or when the beam is stable, keep them on even if you are not taking data.
|
Known Issues
|
Log screenshots of: (this is for the remote shifter, see dedicated Remote Shifts tab above.)
In case of other questions or uncertainties of what to do, call the RC or PDL |
Overview
Tasks
|
|
Webcams
|
Manuals |
Hall Webcams |
Epics on the web
|
Live Monitoring Links
|
|
Hall-B
Run lists |
AcceleratorReferences |
ZOOM meetings
|