Difference between revisions of "Run Group A"

From clas12-run
Jump to navigation Jump to search
Line 123: Line 123:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
−
== <font color=blue>''' Start-up Run Plan:'''</font>==
+
== <font color=blue>''' Start-up Run Plan:'''</font>== (Updated: Aug. 18, 2018 at 10:53 a.m.)
  
 
1) Before the start of beam delivery: Ramp torus field to -100% (negatives inbending) and ramp solenoid field to -100%
 
1) Before the start of beam delivery: Ramp torus field to -100% (negatives inbending) and ramp solenoid field to -100%

Revision as of 09:53, 18 August 2018

[edit]

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+[10 digit number]

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.

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


CLAS12 Run Group A, Fall 2018
Beam energy 10.6 GeV (5 pass)
Important: Document all your work in the logbook!
Remember to fill in the run list at the beginning and end of each run

RC: Daniel S. Carman

PDL: Eugene Pasyuk


  • Note 1: 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 100 Hz are acceptable) and the midstream have to be in the rage 10-20 Hz (acceptable up to 50 Hz) @50 nA. Counting rates in the range of hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.

  • Note 2: At the end of each run, follow the standardDAQ 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 DAQ prestart is complete reboot the scaler IOCs with the command: iocjscalerRestartAll.sh.

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.

  • Note 4: Do not turn OFF FTOF HVs, even during the beam tune
  • Note 5: In case of the Torus and/or Solenoid Fast Dump do the following:
    1. Notify MCC to request beam OFF and to drop Hall B status to Power Permit
    2. Call Engineering on-call
    3. Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org
    4. Notify Run Coordinator
    5. Call the MM expert to turn the detector off
    6. Call SVT expert to turn SVT off
    7. Turn off all the other detectors
  • Note 6: When beam is being delivered to the Faraday Cup:
    1. the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should always be in the state UNMASKED,
    2. No changes to the FSD threshold should be made without RC or beamline expert approval.
  • Note 7: Do not turn on or off SVT - only SVT expert can do that
  • Note 8: Any request for a special run or change of configuration has to be approved by the RC & documented
  • Note 9: Carefully check the BTA every hour and run the script btaGet.py to print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.
  • Note 10: Reset CLAS12MON frequently to avoid histogram saturation.

== Start-up Run Plan:== (Updated: Aug. 18, 2018 at 10:53 a.m.)

1) Before the start of beam delivery: Ramp torus field to -100% (negatives inbending) and ramp solenoid field to -100%

2) Complete beam tuning studies - This effort will be carried out under the direction of the beamline expert

  • Complete beam tuning to the tagger yoke beam dump following the procedures in the beam tuning document
  • Take a Moller run (work with MCC to maximize electron beam polarization (should be >86%)
  • Complete beam tuning to Faraday Cup with empty target following procedures in the beam tuning document
  • Perform beam centering using BOM and FT-Cal along with beamline halo monitors
  • Make sure harp scans results for 2C21, 2C24, and 2H01 are posted in the logbook (these will represent our baseline results for the fall 2018 run)
  • Record nominal beam positions at BPMs in the logbook (these will represent our nominal values for the fall 2018 run)

3) With empty target:

  • Turn on CLAS12 detectors from least sensitive to most sensitive (call SVT, MM, and DC experts to turn their systems on)
  • Check DAQ and trigger functionality and rates
  • Perform current scan - check rates vs. beam current to 100 nA (use 5 nA, 20 nA, 50 nA, 75 nA, 100 nA) - record scalers in logbook and record currents on CTOF, FTOF, and PCAL ammeters (see links on monitoring tab to access cameras)
  • Take empty target run (2 hrs at 100 nA)
  • At end of run, have MCC turn the beam off

If target is functional:

4a) Fill the target (call Engineering for this step)

5a) Perform current scan - - check rates vs. beam current to 75 nA (use 2 nA, 10 nA, 30 nA, 50 nA, 75 nA) - record scalers in logbook and record currents on CTOF, FTOF, and PCAL ammeters (see links on monitoring tab to access cameras)

  • DC experts should use this period to finalize the HV and discriminator thresholds
  • CVT experts should use this period to study currents and stability

6a) Check DAQ and trigger functionality

