<!-- Title: Owl shift. Sun Oct 15, 2000 -->
<!-- Leader: Rick Tesarek/Phil K -->
<!-- Ace: Peter Wittich -->
<!-- Co1: Jonatan Piedra -->
<!-- Co2: Antoni Munar -->
<!-- Co3: Slawek Tkaczyk (SOS1) -->
<!-- Co4: David Saltzberg (SOS2) -->
<!-- Co5: &nbsp; -->
<!-- Notes: -->
<pre>Shift Goals: 
  o Take cosmic ray/proton beam data. 
  o Look for problems in the DAQ/detector systems. 
  o Scan event displays for "good" collision events. 
  o Write up summary of beam collision runs. 
  o Avoid falling asleep. 
</pre>


<!-- Date: Sun Oct 15 00:58:16 2000 -->
<p>BUSY timeout from usual SVX crate. Green screen error message: 
 
<pre> 
----- 15 Oct 2000 00:50:19 CDT ----- b0eb20.fnal.gov ----- tRec_0 
SCPU-P0-E-BufferOverflow: Data from VRB in slot 12 would not fit in remaining buffer space. 
 Buffer size: 51200. Event size: 29408. 
 
----- 15 Oct 2000 00:50:21 CDT ----- b0eb19.fnal.gov ----- tRec_0 
SCPU-P0-E-VrbReadFailed: Error reading VRB in slot 12 for event 25341. 
The VRB had no event. 
 
----- 15 Oct 2000 00:50:22 CDT ----- b0eb19.fnal.gov ----- tRec_0 
SCPU-P0-E-VrbReadFailed: Error reading VRB in slot 13 for event 25341. 
The VRB had no event. 
</pre> 
HRR - no luck.  End run.	 All this happened at the same time as the muon chamber HV crashed due to beam.
<!-- Author: Peter Wittich :: (run 101467) -->
<!-- Comment: Sun Oct 15 01;02;21 comment by...Peter Wittich -->
<pre>This happened after 25K events.</pre>


<!-- Comment: Sun Oct 15 03;05;33 comment by...Peter Wittich -->
Note that this is a case where the green screen really is pointing at a problem in the SVX FIB/VRB connection, as far as I can tell - I think that's what is in b0eb19, vrb slots 12 and 13.
<!-- Comment: Sun Oct 15 09;10;33 comment by...SCN -->
<pre>This is in fact a problem in both SVX VRB crates simultaneously,
so probably not an individual VRB but something in the SRC 
or clocks.  Will start publishing SRC error conditions soon
which may make this clearer...</pre>
<!-- Date: Sun Oct 15 01:06:34 2000 -->
<br><b>Muon system Trip:</b> 
<br>Muon systems trip (CMP,CMX,BMU).  Slawek resets the HV. 
Notes that bottom south side HV is off(CAEN crate=3, chan=32). 
<p> 
Shift crew notes that it would be nice to have access to the 
cell information from the control room (though not HV control). 
<p> 
Noted earlier that beam was in the Tevatron.  Phoned MCR and learned that the muon chamber trips were likely due to a TeV 
abort.  Tev Ramp and low beta studies are underway.
<!-- Author: R.J. Tesarek, S. Tkaczyk -->


<!-- Date: Sun Oct 15 02:03:14 2000 -->
<p>Done timeout from COT02 after 12K events. HRR works!</p> 
 
<p>Get more errors, including SCPU-E_BadChannelCounts from eb14 (COT VRB crate). Now, we get a SVX timeout after another 1K events. 
 
<p>Tried HRR from pause, which killed the run (have to ABORT it). L3 complains about this transistion.  Oops.  Start a new run. 
 
<p>Next run, 101469 goes on for a while, but getting a lot of Runtime errors from all sorts of crates:  CLC bunch counter mismatches and also wrong event number in L2 message in CCAL crates.  I stop run 101469 due to this.</p> 
 
<p>Clean up EVB and L3 farm and start a new run, 101470. 
 
</p>  
<!-- Author: Peter Wittich :: (run 101468-101470) -->
<!-- Comment: Sun Oct 15 02;04;17 comment by...Peter Wittich -->
<p>Note that at the time of the VRB errors from the COT crate (ad the done timeout), a cratemap of b0cot02 shows all crates still on-line.</p>


