Difference between revisions of "Run Group C"
Jump to navigation
Jump to search
| Line 130: | Line 130: | ||
=== PLAN for Saturday-Swing (10/1/2022) to Monday-OWL (10/3/2022) === | === PLAN for Saturday-Swing (10/1/2022) to Monday-OWL (10/3/2022) === | ||
| − | * Take production data on CH2 start with IN configuration. Use | + | * 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 | + | * Somewhere around noon (Sunday-Day shift). Flip the beam into OUT configuration. Still use PROD66 configuration (Do not use PIN configuration) |
* Continue the OUT configuration until the next day (Target swap or further notification) | * Continue the OUT configuration until the next day (Target swap or further notification) | ||
Revision as of 23:08, 1 October 2022
[edit]
- Shift Documentation
- Phone Numbers
- Short Term Schedule
- Shift Expert
- Worker Shift
- Monitoring
- Useful Links
Shift ScheduleHall B LogbookESAD, COO, RSAD
Shift ChecklistHot CheckoutBeam Time Accounting
|
Manuals
|
Procedures |
JLab Logbooks
|
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
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- 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, Summer 2022
Daily RC Meetings at 14:00: CH Room 200C, and on Zoom
Zoom information: Link, Meeting ID: 160 867 4253, Passcode: 786506
Run Coordinator: Zulkaida Akbar
- (9-)757 575-7540
PDL: Eugene Pasyuk
- (9-)757 876-1789 , x6020 office
Run Group Coordinator: Sebastian Kuhn
- (9-)757 639-6640
Run Coordinator and Target Expert Schedule
Longterm Run Plan
IMPORTANT SHIFT NOTES:
- In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House
- If you have symptoms or a positive COVID test, do NOT come to your shift - instead, inform the PDL and the RC and JLab medical services immediately so that replacements can be arranged.
- If needed, worker shifts can 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!
Run Plan: September - December 2022
GENERAL INFORMATION
- 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.
- 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:
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
SHORT RANGE PLAN (last update September 27, 2022)
- 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).
- 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.
- 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.
- 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 Monday-OWL (10/3/2022)
- 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)
- Continue the OUT configuration until the next day (Target swap or further notification)
5-pass (10.55 GeV) Running conditions
- Torus at 100% current, inbending electrons. Setpoint = +3770 A (Readback = +3766 A)
- Solenoid setpoint +2417.5 A
DAQ configuration
- Configuration PROD66/PROD66_PIN, trigger file rgc_300MeV_v2.3_Q2_1.5GeV2.trg
- NOTE: UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to do a RICH recovery - instead do this in between runs.
- NOTE: BOTH the shift expert AND the shift worker MUST check and reset monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems.Watch the raster pattern!
- At the end of each run, follow the STANDARD DAQ RESTART SEQUENCE:
- "end run".
- If the run ended correctly and you will run with the same configuration and trigger file, then: "prestart", "go"
- If you are changing configuration (between PROD66 and PROD66_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 19 Sept. 22
Solenoid set-point of 2417.5 A results in read back 2419.57 A and exactly 5.00 T field on center
Raster settings
- x: Vpp = 3.7 V, offset = -0.65 V
- y: Vpp = 3.25 V, offset = -0.10 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
- 2H01, X = -1.9 mm, Y = +1.2 mm
- 2C24A, X = -2.0 mm, Y = +0.6 mm
- 2C21A, X = -0.4 mm, Y = +0.6 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
- 5 ms dwell time
Reference plots and histograms
- Harp Scans for Beam on Faraday Cup, 2H01 [1], more recent scan (3 Sept 2022): [2]
- Harp Scans for Beam on 2C21 [3], more recent scan (3 Sept 2022): [4]
- Harp Scan on Tagger Dump (3 Sept. 2022) [5]
- Monitoring Histograms (18 Sept 2022) [6]
- RasterMon (18 Sept 2022) [7]
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.
Known issues
- PCAL W strip 55 sector 6
- 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.
|
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.
(remote) shift worker: see dedicated Worker Shift tab above. |
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 clascss-remote.
- Remote Demonstration Video (150 MB)
Shift Worker Tasks
Make the following log entries ONCE per run
- Screenshots: submit to logbook only if you capture the information with beam ON
- Beamline Overview, in VNC or Web Browser
- CLAS12 Trigger rates and DAQ status
- Beam current and position strip-charts
- RGC Polarized Target GUI - under Beamline on CSS
- The new Helicity Trigger Asymmetry strip-chart (example https://logbooks.jlab.org/entry/4041939).
- 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. 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): inspect all monitoring histograms and carefully compare them to the corresponding reference histograms: reference, current, and 5 most recent runs. 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: [8]. 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 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).
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.
- Log the strip charts in time intervals according to the x-axis time span.
- How to get the strip charts:
- For the beam: CS-Studio -> Beamline -> Strip Charts.
- NEW!!! For the helicity trigger asymmetry strip chart: Menu at Helicity-Latched Trigger GUI Screen -> Menu -> livePlot (not accessible remotely)
- right-click on the screen and select "Make Elog Entry", make sure to log to HBLOG and not ELOG
- You can also see beam charts in the Web Browser: Upstream/Midstream Halo Counters, Downstream Halo Counters, Beam Currents, BPM Positions
Webcams
|
Manuals |
Epics on the web |
Live Monitoring Links |
Hall-B
|
Accelerator |
ZOOM meetings
|
|
|
