<!-- Title: Day shift. Sun Nov  5, 2000 -->
<!-- Leader: Young-Kee Kim -->
<!-- Ace: Greg Veramendi -->
<!-- Co1: Olga Lobban -->
<!-- Co2: Kai Yi -->
<!-- Co3: Slawek Tkaczyk (SOS) -->
<!-- Co4: &nbsp; -->
<!-- Co5: &nbsp; -->
<!-- Notes: -->
<pre>We still have the store. 
The luminosity : ~1E29. 
TOF and CLC people are preparing the special runs 
for TOF. 16 channels of the CLC electronics will be used 
to readout TOF). 
The rest of the CLC channels will be used for the Minimum 
bias trigger. 
 
Day shift's goal : 
  1. special run for TOF (COMMISSIONING_2E29) : 200 k events 
  2. Take a million events with COMMISSIONING_2E29 
  3. Take ~500 k events with Min Bias only trigger 
* Level-3 tagset 70 (which includes the COT reconstruction) 
  will be used. 
</pre>


<!-- Date: Sun Nov 5 08:53:35 2000 -->
TOF & CLC people are ready to take data for the TOF.  
<!-- Author: Young-Kee -->


<!-- Date: Sun Nov 5 08:55:23 2000 -->
 
SOC (silicon outside of the COT) is turned on.
<!-- Author: Young-Kee -->


<!-- Date: Sun Nov 5 09:09:11 2000 -->
<pre>Started run after:  
rebooting eb23 and eb24 
then a L3 processor node 1 froze up 
Ivan went and rebooted it.. 
I was foolhearty and decided that svt00 
would work for me when it wouldn't work for anyone else! 
of course it ended our run after 3.5k events.. 
removing it and restarting..</pre>
<!-- Author: Greg V. :: (run 103558) -->
<!-- Comment: Sun Nov  5 10;16;25 comment by...Greg Veramendi -->
<pre>error message:
(MLE) b0l3gate1.fnal.gov:main:9:05:18 AM->Host b0eb11.fnal.gov, task tRec_0
SCPU-P0-E-VrbReadFailed: Error reading VRB in slot 12 for event 3290.
The VRB had no event.
CT: 11/5/2000, 10:4'20"
4'20" 1 crate/s: b0svt00(120),  Done TO.[RXPT]
</pre>
<!-- Date: Sun Nov 5 09:18:13 2000 -->
<pre>Started new run without svt00 
after reset_crate b0svt06  </pre>
<!-- Author: Greg V. :: (run 103560) -->


<!-- Date: Sun Nov 5 09:36:40 2000 -->
<pre>Investigated problem with b0l2de00 crate. 
Doing a VME memory test to the Tracer data FIFO 
reproduced the stuck bit 0x100. 
Then various modules were reseated, which for 
a while made things much worse. 
Eventually, things were reseated such that the 
memory test that was failing now works. 
As there is a run in progress now, the full transfer 
test to the VRB cannot be done. 
If this test is successful, it should be possible to 
try again to use the Level 2 processors.</pre>
<!-- Author: patrick + nachtman -->
<!-- Comment: Sun Nov  5 10;42;26 comment by...Jane -->
I did the VRB test and it passed.  Then we tried to use the Level 2 processors in the run, and immediately got vme bus errors from the tracer on coldstart.  Using VISIONdemo to repeat the test that Jim did earlier shows the same problems with reading the memory.   The crate was removed from the run.  
<!-- Date: Sun Nov 5 09:39:31 2000 -->
<table><tr><td><a href=/elog/notebooks/2000/Sun_Nov__5_2000_Day.093924.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>fired bits: 46</a></td></tr></table>
<!-- Author: O. K. -->


<!-- Date: Sun Nov 5 09:44:24 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-517&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-517  width='250' align='top'></td><td>run: 103560 event: 20767 fired bits: 46</a></td></tr></table>
<!-- Author: Olga & Kai -->