<!-- Date: Sun Oct 15 02:23:43 2000 -->
<pre>I found one of two signals coming from the wet engine  
missing on the scope display in the cryo area. Bruce 
should check it on Monday.  </pre>
<!-- Author: Slawek Tkaczyk -->


<!-- Date: Sun Oct 15 02:39:41 2000 -->
<p>Usual SVX VRB error after almost 10K events.  The Green Screen says, 
 
<pre> 
----- 15 Oct 2000 02:29:31 CDT ----- b0eb12.fnal.gov ----- tRec_0 
SCPU-P0-E-BadVrbByteCount: Event 9706 total byte count is lt 32, gt 65528, or not divisible by 8 for VRB in slot 10. 
Count = 590057. 
 
----- 15 Oct 2000 02:29:31 CDT ----- b0eb10.fnal.gov ----- tsmDisp 
SM-P0-I-Suspending: Suspending event loading until a Recover. 
</pre> 
This would appear to be one of the XFT crates or the Muon trigger crate (how can I tell which VRB channel this is?) 
 
Try a HRR.  Get anouther 100 events, this message in the greens creen and another SVX timeout: 
 
<pre> 
----- 15 Oct 2000 02:37:40 CDT ----- b0eb14.fnal.gov ----- tRec_0 
SCPU-P0-I-VrbHeader: Dump of header words for event 9798 from VRB in slot 10: 
0x00100050 
0x01940208 
0x01a401f8 
0x00fc0000 
0x00000214 
0x038400d4 
0x00000065 
0xee06003b 
 
----- 15 Oct 2000 02:37:40 CDT ----- b0eb14.fnal.gov ----- tRec_0 
SCPU-P0-E-BufferOverflow: Data from VRB in slot 10 would not fit in remaining buffer space. 
 Buffer size: 51200. Event size: 24. 
</pre> 
 
Trying another HRR.  No dice, same error, no green screen message.  Run ends with 9828 events. 
 
   
<!-- Author: Peter Wittich :: (run 101470) -->


<!-- Date: Sun Oct 15 02:53:47 2000 -->
<p>New run, same run configuration.  I would remove a crate if  I had a good culprit, but I don't have one, so continue with the same.</p>
<!-- Author: Peter Wittich :: (run 101471) -->
<!-- Comment: Sun Oct 15 02;59;44 comment by...Peter Wittich -->
<p>After 4k events, green screen says:
<pre>
----- 15 Oct 2000 02:55:15 CDT ----- b0eb14.fnal.gov ----- tRec_0
SCPU-P0-E-BadChannelCounts: Event 4000 has invalid VRB channel byte counts, expect reformatter errors.

----- 15 Oct 2000 02:55:15 CDT ----- b0eb10.fnal.gov ----- tsmDisp
SM-P0-I-Suspending: Suspending event loading until a Recover. 
</pre>
<p>and we get the usual SVX error.  b0eb14 deals with the COT East crates.</p>

<p>Much to my surprise, HRR appears to work, at least for the next 600 events.</p>


<!-- Comment: Sun Oct 15 04;02;20 comment by...Peter Wittich -->
<pre>
----- 15 Oct 2000 04:01:16 CDT ----- b0eb14.fnal.gov ----- tRec_0
SCPU-P0-E-BadChannelCounts: Event 27173 has invalid VRB channel byte counts, expect reformatter errors.

----- 15 Oct 2000 04:01:16 CDT ----- b0eb10.fnal.gov ----- tsmDisp
SM-P0-I-Suspending: Suspending event loading until a Recover. 
</pre>
after 27183 events.  HRR. Seems to function adequately.


<!-- Date: Sun Oct 15 04:13:16 2000 -->
<pre> 
----- 15 Oct 2000 04:12:30 CDT ----- b0eb20.fnal.gov ----- tRec_0 
SCPU-P0-E-BufferOverflow: Data from VRB in slot 12 would not fit in remaining buffer space. 
 Buffer size: 51200. Event size: 28280. 
 
----- 15 Oct 2000 04:12:30 CDT ----- b0eb19.fnal.gov ----- tRec_0 
SCPU-P0-I-VrbHeader: Dump of header words for event 31063 from VRB in slot 13: 
0x8c200007 
0x04104100 
0x82080100 
0x00000000 
0x00000000 
0x00001ffc 
0x1ffc1ffc 
0x1ffc0bfe 
 
