Run Group C

From clas12-run
Jump to navigation Jump to search
[edit]

NOTE: All NON-JLab numbers MUST be dialed with (757) area code. When calling from a CH landline, dial "9" first. To call from outside, all 4-digit numbers must be preceded by 757-269

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 (757) 344-7204 (cell) Daniel Carman
CND (757) 329-4844 (cell) Pierre Chatagnon
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)		 Valery Kubarovsky (primary)
Nathan Baltzell (secondary)
DAQ (757) 232-6221 (cell) Sergey Boiarinov
Cryotarget (757) 218-2266 (cell)
(757) 871-5374 (cell)
(757) 897-1415 (cell)
(757) 746-9277 (cell)		 Xiangdong Wei (first)
James Brock (second)
James Maxwell (third)
Chris Keith (fourth)
RG-E Solid Target (757) 344-1848 (cell) Antonio Radic
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.

Click Here to edit Phone Numbers. Note, you then also have to edit the current page to force a refresh.



CLAS12 Run Group C

Run Coordinator: Bryan McKinnon (9-)757 575-7540

PDL: Eugene Pasyuk (9-)757 876-1789 , x6020 office

Run Group Coordinator: Sebastian Kuhn (9-)757 639-6640

Daily RC Meetings at 14:00: CH Room 200C, and on Zoom Zoom information: Link, Meeting ID: 160 867 4253, Passcode: 786506

Run Coordinator and Target Expert Schedule

Longterm Run Plan

Medium-Term Run plan (FTout portion)

IMPORTANT SHIFT 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 so that replacements can be arranged.

* 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!
* Please refer to the information here and the Expert/Worker Shift instructions for each and every shift!
* Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.

Short Term Schedule Wednesday, Nov. 2, 2022

STATUS:

  • Current: 8 nA
  • Run duration: 100M events or 4 hours, whichever comes first
  • Note, BOM is not installed for this experiment, so it does not matter whether it appears masked in FSD or not.
  • New conditions for raster operation:
    • IF there is any ammonia sample (NH3 and ND3) in the target, the raster MUST be operating at all times. The Raster FSD must be UNMASKED. Orbit locks MUST be OFF (except for brief moments to restore beam position).
    • For beam tuning or other non-rastered beam, the Raster FSD must be MASKED.
    • If MCC needs to diagnose beam with a harp, we can offer them tagger 2C24 and follow the procedures required for that. 2H01 harp scan should not be done when we have the raster.
    • Changing raster offset: ask MCC to NOT correct whatever happens on 2H01. Note new 2H01 values and inform MCC of the new 2H01 x and y values - then they can keep the beam at those positions.
  • Experiment setup is "FTout/ELMO"

PLAN:

  • If HWP is changed by Hall A (they will notify us), start a new run
  • All shift takers: if MCC requests that you perform a beam tuning procedure that you are unsure of, please contact beamline and RC. All beam tune is best done under the watchful eye of the beamline expert, no matter the time of day/night.
  • Thursday: Production data taking NH3-
    • No other special plans
  • Friday: Production data taking NH3-
    • Change HWP to Out (mid day shift)
    • No other special plans


