Difference between revisions of "Run Group A"

From clas12-run
Jump to navigation Jump to search
Line 64: Line 64:
  
 
= Short Term Schedule =
 
= Short Term Schedule =
−
<!--#######################################  SHORT TERM  ################################################-->
 
 
<center><font color=blue size=4>
 
<center><font color=blue size=4>
 
''' CLAS12 Run Group A, Fall 2018 </font> '''<br>
 
''' CLAS12 Run Group A, Fall 2018 </font> '''<br>
 
''' Beam energy 10.6 GeV (5 pass) '''<br>
 
''' Beam energy 10.6 GeV (5 pass) '''<br>
 
''' Important: Document all your work in the logbook! '''<br>
 
''' Important: Document all your work in the logbook! '''<br>
−
''' Remember to fill in the [https://docs.google.com/spreadsheets/d/1j6UMJsId8VlsY00dg9Vqm0wmEJZLWVZlsBS-aL49xxw/edit?usp=sharing run list] at the beginning and end of each run (clas12run@gmail.com can fill the run list)'''<br>
+
''' Remember to fill in the [https://docs.google.com/spreadsheets/d/1j6UMJsId8VlsY00dg9Vqm0wmEJZLWVZlsBS-aL49xxw/edit?usp=sharing run list] at the beginning and end of each run <!--(clas12run@gmail.com can fill the run list)'''<br>-->
  
 
</center>
 
</center>
Line 86: Line 85:
  
 
* '''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.'''
 
* '''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 UPSTREAM counters has to be in the range 0-15 Hz (rates up 100 Hz are acceptable) and MIDSTREAM has to be in the rage 10-20 Hz (acceptable up to 50 Hz) @50 nA. Count rates in the range of hundreds or more may indicate 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 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 DAQ restart sequence '''
 
* ''' Note 2: At the end of each run, follow the DAQ restart sequence '''
Line 92: Line 91:
 
''' "end run", "cancel", "reset"''', then  
 
''' "end run", "cancel", "reset"''', then  
  
−
if run ended correctly ''' "download", "prestart", "iocjscalerRestartAll.sh", "go". '''
+
if the run ended correctly ''' "download", "prestart", "iocjscalerRestartAll.sh", "go". '''
  
−
if run did not ended correctly, or ROCs had to be rebooted '''"Configure", "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 DAQ prestart is complete reboot the scaler IOCs with the command:'''  iocjscalerRestartAll.sh. '''
  
−
Note: 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.
+
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 3: Nominal beam positions:''' ''' 2C24A (X=0.5,Y=0.5) ''', '''2H01 (X=1.0 mm, Y=-1.0 mm)''' see log entry https://logbooks.jlab.org/entry/3570290.
 
* '''Note 3: Nominal beam positions:''' ''' 2C24A (X=0.5,Y=0.5) ''', '''2H01 (X=1.0 mm, Y=-1.0 mm)''' see log entry https://logbooks.jlab.org/entry/3570290.
Line 104: Line 103:
 
* '''Note 4: Do not turn OFF FTOF HVs, even during the beam tune'''
 
* '''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 -
+
* '''Note 5: In case of the Torus and/or Solenoid Fast Dump do the following:
−
*# Notify MCC, request beam OFF and drop Hall 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
−
*# Make separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" filed add Ruben Fair, Probir Goshal, Dave Kashy and esr-users@jlab.org  
+
*# 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  
 
*# Notify Run Coordinator
 
*# Notify Run Coordinator
 
*# Call the MM expert to turn the detector off
 
*# Call the MM expert to turn the detector off
Line 113: Line 112:
 
*# Turn off all the other detectors'''
 
*# Turn off all the other detectors'''
  
−
*'''Note 6: When beam is being delivered to the Faraday Cup -'''
+
*'''Note 6: When beam is being delivered to the Faraday Cup:'''
−
*# the Fast Shut Down: Upstream, Midstream, Downstream, BOM and Solenoid should be always <font color=red> Unmasked</font>,
+
*# the Fast Shut Down elements: Upstream, Midstream, Downstream, BOM, and Solenoid should be always <font color=red>Unmasked</font>,
−
*# No changes to the FSD threshold without RC or beamline expert approval.
+
*# 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 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 RC & documented.'''
+
 
−
*'''Note 9: Check carefully BTA every hour and run script <font color=red> btaGet.py </font>. It will  print for you what HAS TO BE in BTA for this hour. Edit BTA if it is incorrect.'''
+
*'''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 <font color=red>btaGet.py</font> 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.'''
 
*'''Note 10: Reset CLAS12MON frequently to avoid histogram saturation.'''
  
Line 126: Line 128:
 
| valign=top width=50% |
 
| valign=top width=50% |
  
−
== <font color=blue>''' Run Plan: May3-May 6 '''</font>==
+
== <font color=blue>''' Start-up Run Plan:'''</font>==
−
 
 
−
 
 
−
May 4 (Day/Swing)
 
