<!-- Title: 08:36:53  Sat Dec 22 2001 -->
<!-- Crewchief: Diag Shifters -->
<!-- Op1: &nbsp; -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Diagnosis Shifts for Silicon System Monitoring</pre>


<!-- Date: Sat Dec 22 08:37:24 2001 -->
<pre>Run 2112f, file ir02112f.001cali 
 
e4a3 81.813 0 0 0 0 2 2 4 0 8 8 35        
 
	Does not read out Last Chip Last Channel 
 
e463 6.67 0 0 0 0 0 0 0 0 0 0 59        
 
	Chips 87 and a3 give wrong pipecell ID's (they are the same) 
	Diff. between correct and reported pipecells is not constant	 
 
e454 100.0 10 48 0 0 1 0 0 0 0 0 0 0 0 0 0    
 
	Early truncation of readout 
 
e410 
 
	Two consecutive fib headers: e4103bfc e4113bfc                                                        
 
e354 13.135 0 0 0 0 0 0 0 0 0 0 0 0 0 0 59    
 
	Bizarre but perfectly repeated (event-to-event) strip number ordering	 
 
e313 3.33 0 0 0 0 0 0 0 0 0 0 59        
 
	Channel 3f is occasionally repeated (in different chips) 
 
e294 100.0 0 0 0 0 56 3 0 0 0 0 0 0 0 0 0    
 
	Truncation immediately after fib header 
 
e274 100.0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 59    
 
	Bit 1 stuck high 100% 
 
e231 1.16 0 0 0 0 0 0 59            
 
	Bit 1 high 1 instance in 1 event 
 
e212 96.966 0 0 0 0 2 0 0 0 0 0 57        
 
	Pipecell ID's wrong on Z side; no particular bit, and not even 
		same chips from one event to next 
 
e202 100.0 0 0 0 0 0 2 3 3 3 3 45        
 
	Wide variety of weird readout. 
 
e201 1.16 0 0 0 0 0 0 59            
 
	Last chip last channel missing 
 
e1a2 27.271 0 0 0 0 0 1 0 0 0 0 58        
 
	Pipecell ID's for a3 through a0 occasionally wrong 
	LCLC missing occasionally 
 
e151 1.16 0 0 0 0 0 0 59            
 
	Expected strip 72 saw 52 
 
e043 100.0 0 0 0 0 0 0 0 0 0 0 59       
 
	Bit 7 high, only on chip a3</pre>
<!-- Author: ADF -->


<!-- Date: Sat Dec 22 21:38:17 2001 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre> 
22-12-2001: 
=========== 
 
Summary of things you will find below.... 
 
1) We have Layers with "00 f3", where Channel and data are 0. 
2) We have Layers with "00" Channel ---&gt; OBDV? 
3) We have "7f" problem. 7f is dropping in some layers 
   randomly as a Channel Id totaly out of order. 
   Some time, rarely, one sees also a "7d". 
4) Bit errors, where some times 2 stuck bits are working together 
   to cause problems. 
5) d0c2c4c4,c2c2,etc. 
6) I don't have any clue what is going on. 
 
The details you find below. 
 
--------------------------------------------------------------- 
List of included wedges: 
 
SB0W0 SB0W1 SB0W10 SB0W11 SB0W2 SB0W3 SB1W0 SB1W1 SB1W2 SB1W3 SB1W10 SB1W11 
SB2W0 SB2W1 SB2W2 SB2W3 SB2W10 SB2W11 
IB0W2 IB0W3 SB0W4 SB0W5 SB0W6 SB0W7 
SB0W8 SB0W9 SB1W4 SB1W5 SB1W6 SB1W8 SB1W9 SB2W5 SB2W6 SB2W7 SB2W8 SB2W9 
IB0W0 IB0W1 IB0W4 IB0W5 SB1W7 SB3W0 SB3W1 SB3W2 SB3W3 SB3W10 SB3W11 
SB4W2 SB4W3 SB4W10 SB4W11 SB5W0 SB5W1 SB5W2 SB5W3 SB5W10 SB5W11 
IB5W2 IB5W3 SB3W5 SB3W6 SB3W7 SB3W8 SB3W9 SB4W4 SB4W5 SB4W6 SB4W7 SB4W8 
SB4W9 SB5W4 SB5W5 SB5W6 SB5W7 SB5W8 SB5W9 IB5W0 IB5W1 IB5W4 IB5W5 
 
********************************************** 
start with latest run=135542 and will go backwards: 
The latest RUN avaible in David's is 135471 
 
 
IB0W1L1 :    11% Strip Out of Order 
             (first seen in RUN=134513 on a level of 0.4%) 
             Channel ID's are wrong, because bit 2 is high. 
             Sometimes Chip-ID are also wrong because of 
             bit 2 and/or bit 4 high. Bit 4 high is only seen, if 
             Chip-ID's are messed up. 
 
IB0W1L4:     1%  Strip Out of Order 
             (first seen in RUN 134813) 
             I couldn't correlated this error to any high/low bits in the 
             data stream. 
             It is always Chip 8c (phi side chip # 12), which has problems. 
             And common to them is, that you see 
                   8c..7x..07..08.. 
             While x=f,x=e,x=6 
             or 
                   8c..6x..07..08.. 
             or    8c..5x..07..08.. 
 
IB0W3L4:     95%  no data for 
             I thought this was taken out of SVXMon ?? 
             Last Run with problems for this layer in Dave's error monitor 
             is  134525 (50%). 
             One sees that Chip a1 is reading only "f3 00" after a few 
             channels. 
             Fine after that. but let's what tomorrow brings. 
 
IB0W4L2:     4%-17%   Duplicate Channel 
             0.11%    Strip out of Order 
             (First seen in RUN=134720 at a level of 17%) 
             Last Run with problems for this layer  in Dave's error monitor 
             is 134933. 
             Datastream shows duplicated Channels and 
             Chip ID's are wrong for Chip's 8b (phi side chip # 11) 
             onwards, because of bit 4 high! 
 
IB0W4L3:     0.11% C0-2,C4-C8 Pipeline cell id is invalid 
             (First seen in RUN=134812) 
 
             Last Run with problems for this layer in Dave's error monitor 
             is RUN=135471, 100% bad events. 
 
             CapID of Chip's are wrong because of bit 7 high. 
             Bit 7 high is set randomly. It comes and goes, or stays for a 
             while. 
 
             Chip ID of are messed up from Chip 8b onwards, because of 
             bit 4 high. 
 
IB5W0L2:     5%     Strip Out of Order 
             (First seen in Run=134612) 
 
             Last Run with problems for this layer in Dave's error monitor 
             is RUN=135453 (bad events 4.4%). 
 
             Chip ID's from 8b onwards wrong, because of bit 4 high. 
             Channels are out of order, but I couldn't pin it down to 
             a certain bit. What I see is, that most of the hickups are 
             caused by a "7f" Chip ID, which appears out of order. 
 
IB5W2L1:     0.233% C1-C14, Stuck Bit, Cell id bit 7 
             (first seen in RUN=135162) 
             C0 ~0.22% Strips Bad ADC Value 
             (First seen in RUN=134720) 
             C15 (first seeen in RUN=135542) Invalid Cell Id, Pipeline cell id 
             is invalid. 
 
             Last Run with problems for this layer in Dave's eror monintor 
             is RUN=135453. 
 
             Chip ID's from 8b onwards wrong, because of bit 4 high. 
             Cap ID's wrong because of bit 7 high. This error is spread 
             over various chip id's. 
 
             In some runs (e.g. 135355 23%) channels are out of order, but I 
             couldn't pin it down to 
             a certain bit. What I see is, that most of the hickups are 
             caused by a "7f" Chip ID, which appears out of order. 
 
SB0W10: L0-L4:    0.1% Duplicate Channel 
                    (First seen in RUN=135313) 
        L1-L4:    0.1% Out of Order Chip ID 
                    (First seen in RUN=135355) 
 
                L0: After a randomly choosen channel the datastream contains 
                    only "00 f3" until 
                    at some point chip 85 (which is not existing for this 
                    layer) is reached. 
 
                    This list of "00 f3" is interpreted by SVXMon as 
                    Duplicated Channels. I did not see a real duplicated 
                    Channel Error for this Layer. 
 
                L1: Last run with problems for this layer in Dave's error 
                    summary is run=135362 (2.2%) 
                    I see here again that "7f" is set as a channel id 
                    just randomly. 
                    I saw one example of a duplicated channel. 
 
                L2: I see here again that "7f" is set as a channel id 
                    just randomly. 
                    After a randomly choosen channel the datastream contains 
                    only "00 f3" until 
                    at some point chip 89 is reached. 
 
                L3: "7f" problem 
                    bit 1 high causes channel id out of order in data 
                    stream 
                    bit 4 low causes channel id out of order ind data 
                    stream 
                    bit 4 high causes channel id out of order in data 
                    stream 
 
                L4: Last run with problems for this layer in Dave's error 
                    symmary is run=124829. (Must wait for the 
                    runs of today until the Dave's programm have 
                    processed them. ) 
 
SB0W11L0:       0.1% Out of order Chip ID, Strip out of Order 
                (first seen in Run=128066) 
 
                Last run with problems for this layer in Dave's error 
                symmary is run=124830. (Must wait for the 
                runs of today until the Dave's programm have 
                processed them. ) 
 
 
SB0W11L3:       &lt;0.22% Duplicate Channel,Strip Out of Order 
                 ~1% EOR not Found, Invalid EOR,Invalid Word, Wrong Chip Count 
                (First seen in RUN=128066) 
 
                Last run with problems for this layer in Dave's 
                error symmary is run=127351. (Must wait for the 
                runs of today until the Dave's programm have 
                processed them. ) 
 
 
SB0W4L0:        &lt;0/5% EOR not found, Invalid EOR, Wrong Chip Count 
                ~1% Invalid Word 
                Last run with problems in Dave's error summary is run 
                135453 (1-20%). 
 
                Bit 7 high and/or 
                Bit5||Bit4||Bit3 high are causing Channel 
                Id out of order in the data stream. 
                Somehow all first 4 Bits are unstable for this layer. 
 
SB0W4L3:        8% Bad Chip ID 
                80% Chip sid Error 
                100% EOR Not Found 
                96%  Wrong Chip Count 
                88%  Out of Order Chip Id 
                12%  Invalid EOR 
                0.5% Invalid Word 
 
                Last run with problems in Dave's error summary is run 
                135453 (100%). 
                Problems are caused by Bit 7 high, this error is not 
                limited to a certain chip. 
 
SB0W7L1: Strip Out of Order 1 out of 855 
         no error's in daves error monitor 
 
SB0W9L2: Strip Out Of Order 1 out of 855 
         last run in Dave's error monitor=135453 
 
         Couldn't pin it down to a single bit. 
 
 
SB0W9L3: Duplicate Channel 2 out of 855 
         last run in Dave's error monitor = 135362 (1-8%) 
         "7f" problem (see above) 
 
SB0W9L4: Strip Out of order 1 out of 855 
         last run in Dave's error monitor = 135453 
         (0.1%-30%) 
         bit 5 low causes wrong channel id's. 
         bit 7 high + bit 3 low causes wrong chip id's. 
 
SB1W10L2: 14% Strip Out of order 
 
          last run in D.e.m= 135453 (2-30% bad events) 
          wrong Chip Id because of bit 7 low for chip 86. 
          wrong Cap ID because of bit 3 low. 
          Not all of the Cap ID problems are caused by bit 3 low. 
 
 
SB1W4L0:  84% Strip Out of Order 
          C0 Stuck Bit, Cell Id bit 3 gets stuck at 1 prob: 0.23% 
          C1-C3 No Data in 95% 
 
          last run in D.e.m=124830. 
SB1W4L1:  C0-C5 95% No DATA 
          not reported in D.E.M. 
 
SB1W4L4:  C0-C13 95% NO DATa 
          not reported in D.E.M. 
 
SB1W5L2:  2% Strip Out of Order 
          not reported in D.E.M. 
 
SB2W0L0:  0.11% Problems wiht EOR, Wrong Chip Count 
 
          Bit 7 and/or Bit 5 high.==&gt; wrong Channel ID. 
          sometimes, After a randomly choosen channel the datastream contains 
          only "00 f3". 
 
 
SB2W0L2:  0.11% Problems wiht EOR 
          2%  Wrong Chip Count 
          C4-C7 Pipeline out of Sync 1 out of 855 
 
          last run reported in D.E.M=135453 
 
          "d0c2c2c4" and other strange things, like Cap ID changes from 
          15 to 23 and frequently we see channel id with "00" for Chip 85 (may 
          be an OBDV failure (Dave's comment)). 
          Sometime bit 3 is high and causes Cap ID problems. 
 
 
SB2W1L3:  2% Strip out of order 
          Bit 5 low, causes channel id problems. 
 
SB2W1L4:  2% EOR Problems, Invalid Word, Wrong Chip Count 
 
          C1 Pipeline Out of Sync 4 out of 843 
             Stuck Bit, Cell id bit 0 stuck at 1 28.44% prob. 
 
          Bit seven high. 
 
SB2W11L0: 0.11% Strip out of Order 
          last run reported in D.e.M. = 135362 (1-6) 
 
          chip 83 "00 f3" !!! 
 
SB2W7L4: 5% Duplicate Channel 
         100% Out of Order Chip ID, Strip out of order 
         C0 Invalid Cell Id, Pipeline cell id out of sync 2/15 
         C1 No data 54/855 
         C4-C13 NO DATA 95% 
         C2   6% NO DATA 
         C3   50% NO DATA 
 
 
         DSerror mon 100%, since run 135453. 
         Bit 1 stuck high 
 
 
 
SB2W9L4: C0-C13 NO DATA 95% 
 
         bit 6 high 100% 
 
SB3W1L3: 90% Duplicate Channel 
         50% Out of Order Chip Id 
         0.11% level EOR Problems 
 
         C1,C3,C5,C7,C9 Stuck bit, Cell id bit 0 gets stuck at 1 
                                   prob: 15-27% 
 
        last processed run in daves erron mon is 135471. 
        Duplicate Channel rate here is of the order of 3%. 
        I don't see EOR problems. 
        Cap Id and Channel ID errors because of bit 0 high. 
 
SB3W2L4:  C0 INvalid Cell ID 70%, Pipelin cell id is invalid 
        no report in D.E.M. for runs taken in the last 3 days. 
 
SB4W6L3: C0-C9  Stips Bad ADC Value 1/855 
         Bit 3 high. 
 
SB4W7L1: 10% Strip out of order 
         0.22% Duplicalte Channel,Out of order Chip ID 
         no report in D.E.M for runs taken in the last 3 days. 
 
SB4W10L3: 
         c2c2, d0c2c4c4, and Cap ID problems, which I could not 
         pin down to a single bit: 10-&gt;03, 
 
SB5W10L4: 50% Duplicate Channel, since run=135451 
 
SB5W3L1:  C3 STRIPS BAd ADC Value, 28/855 
 
          no report on D.E.M. 
 
 
 
 
 
 
 
 
</pre></td></tr></td></table>
<!-- Author: cigdem -->
<!-- Comment: Sat Dec 22 21;50;26 comment by...cigdem  -->
<pre>D.E.M. means David's error summary</pre>

<!-- Comment: Sun Dec 23 11;57;25 comment by...cigdem -->
<pre>Erratum:

SB0W11L0:       0.1% Strip out of Order,
                     Duplicated Channel
                first seen in RUN = 135539</pre>


<!-- Date: Sun Dec 23 18:45:47 2001 -->
<pre> 
23-12-2001: 
=========== 
 
We could define 6 error classes after scanning the problems of the silicon 
detector. 
 
     1) "7f" problem 
              In this case randomly a channel ID is set most of the time to 
              7f or some times to other high numbers like "6e","5e" or 6f. 
     2) "00 f3" problem 
              In this case we see all channels and data set to 00. 
     3) high/low bit errors 
              Here we have "flacky" stuck bit errors, which are 
              not caused by a single or a couple of high/low bits, 
              but by random high/low bits. 
              And we have high/low bit errors, which are caused only 
              by certain bits. 
     4) OBDV/c2c2 problems 
             In this case we see channels set to "00" or we have 
             d0c2c2c4,c2c2 errors 
     5) Duplicate channel 
     6) Cap ID of the previous event is copied. 
 
 
 
