<!-- Title: 10:21:17  Mon Oct 16 2000 -->
<!-- Crewchief: Evelyn Thomson -->
<!-- Op1: Jay Dittmann -->
<!-- Op2: Phil Koehn -->
<!-- Op3: Chris Neu -->
<!-- Op4: Jong-young Chung -->
<!-- Op5: Richard Hughes -->
<!-- Op6: Brian Winer -->
<!-- Notes: -->
<pre>New logbook for week beginning Monday October 16th</pre>


<!-- Date: Mon Oct 16 10:24:16 2000 -->
<pre>  Report from the 8:00 AM Operations Meeting: 
 
* Collisions on Friday evening and Saturday morning!!! Magnet was on - 
relays, not the fans, seemed to be affected by magnetic field.  COT was 
included in several runs.  See runs 101403, 101424-101427.  Cosmic ray 
runs taken over the rest of the weekend. See shift elog and run summary 
elog for more details. 
 
* Next collisions expected on Friday. 
 
 
  XFT Activities today: 
 
* Supervised access right now. Chris & Jay downstairs fixing 
TDC/transition board problems.  I'm running XTC to Finder tests upstairs 
to check that the problems are fixed and the status of the crates before 
the end of the access. 
 
* Look at runs taken over the weekend. 
 
* Try new ttbar files in finder to linker test. 
 
</pre>
<!-- Author: Evelyn Thomson -->


<!-- Date: Mon Oct 16 14:37:55 2000 -->
<pre>I found an interesting thing in XFT bank dump of events made last  
weekend. 
 
This is output of 018c1b. 
 
Event dump for Run 101403 Event     4390 
================================================================================================= 
                                        --Wire Hit Information-- 
Crate    Slot    Chip    Cell    AbCell  Cable   Prompt Delayed  Marks  TDCCrt   TDCSlt  TDChalf 
================================================================================================= 
  0       7       3d      2       342    205     1        1       0      9        9      1 
  0       8       3a      0       344    206     40       40      0      9        8      0 
  0       8       3b      0       348    207     40       40      0      9        8      1 
  0       8       1a      0       172    43      fff      fff     0      9        15     0 
  0       8       1a      1       173    43      ccc      ccc     0      9        15     0 
  0       8       1a      2       174    43      fff      fff     0      9        15     0 
  0       8       1a      3       175    43      fff      fff     0      9        15     0 
  0       8       1b      0       176    44      fff      fff     0      9        15     1 
 
 
 
Event dump for Run 101403 Event     4389 
================================================================================================= 
                                        --Wire Hit Information-- 
Crate    Slot    Chip    Cell    AbCell  Cable   Prompt Delayed  Marks  TDCCrt   TDCSlt  TDChalf 
================================================================================================= 
  0       7       3d      2       342    205     1        1       0      9        9      1 
  0       8       3a      0       344    206     40       40      0      9        8      0 
  0       8       3b      0       348    207     40       40      0      9        8      1 
  0       8       1a      0       172    43      fff      fff     0      9        15     0 
  0       8       1a      1       173    43      ccc      ccc     0      9        15     0 
  0       8       1a      2       174    43      fff      fff     0      9        15     0 
  0       8       1a      3       175    43      fff      fff     0      9        15     0 
  0       8       1b      0       176    44      fff      fff     0      9        15     1 
  0       8       1b      1       177    44      fff      eee     0      9        15     1 
  0       8       1b      2       178    44      bbb      bbb     0      9        15     1 
  0       8       1b      3       179    44      fff      fff     0      9        15     1 
  0       9       3a      0       360    210     777      777     0      0        10     0 
  0       9       3a      1       361    210     fff      fff     0      0        10     0 
  0       9       3a      2       362    210     eee      eee     0      0        10     0 
 
 
Event dump for Run 101403 Event     4392 
================================================================================================= 
                                        --Wire Hit Information-- 
Crate    Slot    Chip    Cell    AbCell  Cable   Prompt Delayed  Marks  TDCCrt   TDCSlt  TDChalf 
================================================================================================= 
  0       7       3d      2       342    205     1        1       0      9        9      1 
  0       8       3a      0       344    206     40       40      0      9        8      0 
  0       8       3b      0       348    207     40       40      0      9        8      1 
  0       8       1a      0       172    43      fff      fff     0      9        15     0 
  0       8       1a      1       173    43      ccc      ccc     0      9        15     0 
  0       8       1a      2       174    43      fff      fff     0      9        15     0 
  0       8       1a      3       175    43      fff      fff     0      9        15     0 
  0       8       1b      0       176    44      fff      fff     0      9        15     1 
  0       8       1b      1       177    44      fff      eee     0      9        15     1 
  0       8       1b      2       178    44      bbb      bbb     0      9        15     1 
  0       8       1b      3       179    44      fff      fff     0      9        15     1 
  0       9       3a      0       360    210     777      777     0      0        10     0 
  0       9       3a      1       361    210     fff      fff     0      0        10     0 
  0       9       3a      2       362    210     eee      eee     0      0        10     0 
  
Event dump for Run 101403 Event     4391 
 
================================================================================================= 
                                        --Wire Hit Information-- 
