Difference between revisions of "Run Group C"

From clas12-run
Jump to navigation Jump to search
 
(421 intermediate revisions by 17 users not shown)
Line 12: Line 12:
 
===[https://bta Beam Time Accounting]===
 
===[https://bta Beam Time Accounting]===
 
* See guidance at '''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf BTA User Guide]'''.
 
* See guidance at '''[https://accwiki.acc.jlab.org/pub/SWDocs/BeamTimeAccounting/Machine_Time_Accounting_User_Guide.pdf BTA User Guide]'''.
 +
===[https://www.jlab.org/Hall-B/run-web/rgc/ESAD_HallB-CLAS12_rgC.pdf ESAD], [https://www.jlab.org/Hall-B/run-web/rgc/COO_HallB-CLAS12_RGC.pdf COO], [https://www.jlab.org/Hall-B/run-web/rgc/RSAD_HallB-CLAS12_rgC.pdf RSAD], [https://www.jlab.org/div_dept/train/SAF111/Hall%20B%20worker%20Safety%20Training%20%28SAF111%29%20%2008%2001-12-1.pdf ERG] ===
 +
===[https://clasweb.jlab.org/wiki/images/e/ef/Longitudiannly_polarized_target_OSP.pdf Longitudinally Polarized Target OSP]===
 +
===[https://www.jlab.org/Hall-B/run-web/rgc/RICH_OSP_131114.pdf RICH OSP]===
 
   
 
   
 
| valign=top |
 
| valign=top |
Line 66: Line 69:
  
 
<!--- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE -->
 
<!--- JUST MODIFY AND SAVE ANYTHING IN THIS COMMENT BLOCK TO FORCE A REFRESH OF THE PHONE NUMBERS TEMPLATE -->
 
  
 +
= Short Term Schedule =
 
<!--#######################################  Short Term Schedule  #############################################-->
 
<!--#######################################  Short Term Schedule  #############################################-->
  
= General and Short Term Plan =
+
<!-- === <font color=red size=6> '''ALL shifts are presently canceled until Monday, January 30, 8 AM. </font> ''' === -->
  
=== <font color=blue size=4> ''' CLAS12 Run Group C, Summer 2022 </font> ''' ===
 
=== [https://clasweb.jlab.org/wiki/index.php/RGC_RC Daily RC Meetings] at 14:00: CH Room 200C, and on Zoom ===
 
Zoom information: [https://jlab-org.zoomgov.com/j/1608674253?pwd=SFZyYmZLWXJieGtpV2dEdVRiUEJnUT09&from=addon Link], Meeting ID: 160 867 4253, Passcode: 786506
 
  
=== Run Coordinator: Zulkaida Akbar ===
+
=== <font color=blue size=4> ''' CLAS12 Run Group C </font> ''' ===
*  (9-)757 575-7540
 
  
=== PDL: Eugene Pasyuk ===
+
'''Run Coordinator: Mohammad Hattawy''' (9-)757 575-7540
* (9-)757 876-1789 , x6020 office
 
  
=== Run Group Coordinator: Sebastian Kuhn ===
+
''' PDL: Eugene Pasyuk '''  (9-)757 876-1789 , x6020 office
* (9-)757 639-6640
 
  
=== [https://userweb.jlab.org/~kuhn/RGC/RCschedule.pdf Run Coordinator and Target Expert Schedule] ===
+
''' Run Group Coordinator: Sebastian Kuhn ''' (9-)757 639-6640
  
=== [https://userweb.jlab.org/~kuhn/RGC/RunPlan.pdf Longterm Run Plan] ===
+
''' [https://clasweb.jlab.org/wiki/index.php/RGC_RC Daily RC Meetings] at 14:00: CH Room 200C, and on Zoom '''
 +
Zoom information: [https://jlab-org.zoomgov.com/j/1608674253?pwd=SFZyYmZLWXJieGtpV2dEdVRiUEJnUT09&from=addon Link], Meeting ID: 160 867 4253, Passcode: 786506
  
== '''IMPORTANT SHIFT NOTES: '''==
+
''' [https://userweb.jlab.org/~kuhn/RGC/RCschedule.pdf Run Coordinator and Target Expert Schedule] '''
  
* '''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House'''
+
''' [https://userweb.jlab.org/~kuhn/RGC/RunPlan.pdf Longterm Run Plan] '''
* 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 also be taken from off-site - again, 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!
 
  
 +
''' [https://userweb.jlab.org/~kuhn/RGC/RunPlan_FTon2.pdf Medium-Term Run Plan] (FTon Portion Part 2) '''
  
== <font color=blue>''' Run Plan: September - December 2022 '''</font> ==  
+
== '''IMPORTANT SHIFT NOTES'''==
  
=== GENERAL INFORMATION ===
+
* '''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House'''
* '''Before leaving the hall and going to beam permit check that dome lights, forward carriage lights, and pie tower lights are OFF'''
+
* 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.
* Moller runs should be taken with 8-10 nA.
+
* '''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!
* We have a new policy NOT to leave the beam viewer in the beam at all times, to avoid damage to electronics, cameras etc. Please REMOVE the beam viewer unless we are actively tuning the beam or calibrating beam position/raster.
+
 
* '''We have a new FSD condition for when the raster is operating:'''
+
Note to shifts, please:
** 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).
+
* read the '''logbook''', be aware of previous 24 hours
** For beam tuning or other non-rastered beam, the Raster FSD must be MASKED.
+
* arrive at least 10 minutes early for '''shift change'''
* Whenever you change the 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.
+
* refresh the run wiki pages, look over them every shift:
* 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, but if DAQ crashes, you SHOULD follow these steps, and the same for mon12. '''Make sure there is ONLY ONE INSTANCE of RasterMon AND mon12 running anywhere in the Counting House.'''
+
** follow the '''expert/worker shift instructions'''  
* REMINDER FOR ALL EXPERTS: Please take care to fill out the BTA carefully and correctly. 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. ALSO: Make sure that the target type is reflected accurately on the target and beamline GUIs.
+
** find latest pitfalls and known issues under '''GENERAL INFORMATION'''
* '''After each change of running conditions''' (target type, luminosity): Please check that the trigger alarms (on rate/nA) are set appropriately and change them as needed.
+
* '''communicate''' with your co-shift person
* <font color=blue> 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. </font>
+
** the shift expert should know about and refer to logbook entries in their shift summary
* <font color=red> Do not change running conditions while a run is ongoing. This includes changing target polarization or HWP, etc.
+
** the shift worker should discuss an issue with the shift expert before making extra logbook entries
* The Faraday Cup power limit for the continuous operation was lifted up to 1 kW. For the remainder of the RGC the beam blocker should not be used  https://logbooks.jlab.org/entry/4047791 </font>
 
  
 +
== '''Short Term Schedule for the Week from Wednesday,  March 15th, to Monday March 20th, 2023''' ==
  
=== SHORT RANGE PLAN (last update September 27, 2022) ===
+
* Current: 4 nA
  
<!--* Bring beam back to the hall on the tagger dump, follow standard proceedings. Do harp scans (10nA). Afterward do Moller run with 1/2 wave plate OUT.
 
* Then establish beam to FC. Raster must be ON. Check if beam goes cleanly through. You might need to adjust raster, check with RC and/or beamline expert.-->
 
* Production data on NH3 with NEGATIVE polarization with 6nA beam. First run with PROD66_PIN config. afterwards PROD66 config.
 
* We will continue with NH3 until the Maintenance Day (Thursday 9/29). Change HWP from OUT to IN during Swing shift today (Wednesday 9/28).
 
* During Maintenance day, we will do a TE on NH3 and then switch to CH2 target.
 
* We need to check for bleedthrough when HallC increases current. Ask MCC to do this (switching off HallB laser and check beam current in HallB with just C and D on).
 
* <font color=blue>In general, we should take data with the PROD66 configuration. Once or twice a day (BEFORE and AFTER a HWP flip or target polarization change), take a run with the PROD66_PIN (same trigger file in both cases). PROD66_PIN should have at least 20 M events.</font>
 
* We should change the HWP ("lambda/2 plate"), after a full day of useful data on NH3 or ND3. WE MUST INFORM THE OTHER HALLS WHENEVER WE DO THAT.
 
* We should reverse the target polarization after every TWO days of good data taking. So the sequence is "1 day on ammonia, swap HWP, one day on ammonia, flip target polarization, one day on ammonia, swap HWP, one day on ammonia". ND3 may have to be annealed between target polarization changes.
 
* Do a RICH Recovery procedure once a day during day shift (in-between runs) if everything is okay. If a RICH problem occurs, you might have to do the RICH Recovery procedure.  If RICH recovery procedure fails to fix the problem the first time, try again one more time. If the second RICH recovery attempt does not fix the problem  call RICH expert and keep taking data.
 
 
* Run duration: 100M events or 4 hours, whichever comes first.
 
* Run duration: 100M events or 4 hours, whichever comes first.
* Current: 6 nA. For empty target runs, increase beam current as much as possible, up to at MOST 90 nA (NO beam blocker!).
 
  
=== PLAN for Saturday-Swing (10/1/2022) to Tuesday-Owl (10/4/2022) ===
+
* Note, BOM is not installed for this experiment, so it does not matter whether it appears masked in FSD or not.
* Take production data on CH2 start with IN configuration. Use PROD66 configuration (Do not use PIN configuration)
+
 
* Somewhere around noon (Sunday-Day shift). Flip the beam into OUT configuration. Still use PROD66 configuration (Do not use PIN configuration)
+
* '''The Faraday Cup power limit''' for the continuous operation was lifted up to 1 kW. For the remainder of the RG-C the beam blocker should not be used  https://logbooks.jlab.org/entry/4047791
* Continue the OUT configuration until the Monday-day shift (Target swap)
+
 
* For Monday-Day (10/3/2022) shift, continue the data taking on CH2 OUT until the RadCon/Target group come to change the target to Carbon. After RadCon arrive, ask for controlled access
+
* '''Conditions for raster operation:'''
* After the target group finish swap the target, ask MCC for 8 nA beam
+
** 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).
* Run with the PROD66 Configuration (Do not use PIN configuration) for 4 hours OR 100 Million events accumulated.
+
** For beam tuning or other non-rastered beam, the '''Raster FSD''' must be MASKED.
* Continue this production run until the end of Tuesday-Owl shift
+
** 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 beam raster on.'''
 +
** '''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 "FTon"
  
<!-- === <font color=green>Start-up after Configuration Change 3-sept</font>  ===
+
* If HWP is changed, start a new run  
# First target: 2 cm diameter C target (+ LHe) - '''DONE'''
 
## Once beam is available, tune it on the tagger dump.
 
## Once upstream harp scans are acceptable (see below References and Standards), take a Moller run before degaussing the tagger. (Check for bleedthrough)
 
## Establish 5 nA beam on the FC. ** Get clean beam **. Raster off/Raster FSD masked.
 
## Do a harp scan at 2H01.
 
## Once beam profile and position is acceptable, we need to find the limits in beam position with acceptable DC occupancy. Turn on all detectors, start DAQ and mon12. Notify target group that we will change targets in about 2 hours.
 
## Get 5 nA beam:
 
### Ask MCC to move beam in steps of 1 mm in +x-direction until you see a sharp increase in DC occupancies (mon12), especially in Region 1, Sector 4. (Stay below 8% occupancy in R1).
 
### new method (from EP): look at DC_occupancy_norm and compare the R1 s1 and s4 occupancies.  log it for each value of x.  choose the position where the s1 and s4 occupancies are equal and small, in between where the rates increase a lot.
 
### Repeat with -x (watch R1 S1).
 
### Center beam between the 2 limits found above. Repeat same procedure by moving beam in +y direction (Sectors 2 and 3) and -y direction (Sectors 5 and 6).
 
### Have MCC center the beam between all limits: this will be our new reference beam position. Record all BPM x and y values and convey to MCC.
 
## Next step is to check with raster turned on: Offset (0,0) and Vpp(V) = 0.2*Delta-x(mm) , 0.19*Delta-y where Delta-x/Delta-y are the differences in the extreme positions in x and y found above. Take a short run and check mon12 for the occupancy vs. x and y as well as rastermon.
 
### Decrease beam current to ~2.5 nA
 
### Increase raster size until you see a 1/2-circle of target walls on rastermon.  Then reduce it
 
### call Sebastian and/or Eugene to determine optimal raster size
 
# It was too late to call Chris Keith to change targets (LW: 9/3 21:25).  Continue C running
 
# Continue C with LHe - '''DONE'''
 
## Take a series of runs for luminosity scan: 2, 4, 6, 8, 10, 12 nA (with raster). Each run should be the greater of 1 hour or 1 M events with trigger bit 0 (i.e., if trigger bit 0 / all triggers = f, then take 1 M / f events).
 
## Fine-adjust raster to optimize raster radius vs. luminosity (only during day shift).
 
## Take production data at beam current where average R1 DC occupancy is 5-6%
 
# Sunday 13:00 change target (possibly later but no earlier)
 
# 2nd target: raster calibration target - '''DONE''' 9/4 15:30
 
## Take photos of raster calibration target before insertion, so we know what to look for.
 
## Insert beam blocker for FC. Check that FC blocker calibration from last time we did this (before the changeover) are loaded. This is just a precaution in case we need to increase the beam current.
 
## Take a run (roughly 1 hour) with NO LHe, same raster settings as of now, and increase the beam current to get enough trigger rate (5kHz) as long as the DC occupancies don't exceed 6%
 
## Use high-statistics rastermon and mon12 data with raster calibration target to calibrate Vpp, offset, and Voltage->position in rastermon and CCDB. (Requires experts like Eugene, Maurik or Sebastian)
 
## Use the information from rastermon to determine the relative position of the target. Work with target group (J. Brock) to adjust target until it is centered on the raster pattern.
 
# 3rd target: Empty. PARTIALLY DONE. Remaining to do (later, when there's an opportunity to change back to the Empty target):
 
## First '''reduce''' current to about 2 nA and over-raster the target (turn all CD HV off or in safe mode). Observe rastermon - increase Vpp in 0.2 V steps in x and then y until you see MOST of the target rim OR we get FSD trips from halo counters. '''DONE'''
 
## Ask Eugene to ramp down Solenoid and Torus
 
## Empty LHe and turn off raster (Vpp = 0, offsets nonzero).  Take a zero field alignment run (special trigger: rgc_300MeV_v1.6_zero.trg). No LHe. Try 1-2 nA beam (watch occupancies). Take 4-hour runs.  Get 20M events total. '''DONE'''
 
## Ask Eugene to turn ON Solenoid and Torus.  Ask MCC to remask solenoid.  Turn off beam during magnet ramp.
 
## Alignment run
 
### Call Yuri to restore MVT HV to normal operation. 
 
### Increase beam current as occupancy / trigger rate / currents allow.  If you can increase beam past 15 nA, then put in the beam blocker and call Rafo for calibration constants.
 
### Take a two hour beam position calibration run (change trigger to standard DAQ configuration [see below]) WITHOUT LHe and WITHOUT raster (ask MCC to mask raster FSD).
 
### Call Chris Keith, Radcon or MCC, and the RC when the run starts to notify them of a target change in 2 hours..
 
## Take a 2 hour run with standard running condition including raster but no LHe. (Beam blocker in, beam current 15-20 nA)
 
## Take 4-hour run WITH LHe at normal level.
 
# Install carbon target
 
## take carbon data with normal raster and full 4He (raster unmasked). 6 nA, standard configuration (PROD66 - NOT PIN) and trigger.
 
# 4th target: ND3
 
## Noon Tuesday: ask MCC to turn off beam. We will need RadCon. Target group will come and remove C target and install ND3 2cm dia. target.
 
## After target is filled with LHe, target group will do a measurement of polarization with microwave.  Then we ask for beam back.
 
## Cold irradiation (begin around beginning of Swing shift). See also below.
 
### Put beam blocker in, and turn off all HV to all detectors (BMTs in safe mode).
 
### Use our standard raster pattern (see below - check position on all BPMs). Raster FSD must be Unmasked.
 
### Start with 15 nA beam. If nothing trips, keep increasing up to 50 nA. (You will have to increase the downstream halo counter threshold - see below and/or check with Eugene).
 
### NOTE: NO data will be taken in this configuration. However, you can start a "junk run" to check the raster pattern with rastermon - only the random/pulser panel should be filled.
 
### Beam should go away sometime around 7 Wednesday morning (maintenance day). Wait until about 9 and then go to controlled access. We will need Radcon and target group.
 
## Remove ND3 target, anneal, and reinsert. Take baseline, TE, and begin polarizing.
 
## Start of production data taking on ND3 once beam returns. First move beam slightly more to the left by setting raster x-offset to -0.55 V. Also reduce y-raster Vpp to 3.15 V. Check occupancy vs. raster position (mon12) and rastermon as well as DAQ rates, electron lifetime, beam halo monitor rates and average R1 DC occupancies to see if this improve things.-->
 
  
<!-- ==== <font color=green> Cold Irradiation Process</font> ====
+
=== PLAN for March 15-20, 2023 ===
In this process we want to add the irradiation of the target by increasing the beam current. For this <font color="red"> <b>CLAS must be off </b></font>.<br />
+
Note: an hour before changing the HWP, call Bill Henry (from Hall A) at 215-908-2245. He offered his help in optimizing the beam charge asymmetries when changing the HWP. He will stop by the counting house and run his code, which will take a minute. We will do the HWP changes during the day shifts.  
<b>Procedure: </b>
 
* Turn off ALL high voltages, but put MVT in "safe" mode.
 
* Normal raster size (and FSD interlock)
 
* Insert the FCup beam blocker.
 
* You have to allow MCC increase the Fast Shutdown levels to Midstream: 20000, Downstream: 2000000 (i.e. 10x what they are now.) Then ask for 50 nA beam, increasing "slowly" from 15 nA while you watch for FSD or high counts on the beam line monitors.
 
* Irradiate the target for about 16 hours , with this high beam current and raster size.
 
* Target must be annealed and polarized to assess effect of this procedure.
 
  
 +
*Wednesday, March 15th: Beam study downtime starts at 8:00 AM. Beam is expected to be back by 15:00 PM. If they beam shows up before 22:00 PM, we will need to take a Moller run. Then, start taking data on ND3(+) (torus outbending, 4nA beam current, HWP IN).
 +
*Thursday, March 16th: Data taking on ND3 (+) (torus outbending, 4nA, HWP out)
 +
* Friday, March 17th: anneal the target and flip the polarization to negative. Will take about 3 hours starting around 9AM. Then, take data on ND3 (torus outbending, 4nA, HWP out)
 +
* Saturday, March 18th: Continue taking data on ND3(-) (torus outbending, 4nA, HWP IN)
 +
* Sunday, March 19th: Will change the target to C sometime in the day shift and start taking data. Will go to restricted access and will organize this between RadCon and Target Experts.
 +
* Till Monday, March 20th, 07:00 AM: Continue taking data till the beam goes away.
  
## (NOTE: the beam raster MUST be on at all times, hence you cannot do a harp scan at 2H01). You can temporarily put in the beam viewer to take a look at the profile, but then it has to be taken out. Some of the above is also described in the manuals - Physics-Quality Beam and Performing Møller Runs under “Shift Documentation” tab of the Run Group C run wiki.
+
* When the beam goes away:
# <b> We want to re-do the optimization for the raster settings. </b> Start a run and using both the new mon12 plots created by Raffa, and the FT asymmetry (mon12). Change the raster offset by -0.1 in X and Y and check that the amount of "red areas" are similar for all 6 sectors and no yellow or white, and the FT asymmetry is roughly 0. In the previous reference runs, the beam was too much to the right and too high. (Note that the target is large enough in diameter so that you shouldn’t hit the edge - confirm with your rastermon. Note that whenever you change the raster offset, you will have to observe how 2H01 x and y change, and tell MCC that those are the new values to shoot for. (You can tell them to stop trying to center the beam on 2H01 while you are trying out different offsets - otherwise you might end up working at cross-purpose).
+
# Turn all HV OFF except SVT and BMT. For FT we turn HV OFF, but keep the chiller and LV ON, Raffaella will do some LED calibrations.  
# Note the final raster parameters and positions on 2H01 - update the whiteboard and th "Short-Term Schedule” accordingly, and inform MCC. <br /> You don’t need to start a new run for every new set of raster parameters - you can just clear mon12 and rastermon. Ideally someone should write down what you observe and log the raster DC occupancies and the FT asymmetry plots for each setting.
+
# Solenoid will remain ON for the target group to do NMR studies.  
# Once the raster is satisfactory, start a long production run. We want at least 50M events.
+
# The torus should be ramped down. Morgan or Denny can do it if they are around at that time, or call Eugene and he do it.  
# Depending on the report from the FT (Forward Tagger) analysis, we may go back to doing the 50nA "cold irradiation" process. Check the RC.
+
# The hall should go to controlled access awaiting for radcon to come and do a full survey for restricted access.
  
-->
+
NOTES:
<!-- * END EMPTY TARGET RUNNING. Ask target group to install new target (CH2 - check with RC/Sebastian/Target Group).
+
* Watch the beam positions (and thus the midstream halo counters) closely and ask MCC to adjust the positions if they are (on average) >=0.1mm off.
** CH2 run (fill with LHe)
+
* Remember, the hall will only be dropped in controlled mode once someone goes downstairs and enters the hall. You/RadCon should do that right away after calling MCC.  
*** Raster on, FSD unmasked, no orbit lock.
 
*** Take FC blocker out, go back to 4 nA and standard position on 2H01
 
*** Take production data with standard trigger rgc_300MeV_v1.2_no_DC.trg, PROD 66.
 
-->
 
=== 5-pass (10.55 GeV) Running conditions ===
 
* Torus at 100% current, inbending electrons. Setpoint = +3770 A (Readback = +3766 A)
 
* Solenoid setpoint +2417.5 A
 
<!-- * Establish optimal compromise between raster size (if possible, 9 mm radius), luminosity (goal: 10 nA = 10^35), and background.
 
* Run duration 100M events or 4 hours, whichever comes first.
 
** For empty target runs, increase beam current as much as possible.
 
-->
 
  
 
== <font color=blue> DAQ configuration </font> ==  
 
== <font color=blue> DAQ configuration </font> ==  
  
* Configuration <tt>PROD66</tt>/<tt>PROD66_PIN</tt>, trigger file <tt>rgc_300MeV_v2.3_Q2_1.5GeV2.trg</tt>
+
* Configuration is currently <tt>'''PROD66'''</tt>/<tt>PROD66_PIN</tt>, trigger file <tt>'''rgc_300MeV_v1.4_no_DC.trg'''</tt>
* 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''': 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!'''
+
* '''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 <font color=red>STANDARD DAQ RESTART SEQUENCE</font>:
 
* At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font>:
 
** "end run".
 
** "end run".
 
** If the run ended correctly and you will run with the same configuration and trigger file, then: "prestart", "go"
 
** 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 PROD66 and PROD66_PIN) or trigger file: "cancel", "reset", "configure", "download", "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:
 
** if the run did not end correctly or if any ROCs had to be rebooted:
 
*** Quit ALL running instances of mon12 and rastermon
 
*** Quit ALL running instances of mon12 and rastermon
Line 241: Line 165:
 
* 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.
 
* 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.
  
== <font color=blue> References and Standards 19 Sept. 22 </font>==
+
== <font color=blue> References and Standards </font>==  
  
'''Solenoid set-point of 2417.5 A results in read back 2419.57 A and exactly 5.00 T field on center'''
+
=== 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 using shim coils of polarized target on (Oct 26, 2022) -2418.50 A
 +
* Solenoid setpoint +2417.5 A (normal conditions RGA-M)
 +
i-->
 +
* Solenoid set-point of 2416.4 A results in the read back 2419.23 A and exactly 5.00 T field on center
  
'''Raster settings'''
+
'''Raster settings (current as of February 9, 2023)'''
* x: Vpp = 3.7 V, offset = -0.65 V
+
* x: Vpp = 2.7 V, offset = 0.0
* y: Vpp = 3.25 V, offset = -0.10 V
+
* y: Vpp = 2.05 V, offset = 0.50 V
 
* Fundamental Period = 2 s
 
* Fundamental Period = 2 s
 
* The correct raster calibration constants should be automatically loaded by rastermon - if not, enter them through "Config" by hand:  
 
* The correct raster calibration constants should be automatically loaded by rastermon - if not, enter them through "Config" by hand:  
Line 253: Line 184:
 
* f(y) = -0.0115*y + 24.4
 
* f(y) = -0.0115*y + 24.4
  
'''Nominal Beam Positions'''
+
'''Nominal Beam Positions (current as of February 9, 2023) '''
*2H01, X = -1.9 mm, Y = +1.2 mm
+
 
 +
*2C21A, X = -0.4 mm, Y = +0.6 mm  
 
*2C24A, X = -2.0 mm, Y = +0.6 mm  
 
*2C24A, X = -2.0 mm, Y = +0.6 mm  
*2C21A, X = -0.4 mm, Y = +0.6 mm  
+
<!-- *2H01, X = -1.8 mm, Y = +0.9 mm -->
 +
*2H01, X = -1.0 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).
 
* 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).
  
Line 263: Line 196:
 
* Midstream: 2000 Hz
 
* Midstream: 2000 Hz
 
* Downstream: 100000 Hz (1e5)
 
* Downstream: 100000 Hz (1e5)
* BOM: 1000000 Hz
+
* BOM: 1000000 Hz (BOM not installed for RG-C)
 
* 5 ms dwell time
 
* 5 ms dwell time
  
Line 269: Line 202:
  
 
* Harp Scans for Beam on Faraday Cup, 2H01  [https://logbooks.jlab.org/entry/3963256],      '' more recent scan (3 Sept 2022): ''  [https://logbooks.jlab.org/entry/4037457]
 
* Harp Scans for Beam on Faraday Cup, 2H01  [https://logbooks.jlab.org/entry/3963256],      '' more recent scan (3 Sept 2022): ''  [https://logbooks.jlab.org/entry/4037457]
* Harp Scans for Beam on 2C21 [https://logbooks.jlab.org/entry/4021281],    '' more recent scan (3 Sept 2022):'' [https://logbooks.jlab.org/entry/4037438]  
+
* Harp Scans for Beam on 2C21 [https://logbooks.jlab.org/entry/4021281],    '' more recent scan (3 Sept 2022):'' [https://logbooks.jlab.org/entry/4037438] , '' even more recent scan (1 Feb 2023):'' [https://logbooks.jlab.org/entry/4122116]
* Harp Scan on Tagger Dump (3 Sept. 2022) [https://logbooks.jlab.org/entry/4037440]
+
* Harp Scan on Tagger Dump (3 Sep 2022) [https://logbooks.jlab.org/entry/4037440], ''more recent scan (1 Feb 2023):'' [https://logbooks.jlab.org/entry/4122122]
* Monitoring Histograms (18 Sept 2022) [https://logbooks.jlab.org/entry/4043330]
+
* RasterMon (20 Oct 2022) [https://logbooks.jlab.org/entry/4064143], ''more recent raster (2 Feb 2023):'' [https://logbooks.jlab.org/entry/4122766]
* RasterMon (18 Sept 2022) [https://logbooks.jlab.org/entry/4043316]
+
* Monitoring Histograms  
 +
** run 17240, DAY Fr, 10/21/2022, ND3 (ECAL good) [https://logbooks.jlab.org/entry/4065165 https://logbooks.jlab.org/entry/4065165]
 +
** run 17348, DAY We, 11/02/2022, CH2 [https://logbooks.jlab.org/entry/4075177 https://logbooks.jlab.org/entry/4075177]
 +
** run 17363, OWL Sa, 11/05/2022, NH3 [https://logbooks.jlab.org/entry/4076956 https://logbooks.jlab.org/entry/4076956]
 +
** run 17492, DAY Th, 02/02/2023, ND3 (post-solenoid hiatus) [https://logbooks.jlab.org/entry/4122528 https://logbooks.jlab.org/entry/4122528]
 +
** run 17542, EVE Th, 02/09/2023, ND3 [https://logbooks.jlab.org/entry/4127691 https://logbooks.jlab.org/entry/4127691]
 +
** run 17547, DAY Sa, 02/11/2023, ND3 [https://logbooks.jlab.org/entry/4128938 https://logbooks.jlab.org/entry/4128938]
 +
** run 17562, DAY Mo, 02/13/2023, ND3 [https://logbooks.jlab.org/entry/4130446 https://logbooks.jlab.org/entry/4130446]
  
 
'''Counter rates'''
 
'''Counter rates'''
 
* With 6 nA beam, the upstream counters should read zero.  
 
* With 6 nA beam, the upstream counters should read zero.  
 
* The Midstream ones should read 0-20 Hz or so.
 
* The Midstream ones should read 0-20 Hz or so.
* Greatly increased rates may indicate bad beam tune or bleed-through from other Halls.  
+
* Greatly increased rates may indicate bad beam tune or bleed-through from other Halls.
<!--
+
 
* Upstream counters integrated rates: 0-15 Hz (acceptable up to 100 Hz are acceptable) @50 nA.
+
= GENERAL INFORMATION =
* Midstream counters: 10-20 Hz (acceptable up to 50 Hz) @50 nA.  
+
<!--####################################### GENERAL INFORMATION ########################################-->
* Counting rates of ~ hundreds of Hz may indicate bad beam tune or bleed-through from other Halls.
+
 
-->
+
'''see below for Known Detector Issues'''
 +
 
 +
== General Information ==
 +
 
 +
* To open CS Studio interface, type "clascss" in some terminal.
 +
 
 +
* '''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.
 +
 
 +
* 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 beam raster on.'''
 +
 
 +
* '''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.
 +
 
 +
* '''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''':
 +
** rastermon should be using ET on clondaq6
 +
*** this means startup of rastermon via command line: rastermon --et --host clondaq6
 +
** 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.
 +
 
 +
* '''Holes in CND occupancies: CAMAC CFD crate was turned off/on for some reason. You need to run the script to set the thresholds for CND CFDs. Go on a clondaq machine and type cnd-cfd-thresh -w 0. Or call the CND phone if this doesn't work.
 +
 
 +
* '''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.
 +
 
 +
== Known Issues ==
 +
FTT alarms - can be ignored (we do not have the FTT installed)
  
<!--#######################################  Notes/Known Issues ################################################-->
+
Fr 11 Nov 2022
== '''Known issues''' ==
+
ECAL PMT_SEC2_WO8 HV is disabled
# '''PCAL W strip 55 sector 6'''
+
https://logbooks.jlab.org/entry/4080950
# '''FTOF adc ecal energy sector 2 PMT #12 right
 
# '''tdcecal6 and tdcecal1 rocs''': These rocs could show errors in the DAQ screen. If so, check roc-rates, trigger rates and monitoring plots. If all looks okay, continue data taking.
 
# '''DC''': hole in sector 3, superlayer 6, would likely need a major physical repair on the chamber itself
 
# '''BMT (MVT) strips trip''' frequently. Keep an eye on the HV GUI and reset any trips.
 
#'''SLM rates too low:''' the values should not be trusted, there's an issue with the associated sensors. Check the charge asymmetry from the Faraday Cup info instead.
 
  
 +
Follow-up Re: RICH tile 21 in sector 1 is dead. Working without one tile out of 276 for a moment
 +
https://logbooks.jlab.org/entry/4079453
  
<!--
+
Run #17396: RICH lost three scalars
== '''Notes''' ==
+
https://logbooks.jlab.org/entry/4079190
  
# 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:
+
Tuesday, February 7, 2023:
#* ON: [https://logbooks.jlab.org/entry/3825712]
+
BMT Sector 2 Layer 5 is broken (HV set to 200 V)
#* 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.
 
# 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
 
#* Call Engineering on-call and target expert
 
#* Make a separate log entry with copies to HBTORUS and HBSOLENOID logbooks. In the "Notify" field add Probir Goshal, Dave Kashy, and esr-users@jlab.org
 
#* Notify Run Coordinator
 
#* Turn off all detectors
 
# Observe the guidance of the alarm handler.
 
-->
 
  
 
= Shift Expert =
 
= Shift Expert =
 
<!--#######################################  Shift Expert  ################################################-->
 
<!--#######################################  Shift Expert  ################################################-->
{| {{TableStyle1}}
 
| valign=top |
 
 
'''NOTE: BOTH the shift expert AND the shift worker MUST check monitoring histograms at least once every 30 - 60 minutes to make sure there are no major detector problems.'''
 
  
* Follow the '''[[https://wiki.jlab.org/clas12-run/index.php/Run_Group_C#Short_Term_Schedule Short Term Schedule]]''' as outlined by RC  
+
== Shift expert tasks ==
** includes Run Plan, DAQ configuration, and References and Standards
+
* 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
 +
** also check tab '''GENERAL INFORMATION'''
 
* Keep '''shift summary''' up to date in HBLOG. Record all that happens.
 
* Keep '''shift summary''' up to date in HBLOG. Record all that happens.
  
* '''Ensure''' that all monitoring plots are logged correctly and checked against the reference plots for every single run.
+
* Ensure that all '''monitoring''' plots are logged correctly and checked against the reference plots for every single run, see link under https://wiki.jlab.org/clas12-run/index.php/Run_Group_C#Useful_Links
** <font color=red> '''NEW!!!'''  Helicity-Latched Trigger GUI  and the Helicity Trigger Asymmetry strip-chart (not accessible remotely) </font> (example https://logbooks.jlab.org/entry/4041939).  
+
* Both, you and the shift worker should '''reset & check spectra frequently'''
*** To get the helicity-latched trigger GUI, look under "DAQ" in CS-Studio
 
*** For the helicity trigger asymmetry strip chart: Menu at Helicity-Latched Trigger GUI Screen -> Menu -> livePlot.
 
  
* '''Polarized target issues: In all cases contact the polarized target expert on call.''' Examples to keep an eye on:
+
* '''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'''
 
** '''Ice on the run valve'''
*** See the run valve via camera http://hallbcam04/view/index.shtml, (see also Camera on PT12 -- web link at Lognumber 4002803.) Example of ice on the valve, see https://logbooks.jlab.org/entry/4001225. If you see ice, contact the expert on call.
+
*** See the run valve via camera http://hallbcam04/view/index.shtml, (see also Camera on PT12 -- web link at Lognumber 4002803.) Example of ice on the valve, see https://logbooks.jlab.org/entry/4001225.  
** '''NMR running'''
+
** '''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 should be moving, indicating that the NMR is running and the polarization is measured. If the NMR is not running, contact the expert on call.
+
*** 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 polarisation (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. Thus, contact the expert on call.
+
*** If the NMR display is frozen or disappears, here are the steps to follow:
** '''Alarms''' from System RG-C Polarized Target (alarm handler). If you get an alarm, ...
+
**** Open a new terminal window on the bottom right-most screen.  
 +
**** Type "ssh clasrun@clonsl1"
 +
**** Type "nmr-vnc”
 +
**** Click "Run" under "NMR Controls" - the window should now be updating (blue bar moving)
 +
*** 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.
 
* 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. And it also prints out that you have to "Cancel->Reset->Configure->Download->Prestart" before starting the next run.
+
** 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.
  
 
* '''[https://bta.acc.jlab.org Fill out BTA]''' hourly.  Click "Load from EPICS" to automatically fill the left side then correct as needed.
 
* '''[https://bta.acc.jlab.org Fill out BTA]''' hourly.  Click "Load from EPICS" to automatically fill the left side then correct as needed.
Line 345: Line 314:
 
** Experiment beam time  
 
** Experiment beam time  
 
*** ER: experiment ready
 
*** ER: experiment ready
*** PCC: planned configuration change (when beam is masked while radiators are moved, DAQ (roc rebooting,  restarting runs)), if more than 5 minutes, put a short comment, eg harp scans or DAQ.
+
*** PCC: planned configuration change (when beam is masked while radiators are moved, DAQ (stopping/starting runs, tests, ...) are PCC..  
*** UED: unplanned experiment down (hardware failure)
+
*** 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
  
  
Line 352: Line 324:
  
 
(remote) shift worker: see dedicated [https://wiki.jlab.org/clas12-run/index.php/Run_Group_M#tab=Remote_Shifts Worker Shift] tab above.
 
(remote) shift worker: see dedicated [https://wiki.jlab.org/clas12-run/index.php/Run_Group_M#tab=Remote_Shifts Worker Shift] tab above.
 
|}
 
  
 
= Worker Shift =
 
= Worker Shift =
 +
<!--#######################################  Worker Shift  ################################################-->
 +
== Shift Worker Tasks ==
  
 +
* Check the information in the '''Short Term Schedule''' and '''GENERAL INFORMATION''', 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
  
=== For REMOTE Shifts (offsite): ===
 
* '''Zoom for 24-7 communication with counting house:'''  https://jlab-org.zoomgov.com/j/1619881100
 
** Passcode REQUIRED: 927417
 
* 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 <tt>clascss-remote</tt>.
 
* [https://userweb.jlab.org/~baltzell/clas12/shift/remote-demo.mp4 Remote Demonstration Video (150 MB)]
 
 
== Shift Worker Tasks ==
 
 
'''New:''' Use the new '''HBRUN logbook''' for automated and run-specific entries and screenshots, see https://logbooks.jlab.org/entry/4048698
 
  
 
'''Make the following log entries ONCE per run'''
 
'''Make the following log entries ONCE per run'''
* Screenshots: submit to logbook only if you capture the information '''with beam ON'''
+
* '''Screenshots''': submit to logbook only if you capture the information '''with beam ON'''
 
** Beamline Overview, in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser]
 
** Beamline Overview, in VNC or [https://hallbopi.jlab.org/webopi3.3/w?opi=beamline/clas12-web.opi Web Browser]
 
** CLAS12 Trigger rates and DAQ status
 
** CLAS12 Trigger rates and DAQ status
** Beam current and position strip-charts
+
** RGC Polarized Target GUI - under Beamline on CS-Studio
** RGC Polarized Target GUI - under Beamline on CSS
+
** Helicity Asymmetry Strip Charts - see [https://logbooks.jlab.org/entry/4123228] for an example. Also read and follow the instructions below under "Log the Strip Charts".
** Helicity-latched trigger GUI - under DAQ in CS-Studio
 
** The new <font color=red> Helicity Trigger Asymmetry strip-chart </font> (example https://logbooks.jlab.org/entry/4041939) (not accessible remotely).
 
*** For the helicity trigger asymmetry strip chart: Menu at Helicity-Latched Trigger GUI Screen -> Menu -> livePlot. BEFORE SENDING TO LOGBOOK, MAKE SURE YOU SELECT THE 2nd VARIABLE FROM BOTTOM (dark green) ON THE TOP TWO STRIPCHARTS to get a reasonable scale.
 
* Upload monitoring plots to logbook
 
** Standard spectra (mon12): <u> inspect [https://clas12mon.jlab.org/mon12/histograms/?reference=4043330 ''' all monitoring histograms ''']  and carefully compare them to the corresponding reference histograms: reference, current, and 5 most recent runs</u>. You can choose a different reference run if you are confident what you are doing, the reference numbers refer to logbook entries.
 
** Raster Monitoring: upload RasterMon plots to the logbook (use '''"Log Entry" button on RasterMon''' screen at bottom-right corner).
 
** An example of a "decent looking" RasterMon is here: [https://logbooks.jlab.org/entry/4040598]. The x and y distributions should show a smooth dome, without any horns or pentaquark-like peaks on it, and without the distributions looking very sliced-off at the edges.  
 
  
* '''Check''' the [http://hallbcam04/view/index.shtml 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).
+
* '''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: [https://logbooks.jlab.org/entry/4040598]. 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:'''
 
'''Once per shift:'''
Line 399: Line 358:
 
** The logbook entry shows all histograms.
 
** The logbook entry shows all histograms.
  
* Log the '''strip charts''' in time intervals '''according to the x-axis time span.'''
+
* '''Check''' the [http://hallbcam04/view/index.shtml 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).
  
* How to get the strip charts:
+
* '''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.'''
** For the beam: CS-Studio -> Beamline -> Strip Charts.
+
** Beam current and position strip-charts (CS-Studio -> Beamline -> Strip Charts)
**<font color=red> '''NEW!!!''' </font> For the helicity trigger asymmetry strip chart: Menu at Helicity-Latched Trigger GUI Screen -> Menu -> livePlot (not accessible remotely)
+
** Helicity Trigger Asymmetry strip-chart (CS-Studio -> DAQ -> Helicity-Latched Trigger GUI Screen -> click on "Menu" -> myaPlot (not accessible remotely) -> Choose "load config time axis: start: -12 hours end: NOW" and click "accept"
** right-click on the screen and select "Make Elog Entry", make sure to log to HBLOG and not ELOG
+
*** [https://logbooks.jlab.org/entry/4123228 Example] 
** You can also see beam charts in the Web Browser: [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Upstream+and+Midstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scaler_cS3b&pv=scaler_cS4b&pv=scaler_cS6b&pv=scaler_cS12b&pv=scaler_cS13b&pv=scaler_cS14b&pv=scaler_cS15b&scaler_cS3blabel=scaler_cS3b&scaler_cS3bcolor=%23a6cee3&scaler_cS3byAxisLabel=Rate++%28Hz%29&scaler_cS3byAxisMin=&scaler_cS3byAxisMax=&scaler_cS3byAxisLog&scaler_cS3bscaler=&start=2020-08-08+09%3A02%3A36&end=2020-08-08+09%3A07%3A36&scaler_cS4blabel=scaler_cS4b&scaler_cS4bcolor=%231f78b4&scaler_cS4byAxisLabel=&scaler_cS4byAxisMin=&scaler_cS4byAxisMax=&scaler_cS4byAxisLog=&scaler_cS4bscaler=&scaler_cS5byAxisLabel=&scaler_cS5byAxisMin=&scaler_cS5byAxisMax=&scaler_cS5byAxisLog=&scaler_cS5bscaler=&scaler_cS6blabel=scaler_cS6b&scaler_cS6bcolor=%2333a02c&scaler_cS6byAxisLabel=&scaler_cS6byAxisMin=&scaler_cS6byAxisMax=&scaler_cS6byAxisLog=&scaler_cS6bscaler=&scaler_cS7byAxisLabel=&scaler_cS7byAxisMin=&scaler_cS7byAxisMax=&scaler_cS7byAxisLog=&scaler_cS7bscaler=&scaler_cS12blabel=scaler_cS12b&scaler_cS12bcolor=%23e31a1c&scaler_cS12byAxisLabel=&scaler_cS12byAxisMin=&scaler_cS12byAxisMax=&scaler_cS12byAxisLog=&scaler_cS12bscaler=&scaler_cS13blabel=scaler_cS13b&scaler_cS13bcolor=%23fdbf6f&scaler_cS13byAxisLabel=&scaler_cS13byAxisMin=&scaler_cS13byAxisMax=&scaler_cS13byAxisLog=&scaler_cS13bscaler=&scaler_cS14blabel=scaler_cS14b&scaler_cS14bcolor=%23ff7f00&scaler_cS14byAxisLabel=&scaler_cS14byAxisMin=&scaler_cS14byAxisMax=&scaler_cS14byAxisLog=&scaler_cS14bscaler=&scaler_cS15blabel=scaler_cS15b&scaler_cS15bcolor=%23cab2d6&scaler_cS15byAxisLabel=&scaler_cS15byAxisMin=&scaler_cS15byAxisMax=&scaler_cS15byAxisLog=&scaler_cS15bscaler= Upstream/Midstream Halo Counters], [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Downstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scalerS8b&pv=scalerS9b&scalerS8blabel=scalerS8b&scalerS8bcolor=%23a6cee3&scalerS8byAxisLabel=Rate++%28Hz%29&scalerS8byAxisMin=&scalerS8byAxisMax=&scalerS8byAxisLog&scalerS8bscaler=&pv=scalerS10b&pv=scalerS11b&scalerS9blabel=scalerS9b&scalerS9bcolor=%231f78b4&scalerS9byAxisLabel=&scalerS9byAxisMin=&scalerS9byAxisMax=&scalerS9byAxisLog=&scalerS9bscaler=&scalerS10blabel=scalerS10b&scalerS10bcolor=%23b2df8a&scalerS10byAxisLabel=&scalerS10byAxisMin=&scalerS10byAxisMax=&scalerS10byAxisLog=&scalerS10bscaler=&scalerS11blabel=scalerS11b&scalerS11bcolor=%2333a02c&scalerS11byAxisLabel=&scalerS11byAxisMin=&scalerS11byAxisMax=&scalerS11byAxisLog=&scalerS11bscaler= Downstream Halo Counters], [https://epicsweb.jlab.org/wave/?start=2020-07-08+16%3A50%3A02&end=2020-07-08+16%3A55%3A02&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Beam+Currents&fullscreen=false&layoutMode=2&viewerMode=2&pv=IPM2C21A&pv=IPM2C24A&pv=scaler_calc1b&IPM2C21Alabel=IPM2C21A&IPM2C21Acolor=%23a6cee3&IPM2C21AyAxisLabel=Beam+Current+%28nA%29&IPM2C21AyAxisMin=0&IPM2C21AyAxisMax=300&IPM2C21AyAxisLog&IPM2C21Ascaler=&scaler_calc1blabel=Faraday+Cup&scaler_calc1bcolor=%23b2df8a&scaler_calc1byAxisLabel=&scaler_calc1byAxisMin=&scaler_calc1byAxisMax=&scaler_calc1byAxisLog&scaler_calc1bscaler= Beam Currents], [https://epicsweb.jlab.org/wave/?start=2020-08-03+12%3A30%3A57&end=2020-08-03+12%3A35%3A57&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=BPM+Positions+%28Y-Axis+is+mean+%2B%2F-+0.5+mm%29&fullscreen=false&layoutMode=3&viewerMode=2&pv=IPM2C24A.XPOS&pv=IPM2C24A.YPOS&pv=IPM2H01.XPOS&pv=IPM2H01.YPOS&IPM2C24A.XPOSlabel=IPM2C24A.XPOS&IPM2C24A.XPOScolor=%23e31a1c&IPM2C24A.XPOSyAxisLabel=&IPM2C24A.XPOSyAxisMin=-2.0&IPM2C24A.XPOSyAxisMax=+1.0&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=pink&IPM2C24A.YPOSyAxisLabel=&IPM2C24A.YPOSyAxisMin=-2.0&IPM2C24A.YPOSyAxisMax=1.0&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=darkgreen&IPM2H01.XPOSyAxisLabel=&IPM2H01.XPOSyAxisMin=-2.0&IPM2H01.XPOSyAxisMax=1.0&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=lightgreen&IPM2H01.YPOSyAxisLabel=&IPM2H01.YPOSyAxisMin=-2.0&IPM2H01.YPOSyAxisMax=1.0&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler=#a6cee3&IPM2C24A.XPOSyAxisLabel=2C24+X+(mm)&IPM2C24A.XPOSyAxisMin=-1.5&IPM2C24A.XPOSyAxisMax=-0.5&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=%231f78b4&IPM2C24A.YPOSyAxisLabel=2C24+Y+(mm)&IPM2C24A.YPOSyAxisMin=0.3&IPM2C24A.YPOSyAxisMax=1.3&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=pink&IPM2H01.XPOSyAxisLabel=2H01+X+(mm)&IPM2H01.XPOSyAxisMin=-0.6&IPM2H01.XPOSyAxisMax=0.4&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=darkred&IPM2H01.YPOSyAxisLabel=2H01+Y+(mm)&IPM2H01.YPOSyAxisMin=0.4&IPM2H01.YPOSyAxisMax=1.4&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler= BPM Positions]
+
*** '''Choose reasonable y / x axis ranges:''' R-click on the axis -> Modify (axis-name) Axis
 +
*** For the y axis in the bottom panel, choose the NMR polarization and a reasonable range for the y axis (always from 0 to some maximum value), same for the 60-min trigger bit polarization. Those two do NOT have to have the same scale - it is better to try to get the dark blue and red curves to lie on top of each other (more or less).
 +
*** Set the time axis auto-update.  ">>" symbol will appear below the time axis when this is activated.  (Right-click on X axis ->" [A] Set Auto Time Stepping")
 +
 
 +
* You can also see beam charts in the Web Browser: [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Upstream+and+Midstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scaler_cS3b&pv=scaler_cS4b&pv=scaler_cS6b&pv=scaler_cS12b&pv=scaler_cS13b&pv=scaler_cS14b&pv=scaler_cS15b&scaler_cS3blabel=scaler_cS3b&scaler_cS3bcolor=%23a6cee3&scaler_cS3byAxisLabel=Rate++%28Hz%29&scaler_cS3byAxisMin=&scaler_cS3byAxisMax=&scaler_cS3byAxisLog&scaler_cS3bscaler=&start=2020-08-08+09%3A02%3A36&end=2020-08-08+09%3A07%3A36&scaler_cS4blabel=scaler_cS4b&scaler_cS4bcolor=%231f78b4&scaler_cS4byAxisLabel=&scaler_cS4byAxisMin=&scaler_cS4byAxisMax=&scaler_cS4byAxisLog=&scaler_cS4bscaler=&scaler_cS5byAxisLabel=&scaler_cS5byAxisMin=&scaler_cS5byAxisMax=&scaler_cS5byAxisLog=&scaler_cS5bscaler=&scaler_cS6blabel=scaler_cS6b&scaler_cS6bcolor=%2333a02c&scaler_cS6byAxisLabel=&scaler_cS6byAxisMin=&scaler_cS6byAxisMax=&scaler_cS6byAxisLog=&scaler_cS6bscaler=&scaler_cS7byAxisLabel=&scaler_cS7byAxisMin=&scaler_cS7byAxisMax=&scaler_cS7byAxisLog=&scaler_cS7bscaler=&scaler_cS12blabel=scaler_cS12b&scaler_cS12bcolor=%23e31a1c&scaler_cS12byAxisLabel=&scaler_cS12byAxisMin=&scaler_cS12byAxisMax=&scaler_cS12byAxisLog=&scaler_cS12bscaler=&scaler_cS13blabel=scaler_cS13b&scaler_cS13bcolor=%23fdbf6f&scaler_cS13byAxisLabel=&scaler_cS13byAxisMin=&scaler_cS13byAxisMax=&scaler_cS13byAxisLog=&scaler_cS13bscaler=&scaler_cS14blabel=scaler_cS14b&scaler_cS14bcolor=%23ff7f00&scaler_cS14byAxisLabel=&scaler_cS14byAxisMin=&scaler_cS14byAxisMax=&scaler_cS14byAxisLog=&scaler_cS14bscaler=&scaler_cS15blabel=scaler_cS15b&scaler_cS15bcolor=%23cab2d6&scaler_cS15byAxisLabel=&scaler_cS15byAxisMin=&scaler_cS15byAxisMax=&scaler_cS15byAxisLog=&scaler_cS15bscaler= Upstream/Midstream Halo Counters], [https://epicsweb.jlab.org/wave/?myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Downstream+Halo+Counters&fullscreen=false&layoutMode=2&viewerMode=2&pv=scalerS8b&pv=scalerS9b&scalerS8blabel=scalerS8b&scalerS8bcolor=%23a6cee3&scalerS8byAxisLabel=Rate++%28Hz%29&scalerS8byAxisMin=&scalerS8byAxisMax=&scalerS8byAxisLog&scalerS8bscaler=&pv=scalerS10b&pv=scalerS11b&scalerS9blabel=scalerS9b&scalerS9bcolor=%231f78b4&scalerS9byAxisLabel=&scalerS9byAxisMin=&scalerS9byAxisMax=&scalerS9byAxisLog=&scalerS9bscaler=&scalerS10blabel=scalerS10b&scalerS10bcolor=%23b2df8a&scalerS10byAxisLabel=&scalerS10byAxisMin=&scalerS10byAxisMax=&scalerS10byAxisLog=&scalerS10bscaler=&scalerS11blabel=scalerS11b&scalerS11bcolor=%2333a02c&scalerS11byAxisLabel=&scalerS11byAxisMin=&scalerS11byAxisMax=&scalerS11byAxisLog=&scalerS11bscaler= Downstream Halo Counters], [https://epicsweb.jlab.org/wave/?start=2020-07-08+16%3A50%3A02&end=2020-07-08+16%3A55%3A02&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=Beam+Currents&fullscreen=false&layoutMode=2&viewerMode=2&pv=IPM2C21A&pv=IPM2C24A&pv=scaler_calc1b&IPM2C21Alabel=IPM2C21A&IPM2C21Acolor=%23a6cee3&IPM2C21AyAxisLabel=Beam+Current+%28nA%29&IPM2C21AyAxisMin=0&IPM2C21AyAxisMax=300&IPM2C21AyAxisLog&IPM2C21Ascaler=&scaler_calc1blabel=Faraday+Cup&scaler_calc1bcolor=%23b2df8a&scaler_calc1byAxisLabel=&scaler_calc1byAxisMin=&scaler_calc1byAxisMax=&scaler_calc1byAxisLog&scaler_calc1bscaler= Beam Currents], [https://epicsweb.jlab.org/wave/?start=2020-08-03+12%3A30%3A57&end=2020-08-03+12%3A35%3A57&myaDeployment=ops&myaLimit=100000&windowMinutes=30&title=BPM+Positions+%28Y-Axis+is+mean+%2B%2F-+0.5+mm%29&fullscreen=false&layoutMode=3&viewerMode=2&pv=IPM2C24A.XPOS&pv=IPM2C24A.YPOS&pv=IPM2H01.XPOS&pv=IPM2H01.YPOS&IPM2C24A.XPOSlabel=IPM2C24A.XPOS&IPM2C24A.XPOScolor=%23e31a1c&IPM2C24A.XPOSyAxisLabel=&IPM2C24A.XPOSyAxisMin=-2.0&IPM2C24A.XPOSyAxisMax=+1.0&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=pink&IPM2C24A.YPOSyAxisLabel=&IPM2C24A.YPOSyAxisMin=-2.0&IPM2C24A.YPOSyAxisMax=1.0&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=darkgreen&IPM2H01.XPOSyAxisLabel=&IPM2H01.XPOSyAxisMin=-2.0&IPM2H01.XPOSyAxisMax=1.0&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=lightgreen&IPM2H01.YPOSyAxisLabel=&IPM2H01.YPOSyAxisMin=-2.0&IPM2H01.YPOSyAxisMax=1.0&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler=#a6cee3&IPM2C24A.XPOSyAxisLabel=2C24+X+(mm)&IPM2C24A.XPOSyAxisMin=-1.5&IPM2C24A.XPOSyAxisMax=-0.5&IPM2C24A.XPOSyAxisLog&IPM2C24A.XPOSscaler=&IPM2C24A.YPOSlabel=IPM2C24A.YPOS&IPM2C24A.YPOScolor=%231f78b4&IPM2C24A.YPOSyAxisLabel=2C24+Y+(mm)&IPM2C24A.YPOSyAxisMin=0.3&IPM2C24A.YPOSyAxisMax=1.3&IPM2C24A.YPOSyAxisLog&IPM2C24A.YPOSscaler=&IPM2H01.XPOSlabel=IPM2H01.XPOS&IPM2H01.XPOScolor=pink&IPM2H01.XPOSyAxisLabel=2H01+X+(mm)&IPM2H01.XPOSyAxisMin=-0.6&IPM2H01.XPOSyAxisMax=0.4&IPM2H01.XPOSyAxisLog&IPM2H01.XPOSscaler=&IPM2H01.YPOSlabel=IPM2H01.YPOS&IPM2H01.YPOScolor=darkred&IPM2H01.YPOSyAxisLabel=2H01+Y+(mm)&IPM2H01.YPOSyAxisMin=0.4&IPM2H01.YPOSyAxisMax=1.4&IPM2H01.YPOSyAxisLog&IPM2H01.YPOSscaler= BPM Positions]
 +
 
 +
== For REMOTE Shifts (offsite): ==
 +
* '''Zoom for 24-7 communication with counting house:'''  https://jlab-org.zoomgov.com/j/1619881100
 +
** Passcode REQUIRED: 927417
 +
* 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 <tt>clascss-remote</tt>.
 +
* [https://userweb.jlab.org/~baltzell/clas12/shift/remote-demo.mp4 Remote Demonstration Video (150 MB)]
 +
 
 +
==== 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! ====
  
 
= Monitoring =
 
= Monitoring =
Line 429: Line 405:
 
* [https://hallbopi.jlab.org/webopi3.3/w Hall B WebOPI] (CUE Login)
 
* [https://hallbopi.jlab.org/webopi3.3/w Hall B WebOPI] (CUE Login)
 
* [https://epicsweb.jlab.org Accelerator]
 
* [https://epicsweb.jlab.org Accelerator]
* [https://epicsweb.jlab.org/wave/?start=2022-09-18+11%3A56%3A22&end=2022-09-21+12%3A01%3A22&myaDeployment=ops&myaLimit=100000&windowMinutes=1440&title=&fullscreen=false&layoutMode=3&viewerMode=2&pv=B_DAQ%3AHEL%3A60m%3A29%3Aasycorr&pv=TGT%3APT12%3APolarization&pv=IGL1I00OD16_16&B_DAQ%3AHEL%3A60m%3A29%3Aasycorrlabel=Trigger+Asymmetry&B_DAQ%3AHEL%3A60m%3A29%3Aasycorrcolor=%230000cc&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisLabel=&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisMin=-0.025&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisMax=0.025&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisLog&B_DAQ%3AHEL%3A60m%3A29%3Aasycorrscaler=&TGT%3APT12%3APolarizationlabel=NMR+Polarization&TGT%3APT12%3APolarizationcolor=%23ff0000&TGT%3APT12%3APolarizationyAxisLabel=&TGT%3APT12%3APolarizationyAxisMin=-0.9&TGT%3APT12%3APolarizationyAxisMax=0.9&TGT%3APT12%3APolarizationyAxisLog&TGT%3APT12%3APolarizationscaler=&IGL1I00OD16_16label=Half-Wave+Plate&IGL1I00OD16_16color=%23b2df8a&IGL1I00OD16_16yAxisLabel=&IGL1I00OD16_16yAxisMin=&IGL1I00OD16_16yAxisMax=&IGL1I00OD16_16yAxisLog&IGL1I00OD16_16scaler= Polarizatin/Asymmetry Strip Chart on the web]
+
* [https://epicsweb.jlab.org/wave/?start=2022-09-18+11%3A56%3A22&end=2022-09-21+12%3A01%3A22&myaDeployment=ops&myaLimit=100000&windowMinutes=4000&title=&fullscreen=false&layoutMode=3&viewerMode=2&pv=TGT%3APT12%3APolarization&pv=IGL1I00OD16_16&pv=B_DAQ%3AHEL%3A60m%3A29%3Apol&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisLabel=&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisMin=-0.025&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisMax=0.025&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisLog&B_DAQ%3AHEL%3A60m%3A29%3Aasycorrscaler=&TGT%3APT12%3APolarizationlabel=NMR+Target+Polarization&TGT%3APT12%3APolarizationcolor=%23ff0000&TGT%3APT12%3APolarizationyAxisLabel=&TGT%3APT12%3APolarizationyAxisMin=-0.9&TGT%3APT12%3APolarizationyAxisMax=0.9&TGT%3APT12%3APolarizationyAxisLog&TGT%3APT12%3APolarizationscaler=&IGL1I00OD16_16label=Half-Wave+Plate&IGL1I00OD16_16color=%23b2df8a&IGL1I00OD16_16yAxisLabel=&IGL1I00OD16_16yAxisMin=&IGL1I00OD16_16yAxisMax=&IGL1I00OD16_16yAxisLog&IGL1I00OD16_16scaler=&B_DAQ%3AHEL%3A60m%3A29%3Apollabel=Trigger+Target+Polarization&B_DAQ%3AHEL%3A60m%3A29%3Apolcolor=%230000ff&B_DAQ%3AHEL%3A60m%3A29%3ApolyAxisLabel=&B_DAQ%3AHEL%3A60m%3A29%3ApolyAxisMin=&B_DAQ%3AHEL%3A60m%3A29%3ApolyAxisMax=&B_DAQ%3AHEL%3A60m%3A29%3ApolyAxisLog&B_DAQ%3AHEL%3A60m%3A29%3Apolscaler= Polarization Strip Chart on the web]
 +
 
 +
<!--* [https://epicsweb.jlab.org/wave/?start=2022-09-18+11%3A56%3A22&end=2022-09-21+12%3A01%3A22&myaDeployment=ops&myaLimit=100000&windowMinutes=1440&title=&fullscreen=false&layoutMode=3&viewerMode=2&pv=B_DAQ%3AHEL%3A60m%3A29%3Aasycorr&pv=TGT%3APT12%3APolarization&pv=IGL1I00OD16_16&B_DAQ%3AHEL%3A60m%3A29%3Aasycorrlabel=Trigger+Asymmetry&B_DAQ%3AHEL%3A60m%3A29%3Aasycorrcolor=%230000cc&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisLabel=&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisMin=-0.025&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisMax=0.025&B_DAQ%3AHEL%3A60m%3A29%3AasycorryAxisLog&B_DAQ%3AHEL%3A60m%3A29%3Aasycorrscaler=&TGT%3APT12%3APolarizationlabel=NMR+Polarization&TGT%3APT12%3APolarizationcolor=%23ff0000&TGT%3APT12%3APolarizationyAxisLabel=&TGT%3APT12%3APolarizationyAxisMin=-0.9&TGT%3APT12%3APolarizationyAxisMax=0.9&TGT%3APT12%3APolarizationyAxisLog&TGT%3APT12%3APolarizationscaler=&IGL1I00OD16_16label=Half-Wave+Plate&IGL1I00OD16_16color=%23b2df8a&IGL1I00OD16_16yAxisLabel=&IGL1I00OD16_16yAxisMin=&IGL1I00OD16_16yAxisMax=&IGL1I00OD16_16yAxisLog&IGL1I00OD16_16scaler= Polarizatin/Asymmetry Strip Chart on the web]-->
  
 
| valign=top |
 
| valign=top |
 
===Live Monitoring Links===
 
===Live Monitoring Links===
 
*[https://clas12mon.jlab.org/rgc CLAS12 Monitoring Timelines]
 
*[https://clas12mon.jlab.org/rgc CLAS12 Monitoring Timelines]
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge.html Live Charge Collected Plots for FToff]
+
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge.html Live Charge Collected Plots for FTon '23]
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge_r12.html Live Charge Collected Plots for FTon]
+
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge_r12.html Charge Collected Plots for FTon '22]
 +
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_progress_charge_r3.html Charge Collected Plots for FToff '22]
 
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_target_illum.html Total Charge on Target Plot]
 
*[https://clasweb.jlab.org/clas12online/timelines/rg-c/RGC2022_target_illum.html Total Charge on Target Plot]
 +
*[https://clasweb.jlab.org/hydra/HydraRun.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox!
  
 
<!--
 
<!--
Line 458: Line 438:
 
* [https://clasweb.jlab.org/wiki/index.php/Run_Group_C Run Group C Analysis Wiki]
 
* [https://clasweb.jlab.org/wiki/index.php/Run_Group_C Run Group C Analysis Wiki]
 
* [http://clasweb.jlab.org/rcdb RCDB]
 
* [http://clasweb.jlab.org/rcdb RCDB]
 +
* [https://clas12mon.jlab.org/mon12/histograms/?reference=4130409 All monitoring histograms: reference, current, and 5 most recent runs]
 
* [https://clas12mon.jlab.org/ CLAS12 mon page]
 
* [https://clas12mon.jlab.org/ CLAS12 mon page]
* [https://clas12mon.jlab.org/mon12/histograms/?reference=4040785 Comparison between mon12 histograms (last 5 runs plus reference run)]
 
 
* '''[https://clasweb.jlab.org/wiki/index.php/RG-C_RC_and_Target_Expert_Volunteers Run Coordinators and Target Experts Instructions and List]'''
 
* '''[https://clasweb.jlab.org/wiki/index.php/RG-C_RC_and_Target_Expert_Volunteers Run Coordinators and Target Experts Instructions and List]'''
  
Line 476: Line 456:
 
* [https://cebaf.jlab.org/pd/run-coordinator-reports Run Coordinator Reports]
 
* [https://cebaf.jlab.org/pd/run-coordinator-reports Run Coordinator Reports]
 
* [https://accweb.acc.jlab.org/btm/reports/physics-summary Beam Time Accounting Reports]
 
* [https://accweb.acc.jlab.org/btm/reports/physics-summary Beam Time Accounting Reports]
 +
* [http://opsweb.acc.jlab.org/CSUEApps/PSSestamp/psslog.php PSS Elog]
  
 
| valign=top |
 
| valign=top |
Line 482: Line 463:
 
* 08:00 [https://jlab-org.zoomgov.com/j/1601304841?pwd=Z1RIOVVUdkdXL2R2LzREZUNOUlh1dz09 MCC/OPS Morning and Wednesday 1:30 Meeting]
 
* 08:00 [https://jlab-org.zoomgov.com/j/1601304841?pwd=Z1RIOVVUdkdXL2R2LzREZUNOUlh1dz09 MCC/OPS Morning and Wednesday 1:30 Meeting]
 
* [https://logbooks.jlab.org/entry/4000274 See also this log entry]
 
* [https://logbooks.jlab.org/entry/4000274 See also this log entry]
* 14:00 Daily RC Meeting  
+
* (Week-)Daily RC Meeting  
 
** [https://jlab-org.zoomgov.com/j/1608674253?pwd=SFZyYmZLWXJieGtpV2dEdVRiUEJnUT09&from=addon Zoom Link]
 
** [https://jlab-org.zoomgov.com/j/1608674253?pwd=SFZyYmZLWXJieGtpV2dEdVRiUEJnUT09&from=addon Zoom Link]
 
** Meeting ID: 160 867 4253
 
** Meeting ID: 160 867 4253
 
** Passcode: 786506
 
** Passcode: 786506
** [https://clasweb.jlab.org/wiki/index.php/RGC_RC Meeting Agendae]
+
** [https://clasweb.jlab.org/wiki/index.php/RGC_RC Meeting Schedule and Agendae]
  
 
|}
 
|}

Latest revision as of 13:41, 25 July 2024

[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/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 the current page to force a refresh.


CLAS12 Run Group C

Run Coordinator: Mohammad Hattawy (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 (FTon Portion Part 2)

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.
* 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 shifts, 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 
** find latest pitfalls and known issues under GENERAL INFORMATION
* 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

Short Term Schedule for the Week from Wednesday, March 15th, to Monday March 20th, 2023

  • Current: 4 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.
  • 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 beam raster on.
    • 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 "FTon"
  • If HWP is changed, start a new run

PLAN for March 15-20, 2023

Note: an hour before changing the HWP, call Bill Henry (from Hall A) at 215-908-2245. He offered his help in optimizing the beam charge asymmetries when changing the HWP. He will stop by the counting house and run his code, which will take a minute. We will do the HWP changes during the day shifts.

  • Wednesday, March 15th: Beam study downtime starts at 8:00 AM. Beam is expected to be back by 15:00 PM. If they beam shows up before 22:00 PM, we will need to take a Moller run. Then, start taking data on ND3(+) (torus outbending, 4nA beam current, HWP IN).
  • Thursday, March 16th: Data taking on ND3 (+) (torus outbending, 4nA, HWP out)
  • Friday, March 17th: anneal the target and flip the polarization to negative. Will take about 3 hours starting around 9AM. Then, take data on ND3 (torus outbending, 4nA, HWP out)
  • Saturday, March 18th: Continue taking data on ND3(-) (torus outbending, 4nA, HWP IN)
  • Sunday, March 19th: Will change the target to C sometime in the day shift and start taking data. Will go to restricted access and will organize this between RadCon and Target Experts.
  • Till Monday, March 20th, 07:00 AM: Continue taking data till the beam goes away.
  • When the beam goes away:
  1. Turn all HV OFF except SVT and BMT. For FT we turn HV OFF, but keep the chiller and LV ON, Raffaella will do some LED calibrations.
  2. Solenoid will remain ON for the target group to do NMR studies.
  3. The torus should be ramped down. Morgan or Denny can do it if they are around at that time, or call Eugene and he do it.
  4. The hall should go to controlled access awaiting for radcon to come and do a full survey for restricted access.
NOTES: 
* Watch the beam positions (and thus the midstream halo counters) closely and ask MCC to adjust the positions if they are (on average) >=0.1mm off.
* Remember, the hall will only be dropped in controlled mode once someone goes downstairs and enters the hall. You/RadCon should do that right away after calling MCC. 

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 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. 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 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 set-point of 2416.4 A results in the read back 2419.23 A and exactly 5.00 T field on center

Raster settings (current as of February 9, 2023)

  • x: Vpp = 2.7 V, offset = 0.0
  • y: Vpp = 2.05 V, offset = 0.50 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 (current as of February 9, 2023)

  • 2C21A, X = -0.4 mm, Y = +0.6 mm
  • 2C24A, X = -2.0 mm, Y = +0.6 mm
  • 2H01, X = -1.0 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.

see below for Known Detector Issues

General Information

  • To open CS Studio interface, type "clascss" in some terminal.
  • 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.
  • 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 beam raster on.
  • 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.
  • 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:
    • rastermon should be using ET on clondaq6
      • this means startup of rastermon via command line: rastermon --et --host clondaq6
    • 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.
  • Holes in CND occupancies: CAMAC CFD crate was turned off/on for some reason. You need to run the script to set the thresholds for CND CFDs. Go on a clondaq machine and type cnd-cfd-thresh -w 0. Or call the CND phone if this doesn't work.
  • 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.

Known Issues

FTT alarms - can be ignored (we do not have the FTT installed)

Fr 11 Nov 2022 ECAL PMT_SEC2_WO8 HV is disabled https://logbooks.jlab.org/entry/4080950

Follow-up Re: RICH tile 21 in sector 1 is dead. Working without one tile out of 276 for a moment https://logbooks.jlab.org/entry/4079453

Run #17396: RICH lost three scalars https://logbooks.jlab.org/entry/4079190

Tuesday, February 7, 2023: BMT Sector 2 Layer 5 is broken (HV set to 200 V)

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
    • Run Plan, DAQ Configuration, and References and Standards
    • also check tab GENERAL INFORMATION
  • 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.
      • If the NMR display is frozen or disappears, here are the steps to follow:
        • Open a new terminal window on the bottom right-most screen.
        • Type "ssh clasrun@clonsl1"
        • Type "nmr-vnc”
        • Click "Run" under "NMR Controls" - the window should now be updating (blue bar moving)
      • 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.

Shift Worker Tasks

  • Check the information in the Short Term Schedule and GENERAL INFORMATION, 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


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
    • Helicity Asymmetry Strip Charts - see [10] for an example. Also read and follow the instructions below under "Log the Strip Charts".
  • 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: [11]. 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 -> DAQ -> Helicity-Latched Trigger GUI Screen -> click on "Menu" -> myaPlot (not accessible remotely) -> Choose "load config time axis: start: -12 hours end: NOW" and click "accept"
      • Example
      • Choose reasonable y / x axis ranges: R-click on the axis -> Modify (axis-name) Axis
      • For the y axis in the bottom panel, choose the NMR polarization and a reasonable range for the y axis (always from 0 to some maximum value), same for the 60-min trigger bit polarization. Those two do NOT have to have the same scale - it is better to try to get the dark blue and red curves to lie on top of each other (more or less).
      • Set the time axis auto-update. ">>" symbol will appear below the time axis when this is activated. (Right-click on X axis ->" [A] 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