<!-- Date: Sun Nov 5 10:12:48 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-519&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-519  width='250' align='top'></td><td>Run 103560:   COT superlayer 6 still has the strange bump at high start times.  This seems to be coming from Crate 7.</a></td></tr></table>
<!-- Author: Olga & Kai (O.K.) -->



<!-- Date: Sun Nov 5 10:33:06 2000 -->
so we ended the run with 200k events.. 
everything except for svt00, and level2 decision 
Part of the CLC electronics was hooked up to TOF!!!!!  
<!-- Author: Greg V. :: (run 103560 (19488)) -->


<!-- Date: Sun Nov 5 10:33:54 2000 -->
COT SL7 tripped.
<!-- Author: Young-Kee -->


<!-- Date: Sun Nov 5 10:41:47 2000 -->
finished testing wedge 2&3, checked 2 GeV signal bits and B0 marker for both wedges at the input to PreFred, all look ok. all the runs taken so far in this shift had the track trigger on wedge 2&3. I have just put them back to wedge 4&5.
<!-- Author: Ted Liu -->



<!-- Date: Sun Nov 5 10:43:44 2000 -->
<pre>I tried to switch partitions to do a qie calibration 
after working with Jane on the L2 decision crate.. 
and the partition did not close! quiting run control 
and starting the resource manager proxy to see if I 
can clean it up!</pre>
<!-- Author: Greg V. -->
<!-- Comment: Sun Nov  5 11;03;55 comment by...Greg V. -->
clean up successful..
<!-- Comment: Sun Nov  5 14;16;03 comment by...Olga & Kai (O. K.) -->
<br>
<br>
Run 103563:  QIE calibration was taken.  <br>
All looks normal (nothing has changed compared to previous QIE calibration).
<br>
<br>
Run 103565: COTCTT calibration was taken.<br>
All looks normal.<br>
<br>
<!-- Date: Sun Nov 5 11:00:16 2000 -->
Summary of Run 103560 (Trigger table COMMISSIONING_2E29) 
 
<pre>  1. 16 channels of CLC were hooked up to TOF 
  2. XFT wedge 2 and 3 are included in the trigger table. 
  3. Trigger rates : min bias & 2 towers - 32 Hz 
		     min bias & 1 plug tower - 16.4 Hz 
		     muon track (60 deg) - 0.3 Hz 
		     Track (wedge 2, 3)  - ~10 Hz 
  4. SOC included 
  5. Level-3 tag set 70 (COT reconstruction)
  6. 200 k events: 52 events/sec, dead time ~3.4% </pre>
<!-- Author: Young-Kee :: (run 103560) -->



<!-- Date: Sun Nov 5 11:04:27 2000 -->
<pre>RC crashed while trying to cold start.. 
Restarting.. 
</pre>
<!-- Author: Greg V. -->


<!-- Date: Sun Nov 5 11:25:05 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-522&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-522  width='250' align='top'></td><td>run: 103560  PEM & PHA In high Eta regions, there is 90% occapancy </a></td></tr></table>
<!-- Author: Olga & Kai (O.K.) -->
<!-- Comment: Sun Nov  5 15;20;20 comment by...R.J. Tesarek -->
These plots are consistent with beam losses ending up in the plug
calorimeter (the high eta region surrounds the beam pipe).  Further, beam gas events upstream of the plugs produce particles
which enter the very low eta towers of the hadronic sections of the calorimeter.  These type of events were seen, particularly in 
conjunction with large losses in the Tevatron which can be inferred from muon chamber and COT trips (see entry immediately 
below).
<!-- Date: Sun Nov 5 11:29:00 2000 -->
<pre>COT SL7 tripped. 
SL7 was off between event ~130k and ~172k. </pre>
<!-- Author: Young-Kee :: (run 103566 (1948e)) -->