Crate    Slot    Chip    Cell    AbCell  Cable   Prompt Delayed  Marks  TDCCrt   TDCSlt  TDChalf 
================================================================================================= 
  0       7       3d      2       342    205     1        1       0      9        9      1 
  0       8       3a      0       344    206     40       40      0      9        8      0 
  0       8       3b      0       348    207     40       40      0      9        8      1 
  0       8       1a      0       172    43      fff      fff     0      9        15     0 
  0       8       1a      1       173    43      ccc      ccc     0      9        15     0 
  0       8       1a      2       174    43      fff      fff     0      9        15     0 
  0       8       1a      3       175    43      fff      fff     0      9        15     0 
  0       8       1b      0       176    44      fff      fff     0      9        15     1 
  0       8       1b      1       177    44      fff      eee     0      9        15     1 
  0       8       1b      2       178    44      bbb      bbb     0      9        15     1 
  0       8       1b      3       179    44      fff      fff     0      9        15     1 
  0       9       3a      0       360    210     777      777     0      0        10     0 
  0       9       3a      1       361    210     fff      fff     0      0        10     0 
  0       9       3a      2       362    210     eee      eee     0      0        10     0 
 
 
....... 
 
 
What do you think about this ? 
 
 
</pre>
<!-- Author: Jong-young Chung -->


<!-- Date: Mon Oct 16 15:02:40 2000 -->
<pre>Results from XTC/TDC work in supervised access 
 
CONWB-1 b0cot09 slot 15A,15B:- replaced COT transition board 57 
with transition board 187.  XTC->Finder test now works 
 
CONEB-1 b0cot19 slot 8A:-replaced COT transition board 185 with 
board 13.  The original error 0x002 stuck intermittently.  Ran 
100 events and 10 loops of full test with no errors today. 
 
COSEB-1 b0cot16 slot 5B:-replaced COT transition board 82 with 
board 185.  0X100 still always stuck. 
 
-------------------------------------------------------------  
Ran Xtc->Finder test on all TDCs after access: quick test and 
full test with 10 events and 10 loops.   
 
***Only found 3 errors!*** 
 
CONET-3 b0cot10 slot 10A fails, read 0x0 
COSEB-1 b0cot16 slot 5B fails, 0x100 stuck 
CONEB-1 b0cot19 slot 17B fails, 0x800 stuck 
 