1) "7f" layers 
************** 
IB0W1L4,IB5W0L2,IB5W2L1,SB0W10L1-L3,SB0W9L3,SB1W2L4,SB2W8L1,SB3W7L4,SB4W3L4,SB4W5L2 
SB5W5L4,SB5W4L3,SB5W2L2,SB5W0L2 
 
2) "00 f3" layers 
***************** 
SB0W10L0/L2,SB1W4L0,SB2W0L0,SB2W11L0,SB3W2L0,SB1W10L2 
 
3) high/low bit layers 
********************** 
 
-constant high/low bit layers: 
 IB0W1L1,IB0W4L2,IB0W4L3,IB5W0L2,IB5W2L1,SB0W10L2/L3/L4,SB0W11L3,SB0W4L3 
 ,SB1W5L2,SB2W0L0,SB2W1L3,SB2W1L4,SB2W7L4,SB2W9L4,SB3W1L3,SB4W6L3,SB4W7L1 
 ,SB5W11L1,SB5W4L3 
 
-randomly high/low bit layers: 
 SB0W4L0,SB0W9L2,SB0W9L4,SB2W6L4,SB4W10L2 
 
4) OBDV/c2c2 problems layers 
**************************** 
 
SB1W2L4,SB2W0L2,SB4W3L3,SB4W10L3 
 
5) Duplicate Channel layers 
*************************** 
(I only put here layers, where I saw in David's error monitor duplicate channel.) 
IB0W4L2,SB0W10L1/L3/L4,SB0W11L2,SB0W11L3,SB3W1L3,SB2W0L2,SB5W10L4,SB5W5L4 
 
6) Cap ID of the previous event is copied 
****************************************** 
 
SB2W7L4,SB4W10L3 
 
You will find below the summary of todays diagnostic shift. 
You can use the entries below, to learn more about the details in a certain 
layer you saw in the error classes. Some layers do belong to more than one error 
class. 
DEM = David's Error Monitor 
 
--------------------------------------------------------------------------------- 
IB0W1L1 :    11% Strip Out of Order 
             (first seen in RUN=134513 on a level of 0.4%) 
             Channel ID's are wrong, because bit 2 is high. 
             Sometimes Chip-ID are also wrong because of 
             bit 2 and/or bit 4 high. Bit 4 high is only seen, if 
             Chip-ID's are messed up. 
             Chip ID 8b - a4 are 9b-b4 (Bit 4 high) 
#23-12-2001# Still making problems, Last check RUN 135591 
 