<!-- Date: Sun Nov 5 11:47:17 2000 -->
Alan Sill will be the SciCO for the next ~2 hours.
<!-- Author: Young-Kee -->


<!-- Date: Sun Nov 5 12:05:48 2000 -->
CMX NW Wedge 21 tripped. Events between #429000-#539000 have 
no HV on this wedge. 
<!-- Author: S. Tkaczyk -->


<!-- Date: Sun Nov 5 12:11:17 2000 -->
just a few comments for XFT Pt trigger bits vs wedges: 
 
(1) when one looks for events triggered by Pt trigger bits, 
    very often one couldn't find a fitted track points to 
    the right wedge. This is likely due to fake Pt tracks: 
    i.e. when chamber occupancy is high in that region, 
    the noise pattern is such that it will form segments 
    in the FINDER, certain patterns can be linked into 
    high Pt tracks by LINKER this way. 
(2) when looking for these events with online event display, 
    you should enable raw COT hits to see if indeed the fired 
    wedge has high occupancy. of course, the best way to 
    find out this is to use event display offline where you 
    can enable XFT tracks (this is probably not yet avaiable 
    online). 
(3) this is esp. true for the beam data we took in the past 
    two days as only the higher Pt trigger bits were enabled 
    after FRED prescale. just think what's the chance to 
    get a real high Pt (say above 8 GeV) track in the real 
    collision. 
(4) to see if XFT really can assign tracks into correctly 
    Pt bin, at this point I think we can use cosmic ray  
    events. I have posted one example of such event two days 
    ago when we first got track trigger working and took 
    some cosmic ray events (rate of course was very low), 
    for that event, a reconstructed 8.9 GeV cosmic event 
    fired 2, 4, 8 GeV Pt bits, but failed to do so for 
    12 GeV Pt track trigger bit. 
(5) even for cosmic events, there is still a good chance 
    for noises in the chamber to fake high Pt tracks. thus 
    simply looking at reconstructed tracks doesn't always 
    tell you which wedge should fire. 
(6) so we when look at Pt spectrum online, high Pt physics 
    is likely dominated by high chamber noise occupancy,  
    i.e. E&M physics. it's still physics though. 
 
in any case, we should take as much data as possible with 
all track trigger bits enabled before the next trailing edge 
of long beam abort gap (~ 4month?), so that we will have 
enough data to chew on while licking our wounds in order to  
survive the long cold Batavia winter and the beam abort  
gap...  
<!-- Author: Ted Liu -->


<!-- Date: Sun Nov 5 12:25:18 2000 -->
Run ended with svt02 done TO 
could not recover..  
Greg F arrives with a prom fix to possibly   
make low P_T tracks go through FRED and  
asks for a new run with commissioning_2e29[1,70]. 
The shift crew graciously agrees. 
Run number = 103568
<!-- Author: Greg Feild -->
<!-- Comment: Sun Nov  5 12;27;38 comment by...Alan SIll -->
Had gotten to 0.6M events bevore the SVT timeout.  Greg says that min_bias will not work with this PROM version, so we cannot run more anyway with this PROM... we have been shanghaied!


<!-- Date: Sun Nov 5 12:29:52 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-524&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-524  width='250' align='top'></td><td>Run 103082 was a COMMISSIONING_COSMIC run,  and no protons or antiprotons were in the Tevatron (see logbook for Day shift, Nov. 2) PEM: In high eta regions, the occupancy is <30%, compared to 90% occupancies we see when there are collisions (see previous entry today) There still seems to be an asymmetry in the occupancies between low eta and high eta regions of the Plug.</a></td></tr></table>
<!-- Author: Olga & Kai -->
<!-- Comment: Sun Nov  5 15;23;18 comment by...R.J. Tesarek -->
These data indicate that beam was present during some of the 
cosmic ray running.  Often there is beam in the accelerator
without the shift crew aware of it.  Most (if not all) cosmic
ray runs have some beam contamination.
<br>
<!-- Date: Sun Nov 5 12:31:11 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-525&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-525  width='250' align='top'></td><td>Run 103082 PHA</a></td></tr></table>
<!-- Author: Olga & Kai -->