------------------------------------------------------------ 
Swapped boards (from Jay's cratemap) 
COSEB-2 b0cot17 slot 10 TDC 336->687, slot 11 TDC 186->709 
CONEB-1 b0cot19 slot 10 TDC 316->210, slot 11 TDC 299->544 
Tracer also swapped in b0cot19</pre>
<!-- Author: Evelyn Thomson (with Jay Dittmann and Chris Neu) -->


<!-- Date: Mon Oct 16 15:59:53 2000 -->
<pre>Tested new ttbar files - no errors observed.  This means we 
need a new standard linker design file!   
</pre>
<!-- Author: Evelyn Thomson -->


<!-- Date: Mon Oct 16 16:02:59 2000 -->
Why?
<!-- Author: {Quick_Entry} -->


<!-- Date: Mon Oct 16 17:47:44 2000 -->
<pre>Linker to Finder Test 
On b0xft04,05, 
With ttbar2 files. 
Using all events (100 events) in that files. 
00,01 ... 07, 10,11,12_ttbar2 (11 files used ) 
No error found.</pre>
<!-- Author: Jong-young Chung -->


<!-- Date: Tue Oct 17 10:13:31 2000 -->
<pre>  Thanks for the info.   It definitely worked.  I've been going 
through a bunch of the events by hand just to see what's going 
on. Here is what I see: 
 
1.  Starting with event 484, I see one track in the XTRP on each 
event.  On every event I checked in detail (about 8) there was 
total agreement between XFLD and XTRD.  I went through many more 
events in less detail (see below). 
 
2.  I see tracks show up in each of the 4 wedges of interest. 
 
3.  In the output file, the pattern of tracks doesn't loop over 
the same 16 tracks in a row.  This isn't surprising because 4 
events in a row are read out(Myron mode) and then there is some 
delay until 4 more events are read out.  The 4 events in a row 
show the repeating pattern, but the pattern jumps between sets of 4. 
 
4.  I think the XFLD offline "formatted" dump doesn't like the 
fact that you read out 2 linker crates.   On some of the events, 
the formatted dump doesn't report a track, even though it's there 
in the raw dump of XFLD and it shows up in the XTRP.  I didn't 
notice this at all in last week's run when you were reading out 
all 3 crates. 
 
Overall, things look quite good.  We'll try running our XTRPMon 
code on this file tomorrow to look at things in more detail. 
 
********************************** 
Run 0x18cc6 should have tracks in the xtrp bank.  Events after 
900 should be valid.  The events should be the first 16 events 
from the _phi3090_ set. 
 
> 10_phi3090 -> linker in slot 4 -> xtrp slot 7 wedge A 
> 11_phi3090 -> linker in slot 6 -> xtrp slot 7 wedge B 
> 12_phi3090 -> linker in slot 8 -> xtrp slot 8 wedge A 
> 13_phi3090 -> linker in slot 10 -> xtrp slot 8 wedge B 
 
 
</pre>
<!-- Author: From Kevin Pitts -->


<!-- Date: Tue Oct 17 10:26:56 2000 -->
<pre>  Report from the 8:00 AM Operations Meeting: 
 
* 2 flammable gas alarm tests produced 2 power cuts during the supervised 
access yesterday.  Fringe field around solenoid was mapped yesterday, can 
be as high as 50 Gauss near the yoke, 20-30 Gauss inside the crates.  The 
relay operation limit is around 30 Gauss, these will be replaced, bypassed 
for now. 
 
* Busy condition reported in all 3 finder crates Similar messages appeared 
for other systems at other times.  See shift elog, Monday 21:34, for more 
details. 
 
* b0cot19 cannot be included in readout, due to access/power cuts.  See 
shift elog, Monday 14:25, for more details.  We can run XTC to Finder 
tests with this crate though. 
 
 
 Recent XFT Activities: 
 
* Fixed one problem by swapping a COT transition board.  3 problems 
remain, see xft elog, Monday 15:25, for more details. 
 
* Ran Finder to Xtrp test and took a run with tracks in xtrp.  See elog 
for feedback from Kevin Pitts (Tuesday 10:13) 
 
* A new standard linker design file is needed.  Previously, the pt bins 
were different by 1 or more bins between hardware and simulation for 
negatively charged tracks.  The simulation is apparently setting the 
correct pt bin, while hardware is not.  The test of the new ttbar files 
proved this. 
 
 
  XFT Activities today: 
 
* Look at runs taken over the weekend. 
 
* Test duplicate track removal at XTRP - check that new algorithm doesn't 
still remove tracks in chips 5(11) when there is no track in the 
neighbouring chip.  Use b0xft02 and b0xft03 for this. 
 
* Chris wants a finder and a linker crate for more run control tests. 
 
* Jay is using b0xft00 and b0cot10 and b0cot19 to investigate 2 of the 3 
remaining xtc to finder errors. 
 
* Find out why event display doesn't show any xft information for runs 
taken last weekend. 
</pre>
<!-- Author: Evelyn Thomson -->


<!-- Date: Tue Oct 17 14:17:40 2000 -->
<pre>Checked new duplicate track removal algorithm from XTRP. 
Over-zealous track removal gone! 
 
 
 
Event 193 chip 5	 Linker track 	 wrd:  1	 tfnd:1	 phi:7	 pt: 39	 sht:0	 dupl:0	 FTLsys=0 
Event 193 chip 5	 Expect track	 wrd:  1	 tfnd:1	 phi:7	 pt: 39	 sht:0	 dupl:0 
Event 193 chip 5	 Xtrp track 	 wrd:  	 	 tfnd:1	 phi:7	 pt: 39	 sht:0	 xtrpdupl:0 
Event 193 chip 6	 Linker track 	 wrd:  0	 tfnd:0	 phi:0	 pt: 7c	 sht:0	 dupl:0	 FTLsys=0 
Event 193 chip 6	 Expect track	 wrd:  0	 tfnd:0	 phi:0	 pt: 7c	 sht:0	 dupl:0 
Event 193 chip 6	 Xtrp track 	 wrd:  	 	 tfnd:0	 phi:0	 pt: 7c	 sht:0	 xtrpdupl:0 
</pre>
<!-- Author: Evelyn Thomson -->


<!-- Date: Tue Oct 17 17:23:07 2000 -->
<pre>I am trying to look at some data from Run 101426 using ACDump. 
 
I am having a problem skipping n events and looking at just the 
nth event.  It seems as if there is a bug in the code (or more 
likely in my tcl file) that causes not the first N events to be 
skipped, but the first (N+10) events.  Try this and tell me if  
you have similar experiences.  My tcl file is located in 
fcdfsgi2:~neu/acdump/acdump.tcl 
 
The good news is that the bank formatting appears to be  
correct.  I must admit though that I did not look too closely.   
I also tried to look at some events with evd 
but it is so damn slow.  Frustrated, I will look more tomorrow. 
Could we speed this evd up by removing the display of the  
silicon? 
</pre>
<!-- Author: Chris -->


<!-- Date: Wed Oct 18 09:53:59 2000 -->
<pre>  Report from the 8:00 AM Operations Meeting: 
 
* xft crates included overnight.  We should notify the shift crew when we 
take/return xft and xtrp crates for tests.  See shift elog for details. 
 
 Recent XFT Activities: 
 
* Looked at run taken for xtrp (0x18cc6).  Running Brian's version of 
xfld_storableBank print method, see tracks in every event, which agree 
with those seen by xtrp yesterday.  No missing linker board messages for 
linker crate 1 either.  So it looks like the version in Brian's directory 
is different from the default one.  Brian will send this updated version 
to Simona Rolli asap! 
 
* Non-duplicate track removal by xtrp fixed.  New algorithm checks that 
there is a duplicate track (pt != 7c and phi<2) in the adjacent linker 
chip (6 or 0), before removing the track with phi>5 in the previous linker 
chip (5 or 11). 
 
* Finder to xtrp test was very slow yesterday.  Frank Chlebana mentioned 
bus errors in the ts crate at about the same time.   Frank asks 
that we log in to the b0tsi00 crate to see if there are any 
errors before we start our tests and if they start when we 
run our tests.  Such bus errors were occurring just now - and we 
weren't running any code... 
 
* Clock glitches 
prevented a long-term finder to xtrp test.  Will modify code to write out 
a log file in future. 
 
* Jay found a bent pin in b0xft00, which was causing one of the errors on 
xtc to finder tests.  He has fixed it enough so that the test works and 
the finder transition card can be removed and reinserted repeatedly 
without causing the test to fail. 
 
* Concluding that we only have 2 errors left is overly optimistic!  Jay 
said that intermittent errors (ie not a stuck bit on every event) appear 
the longer you run the xtc to finder test... 
 
 
  XFT Activities today: 
 
* Look at runs taken over the weekend, event display + bank dumps.  See 
David Saltzberg's useful classification of runs taken with COT in at 
http://www-cdf.fnal.gov/upgrades/daq_trig/twg/comm_data.txt 
 
* Run a long-term finder to xtrp test during the day.  I will use 
b0xft00-03, as long as Jay doesn't need them.  Take a run with the single 
track file and write banks to investigate the extra pixels in the finder 
bank. 
 
* Chris will need a finder crate and a linker crate for run control test-> 
b0xft04 and b0xft05. 
 
</pre>
<!-- Author: Evelyn Thomson -->


<!-- Date: Wed Oct 18 16:38:08 2000 -->
<pre>Looking at data with ACDUMP:  Run 101426dec = 18c32hex 
Sampled a small number of events ~20: 
 
*  The bunch counters for events match between XFFD and XFLD      
   single event dumps. 
 
*  From knowledge of known COT crate problems and readout  
   exclusions, we were able to explain several questionable 
   blocks of data.  For example, here is a portion of one XFFD    	 
   dump: 
================================================================================================= 
 	 	 	 	 	--Wire Hit Information-- 
Crate 	 Slot  	 Chip 	 Cell 	 AbCell	 Cable	 Prompt	Delayed	 Marks 	TDCCrt	 TDCSlt	 TDChalf 
================================================================================================= 
			. 
			. 
			. 
 0	  11	  3b	  0	  12	 123	 fff	  fff	  0	 0	  6	 1 
  0	  11	  3b	  1	  13	 123	 fff	  fff	  0	 0	  6	 1 
  0	  11	  3b	  2	  14	 123	 eee	  eee	  0	 0	  6	 1 
  0	  11	  3b	  3	  15	 123	 eee	  eee	  0	 0	  6	 1 
  0	  11	  3c	  0	  16	 124	 777	  777	  0	 0	  5	 0 
  0	  11	  3c	  1	  17	 124	 aaa	  aaa	  0	 0	  5	 0 
  0	  11	  3c	  2	  18	 124	 fff	  fff	  0	 0	  5	 0 
  0	  11	  3c	  3	  19	 124	 777	  777	  0	 0	  5	 0 
 
			. 
			. 
			. 
 
   This looks like the effect Jong-Young noticed Monday.  This 
   data is coming from COT crate 00, which has no power; thus  
   one should expect the data to be garbage.  There were several 
   such instances in which we identified suspicious data, and 
   traced the problem back to known COT TDC shortcomings. 
 
*  This collision data came in a Myron mode 1x8 store; thus one 
   would expect the bunch counters of the 4 consecutive events 
   to be consecutive, with bc's running 158-0-1-2.  We do in fact 
   see this! 
   
*  From the way the XTC sends data to the Finder, though, Jay and 
   Ken hypothesized that the data for events 158-0-1 should be  
   the SAME, with event 2 having something different.  We do   
   in fact see that the data for events 158-0-1 are nearly  
   equivalent.  However, the data for event 2 in each cycle  
   is ALSO nearly equivalent.  We do not understand this. 
 
*  Events are not written out in order.  In fact, events from  
   each 158-0-1-2 cycle are not necessarily grouped in 4 event  
   bundles together. 
 
*  At the beginning of the dump, the first ~10 records are  
   skipped. Also, the first record gives the event and run  
   numbers in decimal, while the rest of the events have these 
   values in hex. 
</pre>
<!-- Author: Chris, Jay and Ken -->
<!-- Comment: Wed Oct 18 20;17;05 comment by...Ken -->
We now understand why the data are the same for all four cycles,
not for just three.  The outputs of the XTC are only refreshed
when a CDF_BC comes through.  Since we were on a 1 x 8 clock,
this only happened once every revolution, not every third 
crossing.  We would expect the following 155 crossings to have
the same data too!
<!-- Date: Wed Oct 18 17:20:27 2000 -->
<pre>Looked at 018cc6 file which has been made by Evelyn monday. 
By Evelyn, 
"Events after 900 should be valid.   
The events should be the first 16 events from the _phi3090_ set." 
 
So I looked at event Number 900 to 918. 
 
In event display, I saw clean 1 track events 
You can see them in my directory. 
/cdf/scratch/jych/pic in fcdfsgi2 
101574_900.ps .....101574_918.ps 
 
I also, ran XFTSim to compare these events and simulated one. 
(Recently I modified XFTSim so that it can feed hit information from XFFD bank of Real data and generate simulated bank) 
So I compared  018cc6 with one simulated from its hit data. 
 
I found Finder and linkers are working well. without any  
significant data mismatch. Only one you can suspect in my dump 
file is  Linker Board  7  
It has many mismatch in Input formatter. I understood soon that 
this comes from the fact that she used only b0xft02 and b0xft03 
 
I guess XFTSim made such data from adjacent invalid hit data  
from b0xft04.. 
You also can see my results in /cdf/scratch/jych/dump  
file 018cc6_900.dump 
 
 
</pre>
<!-- Author: Jong-young Chung -->



<!-- Date: Thu Oct 19 14:47:51 2000 -->
<pre>Today we looked further at the data for run 101426.  Of the >850 
events in this run, there are several that have XFT tracks: 
 
		 
Event:	235		         429               573 
        236                      430               574 
        282                      431               575 
        281                      432               576 
        284                      517               731 
        283                      518               732 
                                 519 
                                 520 
 
Upon looking at these events with Event Display, we see that most  
of these tracks are from garbage hits in areas where there are 
no TDCs.  However, events 429-423 (really THE SAME event) do in 
fact point toward an area of the COT that has TDCs. 
 
This is exciting news!  Further analysis is needed to be done, 
but this is encouraging. 
 
A closer look at the hits on the wires without the overlay of  
this XFT track shows a prompt-delayed pttern that does indeed 
look like it would fire a pixel!  See: 
 
/cdf/scratch/jych/cpr/101426_430_notrack.ps, cot_1.ps, zoom1.ps  
for closeups.</pre>
<!-- Author: Jay, Jong-Young, Chris -->
<!-- Comment: Thu Oct 19 16;27;31 comment by...Chris -->
See /cdf/scratch/jych/cpr/101426_430.ps for the Event Display pic WITH the XFT track.
<!-- Date: Thu Oct 19 15:08:50 2000 -->
<pre>Now I made ps files with 101824. 
Evelyn made 101824 with ttbar vector file. 
It seems only two linker crates were used. 
 
I made only 19 files. event number 1050 to 1068 
 
They are in /cdf/scratch/jych/pic/101824_1050.ps ...1068.ps 
 
</pre>
<!-- Author: Jong-young -->
<!-- Comment: Thu Oct 19 15;10;37 comment by...Jong-young chung -->
We need to include all three crates for complete coverage

<!-- Comment: Thu Oct 19 15;18;05 comment by...Jong-young Chung -->
1051, 1056, 1061, 1063, 1068 have similar tracks in it.

<!-- Comment: Thu Oct 19 15;45;27 comment by...Evelyn Thomson -->
Also, it seems like there should be many more tracks found in the 2 linker crates that do have finder hits shown.  The third linker
and finder crates were included (their bunch counters agree with the other crates), but all the data is zero.   See ~thomsone/logs/ on fcdfsgi for more details.

<!-- Comment: Thu Oct 19 16;23;16 comment by...Chris -->
Did the third finder crate get its flashram loaded with
a driver design for the input section?

Can we try this again?



<!-- Date: Thu Oct 19 16:57:39 2000 -->
<pre>For everyone's personal knowledge... 
 
If one is to ever swap a Finder or Linker board out of the  
system, one must update the hardware db.  Here is what you do: 
 
On b0dapxx, 
 
1.  prompt> setup fer devel 
  
2.  prompt> java hdwusr.CardEditor XFTLINKER_00  
        (This number 00 is slot 4 b0xft01; there are 24 entries 
 in the hdwdb 00-23 corresponding to the 23 Linker slots NOT  
serial/ID number.  So slot 8 in b0xft05 is XFTLINKER_18)    
 
Similar entries exist for the 48 Finder boards in the system. 
 
3.  Got to File - Change Database Connection 
 
4.  Input the username and password; one can get this from me or  
the Ace or Bill Badgett when necessary. 
 
5.  Change your fields, remembering to press Enter when done with each field 
 
6.  When all adjustments are completed, go to File - Close 
 
 
 
</pre>
<!-- Author: Chris -->


<!-- Date: Thu Oct 19 17:28:21 2000 -->
<pre>I looked at XFTSim - XFTMonitor output of 101824 (ttbar). 
They seem to have a lot of input formatter mismatches and 
a few Finder pixel output mismatch. 
 
examples of Finder pixel output mismatch,.. 
 
 == Bit by bit print out for Crate [0] Finder 1/3 Board  [5]    Chip 1-[b] Cell 2,3 
 (11:0 Cell 2 Pixel, 12 B0, 13 W0, 14 Err, 27:16 Cell 3 Pixel, 28 B0, 29 W0, 30 Err) 
   +++ simulated word bits : 0000 0000 0000 0000 0000 1100 0000 0000  
   +++ Real      word bits : 0001 0000 0000 0000 0001 1110 0000 0000  
 ** event number =1053 
 == Bit by bit print out for Crate [0] Finder 1/3 Board  [6]    Chip 1-[b] Cell 2,3 
 (11:0 Cell 2 Pixel, 12 B0, 13 W0, 14 Err, 27:16 Cell 3 Pixel, 28 B0, 29 W0, 30 Err) 
   +++ simulated word bits : 0000 0000 0000 0000 0000 0000 0000 0000  
   +++ Real      word bits : 0000 0111 1000 0000 0000 0000 0000 0000  
 ** event number =1053 
 == Bit by bit print out for Crate [1] Finder 1/3 Board  [5]    Chip 1-[b] Cell 2,3 
 (11:0 Cell 2 Pixel, 12 B0, 13 W0, 14 Err, 27:16 Cell 3 Pixel, 28 B0, 29 W0, 30 Err) 
   +++ simulated word bits : 0000 0000 0000 0000 0000 0111 1000 0001  
   +++ Real      word bits : 0000 0000 1001 0000 0000 0111 1000 0001  
 ** event number =1053 
 
 
Examples of Input formatter of Linker boards.. 
 
 == Bit by bit print out for Crate [0] Linker Board  [4]    Input Formatter [4] 
 Finder 2&3, cell [0] (11:0 Finder 2. 23:12 Finder 3)  
   +++ simulated word bits : 0000 0000 0000 0000 0000 0001 1100 0000  
   +++ Real      word bits : 1101 1111 0000 0000 0000 0000 1100 0000  
 ** event number =1053 
 == Bit by bit print out for Crate [0] Linker Board  [4]    Input Formatter [4] 
 Finder 0&1, cell [1] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 1110 0000 0000 0000 0000 0000  
   +++ Real      word bits : 1101 1111 0000 0000 0000 0000 0000 0000  
 ** event number =1053 
 == Bit by bit print out for Crate [0] Linker Board  [4]    Input Formatter [4] 
 Finder 2&3, cell [1] (11:0 Finder 2. 23:12 Finder 3)  
   +++ simulated word bits : 0000 0000 0000 0000 0000 0010 0000 0110  
   +++ Real      word bits : 1101 1111 0000 0000 0000 0000 1100 0000  
 ** event number =1053 
 == Bit by bit print out for Crate [0] Linker Board  [4]    Input Formatter [4] 
 Finder 0&1, cell [2] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0000 0000 0001 0000 0000 0000  
   +++ Real      word bits : 1101 1111 0000 0000 0000 0000 0000 0000  
 ** event number =1053 
 == Bit by bit print out for Crate [0] Linker Board  [4]    Input Formatter [4] 
 Finder 2&3, cell [2] (11:0 Finder 2. 23:12 Finder 3)  
   +++ simulated word bits : 0000 0000 0000 0000 0100 1100 0000 0000  
   +++ Real      word bits : 1101 1111 0000 0000 0000 0000 1100 0000  
 ** event number =1053 
 == Bit by bit print out for Crate [0] Linker Board  [4]    Input Formatter [4] 
 Finder 0&1, cell [3] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0111 0000 1110 0000 0000 0000  
   +++ Real      word bits : 1101 1111 0000 0000 0000 0000 0000 0000  
 ** event number =1053 
 == Bit by bit print out for Crate [0] Linker Board  [4]    Input Formatter [4] 
 Finder 2&3, cell [3] (11:0 Finder 2. 23:12 Finder 3)  
   +++ simulated word bits : 0000 0000 1111 0000 0000 0000 0000 0000  
   +++ Real      word bits : 1101 1111 0000 0000 0000 0000 1100 0000  
 ** event number =1053 
 
 
For more details, look at /cdf/scratch/jych/dump/018dc0_1050.dump 
 
 
</pre>
<!-- Author: Jong-Young Chung -->


<!-- Date: Fri Oct 20 09:21:02 2000 -->
<pre> 
Daily XFT Notes and Activities: 
 
        *  Beam setup starts this morning in preparation for collisions 
hopefully this evening.  Once the shot is delivered it is expected to last 
17 or 18 hours like last time. 
 
        *  In preparation for collisions, all subsystems should be 
dedicated to further integration studies today until the store.  The 
DAQ people need to do some high readout rate tests that have not been done 
in a couple days. 
 
        *  Once collisions begin, the first order of business is to 
investigate some CLC timing issues, and then make more global timing 
adjustments.  I spoke with Greg Field about the possible impact this could 
have on the XFT and he assured me that changes would be transparent. 
 
        *  XFT included in evening and overnight and illustrated good 
behavior. 
 
 
Activities: 
 
 
        ***    ALL XFT CRATES should remain in the control    *** 
                of the DAQ people for integration testing. 
 
        *  Continued analysis of the collision data from last weekend. 
 
        *  Collisions hopefully tonight 
 
</pre>
<!-- Author: Chris -->


<!-- Date: Mon Oct 23 06:12:17 2000 -->
<pre>Reprogramming the Finder Flashrams for capture tests.</pre>
<!-- Author: Jay D -->


<!-- Date: Mon Oct 30 17:18:42 2000 -->
<pre>I added new feature into XFTMonitor. Now it can compare pixel information 
of Finder board (XFFD bank) into Input data of linker input formatter. 
 
It will be helpful to check connection between two boards with Real 
collision data. 
I used this new feature and other methods which XFTMonitor already had 
to check new collsion data which Chris stripped off friday 
(fcdfsgi2:/cdf/scratch/neu/ar018fac_XFTTracks.rt) 
 
In this checking, XFTMonitor did three comparison 
 
First it simulated Finder and linker with XFFD hit data of collision file. 
1) comparison between real and simulated data of XFFD pixel. 
2) comparison between real and simulated data of XFLD linker output. 
 
