09/19/99 Owl shift summary

Valeri Jejer (jejer@uvahea.phys.virginia.edu)
Sun, 19 Sep 1999 08:36:47 -0400 (EDT)

Shift Summary for owl shift, 18/sep/99

On Shift: Theo, Valeri + 0.5 Arun and 0.5 Ashkan

Hours of beam available at all intensities: 7.0
Hours of beam available at nominal intensity: 7.0
Hours of E799 data (special runs not included): 6.7
Hours of special runs (laser scans, muon runs...): 0

Accounting of lost time:

stop/start run, 2 kfrends

========================================================================
Runs ended this shift:

Run 14624 - 1.2M evts - BEAM_799 at 4e12
Run 14645 - 12M evts - BEAM_799 at 8e12

Tapes brought to FCC this shift:
(including tapes for online split)

none

========================================================================
Accesses during shift:

none

========================================================================
Overview of shift:

Smooth running with only 3 kfrends - two because of ktevana errors and
once got busy from crate 53.

Arun started online split with no problems.
========================================================================
Description of Shift:

run spill time comment
-------------------------------------------------------------------------
14624 00:17 Start run to test online split which works.
01:30 Stop run. Call MCR to increase intensity to
8e12. They did.
14625 01:35 Start long run with 10" absorber at 8e12.
03:30 SEM is ~8.4-8.5e12, call MCR to lower it
a little.
04:40 Arun noticed that we do not have any events
in trigger 16 after Level2. L1 3MU3y source
is working. Arun will fix later.
06:59 Tapes are full, run stopped.
========================================================================
Follow up Notes on Previous Shift

Done with Onsplit debugging.

========================================================================
Items to Follow up on Next Shift

Keep running in the same configuration (8e12 with 10" absorber)

Keep eye on PMT gain drift (gains were stable through the owl shift).

Go through all online histograms and make comments about what needs
to be fixed.
-----------------------------------------------------------------------