Run Group D
- General
- Phone Numbers
- Short Term Schedule
- General How-to
- Run Coordinator
- Shift Expert
- Shift Worker
- 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.
Run Coordinator: Lamiaa El Fassi (757) 575-7540
PDL: Nathan Baltzell (9-) 757 876-1789; Office: x5902
RG/Analysis Coordinator (AC): Lamiaa El Fassi (630) 605-4259
Daily RC/OA Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1611984219; Passcode: RGD-RC23), except on Wednesdays, which is on ZOOM ONLY @ 15:30 due to the conflict with the 13:30 MCC Scheduling/Planning meeting.
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-D 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;
- ◊ Refresh the runwiki 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.
- ◊ Review these important links:
- - Recent Changes and Current Issues
- - General How-to for beam restoration procedures and Møller runs.
Run Plan, Thursday, Dec. 14th - Friday, Dec. 15th, 2023
P.S.: If the beam is widely fluctuating above 105 nA, constantly overshooting over 105 nA on 2C21A, please ask MCC to narrow down the fluctuation margin to keep it below 105 nA based on 2C21A reading. They could put the beam current monitor lock on 2C21A in case that may help with the wide fluctuation and/or adjust our laser phase as well as narrow down the slit width, see ELOG entries 4224300 and 4225220. |
General Instructions
|
|
|
Reference Values
FSD Thresholds from RG-D
- Upstream: 2 kHz
- Midstream: 2 kHz
- Downstream: 100 kHz
- BOM: 50 kHz
- 5 ms dwell time
Harp Scan References from RG-D
- 2H01 [3]; x= -1.4 mm; y= 0.0 mm
- Tagger (2C24A) [4]: x= -2.0 mm; y= +0.6 mm
- 2C21A [5]: x= -0.4 mm; y= +0.6 mm (less important; values form RG-C)
IA for Q Asymmetry
Beam Restoration
- Study the manual: Establishing Physics-Quality Beam. If you do not feel confident to do this by yourself, contact the RC or 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 (at the bottom of Short Term Schedule tab) whenever
- • there is a beam steering or a change in its orbits;
- • the beam current is changed; e.g., after a target change;
- • BPMs 2C21A and 2H01 positions are off, i.e., they are not within +/-0.1 mm. If so, ask MCC to bring them to the reference values recorded at the bottom of Short Term Schedule tab.
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 to avoid getting an alarm;
- • 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 (at the bottom of Short Term Schedule tab);
- - 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 at the bottom of Short Term Schedule tab 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
- Check its manual: Performing Møller Runs:
- • Must be noted that the manual has not been updated since the last run period. However, the underlying script in the Møller GUI should do it all for you.
- • After "reconfigure" and "enter," ask MCC for 5 nA and make sure the Orbit Locks are still OFF;
- - The BPMs 2C21 and 2C24A may become out of range after the Møller configuration. That is fine, so don't ask MCC to adjust it to the reference values, as that will mess up the positions after exiting the Møller configuration.
- • Start the run and keep it running until the polarization uncertainty reaches 1.5%, then end the run and log its results after entering your username.
- • Exit the Moller configuration.
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.
- • Make sure the Beam Blocker is OUT of the beamline.
- • Move the collimator to the 20 mm position;
- • Ask MCC to unmask beam halos;
- • Insert the Downstream Viewer in the beamline;
- • Ask MCC for 5 nA beam current;
- • Check the 2C24A and 2H01 beam positions (x, y) against the Reference Values (at the bottom of Short Term Schedule tab);
- - 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 at 2H01 (Midstream Left):
- - 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 at the bottom of Short Term Schedule tab;
- - If good, log the new scan results.
- Once done and prior resuming the production data-taking:
- • Retract the Downstream Viewer from the beamline;
- • Turn all detectors HV ON and make sure the MVT is switched to "HV ON - Full Voltage";
- • Proceed with production as instructed in Short Term Schedule tab:
- - Keep in mind that MCC might need to adjust the beam positions after going to the production beam current.
Responsibilities
- The RC duties are detailed in the COO.
- Check and contact, if needed, upcoming shifts about their training or site access status.
- The training requirements for the shift are:
- - ES&H Orientation (SAF 100);
- - Radiation Worker Training (SAF 801);
- - Oxygen Deficiency Hazard Training (SAF 103);
- - Hall B Safety Awareness Walk-Through (SAF111)
- - ES&H Orientation (SAF 100);
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 run group coordinator and communicate it to the shift crew.
- Log the RC summary in the HBLOG.
- Send a daily invitation for the RC meeting to hallb, clas_members, and rgd_ana mailing list.
- Run the RC meetings at 1 PM in CH Room 200C and on ZOOM, except on Wednesdays.
- On Wednesdays, the RC meeting is on ZOOM ONLY @ 15:30 due to the conflict with the 13:30 MCC meeting and the unavailability of the CH room afterwards.
- ‡ To connect to Zoom in CH Room 200C, follow these steps:
- ◊ 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 near the microphone in the middle of the conference table. Once it rings, answer the call, and you will be prompted to join the meeting.
- ◊ The room has a camera, so you may turn it on, if you wish, in the ZOOM browser interface.
Weekly
- Attend in-person the MCC scheduling meeting on Wednesdays at 1:30 PM and report the run status via the submitted Run Coordinator Weekly Summary;
- ‡ The report summarizes the data-taking status concerning the available beam used (ABU), any beam losses (BANU), CW on target (ABU+ABNU), etc., from 7 AM past Wed. through 7 AM the Wednesday the report is due, in addition to any standing and critical issues, plans for next week, and general comments/requests, if any.
- ‡ Our beam time accounting info can be retrieved either from:
- ◊ OPS logbook entries with tag 'Beam Accounting': Timesheet Summaries;
- ◊ Beam Time Manager; Physics Time Accounting.
- ‡ Refer to the RC Timesheet to calculate the percentage of scheduled experiment hours to date.
- ‡ The total experiment data collected to date could be retrieved from the up-to-date "Accumulated Charge" depicted on the "Total Charge on Target Plot" in the Monitoring tab.
- ‡ A detailed plan of the target configuration change will be generated as soon as the run starts; however, an overview of it is summarized in slide 6 of this RG-D Overview.
- Attend the Hall B meeting on Mondays at 9 AM and present your summary slides that should be sent beforehand to the Hall B leader, Patrick Achenbach, after checking them; please, with the Run Group Coordinator Lamiaa El Fassi.
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;
- • The RC must be notified before any run conditions are changed.
- Operate the Data Acquisition.
- Take action on and log alarms.
- Communicate with your co-shift person.
- The shift worker should discuss an issue with the shift expert before making extra logbook entries.
- 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; see link under https://wiki.jlab.org/clas12-run/index.php/Run_Group_C#Useful_Links
- Both, you and the shift worker should run mon12 and reset & check spectra frequently.
- If the worker shift is remote, maintain communication in Zoom: https://jlab-org.zoomgov.com/j/1619881100
- In case of other questions or uncertainties about what to do, call the RC.
- New RICH recovery protocol
- • See https://logbooks.jlab.org/entry/4201728 for important details.
- • There can be issues with missing tiles or the occupancy as seen in mon12. Put screenshots of scalers and temperatures or the occupancy spectra in the RICH logbook. Do not stop an ongoing run, but do the fast recovery between runs.
- • Daily full RICH recovery remains part of the protocol, preferably done during the daytime and only between runs; do not stop an ongoing run. State in your shift summary that you did the recovery (or why you did not).
- • Avoid unnecessary recoveries, see https://logbooks.jlab.org/entry/4208477. The RICH overview GUI shows how many seconds have passed since the last full recovery. Also, there is a minor alarm when 24 hours have passed since the last full recovery. Acknowledge the alarm and wait for the end of the run before making the recovery.
- • Note that you have to RESTART DAQ from scratch; see DAQ Opration under Short Term Schedule, after any RICH recovery.
- 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.'
- • Sign, viz log completed 8-hour sheet:
- • Note: we can change the timesheet up to 48 hours after completion.
Tasks
- Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.
- Discuss an issue with the shift expert before making extra logbook entries; ask the shift expert to note the ongoing issue in the shift summary and the start/end of run Comment field in the DAQ pop-up window.
Hourly
- Reset and check mon12 histograms
- Note that some plots have radio buttons at the bottom to choose the sector, in which case you should cycle through and check all sectors.
Once per run
- Submit EPICS screenshots to the HBRUN logbook with beam ON!
- ◊ Beamline overview, in VNC or Web Browser
- ◊ CLAS12 trigger rates and DAQ status
- Upload mon12 monitoring plots to the HBLOG logbook with sufficient statistics
- ◊ Afterwards, compare them to the reference and recent runs; see the top-right link at the Monitoring tab.
- Submit strip charts to the HBRUN logbook (set the 'time span width'to be compatible with the run duration)
- ◊ Beam current and position strip-charts (CS-Studio → Beamline → Strip Charts)
- ◊ Also accessible in a web browser: Upstream/Midstream Halo Counters, Downstream Halo Counters, Beam Currents, BPM Positions
Once per shift
- Fill the shift checklist.
- Per Gavalian's request, upload clas12online plots to the HBLOG logbook of the three tabs, Vertex, Photons, Vertex2D, with sufficient statistics!
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: https://jlab-org.zoomgov.com/j/1618614939
- ◊ 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
- ◊ 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.
Webcams
|
EPICS
|
Data Quality
|
Hall-B |
Accelerator |
ZOOM meetings
|