and Input_Comp method of XFTMonitor did 
3) comparison between XFFD pixel data and XFLD pixel input with only REAL 
data (connection checking) 
From this check, I found XFT worked much better than 018c32 run 
(see /cdf/scratch/jych/dump/018c32_428.dump) 
In 018c32,  we had so much mismatched finder pixels. 
 
In this run(018fac), XFT worked much better, I couldn't find significant 
mismatches in pixel data this time, except a few problems. 
 
I don't understand why 018c32 had so much mismatch in pixel data compared 
with  018fac. 
Did we had something on Finder board during last week? Why are there 
so big difference between two run? 
 
But we have still some problems. 
 
Two problems are 
 
1) Finder Board   : Crate 1, Slot 5(starting from 4), Chip 1a, Cell 0 
 
2) Linker Board, Input Formatter  : Crate 0,  Slot 14, Input Chip 3. 
   Finder : Crate 0, slot 18, Chip 4d. 
 
some other boards also have different problems, But  these two are 
found more frequetly . 
 
Here more detailed description. 
 
 
 
1) Finder Board   : Crate 1, Slot 5(starting from 4), Chip 1a, Cell 0 
                    In many case, simulation gives 0  
                     
Case 1  (See underlined(with ****) bits )  
====== 
 
 
(Finder XFFD comparison) 
Simulated Trigger Bank 
Simulated Trigger Bank 
 == Bit by bit print out for Crate [1] Finder 1/3 Board  [1]    Chip 1-[a] Cell 0,1 
 (11:0 Cell 0 Pixel, 12 B0, 13 W0, 14 Err, 27:16 Cell 1 Pixel, 28 B0, 29 W0, 30 Err) 
   +++ simulated word bits : 0000 0000 0000 0000 0000 0000 0000 0000  
   +++ Real      word bits : 0100 0000 0000 0000 0110 0000 1000 0000  
 ** event number =1736                                **** **** **** 
 
 