----- 15 Oct 2000 04:12:30 CDT ----- b0eb19.fnal.gov ----- tRec_0 
SCPU-P0-E-BufferOverflow: Data from VRB in slot 13 would not fit in remaining buffer space. 
 Buffer size: 51200. Event size: 27744. 
</pre> 
after 31073 events. HRR fails.  End run.</p>
<!-- Author: Peter Wittich :: (run 101471) -->
<!-- Comment: Sun Oct 15 09;07;27 comment by...SCN -->
This VRB header indicates that the VRB is hosed.  Looks like
glink synch errors on the bottom 5 channels and 4/5 have
btes counts of 0x1ffc which is 4 bytes less than
the maximum of 0x2000 (8k).  Read All mode for the vrb channel
with the most silicon attached cannot be greater than ~4k.
Best guess is a clock glitch...
<!-- Date: Sun Oct 15 05:15:02 2000 -->
Take this opportunity to do the calibration runs. Running them in partition 1. 
 
<pre> 
Type	Run Number	Comments 
-------------------------------------------------- 
QIE	101473		No CLC (we have beam ). 
			I used the run configuration 
			VAIA_CONFIG_FEW_NEW, as per docs, 
			is this still right? 
QIE	101474		Repeat, as there were problems before 
LED	101475		Not in DB? 
	101476		not in DB.  See consumer error message  
			below. 
Xenon	101477		in DB, though it had the same error message 
			as the LED run. 
COT TDC	101478		OK 
Muon	101479		removed CMX01 as it was not on the white 
			board. 
		 
</pre> 
Run control crashed after 101473 with the following error 
message:  
<pre> 
SIGSEGV 11 (*) segmentation violation 
	stackpointer=0xbe9c1cb0 
</pre> 
<p>and nothing else (no stack backtrace)</p> 
 
<p><b>LED consumer error message</b> was: 
<pre> 
Abnormal termination caused by signal: 15 
 
[22849] ERROR--> hostname:  
         prg name: anonymous 
         function: l3_csl_socket_receive_timedwait_from_any() 
         datetime: Sun Oct 15 04:45:03 2000 
         src file: /cdf/people1/csl/temp/cs-logger/src/library/l3_csl_socket.c 
         src line: 1837 
         src info: select() -> error 
 
[22849] ERROR--> hostname:  
         prg name: anonymous 
         function: l3_csl_socket_receive() 
         datetime: Sun Oct 15 04:45:03 2000 
         src file: /cdf/people1/csl/temp/cs-logger/src/library/l3_csl_socket.c 
         src line: 1026 
         src info: Error receiving message 
APPConsumerInputModule::nextEvent :Received message of length 0 bytes. 
 
[22849] ERROR--> hostname:  
         prg name: anonymous 
         function: APPConsumerInputModule::nextEvent() 
         datetime: Sun Oct 15 04:45:03 2000 
         src file: /home/cdfsoft/dist/packages/ConsumerInterface/V00-00-27/src/APPConsumerInputModule.cc 
         src line: 585 
         src info: l3_csl_socket_receive() -> error 
%ERLOG-w [BAD_RECORD]:  
         /home/cdfsoft/dist/packages/FrameMods/V00-00-57/src/APPCDFInputModule.cc  
        : 372   nextEvent returned an error, error count has reached  1  
          trying again... 15-Oct-2000 04:45:03 run = 101476 event = 0 
</pre> 
I guess this is why it isn't in the DB? 
 
<p>We are not sure how to look at the data from the muon calibration.</p>
<!-- Author: Peter Wittich -->
<!-- Comment: Sun Oct 15 09;21;36 comment by...r. st. denis -->
All of these runs are in the database .. there are problems with using dbana and these should be factorized from the question of whether the calibration is in the database.  When taking calibrations, please go to the ace page and choose calibrations.
The first thing on the page is a place to go to get the list of calibrations on the database -- and this will tell you if it went to the database.  if you then have trouble seeing them on dbana, this is a separate problem and indicates an entirely different path of investigation.
<!-- Date: Sun Oct 15 05:24:27 2000 -->
<pre>Going back to a 2Jet2[1,47] configuration and cosmic ray data taking.</pre>
<!-- Author: Peter Wittich :: (run 101480) -->