GENERAL INFORMATION

  • BMT:
    • After HV trip: the channel HV should be turned back on as soon as you notice the trip, power cycle by turning HV OFF and ON without waiting for any amount of time.
    • HV frequently tripping: Call expert. Do not change HVs without approval from the expert.
  • Controlled access: after you call MCC, they will drop the hall to controlled access once someone goes down and calls them for entry. Then call when they should go back to beam permit and call again to say you want the beam back and what beam current. Rapid access is controlled access without RadCon.
  • mon12: It can happen that histograms do not get cleared completely at run start. This is seen eg as an excess of small multiplicities. The remedy is to quit mon12 and open it again. Other than that, small multiplicities come from time intervals with beam down. You might want to look at the multiplicities before uploading the mon12 histograms in the logbook.
  • DAQ:
    • clondaq6/data is full, switched to clondaq7, rastermon should be using ET on clondaq7
    • It should no longer be necessary to quit RasterMon at the end of each run and restart after a successful "Go" for the next run. However, if DAQ crashes, you SHOULD follow these steps, and the same for mon12.
  • Magnet trip: call "Engineering on call", if due to cryo, also inform the target expert about the cryogenic issues.
  • CND CAMAC crate was off? Need to run the script to set the thresholds for CND CFDs.
  • Hall lights: Before leaving the hall and going to beam permit check that dome lights, forward carriage lights, and pie tower lights are OFF.
  • Moller runs: should be taken with 8-10 nA.
  • Beam viewer: Please REMOVE the beam viewer unless we are actively tuning the beam or calibrating beam position/raster, to avoid damage to electronics, cameras etc.
  • Change of running conditions
    • Check that the trigger alarms (on rate/nA) are set appropriately and RC changes them as needed.
    • Whenever the target type or polarization direction changes, or the half-wave plate status changes, make sure to enter a comment in the BEGIN RUN / END RUN comment box.
    • Do not change running conditions while a run is ongoing. This includes changing target polarization or HWP, etc.

DAQ configuration

  • Configuration is currently PROD67/PROD67_PIN (PROD66/PROD66_PIN), trigger file rgc_300MeV_v2.3_Q2_1.5GeV2.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 and reset 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 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 and rastermon
      • "cancel", "reset"
      • "configure", "download", "prestart", "go"
      • restart mon12 and rastermon
  • 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

5-pass (10.55 GeV) Running conditions

  • Torus at 100% current, inbending electrons. Setpoint = +3770 A (Readback = +3766 A)
  • Solenoid setpoint inverted (Oct 14 2022) -2417.5 A
    • with shim coils of (negatively) polarized target on (Oct 26, 2022) -2418.50 A
  • Solenoid setpoint +2417.5 A (normal conditions RGA-M)

Solenoid set-point of 2417.5 A results in read back 2419.57 A and exactly 5.00 T field on center

Raster settings

  • x: Vpp = 3.6 V, offset = -0.6 V
  • y: Vpp = 3.1 V, offset = -0.15 V
  • Fundamental Period = 2 s
  • The correct raster calibration constants should be automatically loaded by rastermon - if not, enter them through "Config" by hand:
  • f(x) = 0.0104*x + -25.5
  • f(y) = -0.0115*y + 24.4

Nominal Beam Positions

  • 2C21A, X = -0.4 mm, Y = +0.6 mm
  • 2C24A, X = -2.0 mm, Y = +0.6 mm
  • 2H01, X = -1.6 mm, Y = +0.9 mm
  • Orbit lock on 2C24 and 2H01 ONLY if raster is OFF, otherwise orbit lock on 2C21 and 2C24 (note: this appears as "stopped" on the beam line GUI).

FSD Thresholds

  • Upstream: 2000 Hz
  • Midstream: 2000 Hz
  • Downstream: 100000 Hz (1e5)
  • BOM: 1000000 Hz (BOM not installed for RG-C)
  • 5 ms dwell time

Reference plots and histograms

Counter rates

  • With 6 nA beam, the upstream counters should read zero.
  • The Midstream ones should read 0-20 Hz or so.
  • Greatly increased rates may indicate bad beam tune or bleed-through from other Halls.