(Linker Input Formatter comparison) 
Simulated Trigger Bank 
Simulated Trigger Bank 
 == Bit by bit print out for Crate [1] Linker Board  [0]    Input Formatter [4] 
 Finder 0&1, cell [0] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0000 0000 0000 0000 0000 0000  
   +++ Real      word bits : 0000 0000 0000 1000 0000 0000 0000 0000  
 ** event number =1736                 **** **** **** 
 
 == Bit by bit print out for Crate [1] Linker Board  [1]    Input Formatter [0] 
 Finder 0&1, cell [0] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0000 0000 0000 0000 0000 0000  
   +++ Real      word bits : 0000 0000 0000 0000 0000 0000 1000 0000  
 ** event number =1736                                **** **** **** 
 
 
 
Case 2   
====== 
 
 
Simulated Trigger Bank 
Simulated Trigger Bank 
 == Bit by bit print out for Crate [1] Finder 1/3 Board  [1]    Chip 1-[a] Cell 0,1 
 (11:0 Cell 0 Pixel, 12 B0, 13 W0, 14 Err, 27:16 Cell 1 Pixel, 28 B0, 29 W0, 30 Err) 
   +++ simulated word bits : 0000 0000 1100 0000 0000 0000 0000 0000  
   +++ Real      word bits : 0100 0000 1100 0000 0110 0110 0000 0000  
 ** event number =2093                                **** **** **** 
 
 