IB0W1L4:     1%  Strip Out of Order 
             (first seen in RUN 134813) 
             I couldn't correlated this error to any high/low bits in the 
             data stream. 
             It is always Chip 8c (phi side chip # 12), which has problems. 
             And common to them is, that you see 
                   8c..7x..07..08.. 
             While x=f,x=e,x=6 
             or 
                   8c..6x..07..08.. 
             or    8c..5x..07..08.. 
 
#23-12-2001# Still making problems, Last check RUN 135591 
             This is actually a so called "7f" problem layer. 
 
IB0W3L4:     95%  no data for 
             I thought this was taken out of SVXMon ?? 
             Last Run with problems for this layer in Dave's error monitor 
             is  134525 (50%). 
             One sees that Chip a1 is reading only "f3 00" after a few 
             channels. 
             Fine after that. but let's what tomorrow brings. 
 
#23-12-2001# Still making problems, Last check RUN 135591 
 
 
IB0W4L2:     4%-17%   Duplicate Channel 
             0.11%    Strip out of Order 
             (First seen in RUN=134720 at a level of 17%) 
             Last Run with problems for this layer  in Dave's error monitor 
             is 134933. 
             Datastream shows duplicated Channels and 
             Chip ID's are wrong for Chip's 8b (phi side chip # 11) 
             onwards, because of bit 4 high! 
 
23-12-2001#  Still making problems, last check RUN 135591 
             7% Duplicate Channel Errors 
 
IB0W4L3:     0.11% C0-2,C4-C8 Pipeline cell id is invalid 
             (First seen in RUN=134812) 
 
             Last Run with problems for this layer in Dave's error monitor 
             is RUN=135471, 100% bad events. 
 
             CapID of Chip's are wrong because of bit 7 high. 
             Bit 7 high is set randomly. It comes and goes, or stays for a 
             while. 
 
             Chip ID of are messed up from Chip 8b onwards until b4, because of 
             bit 4 high.( Chip ID 8b - a4 are 9b-b4 (Bit 4 high)) 
 
#23-12-2001# NO problems since RUn 135543 
 
IB5W0L2:     5%     Strip Out of Order 
             (First seen in Run=134612) 
 
             Last Run with problems for this layer in Dave's error monitor 
             is RUN=135453 (bad events 4.4%). 
 
             Chip ID's from 8b onwards wrong, because of bit 4 high. 
             Channels are out of order, but I couldn't pin it down to 
             a certain bit. What I see is, that most of the hickups are 
             caused by a "7f" Chip ID, which appears out of order. 
 
#23-12-2001# Still making problems, Last check RUN 135591 
             0.1%-5% Strip Out of Order 
    *NEW*    Since RUN 135539, it has also sometimes Duplicated Channel 
             Errors. 
 
IB5W2L1:     0.233% C1-C14, Stuck Bit, Cell id bit 7 
             (first seen in RUN=135162) 
             C0 ~0.22% Strips Bad ADC Value 
             (First seen in RUN=134720) 
             C15 (first seeen in RUN=135542) Invalid Cell Id, Pipeline cell id 
             is invalid. 
 
             Last Run with problems for this layer in Dave's eror monintor 
             is RUN=135453. 
 
             Chip ID's from 8b onwards wrong, because of bit 4 high. 
             Cap ID's wrong because of bit 7 high 8%. This error is spread 
             over various chip id's. 
 
             In some runs (e.g. 135355 23%) channels are out of order, but I 
             couldn't pin it down to 
             a certain bit. What I see is, that most of the hickups are 
             caused by a "7f" Chip ID, which appears out of order. 
 
#23-12-2001# Still making problems, Last check RUN 135591 
             Stuck Bit, Cell id bit 7 gets stuck at 1 
             with a prob of 0.4%-1.4% 
             Now and then Strips -- BAD ADC Value 
 
 
SB0W10: L0-L4:    0.1% Duplicate Channel 
                    (First seen in RUN=135313) 
        L1-L4:    0.1% Out of Order Chip ID 
                    (First seen in RUN=135355) 
#23-12-2001# Still making problems, Last check RUN 135591 
             Duplicated Channel in L0-L4, 0.1-1% 
             Out of order Chip ID  L1-L4  0.1-1% 
 
 
                L0: After a randomly choosen channel the datastream contains 
                    only "00 f3" until 
                    at some point chip 85 (which is not existing for this 
                    layer) is reached. 
 
                    This list of "00 f3" is interpreted by SVXMon as 
                    Duplicated Channels. I did not see a real duplicated 
                    Channel Error for this Layer. 
#23-12-2001# Still making problems last check RUN 135613 
             SVXMON:Duplicated channel 
 
 
                L1: Last run with problems for this layer in Dave's error 
                    summary is run=135362 (2.2%) 
                    I see here again that "7f" is set as a channel id 
                    just randomly. 
                    I saw one example of a duplicated channel. 
#23-12-2001# Still making problems last check RUN 135613 
             SVXMON:Duplicated channel 
 
                L2: I see here again that "7f" is set as a channel id 
                    just randomly. 
                    After a randomly choosen channel the datastream contains 
                    only "00 f3" until 
                    at some point chip 89 is reached. 
#23-12-2001#   Bit 0 low 
 
                L3: "7f" problem 
                    bit 1 high causes channel id out of order in data 
                    stream 
                    bit 4 low causes channel id out of order ind data 
                    stream 
                    bit 4 high causes channel id out of order in data 
                    stream 
#23-12-2001#        Duplicated Channel 
 
                L4: Last run with problems for this layer in Dave's error 
                    symmary is run=124829. (Must wait for the 
                    runs of today until the Dave's programm have 
                    processed them. ) 
#23-12-2001#       Duplicated Channel and Bit 0 low. 
 
 
SB0W11L0:       0.1% Strip out of Order,Duplicate Channel 
                (first seen in Run=135539) 
 
                Last run with problems for this layer in Dave's error 
                symmary is run=124830. (Must wait for the 
                runs of today until the Dave's programm have 
                processed them. ) 
 
#23-12-2001# Still making problems last checked RUN 135613 
             No entry in DEM avaible. 
 
SB0W11L2 *NEW*: Out of Order Chip ID, in RUN  135591 on 0.1% level 
                This channel has in RUN 135496 and 135498 
                BAD ADC Value error.  23-12-2001 
 
                DEM: Duplicated channels 
 
SB0W11L3:       &lt;0.22% Duplicate Channel,Strip Out of Order 
                 ~1% EOR not Found, Invalid EOR,Invalid Word, Wrong Chip Count 
                (First seen in RUN=128066) 
#23-12-2001# Still making same problems, Last check RUN 135591 
             DEM: bit 7 and/or bit 3 high causing Channel ID problems in Chip 
                 89. 
                 Further Chip ID errors due to bit 0 high. 
                 Cap ID problems 
                 Duplicated Channels, which are spread over all Chips. 
 
SB0W4L0:        &lt;0/5% EOR not found, Invalid EOR, Wrong Chip Count 
                ~1% Invalid Word 
                Last run with problems in Dave's error summary is run 
                135453 (1-20%). 
 
                Bit 7 high and/or 
                Bit5||Bit4||Bit3 high are causing Channel 
                Id out of order in the data stream. 
                Somehow all first 4 Bits are unstable for this layer. 
#23-12-2001# Still making same problems, Last check RUN 135612 
 
 
SB0W4L3:        8% Bad Chip ID 
                80% Chip sid Error 
                100% EOR Not Found 
                96%  Wrong Chip Count 
                88%  Out of Order Chip Id 
                12%  Invalid EOR 
                0.5% Invalid Word 
 
                Last run with problems in Dave's error summary is run 
                135453 (100%). 
                Problems are caused by Bit 7 high, starts always at a3. 
 
#23-12-2001# Still making same problems, Last check RUN 135591 
             + BAD ADC values 
 
SB0W7L1: Strip Out of Order 1 out of 855 
         no error's in daves error monitor 
#23-12-2001# No problems since RUN 135543 
             No errors in Dave's error monitor. 
 
SB0W8L0 *NEW*: Strip Out of Order in RUN=135543,135591 0.1-0.5% 
               23-12-2001 
               Have to wait until Dave's Error monitor has processed this 
               runs. 
 
SB0W9L2: Strip Out Of Order 1 out of 855 
         last run in Dave's error monitor=135453 
 
         Couldn't pin it down to a single bit. Several low or high bits are 
         giving wrong chip id's. 
#23-12-2001# No Problems since RUN 135545 
 
SB0W9L3: Duplicate Channel 2 out of 855 
         last run in Dave's error monitor = 135362 (1-8%) 
         "7f" problem (see above) 
#23-12-2001# No Problems since RUN 135545 
 
SB0W9L4: Strip Out of order 1 out of 855 
         last run in Dave's error monitor = 135453 
         (0.1%-30%) 
         bit 5 low causes wrong channel id's. 
         bit 7 high + bit 3 low causes wrong chip id's. 
#23-12-2001# No Problems since RUN 135545 
 
 
 
SB1W10L2: 14% Strip Out of order 
 
          last run in D.e.m= 135453 (2-30% bad events) 
          wrong Chip Id because of bit 7 low for chip 86. 
          wrong Cap ID because of bit 3 low. 
          Not all of the Cap ID problems are caused by bit 3 low. 
          Cap ID problems due to randomly stuck high bits. 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
 
SB1W2L4 *NEW*: Missed this Layer yesterday. 
               Has Problems since 135277, 
               Bad ADC Value  5-18% 
               Wrong Chip Count,Pipeline Out of Sync 
               Strip Out of Order & Wrong Chip Count 0.1-0.5% 
               23-12-2001 
 
               DEM: d0c2c2c4,c2c2 
                    "7f" problems 
                     bit 6 low (rarely) 
 
SB1W4L0:  84% Strip Out of Order 
          C0 Stuck Bit, Cell Id bit 3 gets stuck at 1 prob: 0.23% 
          C1-C3 No Data in 95% 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
          C0-C3 NO DATA,Stuck Cell Id | 1 | Pipeline cell id is stuck at 13 
 
          DEM: "00 f3" problem. 100% 
 
SB1W4L1:  C0-C5 95% No DATA 
          not reported in D.E.M. 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
             in addition to that we now have also 
             C0: Stuck Bit | 1 | Cell id bit 3 gets stuck at 1 
             with probability 0.925926 % in RUN 135587 
             NO error report in DEM. 
 
SB1W4L4:  C0-C13 95% NO DATa 
          not reported in D.E.M. 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
             no report in DEM. 
 
SB1W5L2:  2% Strip Out of Order 
          not reported in D.E.M. 
#23-12-2001# Still making same problems on the level of 0.5-2%, 
             Last check RUN 135591 
             DEM: bit 5 high, random Chips 5-&gt;7 2.2% 
 
SB2W0L0:  0.11% Problems wiht EOR, Wrong Chip Count 
 
          Bit 7 and/or Bit5 and/or Bit4 on Chip 83 high.==&gt; wrong Channel ID. 
          sometimes, After a randomly choosen channel the datastream contains 
          only "00 f3". 
#23-12-2001# Still making same problems on the level of 0.5-1.0%, 
             Last check RUN 135591 
             no report in DEM. 
 
SB1W5L2:  2% Strip Out of Order 
          not reported in D.E.M. 
#23-12-2001# Still making same problems on the level of 0.5-2%, 
             Last check RUN 135591 
             DEM: bit 5 high, random Chips 5-&gt;7 2.2% 
 
SB2W0L0:  0.11% Problems wiht EOR, Wrong Chip Count 
 
          Bit 7 and/or Bit5 and/or Bit4 on Chip 83 high.==&gt; wrong Channel ID. 
          sometimes, After a randomly choosen channel the datastream contains 
          only "00 f3". 
#23-12-2001# Still making same problems on the level of 0.5-1.0%, 
             Last check RUN 135591 
SB2W0L2:  0.11% Problems wiht EOR 
          2%  Wrong Chip Count 
          C4-C7 Pipeline out of Sync 1 out of 855 
 
          last run reported in D.E.M=135453 
 
          "d0c2c2c4" and other strange things, like Cap ID changes from 
          15 to 23 and frequently we see channel id with "00" for Chip 85 (may 
          be an OBDV failure (Dave's comment)). 
          Sometime bit 3 is high and causes Cap ID problems. 
 
#23-12-2001# Still making same problems on the level of 0.5-1.0%, 
             Last check RUN 135591 
             I see sometimes also Duplicated Channel. 
             Drops read out mostly on a0 and sometimes at 85. 
 
SB2W1L3:  2% Strip out of order 
          Bit 5 low in a3, causes channel id problems. 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
 
 
SB2W1L4:  2% EOR Problems, Invalid Word, Wrong Chip Count 
 
          C1 Pipeline Out of Sync 4 out of 843 
             Stuck Bit, Cell id bit 0 stuck at 1 28.44% prob. 
 
          Bit 7 high on chip 8d. 
 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
  *NEW*    + C9-C12 Stuck bit, Cell id bit 2 gets stuck at 0 with prob. 
                79% in RUN 135580 
 
SB2W6L4 *NEW*: missed this layer yerterday 
               Problems since 128066 on a 0.5% level 
               with EOR and invalid Word. 
               23-12-2001 
 
               a lot of bit errors, randomly getting high. 
 
SB2W11L0: 0.11% Strip out of Order 
          last run reported in D.e.M. = 135362 (1-6) 
 
          chip 83 "00 f3" !!! 
 
#23-12-2001# No problems since RUN 135543 
 
SB2W8L1 *NEW*: missed this layer yesterday 
               Problems started in RUN 135443 
               Strip out of error on a 0.1% level. 
               Chip 83, channel id 45 changes to 7f. 
 
SB2W7L4: 5% Duplicate Channel 
         100% Out of Order Chip ID, Strip out of order 
         C0 Invalid Cell Id, Pipeline cell id out of sync 2/15 
         C1 No data 54/855 
         C4-C13 NO DATA 95% 
         C2   6% NO DATA 
         C3   50% NO DATA 
 
         DSerror mon 100%, since run 135453. 
         Bit 1 stuck high 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
             Copies sometimes CAP ID of previous run. 
 
SB2W9L4: C0-C13 NO DATA 95% 
         bit 6 high 100% 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
 
 
SB3W1L3: 90% Duplicate Channel 
         50% Out of Order Chip Id 
         0.11% level EOR Problems 
         C1,C3,C5,C7,C9 Stuck bit, Cell id bit 0 gets stuck at 1 
                                   prob: 15-27% 
 
        last processed run in daves erron mon is 135471. 
        Duplicate Channel rate here is of the order of 3%. 
        I don't see EOR problems. 
        Cap Id and Channel ID errors because of bit 0 high. 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
 
SB3W2L0: Strip Out of Order in RUN 135501 
         "00 f3" problem and no data read out at all. 
         this layer has this 00 f3 problem now and than. 
 
SB3W2L4:  C0 INvalid Cell ID 70%, Pipelin cell id is invalid 
        no report in D.E.M. for runs taken in the last 3 days. 
 
#23-12-2001# No problems seen since RUN 135543. 
 
 
 
SB3W7L4 *NEW*: missed this one yesterday. 
               problems since RUN 128066 
               Bunch X Out of Sync 50% 
               Strip Out of Order  0.5% 
               Bad ADC Value 10% 
               "7f" problem on chip a2 1% 
               23-12-2001 
 
SB4W3L4 *NEW*: missed this one yesterday 
               problems since RUN 128066 with 
               Strip out of order on a 5-10% level 
               "7f"problem in chip 89 2% 
               23-12-2001 
 
SB4W3L3 *NEW*  SVXMON, problems in 135587 Strip out of Order 0.5% 
               In Dave's Error Monitor one sees 
               problems since 123496 
               d0c2c2c4,c2c2 0.3-18% 
               23-12-2001 
SB4W5L2 *NEW*  missed this one yesterday 
               Problems since RUN 128066 
               Bunch X Out of Sync 50% 
               Strip Out of Order 0.5% 
               "7f" problem in chip 87 
               23-12-2001 
 
SB4W6L3: C0-C9  Stips Bad ADC Value 1/855 
         Bit 3 high.  2% 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
 
 
SB4W7L1: 10% Strip out of order 
         0.22% Duplicalte Channel,Out of order Chip ID 
         no report in D.E.M for runs taken in the last 3 days. 
 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
             bit 2 high. 
 
SB4W10L2 *NEW*:   since RUn 135496, Bad ADC Value, Problems with EOr and 
                  wrong Chip Cpount 0.1-0.2% 
 
                  chip 89 has randomly set high bits, which are causing wrong 
                  channel id's. 
 
SB4W10L3 *NEW*:   since RUN 135495, Wrong Chip Count,Bad ADC Value, 
                  Invalid Cell Id, Pipeline Out of Sync 1% 
 
                 d0c2c2c4,c2c2,c2c4 
                 Cap ID's wrong, but it is not always because of a high/low 
                 bit ?? 24-&gt;2b 
#23-12-2001# copies sometimes cap id from previous event! 
 
SB5W10L4: 50% Duplicate Channel, since run=135451 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
             Chip a1 has Duplicated channels 
 
SB5W3L1:  C3 STRIPS BAd ADC Value, 28/855 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
             no report on D.E.M. 
 
SB5W11L1 *NEW* : Channel ID 34 is randomly switch to 3c (bit 3 high). 0.5% 
 
SB5W5L4 *NEW* : Problems since 135496 in SVXMON 
                BAD ADC, Duplicate Channel 
 
                Duplicate Channels, "7f" Problems 
 
SB5W4L3 *NEW*: Bit 4 high on a0 1% 
 
SB5W2L2 *NEW*: "7f" problem 
 
SB5W0L2 *NEW*: "7f" problem 
 
 
 
</pre>
<!-- Author: Lester & Cigdem  -->


<!-- Date: Mon Dec 24 23:35:36 2001 -->
<pre> 
 
Summary of the diagnostic shift.   
================================  
 
Because I couldn't reach David's Home Page from 8:15pm onwards,   
I couldn't check for all layers the datastream output to analyse   
the bit structure.   
 
*NEW*: Today I found several examples, where David's Error               Monitor detected bad 
events, but SVXMON got no error              messages.   
 
       How can this be? Is SVXMON missing some errors?   
 
       And there are examples,   
       where DEM's got no error messages, while SVXMON had               errors. Are this problems 
with the bank headers?  
 
 
SVXMON ERRors, but no DEM entries:  
IB0W0L2 RUN 135627, Strip Out of Order  
IB0W4L1 RUN 135560, Srip Out of Order  
IB0W5L0 RUN 135614, Strip Out of Order   
etc. (for more details see Barrel 4 Log)  
 
DEM entries, but no SVXMON ERRORS  
IB0W4L1 RUN 135545,134848 c2c2  
etc.  (for more details see Barrel 4 LOg)  
 
 
I observed that the so called "7f" problem is caused by   
several high bits (always bit 0-6,never 7),   
which are set at the same time.   
Usually one sees in the SVXMON "Strip Out of Order" errors.   
(NOt always, but most of the time).   
 
We have actually 76+-2 layers with problems. A list of  
Layers above a level of 1% you can find tin the Silicon  
Elog.  
 
-------------------------------------------------------- 
 
Here is the complete list of problematic layers..... 
very long.  
 
--------------------------------------------------------- 
NEW Problems or Problems I missed yesterday: 
-------------------------------------------- 
 
IB0W0L2:     SVXMon; Strip Out Order (RUN 135627) on a level of 0.1%  
             Prolems in SVXMON started at RUN 134449 (Dec  9 22:45) 
             This layer has sometimes also  
                  Bunch X Out of Sync  10% 
                  Pipeline Out of Sync 10% 
		  EOR Not Found,Wrong Chip Count &lt;0.1% 
 
             BUT: David's Error Monitor has NO bad entry for this  
                  Layer. ????  
 
IB0W1L3:    SVXMON; Strip Out of Order (RUN135627) on a level of 0.1% 
            Problems in SVXMON started at RUN 134848(Dec 14 06:52)  
  
	    DEM:  Sees problems on a 0.1-0.3% level. 
                  It seems to be a "7f" layer. 
                  Bits 1,3,4,5,6 of Chips b6 and a2 are set  
                  randomly and are producing Channel ID's=7f,3f,7d 
  
 
IB0W4L1:   SVXMON; Strip OUt of Order (RUN135627) at a level of 0.1% 
           Problems started in RUN 134720 ( Dec 12 17:56) on a level of 
           5%-0.1%. 
 
           DEM:   Does not show all RUNs, which had problems in  
                  SVXMON. eg. RUN 135560 is not reported, though it  
                  has Strip Out of Order errors in SVXMON. 
                  And SVXMON shows no error messages in RUNS, where  
                  DEM has bad events detected. e.g. 135545,134848  
 
                  I see in DEM, that this layer has sometimes problems 
                  in the order of 1-2%. Most of the events are starting 
                  with a c2c2 after the "backendstate" and no data 
                  is read out.  
                  Some events start with a non valid chip ID: f4,f6,ff 
                  and some events do have the "00 f3" problem.    
  
IB0W5L0:   SVXMON; Strip Ouf of Order (RUN 135628) on a level 0.05-0.1% 
           Problems started in RUN 135073 (Dec 17 09:34)                
    
           DEM:    DEM does not show all RUNS, which had problems in  
                   SVXMON: e.g. 135614. 
                   And SVXMON shows no error messages in RUN, where 
                   DEM has bad events detected: 135452      
                    
                   bit 6 high in one event causes channel ID problems. 
     
IB0W5L2:   SVXMON; Strip out of order, Duplicated Channel &lt;1% 
                   Problems started in RUN 134848 
 
           DEM:    DEM does not show all RUNS, which had problems in SVXMON 
                   And SVXMON shows no error message in RUN, where 
                   DEM has bad events detected.     
                    
		   This is a "7f" layer.  
                   Problems are caused by bit 0,1,2,3,4,6 high, where more 
                   than one bit is high at the same time.   
 
IB5W0L4:   SVXMON; Strip out of Order, EOR problems, Wrong Chip Count 
                   since RUN 134813 on the level of 0.27% 
                   
           DEM:    I see also discrepancy between SVXMON and DEM.  
                   This is a "7f" layer (Channel ID's).  
 
IB5W4L3:   SVXMON; Strip out of Order 
           DEM:    bad events 0.2-2.3% 
                   data stream starts with a "c2c2" after backendstate 
                   Some events are starting with wrong Chip "bf" instead 
                   with "8f", this is caused by bit5 and bit4 high. 
                   Some events do have wrong Channel ID's because  
                   several bits are set high.  
                   This layer is a "7f" layer.  
 
IB5W4L4    SVXMON; Strip Out of Order, 0.1-1% 
           DEM:    0.3-2%, one run 14% 
                   data stream stats with a "c2c2" after backendstate 
                   Channel ID wrong bit 5 high 
                   Some Events are starting with wrong Chip ID "ff" instead  
                   of "8f", this is caused by bit4,5,6 high.  
                   Channel ID because several bits are high at the 
                   same time.--&gt; "7f"       
  
IB5W5L0    SVXMON Strip Out of Order,EOR Problems,Wrong Chip Count 0.1% 
           DEM:   bad events 0.1-15% 
                  Channel ID's wrong, because bits0-6 are high at the  
                  same time--&gt; "7f" 
IB5W5L1    SVXMON Strip Out of Order  0.1% 
                  Stuck Bit | 1 | Cell id bit 0 gets  
                  stuck at 0 with probability 27.3859 %,100%(since RUN 135614) 
		  The probability increased from 27% until it reached 100%  
           DEM    bad events 100%, Problem was getting worser with runs  
                   
 
                  at this point ncdf17 not anymore avaible-&gt;no dave's web page 
 
IB5W5L2    SVXMON Strip Out of Order 0.1%-0.5% (starting at RUN 134933)   
                  EOR Not found, Wrong Chip Count 
 
 
SB0W3L0    SVXMON Strip Out of Order 0.1% (starting at RUN 135615) 
                  Last checked SVXMON RUn 135629  
 
SB0W8L2    SVXMON  Strip Out of Order 0,1% (starting at RUN 135614) 
                   Last checked SVXMON RUn 135629 
 
SB1W11L2   SVXMON  Invalid Word 0.1% (starting at RUN 128066) 
 
SB1W3L2    SVXMON  Strip Out of Order 0,1% (starting at RUN 135539) 
 
SB1W5L0    SVXMON  Pipeline Out of Sync C0-C3 12% Starting at RUn 135627  
                   Strip Out of Order 0.1%        Starting at RUN 135529 
SB1W5L1    SVXMON  Pipeline Out of Sync C0-C5 12% Starting at RUn 135627 
                   Strip Out of Order &lt;1%  Starting at RUN 135498 
SB1W5L3    SVXMON  Duplicate Channel   3%  
                   EOR Not Found       " 
		   Wrong Chip Count    " 
                   Strip Out of Order  10% 
		   C0-C6 Pipeline Out of Sync 12% 
                   C6 Stuck Bit | 1 | Cell id bit 3 gets stuck at 1 with 
                   probability 0.205339 %    
                   Saw this problems only in RUN 135627  
SB1W8L4    SVXMON   Strip Out of Order 0.1% (starting at RUN 134922) 
 
SB3W1L1    SVXMON  Strip Out of Order 0.2% (starting at RUn 135355) 
SB4W10L1   SVXMON  Strip Out of Order 0.6-1% (starting at RUn 135613) 
SB4W5L0    SVXMON  Strip Out of Order 0.1%  
                   Bunch X Out of Sync 50% 
_____________________________________________: 
 
Old friends: 
============ 
 
IB0W1L1 :    SVXMON: 11% Strip Out of Order 
             (first seen in RUN=134513 on a level of 0.4%) 
	     and rarely Duplicate Channel &lt;0.1% 
	     DEM: Channel ID's are wrong, because bit 2 is high.  
                  Channel ID's are wrong, because bit 0 is high.  
                  Chip ID's wrong because of  
                  bit 2 and/or bit 4 high.  
                  Bit 4 high is only seen, if Chip-ID's are messed up.  
	          Chip ID 8b - a4 are 9b-b4 (Bit 4 high) 
            
#23-12-2001# Still making problems, Last check RUN in SVXMON 135591 
#24-12-2001# Still making problems, Last check RUN in SVXMON 135627 
 
             
IB0W1L4:     1%  Strip Out of Order 
             (first seen in RUN 134813) 
	      
 
 
             DEM:  I couldn't correlated this error to any high/low bits in the  
                   data stream.  
	           It is always Chip 8c (phi side chip # 12),  
                   which has problems.  
                   And common to them is, that you see  
                      8c..7x..07..08.. 
                   While x=f,x=e,x=6 
                   or  
                      8c..6x..07..08..  
                   or 8c..5x..07..08.. 
              
#23-12-2001# Still making problems, Last check RUN 135591 
             This is actually a so called "7f" problem layer. 
#24-12-2001# Still making problems, Last check RUn in SVXMON 135627 
             Bits 0,3,4,5,6 of Chip 8c of first Channel are set  
             randomly and are producing Channel ID's=76,7f,66,47,77             
 
IB0W3L4:     95%  no data for  
	     I thought this was taken out of SVXMon ??  
             Last Run with problems for this layer in Dave's error monitor  
             is  134525 (50%). 
             One sees that Chip a1 is reading only "f3 00" after a few  
             channels.  
 
#23-12-2001# Still making problems, Last check RUN 135591  
#24-12-2001# Still making problems, Last check RUn in SVXMON 135631 
 
IB0W4L2:     SVXMON:  4%-17%   Duplicate Channel 
	              0.11%    Strip out of Order 
                      (First seen in RUN=134720 at a level of 17%) 
 
#23-12-2001#  Still making problems, last check RUN 135591 
              7% Duplicate Channel Errors 
#24-12-2001#  Still making problems, last check in SVXMON RUN 135629 
 
	     DEM:   DEM sees bad events on a level of 6-7%. 
                    Chip b4 has Duplicated Channels.  
                    It is always the Channelpair 31 31. 
                    this means somehow bit 0 is high, when chip 
                    b4 tries to produce channel id 30. ??     
                    And again, Chip ID's are wrong for Chip's 8b-b4,  
                    because of bit 4 high! 
                     
 
  
IB0W4L3:     SVXMON:  0.11% C0-2,C4-C8 Pipeline cell id is invalid  
	              (First seen in RUN=134812) 
                      EOR problems, Invalid cell Id 100% 
                      Stuck Bit, Cell id bit 0 gets stuck at 0  
                      with probability 100 % 
 
 
#24-12-2001# Making problems, Last checked RUN in SVXMON 135629 
   
	     DEM:     DEM sees bad events on a level of 30-100% 
                      CapID of Chip's are wrong because of bit 7 high.  
	              Bit 7 high is set randomly.  
                      It comes and goes, or stays for a while.    
		      Channel ID's wrong because several bits are  
                      set randomly high or low. 
 
                      In RUN ar0211be.001_f043 I see "00 f3" in the datastream.  
                      In this event the problem starts with a wrong  
                      ChipID "ff" instead of 8f (bit 4,5,6 high).   
	              Chip ID of are messed up from Chip 8b onwards until b4,  
                      because of bit 4 high. 
 
  
IB5W0L2:     SVXMON; 0.1- 5% Strip Out of Order 
	                     (First seen in Run=134612) 
                     *NEW*   Since RUN 135539, it has also  
                             sometimes Duplicated Channel Errors. 
 
#23-12-2001# Still making problems, Last check SVXMON RUN 135591 
#24-12-2001# Still making problems, last checked SVXMON RUN 135629 
   
	     DEM:    Chip ID's from 8b-a4 onwards wrong, because of bit 4 high. 
                     Channels are out of order, but I couldn't pin it down to  
                     a certain bit. What I see is, that most of the hickups are  
                     caused by a "7f" Chip ID, which appears out of order.  
                     This "7f" is caused by bit 0-6 high at the same time.  
                        
                      
 
 
IB5W2L1:     SVXMON;  0.233% C1-C14, Stuck Bit, Cell id bit 7 
	              (first seen in RUN=135162) 
	              C0 ~0.22% Strips Bad ADC Value 
                      (First seen in RUN=134720) 
	              C15 (first seeen in RUN=135542)  
                      Invalid Cell Id, Pipeline cell id is invalid. 
 
#23-12-2001# Still making problems, Last checked SVXMON RUN 135591 
             Stuck Bit, Cell id bit 7 gets stuck at 1 
             with a prob of 0.4%-1.4% 
             Now and then Strips -- BAD ADC Value 
#24-12-2001# Still making problems, Last checked SVXMON RUN 135629   
             Same error as above + Dupllicate Channel  
 
             DEM:     bad events 1.5-23% 
                      Chip ID's from 8b onwards wrong, because of bit 4 high. 
	              Cap ID's wrong because of bit 7 high 8%.  
                      This error is spread over various chip id's. 
	      
                      "7f" layer, Channel ID is wrong  
                       because of randomly set high bits, where one 
                       sees also more than one bit set high at the same 
                       time.  
 
                        
 
SB0W10: L0-L4:    0.1% Duplicate Channel 
		    (First seen in RUN=135313) 
        L1-L4:    0.1% Out of Order Chip ID 
                    (First seen in RUN=135355) 
#23-12-2001# Still making problems, Last check RUN 135591 
             Duplicated Channel in L0-L4, 0.1-1% 
             Out of order Chip ID  L1-L4  0.1-1% 
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
               
 
		L0: After a randomly choosen channel the datastream contains 
                    only "00 f3" until  
                    at some point chip 85 (which is not existing for this 
                    layer) is reached.  
		     
		    This list of "00 f3" is interpreted by SVXMon as 
                    Duplicated Channels. I did not see a real duplicated  
                    Channel Error for this Layer.  
#23-12-2001# Still making problems last check RUN 135613 
             SVXMON:Duplicated channel  
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
 
		L1: Last run with problems for this layer in Dave's error 
                    summary is run=135362 (2.2%) 
                    I see here again that "7f" is set as a channel id 
                    just randomly.  
                    I saw one example of a duplicated channel.  
#23-12-2001# Still making problems last check RUN 135613 
             SVXMON:Duplicated channel  
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
	        L2: I see here again that "7f" is set as a channel id 
                    just randomly. 
		    After a randomly choosen channel the datastream contains 
                    only "00 f3" until  
                    at some point chip 89 is reached.  
#23-12-2001#   Bit 0 low  
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
		L3: "7f" problem 
                    bit 1 high causes channel id out of order in data  
                    stream 
                    bit 4 low causes channel id out of order ind data  
                    stream    		     
		    bit 4 high causes channel id out of order in data 
                    stream 
#23-12-2001#        Duplicated Channel 
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
                L4: Last run with problems for this layer in Dave's error  
                    symmary is run=124829. (Must wait for the  
                    runs of today until the Dave's programm have 
                    processed them. ) 
#23-12-2001#       Duplicated Channel and Bit 0 low.  
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
		 
SB0W11L0:       0.1% Strip out of Order,Duplicate Channel 
                (first seen in Run=135539) 
 
		Last run with problems for this layer in Dave's error  
                symmary is run=124830. (Must wait for the  
                runs of today until the Dave's programm have 
                processed them. ) 
 
#23-12-2001# Still making problems last checked RUN 135613      
             No entry in DEM avaible.  
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
 
SB0W11L2 :     SVXMON  Out of Order Chip ID, in RUN  135591 on 0.1% level 
                       This channel has in RUN 135496 and 135498 
                       BAD ADC Value error.  23-12-2001 
                
               DEM:    Duplicated channels 
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
 
SB0W11L3:       SVXMON &lt;0.22% Duplicate Channel,Strip Out of Order 
                       ~1% EOR not Found, Invalid EOR,Invalid Word,  
                       Wrong Chip Count 
		       (First seen in RUN=128066) 
 
#23-12-2001# Still making same problems, Last check RUN 135591 
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
 
             DEM: bit 7 and/or bit 3 high causing Channel ID problems in Chip 
                 89. 
                 Further Chip ID errors due to bit 0 high.  
		 Cap ID problems  
		 Duplicated Channels, which are spread over all Chips. 
 
SB0W4L0:        &lt;0/5% EOR not found, Invalid EOR, Wrong Chip Count 
                ~1% Invalid Word 
                Last run with problems in Dave's error summary is run 
                135453 (1-20%). 
 
		Bit 7 high and/or   
                Bit5||Bit4||Bit3 high are causing Channel  
                Id out of order in the data stream.  
                Somehow all first 4 Bits are unstable for this layer.   
#23-12-2001# Still making same problems, Last check RUN 135612 
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
 
SB0W4L3:        8% Bad Chip ID 
                80% Chip sid Error 
                100% EOR Not Found 
                96%  Wrong Chip Count 
                88%  Out of Order Chip Id 
                12%  Invalid EOR 
                0.5% Invalid Word 
		 
		Last run with problems in Dave's error summary is run 
                135453 (100%). 
                Problems are caused by Bit 7 high, starts always at a3.   
 
#23-12-2001# Still making same problems, Last check RUN 135591 
             + BAD ADC values 
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
 
SB0W7L1: Strip Out of Order 1 out of 855 
	 no error's in daves error monitor 
#23-12-2001# No problems since RUN 135543 
             No errors in Dave's error monitor.  
#24-12-2001# Saw problem in RUn 135614, LLast checked SVXMON RUn 135631 
 
SB0W8L0: SVXMON Strip Out of Order in RUN=135543,135591 0.1-0.5% 
               Have to wait until Dave's Error monitor has processed this 
               runs.  
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
 
 
SB0W9L2: SVXMON  Strip Out Of Order 1 out of 855 
	         Duplicate Channel 
	         last run in Dave's error monitor=135453 
          
         DEM:    Couldn't pin it down to a single bit.  
                 Several low or high bits are giving wrong chip id's.   
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
 
SB0W9L3: Duplicate Channel 2 out of 855 
         last run in Dave's error monitor = 135362 (1-8%) 
	 "7f" problem (see above)          
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
 
   
SB0W9L4: SVXMON  Strip Out of order 1 out of 855 
	 DEM:    last run in Dave's error monitor = 135453 
	         (0.1%-30%) 
	         bit 5 low causes wrong channel id's. 
                 bit 7 high + bit 3 low causes wrong chip id's. 
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629  
 
 
SB1W10L2: 14% Strip Out of order 
           
	  last run in D.e.m= 135453 (2-30% bad events) 
	  wrong Chip Id because of bit 7 low for chip 86.  
          wrong Cap ID because of bit 3 low.  
          Not all of the Cap ID problems are caused by bit 3 low. 
          Cap ID problems due to randomly stuck high bits.  
#24-12-2001# Still making problems, Last checked SVXMON RUn 135629 
 
SB1W2L4: SVXMON Has Problems since 135277, 
                Bad ADC Value  5-18% 
                Wrong Chip Count,Pipeline Out of Sync 
                Strip Out of Order & Wrong Chip Count 0.1-0.5% 
	        
	 DEM: d0c2c2c4,c2c2 
              "7f" problems 
              bit 6 low (rarely)	        
#24-12-2001# Still making problems, Last checked SVXMON RUn 135631 
           
SB1W4L0:  SVXMON 84% Strip Out of Order 
                 C0 Stuck Bit, Cell Id bit 3 gets stuck at 1 prob: 0.23% 
                 C1-C3 No Data in 95% 
                 C0-C3 NO DATA,Stuck Cell Id | 1 | Pipeline cell id  
                 is stuck at 13 
	  DEM: "00 f3" problem. 100% 
 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
#24-12-2001# Still making problems, Last checked SVXMON RUn 135631 
 
SB1W4L1:  C0-C5 95% No DATA 
          not reported in D.E.M. 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
             in addition to that we now have also  
             C0: Stuck Bit | 1 | Cell id bit 3 gets stuck at 1  
             with probability 0.925926 % in RUN 135587 
             NO error report in DEM.  
#24-12-2001# Still making problems, Last checked SVXMON RUn 135631 
             But I think the no data problem ist related to a not  
             Restarted SVXMON.  
  
SB1W4L4:  C0-C13 95% NO DATa 
          not reported in D.E.M. 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
	     no report in DEM.  
#24-12-2001# Still making problems, Last checked SVXMON RUn 135631 
             But I think the no data problem ist related to a not 
             Restarted SVXMON. 
 
SB1W5L2:  SVXMON 2% Strip Out of Order (starting at RUN 135500) 
#23-12-2001# Still making same problems on the level of 0.5-2%, 
             Last check RUN 135591 
	     DEM: bit 5 high, random Chips 5-&gt;7 2.2% 
#24-12-2001# Still making problems, now we have also  
             Pipeline Out of Sync C0-C9 12% (starting at RUN 135627) 
             LaST checked SVXMON RUN 135629 
 
 
SB2W0L0:  0.11% Problems wiht EOR, Wrong Chip Count 
	   
          Bit 7 and/or Bit5 and/or Bit4 on Chip 83 high.==&gt; wrong Channel ID.  
	  sometimes, After a randomly choosen channel the datastream contains 
          only "00 f3". 
#23-12-2001# Still making same problems on the level of 0.5-1.0%, 
             Last check RUN 135591 
#24-12-2001# Still making problems, Last Checked SVXMON Run 135631 
   
SB2W0L2:  0.11% Problems wiht EOR 
          2%  Wrong Chip Count 
          C4-C7 Pipeline out of Sync 1 out of 855 
	  Strip Out of Order,Bad Chip ID 	   
	  last run reported in D.E.M=135453 
 
	  "d0c2c2c4" and other strange things, like Cap ID changes from  
          15 to 23 and frequently we see channel id with "00" for Chip 85 (may 
          be an OBDV failure (Dave's comment)). 
	  Sometime bit 3 is high and causes Cap ID problems.  
	   
#23-12-2001# Still making same problems on the level of 0.5-1.0%, 
             Last check RUN 135591 
             I see sometimes also Duplicated Channel. 
             Drops read out mostly on a0 and sometimes at 85. 
#24-12-2001# Still making same problems on the level of 0.5-1.0% 
             Last checked SVXMON RUn 135631 
 
SB2W1L3:  2% Strip out of order 
	  Bit 5 low in a3, causes channel id problems.          
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
#24-12-2001# Still making same problems, Last checked SVXMON RUN 135631 
 
SB2W1L4:  2% EOR Problems, Invalid Word, Wrong Chip Count 
	    
          C1 Pipeline Out of Sync 4 out of 843 
             Stuck Bit, Cell id bit 0 stuck at 1 28.44% prob. 
 
	  Bit 7 high on chip 8d. 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
             + C9-C12 Stuck bit, Cell id bit 2 gets stuck at 0 with prob. 
                79% in RUN 135580 
#24-12-2001# Still making problems, Last Checked SVXMON Run 135631 
 
    
SB2W6L4:  SVXMON  Strip Out of Order 1-15%   
                  Problems since 128066 on a 0.5% level 
                  with EOR and invalid Word.  
                   
          DEM:    a lot of bit errors, randomly getting high.  
    
#24-12-2001# Still making problems, Last Checked SVXMON Run 135631 
 
SB2W11L0: SVXMON 0.11% Strip out of Order 
	         last run reported in D.e.M. = 135362 (1-6) 
	   
	  DEM:   chip 83 "00 f3" !!!  
 
#23-12-2001# No problems since RUN 135543 
#24-12_2001# No problems since RUN 135543 
 
SB2W8L1: SVXMON  Problems started in RUN 135443 
                 Strip out of error on a 0.1% level.  
	 DEM     Chip 83, channel id 45 changes to 7f.  
#24-12-2001# Still making problems, Last Checked SVXMON Run 135631 
 
SB2W7L4: SVXMON  5% Duplicate Channel 
                 100% Out of Order Chip ID, Strip out of order 
                 C0 Invalid Cell Id, Pipeline cell id out of sync 2/15 
                 C1 No data 54/855 
                 C4-C13 NO DATA 95% 
                 C2   6% NO DATA 
                 C3   50% NO DATA 
 
         DEM:    DSerror mon 100%, since run 135453. 
                 Bit 1 stuck high 
		 Copies sometimes CAP ID of previous run. 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
#24-12-2001# Still making problems, Last Checked SVXMON Run 135631 
 
SB2W9L4: SVXMON C0-C13 NO DATA 95% 
         DEM:   bit 6 high 100% 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
#24-12-2001# Still making problems, Last Checked SVXMON Run 135631 
 
SB3W1L3: 90% Duplicate Channel 
         50% Out of Order Chip Id  
         0.11% level EOR Problems 
         C1,C3,C5,C7,C9 Stuck bit, Cell id bit 0 gets stuck at 1  
                                   prob: 15-27% 
 
        last processed run in daves erron mon is 135471. 
        Duplicate Channel rate here is of the order of 3%.  
        I don't see EOR problems. 
	Cap Id and Channel ID errors because of bit 0 high.  
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
#24-12-2001# Still making problems, Last Checked SVXMON Run 135631 
 
SB3W2L0: SVXMON Strip Out of Order in RUN 135501  
         DEM:   "00 f3" problem and no data read out at all.  
	         this layer has this 00 f3 problem now and than. 
#24-12-2001# No problems since RUN 135517 
 
 
SB3W2L4:  C0 INvalid Cell ID 70%, Pipelin cell id is invalid 
        no report in D.E.M. for runs taken in the last 3 days.         
 
#23-12-2001# No problems seen since RUN 135543. 
#24-12-2001# Problems seen in RUN 135614,since then quite. 
 
 
SB3W7L4:  SVXMON problems since RUN 128066 
                 Bunch X Out of Sync 50% 
                 Strip Out of Order  0.5%	 
	         Bad ADC Value 10% 
 
          DEM:  "7f" problem on chip a2 1% 
#24-12-2001# I see only Strip Out of Order errors 0.4% 
             Last checked SVXMON RUn 135631 
 
 
SB4W3L4: SVxMON problems since RUN 128066 with  
               Strip out of order on a 5-10% level 
	 DEM:  "7f"problem in chip 89 2%                
#24-12-2001# Still making problems, Last checked SVXMIN RUN 135631 
 
 
 
SB4W3L3:  SVXMON, problems in 135587 Strip out of Order 0.5% 
                
          DEM: In Dave's Error Monitor one sees  
          problems since 123496 
	  d0c2c2c4,c2c2 0.3-18% 
 
#24-12-2001# Problem seen in RUn 135614, since than quite. 
 
SB4W5L2:  SVXMON  Problems since RUN 128066 
	          Bunch X Out of Sync 50% 
	          Strip Out of Order 0.5% 
	  DEM:    "7f" problem in chip 87 
#24-12-2001# Still making problems, Last checked SVXMON RUN 135631  
 
SB4W6L3: SVXMON C0-C9  Stips Bad ADC Value 1/855 
         DEM:   Bit 3 high.  2% 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
#24-12-2001# Still making problems, Last checked SVXMIN RUN 135631 
          
SB4W7L1: SVXMON 10% Strip out of order  
                0.22% Duplicalte Channel,Out of order Chip ID 
         DEM:   bit 2 high.  	  
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
#24-12-2001# Still making problems, Last checked SVXMIN RUN 135631 
 
SB4W10L2:  SVXMON since RUn 135496, Bad ADC Value, Problems with EOr and  
                  wrong Chip Cpount 0.1-0.2% 
		  Duplicate Channel 
 
           DEM:   chip 89 has randomly set high bits, which are causing wrong  
                  channel id's. 
#24-12-2001# Still making problems, Last checked SVXMON Run 135631 
 
SB4W10L3:  SVXMON since RUN 135495, Wrong Chip Count,Bad ADC Value, 
                  Invalid Cell Id, Pipeline Out of Sync 1% 
                  since RUn 128350 strip Out of order  
   
	   DEM:	 d0c2c2c4,c2c2,c2c4 
		 Cap ID's wrong, but it is not always because of a high/low 
                 bit ?? 24-&gt;2b 
                copies sometimes cap id from previous event! 
#24-12-2001# Still making problems, last checked SVXMON  Run 135631 
 
 
SB5W10L4: SVXMON  50% Duplicate Channel, since run=135451  
          DEM:    Chip a1 has Duplicated channels 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
#24-12-2001# Still making problems, Last checked SVXMON Run 135631 
 
SB5W3L1:  SVXMON   C3 STRIPS BAd ADC Value, 28/855 
#23-12-2001# Still making same problems on the same level, 
             Last check RUN 135591 
             no report on D.E.M. 
#24-12-2001# Still making problems, Last checked SVXMON Run 135631 
 
SB5W11L1: SVXMON  Strip Out of Order 0.2%   
          DEM:    Channel ID 34 is randomly switch to 3c (bit 3 high). 0.5% 
#24-12-2001# Still making problems, Last checked SVXMON Run 135631 
 
SB5W5L4: SVXMON Problems since 135496 in SVXMON 
                BAD ADC, Duplicate Channel &lt;0.1% 
  
         DEM:  Duplicate Channels, "7f" Problems 
#24-12-2001# Still making problems, Last checked SVXMON Run 135631 
 
SB5W4L3: SVXMON Strip Out of Order 0.1%  
         DEM:   Bit 4 high on a0 1% 
#24-12-2001# Still making problems, Last checked SVXMON Run 135631  
 
SB5W2L2: SVXMON Strip Out of Order 0.1%  
         DEM:   "7f" problem 
#24-12-2001# Still making problems, Last checked SVXMON Run 135631 
 
SB5W0L2: SVXMON Strip Out of Order 0.1% 
         DEM:   "7f" problem 
 
#24-12-2001# Still making problems, Last checked SVXMON Run 135631 
 
 
 
 
 
</pre>
<!-- Author: cigdem  -->
<!-- Comment: Mon Dec 24 23;42;05 comment by...cigdem -->
<pre>&lt;a href=
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=85&frame=2&anchor=23:27:10'&gt;
List of problematic layers above 1% level&lt;/a&gt; 
</pre>


<!-- Date: Wed Dec 26 14:34:36 2001 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>DIAGNOSTIC of 26-12-2001 
======================== 
 
I will fron now onwards concentrate on single Bulkheads and  
will give an overview of their problems.  
 
I will begin with Bulkhead 2.  
 
--------------------------------------- 
 
SB2W0L0: 
         SVXMON: First Problem seen in SVXMON is at RUN 135060 0.3% level 
                 EOR not Found, 
                 Invalid EOR 
                 Invalid Word 
                 Wrong Chip Count 
                 Strip Out of Order 
                 Duplicate Channel   (1 time seen) 
         DEM:    bad events 0.5-1%, sometimes 2-11% 
                 Chip 83: most of the Channel ID Problems are caused 
                          by bit 5 high. 
                          some problems are caused by bit7   high 
                          there are also cases where  bit5,7 high 
 
                          and one sees also this: 
 
                          Channel ID 5a-&gt;ff: bit0,2,5,7 high 
 
                          0007 0105 0202 fcf3 ff07 5ef3 5f04 
                                         ^^   ^^ 
                                  bit5 high   bit5+bit1 high 
 
                          Channel ID 5d-&gt;fd: bit2,5,7 high 
                          Channel ID 5b-&gt;ff: bit2,5,7 high 
                          Channel ID 5a-&gt;fe: bit2,5,7 high 
                          Channel ID 5c-&gt;fe: bit1,5,7 high 
 
                          0007 0105 0202 fcf3 ff07 5ef3 5f04 
                                         ^^   ^^ 
                                  bit5 high   bit5+bit1 high 
 
                          0002 59f3 5a07 fbf3 fc05 5df3 
                                         ^^   ^^ 
                                    bit 5high bit5 high 
 
                          0007 01f3 5a03 ff05 fcf3 5d06 5e01 
                                         ^^   ^^ 
                                bit2,5,7high  bit 6 high 
 
                 Chip 82: bit 4 and 5 high ==&gt; Wrong Channel ID 
 
       general comment:   RUNS with a bad event level of 2-11% do have 
                          in addition to the bit errors "00 f3" errors!!!!: 
                          ar020fce.0001test_e200; 135118 
                          ar021091.0001test_e200; 135313 
                          ar0210b8.0001test_e200; 135352 
                          ar0210bb.0001test_e200; 135355 
                          ar0210bb.000atest_e200; 135355 
 
 
 
RUN:135628 - ar0211cc.0001_e200 
Event Number: 199004 
10500d0b 04104100 0000 0000 0000 0000 00000000 00000000 08160816 00000000 
e2000000 e3360000 0000 6a0c e0004afc 8313 0006 0107 0201 1302 1406 150c 160c 
..... 
4401 4507 4604 7ff3 c1c10000 
e2004afc 8313 0003 16f3 1706 18f3 1a01 1b06 1cf3 1d04 
 
bunch crossing 00,backend state 00, switches to layer SB3W3L6 also with 
bunch crossing 00,backend state 00, switches to layer SB0W0L0 with 
bunch crossing 4a,backend state fc, after reading out this layer, 
switches to SB2W0L0, bunch   crossing 4a, backend state fc 
 
               Silimon:  NO Entries for this layer 
 
 
</pre></td></tr></td></table>
<!-- Author: Cigdem  -->


<!-- Date: Thu Dec 27 01:29:26 2001 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>SB2W0L1: 
         SVXMON: First Problem seen in SVXMON is at RUN 135073 0.02% level 
                 But Problems increased since then to an level of 1% 
                 EOR Not Found 
                 Strip out of Order 
                 Wrong Chip Count 
                 Bad ADC Value (if it happens than on a level of 15-60%) 
 
         DEM:    bad events 1-5%, sometimes 15-25% 
                 c2c2,d0c2 c2c40000, d0c2c2c4  ,c2c4 
 
                 Chip 83, Channel ID 6b-&gt;63:  bit3 high 
 
                 Datastream gets often corrupted, can't pinned to a certain 
                 bit or error:\ 
 
                 ..... 7116 7207 7304 7502 760e 7704 7815 1e53 1852 0357 0756 
                                                          ^^   ^^   ^^ 
                  0054 0055 0ac3 0ff3 0401 0303 0402 0c07 0506 0a04 0505 040f 
                  ^^   ^^ 
                  040e 000a 021f 051e 001c ...... 
 
         general comment: This Layer may gave OBDV problems? 
 
         Silimon: No entries for this layer 
 
 
SB2W0L2: 
         SVXMON: First Problem seen in SVXMON is at RUN 135191 0.2% level 
                 Strip Out of Order 1-41% 
                 Wrong Chip Count 0.3-20% 
                 Pipeline Out of Sync 5-50% C4-C9 
                 Bad ADC Value 5% 
                 Duplicate Channel 70%-100% 
                 Invalid Cell Id 90% 
                 Stuck Bit | 1 | Cell id bit 0 gets stuck at 1 
                 with probability 0.290698 %-30% 
 
         DEM:    This is a really BAD LAYER. 
                 It has since RUN 135352 in all RUNs bad events on a level 
                 1%-98%, the last runs it had a level of bad events of ~3% 
 
                 -d0c2, c2c40000 
 
                 -CAP ID 01-&gt;18 bit3,4 high,bit0 low 
                  CAP ID 0e-&gt;12 bit4 high,bit2,3 low 
                  CAP ID 19-&gt;09 bit4 low 
                  CAP ID 17-&gt;21 bit5 high,bit4,1,2 low 
                  CAP ID 2b-&gt;2d bit2 high,bit1 low 
                  ChannelID 27-&gt;07 bit5 low 
                  ChannelID 28-&gt;08 bit5 low 
 
                 -Channel ID's are not always increasing: 
                  7006 71f3 76f3 7707 78f3 0808 0906 0a05 0c02 0d06 .... 
                                           ^^   ^^   ^^ 
                  4601 4706 48f3 6ff3 7006 71f3 7403 7505 76f3 5008 51f3 5203 
                                                               ^^   ^^   ^^ 
                  7001 7107 72f3 1a09 1b07 1f08 1d09 1e0b 1f08 
                                 ^^   ^^   ^^   ^^   ^^   ^^ 
 
                 * Calibration/test RUN(full readout mode): 
 
                   - d0c2c2c4 , d0c1c1c4 
 
                   -Channel ID 03-&gt;00 bit0,1 low 
                    Channel ID 56-&gt;02 bit2,4,6 low 
                    Channel ID 72-&gt;00 bit1,4,5,6low 
 
                    Chip ID    a3-&gt;00 bit0,1,5,7 low 
                    CAP  ID    15-&gt;06 bit0,4 low bit1 high 
                    CAP  ID    0c-&gt;03 bit2,3 low,bit1 high 
                    CAP  ID    01-&gt;0c bit2,3 high 
 
                   -Than we have also the case, that a lot of channel id's are 
                    set to 00 and after a while channel ID 
                    and ADC entries are "00 00" 
 
                   -6904 6a00 6b00 6c00 6dd0 c2c2 
                                            ^ 
                        shouldn't be here "70xx 71xx ... 7fxx" ?? in the 
                        full readout mode??? 
 
                   -In some events the datastream just stops after the chip 
                    id is read,like for example here: 
                     .... 7d00 7e00 7f02 a20a that's it. 
                    or 
                     .... 7b04 7c00 7d09 7e00 7f00 a204 that's it. 
 
                   -I see here also that the Channel numbers are not 
                    increasing always like for example in this case 
                    for chip a4: 
 
                    a419 0df3 0e1c 0f0d 10f3 17f3 1809 19f3 26f3 
                    2707 2808 29f3 2ff3 3007 31f3 .... 
                    7417 7507 7611 770b 780f 7916 7a10 7b15 
                    7c11 7d09 7e0b 7ff3 45f3 460e 470b 48f3 490c.... 
                                        ^^   ^^   ^^   ^^   ^^ 
                    I would expect in the full read out mode, that 
                    the channel ID should start from 00 and that 
                    they increase like 00,01,02...0f,10,11,.... 
                    What I see here is, that the first channel ID for this 
                    CHIP is ad, than it is skipping the Channels 11-16 and 
                    20-25. And as it reaches 7f, it start to parse 
                    40's. 
 
                   -I also see examples, were same channels are missing, 
                    but the datastream does goes back to smaller 
                    channel ID's. 
 
SB2W0L3: 
         SVXMON: First Problem seen in SVXMON is at RUN 135143 0.02% level 
                 A quite layer. I see only 4 RUNS with error messages in 
                 SVXMON. 
                 EOR not found 
                 Strip out of order 
                 Wrong Chip Count 
 
         DEM:    Also here I see only a few RUNS with bad events. 
                 The bad event level is 0.2-6% 
                 Since RUN 135362 no error messages. 
                 (Problems in RUN 135666 are due to turned off Silicon) 
 
                 -d0c2c2,c2c2 
 
                 -a lot of channels have several bits low, causing 
                  very small channels Id's or "00". 
 
                 -Channel ID 31-&gt;0c bit0,4,5low ,bit2,3high 
                  channel ID 48-&gt;00 all bits low 
 
SB2W0L4: 
         SVXMON: First Problem seen in SVXMON is at RUN 135230 17% level 
                 Strip Out of order 
                 This is a quite layer. I only saw one run wiht 
                 eRrors in SVXMON. 
 
         DEM:    Just a few RUNS wiht bad events on a level of 0.1-18% 
                 Since 135230 no errors. 
                (Problems in RUN 135666 are due to turned off Silicon) 
 
                 -CHIP 88, sets 2 randomly choosen Channels somewhere 
                  in the datastream to always 
                  the same pattern: "00f3 a6xx": 
                  ...7601 770a 7801 00f3 a620 15f3 1605 17f3... 
                                    ^^^^^^^^^ 
                                    ^^^^a single "00 f3" 
                 -Sometimes CHIP 88 parses only "00 f3". 
 
 
 
</pre></td></tr></td></table>
<!-- Author: Cigdem -->


<!-- Date: Thu Dec 27 12:53:54 2001 -->
<pre>Diagnostic of SB2w1: 
==================== 
 
 
SB2W1L0: 
         SVXMON: First Problem seen in SVXMON is at RUN 135117 1.5% level 
                 EOR not found 
                 Strip out of Order 
                 Wrong Chip Count 
                 I found 7 RUNS with error messages in SVXMON 
 
         DEM:    Just a few RUNS with bad events, on a level of 0.1-47% 
                 Since RUN 135362 no more bad events 
                 (Problems in RUN 135666 are due to turned off Silicon) 
 
                 -CHIP a1,82,83 are parsing a lot of "00 f3"'s. 
 
SB2W1L1: 
         SVXMON: First Problem seen in SVXMON is at RUN 135355 3% level 
                 Only one RUN found with ERRor messages in SVXMON. 
                 Strip Out of order 
 
         DEM:    Bad events level is 0.1%-6%, only one calibration run 100%. 
                 This layer is usually quite. During 
                 135181-135232,135451-135453 we had 
                 constantly in each RUn bad events. 
                 Since 135614 no bad events reported. 
 
                 -d0c2c4,00d0 c2c20000,d0 c2c20000, 
                 -datastream is messed up. I see frequently Channel and Chip 
                  ID "00" or some other low values. 
                 -see in some events only "00 f3" entries. 
 
                 * Calibration RUN 
                   -Here I see, that the first Chip ID is set to "ff" 
                   -d0c2c2c4,c2c40000 
 
 
SB2W1L2: 
         SVXMON: First Problem seen in SVXMON is at RUN 135115 &lt;0.05% 
                 EOR not Found 
                 Strip outof order 0.1%-3 
                 Wrong Chip count 0.1%-35% 
                 C6-C9 Pipeline Out of Sync 26%-100% 
                 Stuck Bit Cell id bit 0 gets stuck at 1 
                 with probability 0.39604 % 
                 Stuck Bit | 2 | Cell id bit 3 gets stuck at 0 
                 with probability 20 % 
                 Stuck Cell Id | 1 | Pipeline cell id is stuck at 128 
 
         DEM:    Problamatic Layer, I see a lot of runs (~60%) with 
                 bad events on a level of 3-96%. 
                 Since run 135471 no errors. 
 
                 -Cap ID's are wrong from Chip a3 or a2 onwards. 
                  Cap ID 15-&gt;23 bit1,5high bit2,4 low 
                  Cap Id 1d-&gt;15 bit3 high 
                  Cap Id 0d-&gt;1d bit4 high 
                  Cap ID 15-&gt;0d bit3 high, bit4 low 
 
                 -5d0c2 c4c40000,d0 d0c2c2c4,d0c1c1c40000 
 
                 -Channel ID wrong 
                  Channel ID 7d-&gt;04 bit0,3,4,5,6 low 
 
                 -Channel Id's are not increasing always 
                  7bf3 7c0c 7d0a 7e12 7f08 1a06 1b07 1c04 
                                           ^^   ^^   ^^ 
                  7cf3 7d23 7ef3 7f42 a012 00f3 0163 
                                      ^^   ^^^^ ^^ 
                                           ^^^^single "00 f3" 
 
                 -Some events do have only or a lot of "00 f3" entries. 
 
                 * Calibration RUN (full readout mode) 
 
                   -Cap ID's wrong from chip a3 onwards 
                    CAp ID 0c-&gt;03 bit0,1high bit2,3low 
                    Cap ID 24-&gt;01 bit0high bit2,5low 
                   -7e00c2c2 
 
SB2W1L3: 
         SVXMON: First Problem seen in SVXMON is at RUN 135060 22% 
                 Duplicate Channel   &lt;0.1% 
                 EOR not Found   22% 
                 Strip Out of Order 10-100% 
                 Stuck Bit | 1 | Cell id bit 0 gets stuck 
                 at 1 with probability 28.5714 % 
                 Nearly alls RUN after Problems start are buggy! 
         DEM:    A lot of RUNS do have bad events on a level of 1-55%. 
 
                 -Channel ID wrong in chip a3, 
                  most of the problems are caused by bit 5 low. 
 
                  Channel ID 29-&gt;0f bit5 low, bit1,2 high 
                  Channel ID 24-&gt;04 bit5 low 
                  Channel ID 72-&gt;52 bit5 low 
                  Channel ID 35-&gt;18 bit0,2,5 low, bit3 high 
                  Channel ID 60-&gt;20 bit6 low 
 
                 -d0d0c1c1c4 
 
SB2W1L4: 
         SVXMON: First Problem seen in SVXMON is at RUN 135060 0.3% 
                 EOR not found 
                 Invalid EOR 
                 Invalid Word 
                 Chip Side Error 
                 c0 Bad ADC value 
                 C1 Pipeline Out of Sync 
                 stuck bit Cell id bit 7 gets stuck at 1 with 
                 probability 2.15736 % 
 
         DEM:    A Lof of RUNS do have bad events on a level of 0.1-10% 
                 Channel ID in chip 8d wrong, 
                 Channel ID 60-&gt;e0 bit 7 high 
 
                 * Calibration RUN 
                   -Cap ID wrong from Chip a6 onwards 
                    Cap ID 03-&gt;2c bit2,3,5 high,bit0,1 low 
 
 
 
 
</pre>
<!-- Author: Hexa Cigdem  -->


<!-- Date: Thu Dec 27 16:01:47 2001 -->
<pre> 
 
Diagnostic of SB2W2  
===================  
 
This is a quite layer. Has only a few problematic Runs.   
 
SB2W2L0:  
        SVXMON: Problem seen in SVXMON only in RUN 135351 0.5%  
                Strip Out of Order  
        DEM:    NO ERRors since RUN 135355  
                Before this RUN I see only a few runs with bad events on  
                a 0.1-5% level  
 
                -data stream of chip 82  
                 contains after a while "00 f3" entries.  
 
                 Some events to start imidiataly with "00 f3" entries  
                -In some events Chip ID's are messed up from the first Chip  
                 onwards.  
                 The datastreams switches without parsing any chip channels  
                 to another layer:  
                 e2200000 e4220000 e4fc0000 e6740000 e7020000......  
                          ^^^^^^^^  
 
                 e2200000 e3100000 e51c0000  
                          ^^^^^^^^  
 
 
SB2W2L1:  
        SVXMON: Problem only seen in SVXMON is in RUN 135355 2%  
                Strip Out of Order  
        DEM:    Two runs with bad events seen on a level of 2.2and7%  
                (Problems in RUN 135666, because silicon was off)  
 
                -Chip and Channel ID's are often 00  
 
SB2W2L2:  
        SVXMON: First Problem in SVXMON starts at RUN 135279 0.5%  
                Strip Out of Order  
                only in very few RUNs problems,  
                Since RUN 135355 no problems  
        DEM:    4 runs with bad events on a level of 0.1-16%  
 
                -Channel ID wrong in Chip a3,88  
                 Channel ID 61-&gt;41 bit5 low  
                 Channel ID 1d-&gt;0d bit4 low  
 
                -I see events with "00 f3" entries.  
                -d0c2 c2c40000  
SB2W2L3:  
        SVXMON: First Problem in SVXMON starts at RUN 135164 0.1%  
                Strip Out of Order  
                C3,C9 BAD ADC Values 0.5-100%  
                No errors since RUN 135498  
        DEM:    One RUN with problems found on a 0.1% level  
 
                Channel ID wrong, because bit5 low.  
 
 
SB2W2L4:  
        SVXMON: First roblem in SVXMON starts at RUN 135279 2%  
                BAD AdC values  
                Since RUN 135500, no errors  
        DEM:    5 RUNS wiht bad events on a level of 0.1-0.5%  
 
                -The datastreams switches without parsing any chip channels  
                 to another layer: e2240000 e34a0000  
                -Channel ID are "00", or sometimes ff  
 
</pre>
<!-- Author: cigdem -->


<!-- Date: Thu Dec 27 16:55:24 2001 -->
<pre>Diagnostic of SB2W3 
=================== 
 
this is quite wedge....it has in few runs problems: 
 
 
SB2W3L0: 
        SVXMON: First problem in SVXMON starts at RUN 135293 0.05% 
                Strip Out of Order 
                Since 135615 no more errors. 
        DEM:    Just a few runs with bad events on a level of 0.1-5% 
                Since 135362 no problems 
                (Problems in RUN 135666, because silicon was off) 
 
                -Data stream contains "00 f3" entries. 
 
                * Calibration RUN; 
                  the datastream switches without parsing any channel entries 
                  to another layer: e2300000 e9420000 
                                             ^^^^^^^^ 
                  bunchcrossing and backendstate at the beginning of 
                  the datastream are 00. 
 
SB2W3L1: 
        SVXMON: First problem in SVXMON starts at RUN 135279 0.1% 
                Strip out of Order 
                Only 4 runs wiht errors 
        DEM:    just a few runs with bad events; level 0.1-2% 
                no problems since run 135471 
                (Problems in RUN 135666, because silicon was off) 
 
                -Channel ID in CHIP 84 wrong: 
                 Channel ID 06-&gt;26 bit5 high 
                 Channel ID 02-&gt;22 bit5 high 
 
                -Channel ID in CHIP 85 wrong: 
                 Channel ID 21-&gt;a1 bit7 high 
                 Channel ID 7d-&gt;f2 bit7 high 
                 Channel ID 7e-&gt;fe bit7 high 
SB2W3L2: 
        SVXMON:  first problem in SVXMON starts in run 135279 0.1% 
                 Strip Out of Order 
                 No errors since RUN 135497 
        DEM:     Only four runs with bad events; level 0.8-1.2% 
                 Since RUN 135355 no problems 
                 (Problems in RUN 135666, because silicon was off) 
 
                 -d0c1c1c40000 
 
                 * Calibration RUNS 
                   - the datastream switches without parsing any channel 
                     entries to another layer: 
                        e2320000 e9440000 e9440000 e9440000 
                     bunchcrossing and backendstate are "00" 
 
SB2W3L3: 
        SVXMON:  first problem in SVXmOn starts in run 135334 0.1% 
                 Strips outof order 
                 4 RUNS wiht errors. 
                 Last problematic run 135658 had 
                  Chip Side Error 
                  EOR not Found 
                  Wrong Chip count 
        DEM:     NO ERRORS :) 
                 (Problems in RUN 135666, because silicon was off) 
 
SB2W3L4: 
        SVXMON:  first and only problem in SVXMON starts in run 135355 0.1% 
                 Strips out of order 
        DEM:     two run with bad events, level 0.9%/21% 
 
                 -data stream contains "00 f3" entries. 
 
</pre>
<!-- Author: cigdem  -->


<!-- Date: Thu Dec 27 17:27:50 2001 -->
<pre>Diagnostic of SB2W4 + SB2W5 
=========================== 
 
*********************************************************** 
 
SB2W4: not included! 
 
*********************************************************** 
 
SB2W5 is a quite wedge, just a few problematic runs 
 
SB2W5L0: 
        SVXMON: NO ENTRIES, because layer is off 
 
SB2W5L1: 
        SVXMON: first and only problems in runs 135496 & 135517 3% 
                C2 BAD ADC value 
                Strip out of order 
        DEM:    NO ERrors 
                (Problems in RUN 135666, because silicon was off) 
SB2W5L2:  
        SVXMOn: first and only problems in run 135496 & 135498 1.5% 
                C8 BAD ADC Value 
        DEM:    9 runs with bad events on a level of 0.1-0.7% 
                since 124829 no problems 
                (Problems in RUN 135666, because silicon was off) 
 
                -datastream switches without parsing any channel/or 
                 chip entries to the next wedge: 
                  e2520000 e2520000 e2520000 .... 
                 Bunchcrossing and backendstate 00 
 
SB2W5L3: 
        SVXMON: first problems starting in run 135496 6% 
                C4 Bad AdC Value 
                Strip out of order 
                only 4 runs with errors 
 
        DEM:    NO ERRORS :) 
                (Problems in RUN 135666, because silicon was off) 
 
SB2W5L4: 
        SVXMON: first problems seen in run 135539 0.1% 
                Strip out order 
                Duplicate Channel 
                only 3 runs with errors 
        DEM:    9 runs with bad events on a level of 0.1-0.3% 
                since run 124830 no problems 
                (Problems in RUN 135666, because silicon was off) 
 
                -datastream switches without parsing any channel/or 
                 chip entries to the next wedge: 
                    e2540000 e3500000 .... 
                 Bunchcrossing and backendstate 00 
</pre>
<!-- Author: cigdem  -->


<!-- Date: Thu Dec 27 18:15:39 2001 -->
<pre>Diagnostic of SB2W6: 
==================== 
 
Layer 4 is BAD.  
 
SB2W6L0: 
        SVXMON: first problems seen in run 135434 0.25% 
                Strip out of order 
                EOR not found 
                Invalid EOR 
                Wrong Chip Count 
                Since run 135635 no problems. 
 
        DEM:    one run wiht problems,level 0.1% 
                -datastream switches without parsing any channel/or 
                 chip entries to the next wedge: 
                   e2600000 e37a0000 .... 
                 Bunchcrossing and backendstate 00 
                -Channel ID wrong 
                 Channel ID 55-&gt;fd bit3,5,7 high 
 
SB2W6L1: 
        SVXMON:  only problems in run 135434 0.25% 
                 Strip out of order 
        DEM:     NO ERRors 
                 (Problems in RUN 135666, because silicon was off) 
 
SB2W6L2: OFF 
SB2W6L3: OFF 
SB2W6L4: 
        SVXMON: first problems in run 128066;level 0.3% 
                Strip Out of order 
                EOR not found 
                Invalid EOR 
                Invalid Word 
                This layer has in nearly all runs errors and is still 
                making problems 
 
        DEM:    Almost all runs have bad events; level of 0.7-1.2% 
 
                -CHIP 8d: channel id's wrong 
                 Channel ID 67-&gt;77 bit4 high 
                 Channel ID 76-&gt;74 bit1 low 
                 Channel ID 78-&gt;76 bit1 low 
                 Channel ID 75-&gt;77 bit1 high 
                 Channel ID 77-&gt;f7 bit7 high 
                 Channel ID 67-&gt;f7 bit4,7 high 
 
                -datastream is messed up at the beginning 
                    e2640000 00005009 e00056fc 
                        ^^^^          ^^^^ 
                    Bunchcrossing 00 and backend state 00 
                    switches to another wedge. 
 
                -Sometimes Channel ID is set to "ff": 
                     8d29 00f3 fff3 6606 6703 
                          ^^^^ ^^^^ 
                          ^^^^ a single 00f3 entry 
                  or 
                     8d1c 00f3 cff3 0000 
                          ^^^^ ^^^^ 
</pre>
<!-- Author: cigdem -->


<!-- Date: Fri Dec 28 19:30:45 2001 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>Ze plan 
======== 
 
1) SVX/ISL integrated biased until shot end 
 
IF beam lost AND/OR bad conditions  
 
a) Ace puts SVX/ISL in STDBY. Use Ifix voltage page and 
verify SI PS GUI also indicated SVX/ISL are in stdby mode. 
 
b) If 4-5 hours until shot setup again and HEVB types  
available(Boris?) concentrate on fixing L00 EVB problems. 
Will need access to HEVB and Svx crates. 
  
IF no beam, good conditions and no L00 EVB studies needed 
 
a) SI is biased (call main pager for instructions)   
 
b) Take SVX calibration runs DPS ON and DPS OFF 5000 events 
each. Use COSMIC 4_2_0 null table. Instructions on ACE page. 
 
If no beam, calibrations done, evb work done 
 
a) Integrate SI in stdby. 
</pre></td></tr></td></table>
<!-- Author: Mad Mary -->


