<!-- Title: Day shift. Wed Oct  4, 2000 -->
<!-- Leader: John YOh -->
<!-- Ace: Varganov, Kirby -->
<!-- Co1: Bryan Ward -->
<!-- Co2: DongHee Kim -->
<!-- Co3: &nbsp; -->
<!-- Co4: &nbsp; -->
<!-- Co5: &nbsp; -->
<!-- Notes: -->
<pre>Initial rad readings 
1.431	1.465	30.07	36.26 
 
Supervised Access plan : 
	0800 to 1500/1700  Move Plug in 
	15/1700 to 2000	Repairs (ADMEM, COT-TDC, XTC, CMP bypass 			surgery, SVX-PS, cable, test, etc 
 
DAQ plan : 
	Morning	Find out slowdown problem 
	Early PM : L2 (Feild), other crate work 
	6PM --Get DAQ (esp L1/L2) working to make sure that 
		Access repair are successful (and did not 
		cause any new problem)</pre>


<!-- Date: Wed Oct 4 10:50:01 2000 -->
<pre>The 2 MCS View Nodes in the control room is being upgraded from iFIX 2.2 to IFIX 2.21. We have verified that all the needed plots, graphs, tables, etc for both the MCS system and the Gas/Cryo/utilities are functioning properly.</pre>
<!-- Author: John Yoh, Kevin Burkett, Mark Knapp -->


<!-- Date: Wed Oct 4 13:09:07 2000 -->
<pre>We had a problem with event ID mismatch in the plug for the run 100330. We stoped the run and started a new one.</pre>
<!-- Author: Alexei -->


<!-- Date: Wed Oct 4 13:47:30 2000 -->
<pre>Storage shed west bottom flammable gas head latched into trouble 
again. Reading is OK right now.</pre>
<!-- Author: Doug Benjamin -->


<!-- Date: Wed Oct 4 13:53:24 2000 -->
SVT_07 and SVT_01 are powered off. I did not interrupt the run
<!-- Author: Alexei  :: (run 100331) -->


<!-- Date: Wed Oct 4 15:02:58 2000 -->
<pre>This morning until about 1pm there where several tests done to 
understand the event id mismatch problem. 
 
We ran with a large system and the hardware event builder. 
 
The exponential drop in the readout rate is attributed to the  
flood of error messages that are written out when we see the 
event id problem in the vrb crate. Steve T is now sending these 
messages to the error handler so the shift crew will now be able  
to see the error condition more clearly. 
 
When we started we saw event id problems early in the run. 
The crates were rebooted to load code that checks to see if the tracer fifo is not almost full before sending the event. 
 
After booting the crates we started to see problems reading out 
the COT crates (we were getting buss errors) - this is believed 
to be related to the fact that the DACs were probably set to  
zero after rebooting and we were flooded with noise hits. 
 
Steve T will add code to the scanner cpu that will ensure that  
he does not try to readout the fifo past the end of valid addresses. This is believed to be causing the bus errors we saw when reading out the COT crates.  
 
It still has to be understood why the data size was incorrect  
in the vrb.  
 
Arnd M will install code to check that the tracer fifo is empty 
before sending data.  
 
After releasing the trigger crates we started a calib continuous 
run and we did see the event id problem show up: 
 
(ML) b0l3gate1.fnal.gov:main:1:34:49 PM->Host b0eb11.fnal.gov, task tRec_0 
SCPU-P4-E-TracerEventId: Event 107910, crate 85 has Tracer event ID of 5 instead of 6. 
 
(ML) b0l3gate1.fnal.gov:main:1:34:49 PM->Host b0eb11.fnal.gov, task tRec_0 
SCPU-P4-E-TracerEventId: Event 107911, crate 87 has Tracer event ID of 8 instead of 7. 
 
after that we got complaints about crate 87 for all events.... 
 
</pre>
<!-- Author: Frank Chlebana -->
<!-- Comment: Thu Oct  5 11;53;19 comment by...Steve T -->
I checked the SCPU readout code and found that the reading would never go outside the 64K of VME addresses assigned to the fast output FIFO. The code masked the byte count from the event header with 0xffff. The bus errors must have had some other cause.

<!-- Date: Wed Oct 4 15:04:51 2000 -->
<pre> 
    At 2:30 pm the Muon HV PC was rebooted and the  
    HVMON++ was restarted again. During the ramping up 
    of the voltages wedge 9,10 South West and 21 North 
    West tripped. Now we are working on that 
  
    A. Gallas & Tom Lecompte 
 
 
</pre>
<!-- Author: Abraham Gallas -->


<!-- Date: Wed Oct 4 15:14:50 2000 -->
<pre> After some work Tom managed to fix the HV problems 
 in wedges 9,10 South West. We can not fixed  wedge  
 21, this corresponds to the miniskirt which has been 
 installed in the Nort West side of the detector. 
 
</pre>
<!-- Author: Abraham Gallas -->


<!-- Date: Wed Oct 4 15:40:18 2000 -->
After about 40 min of running Run Control I got an error message "java.lang.OutOfMemoryError" which is memory leak.
<!-- Author: Alexei -->


<!-- Date: Wed Oct 4 15:52:31 2000 -->
<font color=red>Shift Summary: </font><pre>Rad sum 0/0/0/0  (Apparantly reset) 
 
Supervised access in progress (west plug done; East in 
Progress). 
 
</pre> 
<br><b>End of Shift Numbers</b>
<table><tr><td width=60% align=left>
<b>CDF Run II <p></b>                       
<pre>
Runs                   
Delivered Luminosity   0  pb-1
Acquired Luminosity    0  pb-1
Efficiency             
   
</td></tr></table></pre>
<!-- Author: John Yoh -->


<!-- Date: Wed Oct 4 16:04:57 2000 -->
<pre>The TS firmware has been updated in all 8 TSs. 
This update should make myron mode work with L1 
Early.  Note that when using L1 Early, you need to 
set IGNORE_BC as well.  </pre><font color=red><cite>(Entry started on Wed Oct  4 16:04:53 2000)</cite></font>
<!-- Author: Andrew Martin -->


<!-- Date: Wed Oct 4 16:28:13 2000 -->
<p>B0COT14 fails the VRB link test. An extra byte is written 
to event_data[23:16] at the beginning of the event, causing 
all of the data words to be corrupted. I've included some of 
the error messages below. 
 
<p>Changing the VRB didn't fix the problem. When I swapped 
channels 3 and 4 on the VRB transition module (which service 
B0COT13 and B0COT14 respectively), the problem stayed with 
the B0COT14 crate. I have asked Ting Miao to exchange the 
Tracer in this crate with a spare. 
 
<pre>Bad data on event 1590 block 4 word 222 
   expected 492b09e9; saw: 49ff09e9 
Bad data on event 1590 block 4 word 223 
   expected 4ad6c1d3; saw: 4a2bc1d3 
Bad data on event 1590 block 4 word 224 
   expected 4c86d28a; saw: 4cd6d28a 
Bad data on event 1590 block 4 word 225 
   expected 45dddff2; saw: 4586dff2 
 
<p> 
<font color=red><cite>(Entry started on Wed Oct  4 16:27:07 2000)</cite></font>
<!-- Author: W. Stuermer -->