Difference between revisions of "Run Group E"
Jump to navigation
Jump to search
| Line 191: | Line 191: | ||
* MON12 histograms: reference and most recent uploads | * MON12 histograms: reference and most recent uploads | ||
** [https://clas12mon.jlab.org/mon12/histograms/?reference=4223511 run 18875] | ** [https://clas12mon.jlab.org/mon12/histograms/?reference=4223511 run 18875] | ||
| + | * [https://github.com/JeffersonLab/caos/tree/main#readme clas12mltrack/clas12online]: | ||
| + | :• '''New'''; displaying real-time reconstructed vertices & various event topologies | ||
* [https://clasweb.jlab.org/clas12online/timelines/ Total Charge on Target Plot] | * [https://clasweb.jlab.org/clas12online/timelines/ Total Charge on Target Plot] | ||
* [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login) | * [https://clasweb.jlab.org/hydra/dashboard2.html Hydra] (CUE Login) | ||
Revision as of 13:13, 16 March 2024
[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 at the same ZOOM link.
- General
- Phone Numbers
- Short Term Schedule
- Run Coordinator
- Shift Expert
- Shift Worker
- Monitoring
- Important Links
GeneralLogbookShift ScheduleRG-E Run 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.
Run Coordinator: Taisiya Mineeva (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 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.
Please put all essential information on the main hall B log HBLOG. Some important alarms have been documented on HBRUN. Use the pulldown menu to choose where an error is reported.
Run PlanTake production data! Don't break anything! Keep an eye on the backgrounds, for example as seen in the halo counters, and on the 2C24 and 2H01 BPM positions. Both of these give confidence that the beam remains centered on the RGE target. Production data taking
In case of the need to manipulate the whole target system - cryotarget or solids - please contact the target experts.
DC firmware test plan (LD2 + Pb)1) Take one run each with 1M events with the trigger files and beam current at 70nA
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 Before the last run call DC expert Florian so that he can change back the firmware after the last run is finished. Note:
LD2+Pb runs
For information on triggers, please see here: https://logbooks.jlab.org/entry/4267187 Long term run plan [1] |
ReferencesBPM PositionsThe most important BPMs to monitor are 2C24 and 2H01, from the point of view of assuring the beam remains centered on the RGE target. The values of the others can be influenced by other steering/focusing beamline elements.
Harp ScansFSD ThresholdsDo NOT change FSD settings without approval from RC or beamline expert!
Charge AsymmetryUpstream Halo countersIf reading on the upstream halo counters exceeds 10, please, contact MCC. |
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.
- 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;
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 with beam ON to the HBRUN logbook
- - 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
- - 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
|
|
|