<!-- Date: Wed Jan 2 17:35:54 2002 -->
<pre>Error analysis for calibration runs taken on Dec. 30 by Mary 
 
------------- 
135950 DPS ON 
------------- 
Exactly zero errors from David's error monitor. 
 
In SVXMon, we see the following errors: 
SB4W10L3 --  Wrong Chip Count and Pipeline cell out of sync  
SB5W5L4  --  Duplicate Channel 
SB5W6L3  --  Pipeline Out of Sync 
 
-------------- 
135951 DPS OFF 
-------------- 
There are a few errors in the error monitor. 
SB5W5L4 -- some channel ID's are wrong for every event  
	   (only in the upper channels of chip 8d) 
 
In SVXMon, we see the following errors: 
SB4W10L3 --  Wrong Chip Count and Pipeline cell out of sync 
SB5W5L4  --  Duplicate Channel 
(The duplicate channel errors persist in SVXMon even in cosmic  
and physics runs taken the shift following the calibration runs.   
Then they go away one day later.) 
 
 
But there are no "7f" errors for either of these calibration  
runs.  (Does this exonerate DPS as a suspect?) 
 
</pre>
<!-- Author: Jason -->


<!-- Date: Fri Jan 4 18:14:55 2002 -->
<pre> 
 
Problem found OFFLINE: 
====================== 
 
  silicheck result from Run134930 - 135453  
          