<!-- Date: Sun Oct 15 05:24:43 2000 -->
<br><b>Runs Taken During Collisions 10/13-10/14:</b> 
<br>Below is a short summary of the information I was able to  
obtain from the e-logs and run summaries. 
<pre> 
10/13 - Eve Shift 
                                  L1 
                                 Rate  No.             
Run      Trigger Table           (Hz)  Evt COT L3 EB cdfclk    Comment        
------------------------------------------------------------------------------- 
101351  COMMISSIONING_B            ??  33k  -  ?   H 36x36 
101355  COMMISSIONING_B            ??  14k  -  ?   H 36x36 
101358  COMMISSIONING_B            ??   1k  -  ?   H 36x36 
101359  COMMISSIONING_B            ??   2k  -  ?   H 36x36 
101361  COMMISSIONING_B            ??  22k  -  ?   H 36x36 
101362  MINIMUM_BIAS               ??   4k  -  ?   H 36x36 
101363  MINIMUM_BIAS               ??  10k  -  ?   H 36x36 
101364  2_JET_2_TEST               ??  10k  -  ?   H 36x36 
101367  MINIMUM_BIAS               ??  10k  -  ?   H  1x8 
101370  2_JET_2_TEST               ??   3k  -  ?   H  1x8 
101372  2_JET_2_TEST               ??  20k  -  ?   H  1x8 
101381  COMMISSIONING_B            ??  10k  ?  ?   H  1x8 
101385  2_JET_2_TEST              3.0   ??  -  -   H  1x8 
------------------------------------------------------------------------------  
 
10/14 - Owl Shift 
                                  L1 
                                 Rate  No.             
Run      Trigger Table           (Hz)  Evt COT L3 EB cdfclk    Comment          
------------------------------------------------------------------------------  
101386  COMMISSIONING_B          60.0  33k  -  -   H  1x8  Si src delay=0 
101387  COMMISSIONING_B          60.0  21k  -  -   H  1x8  Si src delay=1 
101388  COMMISSIONING_B          60.0  21k  -  -   H  1x8  Si src delay=2 
101389  COMMISSIONING_B          60.0  20k  -  -   H  1x8  no  Si src delay=3 
101391  2_JET_2_TEST              3.2  ??   X  -   H  1x8                 
101393  2_JET_2_TEST              3.2  35k  X  -   H  1x8                 
101394  COMMISSIONING_B          56.0  20k  -  -   H  1x8                 
101398  COMMISSIONING_B          56.0  25k  -  -   H  1x8                 
101399  COMMISSIONING_B           0.1   7k  X  -   H  1x8  CLC trig delay 
101400  2_JET_2_TEST              3.2  33k  X  -   H  1x8                 
101401  CMU_LOW_PT_DPHI_120_TEST  0.5   8k  X  -   H  1x8 
101403  CMU_LOW_PT_DPHI_120_TEST  0.4   7k  X  -   H  1x8 
------------------------------------------------------------------------------  
 
10/14 - Day Shift 
                                  L1 
                                 Rate  No.             
Run      Trigger Table           (Hz)  Evt COT L3 EB cdfclk    Comment 
------------------------------------------------------------------------------- 
101405  COMMISSIONING_B          60.0  10k  -  -   H  1x8  Si studies 
101406  COMMISSIONING_B          60.0   1k  -  -   H  1x8  Si studies 
101408  COMMISSIONING_B          60.0   1k  -  -   H  1x8  Si studies 
101409  COMMISSIONING_B          60.0  32k  -  -   H  1x8  Si studies 
101410  COMMISSIONING_B          60.0  13k  -  -   H  1x8  Si studies 
101411  COMMISSIONING_B          60.0  13k  -  -   H  1x8  Si studies 
101412  COMMISSIONING_B          60.0  14k  -  -   H  1x8  Si studies 
101415  SUMET10                   8.0   3k  -  -   H  1x8 
101421  SUMET10                   8.0  14k  -  -   H  1x8  sumET(10) trig test 
101422  MIN_BIAS_50               2.0  23k  -  -   H  1x8  test minbias prescal 
101426  COMMISSIONING_E          10.0   1k  X  -   H  1x8 
101427  COMMISSIONING_E          10.0   2k  X  -   H  1x8 
101428  COMMISSIONING_E                 2k  -  -   H  1x8  sumET studies 
101429  COMMISSIONING_E                 1k  -  -   H  1x8  sumET studies 
------------------------------------------------------------------------------  
 
