<!-- Title: 11:57:35  Mon Oct  9 2000 -->
<!-- Crewchief: Evelyn Thomson -->
<!-- Op1: Jay Dittmann -->
<!-- Op2: Chris Neu -->
<!-- Op3: Jong-Young Chung -->
<!-- Op4: et al. -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Logbook for week beginning Monday October 9th</pre>


<!-- Date: Mon Oct 9 11:59:25 2000 -->
<pre>XFT Daily Notes and Activities:  
 
  Report from the 8:00 AM Operations Meeting:  
 
  * Collisions!  Colliding beam since Sunday's Evening shift. 
  * The solenoid is cold.  Electrical work today.  Possible Field ON 
    later today.  Bob Wagner says COT HV will be ready. 
 
  Recent Activities:  
 
  * On Friday, continued success with Linker->XTRP (see e-log)  
 
  * Over the weekend, the XFT crates were not included in the DAQ 
    readout most of the time (because of other priorities, not 
    because of any problems).  There are two short runs 
    (100703,100704) that do include the XFT crates. 
     
  * This morning, Evelyn and I performed an XTC->Linker test 
    which included 4 COT crates and simulated track data. 
     
    ===> We successfully found our first track in the linker!! <=== 
     
    (Sending data up from the XTCs, that is.) 
     
    Simulated data, but still cool. 
    More details will appear in the logbook shortly. 
 
  XFT Activities today:  
 
  * Evelyn and Jay used 4 COT crates (b0cot02,03,12,13) until 
    11am for XTC->Linker tests, then relinquished them. 
     
  * Evelyn and Jong-Young will use b0xft00-03 and b0xft05 until 
    4pm for Finder->Linker->XTRP? tests and code development. 
     
  * Jay will use b0xft04 for code development (flashram programming) 
   
  * If there are collisions and the COT HV is turned on later 
    today, WE SHOULD BE READY TO GO.   
</pre>
<!-- Author: Jay D -->


<!-- Date: Mon Oct 9 12:29:05 2000 -->
<pre>Tracks sent from XTC to Linker.  Used linker in slot 8 
of b0xft03, finders in slots 6,7,15,16 and cot TDCs in 
crate b0cot02 and b0cot12.  We had to reprogram the TDCs 
in b0cot12 with the latest version of the DSP code (30). 
 
 CLKDEL register value =	2e 
 BCDEL register value  =	1e 
 SYNDEL register value =	c8 
 TTDEL register value  =	34 
 B0DEL register value  =	be 
 NSDEL register value  =	35 
 LATDEL register value =	20 
 PRSC register value   =	d0 
 DLSC register value   =	ff 
 TDC control register  =	400ffff 
 
COT wire hits 
============= 
 