7a) Optimize the FT settings (FT group will take over DAQ control remotely and complete task). This should be done (preferably) during the owl shift.

8a) Complete a luminosity scan and record data in the following sequence with the standard RG-A trigger:

  • 2 nA - 2 hrs
  • 10 nA - 1 hr
  • 30 nA - 30 min
  • 50 nA - 30 min
  • 75 nA - 30 min

9a) Take data with the standard RG-A trigger at 20 nA for 4 hrs to collect data for baseline subsystem calibrations

10a) Take production data with the standard RG-A trigger at 40 nA (3 hr runs)

If target is not functional:

4b) Ramp torus to 0% field (call Engineering for this step)

5b) Take data at 2 nA for DC alignment studies for 1 hr

6b) Have MCC turn the beam off

7b) Ramp solenoid to 0% field (call Engineering for this step)

8b) Take data at 2 nA with both magnets for DC and CVT alignment studies off for 8 hrs

  • From time to time, we might experience trigger bit issues (FT bits: 24, 25, and 26 and 27). Bit 26 might not trigger the alarm but when this issue happens it will count abnormally high pre-prescale. For the time being, shift leaders can try to do the sequence of End->Cancel->Reset, roc_reboot adcft1 (and adcft2, adcft3), make sure the ROCs are connected, then Download->Prestart->Go. If this does not work, repeat the sequence and add "Configure" in front of "Download". If the trig issue persists, please continue to take production data without fixing it -- please make sure you log this infor in the RCDB "Comment" field.
  • If the machine is down for few hours ask for low current first 5 nA make sure that the beam is stable both in position and current, check that the rates are OK on all the detectors and halo counters. Then ask for 40 nA and continue data for production. If there are issues with the beam call the RC. Sometimes MCC operator might ask to deliver tune beam --- please do not accept it. We need CW beam sent to the Faraday cup. If there is indeed a need for tuned beam, it should be sent to the tagger dump with the tagger magnet on. If you are uncertain, please call RC/PDL.
  • Please contact the Micromegas (BMT, FMT & FTT) expert if there are trips, or if you notice any issues in the online monitoring. Do not turn OFF or ON the MM only the expert can do that. See Log entry https://logbooks.jlab.org/entry/3556528

Sometimes, a couple of RICH channel scalers would go to 0 and there is no alarm, even though the "# of fibers connected" would be shown to be the correct 138. Shift takers therefore should periodically, especially at the end of run, check the RICH scalers GUI. If there is an issue:

  • For RICH recovery procedures, please see Log entry https://logbooks.jlab.org/entry/3562273. This would apply in the cases of 1. DAQ crash: rich4 is not responding or 2. RICH alarms (LV,missing tile, temperature etc). If it does not work or you are uncertain about what to do, please contact the RICH expert on call

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

General Instructions:

  • For a given beam current, compute the FSD thresholds according to the Establish Physics Quality Beam document. Call MCC to update the values. Contact the beamline expert if there are questions about setting the FSD thresholds.
  • 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 cooldown.
  • Do not run more than 60 minutes above 30 nA with 5-pass beam without the beam blocker in front of 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 beam is stable, keep them on even if you are not taking data.
  • In case of loss of communication with IOCBTARG, follow instructions at https://logbooks.jlab.org/entry/3502218
  • With any issue contact On-Call Experts or RC - do not spend more than 15-20 min trying to fix the problem.
  • All jscaler iocs (iocjscalerX) on the health screen (under DAQ tab) must be restarted after every DAQ prestart is completed. Follow this link for detailed instructions https://userweb.jlab.org/~baltzell/CLAS12/SC/jlabScalersOps.txt
  • Check that no unecessary beamline-related screens are open. This includes particularly the big beamline overview screen, but also and any motor/harp/collimator screens, and ioc health screens.

Every Shift:

  • Follow run plan as outlined by RC
  • If 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.
  • Check on white board all scalers, strip charts and monitoring plots that need to be logged regularly
  • 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.
  • Fill and submit the shift checklist in the logbook

Every Run:

Log screenshots of:

  • main scaler GUI display
  • Detector occupancy plots
  • Trigger rate gui
  • Beam strip charts
  • FTCalo FADC scalers


Clas12design.png

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