<!-- Title: Owl shift. Sat Apr 21, 2001 -->
<!-- SciCo: Alan Sill /G. Pauletta -->
<!-- DAQAce: Francesco Palmonari -->
<!-- MonAce: Michael Kirby -->
<!-- CO: K. Yamamoto /M.Henneke -->
<!-- OpManager: Steve Hahn -->
<!-- Notes: -->
<pre>At start of shift: 
Beam is coming and going; 
Clock problems, Steve H. is working on them from home; 
We're down to 2 working muon trigger tables; 
L2 folks are working on jet clustering, has central, L1, L2 crates; 
Sedov doing hardware work, will do plug sourcing soon; 
... other than that, everything's fine! </pre>


<!-- Date: Sat Apr 21 00:33:14 2001 -->
a single proton bunch was injected shortly after the biginning 
of the owl shift. Muon chambers tripped and wee put to standby. 
MCR told us they would keep the bunch in all night for accelerator studies. We'll wait for a while before turning muon chambers back on.
<!-- Author: Giovanni Pauletta -->


<!-- Date: Sat Apr 21 00:45:22 2001 -->
Steve Hahn calls to say that the clock should be OK now.  We 
are in the middle of a TOF calibration run, will call him 
back when this is done to have him teach the ace how to set clock 
to free run mode if necessary.
<!-- Author: A. Sill -->


<!-- Date: Sat Apr 21 01:08:11 2001 -->
<pre>Alex Sedov has cured his H/W problems. 
Wants the plug crates and the H/W event builder for two hours.</pre>
<!-- Author: Giovanni Pauletta -->


<!-- Date: Sat Apr 21 01:11:26 2001 -->
Try putting clock back in "Freq Lock" (or TeV-RF Lock) mode using clockGUI. 
<p> 
First, tried doing this from home.  After fixing some X-window problems, find it take a long time with Sergeui's cute pictures over a modem.  Should change this. 
<p> 
Finally, give up and have ace (Francesco) change clock state.  But find that in fact if we put clock back into TeV-RF Lock mode (as it is called under the PCC tab in clockGUI), the clock always has a sync error.  Putting the clock into either Normal mode or Free Run mode clears the errors.  Decide to put clock into Free Run mode to avoid errors overnight if TeV does actions such as changing the beam energy.  This means we cannot take real data, but we are not taking real data anyway.  I will talk with Steve Chappa about this tomorrow.
<!-- Author: Steve Hahn -->


<!-- Date: Sat Apr 21 01:18:35 2001 -->
<pre>>> run 112764 is the TOF-QIE calibration 
 
>> run config. used is: ACE_TOF_QIE_NEW 
 
-> b0wcal06 not included because not responding to vxlogin or minicom
   -> we page the expert </pre>
<!-- Author: Mirko+Francesco :: (run <a href='/cgi-bin/runSummaryRun.cgi?112764' target=_top>112764</a>) -->
<!-- Comment: Sat Apr 21 01;51;46 comment by...francesco + greg -->
<pre>>> Allowed from experts to reset the cal crates:

40 /cdf/people1/cdfdaq % reset_crate b0pcal05
Crate b0pcal05 reset channel is 37
Crate reset complete
41 /cdf/people1/cdfdaq % reset_crate b0wcal06
Crate b0wcal06 reset channel is 22
Crate reset complete
42 /cdf/people1/cdfdaq % reset_crate b0ccal02
Crate b0ccal02 reset channel is 2
Crate reset complete
43 /cdf/people1/cdfdaq % reset_crate b0ccal11
Crate b0ccal11 reset channel is 11
Crate reset complete


>> will re-do the TOF-QIE calib.</pre>


<!-- Comment: Sat Apr 21 02;02;14 comment by...Greg & company -->
<pre>We noticed that pcal05, ccal02,11 were both in a similar
state, after we had paged the expert..

We tried checking Voltman on b0dap23, and it comes
up blank. But when using the netscape on the acnet pc, 
voltman seems to work!?!?!? The voltage seems to have been
steady for at least the last 12 hours.