Event 0 Finder hits 3d  	 0	 	   0	 	 0	 0        FTLsys=0 
Event 0 Expect hits 3d  	 0	 	   0	 	 0	 b00400	 CONWT-1 b0cot02 10 1 
(TDC in b0cot02 slot 10, upper half doesn't seem to work.) 
Event 0 Finder hits 1b      0	 	   0	 	 0	 b00400   FTLsys=0 
Event 0 Expect hits 1b      0	 	   0	 	 0	 b00400	 CONWT-1 b0cot02 16 1 
Event 0 Finder hits 4d      0	 b00400  d0020	   9006 	 FTLsys=0 
Event 0 Expect hits 4d      0	 b00400  d0020	   9006	 CONET-1 b0cot12 7 1 
Event 0 Finder hits 2c      0	 b00400  d0020	   d002   FTLsys=0 
Event 0 Expect hits 2c      0	 b00400  d0020	   d002	 CONET-1 b0cot12 15 0 
Event 0 Finder hits 3a' 90060    d002	    0       0   FTLsys=0 
Event 0 Expect hits 3a' 90060    d002	    0	      0	 CONWT-1 b0cot02 9 0 
Event 0 Finder hits 1a' d0020    d002	    0	      0   FTLsys=0 
Event 0 Expect hits 1a' d0020    d002	    0	      0	 CONWT-1 b0cot02 15 0 
 
Pixels 
====== 
Event 0	 chip4d  	 Finder pixels=	0	 0	 f0 0 FTLsys=0 
Event 0	 chip4d  	 Linker pixels=	0	 0	 f0 0 
Event 0	 chip4d  	 Expect pixels=	0	 0	 f0 0 
Event 0	 chip2c  	 Finder pixels=	0	 0	 20 0 FTLsys=0 
Event 0	 chip2c  	 Linker pixels=	0	 0	 20 0 
Event 0	 chip2c  	 Expect pixels=	0	 0	 20 0 
Event 0	 chip3a' 	 Finder pixels=	f0	 0	 0	 0 FTLsys=0 
Event 0	 chip3a' 	 Linker pixels=	f0	 0	 0	 0 
Event 0	 chip3a' 	 Expect pixels=	f0	 0	 0	 0 
Event 0	 chip1a' 	 Finder pixels=	20	 0	 0	 0 FTLsys=0 
Event 0	 chip1a' 	 Linker pixels=	20	 0	 0	 0 
Event 0	 chip1a' 	 Expect pixels=	20	 0	 0	 0 
 
Tracks! 
======= 
Event 0 chip 5	 Linker track 	 wrd:  1	 tfnd:1	 phi:7	 pt: 30	 sht:0 
Event 0 chip 5	 Expect track	 wrd:  1	 tfnd:1	 phi:7	 pt: 30	 sht:1 
Event 0 chip 6	 Linker track 	 wrd:  0	 tfnd:1	 phi:0	 pt: 31	 sht:0 
Event 0 chip 6	 Expect track	 wrd:  0	 tfnd:1	 phi:0	 pt: 31	 sht:1 
 
Bunch Counters 
=============== 
Finder Bunch IDs 		  buff0  158	  buff1  0	 buff2  1	 buff3  2 
Finder Bunch IDs 	 	  buff0  158	  buff1  0	 buff2  1	 buff3  2 
Finder Bunch IDs 	 	  buff0  158	  buff1  0	 buff2  1	 buff3  2 
Finder Bunch IDs 	 	  buff0  158	  buff1  0	 buff2  1	 buff3  2 
Linker Output Bunch ID buff0  158 158 buff1  0 0 buff2  1 1	 buff3  2 2 
Linker VME Bunch ID    buff0  158	  buff1  0	 buff2  1	 buff3  2 
</pre>
<!-- Author: Evelyn Thomson -->
<!-- Comment: Mon Oct  9 12;38;58 comment by...Jay D -->
We also tried the latest set of XTC/TRACER constants
(NSDEL=0x31,LATDEL=0x38) with the same successful results.


<!-- Date: Mon Oct 9 15:08:40 2000 -->
<pre>Finer to Linker Test. 
With new vector file(xx_sgl), I did FTL test on all crates. 
Until about 100 loops( total 2500 loops) tests were successful, 
even though I couldn't finish all loops in vector file  
due to other requests for using XFT crate.</pre>
<!-- Author: Jong-young Chung -->


<!-- Date: Mon Oct 9 16:20:28 2000 -->
<pre>New duplicate track algorithm for XTRP - before pt was set to 0, 
now pt is set to 7c when there is a duplicate track.   
Checked that this works on 1 event for chip 5.  Will check 
chip 11 tomorrow. 
 
Duplicate track removed by Xtrp in chip 5.  
 
Event 0 chip 5	 Linker track 	 wrd:  1	 tfnd:1	 phi:7	 pt: 30	 sht:0	 FTLsys=0 
Event 0 chip 5	 Expect track	 wrd:  1	 tfnd:1	 phi:7	 pt: 30	 sht:1 
Event 0 chip 5	 Xtrp track 	 wrd:  	 	 tfnd:1	 phi:7	 pt: 7c	 sht:0 
Event 0 chip 6	 Linker track 	 wrd:  0	 tfnd:1	 phi:0	 pt: 31	 sht:0	 FTLsys=0 
Event 0 chip 6	 Expect track	 wrd:  0	 tfnd:1	 phi:0	 pt: 31	 sht:1 
Event 0 chip 6	 Xtrp track 	 wrd:  	 	 tfnd:1	 phi:0	 pt: 31	 sht:0 
</pre>
<!-- Author: Evelyn Thomson, Nathan Eddy -->


<!-- Date: Mon Oct 9 17:35:59 2000 -->
<pre>I did finder to linker tests on b0xft04 and b0xft05 with  
new vector file which Brian made. 
with XX_sgl files, I checked all event (2500 loops) 
Because I had only one set of crates I used 7 linkers 04 to 16  
except 18. 
There are no error at all. 
 
About Crate b0xft00 and b0xft01, Jay was testing with his new 
finder design and XX_sgl vector file sets. 
I couldn't check all 2500 loops, But until 700 loops there are  
no error except finder hit L2 buffer errors. 
But this is expected, it comes from split wires in superlayer 1. 
and his new design doesn't deal it correctly.</pre>
<!-- Author: Jong-young Chung -->
<!-- Comment: Mon Oct  9 18;26;13 comment by...jych-young Chung -->
According to Jay's forwarding mail, the SL1 split finders should
have 0 in all level 2 buffers and at the pixel output., It seems intened operation.


<!-- Comment: Thu Oct 12 14;35;34 comment by...Jongyoung Chung -->
Only 00_sgl is used
<!-- Date: Tue Oct 10 06:20:14 2000 -->
<pre>Scott prepared some new Finder and Pixel Altera designs for us: 
 
Jay - I've made new .hex files for all finder and pixel chip normal designs. 
On power up they should load 93h into the pipelines. On reset the Pipeline 
registers are reset to 93h and all level 2 buffers are set to zero. The Dead 
wire registers do not get reset. 
The SL1 split finders should have 0 in all level 2 buffers and at the pixel 
output. The SL1 split pixel chips should have 0 in all level 2 buffers, the 
pixel output to the channel link should be the pixel info from the non-split 
finders(OR'ing was removed). 
 
Yesterday afternoon, I reprogrammed the Finder flashrams in 
b0xft00 with the new designs.  The Finder to Linker test 
performed as expected (see Jong-Young's entry).  After loading  
patterns into the input 
section, we observed all of the correct hits and pixels in 
the finder and pixel chips except for the split wire chips 
where we observed zeroes.  Evelyn plans to change the checking 
code so that the actual hits for the split wire chips will 
always be compared to zeroes, regardless of the patterns 
loaded into the input section. 
 
=== Now, all of the Finder boards that are currently installed 
in all three crates have the newest designs. ===</pre>
<!-- Author: Jay D -->


<!-- Date: Tue Oct 10 13:35:43 2000 -->
 
There was a supervised access this morning from 7:40am to 11:45am. 
<br>The following was our tasklist and <b><font color="#3366FF">outcome</font><font color="#000000">.</font></b><b><font color="#3366FF"></font></b> 
<p>Tomorrow morning I&nbsp;will try a comprehensive set of XTC->Finder 
tests 
<br>to see where we stand. 
<p><b>XFT Tasklist&nbsp; Supervised Access&nbsp; 10-OCT-00</b> 
<br>------------------------------------ 
<br>Jay Dittmann (12348), Chris Neu (8287V) 
<p>1) <b>CONWB-1</b>&nbsp; b0cot09 (JD) 
<br>&nbsp;&nbsp;&nbsp;&nbsp; a) Check clock, B0, and BC at TRACER front 
panel&nbsp;&nbsp; <b><font color="#3366FF">All signals check out OK</font></b> 
<br>&nbsp;&nbsp;&nbsp;&nbsp; b) Insert TDC in slot 7&nbsp; <b><font color="#3366FF">Done</font></b> 
<br>&nbsp;&nbsp;&nbsp;&nbsp; c) Perform crate map: boards should be present 
in 7-11, 15-17&nbsp; <b><font color="#3366FF">OK</font></b> 
<br>&nbsp;&nbsp;&nbsp;&nbsp; d) Run XTC->Finder test&nbsp;<b> <font color="#3366FF">not 
done yet</font></b> 
<p><b><font color="#FF0000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font><font color="#3366FF">Near 
the end of the access I found that <i>none</i> of the COT transition boards 
were</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fully inserted!&nbsp; 
I inserted them, but have not yet tried to run the XTC->Finder</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; test.&nbsp; 
I don't know why they were pulled out.</font></b> 
<p><font color="#000000">2) <b>COSWB-1</b>&nbsp; b0cot06 (CN)</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; a) Slot 7 => Replace 
XTC&nbsp;&nbsp; </font><b><font color="#3366FF">Done:&nbsp; remove 199, 
insert 161</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; b) Perform crate map: 
boards should be present in 6-8, 12-16&nbsp; </font><b><font color="#3366FF">OK</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; c) Run XTC->Finder test&nbsp; 
</font><font color="#3366FF"> 
<b>not done yet</b></font> 
<p><b><font color="#FF0000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </font><font color="#3366FF">Since 
last Friday, there were problems reading out this crate.&nbsp; Chris replaced 
the</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TRACER and 
that seemed to fix things.&nbsp; He removed #42 (562641) and inserted</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; #91 (562265).&nbsp; 
I have not yet tried to run the XTC -> Finder test.</font></b> 
<p><font color="#000000">3) <b>CONET-3&nbsp;</b> b0cot10 (CN)</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; a) Slots 7,8,9,10,11 
=> Replace XTCs&nbsp;&nbsp; </font><b><font color="#3366FF">Done</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Slot 7:&nbsp; remove 51, insert 163</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Slot 8:&nbsp; remove 41, insert 164</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Slot 9:&nbsp; remove 54, insert 165</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Slot 10:&nbsp; remove 194, insert 160</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Slot 11:&nbsp; remove 186, insert 159</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; b) Perform crate map: 
boards should be present in 5-11, 15-18</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</font><b><font color="#3366FF">At first, slot 11 didn't map.&nbsp; Kirby 
then swapped this TDC/XTC.&nbsp; The old</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
TDC was #697 (now with XTC 159) , the new TDC is #172 (now with XTC ???).</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; c) Run XTC->Finder test</font> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Slot 7:&nbsp; OK</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Slot 8:&nbsp; OK</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Slot 9:&nbsp; OK</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Slot 10:&nbsp; </font><font color="#FF0000">Problem remains -- no control 
bits on cable 10A</font></b> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Slot 11:&nbsp; not done yet</font></b> 
<p><font color="#000000">4) <b>COSEB-1</b>&nbsp; b0cot16 (JD)</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; a) Slot 5 => Diagnose 
dropped data bit 8 on cable B</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - 
Swap COT transition board/inspect backplane</font> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
 