Symbol Definitions: 
~~~~~~~~~~~~~~~~~~~~~~~~~ 
 ?   No Information 
 X   Subsystem included 
 -   Subsystem not included 
</pre> 
<p> 
<i><b>Comment:</b>  In compiling the above table, it is clear 
that we need better record keeping (more automatic?).  Some useful information which might be included in the e-logs is: 
<ul> 
 <li>When collisions begin</li> 
 <li>When collisions end</li> 
 <li>Accelerator information (beam current(s), bunch structures,  
     etc.).</li> 
</ul> 
</i> 
<br>
<!-- Author: R.J. Tesarek -->


<!-- Date: Sun Oct 15 05:28:15 2000 -->
<pre><br><b>Master Clock:</b> 
<br>Reset Master clock module since all red lights were on. 
Reset takes effect beginning after run 101480. 
<br></pre>
<!-- Author: R.J. Tesarek -->


<!-- Date: Sun Oct 15 06:36:13 2000 -->
Usual SVX problem, with this error in the green screen, after 26K events. 
 
<pre> 
----- 15 Oct 2000 06:34:38 CDT ----- b0eb12.fnal.gov ----- tRec_0 
SCPU-P0-E-TracerEventId: Event 26318, crate 0, channel 1 has Tracer event ID of 0 instead of 14. 
Tracer word = 0x05000000 (I think). 
Channel data = 0x00020000 0x0000003b 0x00000003 0x00000002 0x00000004 0x0000001f 0x0000003a 0x00000700 ... 
... 0x05000000 0x05000000 0x07000000 0x05000000 0x05000000 0x05000000 0x07000000 0x05000000 
 
----- 15 Oct 2000 06:34:38 CDT ----- b0eb12.fnal.gov ----- tRec_0 
SCPU-P0-E-TracerEventId: Event 26318, crate 7, channel 2 has Tracer event ID of 0 instead of 14. 
Tracer word = 0x80000207 (I think). 
Channel data = 0x05000000 0x05000000 0x07000000 0x05000000 0x05000000 0x05000000 0x07000000 0x05000000 ... 
... 0x00000000 0x0000aaaa 0xaaaa5555 0x55550062 0xee1e0000 0x80000207 0x00000063 0x981e4c44 
 
----- 15 Oct 2000 06:34:38 CDT ----- b0eb12.fnal.gov ----- tRec_0 
SCPU-P0-E-TracerEventId: Event 26318, crate 0, channel 3 has Tracer event ID of 0 instead of 14. 
Tracer word = 0x00000000 (I think). 
Channel data = 0x00030000 0x000001eb 0x00000003 0x00000008 0x0000000a 0x00000046 0x00000082 0x000000be ... 
... 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 
 
----- 15 Oct 2000 06:34:38 CDT ----- b0eb12.fnal.gov ----- tRec_0 
SCPU-P0-E-TracerEventId: Event 26318, crate 7, channel 4 has Tracer event ID of 0 instead of 14. 
Tracer word = 0x80000207 (I think). 
Channel data = 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 0x00000000 ... 
... 0x00000000 0x0000aaaa 0xaaaa5555 0x55550064 0xee1e0000 0x80000207 0x00000065 0xf81e4c44 
 
----- 15 Oct 2000 06:34:38 CDT ----- b0eb12.fnal.gov ----- tRec_0 
SCPU-P0-E-TracerEventId: Event 26318, crate 0, channel 5 has Tracer event ID of 0 instead of 14. 
Tracer word = 0x50005000 (I think). 
Channel data = 0x00030000 0x000001eb 0x00000003 0x00000008 0x0000000a 0x00000046 0x00000082 0x000000be ... 
... 0x50007000 0x50005000 0x50007000 0x50005000 0x50007000 0x50005000 0x50007000 0x50005000 
 