IB0W3   : was integrated and biased, but no histograms at all.  
 
IB5W3L3 : Secondary phiwedge is dead.  
          There are two phiwedges in this ladder,  
          phiwedge 13 and 14. Look at these histograms 
            &lt;a href="http://www-cdf.fnal.gov/internal/people/links/NahoTanimoto/examples/Run135449IB5W3L3_phiwedge13_r.ps"&gt;Run135449IB5W3L3_phiwedge13_r.ps&lt;/a&gt; and  
            &lt;a href="http://www-cdf.fnal.gov/internal/people/links/NahoTanimoto/examples/Run135449IB5W3L3_phiwedge14_r.ps"&gt;Run135449IB5W3L3_phiwedge14_r.ps&lt;/a&gt; 
 
          The first 4 histograms are for Bulkhead4,  
          and the next 4 histograms are for Bulkhead5. 
          phiwedge13 looks good, but phiwedge14 is bad. 
          I also checked silicon e-log. 
          The VBias trip had happened on Aug 13, click &lt;a href="/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=61&anchor=08%3A32%3A49&hilite=IB5W3L3"&gt;here&lt;/a&gt;. 
 
------------------------------------------------------------ 
  silicheck result from Run135614 
 
IB5W5L1 : stuck bit (red is r-phi side and blue is z side.) 
          &lt;a href="http://www-cdf.fnal.gov/internal/people/links/NahoTanimoto/examples/Run135614IBH5W5L1.ps"&gt;Run135614IBH5W5L1.ps&lt;/a&gt; 
          upper histogram : all cluster 
          under histogram  : cluster on track 
          See &lt;a href="/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=86&scroll=false&anchor=11:22:29"&gt;here&lt;/a&gt;. 
 