</font><font color="#FF0000">Due to the SE CMX position, the rear of the 
crate is completely inaccessible</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - 
Swap TDC/XTC if necessary</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; b) Perform crate map: 
boards should be present in 5-8, 12-18&nbsp; </font><b><font color="#3366FF">OK</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; c) Run XTC->Finder test</font><b><font color="#3366FF">&nbsp; 
 
not done yet</font></b> 
<p><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In slot 8:&nbsp; 
TDC #341/XTC 50 (blown buffer chips) replaced with TDC #671/XTC 212</font></b> 
<p><font color="#000000">5) CONEB-1&nbsp; b0cot19 (JD)</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; a) Slot 17 => Diagnose 
dropped data bit 11 on cable B</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - 
Swap COT transition board/inspect backplane</font> 
<br><font color="#FF0000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
<b>Try a spare COT transition board.&nbsp; Problem remains.&nbsp; Replace 
original.</b></font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - 
Swap TDC/XTC if necessary</font> 
<br><b><font color="#3366FF">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
The XTC was swapped last time; it did not help.</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; b) Slot 16 => Replace 
XTC&nbsp; r</font><b><font color="#3366FF">emove 205, insert 157</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; c) Try to recover TDCs 
in slots 7,8</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; d) Slot 8 => Diagnose 
stuck data bit 5 on cable A</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - 
Swap COT transition board/inspect backplane</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
</font><b><font color="#3366FF">Replace COT transition board 013, insert 
185.&nbsp; Problem fixed.</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Swap TDC/XTC 
if necessary</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; e) Perform crate map: 
boards should be present in 5-11, 15-18&nbsp; </font><b><font color="#3366FF">OK</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; f) Run XTC->Finder test&nbsp; 
</font><b><font color="#3366FF">Full Test 10/10 passes except for 17B</font></b><b></b> 
<p><font color="#000000">6) CONET-1&nbsp; b0cot12 (CN)</font> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; a) Try to recover TDC 
in slot 16&nbsp; </font><b><font color="#3366FF">Done (Kirby)</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; b) Perform crate map: 
boards should be present in 4-19&nbsp; </font><b><font color="#3366FF">OK</font></b> 
<br><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; c) Run XTC->Finder test</font><b><font color="#3366FF">&nbsp; 
 
not done yet</font></b> 
<br>&nbsp; 
<br>&nbsp;
<!-- Author: Jay D -->


<!-- Date: Tue Oct 10 18:29:15 2000 -->
<pre>FTL Test 
Tested on B0xft00 and 01. 
Until loop# 1226 (total 2500) , No errors. 
 
At loop 1227, I got a TS problem, so I had to stop there. 
 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 
Errors above found on loop 1227 Linker is in crate 3 and slot 6 Finders are in slots 5, 6, 14, 15 XTRP is in slot 0 Wedge 0 
L1Accepts issued at 55, 56, 57, 58 First event should be captured with 55 
Finder Bunch IDs 	 buff0  9	 buff1  84	 buff2  11	 buff3  40 
Finder Bunch IDs 	 buff0  9	 buff1  83	 buff2  11	 buff3  40 
Finder Bunch IDs 	 buff0  9	 buff1  85	 buff2  11	 buff3  8 
Finder Bunch IDs 	 buff0  9	 buff1  83	 buff2  11	 buff3  40 
Linker Output Bunch ID 	 buff0  0 0	 buff1  0 0	 buff2  0 0	 buff3  0 0 
Linker VME Bunch ID    	 buff0  0	 buff1  0	 buff2  0	 buff3  0 
XTRP Bunch ID          	 buff0  0	 buff1  0	 buff2  0	 buff3  0 
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++</pre>
<!-- Author: Jong-young Chung -->
<!-- Comment: Thu Oct 12 14;34;42 comment by...Jong-young Chung -->
File used is 00_sgl
<!-- Date: Wed Oct 11 11:54:02 2000 -->
<pre>  [Sorry about the lack of a report yesterday...I'm sure some of you 
   have grown to depend on it like your morning coffee!  I was in 
   the collision hall during the 8am meeting.  Those pesky accesses...] 
 
XFT Daily Notes and Activities:  
 
  Report from the 8:00 AM Operations Meeting:  
 
  * The next shot setup is expected Thursday morning. 
  * The solenoid is cold.  Rob Roser says they will try to 
    energize it this afternoon if he can get all the signatures. 
    Bob Wagner says the COT HV will be ready. 
 
  Recent Activities:  
 
  * During the supervised access yesterday, Chris and I were able 
    to fix a few TDC/XTC problems (see the e-log for details). 
    Some of the remaining problems may be difficult or impossible 
    to fix with the detector in the collision hall due to the 
    inaccessibility of crates.  I performed a set of capture 
    tests this morning.  The results will be in the e-log shortly. 
 
  * Continued Run Control software error reporting enhancements 
    and testing (Chris) 
     
  * Finder->Linker testing (Jong-Young) 
     
 
  XFT Activities today:  
 
  ===>  We need to be ready for collisions tomorrow! 
   
  Plan: 
   
  * From now until 1pm: 
     - Chris will test run control software 
     - Evelyn will test linker designs for duplicate track removal 
     - Jong-Young will run Finder->Linker tests on b0xft02/03. 
 
  * At 1pm we will attempt to take a run where we load up the Finder input 
    section with simulated data and read out the crates using the software 
    event builder. 
     
  * After this test, we should have the shift crew include our crates 
    in a run (using force if necessary) with the hardware event builder. 
</pre>
<!-- Author: Jay D -->


<!-- Date: Wed Oct 11 12:04:36 2000 -->
<pre>XTC->Finder Capture Test  11-OCT-00  
===================================  
 
All of the installed TDCs in the following 16 crates mapped successfully! 
There are now -6- identified problems for 16 crates. 
 
Summary: 
 
CONWT-2 b0cot01 Slots: 9,10,11,12,16,17                FT 10/10:  Pass 
CONWT-1 b0cot02 Slots: 8,9,10,11,15,16                 FT 10/10:  Pass 
COSWT-1 b0cot03 Slots: 7,8,12,13,14,15                 FT 10/10:  Pass 
COSWB-1 b0cot06 Slots: 6,7,8,12,13,14,15,16            FT 100/10: Pass 
COSWB-2 b0cot07 Slots: 6,7,11,12,13,14,15              FT 10/10:  Pass 
CONWB-2 b0cot08 Slots: 8,9,10,11,12,16,17              FT 10/10:  Pass 
CONWB-1 b0cot09 Slots: 7,8,9,10,11,#15#,16,17          FT 100/10: Fail 15AB 
CONET-3 b0cot10 Slots: #5#,6,7,8,9,#10#,11,15,16,17,18 FT 100/10: Fail 5A,10A 
CONET-2 b0cot11 Slots: 4,5,6,7,8,14,15,16              FT 10/10:  Pass 
CONET-1 b0cot12 Slots: 4,5,6,7,8,14,15,16              FT 100/10: Pass 
COSET-1 b0cot13 Slots: 7,8,9,15,16,17,18,19            FT 100/10: Pass 
COSET-2 b0cot14 Slots: 7,8,9,15,16,17,18,19            FT 100/10: Pass 
COSEB-1 b0cot16 Slots: #5#,6,7,8,12,13,14,15,16,17,18  FT 100/10: Fail 5B 
COSEB-2 b0cot17 Slots: 5,6,7,(8),14,15,16,17,18,19     FT 100/10: Pass 
CONEB-2 b0cot18 Slots: 4,5,6,7,8,9,15,16,17,18         FT 100/10: Pass 
CONEB-1 b0cot19 Slots: 5,6,7,#8#,9,10,11,15,16,#17#,18 FT 100/10: Fail 8A,17B 
 
