Run Group K
Jump to navigation
Jump to search
[edit]
- General
- Phone Numbers
- Short Term Schedule
- GENERAL INFORMATION
- Shift Expert
- Shift Worker
- Run Coordinator
- Monitoring
- Important Links
GeneralLogbookShift ScheduleRun Coordinator ScheduleESAD, COO, RSADShift ChecklistBeam Time AccountingHot Checkout |
ManualsSystemsDetectorsSoftware |
Procedures
Logbooks
|
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
- 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 to Edit solely this tab. P.S.: You must click on the top Edit, next to Read, followed by "Save changes" to force the current page to refresh.
Experiment Coordinator: Annalisa D'Angelo
Run Coordinator: Daniel Carman (757) 575-7540
PDL: Daniel Carman (757) 876-1789
Important Notes
Do NOT change FSD settings without approval from RC or beamline expert!
In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House and inform the Crew Chief and RC.
In case of evacuation of the Counting Room (e.g., due to a fire alarm), grab the shift expert phone and leave the room through the "EXIT" door leading to the parking lot. Do not leave through the hallway! Call the RC once outside so the latter will call MCC to turn the beam OFF to Hall B and inform other Hall B staff members.
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 to arrange replacements.
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 "Shift Worker" tab, as you need some lead time to set up!
Note to Shift Takers:
- Read the ESAD, COO, RSAD, and ERG documents found on the "Current RG-K Run Info" as well as the yellow folder in the counting room. Before you start your first shift on the current experiment, you must sign on the list in the yellow folder. Thereby, you confirm that you have read and understand their content.
- Read at least the previous 24 hours logbook entries to be aware of recent run details and changes
- Arrive at least 10 minutes early for shift change
- If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.
- Refresh the run wiki page/tabs; look over it/them every shift
- Follow the Shift Expert/Worker tab's instructions
- Do not spend more than 15-20 min trying to fix a problem. In case of any issue, contact the On-call Experts or the RC.
See tab GENERAL INFORMATION for
- Recent Changes
- Current Issues
- Beam Restoration (for beam restoration procedures and Møller runs)
Run Plan: Mar. 10 - Mar. 11, 2024
Production Running ... to the end!!
- DAQ configuration: PROD67, Trigger: rgk_noDC_v1.1_300MeV.trg - Beam current request: 75 nA - Run duration: 3 hrs
Note: RG-K run ends on Mar. 11 at 7 a.m.
- Turn all detectors off and put BMT HV in safe mode - Ramp torus and solenoid to zero field (contact Eugene to do this) - Call to put Hall B in Restricted Access
Related Information
Find detailed information at tab "GENERAL INFORMATION".
- The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF during run time.
- Orbit locks are on BPMs 2C24A and 2H01 and the locks should generally be on ("Running").
- Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
- The beam position at 2C21A is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.
- The beam position at 2C21A is important for initial beam tuning (on tagger dump).
- If HWP is changed, start a new run. The absolute values of the SLM and FCUP charge asymmetry (Q-Asym (%)) should be less than 0.1%.
- Beam tuning and Møller runs
- Generally, Detector HV OFF but
- SVT: LV ON; HV OFF, and MVT: LV ON; HV ON - Safe Voltage
- Turn DC HV off only for beam tuning
Access to the Hall
- If you need to enter Hall B, alert Denny Insley (757-897-9060, cell/text: 757-810-9576) and the Run Coordinator (757-575-7540).
- Check in with the shift personnel before entering the hall.
DAQ Operation & Related Information
|
NEW STANDARD end and start of the run:
This will ensure proper compression of the FADCs and therefore a smaller data rate and perform a RICH recovery. Restart DAQ
|
|
Triggers files
| rgk_noDC_v1.0_300MeV.trg | DC roads are not in the trigger. Hold off time is 3 us. |
| rgk_noDC_v1.1_300MeV.trg | DC roads are not in the trigger. Hold off time is 2 us. |
| rgk_noDC_v1.2_300MeV.trg | DC roads are not in the trigger. Hold off time is 1 us. |
| rgk_out_v1.1_300MeV.trg | Outbending DC roads, Hold off time is 2 us. |
Reference Values
FSD Thresholds
- Upstream: 2 kHz
- Midstream: 2 kHz
- Downstream: 100 kHz
- BOM: 50 kHz
- 5 ms dwell time
Nominal Beam Positions
2C21A (not important for production)
- x = -0.4 mm
- y = +0.7 mm
2C24A
- x = -1.7 mm
- y = +0.5 mm
2H01
- x = -0.7 mm
- y = +0.6 mm
8.5 GeV Harp Scan References (Feb. 14, 2024)
2C21A: https://logbooks.jlab.org/entry/4252495
Tagger (2C24A): https://logbooks.jlab.org/entry/4252496
2H01: https://logbooks.jlab.org/entry/4252514
6.4 GeV Harp Scan References (Jan. 18, 2024)
2C21A: https://logbooks.jlab.org/entry/4240375
Tagger (2C24A): https://logbooks.jlab.org/entry/4240378
This tab contains information on
- Recent Changes
- Current Issues
- Beam Restoration
Recent Changes
New MVT LV Reboot Procedure
See https://logbooks.jlab.org/entry/4217011 for detailed information on rebooting the MVT LV when observing a drop in BMT strip occupancies. This gets done upon request of DAQ or MVT expert only.
- Turn LV OFF from MVT Overview->Low Voltage->MVT-All. LV status indicators should change from green to black;
- Wait 20 seconds, then turn LV back from the same menu.
- In the alarm handler, with a 2-minute alarm delay, there can be an alarm "NActiveCrates", the status is also seen on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON.
- Reboot mvt1, mvt2, and mvt3 ROCS.
- Start a run with restart DAQ (Cancel → Reset → Configure → Download → Prestart → Go).
- If we have beam, and a reboot process takes more than 5 min, call the DAQ or MVT expert.
RICH issue
- Do not interrupt an otherwise good run on account of RICH (missing tiles).
- Make a logbook entry with screen shots of the RICH temperature and scaler screens, notify the RICH expert (vpk@jlab.org).
- If the DAQ did not crash continue data taking. (See https://logbooks.jlab.org/comment/48141#comment-48141 for a nice explanation of the new procedure which should prevent the DAQ from crashing.)
- For the next run, "restart DAQ".
- If you still see dead RICH tiles in the temperature or scaler maps.
- Make another logbook entry with screenshots,
- Do a RICH recovery after the run.
- If it did not help call the RICH expert, between runs.
- Remember to "restart DAQ" for the next run after recovery.
Rapid/Controlled Access to the Hall
- Ask MCC to stop the beam. Wait for the beacon to stop flashing (15-20 minutes) before access. Rapid access is controlled access without RadCon.
- After higher beam current or a Moller run, the beacon will not stop flashing anytime soon. Then, escorted access, viz the ARM, is needed. In that case, keep the beam until the ARM arrives at the Counting House.
24/7 ZOOM connection for Counting House
- Click on https://jlab-org.zoomgov.com/j/1618614939, included in "Remote Shifts" in tab "Shift Worker"
- choose the option to "join from browser" (Chrome is recommended) and ignore all other messages to update the ZOOM APP in the pop-up windows,.
- Enter the passcode from the logbook entry in tab "Shift Worker"
Current Issues
Lights in the Hall
The main lights in the Hall (dome lights) and the Forward Carriage lights must be OFF because of light leaks of some of the detectors. If these lights are switched on during an access, they should be switched off when leaving the Hall.
- Refer to these photos: ON: [1], OFF: [2]
- We have a new dome light switch outside of the hall in the labyrinth. See logbook entry: https://logbooks.jlab.org/entry/4204460
- When the dome lights are switched off, they cannot be turned back on immediately, they require 10-15 min to cool down.
Beamline
- Orbit locks are on BPMs 2C24A and 2H01 and the locks should generally be on ("Running").
- Beam positions at 2C24A and 2H01 have to be kept, within ±0.1mm, at the nominal beam positions listed below ("Reference Values").
- The beam position at 2C21A is not important for production runs but should be stable. Here, significantly drifting positions can indicate instabilities in beam energy.
- The beam position at 2C21A is important for initial beam tuning (on tagger dump).
- After the HWP change
- The absolute values of the SLM and FCUP charge asymmetry (Q-Asym) should be less than 0.1%. If they are not, contact the Beamline Expert.
- Start a new run
- Tagger Magnet Procedure: If the tagger magnet needs to be turned off, tell the operator to ONLY use the script for degaussing, NEVER do it "by hand"! The latter method might/will trip the circuit breaker for the power supply in the Hall.
BMT/SVT
- If new hot channels appear, call the SVT/MM expert Yuri Gotra (757-541-7539). These channels need to be addressed by the expert.
- BMT HV trips: no screenshots are necessary, power-cycle the channel HV as fast as possible (the underlying script will take care of ramping it up), note the trip and sector/layer in the shift summary. If the same channel trips frequently, ask the expert on call for guidance.
- BMT S1L5 strip is OFF
DAQ
- Some ROCs keep printing error messages while functioning properly; please see their list in this logbook entry # 4215299 to avoid unnecessary reboots since the printout in the ROC terminal won't change. The message will appear in the DAQ run control if they get disconnected!
- NEW STANDARD end and start of the run: End run, Cancel, Reset, Download , Prestart, Go. This will ensure proper compression of the FADCs and therefore a smaller data rate.
DC
- Make sure to log every DC trip in the shift summary. Make sure to list WHERE and why, possibly, the trip occurred.
ECAL/PCAL
- "ECAL_SEC6_UO26 Noisy" https://logbooks.jlab.org/entry/4241957
FTOF
- FTOF S2 Paddle 19-left and S4 Paddle 16-left are known to be "weak" channels that tend to come and go depending on torus polarity and rates. This cannot be fixed during this run period; see https://logbooks.jlab.org/entry/4219555 and https://logbooks.jlab.org/entry/4219876.
RICH
- RICH Sector 1 has three missing tiles; this is known, and no action is required from the shifters.
Beam Restoration
- Study the manual: Establishing Physics-Quality Beam. If you do not feel confident to do this by yourself, contact the Beamline Expert.
Restoring Beam after Short Downtime
- Ask for 5 nA beam current and check the 2C24A and 2H01 beam (x, y) positions against the Reference Values (tab "Short Term Schedule") after
- beam steering or orbit change
- change in beam current, e.g., after a target change
- If BPM 2C24A and 2H01 positions are off, (not within +/-0.1 mm), ask MCC to bring them to the reference values, see run wiki tab "Short Term Schedule"
- The beam position at 2C21A is not important for production
Beam Tuning to Tagger Dump
- Study the manual: Establishing Physics-Quality Beam, and take into account the first steps mentioned therein.
- ◊ Make sure the BMT along FMT is in SAFE mode, SVT HV is OFF, (LV is ALWAYS ON), and all other CLAS12 detectors HV are OFF.
- A few points to note:
- • Change the beam type to "Photon" from the "BTA Config"
- • Ask MCC to energize the tagger magnet
- • Move the collimator to the Blank position after the tagger is energized
- • Ask MCC to mask the beam halo counters (FSDs: Upstream, Midstream, Downstream, BOM)
- • Ask MCC for 5 nA beam current and make sure the Orbit Locks are OFF;
- • Check the 2C21A and 2C24A beam positions (x, y) against the Reference Values (tab "Short Term Schedule")
- - If the beam positions are OFF, ask MCC to bring them to the reference values.
- • In case the two BPMs (x, y) positions look good, take a harp scan (HS) at Harp 2C21 (Upstream Right Counter) and Tagger Harp (2C24; Upstream Right Counter):
- - It should be noted that the beam must be ON during the scan. Once OFF, abort and restart once the beam is back.
- - Compare the results with the HS References (run wiki tab "Short Term Schedule") and bear in mind that the fit ranges might need to be adjusted manually to assess the fit results;
- - If good, log the new scan results.
Møller run
Follow the standard procedure as described in the manual Performing Møller Runs.
A few points to note:
- Request 20 nA , Orbit Locks should be OFF;
- The BPMs 2C21 and 2C24A may be out of range after the Møller configuration.
- Keep running until the polarization uncertainty is < 1.5%
Beam Tuning to Faraday Cup
Study the manual: Establishing Physics-Quality Beam, and take into account the first steps mentioned therein. This is typically done after tuning to the tagger dump (and possibly taking a Moller run).
A few points to note:
- Change the beam type to "Electron";
- Ask MCC to de-energize the tagger magnet, which includes degaussing the tagger magnet and turning the power supply OFF;
- Ask the operator to use the script only, not try it by hand, as this might trip the circuit breaker of the tagger magnet power supply.
- (If initial beam tune, target should be "Empty")
- Make sure the Beam Blocker is OUT
- Move the collimator to the 20 mm position
- Ask MCC to unmask beam halos
- Set the halo counter FSD thresholds to 1 MHz and the integration time interval to 50 milliseconds
- Insert the Downstream Viewer, Chromax, in the beamline
- Ask MCC for 5 nA beam current
- If the 2C24A and 2H01 beam positions are OFF, ask MCC to bring them to the reference values (see run wiki tab Short_Term_Schedule)
- In case the BPM (x, y) positions look good, take a harp scan at 2H01 (Midstream Left)
- The beam must be ON during the scan. Once OFF, abort and restart once the beam is back
- Compare the results with the harp scan references (see tab Short_Term_Schedule)
- If good, log the new scan results.
Once done and before resuming the production data-taking:
- Retract the Downstream Viewer from the beamline;
- Put the FSDs thresholds and integration time to their reference values;
- Turn all detector HV ON, for MVT "HV ON - Full Voltage";
- MCC might need to adjust the beam positions after going to the production beam current.
Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.
- If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.
Follow the Short Term Schedule
- The RC must be notified before changing run conditions
Operate the Data Acquisition
Take action on and log alarms
At the end of the shift, submit the strip charts to the logbook
- If they are not up already: (CS-Studio → Tools → Strip Charts → livePlot)
- Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"
- Choose a time-span width of 10 hours (right-click below x-axis)
- Enter reasonable y-ranges where necessary
- To make a logbook entry:
- - Right click within the grid of one of the charts, choose "Make Logbook Entry"
- - The title of the logbook entry can be changed, eg to Strip charts
- - Un-click ELOG, select HBLOG, and click on "Make Entry" to submit
Communicate with your co-shift person:
- Remind them to read the tab 'Shift Worker'.
- Discuss any issues with the shift worker before making extra logbook entries.
- Remind the shift worker of the end-of-shift Checklist.
- Use the Logbook entry tool for all screen shots (but the strip charts)!
Check for and read any comments to log-book entries made during your shift.
Keep your shift summary up to date in HBLOG. Record all significant happenings.
- Refer to relevant logbook entries in the shift summary.
- Include a run list for the shift with relevant run information.
Ensure that all monitoring plots are logged and checked against the reference plots for every single run.
- Both, you and the shift worker should run mon12 and reset & check spectra frequently.
- If the worker shift is remote, maintain communication over Zoom.
- If you have any other questions or uncertainties about what to do, call the RC.
In case of RICH alarm, see tab 'GENERAL INFORMAION'.
New MVT LV Reboot Procedure can be found at tab 'GENERAL INFORMAION'.
Fill out BTA hourly;
- Accelerator beam time (do not change these values):
- ABU: acceptable beam used
- BANU: beam acceptable but not used (should be reflected in our PCC and UED)
- BNA: beam not acceptable (e.g., tuning, drifting, not focused)
- ACC: Accelerator Configuration Change (e.g., pass change)
- OFF: Accelerator is down
- Experiment beam time (do change these values):
- ER: Experiment ready (should be 60 minutes - PCC - UED)
- PCC: Planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, etc.)
- UED: Unplanned experiment down (hardware failure, DAQ crashes, our problems, ...)
- Exception: BANU, due to time spent on beam tuning and BPM checks after beam down, should be counted as ER on our side.
- Enter fields at the "Shift Information" tab.
- You must save at 7:00, 15:00, and 23:00, to send info to MCC. To see the save button, click 'edit all' or 'edit cc hours.'
- Acknowledge the popup error message about the last hour not being completed by clicking OK.
- Sign, viz log completed 8-hour sheet.
- Note: we can change the time sheet up to 48 hours after completion.
Come to your shift in time for the shift change, 10-15 minutes before the start of your shift;
- If it is your first shift or a shift after a long pause, do shadow an earlier shift for at least 4 hours to familiarize yourself with all shift duties and technicalities of the ongoing experiment.
Discuss any issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary.
Use the Logbook entry tool for all screen shots (but the strip charts)!
Frequently
Reset and check non12 histograms frequently, preferably each 1h
- Note that some plots have radio buttons at the bottom to choose the sector. Remember to cycle through and check all sectors.
Once per run
Using the CS-Studio Logbook Entry tool, submit EPICS screenshots to the HBRUN logbook (one logbook entry) with beam ON
- Beamline overview (remote shift: in VNC or Web Browser)
- DAQ status
- CLAS12 trigger rates
Upload mon12 monitoring plots to the logbook with sufficient statistics and compare them to the reference and recent uploads (see Monitoring tab).
At the end of the run, submit the strip charts to the logbook
- If they are not up already: (CS-Studio → Tools → Strip Charts → livePlot)
- Right click within the grid, choose "Load a Configuration", select "Beamline4Logbook_visibleHaloCounters"
- Choose a time-span width compatible with the run duration (right-click below x-axis)
- Enter reasonable y-ranges where necessary
- To make a logbook entry:
- - Right click within the grid of one of the charts, choose "Make Logbook Entry"
- - The title of the logbook entry can be changed, eg to Strip charts
- - Un-click ELOG, select HBLOG, and click on "Make Entry" to submit
Once per shift
Fill the shift checklist;
- During production, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status and CLAS12 Trigger;
- During extended downtime, get relevant values from the latest EPICS screenshots that you made during production
Upload by the end of the shift while data is being collected clas12online plots to the HBLOG logbook, with sufficient statistics
- Please refresh the clas12online program at the beginning of your shift in case the previous shift does not do it after uploading the snapshots. Also, do that while the DAQ is running!
- Note that the program must also be restarted after each DAQ crash!
For Remote Shifts
Please inform the PDL that your shifts will be remote. Remote shifts are listed here
You must test your setup, including Zoom and VNC connections, at least 24 hours before your first shift!
- Zoom for 24-7 communication with counting house:
- In the Zoom app: https://jlab-org.zoomgov.com/j/1618614939
- Or in a web browser: https://jlab-org.zoomgov.com/wc/1618614939/join?pwd=U003MnRuNVdiU1EzaFpXV0JuNWV1Zz09
- The passcode is required and contained in this log entry
- Remind the expert in the counting house to restart their ZOOM, if necessary
- Remote VNC connection instructions: https://logbooks.jlab.org/entry/3906039
- If you mistyped (username, pincode, passcode,...) a string of numbers will appear with text asking you to respond to this challenge. Back out with ctrl_c and you get another try! After N+1 mistypes you will be locked out. For several hours after that you will not even be able to get to the public JLab webpages.
- All necessary applications should be available 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.
- Some charts are also accessible via web browser: Upstream/Midstream Halo Counters, Downstream Halo Counters, Beam Currents, BPM Positions
Check the upcoming shifts, and if necessary, coordinate with the PDL to contact shift takers about their training and site access status.
Remote shifts are listed here.
Backup shift personnel is listed here.
Daily
Attend the in-person PD/RC and MCC/OPS meetings (7:45 AM and 8 AM Daily). The PD will communicate when and how meetings happen on the weekend.
- See the ZOOM connection info under Important Links tab.
Update the run plan in the Short Term Schedule tab in coordination with the RG-K experiment coordinators (i.e., Annalisa, Daniel) and communicate it to the shift crew.
Log the RC summary in the HBLOG.
Update the list of runs taken on the Google Spreadsheet
Send a daily invitation for the RC meeting to mailing lists hallb, clas12_rgk, clas_members.
Run the daily RC meetings in CH Room 200C and on ZOOM
- Mo-Tu,Th-Fr at 13:00 ET in the Counting House Conference Room
- Wednesdays at 3 PM, zoom only
- Weekends upon agreement
- Keep the Daily RC Meeting Minutes at Run_Group_K wiki, tab "RGK FALL 2023 / SPRING 2024"
Connect to Zoom in CH Room 200C:
- Turn on the projector with the white remote control, then log into your CUE account. If not listed yet, click "Not listed?" in the bottom left to add your account.
- Once logged in, use the recommended Google Chrome to join the ZOOM meeting on the browser or use the ZOOM application.
- Since the room doesn't have audio, don't connect with the computer audio, but choose "Call Me," then enter the number in the small Cisco answering device. Once it rings, answer the call, and you will be prompted to join the meeting.
- The room has a camera, which can be turned on via ZOOM.
Weekly
MCC/OPS planning meeting is in person, on Wednesdays at 13:30, MCC building.
- Submit (save) the online form Run Coordinator Weekly Summary before the meeting and present the contents at the meeting.
- The summary covers the data taking status from 7 am on the previous Wednesday to 7 am on the current Wednesday.
- The beam time accounting can be retrieved from:
- OPS logbook entries with tag 'Beam Accounting': Timesheet Summaries
- Beam Time Manager; Physics Time Accounting
- To calculate the percentage of scheduled experiment hours to date contact Daniel Carman.
- The total experiment data collected to date could be retrieved from the up-to-date "Accumulated Charge" depicted at [3]
Hall B meeting is on Mondays at 9 AM. Present your summary slides that should be sent beforehand to the Hall B leader, Patrick Achenbach.
Webcams
|
EPICS |
Data Quality
|
Hall-B |
Accelerator |
ZOOM Meetings
|
|
|