----- 15 Oct 2000 06:34:38 CDT ----- b0eb12.fnal.gov ----- tRec_0 
SCPU-P0-E-TracerEventId: Event 26318, crate 7, channel 6 has Tracer event ID of 0 instead of 14. 
Tracer word = 0x80000207 (I think). 
Channel data = 0x50007000 0x50005000 0x50000000 0x00000000 0x00000000 0x00000000 0x00000000 0x07000000 ... 
... 0x00000000 0x0000aaaa 0xaaaa5555 0x55550066 0x541e0000 0x80000207 0x00000067 0xde1e4c44 
 
----- 15 Oct 2000 06:34:38 CDT ----- b0eb10.fnal.gov ----- tsmDisp 
SM-P0-I-Suspending: Suspending event loading until a Recover.  
 
----- 15 Oct 2000 06:34:38 CDT ----- b0eb12.fnal.gov ----- tRec_0 
SCPU-P0-E-TracerEventId: Event 26318, crate 18, channel 8 has Tracer event ID of 0 instead of 14. 
Tracer word = 0x00000212 (I think). 
Channel data = 0x00030000 0x000001eb 0x00000003 0x00000008 0x0000000a 0x00000046 0x00000082 0x000000be ... 
... 0x0000aaaa 0xaaaa5555 0x55550067 0xde1e0000 0x80000000 0x00000212 0x00000069 0x001e4d44 
</pre> 
Try HRR.  It appears to be successful.
<!-- Author: Peter Wittich :: (run 101480) -->
<!-- Comment: Sun Oct 15 07;10;36 comment by...Peter Wittich -->
<pre>Same error again, HRR.</pre>


<!-- Date: Sun Oct 15 07:58:47 2000 -->
<font color=red>Shift Summary: </font><pre>Owl Shift Summary 
~~~~~~~~~~~~~~~~~ 
Plan: 
  1. Take cosmic ray data 
  2. Calibrations 
  3. Keep from falling asleep 
   
Execution: 
  Items 1,2 accomplished, web cam has nice picture of A.Munar 
sleeping between updates of the event display run from fcdfsgi2. 
Couple of problems during shift: 
  o Signals from one of the dry engines for the He refrigerators 
    doesn't appear. 
  o Muon system HV trip. 
 
Run Summary.  Blank entries are unchanged from previous entries. 
 
Run      Trigger         L1      # 
No                      Rate    Events 
------------------------------------------ 
101468	2Jet2[1,47]	1.5Hz	13K 
101469			1.6Hz	600 
101470                  1.6Hz   10K 
101471			1.6Hz	31K 
 
(Calibration Runs, see entry at 5.15AM) 
 
101480   2Jet2[1,47]	1.5Hz	54K at end of shift, still going</pre> 
<!-- Author: Rick Tesarek -->





<!-- Date: Mon Oct 16 00:52:35 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-374&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-374  width='250' align='top'></td><td>Trigger Bits for run 101389 decoded from Trigger Bank TSID for Myron Bucket 1. For Myron Bucket 0,2,3 are 0.</a></td></tr></table><font color=red><cite>(Entry started on Mon Oct 16 00:52:27 2000)</cite></font>
<!-- Author: Toni Munar -->


<!-- Date: Mon Oct 16 00:54:01 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-375&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-375  width='250' align='top'></td><td>RUN 101398 (Commisioning B). Plot Trigger Towers Energy vs Myron Bucket Number. Also Total energy in CLC vs Myron Bucket Number.</a></td></tr></table><font color=red><cite>(Entry started on Mon Oct 16 00:53:59 2000)</cite></font>
<!-- Author: Toni Munar -->


<!-- Date: Mon Oct 16 00:54:56 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-376&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-376  width='250' align='top'></td><td>Id. as previous but for run 101399 where CLC clock is shifted by one.</a></td></tr></table><font color=red><cite>(Entry started on Mon Oct 16 00:54:54 2000)</cite></font>
<!-- Author: Toni Munar -->


<!-- Date: Mon Oct 16 00:56:33 2000 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2000&action=view&page=-377&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2000&action=view&page=-377  width='250' align='top'></td><td>Et leading Trigger Tower for Bucket 1 Myron Mode. Run 101389 for trigger 2_JET_2_Test. The minimum energy correspondons to 2 GeV in ADC counts.</a></td></tr></table><font color=red><cite>(Entry started on Mon Oct 16 00:56:32 2000)</cite></font>
<!-- Author: Toni Munar -->