Difference between revisions of "Run Group E"
Jump to navigation
Jump to search
| Line 164: | Line 164: | ||
* Reset and check MON12 histograms frequently, preferably each 1/2h, during a run: | * Reset and check MON12 histograms frequently, preferably each 1/2h, during a run: | ||
| − | |||
:• Note that some plots have radio buttons at the bottom to choose the sector, so you should cycle through and check all sectors. | :• Note that some plots have radio buttons at the bottom to choose the sector, so you should cycle through and check all sectors. | ||
| Line 172: | Line 171: | ||
:◊ 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 | ||
| − | |||
* Upload '''MON12''' monitoring plots to the logbook with sufficient statistics: | * Upload '''MON12''' monitoring plots to the logbook with sufficient statistics: | ||
:◊ Afterwards, compare them to the reference and recent uploads; see the top-right link at the {{#switchtablink:Monitoring|Monitoring}} tab. | :◊ Afterwards, compare them to the reference and recent uploads; see the top-right link at the {{#switchtablink:Monitoring|Monitoring}} tab. | ||
| − | |||
* Submit '''Beam current and position strip charts''' to the logbook at '''the end of the run''' | * Submit '''Beam current and position strip charts''' to the logbook at '''the end of the run''' | ||
:◊ If they are not up already: (CS-Studio → Beamline → Strip Charts); | :◊ If they are not up already: (CS-Studio → Beamline → Strip Charts); | ||
:◊ Choose the 'time-span width' to be compatible with the run duration. | :◊ Choose the 'time-span width' to be compatible with the run duration. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Once per shift === | === Once per shift === | ||
| Line 191: | Line 182: | ||
:• During production or if the beam is down for your entire shift, get relevant values from the epics screens Beamline Overview, CLAS12 DAQ Status, and CLAS12 Trigger; | :• During production or if the beam is down for your entire shift, 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 you made during production. | :• During extended downtime, get relevant values from the latest EPICS screenshots you made during production. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== For Remote Shifts == | == For Remote Shifts == | ||
| Line 237: | Line 222: | ||
* MON12 histograms: reference and most recent uploads | * MON12 histograms: reference and most recent uploads | ||
:• '''New'''; 95 nA on CuSn target (S<sub>T</sub>=+1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4223511 run 18875] | :• '''New'''; 95 nA on CuSn target (S<sub>T</sub>=+1.0): [https://clas12mon.jlab.org/mon12/histograms/?reference=4223511 run 18875] | ||
| − | |||
* [https://clasweb.jlab.org/clas12online/timelines/rg-d/RGD2023_progress_all.html Total Charge on Target Plot] | * [https://clasweb.jlab.org/clas12online/timelines/rg-d/RGD2023_progress_all.html Total Charge on Target Plot] | ||
* [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox! | * [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login) Google-Chrome ONLY, Not Firefox! | ||
| Line 249: | Line 233: | ||
===Hall-B=== | ===Hall-B=== | ||
* [https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc Operation Safety Procedures] | * [https://clasweb.jlab.org/wiki/index.php/CLAS12_OPS_Doc Operation Safety Procedures] | ||
| − | * [ | + | * [Run Group E Analysis Wiki] |
* [http://clasweb.jlab.org/rcdb RCDB] | * [http://clasweb.jlab.org/rcdb RCDB] | ||
* [https://clasweb.jlab.org/cgi-bin/ccdb/objects CCDB] | * [https://clasweb.jlab.org/cgi-bin/ccdb/objects CCDB] | ||
Revision as of 11:01, 21 November 2023
[edit]
Daily RC Meetings at 13:00 in CH Room 200C, and on ZOOM: URL Link (Meeting ID: 1605705819), except on Wednesdays, which is @ 15:00 in CH Room 200C and via the same ZOOM link.
- General
- Phone Numbers
- Short Term Schedule
- Run Coordinator
- Shift Expert
- Shift Worker
- Monitoring
- Important Links
GeneralLogbookShift Schedule[Run Coordinator Schedule]ESAD, 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: Sebouh Paul
Current RP Coordinator: Lamiaa El Fassi (757) 575-7540
PDL: Nathan Baltzell (757) 876-1789, Office: x5902
Important Notes
- In case of medical or fire emergency, call 911 or 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 can call MCC to turn the beam OFF for 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, the RC, and JLab medical services immediately to arrange replacements.
- In case of a problem with the HV Slow Controls, EPICS in general, please call the primary expert on-call, Nathan Baltzell, before reaching out to anyone else.
- Please put all essential information on the main Hall B logbook HBLOG. Some important alarms have been documented on HBRUN. Use the pulldown menu to choose where an error is reported.
Current Run Plan: May 17th to May 19th
Outbending Configuration Runs
Previous Dual-target Configuration Plans- DC firmware test plan (LD2 + Pb)1) Take one run each with 1M events with the trigger files and beam current at 70 nA
2) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_2.trg 3) Take one run with 500k events and beam current at 35nA with trigger file rge_inb_v1.0_200MeV_dcrb17_4.trg
*** Notes ***
LD2+Pb runs
LD2+Sn runs
LD2+Al runs
Lumi Scan for LD2+Al on May 15th
Lumi Scan for LD2+Pb on May 15th - 16th
Streaming Readout Test
Empty-target runs on May 16th - 17th
|
References- BPM Positions
- Harp Scans- FSD Thresholds
- Charge Asymmetry- Upstream Halo counters
|
General Reminders
|
DAQ Operation
|
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 a daily RC summary in HBLOG and send a daily invitation for the RC meeting to hallb@jlab.org and clas_members@jlab.org
- Run the daily 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.
- Attend the Hall B meeting on Mondays at 9 AM and present your summary slides.
Tasks
- Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.
- • If it's your first shift or a shift after a long pause, please come at least 4 hours before your shift (or even better, come a day earlier) to shadow the previous shifter and 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.
- Communicate with your co-shift person:
- • The shift worker should discuss an issue with the shift expert before making extra logbook entries.
- • During production, not in extended downtime, the shift expert should ensure the shift worker is filling their end-of-shift Checklist when the beam is ON, not in the period of beam trips.
- 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 shift activities, issues, if any, and related communications with experts with details and/or reference to any associated logbook entries:
- • Refer to relevant logbook entries in the shift summary.
- • Include a list of runs taken during the shift with relevant run information;
- - See, for instance, this shift summary where all relevant run info, links, and shift activities are cited.
- Ensure that all MON12 monitoring plots are logged and checked against the reference plots for every single run; see the links under Monitoring tab;
- • 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
- If you have any 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.
- • In case of a RICH issue a screen shot of both scalers and temperatures should be logged in the RICH logbook before running the appropriate recovery.
- • Issues can be seen from missing tiles in the scaler and temperature GUIs or the occupancy as seen in MON12. Do not stop an ongoing run, but do the fast recovery between runs.
- • If the issue is seen in the scaler but not in the temperature GUI, then you should do a full recovery; see https://logbooks.jlab.org/entry/4214184. This might preempt the daily full recovery.
- • 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 running the recovery.
- • Note that you have to RESTART DAQ from scratch (cancel-->reset-->configure-->download-->Prestart-->Go); see DAQ Opration under Short Term Schedule, after any RICH recovery.
- ◊ In case of getting a ROC error during the recovery, it's advised to "roc_reboot rich4" in the DAQ VNC terminal.
- • If the beam is ON and a RICH recovery is taking more than 5 min, please call the RICH expert, preferably the secondary number before the primary.
- For any RICH problems overnight or on weekends/holidays, please call the RICH expert, preferably the secondary number before the primary, along with the RC (eventually the AC will get involved) to discuss and fix the issue!
- 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. In brief, it requires a reboot of LV as follows:
- ◊ 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 alarm NActiveCrates, status also reported on the MVT Overview GUI. This alarm will be cleared 2 min after LV is turned back ON;
- ◊ At this point, mvt1, mvt2, and mvt3 ROCS can be rebooted;
- ◊ Start a run by initializing DAQ from scratch: cancel-->reset-->configure-->download-->Prestart-->Go.
- ◊ If the beam is ON, and a reboot process takes more than 5 min, please call the DAQ and/or SVT/MVT/MM expert.
- Fill out BTA hourly;
- • Accelerator beam time:
- ◊ ABU: acceptable beam used,
- ◊ BANU: beam acceptable but not used (should be reflected in our PCC or UED);
- - Exception: BANU due to beam tuning with harp scans or Moller runs might be included in BNA.
- ◊ BNA: beam not acceptable (e.g., tuning, drifting, not focused);
- ◊ ACC: Accelerator configuration change (e.g., pass change or Maintenance/beam studies recovery);
- ◊ OFF: Accelerator is down.
- • Experiment beam time (do change these values):
- ◊ ER: Experiment ready (should be 1 hour - PCC - UED)
- ◊ PCC: Planned configuration change (beam tuning with harp scans or Moller runs, target change, DAQ; e.g., stopping/starting runs, tests, etc.)
- ◊ UED: Unplanned experiment down (hardware failure, DAQ crashes, or experiment/hall problems)
- - Exception: BANU, due to time spent on drifting beam positions after beam down, may 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.' You can check here, https://ace.jlab.org/btm/reports/activity-audit, whether you saved correctly!
- ◊ 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 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;
- • If it's your first shift or a shift after a long pause, please come at least 4 hours before your shift (or even better, come a day earlier) to shadow the previous shifter and familiarize yourself with all shift duties and technicalities of the ongoing experiment.
- 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.
Frequently
- Reset and check MON12 histograms frequently, preferably each 1/2h, during a run:
- • Note that some plots have radio buttons at the bottom to choose the sector, so 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 logbook with sufficient statistics:
- ◊ Afterwards, compare them to the reference and recent uploads; see the top-right link at the Monitoring tab.
- Submit Beam current and position strip charts to the logbook at the end of the run
- ◊ If they are not up already: (CS-Studio → Beamline → Strip Charts);
- ◊ Choose the 'time-span width' to be compatible with the run duration.
Once per shift
- Fill the shift checklist;
- • During production or if the beam is down for your entire shift, 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 you made during production.
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
- 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 to 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
Webcams
|
EPICS |
Data Quality
|
Hall-B
|
Accelerator |
ZOOM Meetings
|
|
|