−
There are a series of special runs planned.
 
−
 
 
−
1. FT-only trigger runs: Genova group (Raffaella/Andrea) just finished this run
 
−
 
 
−
2. Random-trigger with existing PCAL/FTOF map: Started around 9am and should conclude around 2pm. If there is any issue, contact Andrea via bluejeans.com/1342978709
 
−
 
 
−
For 3--5, Sergey will take control of DAQ
 
−
 
 
−
3. DAQ studies(Sergey): Starting from 2:00pm. Sergey must be notified around 1:30pm if he is not already in the counting house. This is a series of short runs
 
−
 
 
−
4. DC/Varying readout window size/current scans: This will be a series of short runs (~30min each). For exact setting, please contact Volker (phone # on white board); Sergey will implement the changes.
 
  
−
5. Mode 7: Sergey will perform this run (~2 hrs). Dan should be contacted if needed via FTOF expert phone.
+
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 - <font color="red">This effort will be carried out under the direction of the beamline expert</font>
 +
* 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 out 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
 +
<font color="red">If target is functional</font>
 +
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)
 +
<font color="red">If target is not functional</font>
 +
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
  
−
May 4(Swing) --- May 6th (Owl)
+
* 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.  
−
 
 
−
When the above special runs are finished. Resume production runs at 50nA with trigger_v12_3.cnf
 
−
 
 
−
 
 
−
 
 
−
'''May 6 at 5 am''' MCC will terminate beam delivery.<br>
 
−
 
 
−
Start preparation for summer shutdown after that
 
−
* '''Turn HV OFF for:'''
 
−
** '''DC'''
 
−
** '''FTOF'''
 
−
** '''ECAL/PCAL'''
 
−
** '''LTCC'''
 
−
** '''HTCC'''
 
−
** '''FTT'''
 
−
** '''BMT/FMT'''
 
−
** '''CTOF'''
 
−
** '''CND'''
 
−
* '''Detectors remain ON for post calibrations:'''
 
−
** '''RICH'''
 
−
** '''SVT'''
 
−
** '''FTC/FTH'''
 
−
** '''Cryotarget stays FULL'''
 
−
* '''Turn OFF Solenoid and Torus''' (call PDL)
 
−
 
 
−
 
 
−
May 6 7am.
 
−
 
 
−
A small reception full of fancy food will be held in the counting house at 7am for the early birds. No reservation needed. Dress code: photo-friendly.
 
−
 
 
−
* 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 cand try to do the sequence of End->Cance->Reset, roc_reboot adcft1 (and adcft2, adcft3), make sure the roc 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 persist, please continue 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 50 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 in deed a need for tune beam, it should be sent to the tagger dump with the tagger magent on. If you are uncertain, please call RC/PDL.
 
  
 +
* 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.
  
 
* <font color=red>'''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 '''</font>
 
* <font color=red>'''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 '''</font>
  
−
Sometimes, a couple of RICH channel scalers would go to 0 and there is no alarm, even though the "# of fjibers 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, please refer to the instruction below.
+
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:
−
 
 
 
* <font color=red>'''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 '''</font>
 
* <font color=red>'''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 '''</font>
  
−
 
+
'''In case of other questions or uncertainties of what to do, call the RC'''
−
 
 
−
 
 
−
'''In case of other questions or uncertainties of what to do, please call the RC'''
 
−
 
 
−
 
 
−
 
 
−
<!-- === Updated March 6, 9:39 ===
 
−
*Due to the power failure, accelerator will be off for some extended time. All shifts are canceled for the 48 hours.
 
−
Next staffed shift will be Thursday, March 8'th expert day shift.
 
−
*Machine update https://logbooks.jlab.org/entry/3543255
 
−
-->
 
−
<!--
 
−
Due to the power failure, accelerator will be off for some extended time. All shifts are canceled for the 24 hours. Next staffed shift will be Tuesday, March 6'th expert swing shift.
 
−
Machine update https://logbooks.jlab.org/entry/3543255
 
−
 
 
−
*Take data with the 50 nA beam, trigger file trigger_v9.cnf, 100M  events per run.
 
−
*Monitor livetime closely.
 
−
 
 
−
* ''Sat Feb 23: Take data with 35 nA beam until Sergei creates the new trigger file''
 
−
* ''When Sergei comes he will test the new trigger file with 50 nA beam '', if it works, then the plan for the weekend is to take production data with 50 nA beam.
 
−
 
 
−
* ''' Before Accelerator gets beam off for beam studies we should take empty target run, It will be around Monday 7 AM. RC will notify later if the time for empty target runs is changed '''
 
−
 
 
−
* ''' Monday when MCC takes the beam off we might go to "Controlled access" during beam studies. Please ask MCC for controlled access with Radiation survay  '''
 
−
* ''' Monday when hall is sweeped, ask MCC to energize the tagger magnet, and then follow instructions in section 1 "Beam to tagger-yoke dump" from this link https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf  '''
 
