Shift Summary for Owl shift, 22/Nov/99

Miguel Barrio (mbarrio@hep.uchicago.edu)
Mon, 22 Nov 1999 15:14:37 -0600

Shift Summary for Owl shift, 22/Nov/99

On Shift: V. Jejer, M. Barrio

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.5
Hours of special runs (laser scans, muon runs...): 0.2

Accounting of lost time:
Just the time required for initialization and such. Had a few ktevana
errors, but nothing unusual.

========================================================================
Runs ended this shift:
Run 15027 - BEAM_799 - 14.1M events.
Run 15029 - BEAM_MUON - muon ~300k events

Tapes brought to FCC this shift:
none.

========================================================================
Accesses during shift:
none.

========================================================================
Overview of shift:
E799 datataking, muon run in between (we took advantage of the tape
change to switch to muon configuration with as little dead time as
possible... (hehe).

========================================================================
Description of Shift:

run spill time comment
------------------------------------------------------------------------
15027 0:00 Tevatron has been chugging along since 3am on
Sunday. Spill is kinda ratty though.

4:08 Taku goes like "I'm full..." or whatever, so we
have to change tapes. Before doing so, we
call the control room to switch to muon mode.

15029 4:20 We start a muon run for about 10 minutes.

4:30 Stop muon run.

Flipped magnet polarity.
Initialized next run in 799 mode,
called MCR to switch to data-taking mode.
We got ktevana errors AFTER stopping the muon
run, dunno why.
SDAQ complains again about the voltages in some
of the crates, and reports weird numbers for
those. Did a sdaq_fresh_start, just in case, and
that fixed this problem.

15030 4:37 Start 799 data run.

"Monitor monitoring monitor" (Valeri's dixit,
aka, that monitor with the 'monitor stats')
isn't updating, so it was restarted. NEXT time a
run is started, a dart_fresh_start should be
performed.

========================================================================
Follow up Notes on Previous Shift
Took a muon run if and when there's some inevitable dead-time.

========================================================================
Items to Follow up on Next Shift
Just a reminder to do a dart_fresh_start for the next run.

-- 
Miguel Barrio
Email:  mbarrio@hep.uchicago.edu
Office: HEP 319, 773-702-7484; fax X-1914
Pager:  630-722-6854