Key:  ## capture errors   
      () missing TDC, slot untested   
      [] TDC doesn't appear in crate map, slot untested   
 
Detailed notes:  
 
1. Crates b0cot00 and b0cot15 are currently powered off  
     (they don't contain TDCs anyway)  
 
2. Crates b0cot04 and b0cot05 don't contain any TDCs in axial slots at this time 
 
3. There is no TDC board in b0cot17, slot 8.  This is the slot where the J1 
     backplane pin must be replaced. 
 
3. b0cot09:  All slots pass FT 100/10 except 15AB which is sending up junk. 
 
Found TDC in CONWB-1 slot 15 
Begin test... 
Random Seed = 5707085352111740285 
Loading TDC with event (0) 
Event=0/0 c=9/15/0/0/7/6 word=0:2 w=20057 r=00031311 x=00011346 1 
Event=0/0 c=9/15/0/0/7/6 word=1:3 w=21054 r=00031355 x=00010301 2 
Event=0/0 c=9/15/0/0/7/6 word=2:4 w=20147 r=00031311 x=00011256 3 
Event=0/0 c=9/15/0/0/7/6 word=3:5 w=20331 r=00031355 x=00011064 4 
Event=0/0 c=9/15/0/0/7/6 word=4:6 w=20200 r=00031355 x=00011155 5 
Event=0/0 c=9/15/0/0/7/6 word=5:1 w=11347 r=00031355 x=00020012 6 
 
4. b0cot10:  No control bits from slot 10A (a known problem) 
             Intermittent extra bits from 5A (this is new, caught with a longer test): 
 
Found TDC in CONET-3 slot 15 
Begin test... 
Random Seed = 8704820399803132467 
Loading TDC with event (0) 
Event=15/8 c=10/5/0/0/20/9 word=40:6 w=0a46a r=0000e46a x=00004000 1 
Event=15/8 c=10/5/0/0/20/9 word=52:6 w=0a46a r=0000e46a x=00004000 2 
Event=45/0 c=10/5/0/0/20/9 word=26:4 w=03152 r=00003172 x=00000020 3 
Event=45/0 c=10/5/0/0/20/9 word=32:4 w=03152 r=00003172 x=00000020 4 
Event=45/0 c=10/5/0/0/20/9 word=38:4 w=03152 r=00003172 x=00000020 5 
Event=45/0 c=10/5/0/0/20/9 word=44:4 w=03152 r=00003172 x=00000020 6 
Event=45/0 c=10/5/0/0/20/9 word=50:4 w=03152 r=00003172 x=00000020 7 
Event=45/0 c=10/5/0/0/20/9 word=56:4 w=03152 r=00003172 x=00000020 8 
Event=45/0 c=10/5/0/0/20/9 word=62:4 w=03152 r=00003172 x=00000020 9 
Event=45/1 c=10/5/0/0/20/9 word=26:4 w=03152 r=00003172 x=00000020 10 
Event=45/1 c=10/5/0/0/20/9 word=32:4 w=03152 r=00003172 x=00000020 11 
Event=45/1 c=10/5/0/0/20/9 word=38:4 w=03152 r=00003172 x=00000020 12 
Event=45/1 c=10/5/0/0/20/9 word=44:4 w=03152 r=00003172 x=00000020 13 
Event=45/1 c=10/5/0/0/20/9 word=50:4 w=03152 r=00003172 x=00000020 14 
Event=45/1 c=10/5/0/0/20/9 word=56:4 w=03152 r=00003172 x=00000020 15 
Event=45/1 c=10/5/0/0/20/9 word=62:4 w=03152 r=00003172 x=00000020 16 
Event=45/2 c=10/5/0/0/20/9 word=26:4 w=03152 r=00003172 x=00000020 17 
Event=45/2 c=10/5/0/0/20/9 word=32:4 w=03152 r=00003172 x=00000020 18 
Event=45/2 c=10/5/0/0/20/9 word=38:4 w=03152 r=00003172 x=00000020 19 
Event=45/2 c=10/5/0/0/20/9 word=44:4 w=03152 r=00003172 x=00000020 20 
Event=45/2 c=10/5/0/0/20/9 word=50:4 w=03152 r=00003172 x=00000020 21 
Event=45/2 c=10/5/0/0/20/9 word=56:4 w=03152 r=00003172 x=00000020 22 
Event=45/2 c=10/5/0/0/20/9 word=62:4 w=03152 r=00003172 x=00000020 23 
   . 
   . 
   . 
 
5. b0cot16:  Known dropped data bit 8 on slot 5B 
 
Found TDC in COSEB-1 slot 5 
Begin test... 
Random Seed = 5707085352111740285 
Loading TDC with event (0) 
Event=0/0 c=16/5/1/2/17/4 word=2:4 w=20147 r=00020047 x=00000100 1 
Event=0/0 c=16/5/1/2/17/4 word=3:5 w=20331 r=00020231 x=00000100 2 
Event=0/0 c=16/5/1/2/17/4 word=5:1 w=11347 r=00011247 x=00000100 3 
Event=0/0 c=16/5/1/2/17/4 word=8:4 w=00147 r=00000047 x=00000100 4 
Event=0/0 c=16/5/1/2/17/4 word=9:5 w=00331 r=00000231 x=00000100 5 
   . 
   . 
   . 
 
6. b0cot19:  Slot 17 -- Known dropped data bit 11 
             Slot 8  -- Stuck data bit 1 !!!  This was the original problem, 
                        but it seemed as though swapping in a spare transition 
                        board yesterday fixed it.  Apparently not. 
 
Found TDC in CONEB-1 slot 17 
Begin test... 
Random Seed = 5707085352111740285 
Loading TDC with event (0) 
Event=0/0 c=19/17/1/0/16/3 word=0:2 w=2cc57 r=0002c457 x=00000800 1 
Event=0/0 c=19/17/1/0/16/3 word=1:3 w=258dc r=000250dc x=00000800 2 
Event=0/0 c=19/17/1/0/16/3 word=4:6 w=26e08 r=00026608 x=00000800 3 
Event=0/0 c=19/17/1/0/16/3 word=5:1 w=13fcf r=000137cf x=00000800 4 
Event=0/0 c=19/17/1/0/16/3 word=6:2 w=0cc57 r=0000c457 x=00000800 5 
Event=0/0 c=19/17/1/0/16/3 word=7:3 w=058dc r=000050dc x=00000800 6 
Event=0/0 c=19/17/1/0/16/3 word=10:6 w=06e08 r=00006608 x=00000800 7 
Event=0/0 c=19/17/1/0/16/3 word=11:1 w=13fcf r=000137cf x=00000800 8 
Event=0/0 c=19/17/1/0/16/3 word=12:2 w=0cc57 r=0000c457 x=00000800 9 
Event=0/0 c=19/17/1/0/16/3 word=13:3 w=058dc r=000050dc x=00000800 10 
Event=0/0 c=19/17/1/0/16/3 word=16:6 w=06e08 r=00006608 x=00000800 11 
  . 
  . 
  . 
 
Found TDC in CONEB-1 slot 8 
Begin test... 
Random Seed = 5707085352111740285 
Loading TDC with event (0) 
Event=0/0 c=19/8/0/0/16/9 word=1:3 w=258dc r=000258de x=00000002 1 
Event=0/0 c=19/8/0/0/16/9 word=3:5 w=24331 r=00024333 x=00000002 2 
Event=0/0 c=19/8/0/0/16/9 word=7:3 w=058dc r=000058de x=00000002 3 
Event=0/0 c=19/8/0/0/16/9 word=9:5 w=04331 r=00004333 x=00000002 4 
Event=0/0 c=19/8/0/0/16/9 word=13:3 w=058dc r=000058de x=00000002 5 
Event=0/0 c=19/8/0/0/16/9 word=15:5 w=04331 r=00004333 x=00000002 6 
Event=0/0 c=19/8/0/0/16/9 word=19:3 w=058dc r=000058de x=00000002 7 
Event=0/0 c=19/8/0/0/16/9 word=21:5 w=04331 r=00004333 x=00000002 8 
Event=0/0 c=19/8/0/0/16/9 word=25:3 w=058dc r=000058de x=00000002 9 
Event=0/0 c=19/8/0/0/16/9 word=27:5 w=04331 r=00004333 x=00000002 10 
Event=0/0 c=19/8/0/0/16/9 word=31:3 w=058dc r=000058de x=00000002 11 
Event=0/0 c=19/8/0/0/16/9 word=33:5 w=04331 r=00004333 x=00000002 12 
Event=0/0 c=19/8/0/0/16/9 word=37:3 w=058dc r=000058de x=00000002 13 
Event=0/0 c=19/8/0/0/16/9 word=39:5 w=04331 r=00004333 x=00000002 14 
Event=0/0 c=19/8/0/0/16/9 word=43:3 w=058dc r=000058de x=00000002 15 
Event=0/0 c=19/8/0/0/16/9 word=49:3 w=058dc r=000058de x=00000002 16 
Total Vectors = 64   Total Errors = 16 
Test FAILED. 
CABLE FAIL 
 
</pre>
<!-- Author: Jay D -->


<!-- Date: Wed Oct 11 17:27:37 2000 -->
<pre>Runs with all finder and linker crates, but not the COT!  
 
/cdf/data08/_APHYSR.0000/ar018ab9.0001phys (valid after event 3000) 
/cdf/data08/_APHYSR.0000/ar018ac2.0001phys (valid after event 800) 
 
(Valid means after a HRR that started up the finder chips in diagnostic 
mode).  The files were the *_sgl_* set, which have a single high momentum 
track (anywhere in the 360 degrees) per event.  The runs were taken with 
the software event builder. 
 
ar018ac2 also had the XTRP in the run. 
 
</pre>
<!-- Author: Evelyn Thomson -->


<!-- Date: Wed Oct 11 17:28:18 2000 -->
<pre>       This morning, Nathan and I successfully checked the duplicate 
track removal works between linker chips 5 and 6 and also between 
neigbouring chips 11 and 0 on the same xtrp board. 
 
However, Nathan thinks there may be errors from the duplicate track 
removal for linker chips between XTRP boards. If the neighbouring XTRP 
board isn't present, then the pt for chip 11 from the second linker may 
get deleted.  I didn't know that XTRP did this - should check this 
tomorrow with a duplicate track in chip 11.  The xtrp board's vme 
interface problem is being cured right now with the addition of a 
capacitor. 
 
 
Duplicate between linker chip 5 and 6 in slot 4 
================================================= 
Event 0 chip 5   Linker wrd:  1 tfnd:1   phi:7   pt: 30  sht:0  Slot 4 
Event 0 chip 5   Expect wrd:  1 tfnd:1   phi:7   pt: 30  sht:0 
Event 0 chip 5   Xtrp   wrd:    tfnd:1   phi:7   pt: 7c  sht:0 
Event 0 chip 6   Linker wrd:  0 tfnd:1   phi:0   pt: 31  sht:0  Slot 4 
Event 0 chip 6   Expect wrd:  0 tfnd:1   phi:0   pt: 31  sht:0 
Event 0 chip 6   Xtrp   wrd:    tfnd:1   phi:0   pt: 31  sht:0 
 
=> xtrp sets pt to 7c for track in chip 5 (lower phi), keeps information 
for track in chip 6.  (Xtrp doesn't put word information in L2 buffer) 
 
Duplicate between linker chip 11 in slot 4 and linker chip 0 in slot 6 
============================================================================= 
Event 1 chip 11  Linker wrd:  1 tfnd:1   phi:7   pt: 31 sht:0 Slot 4 
Event 1 chip 11  Expect wrd:  1 tfnd:1   phi:7   pt: 31 sht:0 
Event 1 chip 11  Xtrp   wrd:    tfnd:1   phi:7   pt: 7c sht:0 
Event 1 chip 0   Linker wrd:  0 tfnd:1   phi:0   pt: 30 sht:0 Slot 6 
Event 1 chip 0   Expect wrd:  0 tfnd:1   phi:0   pt: 30 sht:0 
Event 1 chip 0   Xtrp   wrd:    tfnd:1   phi:0   pt: 30 sht:0 
 
=> xtrp sets pt to 7c for track in chip 11 (lower phi), keeps information 
for track in chip 0. 
 
</pre>
<!-- Author: Evelyn Thomson -->


<!-- Date: Thu Oct 12 08:53:44 2000 -->
<pre>Here I prepared a few eps file from Chris and Evelyn's YBOS file. 
I made them in /cdf/home/jych/eps directory in fcdfsgi2 
 
I used /cdf/data08/_APHYSR.0000/ar018ab9.0001phys 
 
In 3001.eps, 3001 means event number. 
 
3001 gives clean single track. 
But in 3002, additional Hits we see. 
This is also the cases in 3003, 3004. 
 
In 3005 we don't have any hits, tracks. I could find such cases(no 
tracks, no hits) in many other events also. 
 
</pre>
<!-- Author: From jong-young -->


<!-- Date: Thu Oct 12 08:58:46 2000 -->
<table><tr><td><a href=/elog/notebooks/xft/Thu_Oct_12_2000_085837.ps align=top><img src=/elog/gifs/ghost64.gif  width='56' align='top'></td><td>The event displays from jong-young</a></td></tr></table>
<!-- Author: Evelyn Thomson -->
<!-- Comment: Fri Oct 13 09;24;54 comment by...Evelyn Thomson -->
  Report from the 8:00 AM Operations Meeting:

  * The next Tevatron shot setup was expected today, but will not happen
until 9AM tomorrow.  A kautzky valve was being fixed in an access this
morning

  * The solenoid is cold and Rob Roser et al plan to switch it on today.


  Recent Activities:

  * See elog for results of Jay's xtc to finder tests.

  * Took a run yesterday with simulated hit data loaded in the finders and
the software event builder.  Checked the events by looking into the banks
and using the event display.

When decoding the banks, the message "Missing linker" was reported a lot -
the print method for the XFLD bank was checking the uppermost 2 bits to
see if the board was present.  However, only the lower 24 bits are driven
with data!  Print method will be updated.

The event display pictures are in the elog, sometimes extra hits/tracks
are seen, could be due to input file.

  * Also asked the shift crew to include all XFT crates in a run with the
hardware event builder.  The run startup was successful.


  XFT Activities today:

  * Possiblity exists of a cosmic ray run if there is an extended period
without any beam in the Tevatron.  Otherwise, collisions tomorrow will be
the first time COT HV and the magnet are on.

  * Already tested sending data to second XTRP board.  Tested duplicate
track removal between XTRP boards.  Had to swap out LOM 5, chip 6-11 were
always late at the xtrp (many bits set).  Must be very careful to plug in
xtrp cable, saw some bit errors at xtrp, suspect I didn't plug the cable
in right.

  * Run a long-term test sending data to XTRP with duplicate tracks
flagged.

  * Run control - if a board has been swapped, but the hardware database
has not been updated with the new board's serial number, print out a
specific error message.  This should contain the expected and observed
serial number. The shift crew should then be able to update the hardware
database with the new serial number.  We're bound to forget to update the
database at some point...

  * xftdaq - finderboard - add check that finderboard flashrams contain
the standard designs for running.


<!-- Comment: Fri Oct 13 09;25;13 comment by...Evelyn Thomson -->
  Report from the 8:00 AM Operations Meeting:

  * The next Tevatron shot setup was expected today, but will not happen
until 9AM tomorrow.  A kautzky valve was being fixed in an access this
morning

  * The solenoid is cold and Rob Roser et al plan to switch it on today.


  Recent Activities:

  * See elog for results of Jay's xtc to finder tests.

  * Took a run yesterday with simulated hit data loaded in the finders and
the software event builder.  Checked the events by looking into the banks
and using the event display.

When decoding the banks, the message "Missing linker" was reported a lot -
the print method for the XFLD bank was checking the uppermost 2 bits to
see if the board was present.  However, only the lower 24 bits are driven
with data!  Print method will be updated.

The event display pictures are in the elog, sometimes extra hits/tracks
are seen, could be due to input file.

  * Also asked the shift crew to include all XFT crates in a run with the
hardware event builder.  The run startup was successful.


  XFT Activities today:

  * Possiblity exists of a cosmic ray run if there is an extended period
without any beam in the Tevatron.  Otherwise, collisions tomorrow will be
the first time COT HV and the magnet are on.

  * Already tested sending data to second XTRP board.  Tested duplicate
track removal between XTRP boards.  Had to swap out LOM 5, chip 6-11 were
always late at the xtrp (many bits set).  Must be very careful to plug in
xtrp cable, saw some bit errors at xtrp, suspect I didn't plug the cable
in right.

  * Run a long-term test sending data to XTRP with duplicate tracks
flagged.

  * Run control - if a board has been swapped, but the hardware database
has not been updated with the new board's serial number, print out a
specific error message.  This should contain the expected and observed
serial number. The shift crew should then be able to update the hardware
database with the new serial number.  We're bound to forget to update the
database at some point...

  * xftdaq - finderboard - add check that finderboard flashrams contain
the standard designs for running.


<!-- Date: Thu Oct 12 11:53:04 2000 -->
<pre>Finder To Linker Test. 
Ran on B0xft04 and 05 with XX_phi3090 (one of new vector files) 
I had no error until Loop# 343(total 1250 loops, 5000 events) 
 
I didn't find even split wire hit errors! Does new vector file 
has data 0 for split wire? 
 
 </pre>
<!-- Author: Jong-young Chung -->
<!-- Comment: Thu Oct 12 14;31;16 comment by...Jong-young Chung -->
I did stupid thing, 00_phi3090 which I used, doesn't have data 
other than 0 !!




<!-- Date: Thu Oct 12 17:32:04 2000 -->
<pre>Ran ttbar file on all 24 linkers and 48 finders.  Checked 
40 events.  Only errors found were pt errors, where there is 
a difference of 1 (or more) between the pt bins found and in 
simulation.  This only seems to happen for pt bins below 0x30, 
ie only for negative tracks.  In every case, the hardware track 
pt bin was smaller than the simulation pt bin 
 
 
 ERROR! Event 1 chip 1	 Linker track 	 wrd:  0	 tfnd:1	 phi:1	 pt:  d	 sht:0	 dupl:0	 FTLsys=3 
 ERROR! Event 1 chip 1	 Expect track	 wrd:  0	 tfnd:1	 phi:1	 pt:  e	 sht:0	 dupl:0 
 
Errors above found on loop 0, checking 4 L2 Buffers 
Linker is in crate 3 and slot 10 Finders are in slots 7, 8, 16, 17 
 
 ERROR! Event 0 chip 10	 Linker track 	 wrd:  1	 tfnd:1	 phi:0	 pt:  8	 sht:0	 dupl:0	 FTLsys=4 
 ERROR! Event 0 chip 10	 Expect track	 wrd:  1	 tfnd:1	 phi:0	 pt:  9	 sht:0	 dupl:0 
 ERROR! Event 2 chip 8	 Linker track 	 wrd:  2	 tfnd:1	 phi:5	 pt: 17	 sht:0	 dupl:0	 FTLsys=4 
 ERROR! Event 2 chip 8	 Expect track	 wrd:  2	 tfnd:1	 phi:5	 pt: 18	 sht:0	 dupl:0 
 ERROR! Event 2 chip 9	 Linker track 	 wrd:  2	 tfnd:1	 phi:3	 pt: 27	 sht:0	 dupl:0	 FTLsys=4 
 ERROR! Event 2 chip 9	 Expect track	 wrd:  2	 tfnd:1	 phi:3	 pt: 28	 sht:0	 dupl:0 
 ERROR! Event 2 chip 10	 Linker track 	 wrd:  1	 tfnd:1	 phi:7	 pt: 28	 sht:0	 dupl:0	 FTLsys=4 
 ERROR! Event 2 chip 10	 Expect track	 wrd:  1	 tfnd:1	 phi:7	 pt: 29	 sht:0	 dupl:0 
 
Errors above found on loop 0, checking 4 L2 Buffers 
Linker is in crate 3 and slot 12 Finders are in slots 8, 9, 17, 18 
 ERROR! Event 1 chip 7	 Linker track 	 wrd:  0	 tfnd:1	 phi:2	 pt: 25	 sht:0	 dupl:0	 FTLsys=13 
 ERROR! Event 1 chip 7	 Expect track	 wrd:  0	 tfnd:1	 phi:2	 pt: 26	 sht:0	 dupl:0 
 
Errors above found on loop 0, checking 4 L2 Buffers 
Linker is in crate 5 and slot 14 Finders are in slots 9, 10, 18, 19 
 ERROR! Event 3 chip 4	 Linker track 	 wrd:  1	 tfnd:1	 phi:6	 pt: 25	 sht:0	 dupl:0	 FTLsys=16 
 ERROR! Event 3 chip 4	 Expect track	 wrd:  1	 tfnd:1	 phi:6	 pt: 26	 sht:0	 dupl:0 
 ERROR! Event 3 chip 7	 Linker track 	 wrd:  0	 tfnd:1	 phi:1	 pt: 28	 sht:0	 dupl:0	 FTLsys=16 
 ERROR! Event 3 chip 7	 Expect track	 wrd:  0	 tfnd:1	 phi:1	 pt: 29	 sht:0	 dupl:0 
 
Errors above found on loop 0, checking 4 L2 Buffers 
Linker is in crate 6 and slot 4 Finders are in slots 4, 5, 13, 14 
 ERROR! Event 2 chip 8	 Linker track 	 wrd:  2	 tfnd:1	 phi:3	 pt:  b	 sht:0	 dupl:0	 FTLsys=17 
 ERROR! Event 2 chip 8	 Expect track	 wrd:  2	 tfnd:1	 phi:3	 pt:  c	 sht:0	 dupl:0 
 ERROR! Event 2 chip 11	 Linker track 	 wrd:  1	 tfnd:1	 phi:7	 pt:  d	 sht:0	 dupl:0	 FTLsys=17 
 ERROR! Event 2 chip 11	 Expect track	 wrd:  1	 tfnd:1	 phi:7	 pt:  e	 sht:0	 dupl:0 
 
Errors above found on loop 0, checking 4 L2 Buffers 
Linker is in crate 6 and slot 6 Finders are in slots 5, 6, 14, 15 
 ERROR! Event 2 chip 0	 Linker track 	 wrd:  0	 tfnd:1	 phi:6	 pt: 1b	 sht:0	 dupl:0	 FTLsys=18 
 ERROR! Event 2 chip 0	 Expect track	 wrd:  0	 tfnd:1	 phi:6	 pt: 1d	 sht:0	 dupl:0 
 ERROR! Event 2 chip 6	 Linker track 	 wrd:  0	 tfnd:1	 phi:4	 pt: 1b	 sht:0	 dupl:0	 FTLsys=18 
 ERROR! Event 2 chip 6	 Expect track	 wrd:  0	 tfnd:1	 phi:4	 pt: 1c	 sht:0	 dupl:0 
 
Errors above found on loop 0, checking 4 L2 Buffers 
Linker is in crate 6 and slot 8 Finders are in slots 6, 7, 15, 16 
 ERROR! Event 0 chip 5	 Linker track 	 wrd:  1	 tfnd:1	 phi:1	 pt:  9	 sht:0	 dupl:0	 FTLsys=21 
 ERROR! Event 0 chip 5	 Expect track	 wrd:  1	 tfnd:1	 phi:1	 pt:  a	 sht:0	 dupl:0 
 ERROR! Event 1 chip 6	 Linker track 	 wrd:  0	 tfnd:1	 phi:5	 pt:  1	 sht:0	 dupl:0	 FTLsys=21 
 ERROR! Event 1 chip 6	 Expect track	 wrd:  0	 tfnd:1	 phi:5	 pt:  6	 sht:0	 dupl:0 
 
 
 
</pre>
<!-- Author: Evelyn Thomson, Richard Hughes -->
<!-- Comment: Fri Oct 13 09;40;35 comment by...Evelyn Thomson -->
This only happens for some of the negative tracks, not all of them
<!-- Date: Thu Oct 12 18:25:25 2000 -->
<pre>Ran a few events of data from 10 finders to 4 linkers to 2 Xtrp 
boards.  Checked duplicate track removal works between Xtrp 
boards.  If the next xtrp board is missing, the track from chip 
11 is removed as a duplicate by default! 
 
Ran 2250 events from 6 finders to 2 linkers to 1 xtrp board. 
No errors found except for over-zealous duplicate track  
removal by xtrp.  Found an event with a track in linker chip 5 
with (phi=7, pt=3), but no track in linker chip 6 (phi=0, pt=7c) 
The xtrp removes the track in linker chip 5 anyway!   
 
Xtrp will check the algorithm they use to remove duplicate tracks 
- they should check that the pt!=7c in the next linker chip! 
 
Didn't run more events with the 2 xtrp boards due to a wild goose 
chase caused by me not plugging xtrp cables into LOMs correctly...</pre>
<!-- Author: Evelyn Thomson -->


<!-- Date: Thu Oct 12 18:27:18 2000 -->
<pre>Reprogrammed all finder input flashrams with the normal 
designs (xft13inpv2.exo and xft24inpv2.exo) so we will 
be ready if there are cosmic rays tonight!  Will ask shift crew 
to remember to include us in run also!</pre>
<!-- Author: Evelyn Thomson -->


<!-- Date: Thu Oct 12 18:32:54 2000 -->
<pre>Pixel mismatches between Finder and Linker 
Brian and I investigated  addtional hits and pixels in 
EventDisplay of YBOS file made tomorrow. 
(ar018ab9.0001phys) 
 
Here Dump out of Event 3001 to 3004 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*-* 
Event dump for Run 101049 Event     3001 
*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--* 
============================================================================ 
                                --Pixel Information--  
Crate    Slot    Chip    Cell    Marks   AbCell  Pixels  Cell Phi 
============================================================================ 
 1        9       3d      0       0      116     30      1.89804 
 1        9       1b      2       0      58      8       1.89804 
 1        18      4c      1       0      145     c0      1.89804 
 1        18      2b      3       0      87      8       1.89804 
 
*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--* 
========================================================= 
                  --Linker Input Pixels-- 
Crate    Slot    Chip    Ram     Word    Pixel 
========================================================= 
 1       12      3       1       3       8 
 1       12      4       1       2       8 
 1       14      0       1       0       30000 
 1       14      0       0       2       8000 
 1       14      1       0       3       8000 
 1       14      2       1       1       c0000 
==================================================================================== 
 
 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*-* 
Event dump for Run 101049 Event     3002 
*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--* 
============================================================================ 
                                --Pixel Information--  
Crate    Slot    Chip    Cell    Marks   AbCell  Pixels  Cell Phi 
============================================================================ 
 0        8       3b      2       0      350     f00     5.72686 
 0        8       1a      3       0      175     180     5.72686 
 0        17      4a      2       0      438     f0      5.7334 
 0        17      2a      3       0      263     c       5.73777 
 2        8       3c      0       0      224     c       3.66519 
 2        8       1b      0       0      112     18      3.66519 
 2        17      4b      0       0      280     c       3.66519 
 2        17      2b      0       0      168     c       3.66519 
 
*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--* 
========================================================= 
                  --Linker Input Pixels-- 
Crate    Slot    Chip    Ram     Word    Pixel 
========================================================= 
 2       10      3       1       0       c 
 2       10      4       0       0       c 
 2       10      4       1       0       18 
 2       10      5       0       0       c000 
 2       12      0       0       0       18000 
 2       12      0       1       0       c 
 2       12      1       0       0       c000 
 2       12      2       1       0       c 
  
==================================================================================== 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*-* 
Event dump for Run 101049 Event     3003 
*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--* 
 
============================================================================ 
                                --Pixel Information--  
Crate    Slot    Chip    Cell    Marks   AbCell  Pixels  Cell Phi 
============================================================================ 
 0        5       3c      2       0      306     3       5.00691 
 0        5       1b      1       0      153     c       5.00691 
 0        14      4b      2       0      382     c0      5.00036 
 0        14      2b      1       0      229     180     4.996 
 1        8       3c      3       0      99      c00     1.61988 
 1        8       1b      2       0      50      6       1.63624 
 1        17      4c      0       0      124     f00     1.62315 
 1        17      2b      2       0      74      800     1.61443 
 1        17      2b      3       0      75      1       1.63624 
 
*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--* 
========================================================= 
                  --Linker Input Pixels-- 
Crate    Slot    Chip    Ram     Word    Pixel 
========================================================= 
 1       10      3       1       2       800 
 1       10      3       1       3       1 
 1       10      4       1       2       6 
 1       10      5       0       3       c00000 
 1       12      0       0       2       6000 
 1       12      0       1       3       c00 
 1       12      1       0       2       800000 
 1       12      1       0       3       1000 
 1       12      2       1       0       f00000 
  
==================================================================================== 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-**-*-*-*-*-*-*-*-*-*-*-* 
Event dump for Run 101049 Event     3004 
*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--* 
============================================================================ 
                                --Pixel Information--  
Crate    Slot    Chip    Cell    Marks   AbCell  Pixels  Cell Phi 
============================================================================ 
 0        8       3c      2       0      354     c00     5.79231 
 0        8       1b      1       0      177     c0      5.79231 
 0        17      4b      3       0      443     c0      5.79885 
 0        17      2b      2       0      266     c       5.80321 
 1        9       3b      1       0      109     3       1.78351 
 1        9       1a      2       0      54      300     1.76714 
 1        18      4a      0       0      136     3c      1.78023 
 1        18      2a      1       0      81      c00     1.76714 
 
*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--* 
========================================================= 
                  --Linker Input Pixels-- 
Crate    Slot    Chip    Ram     Word    Pixel 
========================================================= 
 1       12      3       1       0       3c000 
 1       12      3       0       1       c00000 
 1       12      4       0       2       300000 
 1       12      5       0       1       3 
 1       14      0       0       2       300 
 1       14      1       0       1       c00 
 1       14      2       0       0       3c000 
  
==================================================================================== 
</pre>
<!-- Author: Jong-young  -->
<!-- Comment: Tue Oct 17 10;26;54 comment by...Jong-young -->
NOT tommorrow , Yesterday. in third line, Sorry.
<!-- Comment: Tue Oct 17 10;27;24 comment by...Jong-young Chung -->
NOT tommorrow , Yesterday. in third line, Sorry.
<!-- Date: Fri Oct 13 09:27:24 2000 -->
<pre> Report from the 8:00 AM Operations Meeting: 
 
  * The solenoid was ramped up to full field yesterday at 5pm, BUT as the 
solenoid approaches full field, the fans in the COT racks fail, causing 
the 60Hz and 400Hz power to trip off on both walls.  This means that the 
clock fanout crates are also off, so no central detector crate has clock 
signals.  Putting a 0.6T AlNiCo magnet underneath a fan pack produced no 
alarms but grinding noises were heard - it appears that fan blades are 
grinding against the fan guard!  The solenoid field was left down for the 
night, an access was proposed for this morning to find out what happens in 
the collision hall when the solenoid field is ramped up... to be continued 
in the shift elog. 
 
 * Collisions possible from 12pm on.  The COT HV will only be switched on 
when the solenoid magnetic field on (at some undetermined level). 
 
 * The event display will run on a special node in the control room, with 
accelerated graphics hardware. 
 
 * 3 TDC's are known to have blown buffer chips.  Jay suspects the number 
to be more like 9 from his own tests. 
 
 * The shift crew included all XFT crates and the XTRP crate in overnight 
runs.  One note of xpt errors for XFT00, 02 and 04 at 22:34. 
 
 
  Recent Activities: 
 
 * Ran data to second XTRP data board.  Duplicate track removal between 
linkers boards checked.  Over-zealous track removal observed, with a track 
with phi=7 in linker chip 5 being removed, even though there is no track 
found in linker chip 6 (phi=0 but pt=7c)  - see elog entry 18:25 
 
 * Ran ttbar events through whole XFT system.  Observed pt errors for 
negative tracks only.  The hardware pt bin is sometimes 1 or more bins 
lower than the simulation pt.  Brian is investigating - the algorithm for 
setting the bits of negative pt tracks is more complicated, hopefully this 
is a bug in the simulation!  See elog entry 17:32 
 
 * Brian and Jong-young investigated the extra hits/pixels observed in the 
run taken with the single track per event files - see elog pictures from 
yesterday.  The extra hits/pixels are only in the finderboard.  The extra 
pixel words look slightly shifted from those for the genuine tracks - may 
be a readout problem? See elog entry 18:32 
 
 
  XFT Activities today: 
 
 * Wait for data, write some documentation, software tidy-up.  
 
 * Jay will try to run xtc to finder tests, should the DAQ not be using 
some of the COT crates.  This is to diagnose the remaining problems, which 
we could try to fix in a planned supervised access on Monday. 
 
 * I will be gone this afternoon, but have made arrangements to contact 
Jay should I be paged. 
                          </pre>
<!-- Author: Evelyn Thomson -->
<!-- Comment: Fri Oct 13 09;34;03 comment by...Jay D -->
Just to clarify...before the 8am meeting I found 9 TDCs that
were not appearing in the crate map.  This symptom may be caused either by blown buffer chips or a non-responsive VME interface chip.  There's no easy way to be sure that buffer chips are blown
without inspecting the boards.



<!-- Date: Sat Oct 14 16:45:51 2000 -->
<pre>I spent a sunny Saturday afternoon looking at the 19 XTC's 
that have been returned from FNAL.  Here's what I found. 
 
XTC 53, 115, and 41 had been in the detector, and we had 
seen evidence for the "stuck bit" problem that I had seen 
on some boards during the original checkout.  I confirmed 
this problem here. 
 
XTC 213 had come from Ting with an unknown complaint.  This 
board also had stuck bits.  We now have a total of 24 boards 
(20 of which never went to FNAL) that show this problem, and 
I am interested in solving it. 
 
XTC 15 had supposedly had stuck bits, and was removed from 
the detector during the Labor Day weekend.  I am not able to 
confirm this; the board seems just fine, passing Finder 
capture tests. 
 
XTC 120 had come from Ting.  I found that it only operated 
properly if 22DEL=2C instead of our usual 34.  Much to my 
chagrin, I had seen that on this board during checkout, and 
even noted it in my records.  Further study showed that there 
was a delay chip that needed reflowing; after that, the board 
works just fine with 22DEL=34. 
 
XTC 228 had come from Ting.  I did not find any problems with 
this board. 
 
XTC 66 had been pulled from the detector with the complaint 
that no bits were coming up the cable.  I saw this happening 
intermittently; it mostly worked, but not always.  I could 
not identify a problem on the board that could cause this, so 
we should keep it out of the detector. 
 
XTC 122 has the B0 marker in the wrong place; it's 132 ns long, 
but it should be 22 ns earlier (or the data and the W0 marker 
should be 22 ns later).  I could not figure out why this was 
happening, so we should keep the board out of the detector. 
 
XTC 206 was removed from the detector (by me) with the 
complaint that many delayed bits were being dropped.  I could 
not confirm this here; the board seems to be just fine. 
 
XTC 186, 54, and 51 had all been in crate b0cot10, slots 11, 
9, and 7.  These had all been showing many missing prompt bits. 
However, I am not able to confirm this problem on any of the 
boards.  Since they all had the same problem and they are all 
in the same crate, I have to wonder whether there is a problem 
with that crate.  (Or maybe the Finder -- do they all go to the 
same one?) 
 
XTC 199 and 205 had B0 markers that were occasionally too short 
by 22 ns.  Jay and I had looked at this, and it did seem like 
these cards needed a non-standard 22DEL setting.  I was not able 
to confirm this; both cards worked at the standard value of 
22DEL=34.  They did not manifest a B0 problem until 22DEL was 
set to 40 or 37, respectively. 
 
The remaining four boards were expected to be just fine.  This 
was not quite the case.  XTC 194 has some sort of glitch in 
the late gate, and I couldn't track it down.  We should keep 
it out of the detector.  XTC 93, 203, and 231 were all fine. 
 
I will consult with Jay and we'll decide which of these boards 
we should back in the pool for installation.</pre>
<!-- Author: Ken Bloom -->