How to be a Run Coordinator

Run Coordinator Duties

Run Coordinator's Daily Report

The normal daily report should include a brief shift summary for the last three shifts, including people on shift, running conditions, and problems. SLC and SLD online Z counts should be reported. The set of standard background plots and the polarization plot should also be shown. The Monday morning report should include a summary of the week's running with offline Z counts. Copies of all or these reports should be pasted into the Run Coordinator logbook for future reference.

The report should be written and filed on the MAC in the CEH (next to the printer). The simplest method is to select a recent report, edit the contents, and file and print the new report. MAC and WORD novices can try the following prescription:

  1. Open file with previous report:
  2. double click SLD Run Coordinator,
  3. double click Status Reports File,
  4. double click < file with previous report >.

  5. Edit old report to produce new report:
  6. click and drag cursor over old text to be deleted (selection turns blue),
  7. type in new replacement text.

  8. File new report:
  9. click File on top menu bar (next to Apple),
  10. drag cursor to Save as ... option,
  11. enter new file name with appropriate date,
  12. click Save (or just Return).

  13. Print new report:
  14. click File on top menu bar (next to Apple),
  15. drag cursor to Print ... option,
  16. click Print (or just Return).

Shift Summary

The daily shift summary should be based on the shift reports written by the expert at the end of each shift. These summaries are pasted into the SLD logbook and entered into the Oracle database. To access the reports from an SLD SCP running on SLDACQ:
  1. navigate to the Shifts panel (Index -> Oracle Database -> Shifts),
  2. list the desired report (List + Shift Report + < select shift > + Execute).

Online Z counts

SLC luminosity measurements are used to make a running online estimate of the number of Zs produced by SLC and recorded by SLD.

From the MCC SCP (left end of Star Wars console):

  1. navigate Index -> Special Display -> Lum History Plots,

  2. select the desired quantity to plot: 
     
  SLC INTZ * BSM     (SLC Z count) 
  SLD INTZ * BSM     (SLC Z count, gated by SLD livetime)
  SLD CDC ON * BSM   (SLC Z count, gated by CDC voltage)
  3. select last 24 hours or set explicit begin and end times
    (Plot Scale Panel -> Enter X Scale),

  4. select Print Graph Display to get printout.

Offline Z counts

Counts of events passing various SLD offline processing filters are available from the Oracle database. A new offline facility has been developed by your friendly offline crew which should make it very easy to get at these numbers. As of now (July 4 1994) it is not completely functional, but check out the SLD Run Info facility anyway.

Background Plots

From the MCC SCP (left end of Star Wars console), navigate Index -> IP Status -> SLD 24hr macro. This will automatically print three standard noise plots on the IMCEH0 printer. Individual history plots for the different noise signals are available in the SLD History Panel.

Polarization Plot

From the SLD POLSCP (across from MCC SCP), navigate
Index -> Compton Polarim -> Pol Time History, then select Cherenk Polar.
This generates a nice polarization plot with error bars.

Run Status Report

The daily run status report is a computer message distributed to the world at large through DUCSNEWS. It should summarize the past 24 hour's running, including an update on SLC performance and problems, any SLD hardware or software problems, plans for the current day, and a luminosity summary. A printed copy should be pasted into the Run Coordinator log book.

It would be really nice if you could update the run status report just by filling in a form such as this one, but you can't because we haven't made it work yet, so instead you have to follow the instructions below, using your choice of operating system and text editor.

For SLACVM lovers

  • If you are lazy you can get a previous report off the G disk by typing
    FILELIST * NEWS G, then copying the most recent file to your own disk for editing. Make sure you edit out the last three lines if you do this, since they are inserted by DUCSNEWS and you don't want them there again.

  • Write the new report and save it back on your disk.

  • Issue the command $SLDNEWS < yourfn > < yourft > and away it will go to DUCSNEWS.

    • For VAX lovers

  • If you are lazy you can edit a previous report, which can be found on disk$fac0:[sld.runstatus]runstatus.doc. From the SLD account on the SLD VAX, just type EVE RUNSTATUS.

  • Write the new report and save it somewhere.

  • Submit your file to DUCS by issuing the commands: 
         $ DUCSNEWS
     DUCSNEWS> ADD < yourfile >

     Enter the expiration date (0007, meaning 7 days from now) 
     Enter the title (e.g. SLD Run Status Report for 15 July 1994)     

     DUCSNEWS> EXIT

    • Run Status Telephone Message

    The daily run status telephone message is a recording available to the world at large by dialing (415) 926-2011. (WWW junkies -- insert hyperlink to phone dialer here!)

    To record a new message, dial 926-5110 and follow the prompts:

  • enter mailbox: 1000#
  • enter password: 1000#
  • enter 5 to record new message (terminate with #)
  • enter 2 to review recorded message (terminate with #)

    • Offline Shift Reports

    Offline shifts check the quality of the data at various stages of processing and report results daily to the run coordinator. The reports are also filed on VM disk ZZERO 211 (filetype REPORT). Reports give run-by-run summaries of polarization, Z counts, Bhabha counts, RTH status, event display status, and CDC high voltage uptime. Problems or suspicious observations are described. The run coordinator should check the reports daily and refer problems to experts.

    Tony Johnson, June 30 1994
    modified by Eric Vella, September 1994