Shift expert 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
    • includes Run Plan, General Information, DAQ Configuration, and References and Standards
  • Keep shift summary up to date in HBLOG. Record all that happens.
  • Polarized target:
    • Helicity-Latched Trigger GUI and the Helicity Trigger Asymmetry strip-chart (not accessible remotely) (example https://logbooks.jlab.org/entry/4041939). (ONLY WHILE ACTUALLY RUNNING ON NH3 AND ND3 targets!)
    • In case of any issues, contact the polarized target expert on call.
    • Ice on the run valve
    • NMR running (ONLY WHILE ACTUALLY RUNNING ON NH3 AND ND3 targets!)
      • The JLab Polarization Display is seen via a VNC window in the counting room. Here, the NMR Controls' blue bar must be moving, indicating that the NMR is running and the polarization is measured.
      • The NMR frequency needs to be controlled by hand. If you see target polarization (on the red graph) starting to drop, call the expert. They will guide you through the adjustment procedure. This will be in the electronics room by the door to the counting room, in the third crate from the right ("CR-6"). White box which says "EIO Tube" and has a red button at the top right, which says "Move", next to a display for "Position". This will be the one to press, under guidance of the target expert.
    • Alarms from System RG-C Polarized Target (alarm handler).
  • Do a RICH recovery (press the RICH Recovery button on the GUI) once daily during 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 automatically fill the left side then correct as needed.
    • Accelerator beam time:
      • ABU: acceptable beam used (eg 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 (eg radiator change or our problems)
      • BNA: beam not acceptable (eg tuning, drifting, not focused)
    • Experiment beam time
      • ER: experiment ready
      • PCC: planned configuration change (when 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 tab "Shift Information"
    • Promptly send "Info for MCC" at 7:00, 15:00, and 23:00
    • Sign, viz log completed 8 hour sheet


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

(remote) shift worker: see dedicated Worker Shift tab above.

Notes

  • Check the information in the Short Term Schedule, for every shift
  • Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.
  • Use the new HBRUN logbook for automated and run-specific entries and screenshots, see https://logbooks.jlab.org/entry/4048698

Shift Worker Tasks

Make the following log entries ONCE per run

  • Screenshots: submit to logbook only if you capture the information with beam ON
    • Beamline Overview, in VNC or Web Browser
    • CLAS12 Trigger rates and DAQ status
    • RGC Polarized Target GUI - under Beamline on CS-Studio
  • Upload monitoring plots to logbook
    • Standard spectra (mon12): inspect all monitoring histograms ' and carefully compare them to the corresponding reference histograms: reference, current, and 5 most recent runs, see link under tab Useful Links
      • You can choose a different reference run if you are confident what you are doing, the reference numbers refer to logbook entries.
    • Raster Monitoring (use "Log Entry" button on RasterMon screen at bottom-right corner).
      • An example of a "decent looking" RasterMon is here: [7]. The x and y distributions should show a smooth dome, without any horns or spikes on it and without the distributions being cut off at the edges.

Once per shift:

  • Fill the shift checklist
  • Log screen shots of RICH temperature and scaler maps. Log in RICH logbook.

Regularly:

  • reset & check spectra frequently (every 30 - 60 minutes)
    • Some plots in the online mon12 have a choice of histogram sets per sector, select buttons at the bottom of the plot. That means you have to look at all sectors for these histograms.
    • The logbook entry shows all histograms.
  • Check the life cam of the polarized target run valve for plumes or ice buildup (hallbcam04)
    • Make sure you refresh the web page! Its no longer necessary to put a snapshot into the logbook UNLESS something looks suspicious. In THAT case, immediately inform the target expert(s).
  • Log the strip charts in time intervals according to the x-axis time span, via right-click on the screen and selecting "Make Elog Entry". Make sure NOT to submit to ELOG.
    • Beam current and position strip-charts (CS-Studio -> Beamline -> Strip Charts)
    • Helicity Trigger Asymmetry strip-chart (CS-Studio -> Helicity-Latched Trigger GUI Screen -> Menu -> myaPlot) (not accessible remotely) (ONLY WHILE ACTUALLY RUNNING ON NH3 AND ND3 targets!
    • For the y axis in the bottom panel, choose the target polarization and a reasonable range for the y axis
      • Set the time axis auto-update. A ">>" symbol will appear below the time axis when this is activated.
        • Right-click on X axis -> Set Auto Time Stepping

For REMOTE Shifts (offsite):

ATTENTION: If you plan to take (a) remote shift(s), you MUST test your setup (including VNC connection) at least 24 hours before your first shift!


Clas12design.png

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