Simulated Trigger Bank 
Simulated Trigger Bank 
 == Bit by bit print out for Crate [1] Linker Board  [0]    Input Formatter [4] 
 Finder 0&1, cell [0] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0000 0000 0000 0000 0000 0000  
   +++ Real      word bits : 0000 0000 0110 0000 0000 0000 0000 0000  
 ** event number =2093                 **** **** **** 
 
 == Bit by bit print out for Crate [1] Linker Board  [1]    Input Formatter [0] 
 Finder 0&1, cell [0] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0110 0000 0000 0000 0000 0000  
   +++ Real      word bits : 0000 0000 0110 0000 0000 0110 0000 0000  
 ** event number =2093                                **** **** **** 
 
 
 
Case 3 ( In this case, simulated word is not 0 ) 
====== 
 
Simulated Trigger Bank 
Simulated Trigger Bank 
 == Bit by bit print out for Crate [1] Finder 1/3 Board  [1]    Chip 1-[a] Cell 0,1 
 (11:0 Cell 0 Pixel, 12 B0, 13 W0, 14 Err, 27:16 Cell 1 Pixel, 28 B0, 29 W0, 30 Err) 
   +++ simulated word bits : 0000 0001 1111 1000 0000 0110 0000 0000  
   +++ Real      word bits : 0101 0001 1111 1000 0111 0111 1100 0111  
 ** event number =30870 
 
 