−
 
 
−
* ''' When good beam is establisged on tagger magnet Yoke, we should do two Moller runs, 1st with half wave plate OUT, and 2nd with half wave plate "IN", please follow instructions in this link https://wiki.jlab.org/clas12-run/images/1/1d/Moller.pdf'''
 
−
 
 
−
* ''' When Moeller runs are finished, ask MCC to deGaus the tagger magnet, and follow instructions for sending the beam to Faraday Cup  https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf Section 2'''.
 
−
 
 
−
* ''' As soon a good beam is established (good harpscan, beam is centered in FTCalo), then turn on HV on detectors, and start taking data with trigger_v7 '''.
 
−
* ''' We want to check whether we can go to a higher current 55 nA, and check whether DAQ is stable and livetime is around 90%, if it works, then we should keep the 55 nA beam current, otherwise we should go back to 50 nA '''
 
−
-->
 
−
<!--
 
−
The beam position should be as indicated above. Make sure FSD thresholds are set correctly for whatever current is selected (refer to instructions in the "Establish-physics quality beam" procedure at [https://wiki.jlab.org/clas12-run/images/e/e3/Estab_beam.pdf]), integration time is set to 5 ms, and that the orbit locks are on. -->
 
−
 
 
−
 
 
−
<!--
 
−
<font color=blue>'''  February 20 swing, February 21 owl and day shifts Run Plan'''</font>
 
−
 
 
−
* Take data with a production trigger trigger_v4.trg untill 1 PM Wed. Feb. 21, and at 1PM call MCC and request "Restricted" access.
 
−
** HV on all detectors should be off, except SVT you can turn HV off, for SVT call Yuri and ask to turn SVT HV off
 
−
** Call PDL (Eugene) and ask to rump Solenoid and Torus down.
 
−
 
 
−
* When we back again to beam permit, we should directly go into FCup
 
−
** Eugune will rump up Solenoid and Torus magnets
 
−
** Make sure Solenoid FSD is unmasked "There should not be any Yellow or Red lights under the Solenoid FSD"
 
−
** Make sure HV on all detectors are off except FT CALO.
 
−
** Tagger magnet is "OFF"
 
−
** Collimator is at '20 mm' position
 
−
** Request for 2 nA beam
 
−
 
 
−
** Make sure Solenoid FSD is unmasked "There should not be any Yellow or Red lights under the Solenoid FSD"
 
−
** Make sure HV on all detectors are off except FT CALO.
 
−
** Tagger magnet is "OFF"
 
−
** Collimator is at '20 mm' position
 
−
** Request for 5 nA beam
 
−
 
 
−
** Look carefully int Halo counters, all halo counters upstream of the target are counting less than 10 Hz
 
−
** Look into FT Calo scaler screen, which is the main measure how the beam is centered, for reference look https://logbooks.jlab.org/entry/3535015 this, and make sure X and Y asymmetry is close to 0 (less than +/-6% with 2 nA beam, and less than 3% when you go to production current).
 
−
** If the beam is centered enough and halo rates on midstream and upstream halo counters don't exceed few Hz, request for 20 nA beam, and ask out orbit lock to be engaged. Check again beam is centered, and halo counters still coun order of few Hz.
 
−
** Check also beam position on 2H01, should be around '''2H01 (X=1.0 mm, Y=-1.5 mm)'''
 
−
 
 
−
* Next step is to do harp scans with all three harps, 2c21 harp, tagger harp and 2H01 harp
 
−
** Before 2C21 and tagger harps scans put Upstream and midstream FSD thresholds to 100000, and the integration time 50ms.
 
−
** You should not see any signifcant halo, the bgr/Peak ratio should be below 5e-3
 
−
** As soon you are done with 2c21 and tagger harp scans, put back FSD hresholds for upstream and midstream counters to 1000, and integration time to 5 ms.
 
−
 
 
−
** For 2H01 harp scan, ask BOM limit to be 1000000 and itegration time 50 ms. then do 2H01 harp scan. Compare harp scan result to the most recent one https://logbooks.jlab.org/entry/3534806, make sure beam sigmas are close to the one in the link.
 
−
 
 
−
* Next step is to tur HV on for detectors, for '''SVT''' only call Yuri and ask him to turn SVT HV on.
 
−
* Sergei has added a new component PCal Ustrips (PCU) in the trigger, it's timing should be checked, call sergei and ask him to take over the DAQ to adjust the relative timing of PCU. This should approximetely take about 1 hour.
 
−
* As soon Sergei has finished timing adjustment, ask for 35 nA beam, and take production data with trigger_v5.trg
 
−
-->
 
−
<!-- * If the machine is down and it is back start with low current first  (2nA and 5 nA)  making sure that the beam is stable in current and position before moving to 30 nA
 
−
-->
 
−
 
 
−
 
 
−
 
 
  
 
<!--
 
<!--

Revision as of 10:46, 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 (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 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 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 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 be always 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:

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 out 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=1470"