Maybe these crates were left in a weird state by the last
shift... dunno..
</pre>
<!-- Date: Sat Apr 21 02:00:02 2001 -->
<pre>>> (after cal crates reset) 
>> FULL TOF-QIE calibration is run 112769 </pre>
<!-- Author: francesco :: (run <a href='/cgi-bin/runSummaryRun.cgi?112769' target=_top>112769</a>) -->



<!-- Date: Sat Apr 21 02:21:17 2001 -->
we are done with jet trigger interface board debugging for the day....it looks like we are down to errors happening every 50-100k events, which is a BIG improvement from the failure rates we had before. We still need to investigate the cause of some sporadic failures and of the wrong eta/phi cluster seed information (see L2cal trigger e-log for more information). 
We will work more on that tomorrow.
<!-- Author: monica and john -->


<!-- Date: Sat Apr 21 03:12:01 2001 -->
<pre>Brought muon voltage back up to test the muon trigger table. 
CMU wedge 13 & 14 tripped, NO AUDIBLE ALARM WAS HEARD!!! 
 
I noticed it after a while.. 
 
eventually brought those wedges back up..</pre>
<!-- Author: Greg V. -->


<!-- Date: Sat Apr 21 03:45:43 2001 -->
IFIX frozen on vnode1.  Can't minimize, activate, or control 
any of the IFIX windows on that machine, even though the 
computer itself is OK.  The "IFIX startup" window does  
restore and minimize, but selecting the "shut down IFIX" 
option only results in a message saying "you do not have  
privilege to shut down IFIX".  Eventually, we shut down the 
machine and rebooted it.  (Had to page JC to get the password 
to start up IFIX after the machine came back up...)
<!-- Author: Alan Sill and Greg V. -->