SB2W7L4 : z-side is dead, and r-phi side is stuck bit. 
          &lt;a href="http://www-cdf.fnal.gov/internal/people/links/NahoTanimoto/examples/Run135614SB2W7L4.ps"&gt;Run135614SB2W7L4.ps&lt;/a&gt; 
         
          I think this ladder was integrated and biased in Run135448 at first. 
          But I can't check the structure of it as Run135448 was statistically poor. 
          The next run 135449 was stuck bit. 
     
          Then, look at this, &lt;a href="http://www-cdf.fnal.gov/internal/people/links/NahoTanimoto/examples/Run135614SB2W7L4_r.ps"&gt;Run135614SB2W7L4_r.ps&lt;/a&gt; 
          First seven histograms are SBH2, and next seven are SBH3. 
          Look at the number of entries on it. 
          First chip has 137 entries, and second has 35, 
          but 3rd, 4th, ... have no entries. 
          And z-side of this ladder is completely dead. 
 
SB0W4L1 : z-side 3rd chip is dead 
SB0W4L3 : z-side is dead 
SB0W6L1 : low occupancy for all chips both side 
SB1W1L0 : r-phi side Landau peak is shifted to high. z-side is OK. 
SB1W4L0 : z-side is dead. r-phi side 2nd chip is also dead. 
SB1W4L1 : both sides are dead. No ADC histograms. 
SB1W4L4 : both sides are dead. No ADC histograms. 
SB2W9L0 : z-side is bad Landau shape. Landau peak is around 17. 
SB2W9L1 : r-phi side is not Landau shape. Peak is around 52. z-side is OK. 
SB2W9L4 : Both sides are dead. 
SB2W11L0 : r-phi side is not Landau shape. Peak is around 55. z-side is OK. 
SB3W0L2 : r-phi side is OK. z-side is low occupancy compared with r-phi side  
          and not Landau shape. 
