Difference between revisions of "Run Group D"
Jump to navigation
Jump to search
| Line 131: | Line 131: | ||
:◊ Both, you and the shift worker should '''reset & check spectra frequently'''. | :◊ Both, you and the shift worker should '''reset & check spectra frequently'''. | ||
* Please put relevant information while starting a run in DAQ run-control about the beam current and the type of runs, such as "Production", in the comment field. | * Please put relevant information while starting a run in DAQ run-control about the beam current and the type of runs, such as "Production", in the comment field. | ||
| − | * Do a '''RICH recovery''' by ''following the new procedure described in the HBLOG entry #:[https://logbooks.jlab.org/entry/4201728 4201728]'' between runs, once daily, preferably during a day shift, or depending on the case described in the referred HBLOG entry. Please log into the shift summary | + | * Do a '''RICH recovery''' by ''following the new procedure described in the HBLOG entry #:[https://logbooks.jlab.org/entry/4201728 4201728]'' between runs, once daily, preferably during a day shift, or depending on the case described in the referred HBLOG entry. Please log into the shift summary; |
:◊ Note the automated "RICH Recovery" sequence already confirms that RICH4 is up and accepting SSH connections before claiming success. | :◊ Note the automated "RICH Recovery" sequence already confirms that RICH4 is up and accepting SSH connections before claiming success. | ||
:◊ You have to "Cancel->Reset->Configure->Download->Prestart" before starting the next run. | :◊ You have to "Cancel->Reset->Configure->Download->Prestart" before starting the next run. | ||
Revision as of 23:40, 18 October 2023
[edit]
- General
- Phone Numbers
- Short Term Schedule
- 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 then have to 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
Responsibilities
Getting Started Standards
- Ensure the safe and efficient operation of the experiment; see the detailed duties in the COO.
- Check the shift schedule and training status of your shift crew (before YOU start!);
- ‡ Training Status: Skill Requirements List; Fill in the user's name and search.
- ◊ Training requirements for shift should also be in the COO, and they 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);
- ◊ Training requirements for shift should also be in the COO, and they are:
- Remote shifts are listed here: Upcoming-remote-shifts
Daily
- Attend the MCC meetings (7:45 AM and 8 AM Daily) in-person when running except on the weekend, which are virtual on ZOOM but @ 9 AM.
‡ See the ZOOM connection info under Important Links tab.
- Update the run plan in the Short Term Schedule tab in coordination with the AC and the run group, and clearly communicate it to the shift crew.
- Run the RC meetings at 1 PM in CH Room 200C and on ZOOM, except on Wednesdays, which is in ZOOM ONLY @ 15:30 due to the conflict with the 13:30 MCC meeting and the unavailability of the CH room afterward;
- ‡ 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 on "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 written 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.
- Check on shift crews at the start of each shift, especially if they are new.
- Send the RC summary to the HBLOG, hallb, clas_members, and rgd_ana mailing list.
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 with regard to 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/or 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 Analysis 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 as outlined by RC (/AC):
- ◊ Run Plan, DAQ Configuration, and References and Standards
- Keep shift summary up to date in HBLOG. Record all significant happenings.
- Include relevant links to other logbook entries during your shift and add a run list at the end (see previous shift summaries).
- 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
- ◊ Both, you and the shift worker should reset & check spectra frequently.
- Please put relevant information while starting a run in DAQ run-control about the beam current and the type of runs, such as "Production", in the comment field.
- Do a RICH recovery by following the new procedure described in the HBLOG entry #:4201728 between runs, once daily, preferably during a day shift, or depending on the case described in the referred HBLOG entry. Please log into the shift summary;
- ◊ Note the automated "RICH Recovery" sequence already confirms that RICH4 is up and accepting SSH connections before claiming success.
- ◊ You have to "Cancel->Reset->Configure->Download->Prestart" before starting the next run.
- Keep taking data whenever possible;
- ◊ If you notice a problem, keep taking data, if possible, until you know what to do. Also, if you are waiting for an expert, keep taking data, if possible, and note the ongoing issue in the shift summary and the start of run Comment field in the DAQ pop-up window.
- Fill out BTA hourly. The new interface does automatically load the value from MCC EPICS; you may need to adjust the ABU/BANU/UED/ER...etc, numbers if they don't match the ongoing events on an hourly basis from the "editing" button on the left side of each row. You can also use the "Choose" drop menu in the top left corner to switch from hours to minutes, pick the experimental hall, shift period, etc.
- ◊ Accelerator beam time:
- ‡ ABU: acceptable beam used (e.g., 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 (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
- - ER: experiment ready (should be 1 hour minus BNA, and the time of BNA should be reflected in our PCC and UED)
- - PCC: planned configuration change (when the beam is masked while radiators are moved, target change, DAQ (stopping/starting runs, tests, ...)
- - UED: unplanned experiment down (hardware failure, DAQ crashes, ...)
- ‡ Enter fields at the tab "Shift Information"
- ‡ Promptly send "Info for MCC" at 7:00, 15:00, and 23:00
- ‡ Sign, viz log completed 8-hour sheet
- ‡ ABU: acceptable beam used (e.g., harp scans, calibrations, trigger settings, running)
- If the worker shift is remote, maintain communication in Zoom: https://jlab-org.zoomgov.com/j/1619881100
In case of other questions or uncertainties of what to do, call the RC
Tasks
- Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.
- Keep taking data whenever possible;
- ◊ If you notice a problem, keep taking data, if possible, until you know what to do. Also, if you are waiting for an expert, keep taking data, if possible, and ask the shift expert to note the ongoing issue in the shift summary as well as the start/end of run Comment field in the DAQ pop-up window.
Hourly
- Kill and restart the mon12 program after the end of each run until it's instructed otherwise!
- ◊ 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, which are maintained 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
|
|
|