Simulated Trigger Bank 
Simulated Trigger Bank 
 == Bit by bit print out for Crate [1] Linker Board  [0]    Input Formatter [4] 
 Finder 0&1, cell [0] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0110 0000 0000 0000 0000 0000  
   +++ Real      word bits : 0000 0000 0111 1100 0111 0000 0000 0000  
 ** event number =30870 
 == Bit by bit print out for Crate [1] Linker Board  [1]    Input Formatter [0] 
 Finder 0&1, cell [0] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0000 0000 0000 0110 0000 0000  
   +++ Real      word bits : 0000 0000 0000 0000 0000 0111 1100 0111  
 ** event number =30870 
 
 
 
 
I observed this problem in  
Event 6790,  6931, 8741, 11740, 27076, 30870, 32516,33249 
33251, 39865, 40864, 50281, 56613, 60113, 60281, 66774, 71640, 78328, 84167, 85557, 88389, 88944 
91120, 92060, 93374, 97612, 110785,  113629,  116500, 116808, 119680 
 
 
 
 
2) Linker Board, Input Formatter  : Crate 0,  Slot 14, Input Chip 3. 
   Finder : Crate 0, slot 18, Chip 4d. 
 
 We have two problems,  Finder pixel mismatch and reverse cable between finder bd and linker bd. 
                        Finder cell 0, 1 goes to input fmt cell 3,4 
 