SB3W8L0 : z-side is low occupancy. 
SB3W8L1 : Both sides are dead. No ADC histograms 
SB3W8L2 : Landau peak of 3rd and 4th chips in z-side are low, around 13 and 17. 
SB3W8L3 : Both sides are dead. No ADC histograms 
SB3W8L4 : r-phi side is OK. z-side is not Landau shape. 
SB4W5L0 : r-phi side is not Landau shape. Peak is shifted to high, around 54. 
          z-side is OK. 
SB5W3L1 : Both sides are not Landau. r-phi side is just spreaded broadly, and  
          z-side is low occupancy.  
</pre>
<!-- Author: Naho -->


<!-- Date: Fri Jan 4 18:17:49 2002 -->
<table border=0><td><tr><td bgcolor=#e0e030><h2> 
<a href= 
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=87&frame=2&anchor=18:15:00'>7f Problem Solved in SB4W3L4</a><p></h2> 
Aaron</td></tr></td></table>
<!-- Author: Aaron -->


<!-- Date: Tue Jan 8 23:14:39 2002 -->
<pre>Pre-access summary of non-tracking wedges. 
A tracking wedge has reasonable (could be imperfect) 
data from &lt;=3 layers. 51 wedges are tracking wedges. 
 
SB2W1L2-3, SB2W7L4, SB2W9L4, SB3W1L1, and SB3W2L0 
are currently integrated but give enough online errors 
to have compromised data and therefore create a  
nontracking wedge. 
 