<!-- Date: Sat Apr 21 04:04:33 2001 -->
Either coincidentally or by some unknown connected cause, we also have run into frozen-window problems on 2 other computers (b0dap59 and one that Giovanni was using -- didn't get its node name)... had to reboot each of these, too, as X-windows resets etc. did nto produce a response.
<!-- Author: AFS -->


<!-- Date: Sat Apr 21 04:12:27 2001 -->
<pre>CMU01, SVT02, and l2gl00 stopped responding to vxlogin or minicom  
performed reset_crate on all three..  
CMU01 and SVT02 recovered...  
still can't communicate to l2gl00  
I wanted to manually reset it,   
but I couldn't figure out where it lives!  
so removing it from the run..  
we have no idea what the consequences of this are... </pre>
<!-- Author: Greg V. -->
<!-- Comment: Sat Apr 21 05;12;22 comment by...AFS -->
(b0l2gl00 does not seem to be physically in the location indicated on the list of crates posted.  Should be in 2RR29C1
top.  That crate exists but the cpu module is missing... perhaps the L2 people took it out to work on it?)
<!-- Comment: Sat Apr 21 09;16;38 comment by...patrick -->
b0l2gl00 has NEVER been installed
<!-- Comment: Sun Apr 22 00;29;03 comment by...AFS -->
Do we get some sort of prize for noticing this??
<!-- Date: Sat Apr 21 05:11:18 2001 -->
<pre>>> run 112790 
 
-> run config is ACE_CALORIMETER_MINIMAL 
-> trig table is MUON_TEST_4_4[5,101] 
 
 just a try to see if we can run something  
 with the SOFTWARE EVB.  
 However in this run muon crates & muon trigger 
 wasn't there. </pre>
<!-- Author: Greg + Francesco :: (run <a href='/cgi-bin/runSummaryRun.cgi?112790' target=_top>112790</a>) -->
<!-- Comment: Sat Apr 21 05;31;51 comment by...noi -->
<pre>2 runs before this one:

112786:	EVB errors

112787: Silicon & muons errors -> take them out after this run</pre>
<!-- Comment: Sat Apr 21 05;41;29 comment by...greg francesco -->
<pre>ERRORS from the previous 2 runs :

from 11278
---------

 /cdf/code-common/cdfonline/errmon/log/daq % ls -alF | grep 112787.*
grep: No match.
29 /cdf/code-common/cdfonline/errmon/log/daq % more errorfile112786.log
Error Handler Log File
All timestamps are referred to CT
CT: 4/21/2001, 4:41'23"
Partition:0 Run number: 112786 (0x1b892)
(RC) Config -> READY
(MLE) b0l3gate1.fnal.gov:Sender:4:42:47 AM->Could not start new run 112786.
(MLE) b0l3gate1.fnal.gov:main:4:42:48 AM->Host b0eb10.fnal.gov, task tsmHot
SM-P0-E-ScpuUnresponsive: One or more SCPUs failed to respond to Define Partition. Check
SCRAMNet.
(RC) Reset -> START
43'27" b0dau32.fnal.gov:csl_mon_send:4:43:28 AM->Data file for partition 0, run 112786 was closed with zero events.
 [MLW]
(MLE) b0dap57.fnal.gov:AWT-EventQueue-0:4:47:39 AM->Strange (but not fatal) Run Configuration selections:
Unusual setting for l3MaxProc 1, usual setting is 8
 
47'40" -----Status cleared----
47'40"
(RC) Reset -> IDLE
(MLE) b0dap57.fnal.gov:AWT-EventQueue-0:4:49:16 AM->Strange (but not fatal) Run Configuration selections:
Unusual setting for l3MaxProc 1, usual setting is 8
                                                                                         



from 112787
------------

Error Handler Log File
All timestamps are referred to CT
CT: 4/21/2001, 4:42'58"
Partition:1 Run number: 112787 (0x1b893)
(MLE) b0cmx01:Messenger:4:43:11 AM->Resetting card in slot 3 failed
(MLE) b0cmx01:Messenger:4:43:11 AM->Statechange failed
(RC) Config -> ERROR
(MLE) b0fib06:Messenger:4:43:16 AM->Error Initializing HDI Slot 9 Chan 0
(MLE) b0fib06:Messenger:4:43:16 AM->Statechange failed
(MLE) b0fib02:Messenger:4:43:21 AM->Error Initializing HDI Slot 18 Chan 0
(MLE) b0fib02:Messenger:4:43:21 AM->Error Initializing HDI Slot 18 Chan 5
(MLE) b0fib02:Messenger:4:43:21 AM->Statechange failed
(RC) Reset -> START
44'6" b0dau32.fnal.gov:csl_mon_send:4:44:06 AM->Data file for partition 1, run 112787 was closed with zero events.
 [MLW]
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:54:20 AM->Partitionable action detected: removeCrate CMX_EAST_01
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:54:52 AM->Partitionable action detected: removeCrate FIB_SVX_02
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:54:52 AM->Partitionable action detected: removeCrate FIB_SVX_06
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:54:55 AM->Partitionable action detected: removeCrate FIB_ISL_01
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:55:09 AM->Partitionable action detected: removeCrate VRB_ISL_06
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:55:09 AM->Partitionable action detected: removeCrate VRB_ISL_07
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:55:09 AM->Partitionable action detected: removeCrate VRB_ISL_08
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:55:09 AM->Partitionable action detected: removeCrate VRB_SVX_00
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:55:09 AM->Partitionable action detected: removeCrate VRB_SVX_01
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:55:09 AM->Partitionable action detected: removeCrate VRB_SVX_02
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:55:10 AM->Partitionable action detected: removeCrate VRB_SVX_03
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:55:10 AM->Partitionable action detected: removeCrate VRB_SVX_04
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:55:10 AM->Configurable action detected: useSrc
false
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:56:09 AM->Partitionable action detected: removeCrate SVT_FANOUT_07
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:56:09 AM->Partitionable action detected: removeCrate SVT_FITTER_06
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:56:09 AM->Partitionable action detected: removeCrate SVT_TRACKING_02
(MLE) b0dap59.fnal.gov:AWT-EventQueue-0:4:56:10 AM->Partitionable action detected: removeCrate SVT_TRACKING_03
56'33" -----Status cleared----
56'33"
(RC) Reset -> IDLE                                                                       

</pre>
<!-- Comment: Sat Apr 21 08;01;00 comment by...Franz & Sav -->
<pre>The error on SVX was due to 3 ladders in OFF status.</pre>
<!-- Date: Sat Apr 21 05:20:48 2001 -->
<pre>>> run 112791 
 
-> included muons and muon trigger -> busy timeouts** 
 
(**) almost immediatly after the start of the run 
      
-> take out b0cmx01 -> failed card reset for slot3 
 
-> resetted b0mutr00 
 </pre>
<!-- Author: Greg & Francesco :: (run <a href='/cgi-bin/runSummaryRun.cgi?112791' target=_top>112791</a>) -->
<!-- Comment: Sat Apr 21 08;07;35 comment by...Greg V. -->
<pre>for CMX01:
I looked at the cards included in the crate,and it
looks like slot 5 is in the crate map, but not in the Run
Control crate set. And the RC crate set shows a card in slot
3, but there doesn't appear to be a card there. I issued a
bus reset twice and it didn't appear. Maybe someone got mixed
up?</pre>
<!-- Date: Sat Apr 21 05:24:55 2001 -->
<pre>>> run 112796 
 
-> as before but with trig. table: MUON_SIMPLE_4_4[1,97]</pre>
<!-- Author: greg francesco :: (run <a href='/cgi-bin/runSummaryRun.cgi?11795' target=_top>11795</a>) -->




<!-- Date: Sat Apr 21 06:00:53 2001 -->
<pre>Trying to look something up about silicon 
and discovered that the link on the ace web page 
is no longer valid: 
Running the SVX as an ACE 
 
please update this.</pre>
<!-- Author: Greg V. -->


<!-- Date: Sat Apr 21 06:22:26 2001 -->
<pre>finally got a run going!! 
removing cmx, silicon, svt, xft linker, mutr 
trying to understand the problems with them in another partition 
 
run ended with: 
(MLE) b0ccal03:Messenger:6:10:08 AM->Runtime Error 1, Event 2840: See nonsequential event number (old 7, new 4) in L2 message 
(MLE) b0ccal00:Messenger:6:10:09 AM->Runtime Error 1, Event 2840: See nonsequential event number (old 7, new 1) in L2 message                         
(MLE) b0ccal03:Messenger:6:10:08 AM->Runtime Error 3, Event 2840: SMXR in slot 3 is not responding, header 0x0x3ffe39b 
(MLE) b0ccal06:Messenger:6:10:09 AM->Runtime Error 2, Event 2840: SMXR in slot 3 is not responding, header 0x0x3e0037e 
(MLE) b0ccal01:Messenger:6:10:09 AM->Runtime Error 1, Event 2840: See nonsequential event number (old 7, new 4) in L2 message     
 
and so on... 
                     
</pre>
<!-- Author: Greg and Francesco :: (run <a href='/cgi-bin/runSummaryRun.cgi?112798' target=_top>112798</a>) -->
<!-- Comment: Sat Apr 21 07;19;06 comment by...Greg V. -->
<pre>Many crates went into error states:
b0ccal05, wcal00-03, cot00-09
cannot vxlogin or minicom!
</pre>
<!-- Date: Sat Apr 21 06:30:10 2001 -->
<pre>There is one hot channel in the calorimeter.  
It seems to be Eta tower +7, phi wedge 21 in the  
CHA East RPMT. </pre>
<!-- Author: Martin Hennecke :: (run <a href='/cgi-bin/runSummaryRun.cgi?112789' target=_top>112789</a>) -->
<!-- Comment: Sun Apr 22 16;45;04 comment by...R. Erbacher -->
If you see such a thing can you please post the plot from which you've drawn your conclusions?  It would help for the experts
to see how bad a problem it really is.  Thanks.
<!-- Comment: Sun Apr 22 16;45;31 comment by...R. Erbacher -->
Never mind... see below.
<!-- Date: Sat Apr 21 06:34:07 2001 -->
<pre>>> trying to run the silicon with SOFTWARE EVB 
   (NB: the Hardware evb is not avaible now) 
   problems with  
   fib02 [HDI Slot 18 Chan 0] 
   fib06 [HDI Slot 9  Chan 0]</pre>
<!-- Author: francesco :: (run <a href='/cgi-bin/runSummaryRun.cgi?112802 and 112805' target=_top>112802 and 112805</a>) -->
<!-- Comment: Sat Apr 21 07;19;35 comment by...fra -->
<pre>checkout also the small run 112813
only b0fib01 included... so to at 
least run something</pre>
<!-- Date: Sat Apr 21 06:41:57 2001 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2001&action=view&page=-700&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2001&action=view&page=-700  width='300' align='top'></td><td>The hot tower is in the upper right corner.</a></td></tr></table>
<!-- Author: Martin Hennecke -->
<!-- Comment: Sun Apr 22 18;16;21 comment by...R. Erbacher  -->
Under investigation... (wedge=21)
<!-- Date: Sat Apr 21 06:42:27 2001 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2001&action=view&page=-700&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2001&action=view&page=-700  width='300' align='top'></td><td>The hot tower is in the upper right corner.</a></td></tr></table>
<!-- Author: Martin Hennecke -->


<!-- Date: Sat Apr 21 06:46:54 2001 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2001&action=view&page=-701&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2001&action=view&page=-701  width='300' align='top'></td><td>Hot channel described above.  This wedge has a hit in almost every event. </a></td></tr></table>
<!-- Author: Yamamoto -->


<!-- Date: Sat Apr 21 06:56:22 2001 -->
<pre>Having problems trying to get the plug source working.... 
tsi00 gives error on activate: 
 
(RC) Setup -> READY 
(MLE) b0pcal05:Messenger:6:52:48 AM->Runtime Error 2, Event 1: SMXR in slot 5 is not responding, header 0x0x3bfe586 
(MLE) b0pcal05:Messenger:6:52:49 AM->Runtime Error 4, Event 1: SMXR in slot 6 is not responding, header 0x0x3bfe686 
(MLE) b0pcal05:Messenger:6:52:49 AM->Event 1: Bunchcounters in slot 15 and slot 
17 disagree (at least) 
(MLE) b0pcal05:Messenger:6:52:49 AM->Runtime Error 5, Event 1: Bunch counter mismatch, mismatch count = 10 
(MLE) b0tsi00:Messenger:6:52:49 AM->TS failed to Recover (State 2)               
 
logging into tsi crate I get: 
Messenger: processStatechange Activate [0] 
Starting run 0 at 987853968 
TM_wrap: ACTIVATE 
Configuring CSR handle 
Configuring RAM handle 
Resetting SCRAMnet moduleReset of SCRAMnet Module Complete. 
Status: 
Node ID 40 
Rx : 1 
Tx : 0 
Online : 0 
Outstanding Errors: 
CD 0 
Receiver Overflow 0 
Tx Retry Timeout 0 
Fiber Bypass not connected 0 
p_flag=1 
TM_wrap: call tm_start_flow 0 
Sent ack to Run Control: 0 ERROR ERROR 
TS failed to Recover (State 2) 
Messenger: processStatechange Abort [0] 
Sent ack to Run Control: 0 IDLE SUCCESS 
Messenger: processStatechange Reset [0] 
TM_reset partition 0 
TM_wrap: END, call tm_stop_partition 0 
p_flag after end 1 
TM_wrap: END  end 
Semaphore Id        : 0xc60ae8 
Semaphore Type      : BINARY 
Task Queuing        : PRIORITY 
Pended Tasks        : 0 
State               : EMPTY 
  
  
     ts pollster stops ...  partition 0 at slot 3 
  
     RUN SUMMARY: partition 0 
 0 event(s) loaded 
 0 unread event(s) 
 0 DONE Timeout(s) handled 
 0 time(s) flow stopped 
 0 time(s) partition flushed at request of SM 
 0 time(s) partition flushed at request of TM 
 0 event(s)  since last stop flow 
 0 event(s) processed since last stop flow 
  
Trigger Manager stopped! 
p_flag after reset:0 
Messenger: processPartition 2 
This is a multipartition crate - adding partition 2                      
</pre>
<!-- Author: Greg V. :: (run <a href='/cgi-bin/runSummaryRun.cgi?112812' target=_top>112812</a>) -->
<!-- Comment: Sat Apr 21 07;00;41 comment by...Greg V. -->
<pre>we tried to reboot the trigger crates because I saw a bunch
of errors on them. That didn't seem to help..
rebooting pcal05 to see if that will do the trick.
</pre>

<!-- Comment: Sat Apr 21 07;06;46 comment by...Greg V. -->
<pre>tried to start another run, but none of the pcal's would
activate message in crate:

Messenger: processStatechange Activate [0]
Starting run 12 at 987854531
Opening file >>/cdf/code-common/cdfonline/smx_calib/smcalibb0pcal05.txt<<

now pcal07,08,10,11 have turned red on vxworks display...
logging into pcal07 I get the following message:
evt 1, sending 16384/822632 bytes         

over and over again...

it just gets stranger and stranger!
I guess I'll just reboot them....</pre>

<!-- Comment: Sat Apr 21 07;11;09 comment by...greg -->
<pre>There seemed to be a leftover task:
Readout_CalFER_calib      9e2ff8 200 READY        201d80   9e2d60  300002     0

it is gone after rebooting..
</pre>




<!-- Date: Sat Apr 21 07:42:15 2001 -->
By paging through the IFIX screens one by one looking for 
anything that had to do with the COT, we finally found COSWB, 
COSWT, CONWB, CONWT AC tripped off.  This was apparently due 
to a drip sensor rack protection trip that caused NO AUDIO ALARM 
of any sort.  Got the cryo tech to reset this, and now these 
racks are all back up.
<!-- Author: AFS -->


<!-- Date: Sat Apr 21 07:44:09 2001 -->
<pre>Alan noticed that the west side cot and Wcal crates had tripped. 
They are back online now... 
 
Alex went to his office as soon as things are working again 
here we are supposed to call him, if before the 8am meeting.. 
 
cot09 failed to reset card in slot 7-> Bus reset recovered it.. 
 
got a TS failed to Recover (State 2) error.. 
with pcal01,02,04,05,07,08,10,11 giving busy,[RXPT] 
 
Alan seems to think cleanup evb will help... 
</pre>
<!-- Author: Greg V. :: (run <a href='/cgi-bin/runSummaryRun.cgi?112815' target=_top>112815</a>) -->
<!-- Comment: Sat Apr 21 08;00;38 comment by...greg -->
only i'm not using the Hevb, i'm using Sevb!
I get: TS failed to Recover (State 2)
I went over to the tsi, and I saw the same state for my
partition. that Alex had when we were trying to debug
the same problem. There is an error state in the tsi00:
L1:2
L2:1
BO:1
Cal:0
error light is on..

tried in parition 4 and got the same errors...

<!-- Date: Sat Apr 21 07:59:32 2001 -->
<font color=red>Shift Summary: </font><pre>Lousy shift. 
 
Tried out 2 new muon tables (TEST_MUON_4_4[5,101] and  
SIMPLE_MUON_TEST_4_4[1]), which didn't work. 
 
L2 folks had moderate success (see their logbook and entry 
above), but L2 global cpu is MIA... (probably OK, but it would  
be nice to know!).  Plug sourcing greatly interrupted by busy 
timeouts -- got some done, but not all. 
 
COT crates etc. taken offline for ~40 mins by silent rack  
protection trip, found by paging through IFIX. 
 
Clock still cannot be synched with beam. 
 
Next shift: please figure out what to do about muon tables, 
try to complete calibrations, fix the clock, and get a more 
complete plan for the rest of the weekend!</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   various, nothing useful
Delivered Luminosity   0  pb-1
Acquired Luminosity    0  pb-1
Efficiency             100
   
</td></tr></table></pre>
<!-- Author: Alan Sill -->


<!-- Date: Sat Apr 21 07:59:40 2001 -->
<pre>Layer 0 of SVX wedges 6 and 7 Bulkhead 2 were off. Also 
later 2 of bulkhead 2 wedge 8. 
This explains the error messages in initialization. </pre>
<!-- Author: Francesco & Saverio -->