Resent-Date: Fri, 19 Jan 1996 15:06:37 -0600 (CST)
Resent-From: SIGNORE@FNALV.FNAL.GOV
Resent-To:   sigNORE@DAUMI1.FNAL.GOV
Date: Fri, 19 Jan 1996 15:05:21 -0600 (CST)
From: CTAYLOR@FNALV.FNAL.GOV
Subject: First store report
Resent-to: SIGNORE@FNALV.FNAL.Gov
To: t864-l@fnmine.fnal.gov
Resent-message-id: <01I0761NA6K40003KM@FNAL.FNAL.GOV>
Message-id: <960119150521.25a7e4dc@FNALV.FNAL.GOV>
X-VMS-To: IN%"t864-l@fnmine.fnal.gov"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

This is a preliminary report of day 1 of E811 running, which has just
ended--27 hours of continuous data-taking.

People on shift during this period include:
Bill Davis, Ken Delsignore, Jon Streets, Cyrus Taylor, Larry Jones and 
Mike Longo; "Art" Martens also spent some crucial time in the portakamps
explaining to us how to turn the MR Gate on and off.

A couple of general comments:  We began the run with a delay curve,
a luxury we've usualy eshewed under collider conditions.
We have better on-line monitoring 
(including an on-line version of Bj's monitor code) than ever before,
and a dst had been made of the first 50,000 events before midnight:
tracks confirmed by aid of a viewer!  Efficiencies were checked with
the first run, and and re-checked (at lower voltages) later in the
run!  There were intermitent periods of losses throught the evening;
this may be reflected in somewhat varying mean NHITS. John carried
the first few tapes (all tapes are copied from MINxxx labels to
MM0xxx labels, and the MM0xxx tapes are taken to the tape vault)
over to the tape vault at about 11PM.  MR was off for the first 12
hours of the run.  Note that the store is longer than the nominal 24 hour
cycle A/D has in mind because the stack was lost.

Overall score:

Collider trigger, pb in: 1.18 million events to disk/tape
Collider trigger, pb out: ~255,000 events to disk/tape
[On this run, we biased to pb in more than we plan to overall]

Disk runs will be copied to FNMINI$dua1:[data], and to FNALU/d10.
Jon is working to acquire more disk space for us on FNALU.  Tape runs
will appear on FNALU by and by it seems.

Run Summary:

Run 1087 
Seps on Pb out bd pbar or delay=7ns 6005 events to disk

Run 1088 
Seps on Pb out bd pbar or delay=7ns 3272 events to disk [seps off at end

Run 1089 
seps off Pb out bd pbar or delay=8ns 50134 events to disk

Run 1090	[scanning run]
seps off Pb moveing bd pbar or delay=22ns 3652 events to disk

Run 1091
seps off Pb in bd pbar or delay=8ns 100826 events to disk

Run 1092
seps off pb in bd pbar or delay=8 ns 251252 events to tape MIN200

Run 1093
seps off pb out bd pbar or delay=8 ns 103119 events to tape MIN201

Run 1094
seps off pb in bd pbar or delay=8 ns 84014 events, E811 begins second
scrape at end

Run 1095
seps off pb in bd pbar or delay=8ns 24514 events to disk; scraping

Run 1096
seps off pb in bd pbar or delay=8ns 250044 events to tape MIN203

Run 1097	[scanners run]
seps off pb out bd pbar or delay=22ns 11612 events to disk

Run 1098
seps off pb out bd pbar or delay=8 ns 50091 events to disk [voltage run]

Run 1099
seps off pb in bd pbar or delay=8 ns 174804 events to tape MIN204

****Here the MR gate returns---along with some MR contamination problems
see log 4 p 38 ff.

Run 1100
spes off pb in bd pbar or delay=8ns 110659 events to tape MIN205
chamber trip at 12:29 AM
call MCR "Ralph is making a measurement"

3:12 AM
MR gate is letting some MR in {"BD went from ~0->6K almost instantly"]

Run 1101
seps off pb in bd pbar or delay=8 ns 109516 events to tape MIN 206
lostp spiking early, ~4:20 and 4:25

Run 1102	[scanners run]
seps off pb out bd pbar or delay=22 ns 12177 events to disk

Run 1103
seps off pb in bd pbar or delay=8 ns 75232 events to disk

Run 1104
seps off pb out bd pbar or delay=8 ns ~52000 events to disk
(We cant' be more accurate because of a strange glitch in the
event to disk scalar over the terminal, apparenlty caused by
bumping the table.)  Also note a burst in the alphabet rate at
event 158364. 

Resent-Date: Sat, 20 Jan 1996 20:47:21 -0600 (CST)
Resent-From: SIGNORE@FNALV.FNAL.GOV
Resent-To:   sigNORE@DAUMI1.FNAL.GOV
Date: Sat, 20 Jan 1996 20:45:21 -0600 (CST)
From: LJONES@FNALV.FNAL.GOV
Subject:
Resent-to: SIGNORE@FNALV.FNAL.Gov
To: t864-l@fnmine.fnal.gov
Resent-message-id: <01I08W8GJ978000BT3@FNAL.FNAL.GOV>
Message-id: <960120204521.4020745c@FNALV.FNAL.GOV>
X-VMS-To: IN%"t864-l@fnmine.fnal.gov"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Second run update of January run (Jan. 18, 19, 20)

This message updates Cyrus' message of yesterday with results of subsequent
running.  In general, the running has gone very smoothly.  In particular, we
have not only had optimal seps off luminosity but for much of the time, the
main ring has been off so that we have had essentially 100% live time.  Today
(Jan 20) late in run 1111, Cyrus noted the TDC distributions from the alphabet 
counters looked bad.  Cyrus, Dick, and Bill spent two or three hours working on
the problem and finally deduced that the TDC unit was flakey (since run 1101).
In the course of working on this problem, the T0 signal got re-plugged into the
wrong spigot, resulting in a BD-Pbar OR rate/Beam Trig rate of about 1/3 rather
than 1.0.  This occured during run 1114 (a diagnostic run) and was diagnosed
and fixed by Dick during run 1119.  At 1730 the store was dumped for an 811
access.  Meanwhile, a booster PS is busted and of this writing (20:00) there is
no estimate when the MR will start up again.  Following startup, there will be
abt 4 - 5 hours of p-bar stacking (now only 35 ma in stack), so we will be off
until at least past midnight; as of now, no estimate from MCR.  

In all runs tallied below, the [bd pbar or] delay was 8 ns.  Where on tape, the
tape MIN number is noted.  Note that runs 1105 and 1112 - 1116 were diagnostic,
and 1106 was a short beam-gas run. These are not recorded in the run summary 
below.  For all of the data below the MR was off.

Run 1107  	Pb in		 46,270 evts	disc

Run 1108        Pb out		250,073 evts	MIN207

Run 1109	Pb in		250,167 evts	MIN208

Run 1110	Pb in		250,033	evts	MIN209

Run 1111	Pb out 		234,430 evts	MIN210

Run 1117	Pb out		  3,168 evts	disc

Run 1118	Pb in		 24,458 evts   	disc

Run 1119	Pb in		 13,419	evts	disc

 As of this writing (surely through midnight) the box score for "good" data is:

	Pb OUT 	  744,660 events
	Pb IN	1,765,124 events

	Total:  2,509,784 events.

On shift: Cyrus, Dick, Mike L., Bill, Ken, Larry (not all at once!).

							Larry

Resent-Date: Mon, 22 Jan 1996 8:06:40 -0600 (CST)
Resent-From: SIGNORE@FNALV.FNAL.GOV
Resent-To:   sigNORE@DAUMI1.FNAL.GOV
Date: Mon, 22 Jan 1996 08:05:59 -0600 (CST)
From: CTAYLOR@FNALV.FNAL.GOV
Subject: store 3 report
Resent-to: SIGNORE@FNALV.FNAL.Gov
To: t864-l@fnmine.fnal.gov
Resent-message-id: <01I0AY915VIS0003KD@FNAL.FNAL.GOV>
Message-id: <960122080600.25a76191@FNALV.FNAL.GOV>
X-VMS-To: IN%"t864-l@fnmine.fnal.gov"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

Shot setup for store 5867 begins at 5:15 AM 21 Jan '96.  KD on deck
Shooting from a 60 ma stack

7:18 AM unstacking pbars; bunches 6, and especially 5 are light compared
to others

7:40 AM Begin run 1121 to disk
seps on, scraping
BD pbar or delay=22ns Pb out
7:58 AM end run 1121 19383 triggers to disk

8:10 AM seps off
Run delay curve; leave at 8ns for now
8:15 AM begin run 1122 
PB out, MR ON, Seps OFF
BD Pbar or 8 ns
to disk
genmon reports Beamtrig/BDPbar or rates = 2.0!!
8:42 AM Mike Longo traces the problem to an unterminated cable
problem fixed at events ~58222
9:10 Online monitoring of Alphabet counter TDC's indicates that the sudden
time shift is recurring (Db,Dt,Bb,Bt by 70 TDC counts, Db by 75 TDC counts,
Ct by 45 TDC counts) Anomaly not seen in other counters
9:46 AM end run 1122 87095 triggers to disk

09:54 AM Begin run 1123 to tape MIN213
Pb out BD Pbar-or delay=8ns
throughout much work by Dick/Bill parasitically studying timing signals
wioth scope
10:45 AM
MCR calls to tell us that the second E811 scrape is about to begin
end run 1123, 37131 triggers to disk

swap TDC module

11:05 AM begin run 1124 to disk
BD Pbar-or 8n Pb out MR still ON
TDC's look beautiful!
Dick Adds Pbar or TDC N=2, A=2 {TDC(11)--on the fnmine genmon, this was already
labeled as an upstream TDC, but this must predate bj's June 15th message; the
only current inputs to this TDC are 9,10,15,16 which are K-counters; the
pbar-or input goes through a LOT of delay cable to fit in the gate of this
module!}
Call MCR--only 1 pbar bunch shows any significant number of pbars! Did they
over scrape? "We don't think so--we're working on it"  They call back a
few minutes later to report that because of the low currents, their
instrumentation had trouble picking it up...but now they have it.
Now Dick begins to work on getting the new Kicker ADC's to read out
[ADC(133)-ADC(136) to read out.
D0 luminosity .06e30, protons ~3.5e9/bunch, pbar~3e9 (except bunch 5~.6e9)
12:38 PM MCR calls MR going off for ~12 hours
at event #38529 of run 1124
Dick fixes kicker ADC's [calibration in ADC(138)]
end run 1124
91976 triggers to disk  

2:27 PM move Pb in
Run a delay curve...concensus of Dick, Bill, Cyrus is to leave at 8ns

3:03 PM
Begin run 1125 to tape MIN214
BD pbar-or delay=8ns PB in No MR
[very quiet running...]
12:20 AM 22 January '96: beamtrig rate = 6Hz
1:20 AM end run 1125, 251501 triggers to tape

1:20 AM start run 1126 to MIN215
MR off Pb IN, BD Pbar or delay=8ns
4:18 AM end run 1126, 50479 triggers to tape

4:21 AM Begin run 1127 to tape MIN216
MR off PB IN BD Pbar or delay=6 (six) ns
[histograms suggest that this may reduce beam gas content rather 
substantially: from ~1% to .1%?? NHITS may increase slightly...will check
efficiencies after store ends...the check is the number of entries in
pbar adc multiplicity with 0 pbar counters firing, which, if I did the
arithmetic right, dropped from about 1% to about .1%]
4:48 AM MCR calls to report that they will resume MR operation at 5:00
4:50 AM restore MR gate (at event number ~412177)
5:14 AM MR operation still somewhat intermittent
5:30 AM beamtrig rate ~5 Hz
8:03 AM seps on 28944 triggers to tape store ends

Cyrus

Resent-Date: Tue, 23 Jan 1996 8:13:14 -0600 (CST)
Resent-From: SIGNORE@FNALV.FNAL.GOV
Resent-To:   sigNORE@DAUMI1.FNAL.GOV
Date: Tue, 23 Jan 1996 08:08:31 -0600 (CST)
From: CTAYLOR@FNALV.FNAL.GOV
Subject: store 4 report
Resent-to: SIGNORE@FNALV.FNAL.Gov
To: t864-l@fnmine.fnal.gov
Resent-message-id: <01I0CCRH8P78000EG4@FNAL.FNAL.GOV>
Message-id: <960123080831.25a81855@FNALV.FNAL.GOV>
X-VMS-To: IN%"t864-l@fnmine.fnal.gov"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

This is a report on MiniMax running during the fourth and final
E811 store.

People on shift include Jon Streets, Ken Delsignore and Cyrus Taylor;
Dick did a final check of timings just before seps went off.

Note that the store was 5x5, with missing bunches a6, p6 colliding
at C0.  The Main Ring was on for the entire store.

The first several hours of the store are used to map out a delay
curve: 50 K events Pb in/out at delays of 2,4,10,12 ns and 6ns Pb out.
NHITS appears to increase as the delay shortens.

1:09 PM Seps Off
Begin run 1128 to disk
BD pbar or delay=6 ns
Pb out
Initial D0 luminsity .64e30

1:24 PM  Double pulsing observed in Beamtrid/BDPbaror rate...
this is no doubt due to an unterminated cable someone used in the
past twenty four hours to check timing, and indeed I found more
than one such cable, but...no fix.  This is an intermitent problem
through the run

1:48 PM MCR calls--a little more scraping (event #55781)

1:58 PM end Run 1128 50743 triggers to disk
ship to fnalu and check efficiencies...seem nominal

2:07 PM start run 1129 to tape MIN217
BD pbar-or delay=10ns Pb out
2:08 PM scraping ends
2:59 PM end run 1129, 53803 triggers to tape

3:04 PM Begin Run 1130 to tape MIN218
BD pbar or 10ns Pb in
at ~event #83999:
Observe a spike in Kicker 1,2 TDC's: very sharp somewhat before 
the pbar signal.  Can't decipher it.  Briefly pull the pbar-or input
to that TDC module without terminating it--causes a second peak
in trig time plot to appear without ending the anomalous kicker spike.
Replace the pbar-or tdc input, trigger time again sharp.

3:51 PM end run 1130, 50448 triggers to tape

3:54 pm Begin run 1131 to tape MIN219
BDPbar-or 4 ns Pb in
4:39 PM end run 1131 51257 triggers to tape

4:43 pm begin run 1132 to tape MIN220
BDPbarOr 4 ns Pb out
5:31 pm end run 1132 with 52422 triggers to tape

5:35 begin run 1133 to tape MIN221
BDPbarOr 12 ns Pb out
6:26 pm end run 1133 with 50686 triggers to tape

6:30 pm begin run 1134 to tape MIN222
BDPbarOr 12 ns Pb in
7:20 pm end run 1134 with 50022 triggers to tape

7:21 pm begin run 1135 to tape MIN 223
BDPbarOr 2 ns Pb in
8:11 pm end run 1135, 50026 triggers to tape

8:15 pm begin run 1136 totape MIN224
BDPbarOr 2 ns Pb out
9:04 end run 1136, 50037 triggers to tape

9:08 pm start run 1137 to MIN225
BDPbarOr 8ns Pb in
0:50 AM 23 January 1996 end run 1137, 250011 triggers to tape

0:50 AM start run 1138 to MIN226
BDPbarOr 8 ns Pb out
4:43 AM end run 1138, 260572 triggers to tape
unfortunately, ct hits 'I' in global menu rather than run control; tape comes out of
drive, but I decide it is the better part of valor to reboot.
While this is going on, I run delay curves with various triggers.
This is complicated because the length of the MR cycle
changes during this period... in the end I decide:

5:40 AM begin run 1139 to tape MIN227
BDPbarOr delay=8ns Pb in
8:03 AM end of store end of run 1139 153037 triggers to disk