Simulated Trigger Bank 
Simulated Trigger Bank 
 == Bit by bit print out for Crate [0] Finder 2/4 Board  [5]    Chip 4-[d] Cell 0,1 
 (11:0 Cell 0 Pixel, 12 B0, 13 W0, 14 Err, 27:16 Cell 1 Pixel, 28 B0, 29 W0, 30 Err) 
   +++ simulated word bits : 0000 0000 0011 1111 0000 1101 1111 1101  
                                  #### #### ####      @@@@ @@@@ @@@@ 
   +++ Real      word bits : 0100 0000 0011 1111 0110 1111 1101 0100  
 ** event number =102             %%%% %%%% %%%%      &&&& &&&& &&&& 
 
 
Simulated Trigger Bank 
Simulated Trigger Bank 
 == Bit by bit print out for Crate [0] Linker Board  [5]    Input Formatter [3] 
 Finder 0&1, cell [0] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0000 0000 0000 1101 1111 1101  
                                                      @@@@ @@@@ @@@@ 
   +++ Real      word bits : 0000 0001 0000 0000 0000 0000 0000 0000  
 ** event number =102 
 == Bit by bit print out for Crate [0] Linker Board  [5]    Input Formatter [3] 
 Finder 0&1, cell [1] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0000 0000 0000 0000 0011 1111  
                                                      #### #### #### 
   +++ Real      word bits : 0000 0001 0000 0000 0000 0000 0000 0000  
 ** event number =102 
 == Bit by bit print out for Crate [0] Linker Board  [5]    Input Formatter [3] 
 Finder 0&1, cell [2] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0000 0000 0000 0000 0000 0000  
   +++ Real      word bits : 0000 0001 0000 0000 0000 1111 1101 0100  
 ** event number =102                                 &&&& &&&& &&&& 
 == Bit by bit print out for Crate [0] Linker Board  [5]    Input Formatter [3] 
 Finder 0&1, cell [3] (11:0 Finder 0. 23:12 Finder 1)  
   +++ simulated word bits : 0000 0000 0000 0000 0000 0000 0000 0000  
   +++ Real      word bits : 0000 0001 0000 0000 0000 0000 0011 1111  
 ** event number =102                                 %%%% %%%% %%%% 
 
 
## This is comparison of Real data between XFFD Pixel data and XFLD data (input FMT) . 
 
 ERROR! Event 102, Linker: crate = 0, board = 5, Finder 4d   cell=0 
-- Finder pixels= fd4 
-- Linker pixels= 0 
 ERROR! Event 102, Linker: crate = 0, board = 5, Finder 4d   cell=1 
-- Finder pixels= 3f 
-- Linker pixels= 0 
 ERROR! Event 102, Linker: crate = 0, board = 5, Finder 4d   cell=2 
-- Finder pixels= 0 
-- Linker pixels= fd4 
 ERROR! Event 102, Linker: crate = 0, board = 5, Finder 4d   cell=3 
-- Finder pixels= 0 
-- Linker pixels= 3f 
 
You can see the swapping between cell 0, 1 and cell 2, 3. 
 
Same problems are found in  
Event 11082, 18629, 25102, 35409, 39844, 50781, 53077, 54086, 54378, 54890, 58224, 59193, 65651, 
65910, 78465, 92060, 105136, 110100, 115486, 116315, 116616 
 
 
 
 
 
 
 
</pre>
<!-- Author: Jong-Young Chung -->
<!-- Comment: Mon Oct 30 17;23;21 comment by...Jong-young Chung -->
If you want to see dump output of above result
see /cdf/scratch/jych/dump/018fac.dump