Shift Guidelines for Shift Leader

From Hall D Ops Wiki
Revision as of 12:58, 9 March 2020 by Elton (Talk | contribs) (Changing radiators)

Jump to: navigation, search

Run info logging

  1. Keep a list of the runs at the end of the shift summary log entry, eg https://logbooks.jlab.org/entry/3795057
  2. Keep the runs to 2h real-time at most. Calibrations drifts are noticeable after about 2h.
  3. Write run info into the DAQ run comments box at the start of the run and save it.
  4. Make sure that the paper list of runs is kept up to date.

Monitoring

  1. Half-way through each run, post the rootspy monitoring histograms to the logbook and reset them. Post the new plots at the end of the run.
  2. Make a screenshot of the GlueX overview CSS logentry mid-shift.
  3. Remind the shift worker to complete the shift checklist.
  4. Watch the beam monitoring stripcharts, currently using beam_instability_monitoring configuration, & post to the logbook at the end of the shift
  5. New, maybe temporary: if PS coincidence rates drop by 30% or more, do harp scans (MCC & ours)

Changing radiators

  1. Each time the amorphous radiator is inserted, make a new AMO reference with beam on.
  2. Each time the diamond radiator is inserted or its orientation changed, use the nudge buttons to obtain the desired coherent edge fit value, save the new configurations as instructed in ," Adjusting the Peak Positions," and make a screenshot logentry of the cobrems gui.

Alarms

  1. When acknowledging alarms for mechanical and DIRC, acknowledge them at the lowest level of the tree. This is to avoid sending 'OK' messages to the on-call phones for all the branches of the tree which were not alarming.
  2. Make separate logbook entries for worrying alarms & contact experts as needed.

Beam-Time Accounting (BTA) Guidelines

Access

  1. We keep a list of requests for opportunistic access on the whiteboard. We also have to keep a list of who is actually in the hall during accesses.