Run Group D

From clas12-run
Revision as of 23:04, 6 September 2023 by Elfassi (talk | contribs)
Jump to navigation Jump to search
[edit]
Role Phone Number
Hall B Run Coordinator (757) 575-7540 (cell)
Hall B Physics Division Liaison (757) 876-1789 (cell)
MCC 7048
Crew Chief 7045
Crew Chief (757) 876-3367 (cell)
Program Deputy (757) 876-7997 (cell)
RadCon (757) 876-1743 (cell)
Gate House Guard 5822
Location Phone Number
Hall B Floor 5165
Hall B Space Frame 5170 and 5171
Hall B Forward Carriage 5371
Hall B Gas Shed 7115
Hall B Counting House 5244 (Shift Expert)
Hall B Counting House (757) 329-4846 (Shift Expert cell)
Hall B Counting House 5245 or 5126 (Shift Worker)
Hall A Counting House 5501
Hall C Counting House 6000
Hall D Counting House 5504
Hall B System Phone Number On-Call Person
Engineering (757) 748-5048 (cell)
(757) 897-9060 (cell)		 Engineering On-Call (primary)
Denny Insley (secondary)
Slow Controls (757) 748-6922 (cell) Nathan Baltzell
Beamline (757) 303-3996 (cell) Eugene Pasyuk
DC (757) 218-4372 (cell)
(757) 748-5048 (cell)		 Florian Hauenstein (primary)
Engineering On-Call (secondary)
SVT/MVT/MM (757) 541-7539 (cell)
(757) 753-7769 (cell)		 Yuri Gotra (primary)
Rafo Paremuzyan (secondary)
ECAL (757) 810-1489 (cell) Cole Smith
FTOF/CTOF/CND (757) 344-7204 (cell) Daniel Carman
ALERT (757) 329-4844 (cell) Raphael Dupré
HTCC/LTCC (757) 344-7174 (cell) Youri Sharabian
FT (757) 344-1848 (cell) Raffaella De Vita
BAND (757) 310-7198 (cell) Florian Hauenstein
RICH (757) 344-3235 (cell)
(757) 748-6922 (cell)		 Christopher Dilks (primary)
Nathan Baltzell (secondary)
DAQ (757) 232-6221 (cell) Sergey Boiarinov
HYDRA (317) 550-9226 (cell) Torri Jeske
Authorized Hall B Solenoid/Torus Operators
Hall B Denny Insley, Morgan Cook, Eugene Pasyuk
Magnet Group Probir Ghosha, Renuka Rajput-Ghoshal
Detector Support Group Brian Eng, Pablo Campero, Tyler Lemon
DC Power Onish Kumar, Sarin Philip
  • 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.

Run Coordinator: Lamiaa El Fassi (757) 575-7540

PDL: Nathan Baltzell (9-)757 876-1789 , x5902 office

Daily RC Meetings at 15:30: CH Room 200C, and on Zoom: Link, Meeting ID: 1611984219, Passcode: RGD-RC23

Important Notes

  • In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House
* If you have symptoms or a positive COVID test, do NOT come to your shift - instead, inform the PDL and the RC and JLab medical services immediately to arrange replacements.
* Remote shift: If needed, worker shifts can be taken from off-site. Inform the PDL and RC. Also, make sure that you follow the instructions under the "Worker Shift" Tab - you need some lead time to set up!

Note to shift takers, please:
* Read the logbook, be aware of previous 24 hours
* Arrive at least 10 minutes early for shift change
* Refresh the run wiki pages; look over them every shift
** Follow the expert/worker shift instructions 
* Communicate with your co-shift person
** The shift expert should know about and refer to logbook entries in their shift summary
** The shift worker should discuss an issue with the shift expert before making extra logbook entries

LE: Please don't change: Work in progress

Short-Term Schedule for the Week from Burgsday, July 17, 2023 -

  • In-bending torus field, 5-pass beam on ND3.
  • Beam Current: 666 nA
  • Run duration: 100M events or 4 hours, whichever comes first.
  • CODA Configuration: PROD66
  • Trigger file: rgd_300MeV_v1.0.trg
  • If HWP is changed, start a new run

DAQ configuration

  • Configuration is currently PROD66/PROD66_PIN, trigger file rgc_300MeV_v1.4_no_DC.trg
  • NOTE: UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to make a RICH recovery - instead, do this in between runs.
  • NOTE: BOTH the shift expert AND the shift worker MUST check and reset monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems. Sometimes it is the only way to know that a roc needs to be rebooted. Watch the raster pattern!
  • At the end of each run, follow the STANDARD DAQ RESTART SEQUENCE:
    • "end run."
    • If the run ended correctly and you will run with the same configuration and trigger file, then: "prestart", "go"
    • If you are changing configuration (between PROD6X and PROD6X_PIN) or trigger file: "Cancel", "reset", "configure", "download", "prestart", "go".
    • If the run did not end correctly or if any ROCs had to be rebooted:
      • Quit ALL running instances of mon12
      • "Cancel", "reset"
      • "configure", "download", "prestart", "go"
      • restart mon12
  • After each step, make sure it is completed in the Run Control message window. If an 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.

