Difference between revisions of "Run Group D"
Jump to navigation
Jump to search
Line 78: | Line 78: | ||
== Important Notes == | == Important Notes == | ||
− | * In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House | + | * '''In case of medical or fire emergency, call 9-911 from a LANDLINE phone in the Counting House''' |
− | * 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 | + | * 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 "Worker Shift" Tab - you need some lead time to set up! | |
− | |||
− | |||
− | |||
− | |||
− | |||
+ | Note to shift takers, please: | ||
+ | * Read the '''logbook''', be aware of previous 24 hours | ||
+ | * Arrive at least 10 minutes early for '''shift change''' | ||
+ | * Refresh the run wiki pages; look over them every shift | ||
+ | ** Follow the '''expert/worker shift instructions''' | ||
+ | * '''Communicate''' with your co-shift person | ||
+ | ** The shift expert should know about and refer to logbook entries in their shift summary | ||
+ | ** The shift worker should discuss an issue with the shift expert before making extra logbook entries | ||
+ | |||
+ | <font color=red>'''LE: Please don't change: Work in progress ''' </font> | ||
== Short-Term Schedule for the Week from Burgsday, July 17, 2023 - == | == Short-Term Schedule for the Week from Burgsday, July 17, 2023 - == | ||
* In-bending torus field, 5-pass beam on ND3. | * In-bending torus field, 5-pass beam on ND3. | ||
Line 93: | Line 98: | ||
* CODA Configuration: PROD66 | * CODA Configuration: PROD66 | ||
* Trigger file: <tt>rgd_300MeV_v1.0.trg</tt> | * Trigger file: <tt>rgd_300MeV_v1.0.trg</tt> | ||
− | * If HWP is changed, start a new run | + | * If HWP is changed, start a new run |
+ | |||
+ | == <font color=blue> DAQ configuration </font> == | ||
+ | |||
+ | * Configuration is currently <tt>'''PROD66'''</tt>/<tt>PROD66_PIN</tt>, trigger file <tt>'''rgc_300MeV_v1.4_no_DC.trg'''</tt> | ||
+ | * '''NOTE''': UNLESS a RICH problem crashes the DAQ, do NOT interrupt an otherwise smooth run to make a RICH recovery - instead, do this in between runs. | ||
+ | * '''NOTE''': BOTH the shift expert AND the shift worker MUST check and reset monitoring histograms at least once every 30-60 minutes to make sure there are no major detector problems. Sometimes it is the only way to know that a roc needs to be rebooted. '''Watch the raster pattern!''' | ||
+ | * At the end of each run, follow the <font color=red>STANDARD DAQ RESTART SEQUENCE</font>: | ||
+ | ** "end run." | ||
+ | ** If the run ended correctly and you will run with the same configuration and trigger file, then: "prestart", "go" | ||
+ | ** If you are changing configuration (between PROD6X and PROD6X_PIN) or trigger file: "Cancel", "reset", "configure", "download", "prestart", "go". | ||
+ | ** If the run did not end correctly or if any ROCs had to be rebooted: | ||
+ | *** Quit ALL running instances of mon12 | ||
+ | *** "Cancel", "reset" | ||
+ | *** "configure", "download", "prestart", "go" | ||
+ | *** restart mon12 | ||
+ | * After each step, make sure it is completed in the Run Control message window. If an ROC has crashed, find which one it is, issue a roc_reboot command ON JUST THAT ROC, and try again. Contact the DAQ expert if there are any questions. | ||
== Reference Values == | == Reference Values == | ||
Line 149: | Line 170: | ||
== Tasks == | == Tasks == | ||
− | * Come to your shift in time for the shift change, 10-15 minutes before the start of your shift. | + | * 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 | + | * Follow the '''Short Term Schedule''' as outlined by RC |
− | * Keep | + | ** Run Plan, DAQ Configuration, and References and Standards |
− | + | * Keep '''shift summary''' up to date in HBLOG. Record all that happens. | |
− | * Ensure that all monitoring plots are logged correctly and checked against the reference plots | + | <!-- |
− | * Do a RICH recovery once daily during day shift, between runs | + | * 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 |
− | * [https://bta.acc.jlab.org | + | * Both, you and the shift worker should '''reset & check spectra frequently''' |
− | * If the worker shift is remote, maintain communications with them in | + | ---> |
+ | * Do a '''RICH recovery''' (press the RICH Recovery button on the GUI) once daily during the day shift, between runs. Please log in shift summary. | ||
+ | ** Note the automated "RICH Recovery" sequence already confirms RICH4 is up and accepting SSH connections before claiming success. | ||
+ | ** You have to "Cancel->Reset->Configure->Download->Prestart" before starting the next run. | ||
+ | |||
+ | * '''[https://bta.acc.jlab.org Fill out BTA]''' hourly. Click "Load from EPICS" to fill the left side automatically, then correct as needed. | ||
+ | ** 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 (e.g. target change or our problems) | ||
+ | *** BNA: beam not acceptable (e.g. tuning, drifting, not focused) | ||
+ | ** Experiment beam time | ||
+ | *** ER: experiment ready | ||
+ | *** PCC: planned configuration change (when the beam is masked while radiators are moved, DAQ (stopping/starting runs, tests, ...) are PCC. | ||
+ | *** UED: unplanned experiment down, is used for hardware failure | ||
+ | ** 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 | ||
+ | * If the worker shift is remote, maintain communications with them in Zoom: https://jlab-org.zoomgov.com/j/1619881100 | ||
'''In case of other questions or uncertainties of what to do, call the RC or PDL''' | '''In case of other questions or uncertainties of what to do, call the RC or PDL''' |
Revision as of 23:04, 6 September 2023
[edit]
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.
Run Coordinator: Lamiaa El Fassi (757) 575-7540
PDL: Nathan Baltzell (9-)757 876-1789 , x5902 office
Daily RC Meetings at 15:30: CH Room 200C, and on Zoom: Link, Meeting ID: 1611984219, Passcode: RGD-RC23
Important Notes
* 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 "Worker Shift" Tab - you need some lead time to set up! Note to shift takers, please: * Read the logbook, be aware of previous 24 hours * Arrive at least 10 minutes early for shift change * Refresh the run wiki pages; look over them every shift ** Follow the expert/worker shift instructions * Communicate with your co-shift person ** The shift expert should know about and refer to logbook entries in their shift summary ** The shift worker should discuss an issue with the shift expert before making extra logbook entries LE: Please don't change: Work in progress Short-Term Schedule for the Week from Burgsday, July 17, 2023 -
DAQ configuration
Reference ValuesFSD Thresholds from RG-C
Harp Scan References from RG-C |
General Instructions:
Every Shift:
Every Run:
To access the Hall:
|
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
- Run Plan, DAQ Configuration, and References and Standards
- Keep shift summary up to date in HBLOG. Record all that happens.
- Do a RICH recovery (press the RICH Recovery button on the GUI) once daily during the day shift, between runs. Please log in shift summary.
- Note the automated "RICH Recovery" sequence already confirms RICH4 is up and accepting SSH connections before claiming success.
- You have to "Cancel->Reset->Configure->Download->Prestart" before starting the next run.
- Fill out BTA hourly. Click "Load from EPICS" to fill the left side automatically, then correct as needed.
- 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 (e.g. target change or our problems)
- BNA: beam not acceptable (e.g. tuning, drifting, not focused)
- ABU: acceptable beam used (e.g. harp scans, calibrations, trigger settings, running)
- Experiment beam time
- ER: experiment ready
- PCC: planned configuration change (when the beam is masked while radiators are moved, DAQ (stopping/starting runs, tests, ...) are PCC.
- UED: unplanned experiment down, is used for hardware failure
- 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
- Accelerator beam time:
- If the worker shift is remote, maintain communications with them in Zoom: https://jlab-org.zoomgov.com/j/1619881100
In case of other questions or uncertainties of what to do, call the RC or PDL
Tasks
- Come to your shift in time for the shift change, 10-15 minutes before the start of your shift.
Hourly
- Reset and check mon12 histograms
- Note, 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 HBLOG logbook with sufficient statistics
- Afterwards, compare them to the reference and recent runs, see the top-right link at Monitoring tab above.
- Submit strip charts to the HBRUN logbook
- 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
For Remote Shifts
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 avaible 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
|