<!-- Date: Sun Nov 5 13:03:55 2000 -->
<pre>I just got back and now we are finishing 
the Min_bias run.. again no fib01, 
For now on we are to include fib01 as a  
part of the normal run config. 
 
Also I forgot to set the cotdac voltages 
I set them at about 90k events..</pre>
<!-- Author: Greg V. :: (run 103569 (0x19491)) -->
<!-- Comment: Sun Nov  5 13;37;07 comment by...Greg V. -->
<pre>ran to about 380k events
stopping now to do some special silicon runs
</pre>
<!-- Date: Sun Nov 5 13:08:38 2000 -->
Greg Feild has completed his test (claims it seems to work) and has returned the previous PROMs so we can continue the min bias run.  
<!-- Author: AFS -->


<!-- Date: Sun Nov 5 13:17:34 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-526&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-526  width='250' align='top'></td><td>proof that trigger bits 44, 45, etc. fire when using Greg's PROM change. (Since it removes prescaling and masking entirely, this is not surprising!)</a></td></tr></table>
<!-- Author: Alan Sill -->


<!-- Date: Sun Nov 5 13:22:22 2000 -->
CMX tripped again around event 247K
<!-- Author: Alan Sill :: (run 103569) -->
<!-- Comment: Sun Nov  5 13;28;35 comment by...AFS, ST -->
Back on at about 315K -- same wedge as before, NW21 CMX



<!-- Date: Sun Nov 5 13:44:25 2000 -->
Starting special silicon runs... up to now, have used 
default setting of 5 for preamp NMOS input bias current 
(ISEL 1-3 = 101) for all runs.  Will begin with changing 
this to 6 (=110) and look to see effect on cluster sizes 
and gain.  (In principle, the chip is more sensitive to 
this adjustment in terms of risetime and gain than they 
are to the bandwidth setting we have been adjusting up to 
now.)
<!-- Author: AFS -->



<!-- Date: Sun Nov 5 15:15:11 2000 -->
Mike Church stopped by to inquire about our progress and 
to let us know that they will be doing collimator studies 
beginning at 4:00 am Monday morning (assuming that the store 
survives that long).  If this is not OK with us, we have to 
call them this afternoon or evening to let them know!
<!-- Author: Alan -->


<!-- Date: Sun Nov 5 15:15:46 2000 -->
The event rate dropped to 12 Hz,  
which sometimes means a problem with the EVB 
I paged EVB pager, and Ilya called back,  
we found that eb20 was spewing out error messages 
by logging in using minicom. 
Had to reset eb20, and clean up EVB  
<!-- Author: Greg V. :: (run 103575) -->
<!-- Comment: Sun Nov  5 15;26;44 comment by...Alan -->
Event rate is still low (12 Hz) in run 103576, even after
cleaning up EB as instructed by Ilya.

<!-- Comment: Sun Nov  5 15;29;21 comment by...Greg V. -->
<pre>this didn't seem to work. 
The event rate is still ~12 Hz, and
when I log into eb20 (using minicom), 
I still see the same messages.. 
Paging Ilya again..</pre>


<!-- Date: Sun Nov 5 16:08:13 2000 -->
<font color=red>Shift Summary: </font><pre>Traced problem with SVT interface board test to stuck bit on 
TRACER 
Greg (by magic) got the muon track trigger to work 
Alan Sill is in process of a few more SVX special runs (held up 
by an EVB problem) 
J. Proudfoot reporting for Alan</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   103558-103576
Delivered Luminosity   some  pb-1
Acquired Luminosity    some  pb-1
Efficiency             Medium
   
</td></tr></table></pre>
<!-- Author: J. Proudfoot -->