Reference Values

FSD Thresholds from RG-C

  • Upstream: 5 Hz
  • Midstream: 2 kHz
  • Downstream: 10 kHz
  • BOM: 1 MHz
  • 5 ms dwell time

Harp Scan References from RG-C

General Instructions:

  • 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 an access, they should be switched off when leaving the Hall. Note that the dome lights, when switched off, cannot be turned back on immediately because they require 10-15 min to cool down.
  • Do not run more than 30 minutes above 30 nA with a 5-pass beam without the beam blocker in front of the Faraday cup . Put beam blocker in for long-running at high currents for 5-pass operations.
  • 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.
  • With any issue, contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem. If the phone is not answered, try the "Page Experts" button on top of CLASCSS.
  • Check for and read any comments to log-book entries made during your shift!

Every Shift:

  • Follow the run plan as outlined by RC
  • If there is any concern about beam stability, ask MCC if orbit locks are on (they should be).
  • Keep shift summary up to date in HBLOG. Record all that happens.
  • Document any beam condition change and send scaler GUIs to HBLOG
  • Fill out BTA hourly. Click "Load from EPICS" to automatically fill the left side. Run the script btaGet.py to print you the correct BTA info for this hour -- edit the values on the BTA page if they are wrong!
  • Upload spectra from clas12mon at the beginning and end of the shift and cross-check with reference spectra (make sure you select the SAME SECTOR for the reference plots on tabs with multiple sectors).
    • Reset clas12mon every ~2 hours and inspect spectra (some detectors have buttons at the bottom to toggle between the sectors -- please check all of them).
  • Fill and submit the shift checklist in the logbook

Every Run:

  • Check values at the start of every run and log screenshots of:
    • Main scaler GUI display
    • Trigger rate GUI
    • Beam strip charts
    • FTC scalers
  • At the start and end of every run, check that the data filled in the database run list is correct (especially fields that are filled in manually, like beam current and comments). This replaces the previously used spreadsheet.

To access the Hall:

  • If you need to go down into Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).
  • Check in with the shift personnel before entering the hall.


Tasks

  • Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.
  • Follow the Short Term Schedule as outlined by RC
    • Run Plan, DAQ Configuration, and References and Standards
  • Keep shift summary up to date in HBLOG. Record all that happens.
  • Do a RICH recovery (press the RICH Recovery button on the GUI) once daily during the day shift, between runs. Please log in shift summary.
    • Note the automated "RICH Recovery" sequence already confirms RICH4 is up and accepting SSH connections before claiming success.
    • You have to "Cancel->Reset->Configure->Download->Prestart" before starting the next run.
  • Fill out BTA hourly. Click "Load from EPICS" to fill the left side automatically, then correct as needed.
    • Accelerator beam time:
      • ABU: acceptable beam used (e.g. harp scans, calibrations, trigger settings, running)
        • The info from EPICS is not always correct; e.g. when taking data with low beam current, you should change the ABU to the proper (estimated) time by hand instead of simply accepting "0" if you are actually taking data.
      • BANU: beam acceptable but not used (e.g. target change or our problems)
      • BNA: beam not acceptable (e.g. tuning, drifting, not focused)
    • Experiment beam time
      • ER: experiment ready
      • PCC: planned configuration change (when the beam is masked while radiators are moved, DAQ (stopping/starting runs, tests, ...) are PCC.
      • UED: unplanned experiment down, is used for hardware failure
    • Enter fields at the tab "Shift Information"
    • Promptly send "Info for MCC" at 7:00, 15:00, and 23:00
    • Sign, viz log completed 8-hour sheet
  • If the worker shift is remote, maintain communications with them in Zoom: https://jlab-org.zoomgov.com/j/1619881100

In case of other questions or uncertainties of what to do, call the RC or PDL

Tasks

  • Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.

Hourly

  • Reset and check mon12 histograms
    • Note, some plots have radio buttons at the bottom to choose the sector, in which case you should cycle through and check all sectors.

Once per run

Once per shift

For Remote Shifts

You must test your setup, including Zoom and VNC connections, at least 24 hours before your first shift!

  • Zoom for 24-7 communication with counting house: https://jlab-org.zoomgov.com/j/1618614939
    • The passcode is required and contained in this log entry
    • Remind the expert in the counting house to restart their zoom, if necessary
  • Remote VNC connection instructions: https://logbooks.jlab.org/entry/3906039
    • All necessary applications should be avaible from the desktop menu (left/right click on the desktop)
    • EPICS GUIs should be accessed ONLY via the desktop menu or by running clascss-remote.

Webcams

EPICS

Data Quality



Clas12design.png

Retrieved from "https://wiki.jlab.org/clas12-run/index.php?title=Run_Group_D&oldid=5783"