===================================================== 
 
14 have 3 ladders, here are the reported symptoms: 
 
Wedge,Layer,Problem 
      /L2  6th chip AVDD2 'bizarre data' 
SB0W1  
      \L4  AVDD overcurrent                 
 
      /L3  bias shorted at JC 
SB0W8 
      \L4  no init, no data 
 
      /L1  unbiasable 
SB0WB 
      \L4  chip 87: 7x-&gt;3x 
 
      /L2  missing chips, multiple chips 
SB2W1 
      \L3  chip A3 bit 5 low 
 
      /L0  flaky init, OBDV bad 
SB2W5 
      \L4  high IDVDD when running 
 
      /L2  bit 6 50uW 
SB2W6 
      \L3  c4c4c4c4 reformatter 
 
      /L1  bit 1 0uW 
SB2W7 
      \L4 bit 1 high 
 
      /L2  chip 88 no FE 
SB2W8 
      \L4  AVDD2 6th chip 
 
 
      /L3  bit 0 high 75% events (DErM) 
SB3W1 
      \L4  unbiasable 500@5V 
 
 
      /L0  OBDV 35% (DErM) 
SB3W2 
      \L2  DVDD OV 
 
      /L1  bit 1 low, untested swapped RX 
SB3W7 
      \L2  unbiasable 
 
      /L3  bit 7 high 
SB4W4 
      \L4  unbiasable 1390@6V 
 
      /L2  Drop RO last chip 
SB4W7 
      \L4  last chip CAPID 
 
      /L1  Plastic reported MIA, Drop RO 
SB4W8 
      \L2  Drop RO 4% 
 
============================================== 
 
2 have 3 ladders out, here are the reported symptoms: 
 
      /L2  ?? no record  
SB0W3  L3  chip 5 no FE 
      \L4  No init, no data 
 
      /L0  No FE 
SB0W6  L2  AVDD2 
      \L3  DVDD overcurrent 
 
 
============================================ 
 
One with 4 ladders out: 
 
SB5W3 L0  No DVDD current drawn 
      L2  DVDD OV 
      L3  No DVDD current drawn 
      L4  'cell logic' 
 
============================================ 
 
4 with all layers off: 
 
SB1W4 Pilot error (meant SB0W4) 
 
SB1W7 PRD2 
 
SB2W4 Init RB off by one, no data 
 
SB3W4 No init, no data 
 
====================================== 
 
21 non tracking wedges</pre>
<!-- Author: LHM -->
<!-- Comment: Tue Jan  8 23;19;20 comment by...lhm -->
<pre>clerical error: 
SB2W8 should be SB2W9</pre>


<!-- Date: Wed Jan 9 00:08:05 2002 -->
<pre>So actions to take. 
 
================================================== 
 
Six wedges can apparently be recovered by reintegration: 
 
SB0WBL4 
SB2W9L2 
SB4W8L2 
SB4W7L4 
SB0W3L2,3 
SB1W4,all 
 
===================================================== 
 
Of the remaining, I confirmed symptoms if possible, 
noted if different, and figured on some actions: 
 
SB0W1L2 reintegrate with ISEL sixth chip 0 
SB0W1L4 check AVDD regulator (reduce AVDD) 
 
SB0W8L4 HST fine 100k events. Reintegrate. 
 
SB2W1   Replace VRB. Symptoms implicate it. 
 
SB2W4   Now no init at all. Check FIB command cable. 
 
SB2W5L0 HST sees rare drop RO chip A0. Reintegrate. 
 
SB2W6L2 HST drop RO chips A0. (no bit6?) Reintegrate. 
SB2W6L3 HST confirms c4c4c4c4, look at OBDV? 
 
SB2W7L4 HST confirms bit 1 high. Optical tests. 
 
SB3W1L3 HST fine. 
 
SB3W2L0 HST drop RO chip A0. 
SB3W2L2 DVDD OV, check LV cable 
 
SB3W7L1 HST fine. Reintegrate. 
 
SB4W4L3 HST fine. Reintegrate. 
 
SB5W3   L0,2,3 now draw no current and no init. 
        Check LV cable. 
 
================================================= 
 
Or to summarize for the access: 
 
Reintegrate: 
SB0WBL4 
SB0W8L4 
SB2W5L0 
SB2W6L2 
SB2W9L2 
SB3W7L1 
SB4W4L3 
SB4W8L2 
SB4W7L4 
SB0W3L2,3 
SB1W4,all 
 
Optical tests: 
SB2W7L4 check bit 1 
SB2W6L3 check OBDV 
 
Power supply: 
SB0W1L4 reduce AVDD voltage to check regulator 
SB3W2L2 DVDD overvoltage: check LV cable grounds 
SB5W3   check LV DVDD for open on L1,2,3 
 
Other: 
SB0W1L2 ISEL bits, reintegrate 
SB2W1   replace VRB 
SB2W4   check FIB timing cable 
 
Puzzlers: 
SB3W1L3 Offline bit 0 high not seen in HST 
SB3W2L0 HST does not match offline OBDV problem 
 
================================================== 
 
Since not many of these things are access oriented,  
someone should perhaps make a prioritized list of Layer 0 
problems. I will try this tomorrow afternoon if possible. 
</pre>
<!-- Author: lhm -->


<!-- Date: Sat Jan 12 15:21:46 2002 -->
<pre>The idea here is to provide a snapshot of the diagnosed problems 
in silicon.  I am basing most of these observations on runs 
136852 and 136860.  A more detailed analysis of each problem 
will have to wait for the data to arrive at the error parser. 
(fcdfsgi2 is still down.) 
 
Welcome Layer 00 to the Strip Out of Order parade. 
 
SiliMon errors 
SB2W5L0PC0 stuck bit 1 (cross-reference with SVXMon below) 
 
SVXMon errors 
IB0W1L1   Strip Out of Order (10%) 
          Duplicate Channel (&lt;1%) 
IB0W3     No Data 
IB0W4L1   Strip Out of Order (5%) 
          Duplicate Channel (&lt;1%) 
IB4W3L0   No Data 
IB4W3L2   No Data 
IB4W3L4   No Data 
IB5W2L1   all chips have stuck cell id bit 7 (1%) 
IB5W5L4   No Data 
LB1W0L2   Strip Out of Order (&lt;1%) 
LB1W4L3   Strip Out of Order (&lt;1%) 
SB0W0L2   Strip Out of Order (30%) 
          No Data on last 7 chips 
SB0W2     Pipeline out of sync (all chips, all layers!) 
SB0W2L3   Strip Out of Order (15%) 
SB0W3L3   No Data 
SB0W4L1   Strip Out of Order (&lt;1%) 
SB0W5L0   Duplicate Channel (&lt;1%) 
SB0W5L4   Duplicate Channel (&lt;1%) 
SB0W6L1   Duplicate Channel (&lt;1%) 
SB0W6L4   Duplicate Channel (&lt;1%) 
SB0W7L3   EOR Not Found (1%) 
          Cell id bit 2 gets stuck at 1 with prob 2% (last 9 chips) 
SB1W1L3   Strip Out of Order (&lt;1%) 
SB1W10L2  Strip Out of Order (25%) 
SB1W2L2   Invalid Cell Id (5-10%) 
          Pipeline Out of Sync (50%) 
          No Data (last 4 chips) 
SB1W4L2   Strip Out of Order (1%) 
SB1W5L2   Strip Out of Order (&lt;1%) 
SB2W0L2   Wrong Chip Count (&lt;1%) 
SB2W0L4   Bunch X Out of Sync (3%) hmm.. that's a new one for me 
          Duplicate Channel (20%) 
SB2W1L3   Strip Out of Order (20%) 
SB2W5L0   Strip Out of Order (100%) 
          No Data (last 3 chips) 
SB2W6L2   Strip Out of Order (&lt;1%) 
SB2W6L4   Invalid Word (1%) 
SB2W7L4   Out of Order Chip ID (&lt;1%) 
SB3W0L2   Bunch X Out of Sync (1%) 
SB3W1L3C1 Cell id bit 0 gets stuck at 1 with prob 1% 
SB3W2L0   Strip Out of Order (60%) 
SB3W3L3   Strip Out of Order (&lt;1%) 
SB4W0L3   Strip Out of Order (&lt;1%) 
SB4W0L4   No data (last 13 chips) 
          Pipeline out of sync 100% on chip 0. 
          **This is the ladder with the new AVDD2 problem noted 
          In the logbook by Jean and Saverio.** 
          First problem is in run 136852. 
SB4W3L0   Bad ADC Values (value is -5, what's special about -5?) 
SB4W3L4   Strip Out of Order (3%) 
SB4W6L2   Duplicate Channel (6%) 
SB4W7L1   Strip Out of Order (15%) 
SB4W8L2   Strip Out of Order (40%) 
          Wrong Chip Count (60%) 
SB5W10L4  Duplicate Channel (5%) 
SB5W3L1C3 Bad ADC Value 528 in 25% of events 
SB5W3l4C4 Pipeline Out of Sync (99%) 
SB5W7L0C2 Stuck cell ID bit 7 (1%) 
</pre>
<!-- Author: Jason -->